I have not extensively tested the running time, but I do know enough about my current practices.
On my Librem 5 USA, I use the lowest brightness most of the time, only permit Wi-Fi, and use Firefox ESR to interact with the Purism community forums. In the Settings app, as shown in the screenshot at the beginning of this thread, I use the “Balanced” Power Mode, but do not enable suspend. Based on this configuration, every 1% of battery life is equivalent to 4 minutes, which in practice, becomes a total runtime of 6 hours and 40 minutes. I take frequent breaks throughout the day so that I can extend the usage of my Librem 5 USA and achieve a holistically balanced lifestyle.
Do you know if they’ve fixed that issue involving the wrong date being displayed at midnight. The date only updates at one minute after midnight, but this issue only affects the Notification List drop down, not the Lockscreen.
I have been getting /boot is running low on space banners after startup, so I decided to reflash my Librem 5 USA with Byzantium. My experience with Crimson has been fine, and it is very close to being my daily driver, but I will be demonstrating my Librem 5 USA to the public soon and need the hardware kill switches and related modules to reliably work on demand. After the demonstration, I have enough positive experiences with Crimson to consider reflashing it again.
A minor annoyance on Crimson was only being able to install one Flatpak application (Secrets), but not having enough space in /var for the other two Flatpaks I use: Lollypop and Shortwave. I decided early on to use Crimson for productive purposes, so while I was successful in proving such, I did not catch a break throughout.
I never found out, but based on the research I did during that time, plus my experience just before reflashing back to Byzantium, I am highly confident that both /var and /boot are much smaller partitions on Crimson than Byzantium. There may be other partitions I am not aware about that share this trait.
Plenty, but the main reason is that I appreciate a clean, untampered slate to work with.
No, I have never used Bluetooth on my Librem 5 USA since I bought it.
On Byzantium I actually have a major bug (some time later I realized it also happens with USB) that prevents my device from using W-Lan and from shut down actions (7s power-off button works). It’s maybe fixed on Linux 6.6, but I can tell more when it arrives (and I think it will on Byzantium). So there is also a chance that it improves other things, too. So let’s wait for next kernel update.
Yes, trying to upgrade from one major version to the next major version (for any Linux distro) when the distro hasn’t specifically provided for that can lead to a mess.
This is doubly so when crimson hasn’t even been released yet !
It is always going to guarantee a cleaner result to flash from scratch, albeit that it is painful to have to reestablish additional installed packages, system config, user config, user content, …
That said, reflashing is probably not the right approach for /boot becoming full. The right approach is probably to manually uninstall excess packages and/or investigate what is using the space.
df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 461087 191921 245358 44% /boot
So that means that /boot has been allocated about 450 MiB (472 MB).
Each kernel version seems to be about 96 MB, so I would not have more than 2 kernel versions (except during a kernel upgrade, when I will temporarily have 3).
PS On my phone /var is on the root file system so df / is the answer for that but, unless your disk is actually basically full, there shouldn’t be a problem with /var
For what it’s worth, (I don’t want to jinx it, but) there has been exactly zero BT audio stuttering for me since the upgrade to 6.6.0-1-librem5 on my L5 a few days ago.
Kernel upgrades in the past haven’t made many huge changes but I swear things improved (not just BT) since the 6.6.0 update.
Sounds good. I really want to try it out, but I want to stay on stable Byzantium until Crimson release is also stable. The only reason I restart my ppc is that usb/bt bug.