It’s a tragedy every time a modern smartphone is tossed into e-waste. We prefer to find another life for these bundles of useful hardware. But given all the on-board barriers erected by manufacturers, it’s impractical to repurpose smartphones without their support. A bit of good news on this front is Samsung testing the waters with a public beta of their “Galaxy Upcycling at Home” program, turning a few select devices into SmartThings sensor nodes.
More devices and functionality are promised, but this initial release is barely a shadow of what Samsung promised in 2017. Missed the announcement back then? Head over to a “How it started/How it’s going” comparison from iFixit, who minced no words starting with their title Galaxy Upcycling: How Samsung Ruined Their Best Idea in Years. They saw a bunch of Samsung engineers at Bay Area Maker Faire 2017, showing off a bunch of fun projects reusing old phones as open hardware. The placeholder GitHub repository left from that announcement still has a vision of a community of makers dreaming up novel uses. This is our jam! But sadly it has remained a placeholder for four years and, given what we see today, it is more likely to be taken down than to become reality.
The stark difference between original promise and actual results feel like an amateur Kickstarter, not something from a giant international conglomerate. Possibly for the same reason: lack of resources and expertise for execution. It’s hard to find support in a large corporate bureaucracy when there is no obvious contribution to the bottom line. Even today’s limited form has only a tenuous link of possibly helping to sell other SmartThings-enabled smart home devices.
Ars Technica was similarly unimpressed with launch functionality, but was more diplomatic describing the beta as “a very modest starting point”. XDA-Developers likewise pinned their hopes on the “more devices will be supported in the future” part of Samsung’s announcement. Until Samsung delivers on more of the original promise, we’ll continue to be hampered by all the existing reasons hacking our old cell phones are harder than they should be. Sometimes an idea can be fulfilled by helpful apps but other times will require hacking into our devices the old-fashioned way.
Our smartphones are incredibly powerful computers in their own right, yet we don’t often see them directly integrated into projects. Intel Intelligent Systems Lab has done exactly that with the release OpenBot, an open source smartphone based self-driving robot.
Most of the magic happens on the smartphone, which runs an app built on TensorFlow Lite, and integrates the camera and array of sensors on the smartphone, as well as the data from ultrasonic sensors and wheel encoders on the robot. The robot itself is relatively simple, with four geared DC motors, motor drivers wired to an Arduino Nano that interfaces with an Android Phone over serial.
The app created by the Intel ISL team comes preloaded with three AI models that can do either person following, or two different modes of autonomous navigation. By connecting a Bluetooth controller to the smartphone and drive the robot around manually in your specific environment while collecting data, you can train a custom autonomous driving policy to suit your environment.
This looks like an excellent way to get a taste of autonomous robots on a small budget, while still being a viable base for more demanding applications. We’ve seen only a few smartphone based robots like DriveMyPhone and SmartiPresense, which don’t have AI capabilities, but are intended for telepresence applications. We’ve always wondered why we don’t see more projects with cellphones, so we welcome the example.
Continue reading “Open Source Self-Driving Smartphone Robot”
Not every build needs to be immediately useful or revolutionary. Plenty of builds are just for fun, for education, or even purposefully useless but still challenging. This clock, for example, might fit into all three categories. It’s a clock that displays time through a QR code, making it completely inscrutable unless you have a device which likely has its own readable clock on it already.
The QR Code clock comes to us from [Aaron] and is based on the now-ubiquitous ESP32 WiFi chip. The ESP32 is connected to a 64×64 LED matrix which is updated every second with a code for the current time. With single-second resolution that means that even with a method for reading a QR code by hand, like you sometimes can with barcodes, there’s no way to read it without a smartphone since it changes so rapidly.
Of course [Aaron] recognizes the flaw in his design in his video in which he notes tongue-in-cheek that with this clock you would never have to look at a smartphone again, since the clock is right there on the wall. We appreciate the humor and also that [Aaron] has made all of his source code available in case you would like to use this as an example project for using QR codes for more useful purposes. For now, though, we’ll just forward you along to some other useless machines.
Thanks to [willmore] for the tip!
Continue reading “Clock Is Not Readable By Humans”
If you ever thought about becoming a treasure hunter this simple DIY metal detector by [mircemk] may be a nice project to start with.
The design is based on an opensource metal detector called Smart Hunter. This Very Low Frequency (VLF) metal detector uses transmitter and receiver coils in so-called Double-D geometry. The transmitter coil is driven by a signal generator module that operates at its resonant frequency of 4.74 kHz.
The resulting oscillating magnetic field will induce eddy currents in a nearby metal object that in turn induce a signal in the receiver coil. This signal is then fed into the microphone port of a smartphone and analyzed by a custom metal detector app. [mircemk] also included an audio amplifier and small speaker into the device.
The detector turned out to be quite sensitive and can detect a coin at up to 25 cm distance and larger metal objects even up to 1 m. Modern metal detectors can also distinguish between different types of metal by analyzing the phase shift of the detected signal which might be some way to improve the design.
Video after the break.
Continue reading “A Smart DIY Metal Detector”
You don’t have to be an extinct mammal or a Millennial to enjoy the smooth, buttery taste of an avocado. Being psychic on the other hand is definitely an advantage to catch that small, perfect window between raw and rotten of this divaesque fruit. But don’t worry, as modern problems require modern solutions, [Eden Bar-Tov] and [Elad Goldberg] built the AvoRipe, a device to notify you when your next avocado has reached that window.
Taking both the firmness and color of an avocado as indicators of its ripeness into account, the team built a dome holding a TCS3200 color sensor as stand for the avocado itself, and 3D printed a servo-controlled gripper with a force sensor attached to it. Closing the gripper’s arms step by step and reading the force sensor’s value will determine the softness the avocado has reached. Using an ESP8266 as centerpiece, the AvoRipe is turned into a full-blown IoT device, reporting the sensor readings to a smartphone app, and collecting the avocado’s data history on an Adafruit.IO dashboard.
There is unfortunately one big drawback: to calibrate the sensors, a set of nicely, ripe avocados are required, turning the device into somewhat of a chicken and egg situation. Nevertheless, it’s a nice showcase of tying together different platforms available for widescale hobbyist projects. Sure, it doesn’t hurt to know how to do each part from scratch on your own, but on the other hand, why not use the shortcuts that are at our disposal to remove some obstacles — which sometimes might include programming itself.
Continue reading “AvoRipe Takes A Firm Grip On The Ultimate First World Food Problem”
[Labpacks] wanted to build a robot car controlled by his phone. As a Hackaday reader, of course you probably can imagine building the car. Most could probably even write a phone application to do the control. But do you want to? In most cases, you are better off focusing on what you need to do and using something off the shelf for the parts that you can. In [Labpacks’] case, he used Visuino to avoid writing ordinary code and RemoteXY to handle the smartphone interface.
RemoteXY is a website that allows you to easily build a phone interface that will talk to your hardware over Bluetooth LE, USB, or Ethernet (including WiFi). One thing of interest: even though the interface builder is Web-based, the service claims that the interface structure stays on the controller. There’s no interaction with the remote servers when operating the user interface so there is no need for an external Internet connection.
Continue reading “RemoteXY Simplifies Arduino Control”
[Editor’s note: There’s an ongoing back-and-forth about this “spyware” right now. We haven’t personally looked into it on any phones, and decoded Wireshark caps of what the cleaner software sends home seem to be lacking — it could be innocuous. We’re leaving our original text as-run below, but you might want to take this with a grain of salt until further evidence comes out. Or keep us all up to date in the comments. But be wary of jumping to quick conclusions.]
Samsung may have the highest-end options for hardware if you want an Android smartphone, but that hasn’t stopped them from making some questionable decisions on the software they sometimes load on it. Often these phones come with “default” apps that can’t be removed through ordinary means, or can’t even be disabled, and the latest discovery related to pre-loaded software on Samsung phones seems to be of a pretty major security vulnerability.
This software in question is a “storage cleaner” in the “Device Care” section of the phone, which is supposed to handle file optimization and deletion. This particular application is made by a Chinese company called Qihoo 360 and can’t be removed from the phone without using ADB or having root. The company is known for exceptionally bad practices concerning virus scanning, and the software has been accused of sending all information about files on the phone to servers in China, which could then turn all of the data it has over to the Chinese government. This was all discovered through the use of packet capture and osint, which are discussed in the post.
These revelations came about recently on Reddit from [kchaxcer] who made the original claims. It seems to be fairly legitimate at this point as well, and another user named [GeorgePB] was able to provide a temporary solution/workaround in the comments on the original post. It’s an interesting problem that probably shouldn’t exist on any phone, let alone a flagship phone competing with various iPhones, but it does highlight some security concerns we should all have with our daily use devices when we can’t control the software on the hardware that we supposedly own. There are some alternatives though if you are interested in open-source phones.
Thanks to [kickaxe] for the tip!
Photo from Pang Kakit [CC BY-SA 3.0 DE (https://creativecommons.org/licenses/by-sa/3.0/de/deed.en)]