To the contrary, PureOS benefits a lot from (and improves upon) work made by Mobian and postmarketOS communities. In the past, this worked both ways and the work done on PureOS was benefiting everyone else as well, to the point where I would consider PureOS to be perhaps the biggest driving factor in this space. This hasn’t been the case for a while now, as PureOS hasn’t been receiving much development for some time and ended up being quite a lot behind, for several reasons. Since the development resumed, we’ve been mostly playing catch-up, but most of it is already done by now and I’m pretty hopeful that PureOS could start playing one of the leading roles once again in some foreseeable future.
(though even in my recent work on Crimson I’ve managed to fix some bugs in some components that were still relevant in their latest upstream versions, so it’s not just 100% catching-up )
I already consider Crimson to be daily driveable - I use it on my own phone which I’ve upgraded from Byzantium about two months ago. The remaining issues are pretty much cosmetics and a good chunk of them I already have resolved locally and is now waiting to be packaged and uploaded.
As it is right now, PureOS Crimson definitely provides a much better experience than either PureOS Byzantium or Debian (Mobian) Bookworm. It’s a pity that it took so long to get it there, but it finally happened. Of course, it’s 2025 (almost 2026) now and Crimson being based on Bookworm means that it’s still behind. It’s hard to compare the user experience between Crimson and Trixie right now, as Trixie comes with multitude of improvements from both Debian and various upstream projects, but also brings in many regressions when compared to Crimson when used on the Librem 5. The future work will be focused on making sure Dawn won’t inherit those, so it can provide experience that’s strictly superior to both PureOS Crimson and Debian/Mobian Trixie.
Depends on what you exactly mean by that. Dawn is already in a better shape than Crimson was for ~90% of its existence. It will still need some work to consider it daily driveable and releasable.
I don’t expect Dawn to drag out anywhere as long as Crimson did, but I also don’t see why one wouldn’t switch from Byzantium to Crimson already but rather wait for Dawn. I believe in Dawn coming out “pretty soon”, but it sure won’t be here in a week or two
I’m not sure when the last published images are from. If they’re fresh enough (or you build your own fresh one), then no.
Last stable Crimson is from August and it’s still definately alfa version using old packages and not updatable. You may have good time with crimson but most haven’t seen that..
Do you foresee any big hurdles in getting Dawn to the daily driveable state?
Edit:
In the interest of also keeping my post on topic to the thread…
I’m still going strong 2.5 years in. Thanks to the unofficial backports, I’ve been in a pretty comfortable state for a while. Sure there are some problems and I want newer software, but the phone itself still works for me.
Kinda messed up that it gets flaunted but there’s no announcement, no thread, no how-to - everyone else just hears these rumors and are left out while not knowing how to do this magical upgrade (byz nor crim do not offer it). No wonder this is so off putting that people are leaving.
The biggest is GTK4’s renderer requiring GLES3. We may also use this opportunity to attempt switching to PipeWire, which will require work to not break echo cancellation for voice calls. Many patched packages need to be rebased and updated - not really “hurdles”, but work to do nevertheless. Other than that - we’ll see. I never booted into Dawn on any of my phones yet - but I’ll have to do so soon
Short guide: switch the repos and do sudo apt full-upgrade.
Detailed guides and automation scripts still need to be written, which is why you don’t see announcements and how-tos yet. But if you’re capable of upgrading your Debian desktops and dealing with usual issues that may arise there, you can already do that with your phone as well.
That’s the thing. Assuming most can. It’s pretty much gatekeeping and keeping most L5 users away from crim. Those kinds of short guides are not the bread crumbs that most are able to follow.
Your point was that it’s “kinda messed up” that it’s not being widely announced as already usable, so I told you that it’s not being widely announced because the detailed guides for people who aren’t technical enough to manage the upgrade on their own aren’t written yet. So yes, I’m perfectly aware of that.
@dos what about, Lnx 6.12 for Crimson or Dawn?
Redpine 2.6.1 driver support for Lnx 6.6 or 612?
The things is that rsi mainline may not work without firmware as i thinking…as i not tested either.
The redpine driver that do not need firmware is not on mainline.
Can you explain me.
My Redpine module it has 2.5 firmware burned, it work nice, however looks like it need 2.5 driver, but my dream is 2.6.1 driver with 2.6.1.rps
However i pretty sure that 2.5 driver need some work for Lnx6.6
Forward-porting our kernel tree to at least 6.12 will be an important part of moving towards Dawn, yes. It shouldn’t be a blocker for other tasks though.
Hah, I just now upgraded to Crimson. Most everything seems to work except for GNOME Keyring which Authenticator cannot unlock the Login key chain for. Nice!
)
