Running Octoprint On A PinePhone Turns Out To Be Pretty Easy

3D printer owners have for years benefitted from using Octoprint to help manage their machines, and most people run Octoprint on a Raspberry Pi. [Martijn] made it run on his PinePhone instead, which turned out to be a surprisingly good fit for his needs.

While [Martijn] was working out exactly what he wanted and taking an inventory of what Raspberry Pi components and accessories it would require, it occurred to him that his PinePhone — an open-source, linux-based mobile phone — would be a good candidate for his needs. It not only runs Linux with a touchscreen and camera, but even provides USB, ethernet, and separate DC power input via a small docking bar. It looked like the PinePhone had it all, and he was right. [Martijn]’s project page gives a walkthrough of the exact steps to get Octoprint up and running, and it even turns out to not be particularly difficult.

[Martijn] is no stranger to hacking his PinePhone to do various things; we’ve already seen him add thermal imaging to his PinePhone. For those of you who are intrigued by the idea but don’t own a PinePhone? Check out the octo4a project, which allows running Octoprint on Android phone hardware.

PinePhone Speed Up Takes Soldering

It is no secret that we like a good hack and [Federico Amedeo Izzo] explains a hack for the PinePhone that can double the speed used for the device’s memory chips. Like many good hacks, it all started with a question. [Federico] was reading a review of the PinePhone Pro (the source of the image for this post) and apparently, the eMMC memory in that phone clocks in at about 150 MB/s. The original phone gets about 50-80 MB/s.

Reading some datasheets, it looked like the same chips are in both phones and should support not only DDR52 mode — the mode the original phone uses — but also HS200 and HS400 modes which top out at 200 and 400 MB/s, respectively. But there was one problem.

Continue reading “PinePhone Speed Up Takes Soldering”

Privacy Report: What Android Does In The Background

We’ve come a long way from the Internet of the 90s and early 00s. Not just in terms of technology, capabilities, and culture, but in the attitude most of us take when accessing the ‘net. In those early days most users had a militant drive to keep any personal or identifying information to themselves beyond the occasional (and often completely fictional) a/s/l, and before eBay and Amazon normalized online shopping it was unheard of to even type in a credit card number. On today’s internet we do all of these things with reckless abandon, and to make matters worse most of us carry around a device which not only holds all of our personal information but also reports everything about us, from our browsing habits to our locations, back to databases to be stored indefinitely.

It was always known that both popular mobile operating systems for these devices, iOS and Android, “phone home” or report data about us back to various servers. But just how much the operating systems themselves did was largely a matter of speculation, especially for Apple devices which are doing things that only Apple can really know for sure. While Apple keeps their mysteries to themselves and thus can’t be fully trusted, Android is much more open which paradoxically makes it easier for companies (and malicious users) to spy on users but also makes it easier for those users to secure their privacy on their own. Thanks to this recent privacy report on several different flavors of Android (PDF warning) we know a little bit more on specifically what the system apps are doing, what information they’re gathering and where they’re sending it, and exactly which versions of Android are best for those of us who take privacy seriously.

Continue reading “Privacy Report: What Android Does In The Background”

A Tidy Clamshell Keyboard For The Pinephone

Something a lot of people don’t realise about modern smartphones is that many of them have fully-featured USB interfaces. Perhaps the best of all is the Pinephone, which is a fully open-source smartphone that gives end users total control over their phone experience. [silver] has such a phone, and set about building himself a neat keyboard setup for the platform.

The build is based around an RCA RKT773P tablet keyboard case, which uses USB to interface with a tablet via pogo pins. [silver] modified this by soldering on a USB cable to the pins, paired with a USB-C host adapter on the Pinephone. Paired with a few 3D printed parts to hold everything in place, it almost turns the assembly into a cute little Pinephone laptop.

It’s a neat build that would likely save a lot of frustration when hacking away at a terminal window on the Pinephone. Parts are available on Thingiverse for those interested in replicating the hack. Those eager to dive into the Pinephone platform may relish the new Pro model that has just dropped, too. Video after the break.

Continue reading “A Tidy Clamshell Keyboard For The Pinephone”

A homebrew telephone connects home and workshop.

The Calls Are Coming From Inside The House (or Workshop)

Hot on the heels of their carbon microphone build a few years ago, [Simplifier] strung up a two-phone network between the house and the workshop. Both telephones are completely DIY except for the pair of switches on the front. Each side has a bell, a microphone, and an audio transformer. Listening is done through a pair of headphones, and both users speak through a homebrew carbon microphone.

We particularly love the bell, which is made from fence post caps. Sitting between the bells and ready to strike is a ball bearing mounted on a really thick piece of wire that’s driven by an electromagnet. To make a call, you use both switches — the one on the left pulls either the bell or the microphone to ground, while the switch on the left right is used momentarily to send 6 V from the lantern battery down the 50 ft. line to the other phone to ring it. You’ll see what we mean in the demo video after the break. Check out the sound of those fence post caps!

[Simplifier] wound an audio transformer that provides the necessary impedance matching to use regular headphones as receivers. Since the homebrew microphones only need 1.5 V, [Simplifier] split the voltage across two carbon contacts placed in series. That’s still more than necessary, but [Simplifier] was able to make it work.

More recently, [Simplifier] has built a beautiful and even better carbon microphone and even hosted a back-to-basics Hack Chat.

Continue reading “The Calls Are Coming From Inside The House (or Workshop)”

Showdown Time For Non-Standard Chargers In Europe

It seems that few features of a consumer electronic product will generate as much rancour as a mobile phone charger socket. For those of us with Android phones, the world has slowly been moving over the last few years from micro-USB to USB-C, while iPhone users regard their Lightning connector as the ultimate in connectivity. Get a set of different phone owners together and this can become a full-on feud, as micro-USB owners complain that nobody has a handy charging cable any more, USB-C owners become smug bores, and Apple owners do what they’ve always done and pretend that Steve Jobs invented USB. Throwing a flaming torch into this incendiary mix is the European Union, which is proposing to mandate the use of USB-C on all phones sold in its 27 member nations with the aim of reducing considerably the quantity of e-waste generated.

Minor annoyances over having to carry an extra micro-USB cable for an oddball device aside, we can’t find any reason not to applaud this move, because USB-C is a connector born of several decades of USB evolution and brings with it not only the reversible plug but also the enhanced power delivery standards that enable fast charging no matter whose USB-PD charger you are using. Mandating USB-C will put an end to needlessly overpriced proprietary cables, and bring eventual unity to a fractured world. Continue reading “Showdown Time For Non-Standard Chargers In Europe”

Dial A For Arduino

A lot of phrases surrounding phones don’t make sense anymore. With a modern cellphone, you don’t really “hang up” and there’s certainly no “dial” to be had. However, with [jakeofalltrades’] project, you can read an old-fashioned phone dial using an Arduino.

The idea behind a phone dial is actually pretty simple. When you pull the dial back to the stop using one of the numbered holes and release it, it causes a switch to open and close the same number of times as the hole you selected. That is, if you pull back the 5 hole, you should get 5 switch closures. The duration of each switch event and the time between switch events is a function of the speed the dial moves because of its internal spring. The zero hole actually produces ten pulses.

There are standards for how precise the timing has to be, but — honestly — it’s pretty loose since these were not made to be read by precise microcontroller timers. In the United States, for example, the dial was supposed to produce between 9.5 and 10.5 pulses per second, but the equipment on the other end would tolerate anything from 8 to 11.

Even if you don’t want a rotary dial in your next project, the code has some good examples of using ATmega328 timers that you might find useful in another context. However, a dial would add a nice retro touch to any numeric input you might happen to need.

If you need project inspiration, how about a volume control? Or, why not a numeric keypad?