I recently spent a largely sleepless night at a hotel, and out of equal parts curiosity and boredom, decided to kill some time scanning the guest network to see what my fellow travelers might be up to. As you’d probably expect, I saw a veritable sea of Samsung and Apple devices. But buried among the seemingly endless number of smartphones charging next to their sleeping owners, I found something rather interesting. I was as picking up a number of Amazon-made devices, all of which had port 5555 open.
As a habitual Android tinkerer, this struck me as very odd. Port 5555 is used for Android Debug Bridge (ADB), a development tool used to control and perform various administrative tasks on an Android device over the network or (more commonly) locally over USB. The number of users who would have legitimately needed to enable network ADB on their devices is surely rather low, so to see a half dozen of them on the network at the same time seemed improbable to say the least.
Why would so many devices manufactured by Amazon all have network ADB enabled? I realized there must be a connection, and it didn’t take long to figure it out.
When project inspiration strikes, we’d love to do some quick tests immediately to investigate feasibility. Sadly we’re usually far from our workbench and its collection of sensor modules. This is especially frustrating when the desired sensor is in the smartphone we’re holding, standing near whatever triggered the inspiration. We could download a compass app, or a bubble level app, or something similar to glimpse sensor activity. But if we’re going to download an app, consider Google’s Science Journal app.
It was designed to be an educational resource, turning a smartphone’s sensor array into a pocket laboratory instrument and notebook for students. Fortunately it will work just as well for makers experimenting with project ideas. The exact list of sensors will depend on the specific iOS/Android device, but we can select a sensor and see its output graphed in real-time. This graph can also be recorded into the journal for later analysis.
Science Journal was recently given a promotional push by the band OK Go, as part of their OK Go Sandbox project encouraging students to explore, experiment, and learn. This is right up the alley for OK Go, who has a track record of making music videos that score high on maker appeal. Fans would enjoy their videos explaining behind-the-scene details in the context of math, science, and music.
An interesting side note. Anyone who’s been to Hackaday Superconference or one of the monthly Hackaday LA meetups will likely recognized the venue used in many of the OK Go Sandbox videos. Many of them were filmed at the Supplyframe Design Lab in Pasadena. It’s also nice to see AnnMarie Thomas (Hackaday Prize Judge from 2016 and 2017) collaborated with OK Go for the Sandbox project.
While the Science Journal app has provisions for add-on external sensors, carrying them around would reduce its handy always-available appeal. Not that we’re against pairing smartphones with clever accessories to boost their sensing capabilities: we love them! From trying to turn a smartphone into a Tricorder, to an inexpensive microscope, to exploring serious medical diagnosis, our pocket computers can do it all.
Modern cars and head units are pretty fancy gadget-wise. But what if your car still has an 8-track? No problem. Just pick up a Raspberry Pi 3 and a seven-inch touchscreen, and use Crankshaft to turn it into an Android Auto setup.
The open source project is based on OpenAuto which, in turn, leverages aasdk. The advantage to Crankshaft is it is a plug-and-play distribution. However, if you prefer, you can build it all yourself from GitHub.
When repairing something, there are in effect two schools of thought: you can craft a repair that seamlessly blends into the original hardware and doesn’t look like a repair, or you can slap that thing together and keep it moving. A lot of variables go into this decision making process, such as the complexity of the repair, the available materials, and of course whether or not you need to keep the fact you broke the thing from your significant other.
Printing such a tiny part, especially with the little details like the channel for you to hook your fingernail into, requires a fairly well calibrated printer. If you can’t muster up a 0.1mm first layer you might as well sit this one out; and if you haven’t mastered the art of bridging, that little valley to help you get the SIM back out may end up overflowing into a river of tears.
For [Alex], the piece ended up working perfectly. It might look a little weird, but if you’ve got the tablet in a case you’ll never see it anyway. It’s also worth noting that this design may work on other devices with a similar SIM arrangement, or at the very least, might be a good starting point to work from if you’ve got to come up with your own.
Remember, there’s still plenty of time to enter your own printed fix into our “Repairs You Can Print” contest. The top 20 repairs will take home $100 in Tindie credit, and for the best repair done by a Student or Organization, there’s two Prusa i3 MK3 printers with the Quad Material upgrade kits on the line.
Taking a dive into VR or augmented reality — once, dreamed-of science fiction — is not only possible for the average consumer, but crafting those experiences is as well! Hackaday.io user [kvtoet]’s HandHolo is a homebrew method to cut your teeth on peeking into a virtual world.
This project requires a smartphone running Android Oreo as its backbone, a Bluetooth mouse, a piece of cardboard and a small mirror or highly reflective surface. The phone is slotted into the cardboard housing — prototype with what you have! — above the mouse, and the mirror angled opposite the screen reflects the image back to the user as they explore the virtual scene.
Within Unity, [kvtoet]’s used a few scripts that access phone functions — namely the gyroscope, which is synchronised to the mouse’s movements. That movement is translated into exploration of the virtual space built in Unity and projected onto the portal-like mirror. Check it out!
There are many viable options for home security systems, but where is the fun in watching a static camera feed from inside your place? The freedom to really look around might have been what compelled [Varun Kumar] to build a security car robot to drive around his place and make sure all is in order.
Aimed at cost-effectiveness and WiFi or internet accessibility, an Android smartphone provides the foundation of this build — skipping the need for a separate Bluetooth or WiFi module — and backed up by an Arduino Uno, an L298 motor controller, and two geared DC motors powering the wheels.
Further taking advantage of the phone’s functionality, the robot is controlled by DTMF tones. Using the app DTMF Tone Generator and outputting through the 3.5mm jack, commands are interpreted by a MT8870DE DTMF decoder module.While this control method carries some risks — as with many IoT-like devices — [Kumar] has circumvented one of DTMF’s vulnerabilities by adding a PIN before the security car will accept any commands.
He obtains a live video feed from the phone using AirDroid in concert with VNC server, and assisted by a servo motor for the phone is enabled to sweep left and right for a better look. A VNC client on [Kumar]’s laptop is able to access the video feed and issue commands. Check it out in action after the break!
If you’re an Android fan, there’s a good chance you’ve heard of the Nexus 5X. The last entry in Google’s line of low-cost Nexus development phones should have closed the program on a high note, or at the very least maintained the same standards of quality and reliability as its predecessor. But unfortunately, a well known design flaw in the Nexus 5X means that the hardware is essentially a time-bomb. There are far too many reports of these phones entering into an endless bootloop right around the one year mark to say it’s just a coincidence.
The general consensus seems to be that faulty BGA chip soldering on the CPU works lose after about a year or so of thermal stress. Whatever the reason, [hillbillysam] recently found himself the proud owner of a dead Nexus 5X. Resigned to the fact that he would need to get a new phone, he at least wanted to get some of his data off the device before it went to that big landfill in the sky.
As it turns out these bootlooped phones can temporarily be revived by cooling them down, say by putting them in the freezer for a few hours. There’s plenty of debate as to why this works, but even our own [Lewin Day] can testify that it does seem to get the phone booting again; though only until it comes back up to operating temperature. With this in mind, [hillbillysam] reasoned that if he kept the phone as cold as possible while it was running, it may stay operational long enough for him to pull his files off of it over USB.
He couldn’t exactly freeze the phone in a block of ice, but remembering his high school chemistry, he came up with something pretty close. By adding salt to water, you can significantly lower temperature at which it freezes. Putting the phone into a watertight bag and submerging it in this supercooled solution is an easy and non-destructive way of keeping it very cold while still being accessible over USB.
His Nexus 5X was able to keep kicking the whole time it was luxuriating in its below-freezing saltwater bath, giving him plenty of time to copy everything he needed. It doesn’t sound like the kind of spa day we’d like to have personally, but to each their own.