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.
Modern smartphones, even the budget models, are extremely impressive pieces of technology. Powerful ARM processors, plenty of RAM, and an incredible number of sensors and radios are packed into a device that in some cases are literally given away for free when you sign up for a service plan. Unfortunately manufacturers are not obligated to keep up with software updates, and while the hardware may be willing to keep on fighting, the user is often pushed to upgrade due to perennially outdated software. Even if you aren’t the kind of person to be put off by using a phone that doesn’t have the latest and greatest OS, the lack of software security updates pose a clear threat in a world where mobile devices are increasingly targeted by attackers.
One of the key goals of postmarketOS is to avoid the fragmented nature of previous attempts at replacing Android with a community-developed operated system. By avoiding binary blobs and focusing on getting the mainline Linux kernel running on as much as the hardware as possible, there’s no need to make different forks and releases for each supported device. By unifying the OS as much as far as it can be, an upstream update can be pushed to all devices running postmarketOS regardless of their make and model, just like with traditional Linux distributions.
The blog post shows two things very clearly: that the community is extremely excited and dedicated to the prospect of running what is essentially desktop Linux on old smartphones and tablets, and that postmarketOS still has a long way to go. In these early days, many devices aren’t what could be considered “daily drivers” by most standards. In fact, the blog post mentions that they’ve decided to abandon the term “supported” when talking about devices, and make no claims beyond the fact that they will boot.
Still, incredible progress is being made on everything from mainline kernel development to getting standard Linux desktops such as Gnome, MATE and XFCE4 running. Work has also been done on the backend process of compiling and packaging up components of the operating system itself, promising to speed up development times even for those who don’t have a beefy machine they can dedicate to compiling. The blog post ends with a helpful list of things the reader can do to help support postmarketOS, ranging from making your own t-shirts to porting to new hardware.
Famed whistleblower [Edward Snowden] has recently taken to YouTube to announce Haven: an Open Source application designed to allow security-conscious users turn old unused Android smartphones and tablets into high-tech monitoring devices for free. While arguably Haven doesn’t do anything that wasn’t already possible with software on the market, the fact that it’s Open Source and designed from the ground up for security does make it a bit more compelling than what’s been available thus far.
Developed by the Freedom of the Press Foundation, Haven is advertised as something of a role-reversal for the surveillance state. Instead of a smartphone’s microphone and camera spying on its owner, Haven allows the user to use those sensors to perform their own monitoring. It’s not limited to the camera and microphone either, Haven can also pull data from the smartphone’s ambient light sensor and accelerometer to help determine when somebody has moved the device or entered the room. There’s even support for monitoring the device’s power status: so if somebody tries to unplug the device or cut power to the room, the switch over to the battery will trigger the monitoring to go active.
Thanks to the Open Source nature of Haven, it’s hoped that continued development (community and otherwise) will see an expansion of the application’s capabilities. To give an example of a potential enhancement, [Snowden] mentions the possibility of using the smartphone’s barometer to detect the opening of doors and windows.
With most commercially available motion activated monitor systems, such as Nest Cam, the device requires a constant Internet connection and a subscription. Haven, on the other hand, is designed to do everything on the local device without the need for a connection to the Internet, so an intruder can’t just knock out your Wi-Fi to kill all of your monitoring. Once Haven sees or hears something it wants you to know about it can send an alert over standard SMS, or if you’re really security minded, the end-to-end encrypted Signal.
Over the years we’ve noticed that there is a subset of hackers out there who like to turn real life vehicles into remote controlled cars. These vehicles are generally destroyed in short order, either by taking ridiculous jumps, or just smashing them into stuff until there’s nothing left. In truth that’s probably what most of us would do if we had access to a full size RC car, so no complaints there.
As a rule, the donor vehicles for these conversions are usually older and cheap. That only makes sense, why spend a lot of money on a vehicle you intend on destroying? But even still, the RC conversion [William Foster] has recently completed may take the cake. We don’t know how much of the “antiquing” of his donor vehicle was intentionally done, but on the whole, the thing looks like it got dragged from the bottom of a lake somewhere. Presumably, he got a great deal on it.
The video posted to YouTube is primarily about [William] driving his creation around (sometimes from the back seat, no less), but towards the second half of the video there’s a quick rundown on the hardware used to make this pile of rust move.
A standard RC transmitter and receiver combination are used to control a pair of Arduinos mounted in the center console, which are in turn hooked up to external stepper drivers. The wheel is turned via a chain and sprocket arrangement, and the pedals are pushed with homebrew contraptions that look like they are made from lead screws intended for 3D printers.
All in all, it appears [William] has cooked up a fairly responsive control system with commodity hardware you could get on Amazon or eBay. Not sure we’d be backseat driving this thing personally, but to each their own.