# Postmarketos Published articles for Postmarketos. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects DevFeed: [postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects]() Original publisher: [Read original article]() Published: 2026-09-06T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [Testing](), [Operating system](), [GitLab](), [Internationalization (i18n)](), [gdb]() Tags: [2026](), [conferences](), [gdb](), [git](), [gitlab](), [i18n](), [infrastructure](), [linux](), [mobile](), [opensource](), [postmarketos](), [testing]() ### AI overview The August 2026 postmarketOS update covers conference appearances and a newly scheduled project conference, infrastructure improvements including faster Git repositories and a new debuginfod server, progress on musl libc collation and internationalization support, and an accepted proposal for an immutable postmarketOS release with improved automated hardware testing. ### Source excerpt Conferences has been the main theme of this month. We had stands at FrOSCon (photo, next to our friends from Phosh), FOSSY (pictured above) as well as DEFCON and the following postmarketOS / Linux Mobile related talks were given: Automated testing of a phone operating system (Luca at FrOSCon) Push-Benachrichtigungen. Dezentral und OpenSource (Daniel G. at FrOSCon) Random Cool Things from postmarketOS (a linux-based mobile OS) (Ranny at DEFCON) Controlling our devices: linux on mobile (Ranny at DEFCON) Besides that we have of course been very busy planning our own conference and are happy to announce that the schedule is now live! For those who did not get a ticket, the event is completely booked now but we are trying to do video recordings and/or live streams so you can watch the talks at home (no promises for that though since this is our first event). If all goes well, we might even follow up with another one next year. For those who will be there, make sure to join the Matrix chat / IRC channel. Organizational OSUOSL, who maintain gitlab.postmarketos.org, have reacted to slowdowns we have observed across the site and made it significantly faster by moving git repositories to SSDs. Thanks, Lance! Paul has joined the infrastructure team. NLnet and NGI Zero Core related news A production debuginfod server for postmarketOS and Alpine was set up, "allowing developers to automatically fetch debug symbols during crash analysis with tools like coredumpctl and gdb" (!9468, sync-debuginfod, milestone 34) An update was posted by Rich on the collation + i18n support in musl libc project: "I'm pleased to announce a big step in the #musl locale overhaul project: collation is working! This is the result of a long project to design data structures and logic that would admit honoring the full Unicode Collation Algorithm rules, including equivalence under normalization, and keep the size of collation weight tables for the entirety of Unicode under control." And last but not least, ## postmarketOS in 2026-07: libcamera 0.7.2 DevFeed: [postmarketOS in 2026-07: libcamera 0.7.2]() Original publisher: [Read original article]() Published: 2026-08-06T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [Pipewire](), [Firefox](), [WebRTC](), [GPU]() Tags: [alpine-linux](), [audio](), [boot](), [bug](), [camera](), [changelog](), [firefox](), [linux](), [mobile](), [notifications](), [patches](), [postmarketos](), [webrtc]() ### AI overview A postmarketOS monthly update covering the libcamera 0.7.2 release, camera color-correction and GPU-ISP performance improvements, video-call support through PipeWire and Firefox, and additional fixes and updates for mobile devices. ### Source excerpt The artwork above is a variation of a rollup banner for the upcoming FrOSCon event that Ranny has been working on. He shared a behind the scenes screenshot on Mastodon . Unless you are very familiar with the graphite graphics toolbox, you probably cannot imagine how complicated it looks. We are at DEFCON and FOSSY right now and will soon be at FrOSCon as well as our very own postmarketOS and Alpine Linux Conference. More on that as usual in the and what's next? section further below. Organizational Alicja is now a trusted contributor in postmarketOS! Libcamera 0.7.2 and video calls One of the most noticeable things that happened last month is the libcamera 0.7.2 release. Robert M. upgraded the postmarketOS edge package in !8991, dropping 11 (!) patches that he managed to upstream in the process. "The release notably includes fixes that allow us to start shipping color correction matrices in tuning files. This commit includes the current tuning iterations for the imx363 (used e.g. as Pixel 3a rear camera) and the s5kjn1 (used on e.g. as FairPhone 5 front camera). The later is also used for the other corresponding cameras on the mentioned devices, as they improve the quality over the default. This is, of course, planned to change in the future. The GPU-ISP also received major performance improvements, in particular if the dmabuf direct import path can be used. If that's not the case some INFO logs are printed, giving hints what needs to be improved in the V4L2 or GPU drivers." He also fixed camera selection for pipewire/libcamera in mobile-config-firefox 5.4.1 (!138) and wrote: "So on devices with working cameras you should be able to do video calls now OOTB. Some sites might run into a remaining webrtc issue though (the camera freezing after a short time) - I have some pending patches for that, with a FF test build at aports!105606 (mrtest add -a 105605). With that all major video chat sides should work." Thanks to Robert M. and the libcamera developers! Duranium The ## postmarketOS in 2026-06: Plasma 6.7 DevFeed: [postmarketOS in 2026-06: Plasma 6.7]() Original publisher: [Read original article]() Published: 2026-07-06T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [cloud-infrastructure](), [Hardware](), [USB](), [Rust](), [ci]() Tags: [2026](), [alpine-linux](), [ci](), [embedded](), [hardware](), [linux](), [postmarketos](), [rust](), [usb]() ### AI overview A June 2026 postmarketOS update highlights Plasma 6.7 reaching Alpine Linux and postmarketOS, a distributed phone CI project, conference collaboration, community changes, and work on the project's legal entity. It also reports the merger of usb-signaller into postmarketOS edge and a Rust rewrite addressing USB role switching and mainline-device issues. ### Source excerpt This June Plasma 6.7 was released and found its way into Alpine Linux and postmarketOS thanks to Bart who maintains KDE in both distros. Find out all about it in the official release announcement post! The post here covers some more highlights of what happened in postmarketOS since we made the last monthly blog post -- besides Alpen Avocado of course. Talks postmarketOS, freeing yourself from big tech with a proper Linux distribution doing it 'the right way' by Bart at NLUUG (Netherlands Unix Users Group) A Distributed Phone CI for postmarketOS by Pablo at Embedded Recipes Organizational Alpine Linux has joined our conference, making it officially The postmarketOS and Alpine Linux conference! This made sense since we are working together closely with Alpine folks on a lot of topics already, and so we get to meet each other in real life at this shared conference. They have graciously offered to cover snacks and lunch for all attendees. The Call for Proposals has been extended until 2026-07-31. Several people in our community and from other projects were interested in the phone harness (PDU) we created for our hardware CI. Pablo has created a process for requesting the phone harness. bluebunny and Lukas are now Trusted Contributors in postmarketOS! Ferass and Stefan have joined the Code of Conduct team. We have also added documentation for community spaces after receiving feedback that it wasn't obvious where the CoC applies. As reported before on this blog, we are working on creating a legal entity for postmarketOS. We have now contracted the non-profit European Activism Incubator to move forward with that and will follow up with more details after the summer. Thanks Pablo, Antoine, Rob! usb-signaller Dylan's usb-signaller has been merged to postmarketOS edge! He wrote in !8553: Some time ago, usb-moded was introduced to improve the handling of USB gadgets in postmarketOS, usb-moded was picked due to its long track record of being around as the daemon for this purpose ## postmarketOS v26.06 release: Alpen Avocado updates Alpine Linux, mobile UIs, and stability DevFeed: [postmarketOS v26.06 release: Alpen Avocado updates Alpine Linux, mobile UIs, and stability]() Original publisher: [Read original article]() Published: 2026-06-21T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [releases](), [Linux](), [Software](), [Mobile](), [User Interfaces]() Tags: [alpine-linux](), [linux](), [mobile](), [postmarketos](), [releases](), [software](), [ui]() ### AI overview The postmarketOS v26.06 release, named Alpen Avocado, targets Linux enthusiasts and includes stability improvements, automated testing work, an Alpine Linux 3.24 software stack, and updated mobile user interfaces. ### Source excerpt This release is geared mainly towards Linux enthusiasts. We are working hard on stability improvements and automated testing, but if you expect Android or iOS levels of polish, then this is not for you yet. Introduction That's right, we have a new naming scheme for our releases! Instead of the Friends-inspired "The One With...", we are now using an alliteration of the new wallpaper name (Alpen) and a fruit (🥑). The reason is that the previous scheme didn't always work, since new releases are time-based snapshots of Edge, and may not always have that one important feature to name the whole release after. Six months of work in upstream projects and in the postmarketOS community can often not be encapsulated in this format. So instead of "The One Where The Saga Continues, Part II", here is "Alpen Avocado"! Software Stack As always we target the most recent Alpine release. In case of v26.06 it is the excellent Alpine Linux 3.24. User Interfaces (UIs) Mobile UI Versions GNOME 50 replaces GNOME 49 from v25.12. The mobile variant stays on 48.mobile.0 for this release, but has received important fixes by Cédric in !8798 (fix for a crash and for busy looping in some scenarios). A question that regularly comes up is whether the mobile variant can be fully merged into upstream. Significant parts have already been upstreamed over the past years (most notably the new gesture framework), but there is still a lot left to do, and more contributors are needed to make this happen. If you are interested in improving GNOME Mobile, such as helping to upstream the rest and, in the meantime, help out with rebasing on new GNOME versions, then join the GNOME Mobile matrix channel. Thanks to Cédric and all the GNOME contributors! KDE Plasma Mobile 6.6.5 replaces version 6.5.6 from v25.12. Thanks to Devin, Bhushan, Andrew, Bart and all the KDE contributors! Phosh 0.55.0 replaces version 0.51.0 from v25.12. Stefan managed to reduce the number of settings apps we ship with Phosh by integrating re ## postmarketOS in 2026-04: new boot splash DevFeed: [postmarketOS in 2026-04: new boot splash]() Original publisher: [Read original article]() Published: 2026-05-10T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [releases](), [Maintainers](), [Development](), [Documentation]() Tags: [2026](), [boot](), [development](), [linux](), [maintainers](), [news](), [postmarketos](), [releases](), [tegra]() ### AI overview A postmarketOS project update reports a new Plymouth-based boot splash with boot-log access and screen rotation support. It also covers a ModemManager upgrade, plans to upstream q6voice to mainline Linux, the v26.06 release timeline, reimbursement-policy changes, governance updates, and maintainer changes. ### Source excerpt Booting has been made more appealing by the new splash screen, which is shown above. It changes the splash by adding the three segments of the logo fading in and out, but comes with some underlying functional improvements as well. As we switched from pbsplash to Plymouth, it is now possible to press ESC (or power on phones) to get the boot log and we can finally rotate the splash screen on devices where it looks wrong otherwise. Implementing this was great teamwork by Clayton, Aster, Brady, Rob, Ferass, Hakşiye, Mirthe, bluebunny and Sicelo in !7482! In other news, ModemManager was upgraded to 1.25.95_git20260422 in edge by Achill: "Stable release will be soon (expected in a few weeks) and has been very stable for most users, while bringing new features like cell broadcast that we can start to test in Alpine edge." As always, we are very grateful for the hard work of ModemManager maintainers (Aleksander et al.), and specifically Guido from Phosh for implementing cell broadcast. Organizational We will be financing work to upstream q6voice(d) to mainline Linux, see the previous blog post for details. The timeline for the upcoming v26.06 release has been published (now at docs.postmarketos.org, the previous wiki page for creating releases has been split up, reworked and moved to dpo / issue templates as it made more sense: !8486). We have approved changes to our reimbursement policy which allow community members to request reimbursement of items they use for the development of the project (!46). In order to put it into action, we have approved an additional budget entry of 500EUR to cover some of those expenses (!23). If what you are doing fits the policy, please feel free to make use of it! Following up on the power delegation topic from the Hackathon, the responsibility over selecting finance team members was moved from only Core Contributors to the Assembly (Core Contributors and Trusted Contributors). device-microsoft-surface-rt and device-nvidia-tegra-armv7 (both us ## postmarketOS funds work to upstream q6voice call-audio support for Qualcomm devices DevFeed: [postmarketOS funds work to upstream q6voice call-audio support for Qualcomm devices]() Original publisher: [Read original article]() Published: 2026-05-08T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Kernel](), [Qualcomm](), [Mobile](), [Software](), [Streams]() Tags: [android](), [audio](), [cellular](), [devices](), [driver](), [kernel](), [linux](), [maintenance](), [mobile](), [modem](), [patches](), [phones](), [postmarketos](), [qualcomm](), [software](), [streams]() ### AI overview postmarketOS is funding work to upstream q6voice support for Qualcomm devices. The project targets kernel patches and the q6voiced userspace daemon used to enable call audio on Linux mobile devices, reducing reliance on kernel forks and lowering maintenance burden. ### Source excerpt As we have mentioned in the 2026 financial budget, we are able to follow up last year's success of financing important audio improvements in postmarketOS and the wider Linux Mobile ecosystem with another project this year! This time we will tackle the currently unupstreamable q6voice patches that every kernel fork for Qualcomm devices has to carry in order to be able to do audio calls. This is one of the last pieces of technical debt that hold back most devices from using a pure mainline kernel without additional patches, which would in turn lower the maintenance burden significantly, make call audio more reliable and would make it easier for other Linux distributions to run on these devices as well. The proof of concept It was early 2020, not even three years had passed after postmarketOS was published, and most people reading this probably had not heard of the project yet. At that time, Minecrell and Nikita were very busy maintaining and bringing up the MSM8916 family of devices. In the process, they achieved a considerable milestone: they managed to get calls (!907) and call audio (!1228, !1233) working on mainline for devices released with Android. This, for the first time, allowed those devices to be used as actual phones! Specifically for enabling call audio, Minecrell wrote two distinct pieces of software: The q6voice kernel driver: first included in a release of the msm8916 close-to-mainline kernel, it talks to the modem, and configures it so the audio that is being received from the cellular tower can be consumed in software. The q6voiced user-space daemon talks to the kernel to start or stop the audio streams so one can hear the other person on the other side of the call. Although an extraordinary achievement, the implementation was considered a workaround by the authors. From the initial commit: Eventually this should go away by implementing codec2codec support for q6voice in the kernel. In that case, the stream would be started once the audio routes are ## postmarketOS in 2026-03: conference announcement DevFeed: [postmarketOS in 2026-03: conference announcement]() Original publisher: [Read original article]() Published: 2026-04-05T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Python 3.14](), [decision-making](), [meetings](), [Hackathon]() Tags: [2026](), [alpine](), [announcement](), [conference](), [decision-making](), [gnome](), [hackathon](), [meetings](), [postmarketos](), [teams](), [technical]() ### AI overview A postmarketOS monthly update covering Python 3.14 entering Alpine edge, GNOME 50, community event participation, an upcoming postmarketOS conference in Aachen, governance changes, and package-maintainer workflow updates. ### Source excerpt A lot has happened since the last monthly blog post. Python 3.14 is now in Alpine edge (which as usually involved rebuilding and fixing up a lot of packages, thanks to everybody who took part in this!). The amazing GNOME developers brought us GNOME 50 "Tokyo" and speaking of that city, OSC Tokyo 2026 Spring took place and we were represented by Rob at the event. He had a stand, handed out Japanese and English leaflets about postmarketOS as well as stickers and showed postmarketOS running on several devices. From his event report: "As always there were many interested members of the community coming to the table, many [had not] heard about postmarketOS, but also several (10-20%) mentioned, they had an older device, which they want to test on but have not done so." Conference Announcement While we have talked about lots of events that we attended before, we are very excited to announce that we are hosting our own little conference later this year! When: 25th to 27th of September Where: RWTH Aachen University, Aachen, Germany (two rooms, not all buildings 😉) The goal is to get people from postmarketOS and related communities like Alpine Linux together and to have talks, workshops, technical discussions, figure out how to advance the project and to simply see each other IRL. A lot still needs to be figured out, but we are announcing the date early so the people who want to attend can already mark it in their calendar. We will follow up with a call for participation, registration and a conference schedule and are extremely excited to bring this together. Thanks to RWTH Aachen for the opportunity and to Aelin, Achill and Pablo for organizing it so far! Organizational Following up on the power delegation and teams topic from the hackathon, the decision making power has been moved from the Core Team to the whole team (Core Contributors + Trusted Contributors), and decisions are now being made asynchronously between team meetings (so more people have the chance to vote, not ## Introducing Duranium: a more reliable postmarketOS DevFeed: [Introducing Duranium: a more reliable postmarketOS]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Operating system](), [systemd](), [Linux](), [Deployment](), [reliability](), [systems](), [Tooling]() Tags: [deployment](), [hardware](), [postmarketos](), [reliability](), [systemd](), [technical]() ### AI overview Duranium is an immutable postmarketOS variant that uses read-only, cryptographically verified system images and automatic rollback for updates. The project prioritizes reliability and ease of use, while requiring newer hardware and remaining a work in progress seeking testers. ### Source excerpt Image-based updates are nothing to bawk at. Duranium is an immutable variant of postmarketOS, built around the idea that your device should just work, and keep working. You shouldn't need to know what a terminal is to keep your device running. "Immutable" means the core operating system is read-only and can't be modified while it's running. System updates are applied as complete, verified images rather than individual packages. Either the new image works, or the system falls back to the previous one automatically. No partially-applied state. No debugging audio when you need to make a phone call and no fussing with a broken web browser when you just want to doomscroll cat photos. It also means developers can reproduce the exact state of a user's device, making it much easier to track down and fix issues. Reliability and ease of use take priority over flexibility. Some choices that make it robust also mean it has higher hardware requirements and won't run on every device that can boot postmarketOS. Not every device that can boot postmarketOS will be supported. The package base for Duranium is shared with current versions of postmarketOS, and improvements flow into both. Think of it as a different deployment model on top, not a fork. Duranium is still a work in progress. We are looking for testers, not people who need a reliable daily driver just yet. See the Help Wanted section at the end of this post if this interests you! The initial proof-of-concept was funded by NLnet through the NGI initiative. Some ongoing development is funded through the postmarketOS Contributor Support Program. The technical details If the implementation details aren't your thing, feel free to skip to the end. For full details on everything covered here, see the design document. Tooling choices Duranium is built on systemd's image-based OS tooling. If you want the full story on why postmarketOS ships systemd, that's covered here. Specifically: tools like systemd-sysupdate, systemd-repart, and ## Financial update: 2025 financial report and new budget DevFeed: [Financial update: 2025 financial report and new budget]() Original publisher: [Read original article]() Published: 2026-03-11T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [foss](), [Linux](), [Mobile](), [Automation]() Tags: [2025](), [blog-post](), [financial](), [postmarketos](), [report](), [update]() ### AI overview A postmarketOS financial update reviews the 2025 budget against actual income and expenses, explains the move to automated double-entry bookkeeping with hledger, and outlines the approved 2026 budget, including q6voice rework and upstreaming for Linux Mobile devices. ### Source excerpt At the end of January, the 2025 financial year for postmarketOS came to its end, and soon afterwards the budget for the 2026 financial year got approved. Therefore, it is time for a new financial update! This blog post is split into a look at the 2025 budget (plan vs. execution), and further below the budget for 2026, of which the most exciting part is probably the q6voice rework and upstreaming which will improve audio significantly for postmarketOS and other Linux Mobile distributions on a large number of QC devices. Thanks to everybody who has donated to postmarketOS to make this possible! 2025 financial year report During the 2025 financial year we have put a lot of work and emphasis on financial automation, which lead to a previous report mid-year. However, as our income and expenses have continued growing, the complexity of the operations have too. In consequence, just tracking the money in and money out of our Open Collective account is no longer enough to represent our financial situation. For example, if a certain task has been commissioned to happen in 2025, but for whatever reasons the invoice only arrived in 2026, there needs to be a way to keep track of that. The standard way to do so is by using double-entry bookkeeping. Luckily, there are a few FOSS tools which allow to still automate most of such setup, and keep things transparent. We have decided on hledger and published our initial journal file with the 2025 financial year data here. We will go through it below. Budget and results The plan for 2025 was to receive 12948EUR in donations income, and have 27785EUR as expenses. The idea was to reduce the 47000EUR that were laying in our account and put them to good use. Given that through the year we saw a remarkable increase in income, we amended the budget twice, increasing the expenses for a total of 35985EUR . We did so to be able to execute on the goal of putting money to good use, rather than have it sit in a bank account. At the end of the year, we receiv ## postmarketOS in 2026-02: generic kernels DevFeed: [postmarketOS in 2026-02: generic kernels]() Original publisher: [Read original article]() Published: 2026-02-26T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Development](), [Maintainers](), [Mobile](), [Android](), [Artificial Intelligence]() Tags: [2026](), [android](), [development](), [maintainers](), [mobile](), [phones](), [postmarketos]() ### AI overview A February 2026 postmarketOS update covers project requirements for the main device category, an updated policy forbidding generative AI, changes among Trusted Contributors, and contributor work on Android phones, Chromebook support, mobile devices, and related development. ### Source excerpt The biggest thing in February for postmarketOS was of course FOSDEM and our hackathon, about which we wrote a whole blog post already. Because of this, and the new approach outlined in the last monthly post, the blog post here is compareatively short. Organizational The PMCR 0009 about defining new requirements for the "main" device category is still in discussion but coming along nicely. The goal of this is to ensure that devices in main will be reliable and will be set up to stay there for a long time, once they are in that category. Thanks to everybody who has given feedback so far! Our AI policy has been updated to explicitly forbid generative AI, and to be shorter and easier to understand (!49). Thanks, Oliver! Trusted Contributors Bhushan is now a Trusted Contributor in postmarketOS! He has already been quite active in postmarketOS from 2018 to 2021 and has recently returned to KDE Plasma Mobile upstream development as well, which he has been doing for several years beforehand. Furthermore he is helping with improving certain mainline devices, such as the Fairphone 5 where he recently collaborated with Luca to get call audio from the speaker working for the first time! Minecrell stepped down as a TC. Among many other things, he was one of the initial maintainers that brought postmarketOS to Android phones, maintaining many of the MSM8916 devices, and the first one that enabled voice calls developing q6voiced. Minecrell is still available to answer questions and help guide people in the community in things that are part of his expertise. Anton stepped down as TC. He has pioneered Chromebook support in postmarketOS, implementing depthcharge support in pmbootstrap and many other things that were needed to make this possible. Furthermore he has been maintaining the port for the AYA Odin game console, and mainlining it, and worked on many other great things in postmarketOS. A warm welcome to Bhushan and a huge thanks to Minecrell and Anton for how they have pushed ## FOSDEM 2026 + Hackathon DevFeed: [FOSDEM 2026 + Hackathon]() Original publisher: [Read original article]() Published: 2026-02-10T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [FOSDEM](), [foss](), [Mobile](), [Hackathon](), [ci](), [Kernel](), [Hardware](), [reliability](), [patches]() Tags: [2026](), [ci](), [fosdem](), [hackathon](), [hardware](), [kernel](), [linux](), [mobile](), [patches](), [pcb](), [postmarketos](), [qr-code](), [recording](), [reliability]() ### AI overview A postmarketOS report on FOSDEM 2026 and its accompanying hackathon, covering the project's stand, FOSS on Mobile talks, podcast recording, phone updates, hardware CI, and collaborative hacking activities. ### Source excerpt Another FOSDEM and Hackathon are in the rear-view mirror, and it is hard to find words to describe how amazingly productive and fun the experience was! We met so many people at the postmarketOS stand, in the FOSS on Mobile devroom and at dinners in the evening. As always it is fun to put faces to nicknames and to talk about the Linux Mobile ecosystem, and figure out how to improve it in person. FOSDEM 2026 Stand: Besides a good selection of phones (+ external screen) and stickers, version v0.3 of our phone-harness PCB had arrived just in time to show it at the stand this year and people were quite excited about it! This year we also had proper phone stands for the first time, as well as shirts (we gave 26 of them away to people who donated), namecards, and a QR code that goes to the donation page. There were too many great interactions to recount here, but to quote just one from Mat's fedi post: "Most memorable #FOSDEM moment for me has to be at the #postmarketOS booth, where I asked for help updating my phone, handed it over and ended up with Bhushan almost (I think) getting the mic working on it. Had to leave to catch a talk, but hey I did get my phone updated 😄" Luca, Bart, Hugo B. and Aelin are ready for curious FOSDEM visitors after preparing the stand together with Federico. The other side of the stand, where one can see the PCB that the phone on the right was connected to. Federico, who created it together with Nicola, was there in person and happily talked to the many people interested in our hardware CI setup. Talks: The FOSS on Mobile devroom had far better ventilation than last year, and was pretty much full all the time. We had plenty of postmarketOS related talks, and recordings for all of them are available: postmarketOS: Reliability in 2026 by Oliver Mainline kernel for Fairphones - 2026 update by Luca Phosh: What's new and where are we going? by Evangelos Snapdragon 8 Gen 3 Mainline: From Day-1 Patches to Product Reality by Neil Running mainline Lin ## postmarketOS in 2026-01: monthly blog post reboot DevFeed: [postmarketOS in 2026-01: monthly blog post reboot]() Original publisher: [Read original article]() Published: 2026-01-25T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [foss](), [Linux](), [Mobile](), [Kernel](), [e-ink](), [Testing]() Tags: [2026](), [blog-post](), [bootloader](), [e-ink](), [fosdem](), [foss](), [kernel](), [linux](), [mobile](), [pinenote](), [postmarketos](), [team](), [update]() ### AI overview A postmarketOS update explains the project's new blog format, highlights organizational changes and contributor work, and previews FOSDEM 2026 talks about Linux Mobile, Fairphone kernel support, and reliability. It also covers PineNote and other device, package, kernel, and bootloader contributions. ### Source excerpt A new year is a good opportunity to reflect on what has worked and what did not, and improve the things that didn't. We did that with the "monthly" blog posts, of which we had published the last one for October 2025. The reason that it took us so long to write these is, that we were trying to link every merge request that got merged since the previous post and write short summaries for most of them. While this results in a very detailed account of what has happened, it became less feasible over time as we had more contributions in postmarketOS. After a good conversation we decided to change the format to talk about the highlights and going into detail sometimes, instead of achieving a complete report of everything that has happened. One major goal of the previous approach was thanking all the amazing people who contributed to the project, but we solved that by just adding the contributor names in the blog post in a separate section. The title image of this blog post was taken at the very inspiring 39C3. If you would like to have some postmarketOS stickers as well, the next chance to get them is FOSDEM 2026 where we will have our own stand again where you can stop by and talk to us about all things postmarketOS! We are also excited to have two talks from postmarketOS team members: Mainline kernel for Fairphones - 2026 update postmarketOS: Reliability in 2026 ...as well as many more postmarketOS and Linux Mobile related talks in the FOSS on Mobile devroom! Organizational Alexey M. stepped down as Trusted Contributor. He has been improving postmarketOS across the whole stack since 2019. Among lots of other things he created libapk-qt and used it to add an apk backend to KDE's Plasma Discover, which eventually found its way upstream. He also improved pmbootstrap, maintained multiple devices and kernels and did a lot of kernel and bootloader work. Thank you very much and all the best for your new endeavours! The PineNote using Sway with hrdl's opinionated configuration. No ## Hardware testing automation: a minimum viable product DevFeed: [Hardware testing automation: a minimum viable product]() Original publisher: [Read original article]() Published: 2026-01-21T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Automation](), [Testing](), [Integration testing](), [GitLab](), [ci](), [Tooling](), [qemu](), [Kernel](), [boot](), [Embedded Software Dev](), [deploy](), [x86]() Tags: [automation](), [boot](), [ci](), [firmware](), [gitlab](), [hardware](), [integration-testing](), [kernel](), [postmarketos](), [qemu](), [testing](), [x86]() ### AI overview The postmarketOS team reports a minimum viable hardware-testing automation system now integrated into its regular development workflow. It provides QEMU runners and a OnePlus 6T real-hardware runner in GitLab, supports integration testing on device runners, and describes related PCB revisions and control firmware. ### Source excerpt Since our last update in May we have continued working on hardware-testing automation. We are happy to announce that we have reached an important milestone: we are now testing the OnePlus 6T as part of our regular development workflow! If you are not sure why this is important, or want to read more about the design decisions and the different parts that compromise the system, you can find all the information in the previous blog post. Work done and current status Since May, the system that we designed has been put in place. To make it possible, the following work has been executed: 4 QEMU runners available, 2 for x86_64, 1 for aarch64, and 1 for armv7 are now available in GitLab, and can be used in any project. This can be done importing the corresponding tags. Thanks Oliver and Martin R. for setting these up! A OnePlus 6T runner is now also available in GitLab, which means that if selecting this device, tests will run on real hardware. You can see a full demo video of the device booting up in here. Thanks Martin R. and Clayton for setting it up! Thanks to Martin R. and Pablo, support for integration testing on the device-runners is now available in our GitLab (!17, !19, !20) and integrated in: postmarketos-mkinitfs (!63) boot-deploy (!81) pmaports (!6696, !7553, !7489) Thanks to Federico and Nicola, the PCB to control the hardware went through 3 revisions: The first revision (v0.1) included just 2 assembled boards, and other empty ones for debugging. The PCBs were received, and although non-functional, most issues could be debugged successfully. The second version (v0.2) included the fixes from the first revision, and consisted already of 5 fully assembled PCBs. This version is already good enough for being used to power the OnePlus 6T in Martin R.'s farm. The third revision (v0.3), has some small fixes, and potentially support for buttons for Samsung (and maybe other) devices. This order is a bigger batch of 20 boards to distribute to Trusted Contributors, and sho ## Quiet audio on systemd with GNOME/Phosh installs for stable and edge DevFeed: [Quiet audio on systemd with GNOME/Phosh installs for stable and edge]() Original publisher: [Read original article]() Published: 2026-01-17T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [systemd](), [Mobile](), [Qualcomm]() Tags: [audio](), [bugs](), [mobile](), [postmarketos](), [qualcomm](), [release-notes](), [systemd](), [upgrade]() ### AI overview A postmarketOS release issue caused non-functional or very low audio by default on some Qualcomm devices using systemd with GNOME or Phosh in stable and edge installations. The issue involves audio-server selection and Pipewire-related problems; an upgrade or Pulseaudio package change may resolve it depending on the installation. ### Source excerpt Unfortunately, despite a lot of testing previous to the v25.12 release, a combination of several bugs with similar symptoms resulted in non-functional audio by default for some Qualcomm devices when specifically installing systemd and GNOME/Phosh (more specifically gnome-settings-daemon, which is a core part of the desktop). If you are using a device with a Qualcomm chip, are in edge or stable, have a recent install of systemd with GNOME, and experience very low audio, you might be able to fix the issue by running the following command: doas apk add postmarketos-base-ui-audio-pulseaudio In case that does not fix your issues, you can come back to the previous status by running doas apk del postmarketos-base-ui-audio-pulseaudio EDIT: We merged !7776, which obsoletes the steps mentioned for postmarketOS edge, you just need to run doas apk upgrade -Ua. We're still waiting a testing period before we merge this for the stable release v25.12 as well. (!7783) Root causes Some Qualcomm devices have had issues with volume under Pipewire due to audio formats for a while. There is a workaround available in postmarketOS, but it is not applied consistently to all devices. This should not have been a big deal, since in principle we are not using Pipewire's audio server by default. However, there is also an issue affecting the default choice of audio server between pipewire-pulse and pulseaudio on new installs. For some reasons that we have not yet fully understood, the combination of systemd and gnome-settings-daemon results in pipewire-pulse being installed, even when pulseaudio is expected. Progress is being tracked in !7776. We also cannot discard further issues with Pipewire's audio server, as that is not yet extensively tested on mobile. The day we change the default, we will provide a notice and make sure that more testing is executed. Hopefully the hardware CI work can help with this in the future. We apologize for the inconvenience this has caused, specially since this iss ## postmarketOS v25.12 release upgrades Alpine Linux, package management, and mobile UIs DevFeed: [postmarketOS v25.12 release upgrades Alpine Linux, package management, and mobile UIs]() Original publisher: [Read original article]() Published: 2025-12-23T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [releases](), [Linux](), [Package manager](), [Release notes](), [Software](), [upgrade](), [Testing]() Tags: [alpine-linux](), [linux](), [packages](), [postmarketos](), [projects](), [release-notes](), [software](), [testing](), [upgrade]() ### AI overview The postmarketOS v25.12 release targets Linux enthusiasts and includes Alpine Linux 3.23, Alpine Package Keeper version 3, updated software, and mobile UI changes. The package manager now downloads packages before installation and logs changes. ### Source excerpt This release is geared mainly towards Linux enthusiasts. We are working hard on stability improvements and automated testing, but if you expect Android or iOS levels of polish, then this is not for you yet. Introduction The year is coming to a close and while you might be unwrapping other gifts shortly, we have just wrapped up the latest postmarketOS release for you. Following the epic v25.06 release where we added systemd, the most substantial change this time is less visible, but nevertheless very important: a major upgrade of the package manager (more on that below). Besides that you get once more a completely upgraded software stack representing six months of work in upstream projects and in the postmarketOS community. Software Stack Alpine Linux 3.23 As always we target the most recent Alpine release. In case of v25.12 it is the excellent Alpine Linux 3.23 and it comes with the new major version 3 of the Alpine Package Keeper, which has been released after five years (!) of development. It includes some really nice changes, such as downloading packages before installing them (which we enabled by default in postmarketOS), so that a flaky internet connection can't ever break your system again while installing updates. Another long awaited feature is logging all changes to /var/log/apk.log. See the apk3 release notes for more information. Thanks to everybody who worked on apk3 and Alpine Linux 3.23! User Interfaces (UIs) Mobile UI Versions GNOME 49 replaces GNOME 48 from v25.06. As with everything below, we recommend taking a look at upstream's release notes if you are running this UI to discover all the amazing things that made it in there! The mobile variant stays on 48.mobile.0 for this release. However we are excited to have GNOME Software upgraded from 45.3 (we had to hold it back earlier as the apk plugin couldn't be adjusted in time) to 49.2 thanks to amazing work by Angelo, Rasmus, Pablo, Sertonix, Achill and Stefan (!91416, !55). Furthermore new installat ## postmarketOS launches a contributor compensation programme funded by donations DevFeed: [postmarketOS launches a contributor compensation programme funded by donations]() Original publisher: [Read original article]() Published: 2025-12-19T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Development](), [maintenance](), [Documentation](), [Support](), [Tool](), [Repositories]() Tags: [contributions](), [contributors](), [development](), [documentation](), [financial](), [funding](), [kernel](), [metrics](), [postmarketos](), [processes](), [repositories](), [support](), [upgrades](), [work]() ### AI overview postmarketOS announces a Contributor Support Programme that offers financial compensation to contributors with high time commitments. The programme aims to support essential maintenance, support, and administrative work, while distributing funds using equal hourly compensation and logged work. ### Source excerpt We are excited to announce the Contributor Support Programme. This programme offers postmarketOS contributors with a high time-commitment the option to receive financial compensation for the work they do. It is designed to achieve the following goals: Address some of the sustainability challenges facing postmarketOS development. While we can oftentimes fund feature development through donations (e.g. wireplumber and callaudiod) or grants, other work like essential maintenance, support, and administrative tasks remains difficult to get funded with our current approaches. Some people have already been working on these topics full-time or part-time with no compensation. Ensure fairness and equality among participants and their contributions. Everybody is entitled to the same hourly compensation, regardless of location, kind of tasks, or any other variables. Fulfill our commitment to supporters who have donated specifically to compensate contributors, as stated on our Open Collective page. Establish metrics that strengthen future funding applications by demonstrating our current resource investment, and our ability to distribute funds fairly and efficiently. High level overview Every quarter, eligible contributors can opt in for the programme. The total amount of funds available is taken from excess donation income, while making sure that other budgeted items are not affected. Then, every month, contributors invoice proportionally to the hours they work, and report on the tasks that they spend time based on the logged hours. If you want to read more details about criteria, processes, and reasons, you can check the documentation. We see this as another small step towards improving the project and fulfilling the long-term goals! Monthly report November 2025 And as we started working on this programme in November, we are now able to provide our first report! During this last month: Stefan spent a lot of time looking at pmbootstrap, the tool we use for development. He opene ## postmarketOS in 2025-10: Fairphone Camera Streak, Sxmo 1.18.0, SDM660 Enablements, MCF Rework, FLOSS/fund, LLVM for kernels, Better Docs DevFeed: [postmarketOS in 2025-10: Fairphone Camera Streak, Sxmo 1.18.0, SDM660 Enablements, MCF Rework, FLOSS/fund, LLVM for kernels, Better Docs]() Original publisher: [Read original article]() Published: 2025-11-13T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Mobile](), [Linux](), [Open Source](), [Development]() Tags: [linux](), [mobile](), [open-source](), [postmarketos]() ### AI overview A postmarketOS update covering Linux mobile development, including working Fairphone 3 and 4 cameras with mainline Linux, device enablements, community events, project funding, and development support. ### Source excerpt Since our last blog post, we have been at a couple of events again: Federico represented us in Palermo, Italy on the 25th of October, doing a talk and sharing a stand with Marco from the Mobian community (event report). On the same day Rob had a postmarketOS stand at Open Source Conference 2025 Tokyo/Fall in Japan (event report). If you are in the area, Rob was invited to do an upcoming presentation at TLUG. Jozef posted a photo from the Linux Mobile stand at OpenAlt in Brno, Czech Republic taking place on November 1 and 2, with some devices running postmarketOS and other alternative cool operating systems from the Linux Mobile ecosystem. Last weekend SeaGL took place in Seattle, US with Clayton, Arnav and Paul at the postmarketOS table, among other things playing with immutable postmarketOS on the new BlackBerry KEY 2 port. Thanks to everybody who went to those events, and to Free Circle G/LUG from Palermo and all other event organizers! Luca on the other hand stayed at home with his cat to bring up the Fairphone 4 cameras in one week, and Fairphone 3 cameras the week after from a night train: "As of tonight the Fairphone 3 cameras (front and rear) are working on postmarketOS with mainline Linux! And if you saw, only last week I got the Fairphone 4 cameras to work. A bright future is ahead for mobile Linux! 📸" Organizational Applying for FLOSS/fund was well worth it: "We are pleased to inform you that postmarketOS is being awarded 25000 USD by FLOSS/fund to support its continued development. We deeply appreciate the work you do and its impact, and are happy to be a small part of something that all of us derive immense value from. You can read more about our second tranche, learnings from this year, and future plans on our anniversary blog post." We are currently working out how the funds are going to be transferred into our Open Collective. Thank you very much FLOSS/fund, we will put this to good use to drive postmarketOS and Linux on Mobile development forward! An ## postmarketOS in 2025-09: PCB v0.2, Tauchgang, immutable, cellbroadcastd, pmb 3.6.0, ppc64le, SM7150 overhaul DevFeed: [postmarketOS in 2025-09: PCB v0.2, Tauchgang, immutable, cellbroadcastd, pmb 3.6.0, ppc64le, SM7150 overhaul]() Original publisher: [Read original article]() Published: 2025-10-12T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [systemd](), [Kernel](), [Development](), [Qualcomm](), [engineering-culture](), [Rust]() Tags: [code-review](), [culture](), [kernel](), [linux](), [postmarketos](), [qualcomm](), [rust](), [smartphones](), [systemd]() ### AI overview A postmarketOS development update covers recent work on mobile Linux, including the Tauchgang project, systemd maintenance, Qualcomm SM7150 devices, kernel and U-Boot development, Rust musl support, community office hours, and code review guidelines. ### Source excerpt Welcome to the latest edition of what happened in the last (two) months of postmarketOS development! This time we kick it off with a photo of a Xiaomi Mi 9T running the new Tauchgang project, more on that below. It was taken at BTO7, one of the many events where we hung out lately. Others include XDC, Datenspuren (pmOS flashing stand, pmOS talk, Linux on smartphones talk), KDE Akademy 2025, FrOSCon 20 (FOSS on mobile stand, pmOS talk), WHY2025, and DEF CON 33. Thanks to all who attended and represented postmarketOS and Linux Mobile there! Organizational Jane stepped down as Trusted Contributor. She has done a lot of great things in Alpine (e.g. maintaining Phosh there for some time) and postmarketOS. Most notably she made the very first systemd proof-of-concept and played a huge part in getting it all the way to the v25.06 stable release of postmarketOS. Jane has been maintaining systemd in postmarketOS for all this time, ensuring new versions land, hunting down bugs, doing some of the musl-related patches upstreaming, adjusting other packaging to have it nicely work together, etc. Thank you very much! Aelin is our newest TC! She is maintaining Qualcomm SM7150 devices, doing Kernel development and U-Boot bringup, making more devices boot generic images and even improving musl support in the Rust compiler. Furthermore she runs a monthly mainlining meetup at the CCCAC that you should definitely check out if you are in the area. Welcome to the team! Pablo joined Clayton with setting up office hours, but with his own focus "on non-technical aspects and listen to people about their feedback and frustrations". If you want to talk about that, join his weekly Jitsi call with your browser. Thanks, Pablo! Clayton has been working on postmarketOS full-time for about 1.5 years! "But this story really starts a bit earlier, when I realized I couldn't keep splitting my attention between a job I loved and a side project that had grown into an obsession. Once I finally admitted that ## postmarketOS clarifies its Code of Conduct Team and conflict-handling processes DevFeed: [postmarketOS clarifies its Code of Conduct Team and conflict-handling processes]() Original publisher: [Read original article]() Published: 2025-09-07T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [Maintainers](), [Open Source]() Tags: [accountability](), [communication](), [community](), [maintainers](), [open-source](), [postmarketos](), [team]() ### AI overview The postmarketOS Code of Conduct Team explains its purpose, updated enforcement guidance, conflict-of-interest handling, and confidential reporting process. The post describes the team's move toward clearer accountability and documented procedures for resolving community conflicts. ### Source excerpt The postmarketOS CoC (Code of Conduct) Team was established late last year, it is made up of myself (Casey), Oliver, Luca, and Bart. Other than being open source maintainers, none of us had much experience or training to deal with actual conflicts, and we had not developed any proper processes describing how we deal with issues. The potential fallout from poorly handling a conflict is huge, and it's our responsibility to prevent that from happening by ensuring that issues are dealt with timely and fairly, and are communicated effectively to all parties. Historical team structure Before the CoC Team, interpersonal conflicts were typically handled by the Core Contributors, operating in good faith to try and resolve issues. While this is typically acceptable for small projects, there is zero accountability and lots of potential for miscommunication especially as more people are involved. The CoC email address help@postmarketos.org was originally set up as an alias to the infrastructure team. Additionally, very little communication was made about the creation of this early CoC pseudo-team, and as a result we believe the CoC Team were viewed as a "last resort" for the community, a major oversight on our behalf. The new team The new CoC Team has been around for a while but we are writing this blog post to clarify our purpose and provide additional context. The exact nature of the CoC Team and processes we follow can now be seen on the updated enforcement section of the CoC page and the new CoC Team: Processes and Guidelines page. We have taken a lot of inspiration from the Freedesktop constitution, as their CoC Team have well established and documented processes. We have been careful to be explicit about dealing with conflict of interest situations and the confidential nature of CoC reports. Stating the obvious The CoC Team are here to help the community, if you feel as though someone has behaved in a way that violates the CoC, either towards you or someone else, please d ## New financed postmarketOS project: wireplumber and callaudiod DevFeed: [New financed postmarketOS project: wireplumber and callaudiod]() Original publisher: [Read original article]() Published: 2025-08-17T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Pipewire](), [Linux](), [Mobile]() Tags: [audio](), [automate](), [community](), [integrate](), [linux](), [mobile](), [money](), [music-player](), [plugin](), [postmarketos](), [project](), [routing](), [speakers](), [support]() ### AI overview postmarketOS is funding a EUR 6,400 project to replace callaudiod with a WirePlumber plugin. The work aims to integrate phone-call audio routing into the PipeWire and WirePlumber stack for Linux mobile devices. ### Source excerpt Since May, we had already received more money in donations than we had budgeted for the whole year. As stated in our latest budget, our goal for this year is not to save the money, but to put it to use. Therefore, the postmarketOS team decided to amend the budget to add a project expense of 6400EUR for audio-related work. We decided on the topic and amount for the following reasons: Audio is one of the important focus areas of the project, and one where we set ourselves to support the community through this year. It is also one of those areas where expertise is scarce, and having economic support can make a considerable difference. We found a potential project that the Linux Mobile community was looking for to solve for a long time, and a potential candidate available on short-notice with the skills to do the job. The scope of the project fits roughly the excess income we had available compared to our budget, and that made up for the final 6400EUR decision. The project: replacing callaudiod with wireplumber plugin callaudiod was started by Arnaud, the Mobian founder and one of its main contributors, as a way to automate routing changes for phones calls. This basically means that as you are listening to music on your device, and you receive a phone call, the phone automatically changes audio sources so that the speakers play the audio coming from the modem, instead of from your music player. It was designed to work within the PulseAudio stack, since it was the most mature solution at the time. However, Pipewire and Wireplumber have improved considerably since then and they are universally agreed as the future (and sometimes present) of audio on Linux. Unfortunately, the callaudiod solution is lacking in many ways when interacting with this stack. Therefore, more than a year and half ago, Arnaud opened an issue to discuss a way forward that would integrate audio routing in Pipewire+Wireplumber. Such solution would not require callaudiod, resolving all kind of issues. On t ## postmarketOS in 2025-07: Fairphone 6, apk3, /usr merge, immutable, new plasma camera DevFeed: [postmarketOS in 2025-07: Fairphone 6, apk3, /usr merge, immutable, new plasma camera]() Original publisher: [Read original article]() Published: 2025-08-03T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Kernel](), [Mobile](), [reliability](), [releases]() Tags: [computers](), [contributors](), [infrastructure](), [kernel](), [linux](), [mobile](), [postmarketos](), [releases](), [reliability](), [team]() ### AI overview A July 2025 postmarketOS update reports a new Fairphone 6 port, Linux patches, new contributors, funding for audio-stack reliability work, GNOME Advisory Board membership, and progress on mobile Linux infrastructure and VoLTE support. ### Source excerpt Let's start with this amazing photo that Luca took of the Fairphone (Gen. 6) showing the brand new postmarketOS port. Like with Fairphone 4 and 5 before, he published it on release day of the new Fairphone, this time along with 59 (!) patches to upstream Linux! Below the phone you can see a new sticker pack that Ranny, dikasp, Oliver and Luca made for the upcoming FrOSCon 2025 event and many events after (!65, !66, until they run out, of course)! Organizational We have two new Trusted Contributors: Rudraksha and Paul! Among other things, Rudraksha is working on mainlining MSM8960 while Paul is doing a port to the BlackBerry KEY2. Welcome to the team! It is only July, but we have already made more than 100% of the whole year's planned income via donations! With that in mind, the team has unanimously approved an amendment to our budget for spending 6400EUR to improve the reliability of the audio stack. As Pablo wrote in the "implementing missing bits to improve phone call routing" issue pipewire#3704: "So after talking with Arnaud, we are paying Richard Ac., a member from our community and maintainer of the close-to-mainline kernel for the Pixel 3a, among many other things, to try do this work and get it upstream.". There will be a separate blog post on this topic. Thanks to Richard Ac., Pablo, Arnaud and everybody who donated to postmarketOS to make this possible! From GNOME's 2025-07-12 Foundation Update: "We are excited to announce that postmarketOS has joined the GNOME Advisory Board! This is particularly fun, because it breaks GNOME out of its safe shell. GNOME has had a complete desktop product for 15 years. Phones and tablets are the most common computers in the world today and the obvious next step for GNOME app developers. It's a long hard road to win the mobile market, but we will. 🙂 (I'm just going to keep saying that because I know some people think it's extraordinarily silly... but I do mean it.)" A good chunk of the work in postmarketOS is fueled by NLnet an ## postmarketOS v25.06 adds systemd and updates mobile user interfaces DevFeed: [postmarketOS v25.06 adds systemd and updates mobile user interfaces]() Original publisher: [Read original article]() Published: 2025-06-22T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [systemd](), [releases](), [Linux](), [Mobile](), [User Interfaces]() Tags: [linux](), [mobile](), [postmarketos](), [releases](), [systemd](), [user-interfaces]() ### AI overview postmarketOS v25.06 introduces systemd, targets Alpine Linux 3.22, and updates its mobile user interfaces, including GNOME, KDE Plasma Mobile, and Phosh. ### Source excerpt This release is geared mainly towards Linux enthusiasts. We are working hard on stability improvements and automated testing, but if you expect Android or iOS levels of polish, then this is not for you yet. Introduction 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. Thanks to Jane, Casey, Clayton, Achill, Jakub, Bryant, Stefan, Bart, Pablo, Oliver, Robert M., Alexey M., Alistair, Devin, Aster, George, Luca, Bhushan, Dylan, Henrik, bjorn3, David H., Aelin, Federico, Ferass, Sam and everybody else who has helped with making this possible. It was truly a team effort! Software Stack As always we target the most recent Alpine release. In case of v25.06 it is the excellent Alpine Linux 3.22. User Interfaces (UIs) Mobile UI Versions GNOME 48 and gnome-shell-mobile 48.mobile.0 replace GNOME 47 and 46-mobile.1 from v24.12. With the new versions we get massive performance improvements with dynamic triple buffering and more, new fonts, notification stacking, window placement and input improvements and much more. Thanks to Jonas, Achill and all the GNOME contributors! KDE Plasma Mobile 6.3.5 replaces version 6.2.4 from v24.12. This release has improvements for the task switcher, window placement, action drawer, quick settings, status bar, volume controls, manual screen rotation, a new traffic monitor in the Wi-Fi settings and major bug fixes regarding the lockscreen and dual-sim devices. The new chat page has gotten new UX as well. See the recent dev log post for details (search for 6.3). Thanks to Devin, Bhushan, Luis, Micah, Vlad, User8395, Sebastian K., Bart and all the KDE contributors! Phosh 0.47.0 replaces version 0.45.0 from v24.12. Between these releases, Phosh has gained support for setting a lockscreen wallpaper (which we have enabled in pmOS), quick settings improvements, searching in the file chooser porta ## Creating QMI traces from Android phones with Frida to reverse engineer Voice over LTE DevFeed: [Creating QMI traces from Android phones with Frida to reverse engineer Voice over LTE]() Original publisher: [Read original article]() Published: 2025-06-17T00:00:00Z Content type: tutorial Language: en Sources: [postmarketOS Blog]() Topics: [Android](), [Qualcomm](), [Protocol (disambiguation)](), [Linux]() Tags: [android](), [frida](), [postmarketos](), [qualcomm]() ### AI overview A technical post on investigating Qualcomm-based Android phones' Voice over LTE stack through the QMI interface. It discusses QMI services and transports, limitations of Qualcomm Diag tooling, and using Frida to capture QMI messages from a running process. ### Source excerpt This is a guest blog post by Alexander 'lynxis' Couzens, one of the people behind the OpenIMSd NLnet project funded by NGI Zero Core. At postmarketOS we helped them create a grant proposal, and continue helping with project planning. For more details, check the project website. We thank NLnet and the NGI Zero Core fund for supporting this initiative. Introduction To investigate how the Voice over LTE stack in Qualcomm based phones works, I have to look into the QMI interface. QMI is a structured interface using TLV. Furthermore, QMI is a protocol which can be used over different interface and offers communication between services. A service usually handles a logical component of the baseband, e.g. the communication with the simcard is handled by the UIM (User Identity Module). Or the NAS handles the high level Network Access. QMI also supports multiple clients at the same time. It allows two daemons to communicate via QMI at the same time without the need to synchronize with each other. QMI supports at least communication over the following transports (not a full list): USB (e.g. mini-pcie) Shared memory (SoC) Socket (kernel socket class, but internally over shared memory) Tunneled over Qualcomm Diag To research the QMI VoLTE messages of a stock Android, we need to able to capture those messages. When I first encountered QMI and researched how the "legacy" voice calls are working on Qualcomm based phones, I used Qualcomm Diag for it using the osmo-qcdiag project. Sadly osmo-qcdiag only supports Qualcomm Diag when exposed as TTY on Linux via /dev/ttyXXXX, but not (as many other projects by now) directly via USB without a kernel driver. The issue with the kernel driver is the limited support of devices. When enabling Qualcomm Diag for a new phone, it requires a small patch to add the USB ID to the driver. Other projects like SCAT or QCSuper can use libusb to directly communicate with the phone. Because of this I tried to add QMI sniffing in SCAT, but it didn't work wi ## postmarketOS in 2025-05: Continuous testing, downstream split, niri, os-installer DevFeed: [postmarketOS in 2025-05: Continuous testing, downstream split, niri, os-installer]() Original publisher: [Read original article]() Published: 2025-06-02T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [free software](), [Wayland]() Tags: [free-software](), [linux](), [mobile](), [postmarketos](), [wayland]() ### AI overview A postmarketOS update covers mobile Linux activities, community events, talks, contributor changes, and related projects including KDE Plasma on mobile devices and Wayland. ### Source excerpt Two months after the last "monthly" blog post, it's time for another double-feature. We have a lot to talk about, but let's start with what you can see in the header image. At the center is fdlamotte's Pixel 3a running SXMO and it is connected to... a G-Shock B2100! He wrote a great blog post showing how he sends notifications to the three-character-screen on the watch as well as configuring the watch (alarms etc.) from SXMO menus. In three corners we have photos from events. The top left one is from the Plasma Sprint 2025 that took place in Graz, Austria, "co-hosted with Grazer Linuxtage where we had a KDE booth on Saturday. We show-cased KDE Plasma running on SteamDeck, Krita with drawing tablet support on Wayland, HDR support and of-course Plasma Mobile running on OnePlus 6" as Bhushan writes on his blog. Devin and Luis were there as well and wrote separate posts. Another event in Austria was the permacomputing & postmarketOS residency (photo bottom left) from Chaline. In Argentina, the FLISoL (Latin American Free Software Installation Festival) took place where Val held a talk "Sustainability and sovereignty in your pocket with postmarketOS". She writes in #6: "It was great! There was no recording, but I could share the audience selfie I took with the motorola-nora I brought with me :D It's lower resolution than the front camera itself due to pipewire/snapshot shenanigans, but let's say its lo-fi quality in general is a privacy measure designed to thwart facial recognition :p" Speaking of talks, Pablo also did one called "postmarketOS: opportunities and challenges of a mobile-first platform" at Linux App Summit and he was interviewed by the Association for Progressive Communications (APC) along with Clayton and Oliver. Organizational We have two new Trusted Contributors: Ranny and Hugo B.! Ranny is a designer, art creator, and has helped with the website, e.g. writing an initial version and providing artwork for the contribute page. He is also our first TC without [Next page]()