Mobile Archive

I’ve been going through my collection of PDAs over the last few weeks for, among other OSAlert things, my Pixelfed account, and while playing around with various old applications, I came across the Google Maps application for Palm OS. As it turns out – this official Google application, last updated in 2008, still fully and completely works today, in 2023! I shot a quick video using the application, and uploaded it to the new (and not fully set-up yet, so forgive the lack of avatars, descriptions, banner images, and so on – it’s late in my time zone) OSAlert PeerTube account, embedded below for your convenience. Navigation still works. You can pan around in both map and satellite view. And, as the video shows, you can zoom in quite far and get some incredible detail on that old Palm TX display (you can zoom in further). That’s some impressive API backwards compatibility.

Perhaps unsurprisingly, the techniques described in Let’s Go Whaling bear comparison to some of those that bookmakers and casinos have long deployed, capitalising on deep understanding of psychology. The big difference, of course, is that the gamer can never win money, only prestige or progress in a virtual game. The very uncomfortable truth for Apple and Google: much – 70-75% – of App Store and Play Store revenue comes from exploitative casino games, mostly expertly designed to target the most vulnerable among us, like gambling addicts, children, people with mental issues like depression, and so on. It’s seedy, disgusting, predatory, and should be deeply, deeply illegal. Left or right, can’t we all agree we should ban these practices?

Welcome to Magic Cap, the oddest yet somehow most endearing interface a PDA — and, briefly, Windows 95 — ever had. Unlike the Palm OS where I bought my first device brand new, I was a late convert to Magic Cap, picking up this wacky device called a DataRover in 2004 just to play with. It wasn’t exactly pocket-sized, but it was still quite portable, and the whimsical audio feedback and immediately accessible interface drew me in. I found some games and an Ethernet driver and the browser and enjoyed using it as a handheld in my old apartment. Despite my love for PDAs and my pretty large collection of devices covering most PDA platforms, I’ve never actually owned or used a Magic Cap device. I wonder if it’s time to address that shortcoming.

Creating the PiRS232 and playing with the Pi over serial has been leading towards an idea – I wanted to create a small, battery powered device, a sidecar that I could carry with my Psion and use as portable Linux terminal. I also managed to turn it into an Internet gateway, leading to some interesting experiences. The idea was straightforward: take a Pi Zero, add an RS232 board that already handles the null modem side, add a Lipo battery, power management and charging, and print a case for it. It’s taken a few months from initial idea to final design, but I’m happy the result, it’s usable and practical, and you can build one too. This is incredibly cool.

A traditional PalmOS emulator requires a ROM: a binary object that contains the original PalmOS compiled and linked for the 68K architecture. When you run an application PRC in those emulators, everything is emulated down to the hardware layer, so the ROM thinks it is talking to an actual device. Therefore, as an emulator developer, your job is to provide an implementation of the CPU, memory, display, serial port, and so on, taking into accounting the low level differences between the myriad of devices that ran PalmOS back then. As long as your implementation of the physical layer is accurate, applications will generally run fine. PumpkinOS also allows you to run binary 68K applications, but do not require a copyrighted PalmOS ROM. The short story is this: the developers of PalmOS devised a clever way to implement system calls (also used in other 68K systems, I think). They used a feature of the 68K CPU called trap. A trap is like a subroutine call, but instead of jumping to a different memory addresses depending on the system call, it jumps to a fixed address, passing an argument identifying the system call. PumpkinOS takes advantage of this fact and, whenever a trap is issued, it intercepts the execution flow, identifies the system call, extract the parameters and calls a native implementation inside PumpkinOS, bypassing a ROM altogether. It is very similar to the way PACE (Palm Application Compatibility Environment) was implemented when PalmOS 5 was introduced. If the 68K application plays by the rules and only calls the OS through system traps, never accessing hardware directly, it will also run fine on PumpkinOS. Now, if you want to know the long version of this story, keep reading. Even more details about the inner-workings of PumpkinOS.

The developer of Pumpkin OS (which we talked about before), a port of the Palm OS to x86-64, has written a very interesting post about dealing with multi-threading. Pumpkin OS is multi-threaded from the start, but several parts of the operating system rely on old parts of Palm OS that were never meant to be multi-threaded – such as the M68K emulator used to run Palm OS applications written for that architecture. The solution I came up with uses something called thread local storage. Each thread has access to a private memory region that the main thread can setup in advance. When a deeply nested function needs to access global state, instead of using a global variable, it gets a pointer to its local storage. Each emulated M68K thread writes to its own M68K state, not interfering with another thread. And no function prototype needs to change. The first step was to identify all global variables used by the M68K emulator, which were surprisingly few. I’m so excited about this project.

We aim for the beautiful Sailfish user experience to bring a similar elegance and simplicity to an otherwise busy and distracting world. But the beauty on the surface has to be backed up with cutting-edge technology underneath which keeps up with modern standards and developments. That’s why in the 4.4.0 Vanha Rauma release we’ve been working hard to improve compatibility across the board, keeping up with recent browser and feature developments. At the same time, we’ve been refining the user interface to allow all the new features to be exposed in a way that doesn’t impact on the simplicity of your device in daily use. I’ve been a Sailfish OS user for years and am now involved in its development, so can’t claim to be an impartial actor. But it means I also have some understanding of the effort and ideas that went into this release. Some of the big new features are the updated Gecko browser engine, all apps Sailjailed by default, NFC Bluetooth pairing, and many nice community-contributed improvements to positioning, calendar and more – and all built on a a strong Linux/glibc foundation.

Dear friends, we’re gathered here today to mourn the death of that once-beloved monarch of the mobile world: BlackBerry. And, yes, I realize that this is not the first time we’ve announced the death of the company or its devices (and, for reasons I’ll explain below, it likely won’t be the last) but this is a very definite ending for legacy BlackBerry hardware. As of January 4th, any phones or tablets running BlackBerry’s own software — that’s BlackBerry 7.1 or earlier, BlackBerry 10, or its tablet operating system BlackBerry PlayBook — will “no longer reliably function,” says the company. Whether on Wi-Fi or cellular, there’ll be no guarantee you can make phone calls, send text messages, use data, establish an SMS connection, or even call 9-1-1. That sounds pretty darned dead to us. This seems ripe for a community of dedicated fans to build custom servers to keep things going – much like exist for many older games.

The headline improvement is one that was already trailed by Ville in his recent Sandboxing blog post. From now on, any app that defines an application profile will be automatically sandboxed. This is currently an opt-in process; any app that isn’t updated in this way will still run outside the sandbox. As a user this means you will start to see some third party apps bring up the sandboxing dialogue on first run. You should already be familiar with this from 4.2.0, in which the Jolla apps were already sandboxed. In 4.3.0 Suomenlinna you’ll start to see this more often. Users can of course still run apps however they want, but can feel more confident when running apps inside the sandbox. This is an important security advancement, and follows the roadmap Ville described towards having all apps sandboxed. We’ve been careful to increase security without compromising user-control, and we think you’ll appreciate the extra peace-of-mind that sandboxing brings. That’s a big new feature, and a welcome one, too. As usual, this new version also includes improvements to Sailfish’ Android application support and its web browser, among other things.

Sailfish OS 4.2.0 has been released, and it packs a completely reworked sharing systems, improvements to the browser and camera application, further work on application sandboxing, and more. Read the full release notes for more details.

Apple is gearing up to roll out iOS 15 later this year. The company plans to roll it out to several of its devices, going all the way back to the iPhone 6s and iPhone 6s Plus. This will make Apple the only smartphone OEM to offer seven years of software updates to its devices. That’s a remarkable feat, considering that only a couple of OEMs on the Android side promise three years of OS upgrades and four years of security updates. To bridge this gap, the EU proposed a new law earlier this year that would force all smartphone OEMs to offer up to five years of security updates for their devices and deliver reasonably priced spare parts for the same duration. Although the EU’s new right to repair laws are yet to go into effect, the German Federal Government has now announced plans to extend the support timeline by two years. A spokesperson for Germany’s Federal Ministry of Economics recently said (via Heise Online) that the government body plans to enforce stricter rules that would require OEMs to deliver spare parts and software updates for seven years. In addition, the Federal Government wants OEMs to publish the spare part prices and not increase them over time. That’s excellent news. With Germany being such an important part of the EU, I can only hope they will set the tone for the rest of the countries to follow. Do note, however, that it’s election season in Germany, so be on the lookout for political trial balloons.

For the last few weeks, I’ve been running CalyxOS. It is the latest in Free/Open Source mobile phone operating systems that I’ve used. This post is a summary of my experience using FLOSS mobile OSes and what my experience can tell us not only about phones, but Free/Open Source OSes in general. An excellent rundown of the various options in this space, and I’m tempted to see if I can make this step in the near future too. Cutting Google out of my mobile phone would be quite, quite welcome.

It’s 2021, and it’s time to upgrade your smartphone. Maybe it’s getting slow, it might be damaged, or your device’s OEM refuses to update your version of Android. Whatever the reason, you set your budget and full of hope and starry-eyed about all the possibilities, you go to your preferred electronics store (or carrier, if you’re American) – and as you scroll through the possible phones, your hopes are shattered and your heart sinks in your shoes. Your choices are between an endless array of black slabs, and while you can technically choose between Android and iOS, you will have most likely made that specific choice ages ago, and switching platforms is hard. Slightly dramatised, sure, but the reality of smartphones today is that all of them look and feel the same. The difference between mid range and high end have shrunk over the years, and while there are still small differences here and there, the general experience is going to be the same from device to device. Even if you skip a few years of upgrades, the jump in performance to the latest and greatest processor isn’t going to make that much of a difference in your day to day use. While you can technically opt for one of the new folding phones, the reality is that they still suffer from early adopter problems, and their prices are far beyond what most of us would want to pay for a smartphone. With all phones looking the same, it’s hard to find a company willing to stand out in a crowd of black rectangles. One of the victims of this race to the rectangle is the smartphone keyboard – whether it’s BlackBerry or Android phones with keyboards, they’re basically no longer being made, and if you’re simply not a fan of typing on featureless glass, you’re pretty much out of luck. Except, not really. There are a few companies left still making smartphones with keyboards, and the British company Planet Computers is one of them. This British company does not just focus on building Android smartphones with keyboards – they take the concept a step further and gun for the iconic Psion devices from the ’90s. The company’s chief designer, Martin Riddiford, worked at Psion in the ’90s and aided in the design of the Psion Series 5’s keyboard, and that design has formed the basis for the company’s first two devices: the Gemini PDA and the Cosmo Communicator. After seeing my sorrowful lament of the Nokia N900, the company contacted me and asked me if I wanted to review their Cosmo Communicator Android smartphone. I obviously didn’t hesitate to say yes, and after a few weeks of delay due to our first child being born, I can finally give you my thoughts and insights on this device that fills a unique niche in the current mobile landscape. Keyboard and hinge The Cosmo Communicator is unlike any other Android device on the market today. As to be expected due to its pedigree, the device resembles a Psion Series 5, or perhaps a Nokia Communicator if you’re more familiar with that line of devices. When closed, the device is thicker and heftier than most other smartphones, but there’s a valid reason for that: open it up, and inside you’ll find a full QWERTY keyboard with real keys. When opened, it looks more like a small laptop than a smartphone. I want to dive straight into that keyboard, since it’s by far the device’s most defining feature. First of all, it’s smaller than a regular keyboard, obviously, so it definitely takes a little time to get used to. I have small hands and tiny fingers, so for me, it wasn’t that hard to get used to the size of the keyboard. The layout of the keys feels natural, and for me, there are no cases where I would’ve opted for keys in different positions. With such a cramped space, you’ll always have to make compromises and hard choices, but I think the Planet team has made all the right choices. The layout will take some getting used to, but that’s to be expected with any new keyboard, especially one in such an exotic form factor. I’m slightly less happy about the actual typing experience, though. Granted, I am a very light typist who applies relatively little force to each key press, but I found that my key presses would often not register unless I applied what I would consider too much force. This problem increases the farther away from the home row I am, and it’s downright annoying. Getting used to a new keyboard layout and smaller keys is one thing – unless you have truly gigantic hands, it won’t take you more than a few days – but having to change how hard you press down on a key is very, very hard to learn. However, as said, if you apply more force for each key press than I do, this might not be much of an issue at all for you. You might wonder if you can use the keyboard when thumb-typing. My hands are definitely too small for thumb-typing, as reaching the centre-most keys requires an uncomfortable amount of stretching and grip adjustments. Again, though, my hands are small, and if you have more average-sized hands, you might be able to thumb-type just fine. The keyboard is backlit, and comes in a variety of keyboard layouts to choose from upon purchase. Using the Fn key, you can also control things like volume, brightness, airplane mode, and other Android-specific features, and Planet was smart enough to include full inverted-T arrow keys. Aside from the cramped size, it comes very close to offering all the functionality of a regular keyboard, and while my personal typing style doesn’t mesh well with it, the Planet team has done a great job given the constraints they were working in. Moving on from the keyboard, the second aspect of the Cosmo that stands out is

Sailfish OS Kvarken 4.1.0 has just been released to Early Access users across all officially supported devices, alongside which there’s also been an announcement of official support for the Xperiai 10 II. The free trial version of Sailfish OS is available for Xperia 10 II devices now in the early access phase. The commercial licences will be launched when OS release 4.1.0 rolls out to all users. In addition to the long list of bugfixes and feature improvements, Kvarken 4.1.0 on the Xperia 10 II is also the first version of Sailfish OS to run as 64-bit on ARM.