Here’s an interesting bit of news out of Mobile World Congress: Qualcomm says the Snapdragon 8 Gen 2 has been certified as the “world’s first commercially deployable iSIM (Integrated SIM)”. What the heck is an iSIM? Didn’t we just go through a SIM card transition with eSIM? We did, but iSIM is better than eSIM. We’ll explain, but the short answer is that iSIM is the next step in the continual march to reduce the size of SIM cards. eSIMs are still a chip taking up space on your motherboard, and that’s not ideal if you want to squeeze every square millimeter of space out of a phone. The next shrinking step is iSIM—an Integrated Subscriber Identity Module. Rather than a chip on the motherboard, iSIMs are integrated directly onto the SoC. SoC (system on a chip) integration is the technology that makes smartphones possible. Instead of a thousand little chips for things like the CPU, GPU, RAM, modem, and a bunch of other things, everything gets packed into one single do-everything piece of silicon. Individual chips require more space and power thanks to having to make motherboard traces to connect everything and having to deal with chip packages. I’m still using an old-fashioned traditional SIM card, and while I’m sure going with eSIM and now iSIM is great from a simplification and power usage point of view, I feel like they’re both also about taking control away from the user and shifting it towards the carrier. It was a long fight to get rid of locked phones (mostly), but with eSIM/iSIM it seems locking devices down in more fine-grained ways only becomes easier. I might be overreacting, but little red flags go up when I read about eSIM and now iSIM.
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.
We have seen how PumpkinOS runs a classic 68K application. First, code.0 and data.0 resources from the PRC are loaded and decoded. Then code.1 is loaded and the 68K emulator starts running it. Native applications, that is, applications compiled from source to the target architecture of PumpkinOS (x86 or ARM), are still stored in PRC files, having access to all PalmOS resources like forms, bitmaps, alerts, etc. In fact, the same resource compiler (pilrc) used to generate the binary resources for PalmOS is used in PumpkinOS. The difference lies in how code and data are stored and processed. PumpkinOS’ developer also sent out a tweet with a video of a new shell – which looks quite 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.
webOSArchive (WOSA) is the unofficial repository of information, restoration efforts, and archives for Palm/HP’s mobile webOS operating system. This site does not provide material or information about the spin-off operating systems, webOS Open Source Edition (wOSE) or LG’s webOS for TVs. It’s the position of the curator, and the remaining webOS community, that Palm and HP’s webOS devices, including the Pre series phones, the Veer and Pixi phones, and the TouchPad, remain useful devices that both provide value to their users and education to the rest of the industry. In fact, many webOS innovations have been copied by modern mobile OS developers. You can follow the ongoing efforts to restore and retain the usefulness of the platform here, or join the community and participate! This includes the entire application catalog, SDK, developer information, documentation, and a lot more. Impressive effort, and a great resource for people still using and/or playing with their webOS devices.
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.
MuditaOS has been released as open source. This mobile operating system is designed specifically for the Mudita Pure e-ink mobile phone, and is based on FreeRTOS. Developing our mobile operating system has been a big challenge in the process of creating Mudita Pure. We came up with a beautifully designed E Ink mobile OS and open-sourced it to fully meet our users’ desire for quality and transparency. This is an interesting take on the minimalist feature phones that enter the market every now and then, but I always wonder what the market is for these things, and how long it takes for users to give in and grab their regular smartphone again. You can find the code on GitHub.
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.
Pumpkin is the name I have given to my port of PalmOS running on the x64 architecture. Please refer to this article for basic information on this project. Also look for other articles in the PalmOS category for more information and some technical details on the implementation. This article is about the first Technology Preview of this project: a functional version of Pumpkin OS running on the Windows platform. This first release is limited on purpose: just a few PalmOS applications and nothing much else. This is also a binary only distribution, but do not worry, full source code will be released in the future. I’ve been following this project for a while now, and this is bonkers awesome work. Very limited for now, of course, but as a longtime Palm OS user and lover of all things Palm OS, this feels like it’s made just for me.
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.
We’re happy to share with you the many firsts in this release: the 1st fully stacked 64-bit ARM Sailfish OS, that you can download and flash onto the Sony Xperia 10 II, which is also the first Sailfish device with AOSP-10 HW adaptation. The commercial Sailfish X package also introduces the 64-bit Android App Support for Xperia 10 II. Sailfish OS Kvarken 4.1.0 has now moved from early access to full release. That means the early access bugs have been ironed out, but also that the paid-for additions (particularly Android App Support) are also now available for it. While the headline changes in 4.1.0 is the shift to full 64-bit ARM and support for the new hardware, it also introduces many other improvements, including to location data support, VPN support, audio recording, browser, calendar sync and contact sync, amongst other things.
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.
In what seems like several lifetimes ago, the mobile devices market seemed like it would be wide open. Even as the window for platforms that weren’t Android or iOS was closing rapidly, we were all hoping we wouldn’t end up with another duopoly. While there were several contenders – BlackBerryos 10, Windows Phone, to name a few – quite a few more nerdy mobile device users held out hope that instead of neutered, restrictive, and limited operating systems, we’d end up with a true computer in our pocket. No other device represented this slice of the market better than the Nokia N900. The N900 was the last standard Linux mobile device from Nokia, the last in the line of the N770, N800, and N810 internet communicators. The N900 was the first to include mobile phone functionality, making it the first Linux mobile phone device from Nokia, but not the last – the N950 and N9 would follow, but those were markedly different, more Android and iOS than standard Linux. The N900 ran Maemo, Nokia’s Linux platform for mobile devices, developed in collaboration with and/or using many popular open source Linux projects, like the Linux kernel (obviously), Debian, Gtk, GNOME, Qt, and more. Maemo’s user interface used the Matchbox window manager, and its application framework was Hildon. Underneath the Gtk+ user interface, Maemo was a remarkably standard Linux distribution, based on Debian, so you had easy access to all the usual Linux and Debian command line tools. It used APT for package management and software installation, BusyBox as the replacement for the GNU Core Utilities, and the X window manager. Still, despite its heavy focus on open source software, certain parts of the software stack were still closed source, like some code related to power management, as well as certain bits and bobs of the user interface, like a few status applets. This “mostly open source, but with some closed bits and bobs” would be a running theme into the future branches of the platform, like Sailfish and MeeGo. The hardware of the N900 is a case of throwing everything humanly possible into a single device, but to keep costs down, it mostly consists of cheaper parts. For example, the 800×480 resolution looks crisp on the 3.5″ display, but despite being released almost two years after the iPhone, the touch screen is resistive and requires a stylus. The SoC is a Texas Instruments OMAP3430, with a single core running at 600Mhz, supported by a 430 MHz C64x+ DSP and a PowerVR SGX530 GPU. You’ve got 256MB of RAM, 256MB of NAND flash, and 32GB of eMMC flash. The star of the show, of course, is the slide-out keyboard. It’s a full QWERTY keyboard that’s reasonably comfortable to type on considering its small size, and anyone who has ever used a Symbian device with a keyboard will feel right at home. It’s got a little kick stand, stereo speakers, and TV-out functionality through a special dongle and cable. Seeing Maemo 5 output to a giant 55″ 4K TV is a special kind of entertaining. Add to this the various standard things like WiFi, Bluetooth, a headphone jack, removable battery, rear and front camera, a dedicated camera button, and probably a few other features I’m forgetting. The N900 comes packed. Users of the N900 when it was new were a special kind of people. One of them was my brother – he was a die-hard N900 user for many years, so much so he bought a spare N900 in case his main one died. It wasn’t until the N900 really couldn’t keep up with modernity anymore – well past that point, honestly, but let’s not hurt his feelings – that he begrudgingly decided to switch over to an Android phone. He gifted one N900 to me for my collection. The N900 is a special kind of device that, while a footnote in mobile history, holds a special place in the hearts of a dedicated group of users who nobody is serving any more. These people wanted a proper mini-computer in their pocket, preferably running Linux, and the N900 was the only device that properly fit that niche. Its sort-of successors – the N9 and Jolla Phone, which I both have as well – simply do not fill that niche and do not scratch that itch. Today, most N900 users have probably migrated on to Android (and a few stragglers to Sailfish, I’m guessing), leaving behind the standard, regular Linux installation for the bastardised, weird Linux offshoot from Google. While you can install BusyBox on Android and unlock the bootloader and sort-of create an approximation of a standard Linux computer in your pocket – without the keyboard, without the more standard stacks and toolchains, it’s just not the same. There is still some hope for fans of the N900 – and other people who want a true Linux computer in their pocket – since there are two companies that sort-of cater to this niche. First, there’s F(x)tec, which probably comes closest with its line of smartphones with a slide-out keyboard. They currently offer a very cool device up for pre-order that’s capable of running Android, Sailfish, Ubuntu Touch, and standard ARM Linux distributions as well. I’ve been trying to get into touch with them for a review unit, but they have not responded (we’re small, after all). Another option that requires a bit more squinting are some of the very tiny laptops made by GPD – such as the GPD Pocket 2 and similar devices they make. They’re not quite the same as the F(x)tec or N900, but you can get quite close. GPD, too, has not responded to review requests, but again – we’re small, and if you can send stuff to outlets like Linus Tech Tips, OSNews simply isn’t on your radar. I’m genuinely sad that the N-line was yet another victim of Nokia’s endless mismanagement, since the N900 is simply a unique, one-of-a-kind device in a category virtually nobody even dares tip
The KaiStore team keeps up the momentum with another set of updates that make it easier to find the apps you’re looking for and enhance the UX experience as a whole. We don’t talk much about KaiOS on OSNews, which is a shame – it’s an offshoot of Firefox OS, and a massive success on phones that blends smartphone and feature phone functionality into one platform. This isn’t a big news item or anything, but ran across it and feel some attention for this platform is more than warranted.