Mobile Archive

Earlier this year, Garmin closed its Connect API developer program because it was being flooded with “AI”-generated applications to the point it couldn’t handle them anymore. What made it worse was that half of the applications were never actually used, not even once. It also didn’t help that Garmin treated every single application to the program the same way, whether it was from a hobbyist just wanting access to their own data, to a massive corporation developing a popular service used by god knows how many people. Today, the company has relaunched the program, and it’s been considerably overhauled. While hobbyist use of the API is going to be free – which is way better than it was before – once you hit a thousand users, you’re going to have to start paying. Still, Garmin’s shift here towards charging for API access will set a dangerous precedent for the industry. Especially for a company that bills itself as a (or the?) premium sports hardware provider. On the flip side, there’s simply no ignoring the flood of mostly AI apps that take up resources at Garmin and elsewhere to support. Heck, my inbox is flooded with these apps daily requesting reviews. It sounds like when Garmin shut off access to the API last spring, they were seeing inbound API requests at a daily scale that they’d previously only seen over a period of weeks. Simply put, there’s no good answer. ↫ Ray Maker at DC Rainmaker The excesses of the easy availability of “AI” code generation impacts the entire industry. At least one good thing has come out of this: hobbyists can now access the Connect API developer program much easier than before.

Only a few day ago I linked to a massive collection of original Palm OS development resources, and today we can take a look at what it was like to put all of those resources into practice: the original source code for the Palm OS port of Lemmings. With these resources combined, there’s no excuse to not building any Palm OS applications. I’d really like a modern email client, a Fediverse client, and a slightly more modern browser surely wouldn’t hurt. Get on it!

Amos B. Batto has published an incredibly detailed look at the state of Linux on smartphones. It’s an excellent read you really shouldn’t skip. Five years ago, Linux phones looked like they were poised to become a viable alternative to the Android/iOS duopoly that has an iron grip on the mobile phone industry. Sadly, after a brief flash of activity and community engagement with the release of the Purism Librem 5 and the PINE64 PinePhone in 2020, the Linux phone market has generally stagnated. This stagnation occurred partly because of the problems at Purism and PINE64, but also because the available Linux SoC’s weren’t up to the task of running a modern smartphone, and the hardware industry wasn’t providing any good alternatives with good free/open source drivers. In addition, Plasma Mobile and Phosh were still inchoate mobile interfaces at the time, and there wasn’t a good distro option to run these interfaces on Android kernels with a normal integrated mobile SoC. The poor performance of the PinePhone and Librem 5 and the problems with the PinePhone Pro and the Librem 5 refunds sapped people’s enthusiasm and willingness to take a chance on the next Linux phone. Fortunately, all of these conditions are changing, and I believe that there is now the possibility that Linux could finally become a viable alternative to Google’s Android and Apple’s iOS in the mobile space, just like desktop Linux has become a viable alternative to Windows and Mac OSX on the PC over the last three decades. This isn’t to say that mobile Linux will fundamentally challenge the business of Google or Apple, but the conditions are ripe for a small market to arise for Linux phones, similar to the way that people can currently buy Linux PCs from a number of small companies, such as TUXEDO, System76, Purism, Slimbook, ThinkPenguin, Ubuntushop.biz, Entroware, Star Labs, Juno, Laptop with Linux, Linux Certified, ArkPC, etc. ↫ Amos B. Batto I’m not quite as optimistic as Batto, and that’s almost exclusively down to how running Android applications through compatibility layers will remain an absolute necessity for anyone trying to use one of these Linux smartphones today. As long as crucial applications and services required to function in a modern society, like banking, messaging, government services, and so on, require the use of an Android application when using a Linux smartphone, I just don’t think any significant number of people will be switching over. What’s needed is something that will force these crucial services to become available on platforms other than Android and iOS, since I don’t think any of them will do so of their own volition. The only way I can see this happening is if the European Union, spurred on by our desire to reduce our dependence on adversarial US companies, mandates that several services marked as crucial must make themselves available on platforms other than Android and iOS. I doubt that will happen, but I honestly don’t see Linux smartphones becoming anything more than a mere curiosity you fiddle with at home, while carrying an Android phone or iPhone as your actual phone.

Today, you can get low-quality knockoffs of just about any popular smartphone on sites like AliExpress or Temu, whether they be iPhones, Galaxy phones, or whatever else. They have terrible build quality, bottom-of-the-barrel components and specifications, and all run outdated versions of Android – badly. At the same time, various consumer electronics brands, once popular in a bygone era, sell the rights to their brand name to unknown companies, who then put these brands on generic hardware to give their products a sheen of legitimacy. That’s why today, you can still buy Nokia smartphones, Polaroid cameras, and low-effort Hi-Fi equipment from various once-respected brands. None of this is new, however. In the late ’90s and early 2000s, companies were already doing the same thing. In fact, there’s one device from this era which combines both business practices – it’s both a cheap knockoff of a wildly successful device, and it carries a once-revered brand name. Also, just to add some juice, this story involves stolen source code. Let’s take a look at the worst PDA of all time, the Olivetti daVinci. In 1997, Palm launched the Palm Pilot, and it and its successors proved to be a massive hit. Where countless before it had failed, Palm found the magic formula to make pocket computing work. I wrote an in-depth article about Palm over 13 years ago which goes into much (much) more detail, but the reason the Palm Pilot succeeded where things like the Newton, PenPoint OS, and Windows for Pen Computing failed, is that Palm’s founder, Jeff Hawkins, realised that they were competing with paper, not with desktop computers. Instead of trying to shove the capabilities of a full personal computer into a (barely) pockatable device, a pocket computer had to be as fast and convenient as paper, and therefore extremely strict about which features to add, and which to omit. To this day, the entirety of smartphone computing stands on the shoulders of Palm. Palm’s ideas, implementations, approaches, paradigms, and even people were absorbed by Apple and Google, where they shaped both iOS and Android. The phone you’re looking at right now has a ton of Palm DNA in it, still. After all, you’re still using the homescreen-with-apps paradigm Palm already perfected in the late ’90s and early 2000s. The success of the Palm Pilot and its successors did not go unnoticed. Microsoft, most prominently, felt incredibly threatened by Palm’s success: The success of Palm’s products got the attention of Microsoft, and the company pretty much announced it was going to crush Palm. According to Hawkins, Microsoft had a sales conference, where, at some point, a big target appeared on the projector screen, with the Palm logo dead in the centre of it: “we are going to crush and kill these guys”, was the central message. Hawkins recalls that he got condolence letters after that, stating things like “Sorry Jeff. Too bad.” ↫ Thom Holwerda While Microsoft proved to be unable to “kill and crush” Palm, it did manage to build a relatively successful business selling PDAs running various incarnations of Windows CE. Together, Palm and Microsoft dominated the PDA market pretty much throughout its entire existence, and while the market was a mere fraction of the smartphone market of today, other companies still wanted a piece of this pie too. One of these companies was Olivetti, a storied Italian company with a long history making typewriters, computers, and other electronics. I’m not going into detail about Olivetti’s history, but the company was renowned for its attention to design, creating iconic products like the Lexikon 80, Lettera 22, Elea 9003, Programma 101, and so, so many more. Olivetti also entered the personal computer market, first with a variety of custom machines featuring Z80 and later Motorola 68000 processors running a variety of custom operating systems developed by Olivetti (including its own UNIX variant, X/OS). After a few machines using MIPS and Alpha processors in the early ’90s, the company would eventually focus entirely on Intel-based PCs (including this amazing failure) running Windows. Like so many other computer makers from that era, Olivetti eventually left the PC business by selling it off in 1997. To this day, Olivetti PCs tend to cost more on the used market than those from other brands, despite no technical merits dictating so. At around this time, our current story begins. Seeing the success of the Palm Pilot and the emergence of copycat devices running Microsoft’s Windows CE, Olivetti wanted in on the action. And so, in the late ’90s, the company introduced the Olivetti daVinci, a line of PDAs whose software looked suspiciously like Palm OS. There’s not a ton of information out there about the development history, but it seems that while Olivetti designed the hardware, it contracted the development of the operating system out to a company from Hong Kong, Echolink Design. And this is where things went horribly wrong for Olivetti. The software Echolink Design developed for the daVinci didn’t just look like Palm OS, it was Palm OS – at least, according to Palm. After being on the market for about a year, the Palm Pilot maker, then a subsidiary of 3Com, filed for an injunction, alleging that the daVinci operating system designed by Echolink Design contained actual Palm OS source code. In addition, Palm also filed suit against CompanionLink Software, the company that developed the Outlook synchronisation software for the daVinci. Palm won handily, and within a day of the filing, temporary restraining orders were put in place on both Olivetti and CompanionLink, stopping sales of the daVinci and its software dead in its tracks. It seemed to have been a pretty clear-cut case. From The Wall Street Journal at the time: U.S. District Judge James Ware ruled Olivetti’s Royal daVinci organizer contains software that appears to have been copied from the operating system for 3Com’s Palm organizers. Judge Ware said a review by a software expert found the daVinci software contains private Palm code and even grammatical

João Carrasqueira at XDA Developers has taken a look at the current state of Sailfish OS, and concludes: As an idea, I love Sailfish OS. Not only does it bring a wholly unique interface to mobile devices at a time when things seem more unified than ever, but it also has the potential to bring the full power of Linux to a smartphone you actually want to use. But the lack of apps makes it hard for it to become anyone’s daily driver, and the power of Linux is somewhat hampered because it relies on dedicated repositories that, again, don’t get much support. The community as a whole would benefit if the UI for Sailfish OS could also be open-sourced and made available as a desktop environment other distros could adopt. I can see a world where many more Linux distros might be ported to mobile devices using this UI, and leading to more apps being ported to the platform as well. It’s unlikely, but taking that step could make a big difference. ↫ João Carrasqueira It seems like Sailfish OS, much like any other mobile operating system that isn’t Android or iOS, is still stuck in application hell, where they’ve always been. Windows Phone, BlackBerry 10, postmarketOS, Sailfish OS – they all suffer from the fact that the services and associated applications people actually need to use in their day-to-day life just simply aren’t there, and never will be unless something utterly drastic happens. You’re pretty much forced to fall back on possible Android application compatibility layers, at which point you’re basically just running Android in an worse way. As an extremely early customer of the original Jolla Phone, and owner of the very rare Jolla Tablet, I considered if I should add the new Jolla Phone as an incentive for the current fundraiser, but I decided against it because I already know what the review is going to be like. Interesting user interface, very limited set of often buggy native applications, constant reliance on often buggy Android compatibility layer, €750 is a lot of money for a barely mid-range phone. Oh, and the UI layer is closed source. I don’t need an expensive phone I won’t use after the review period to write any of that. There’s very little new to write about or discover when it comes to mobile operating systems other than Android and iOS, and that’s not through the fault of the people developing these platforms. All the smart developers working on postmarketOS, Salfish, Ubuntu Touch, and others are doing a great job and the very best they can, but in the end these platforms are limited by the fact that the services we all depend on just do not work on any of them. I don’t have the solution for the problem – other than very heavy-handed regulation to demand open APIs, which I support but will never happen – so the status quo will remain as it is. It’s a sad state of affairs when even Google-free Android is almost a non-starter at this point.

I have a Nokia N8, and it’s one of my favourite retro (?) devices I own. It was one of Nokia’s last efforts to make Symbian happen in the post-iPhone era, and while the hardware was quite nice, Symbian just wasn’t made for multitouch devices. It didn’t move the needle much for an already dying Nokia, and things just got worse from there. A bright spot with the Nokia N9, some decent Windows Phone devices, and then the end. We all know the story. The Nokia N8, though, seems to have been given a new lease on life recently. This smartphone, released in 2010, can be turned into a usable, capable device again, thanks to a brand new, modern custom Symbian ROM called Reborn. It takes the latest stock Symbian version for the N8, removes any and all applications/links/etc. that don’t work anymore, and then proceeds to make a ton of things work again. Modern TLS for HTTPS support, updated certificates, modern email support, a brand new application store, a new update application with a steady stream of OTA updates to fix issues, a bunch of security fixes, a whole slew of quality-of-life touches, and so, so much more. This is absolutely amazing work. Clearly a labour of love, there’s already been tons of updates over the past year since the ROM’s initial release, and I obviously can’t not install this on my own N8, assuming it still works. A video by Janus Cycle covering the project is also available, for the more visually-oriented among us.

Have you bought and set up a new phone for someone else lately, especially someone less technologically savvy? It’s a bit of a nightmare, with an endless list of confusing steps and dark patterns trying to trick you into signing up for all kinds of services. Joel Chrono (he took his username from the best game ever made) just went through this experience, with new Samsung phones for his parents, and it wasn’t great. Without me, my parents would have ended up creating at least one extra Samsung account. Cloud services like OneDrive or Google Photos would be sucking up files and copying them to their servers, getting filled up with the data and then asking them to subscribe to unlock more storage a couple of months down the line. Left on their own, my parents may be seeing ads popping up constantly in OneUI, as well as browsing the web without an adblocker, they would be using default applications that don’t work as reliably, that track whatever they do to a certain degree. And of course, all of those AI assistants would be listening in in the background. It really is a nightmare out there, and it’s not only affecting my parents, it affects all of those unaware of the dangers that these practices bring. It’s a mess all around. ↫ Joel Chrono In this particular case it involves Samsung phones, but the same applies to phones from other brands and even with other operating systems. Do you want to login with these accounts? Please add your credit card and all your personal information! Set up tap-to-pay so we can see where you buy what! Do you want to subscribe to our music service? Do you want access to our streaming service? What about the premium versions? Need more online storage? You’re only getting 5GB for free, so if you don’t want to lose those priceless pictures of your grand kids you should really upgrade to 1TB! Have you checked out our application store yet? And don’t worry, if you say no to any of these questions we’ll keep pestering you about them with notifications, fullscreen interstitials and banners in the settings application until your brain dissolves to mush! I have a collection of about a million PDAs, from the early days up until the very fanciest models from right around when the iPhone and Android started taking off. Of course, they’re in storage so virtually always out of battery, but when I do turn any of them on, their onboarding process couldn’t be simpler. Tap a few locations on the screen to calibrate the touch layer, set the date and time, and that’s it – you’re at the home screen ready to go. I wish modern smartphones were similar. I wish the greedy bean counters were told to pound sand and the user interface specialists took over again. My wife and I have two young boys, 3 and almost 5. One day, I’ll be the out-of-touch dad or grandpa and I’ll need their help to set up my brain implant chip or whatever. I hope it won’t involve upsells for streaming services.

This must be a universal experience at this point for people who aren’t swayed by the latest and greatest marketing hype around new phone models: there’s just nothing out there that fits one’s needs. When I walked into a phone shop, I expected to witness with amazement how much technology has advanced in the present day compared to my eight-year-old model, and for the power of marketing to mind control me into buying a new phone that would bring all sorts of benefits to my life. But instead, I felt disappointed that I’d be forced to choose between two suboptimal devices, either of which would be a compromise compared to what I already have. I felt frustrated that my OnePlus 5T, which still meets my needs and is working wonderfully (apart from the volume buttons), is being taken from me by the 3G shutdown. ↫ Cadence It’s remarkable how a market that was once rife with competition and choice, has now been reduced to well I guess I’ll settle for this one then in such a short time frame. There’s barely any competition, the number of device makers in (western or western-adjacent) countries has dropped to two, maybe three, and all of them are making what is essentially the exact same device with only the smallest of differences between them. For most average, normal people, it’s some model by either Samsung or Apple. There’s definitely more choice once you’re willing to leave local stores (and thus, easy and quick repairs) behind, but most normal people who just want a phone aren’t going to do that. You can also spend like twice or thrice the amount of money to get some foldable thing, but again, if you’re just looking for a bog-standard normal-person phone, that’s not a realistic option either. Smaller devices, headphone jacks, SD card slots – so many things have just disappeared from the face of the earth for most people, something that will definitely come as a huge, unpleasant surprise if you’ve been happy with an older phone that just had those things. It’s like driving the same car for a decade and needing a new one, but you can only choose between a Toyota and a Volkswagen that look and feel entirely the same. And also the seats are now candles, door handles are gone, and there’s no trunk.

Posh, GNOME’s mobile shell, published a look back on the project’s 2025. The Phosh developers focus from day one was to make devices running Phosh daily drivable without having to resort to any proprietary OSes as a fallback. This year showed improvements in some important areas people rely on like cell broadcasts and emergency calls, further improving usability and starting some ground work we’ll need for some upcoming features. ↫ Phosh developers In 2025, Posh gained support for cell broadcasts – like the emergency messages regarding storms, or alerts about missing persons, that sort of stuff – which is a pretty important feature in this day and age. Posh also improved its support for per-source audio volumes and one source of audio muting another, its on-screen keyboard, its compositor, and much more. Of course, the main problem for shells like Phosh is hardware support, which is handled by the underlying operating system, like PostmarketOS. These Linux mobile operating systems are fighting an uphill battle when it comes to hardware support, and while Android application support can fill some of the application shortcomings, you’re going to be making pretty significant concessions by switching to mobile Linux at the moment. When even Android ROMs not sanctioned by Google are having issues with banking applications or government ID stuff, using mobile Linux will be even more of a problem. None of this is the fault of any of the people dedicating their free time to things like Phosh or PostmarketOS, of course – it’s just a sad reality of a market we once again just gave up to a few megacorporations, with our governments too cowardly to stand up and fix this issue.

Any computing device will inevitably get a custom operating system – whether based on an existing operating system or something entirely custom – and of course, Kobo e-readers are no exception. QuillOS is an Alpine Linux-based distribution specifically developed for the unique challenges of e-readers, and comes with a custom Qt-based user interface, support for a whole slew of e-book formats, NetSurf as a web browser, encrypted storage, a VNC viewer, and a ton more. Basic hardware capabilities like Wi-Fi and power management are also supported, and it has online update support, too. The current release is already two years old, sadly, so I’m not sure how active the project is at this point. I wanted to highlight it here since something like this is a great way to liberate your Kobo device if, for some reason, Kobo ever started making their devices worse through updates, or the company shutters its services. You know, something that seems rather relevant today. Sadly, my own Kobo does not seem to be supported.

Some of you may be aware of rePalm, a project by Dmitry Grinberg to port the PalmOS to various devices it was never supposed to run on. We covered rePalm back in 2019 and again in 2023. His latest project involved porting PalmOS to a set of digital toys that were never intended to run PalmOS in any way. Fisher-Price (owned by Mattel) produced some toys in the early 2000 under the Pixter brand. They were touchscreen-based drawing toys, with cartridge-based extra games one could plug in. Pixter devices of the first three generations (“classic”, “plus”, and “2.0”) featured 80×80 black-and-white screens, which makes them of no interest for rePalm. The last two generations of Pixter (“color” and “multimedia”) featured 160×160 color displays. Now, this was more like it! Pixter was quite popular, as far as kids’ toys go, in USA in the early 2000s. A friend brought it to my attention a year ago as a potential rePalm target. The screen resolution was right and looking inside a “Pixter Color” showed an ARM SoC – a Sharp LH75411. The device had sound (games made noises), and touch panel was resistive. In theory – a viable rePalm target indeed. ↫ Dmitry Grinberg Considering the immensely limited ARMv7 implementation he had to deal with – no cache, no memory management unit, no memory protection unit – it’s a miracle Grinberg managed to succeed. To make matters even harder, the first revision boards of the “color” model only had 1MB of flash, which is incredibly small even for PalmOS 5, so he had to rewrite parts of it to make it fit. Implementing communication over infrared was also a major difficulty, but that, too he managed to get working – on a device that doesn’t have IrDA SIR modulation. Wild. Grinberg went above and beyond, making sure the buttons on the devices work, developing and building a way to put PalmOS on a “game” cartridge, reverse-engineering the display controller to make sure things like brightness adjustment works, adding screen type detection for that one small run of Pixter Color devices that came with a TFT instead of an STN screen, and so, so much more. Until you read the article, you have no idea how much work Grinberg put into this project. I continue to be in awe of Grinberg’s work every time I come across it.

As someone who cut their teeth on Maemo (the N800/N900 still live in my basement) and carried the first Jolla dev device, I like to pull out my SailfishOS phones every few months to see how things are progressing. Here’s where I’m at in September 2025. ↫ Nick Schmidt I was one of the very first people to review the original Jolla Phone way back in 2014, and I also happen to own the quite rare Jolla Tablet, so I was definitely a serious backer and believer in the platform back when it first entered the market. Sadly, the pace of improvements was slow, and failed adventures and mismanagement eventually led to the platform almost dying out. It’s only in recent years that they’ve been back on track and Sailfish OS is a more serious option again, but reading through Nick Schmidt’s findings, it seems the same problems still haunt the platform. And we all know what the main problem will be: application availability. In your day-to-day use, you’re going to be spending a lot of time using the Android compatibility layer, because native Sailfish applications simply don’t pull their weight. This leads to the age-old problem of any operating system that loses focus on native applications and opts to go all-in on compatibility layers or ports instead, and int he case of Sailfish that means: why run Sailfish to run Android applications poorly, when you can also just run Android? And why develop native applications, when your Android build can run using the compatibility layer? OS/2 (with Windows applications) and Haiku (with Qt/GTK applications) suffer from the same problem. Apparently, the Jolla C2 phone is not exactly great either, and doesn’t showcase Sailfish properly, and Sailfish’s keyboard is still unpleasant to use, a problem I also had in my original review so many years ago. There are some bright spots, too; the swipe-based navigation is still great, and apparently Wi-Fi connectivity is much more stable now. Still, it seems like Sailfish is suffering from more or less exactly the kind of problems you’d expect a small platform to suffer from, and whether or not you can deal with those problems is a more a question of dedication than just altering some use patterns. Android and iOS, though illegal practices, have sucked all the air out of the room, and I doubt we’re ever going to get any of it back.

Introduction It is very important to update your iPhone or iPad if you want to improve performance and security and get new features. However, it is also typical that the iOS update fails. Poor network, little storage, or various bugs are usually the reasons that the update gets interrupted. Most problems can be prevented with some proper preparation. In this guide, we’ll cover why iPhone software update failed error appears, how to prevent them, the best installation methods, and what to do if errors occur — including how Dr.Fone iOS System Repair can quickly fix failed updates without data loss. Why iOS updates fail iOS updates can fail due to numerous reasons. These failures are, in most cases, linked to device or network issues. A few of the most common causes are: Pre-update checklist to avoid failures A few simple preparations can go a long way to prevent an iOS update failure. Before you start, keep in mind that you should have already checked each of these: Recommended installation methods In essence, there are two dependable means to carry out iOS updates, and leveraging the right one would be as simple as a walk in the park: What to do if an iOS update fails Sometimes, even a well-anticipated iOS update can fail without obvious reasons. The cause might be hidden bugs or unexpected issues. When you encounter problems, keep calm and try these solutions: Fixing Update Failures with Dr.Fone iOS System Repair Why Use Dr.Fone iOS System Repair If simple troubleshooting has failed to resolve your iOS update issues, an iOS system repair tool specially made for the purpose can come to your aid. Dr.Fone – iOS System Repair by Wondershare is a product that can resolve over 150 iOS issues, such as failure of updates, continuous restarting, black screen, or a stuck device in Recovery Mode. Why use Dr.Fone iOS System Repair How to fix iOS update failures with Dr.Fone iOS System Repair By using Dr.Fone, here are the steps you should take to fix failed updates and to repair your iPhone or iPad: Step 1: Launch Dr.Fone and connect your device Get Wondershare Dr.Fone opened on your computer after downloading it. In the main dashboard, move to the Toolbox, and select System Repair. Step 2: Select iOS repair mode Pick your device kind (iPhone/iPad) and go along to iOS Repair. You may want to consider Standard/Advanced Repair to solve almost all issues without data loss. Step 3: Activate Recovery Mode By following the directions on the screen, you will turn your iPhone or iPad into Recovery Mode (or DFU Mode if it is necessary). Step 4: Obtain iOS firmware The software will find the right firmware automatically for your device. By clicking on Download, you will take the latest iOS package. After the download is done, Dr.Fone will double-check the firmware to ensure it’s safe and compatible. Step 5: Fix and device reboot Click on Repair Now, so the process of trouble-shooting your device starts. A progress bar will present the installation’s time. Tips to avoid future update failures Conclusion In fact, iOS updates are a must in order to keep the device running smoothly, be safe, and enjoy the new features, but a malfunction can still happen and be quite irritating. Most problems can be prevented if you ‘prepare’ by properly verifying your internet, storage, and battery. If the update is still stuck, some simple methods such as rebooting and switching the network, usually give results and more complex tools like Dr.Fone iOS System Repair are very effective in solving the hard ones without losing the data.

This is it, the one that adds systemd to postmarketOS! We have talked about the decision at length on this blog, make sure to read the initial announcement if this is the first time you are hearing about this. ↫ postmarketOS v25.06 release announcement While adding systemd to postmarketOS is certainly the tentpole feature of this release, it also updates the various user interfaces – GNOME’s and KDE’s mobile shells and applications – and moves to Alpine Linux 3.22 as its base. The mobile user interfaces for both Firefox and Thunderbird have been updated as well, there’s a ton of improvements and additions for individual devices, and a lot more. PostmarketOS, in case you are unaware, is a Linux distribution optimised for smartphones, focused on running mobile shells and applications. It’s not ready for prime-time quite yet, and device support will probably be the biggest hurdle for anyone wanting to try it out.