An Up-To-Date Development Environment For The Nokia N-Gage

One of the brave but unsuccessful plays from Nokia during their glory years was the N-Gage, an attempt to merge a Symbian smartphone and a handheld game console. It may not have managed to dethrone the Game Boy Advance but it still has a band of enthusiasts, and among them is [Michael Fitzmayer] who has produced a CMake-based toolchain for the original Symbian SDK. This is intended to ease development on the devices by making them more accessible to the tools of the 2020s, and may serve to bring a new generation of applications to those old Nokias still lying forgotten in dusty drawers.

In much of the public imagination, the invention of the smartphone came with the release of the first Apple iPhone in 2007. Hackaday readers will of course trace the smartphone back much further than that to an original IBM prototype, and will remind any doubters that the Nokias which the iPhone vanquished were very successful smartphones without any of Cupertino’s magic in sight. Nokia’s tragedy was that they appeared not to understand what they had in Symbian, and released a bewildering array of devices intended to satisfy every possible market without recognizing that the market they needed to serve was their customers being easily able to run the apps of their choice on the things.

Symbian itself has long ago become a piece of abandonware, but during its chequered history there was a period in which an open-source version was released. It would be nice to think that projects such as this one might revive interest in this capable yet forgotten operating system, as with the passage of a decade the cost of hardware which might run it has fallen to the point of affordability. Does anyone want to relive the 2000s?

Header image: Evan-Amos, Public domain.

A Dodgy Dial Gets A Teardown And Some Oil

The pulse-dial telephone and its associated mechanical exchange represents the pinnacle of late-19th and early-20th century electromechanical technology, but its vestiges have disappeared from view with astonishing rapidity. [Matthew Harrold] is a telecoms enthusiast who’s been kind enough to share with us the teardown and refurbishment of that most signature of pulse-dial components, a telephone dial. In this case it’s on a rather unusual instrument, a British GPO outdoor phone that would have been seen in all kinds of industrial and safety installations back in the day and can probably still be found in the wild today if you know where to look.

The teardown soon identifies a dial that runs very slowly and is sorely in need of a clean. There follows a detailed part-by-part dismantling of the dial mechanism, followed by a careful clean, polish, and reassembly. He notes that a previous owner had used grease to lubricate it, probably the reason for its slow operation.

The result is a smoothly running dial and a refurbished phone that would probably last another half-century or more before needing more maintenance. It’s enough to make others who’ve experimented with pulse dial phones very envious.

Threaded Wires Save Phone Numbers

If you thought programming your 1990s VCR was rough, wait until you see this Russian telephone autodialer that [Mike] took apart over on the mikeselectricalstuff YouTube channel (video below the break). [Mike] got this 1980s Soviet-era machine a few years ago, and finally got around to breaking into it to learning what makes it tick. The autodialer plugs into the phone line, much like an old-school answering machine. It provides the user with 40 pre-set telephone numbers, arranged in two banks of 20, and a speaker to monitor the connection process. It uses pulse dialing — no touch tones. What’s surprising is how you program the numbers. Given that this was build in the 1980s Soviet Union, he wasn’t expecting a microcontroller. But he wasn’t expecting transformer core “rope” memory, either.

The phone normally sits on a platform on the left side of the machine. Raising up the platform exposes a bank of toroidal cores, arranged in seven rows of four. Each row corresponds to a dialed digit, and the four cores used to encode a single digit. At the top and bottom of the programming board are two 40-pin connectors, each pin corresponding to one of the preset phone numbers. A bunch of patch wires would have been provided, and you program each number by threading a long wire through the appropriate cores, connecting it at the top and bottom connectors much like a modern solderless breadboard. It’s also interesting to see the components and construction technique of this circuit board. For example, the diodes have the strip on the Anode end, not the cathode as we’re normally used to today. The transistor cans are mounted upside down like dead spiders.

Continue reading “Threaded Wires Save Phone Numbers”

PinePhone Malware Surprises Users, Raises Questions

On December 5th, someone by the IRC nickname of [ubuntu] joined the Pine64 Discord’s #pinephone channel through an IRC bridge. In the spirit of December gift-giving traditions, they have presented their fellow PinePhone users with an offering – a “Snake” game. What [ubuntu] supposedly designed had the potential to become a stock, out-of-the-box-installed application with a small but dedicated community of fans, modders and speedrunners.

Unfortunately, that would not be the alternate universe we live in, and all was not well with the package being shared along with a cheerful “hei gaiz I make snake gaem here is link www2-pinephnoe-games-com-tz replace dash with dot kthxbai”  announcement. Shockingly, it was a trojan! Beneath layers of Base64 and Bashfuscator we’d encounter shell code that could be in the “example usage” section of a modern-day thesaurus entry for the word “yeet“.

Continue reading “PinePhone Malware Surprises Users, Raises Questions”

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”