[Mike] is the only one in his house who drinks coffee, and uses a simple single-serving brewer with no auto-on feature. And since no one really wants to have to stand around making coffee in the morning, [Mike]’s solution was to IoT-ize his electrical socket.
The project consists of a relay board controlled by an ESP8266-packing Adafruit Huzzah. It’s all powered by a 9V power supply with a regulator supplying the relay coil and Huzzah with 5V. [Mike]’s using CloudMQTT to communicate with the outlet.
We often see these automation projects hit a wall when it comes to adding a user-side dashboard. [Mike] is using a free Android app called MQTT Dash which allows for a number of different UI components and even had coffee maker icons already built in. It’s certainly worth a look for your own projects. [Mike] uses it to turn on the outlet for 10 minutes, and by the time he grabs half-and-half the outlet is already off again.
They say the eyes are the windows to the soul. But with a new smartphone app, the eyes may be a diagnostic window into the body that might be used to prevent a horrible disease — pancreatic cancer. A research team at the University of Washington led by [Alex Mariakakis] recently described what they call “BiliScreen,” a smartphone app to detect pancreatic disease by imaging a patient’s eyes.
Pancreatic cancer is particularly deadly because it remains asymptomatic until it’s too late. One early symptom is jaundice, a yellow-green discoloration of the skin and the whites of the eyes as the blood pigment bilirubin accumulates in the body. By the time enough bilirubin accumulates to be visible to the naked eye, things have generally progressed to the inoperable stage. BiliScreen captures images of the eyes and uses image analysis techniques to detect jaundice long before anyone would notice. To control lighting conditions, a 3D-printed mask similar to Google’s Cardboard can be used; there’s also a pair of glasses that look like something from [Sir Elton John]’s collection that can be used to correct for ambient lighting. Results look promising so far, with BiliScreen correctly identifying elevated bilirubin levels 90% of the time, as compared to later blood tests. Their research paper has all the details (PDF link).
Tools like BiliScreen could really make a difference in the early diagnosis and prevention of diseases. For an even less intrusive way to intervene in disease processes early, we might also be able to use WiFi to passively detect Parkinson’s.
If you have a few servo motors, an Arduino, and a Bluetooth module, you could make Biped Bob as a weekend project. [B. Aswinth Raj] used a 3D printer, but he also points out that you could have the parts printed by a service or just cut them out of cardboard. They aren’t that complex.
Each of Bob’s legs has two servo motors: one for the hip and one for the ankle. Of course, the real work is in the software, and the post breaks it down piece-by-piece. In addition to the Arduino code, there’s an Android app written using Processing. You can build it yourself, or download the APK. The robot connects to the phone via BlueTooth and provides a simple user interface to do a few different walking gaits and dances. You can see a few videos of Biped Bob in action, below.
This wouldn’t be a bad starter project for a young person or anyone getting started with robotics, especially if you have a 3D printer. However, it is fairly limited since there are no sensors. Then again, that could be version two, if you were feeling adventurous.
We have mixed feelings about the BlueTooth control. BlueTooth modules are cheap and readily available, but so are ESP8266s. It probably would not be very difficult to put Bob on WiFi and let him serve his own control page to any web browser.
Upgrading RAM in the average computer is a relatively trivial task. Pop the case open, and you slide the new sticks into the extra slots. It’s not the same case for smartphones and tablets — in the endless quest for the slimmest form factor, all parts are permanently soldered. In addition, every device is essentially bespoke hardware; there’s no single overarching hardware standard for RAM in portable devices. You could find yourself searching high and low for the right chips, and if you do track them down, the minimum order quantity may very well be in the thousands.
Unless, of course, you had access to the Shenzhen markets where it’s possible to buy sample quantities of almost anything. Given access to the right parts, and the ability to solder BGA packages, it’s a simple enough job to swap a bigger RAM chip on top of the CPU during the repair.
If Star Trek taught us anything, it’s clearly that we’re not quite in the future yet. Case in point: androids are not supposed to be little flecks of printed circuits with wires and jacks sprouting off them. Androids are supposed to be gorgeous fembots in polyester kimonos with beehive hairdos, designed to do our bidding and controlled by flashing, beeping, serial number necklaces.
Not willing to wait till the 23rd century for this glorious day, [Peter Walsh] designed and built his own android amulet prop from the original series episode “I, Mudd.” There’s a clip below if you need a refresher on this particularly notable 1967 episode, but the gist is that the Enterprise crew is kidnapped by advanced yet simple-minded androids that can be defeated by liberal doses of illogic and overacting.
The androids’ amulets indicate when they BSOD by flashing and beeping. [Peter]’s amulet is a faithful reproduction done up in laser-cut acrylic with LEDs and a driver from a headphone. The leads for the amulet go to a small control box with a battery pack and the disappointing kind of Android, and a palmed microswitch allows you to indicate your current state of confusion.
There was a time a few years ago when the first Android phones made it to market, that they seemed full of promise as general purpose computers. Android is sort of Linux, right, or so the story went, so of course you must be able to run Linux on an Android phone and do all sorts of cool stuff with it.
As anyone who tried to root an Android phone from 2010 will tell you, it was a painful and unrewarding process. There was normally a convoluted rooting process followed by somehow squeezing your own Linux filesystem tree onto the device, then chroot-ing into it. You’d then have to set up a VNC server and VNC into it, and eventually you’d feel immensely proud of your very slow tiny-screen Linux desktop that you’d slaved over creating. It was one of those things that’s simple in theory, but extremely convoluted in practice.
But six years have passed since those days, phones have gotten much faster and so has the software for tasks such as rooting, so maybe it’s time to return to the topic of Linux on an Android device. [Pete Scargill] gave it a try when a friend gave him a Chinese quad-core Android phone with a broken screen. He proceeded to put a Debian installation on it, upon which he runs his collection of server processes.
Rooting the phone was straightforward process using the KingRoot app, a sideloaded version as it seems there’s a bogus copy on the Play Store. Then bringing a Linux system to it could be achieved with the LinuxDeploy app. The result is surprisingly useful, after some installation steps upon which he goes into detail.
You might ask what would be the point of this exercise, given that you can do the same thing much more easily with a single board computer such as a Raspberry Pi. But to buy a Pi, SD card, screen, and UPS, as he points out you’d have to spend a lot more than you would for a second-hand phone from eBay — or a free, slightly broken, one from friends or family.
Oh Nexus 5X, how could you? I found my beloved device was holding my files hostage having succumbed to the dreaded bootloop. But hey, we’re hackers, right? I’ve got this.
It was a long, quiet Friday afternoon when I noticed my Nexus 5X was asking to install yet another update. Usually I leave these things for a few days before eventually giving in, but at some point I must have accidentally clicked to accept the update. Later that day I found my phone mid-way through the update and figured I’d just wait it out. No dice — an hour later, my phone was off. Powering up led to it repeatedly falling back to the “Google” screen; the dreaded bootloop.
Stages of Grief
I kept my phone on me for the rest of the night’s jubilant activities, playing with it from time to time, but alas, nothing would make it budge. The problem was, my Nexus still had a full day’s video shoot locked away on its internal flash that I needed rather badly. I had to fix the phone, at least long enough to recover my files. This is the story of my attempt to debrick my Nexus 5X.