[Kedar Nimbalkar] hyperbolically advertises the ultimate cell phone speaker dock. It costs a dollar. It doesn’t need you to pair with it via Bluetooth or WiFi. It pairs extremely fast, 0.000000000001, he clarifies. It may also look like a broken laptop speaker with a stomped wall wart soldered to it, but who can keep up with industrial design trends these days?
He shows us the device in operation. He starts playing some music on his phone’s speaker. It’s not very loud, so he simply lays the phone on the dock. Suddenly, all the audio fidelity a Dell Lattitude from the 90s can provide erupts from the device! How is this done?
Of course, there’s not much to the trick. Since the cellphone speaker is a coil it can induce a small current in another coil. The resulting voltage can be picked up by an audio amplifier and played through the speakers. Nonetheless it’s pretty cool, and we like his suggestion of betting our friends that we could wirelessly pair with their ear buds. Video after the break.
Once again, [Rulof]’s putting his considerable hacking abilities to good use, his good use that is. By modding a few simple parts he’s put together something that he can carry around on his keychain that’ll allow him to steal power from his friend’s phones to charge his own phone.
He starts by cutting away the motor from an iPhone fan to isolate the Micro USB connector. He then removes the charging circuit board from a cheap Chinese USB power bank, and solders wires from the Micro USB connector to one side of the board. Lastly, he cuts away the Lightning connector from a Lightning-to-USB cable and solders that connector to the other side of the circuit board. For longevity and cosmetics, he puts it all in a small wood block and connects a key ring. The result is a small, neat looking box with a Micro USB connector on one side and a Lightning connector on the other. You can see him make it, and then use it to steal power from his friends in the video after the break.
It was one of the more interesting consumer tech stories floating around at the turn of the century, a disposable cell phone manufactured using a multi-layer folded paper circuit board with tracks printed in conductive ink. Its feature set was basic even by the standards of the day in that it had no display and its only function was to make calls, but with a target price of only $10 that didn’t matter. It was the brainchild of a prolific New Jersey based inventor, and it was intended to be the first in a series of paper electronic devices using the same technology including phones with built-in credit card payment ability and a basic laptop model.
The idea of a $10 mobile phone does not seem remarkable today, it’s possible that sum might now secure you something with features far in excess of the Nokias and similar that were the order of the day at that time. But when you consider that those Nokias could have prices well into three figures without a contract, and that the new features people considered exciting were things like integrated antennas or swappable coloured plastic covers rather than the multicore processors or high-res cameras we’re used to today, a phone so cheap as to be disposable promised to be very disruptive.
The web site publicity shot for the disposable paper phone.
The product’s wonderfully dated website (Wayback Machine link, we’ve skipped the Flash intro for you) has pictures of the device, and the video below the break features shots of it in use as its inventor is interviewed. But by the end of 2002 the Wayback Machine was retrieving 404 errors from the server, and little more was heard of the product. No sign of one ever came our way; did any make it to market, and did you have one?
With the benefit of fifteen years hindsight, why did we not have paper mobile phones as part of the ephemera of the early years of the last decade? It was not a product without promise; a ten-dollar phone might have been a great success. And the description of a cheap laptop that talks to a remote server for its software sounds not unlike today’s Chromebooks.
Some of you might claim the product was vapourware, but given that they demonstrated a working prototype we’d hesitate to go that far. The likelihood is that it did not find the required combination of component price and manufacturing ease to exploit its intended market segment before its competition improved to the point that it could no longer compete. If you have ever taken apart a typical mobile phone of the period you’ll have some idea of why they were not cheap devices, for example the RF filter modules of the day were individually adjusted precision components. And paper-and-ink printed circuit boards are still a technology with a way to go even now, perhaps the idea was simply too far ahead of its time. Meanwhile within a relatively short period of time the price of simple candybar phones dropped to the point at which they would tempt the $10 buyer to spend more for a better product, so the window of opportunity had passed.
[Sergey Mironov] sent in his SelfieBot project. His company, Endurance Robots, sells a commercial version of the bot, which leads us to believe that in a strange and maybe brilliant move he decided to just sell the prototype stage of the product development as a kit. Since he also gave away the firmware, STLs, BOM, and made a guide so anyone can build it, we’re not complaining.
The bot is simple enough. Nicely housed hobby servos in a 3D printed case take care of the pan and tilt of the camera. The base of the bot encloses the electronics, which are an Arduino nano, a Bluetooth module, and the support electronics for power and motor driving.
To perform the face tracking, the build assumes you have a second phone. This is silly, but isn’t so unreasonable. Most people who’ve had a smart phone for a few years have a spare one living in a drawer as back-up. One phone runs the face tracking software and points the bot, via Bluetooth, towards the user. The other phone records the video.
The bot is pretty jumpy in the example video, but this can be taken care of with better motors. For a proof-of-concept, it works. A video of it in action after the break.
Smartphones are the opium of the people. If you need proof, just watch the average person’s reaction when they break “their precious”. Repairing smartphones has become a huge business. The most often broken item on phones is of course the front glass. In most cases, the screen itself doesn’t break. On newer smartphones, even the touchscreen is safe. The front glass is only a protective lens.
The easiest way to repair a broken front glass is to swap the entire LCD assembly. For an iPhone 6 plus, this will run upwards of $120 USD. However, the glass lens alone is just $10. The problem is that the LCD, digitizer and front glass are a laminated package. Removing them without breaking the wafer thin LCD glass requires great care. The hardest part is breaking down the optical glue securing the glass to the LCD. In the past that has been done with heat. More recently, companies from China have been selling liquid-nitrogen-based machines that cool the assembly. Now immersing a phone screen in -196° C liquid nitrogen would probably destroy the LCD. However, these machines use a temperature controller to keep a surface at -140° C. Just enough to cause the glue to become brittle, but not kill the LCD.
[JerryRigEverything] doesn’t have several thousand dollars for a liquid nitrogen machine, but he does have a $5 block of dry ice. Dry ice runs at -78.5°C. Balmy compared to liquid nitrogen, but still plenty cold. After laying the phone screens down on the ice for a few minutes, [Jerry] was able to chip away the glass. It definitely takes more work than the nitrogen method. Still, if you’re not opening your own phone repair shop, we think this is the way to go.
You need to get an SPI bus on something right now, but you left your laptop at home. No problems, because you’ve got your Bus Pirate and cellphone in your pocket. And a USB OTG cable, because you’re going to need one of those. And some probes. And maybe a soldering iron for tacking magnet wire onto those really small traces. And maybe a good magnifying glass. And…
OK, our fantasy of stepping away from the party for a quick JTAG debugging session is absurd, but what’s not at all absurd is the idea of driving your Bus Pirate from a nice GUI app on your Android phone. [James Newton] wrote DroidScriptBusPirate so that he wouldn’t have to hassle with the Bus Pirate’s nested single-character menu system, and could easily save complete scripts to do common jobs from pleasant menus on his phone.
The setup depends on downloading DroidScript, a free Javascript and HTML5 IDE, and then pasting and saving [James]’ code. He’s written up full instructions to help you with the install. It’s not so hard, and once you’re done you’ll be ready to drive the Pirate from the comfort of your phone.
In fact, now that we think of it, we’re missing a Bus Pirate GUI for our desktop as well. Whenever we have complex tasks, we end up scripting something in Python, but there ought to be something more user-friendly. Anyone know of a good GUI solution?
Readers of a certain age will remember the payphone trick of letting the phone ring once and then hanging up to get your quarter back. This technique was used with a pre-planned call time to let someone know you made it or you were okay without accruing the cost of a telephone call. As long as nobody answered you didn’t have to pay for the call, and that continues to be the case with some pay-per-minute cellphone plans.
This is the concept behind [Antonio Ospite’s] ringtone data transfer project called SaveMySugar. Don’t judge him, this work has been ongoing for around ten years and started back when cellphone minutes were a concern. We’re just excited to see that he got the excruciatingly slow thing to work.
Those wanting to dig down to the nitty-gritty of the protocol (and you should be one of them) will want to read through the main project page. The system works by dialing the cellphone, letting it ring once, then hanging up. The time between redials determines a Morse code dot, dash, or separation between characters. Because you can’t precisely determine how long it will take each connection to read, [Antonio] built ‘noise’ measurement into the system to normalize variations. The resulting data transfer works quite well. He was able to transfer the word “CODEX” in just six minutes and thirty seconds. But it is automatic, so what do you care? See the edge-of-your-seat-action play out in the video below.
