With mobile phones now ubiquitous for the masses in much of the world for over two decades, something a lot of readers will be familiar with is a drawer full of their past devices. Alongside the older smartphone you’ll have a couple of feature phones, and probably at the bottom a Nokia candybar or a Motorola flip phone. There have been various attempts over the years to make use of the computing power the more recent ones contain through using their smartphone operating systems, but the older devices remain relatively useless.

[Vishwasnavada] has a neat plan though, using an ancient phone as a remote trigger device, by interfacing it with an Arduino. There are many ways this could be achieved depending on the model of the phone in question, but one thing common to nearly all devices is a vibration motor. Removing the motor and taking its power line to a GPIO allows the Arduino to sense when the phone is ringing. The idea then is that a call can be placed to the phone which is not picked up, but because it triggers the vibration motor it can be used to make the microcontroller do something remotely. A hack with limited capabilities then, but one that is cheap and simple, uses a recycled device, and should work almost anywhere populated on the planet given the global reach of 2G networks.

This isn’t the first respin of a classic Nokia we’ve brought you, they will also talk data.

App development is not fun for everyone, and sometimes you just want to control a device from your phone with minimal work. Blynk appears to be a fairly put-together library for not only hooking up any Arduino or esp8266 to a phone through WiFi, but also through the net if desired.

Install the app onto your iPhone or Android device. Install the libraries on your computer. Next, modify your Arduino source to either pass direct control of a pin to Blynk, or connect Blynk to a virtual pin inside your code for more advanced control. If you want to go the easy route, create an account, log into the app, and drag and drop the interface you’d like. If the idea of letting some corporation host your Arduino project sends shivers down your spine, there is also an option to host your own server. (Editorial snark: Yes, it requires a server. That’s the cost of “simplicity”.)

There have been a few times where we’ve wished we could add app control to our projects, but installing all the libraries and learning a new language just to see a button on a screen didn’t seem worth it. This is a great solution. Have any of you had experience using it?

The Nokia 3100 is a classic in the circles we frequent. The LCD in this phone is a very cheap and very common display, and it was one of the most popular phones since the phone from Bell, making it a very popular source of cool components.

Now everything is an Internet of Thing, and cellular data for microcontroller projects is all the rage. [Charles] thought it would be interesting to use the famous Nokia 3100 to transmit and receive data. After battling with some weird connectors, he succeeded.

The Nokia 3100 doesn’t have a USB connector, as this phone was made before the EU saved us from a menagerie of cell phone chargers. Instead, this phone has a Nokia Pop-Port, a complex connector that still has TX and RX pins running at 115,200 bit/s 8N1. By fitting a USB socket onto a prototyping board, adding a few level shifters, and connecting the pins in the right order, [Charles] was able to get his Arduino talking to an old Nokia Brick.

[Charles] isn’t quite at the level of sending SMS from his confabulation, and even following a tutorial from [Ilias Giechaskiel] didn’t work. [Charles] is looking for help here, and if you have any suggestions, your input would be appreciated.

There is a problem with using a Nokia 3100 as a cheap Arduino cellular shield: it’s only 2G, and sometime soon those cell towers will be shut down. For now, though, it works, and once those 2G towers are shut down, there are plenty of options with cheap, early Android and iOS phones.

While [Ilias Giechaskiel] was waiting for his SIM900 shield to arrive, he decided to see what he could do with an old Nokia 6310i and an Arduino. He was researching how to send automated SMS text messages for a home security project, and found it was possible to send AT commands via the headphone jack of Motorola phones. But unfortunately Nokia did not support this, as they use a protocol know as FBus. With little information to go on, [Ilias] was able to break down the complicated protocol and take control with his Arduino.

With the connections were in place, [Ilias] communicated with the Nokia phone using a program called Gnokii — a utility written specifically for controlling the phone with a computer. Using the Arduino as an intermediary, he was eventually able tap into the FBus and send SMS messages.

Be sure to check out his blog as [Ilias] goes into great detail on how Nokia’s FBus protocol works, and provides all source code needed to replicate his hack. There is also a video demonstration at the end showing the hack in action.

It makes an Arduino look like a 555.  A 364 Mhz, 32 bit processor. 8 MB RAM. GSM. Bluetooth. LCD controller. PWM. USB and dozens more. Smaller than a Zippo and thinner than corrugated cardboard. And here is the kicker: $3. So why isn’t everyone using it? They can’t.

Adoption would mandate tier after tier of hacks just to figure out what exact hardware is there. Try to buy one and find that suppliers close their doors to foreigners. Try to use one, and only hints of incomplete documentation will be found. Is the problem patents? No, not really.

[Bunnie] has dubbed the phenomenon “Gongkai”, a type of institutionalized, collaborative, infringementesque knowledge-exchange that occupies an IP equivalent of bartering. Not quite open source, not quite proprietary. Legally, this sharing is only grey-market on paper, but widespread and quasi-accepted in practice – even among the rights holders. [Bunnie] figures it is just the way business is done in the East and it is a way that is encouraging innovation by knocking down barriers to entry. Chinese startups can churn out gimmicky trash almost on whim, using hardware most of us could only dream about for a serious project.

He contrasts this with the West where only the big players like Apple and Google can step up to the plate. Everyone else is forced to use the embarrassingly obsolete hardware we are all familiar with. But [Bunnie] wants to get his foot in the door. “Can we find a way to still get ahead, yet still play nice?” he asks.

Part of his solution is reverse engineering so that hardware can simply be used – something the EFF has helped legally ensure under fair use. The other half is to make it Open Source. His philosophy is rooted in making a stand on things that matter. It is far from a solid legal foundation, but [Bunnie] and his lawyers are gambling that if it heads to a court, the courts will favor his side.

The particular board targeted is the one described above – the MT6260. Even spurred by the shreds of documentation he could gather, his company is a 2-man team and cannot hope to reverse engineer the whole board. Their goal is to approach the low-hanging fruit so that after a year, the MT6260 at least enters the conversation with ATMega. Give up trying to use it as a phone; just try to use like the Spark Core for now.

He is already much of the way there. After telling you what is on board and why we would all want to use it, [Bunnie] shows how far he has gone to reverse engineering and describes his plans for the rest. From establishing an electronic “beachhead” base of operations to further probe the device, to X-rays, photos, diagrams and the beginnings of an OS. If this type of thing interests you at all, the meticulous approach and easy-reading of this tech teardown will surely impress and inspire you. Every step of progress requires a new hack, a new solution, a new ingenious way to pry information out.

We’ve featured some awe-inspiring reverse engineering attempts in the past, but this is something that is still new and relevant. Rather than only exploit his discoveries for himself, [Bunnie] has documented and published everything he has learned. Everyone wins.

Thanks [David] for the tip.

What do you do if you suck at a smartphone game? Buy some in-game upgrades to pretend like you’re good? Screw that! [Valentin] did what any self-respecting hacker would: developed an automated system to play for him.

Granted, when you see the demo video embedded below you’ll realize there isn’t much strategy involved in this game. But that setup to simulate the touchscreen presses is pretty neat. We’re used to seeing mechanical touchscreen hacks but this one is electronic, using a couple of pads of copper foil tape and some relays to make it happen. Here’s the one caveat: you still need to be touching something with your hand. This just uses the relays to switch the connection between the pads and your body.

We’ve looked around for this before. Does anyone have a cheap, simple, and effective hack to fully automate presses on a modern touchscreen? Can we use a potato or something? Tell us below, but send it in to the tips line too!