Dear, @carlosgonz , thank you soo much!
It is really nice! I’m just sharing the work that I do for myself… Moreover, I have problems with my paypal in the last few years, so, crypto is my best friend for international payments, but I believe it is a bit complicated for coffee, even for such a delicious one 
p.s. did you try to upgrade your system? Does it work?
So on a fresh slate I installed the debs using this ^ command. Everything worked except sound. To fix sound, I used:
This fixed the sound issue.
I also tested Gnome Clocks a little bit. It woke the phone from suspend 30 or 45 secs before the alarm went off.
I like the newest phosh version; lots of improvements.
Almost ready to use on my daily driver, but I have not tested sufficiently to put away my concerns quite yet.
Overall pretty good, but needs polishing from upstream 
I forget if I stated but those same commands also fixed my sound.
The only issue I have now is Suspend not working any more. I gave up on that and turned Suspend off, and will probably just flash Crimson once it’s available and reset everything at that time.
I like the newest
phoshversion; lots of improvements.
Agreed. It’s really SO good right now. I’m excited for the even newer Chatty and Phosh versions as well (not in these backports)
One of the reasons I do not play with unstable software on my daily driver. Suspend and stable system is more important to me than new improvements on other things. And I know how cool some stuff is, since I use it on Mobian test system.
In fact it works well for me when I apply a workaround for my luks partition on sd-card.
@spacemanspiffy do you have some stuff on sd-card? could you show your logs just before suspend?
One of the reasons I do not play with unstable software on my daily driver
Yes I took a pretty big risk installing this on my DD. My plan if anytrhing went too wrong was to reflash back to regular Byzantium.
And that says nothing of the security implications of installing “some random guy’s” .deb files onto my phone rather than one from the distro.
Not to imply anything wrong on @galilley 's part, just that it generally is not good security practice.
But, I was attracted by shiny new toys :).
Yes, please see relevant bits from my fstab:
/dev/sda1 /mnt/sd ext4 errors=remount-ro,nofail,x-systemd.device-timeout=8 0 2
/dev/sda2 /mnt/media ext4 errors=remount-ro,nofail,x-systemd.device-timeout=8 0 2
# Bind mounts
/mnt/sd/flatpak /home/purism/.var none bind 0 0
#/mnt/sd/waydroid /var/lib/waydroid none bind 0 0
/mnt/sd/camera /home/purism/Pictures/camera none bind 0 0
/mnt/sd/projects /home/purism/projects none bind 0 0
The partitions on the SD are not encrypted.
Here is the output of journalctl -f after pressing Suspend from the Phosh Quick Settings power menu.
Dec 02 17:42:19 voyager gsd-power[1796]: Couldn't hold power-saver profile: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.hadess.PowerProfiles was not provided by any .service files
Dec 02 17:42:20 voyager systemd[1399]: app-gnome-ffapp\x2dmessenger-3105.scope: Consumed 10min 44.414s CPU time.
Broadcast message from neil@voyager (Mon 2024-12-02 17:42:25 EST):
The system will suspend now!
This time - it worked, sort of. The screen stayed on. After pressing the power button, I was presented with the LUKS decrption screen. After this it brought me to the Phosh Lock screen.
Sometimes it does this, sometimes it just plain doesn’t respond while suspended. ( I have a post above where I stated this happened, but more often than not, it fails to resume, hence why I just turned Suspend off)
Here are some of the logs printed after resuming:
Dec 02 17:42:25 voyager systemd-logind[739]: The system will suspend now!
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8662] manager: sleep: sleep requested (sleeping: no enabled: yes)
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8676] device (usb0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 02 17:42:25 voyager waked[934]: Checking alarm for suspend ...
Dec 02 17:42:25 voyager waked[934]: Rescedule...
Dec 02 17:42:25 voyager ModemManager[904]: <msg> [sleep-monitor-systemd] system is about to suspend
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8777] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 02 17:42:25 voyager systemd-networkd[498]: usb0: Link DOWN
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8826] manager: NetworkManager state is now ASLEEP
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8839] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Dec 02 17:42:25 voyager NetworkManager[684]: <info> [1733179345.8930] device (cdc-wdm0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Dec 02 17:42:25 voyager dbus-daemon[678]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=684 comm="/usr/sbin/NetworkManager --no-daemon ")
Dec 02 17:42:26 voyager systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Dec 02 17:42:26 voyager dbus-daemon[678]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 02 17:42:26 voyager systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Dec 02 17:42:26 voyager wpa_supplicant[809]: wlan0: CTRL-EVENT-DISCONNECTED bssid=14:cc:20:67:d5:0a reason=3 locally_generated=1
Dec 02 17:42:26 voyager systemd-networkd[498]: wwan0: Link DOWN
Dec 02 17:42:26 voyager systemd-networkd[498]: wwan0: Lost carrier
Dec 02 17:42:26 voyager systemd-networkd[498]: wlan0: Lost carrier
Dec 02 17:42:26 voyager wpa_supplicant[809]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 02 17:42:26 voyager systemd-timesyncd[631]: No network connectivity, watching for changes.
Dec 02 17:42:26 voyager NetworkManager[684]: <info> [1733179346.1326] device (wlan0): supplicant interface state: completed -> disconnected
Dec 02 17:42:26 voyager NetworkManager[684]: <info> [1733179346.1415] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
I’m totally agree with you! 
However, for example, when I used a custom Android ROM in past it looks much better that the official one with a lot of preinstalled adware stuff and no control of permissions. So, I decided to use a ROM from a stranger and I understand the risks of security implications. Here the situation is pretty the same… Of course, you should not blindly trust anyone, but I’m sure that it’s better when there is a choice ;). I hoped that it will be much easier to make a backports for Crimson, so I could share some howto about it to someone could reproduce it by himself.
Me too (on my PC), but here, on the mobile, I see a huge difference between the official repo and latest (unstable) versions (online contacts and calendar sync, imap mail, usability, new phosh features and so on). All of these are important for my daily use. Moreover, you become capable to provide a feedback for upstream!
The my one is a little bit different but it shouldn’t matter:
UUID=xxx /mnt/storage ext4 errors=remount-ro 0 1
/mnt/storage/flatpak/repo /var/lib/flatpak/repo auto bind 0 0
Everything looks fine… What about the kernel? I use the latest one (6.6.57pureos1~byz1). Could you show the output of the next commands:
$ uname -a
$ apt list --installed | grep linux-image
Not yet. Have you backported GTKLib for Byz?
Linux voyager 6.6.0-1-librem5 #1 SMP PREEMPT Mon Oct 28 12:21:18 EDT 2024 aarch64 GNU/Linux
...
linux-image-6.5.0-1-librem5/now 6.5.13pureos1~byz1 arm64 [installed,local]
linux-image-6.6.0-1-librem5/byzantium-updates,byzantium-updates-proposed,now 6.6.57pureos1~byz1 arm64 [installed]
linux-image-librem5/byzantium-updates,byzantium-updates-proposed,now 6.6.57pureos1~byz1 arm64 [installed]
Which one exactly?
$ apt list --installed | grep libgtk
...
libgtk-3-0t64/unknown,now 3.24.43-4 arm64 [installed]
libgtk-4-1/unknown,now 4.16.5+ds-2 arm64 [installed,automatic]
libgtk2.0-0/byzantium,now 2.24.33-2+deb11u1 arm64 [installed,automatic]
...
Sorry. I mean Libgtk4
Looks like updated. Thanks 
Exactly the same kernel…
Why you see the LUKS decrption screen after resume?.. It must show up only on the boot time. After resume you should see only the Phosh lock screen. May be you try to suspend your root luks partition?
I just tested suspend and it crashed phosh
Edit: and sound is not working again
I really have no idea about the roots of suspend issue, and I have no time right now to try a clean upgrade on my phone, sorry…
@ASwyD2 , @spacemanspiffy are you upgrade the fresh flashed image? What image exactly did you use? I will try to reproduce on the Christmas holidays, I hope.
No I am not. I traded my spare phone with my brother because of a broken screen, so I just installed the backports on top of that. I reflashed that in August of this year
are you upgrade the fresh flashed image? What image exactly did you use?
Nope.
Just the most recent updates from byzantium and byzantium-updates-proposed. Otherwise, it’s what came flashed on the phone from Purism.
I installed the first round of updates with sudo apt dist-upgrade.
I then took your most recent debs and did sudo apt install ./*.deb, after removing a few I know I don’t use (like KDE Connect, for example).
Very similar to my case…
What about LUKS decrption screen after resuming? It is some thing that should not happen.
Unfortunately phone got borked. What i did and maybe that was incorrect:
cd /home/purism/Downloads
git clone https://codeberg.org/galilley/librem5-byzantium-backports.git
sudo nano/etc/apt/source.list
add 'deb [allow-insecure=yes] file:/home/purism/Downloads/librem5-byzantium-backports ./
sudo apt update
sudo apt upgrade (this upgraded some packages, and seemed to run fine and maybe snappier)
sudo dpkg -i *.deb (this failed due to too many errors and it couldn’t update the initramfs)
Probably shouldn’t have tried to install all *.deb packages in folder?
Are you supposed to only run?:
sudo apt install geary folks-common chatty gnome-calls gnome-contacts gnome-calendar gnome-maps gnome-books gnome-authenticator phosh phosh-osk-stub linux-kernel-6.6.34
In my experience,
sudo apt install ./*.deb
ran first was the best course.
Disclaimer: go through the folder and remove the packages you don’t want. eg. 'pidgin, telegram, tigerVNC, etc
aaahh ok thanks!