Byzantium backports unofficial

shak · November 22, 2024, 8:12am

So can you confirm that alarm works now on Purism when phone is on suspend ?

galilley · November 22, 2024, 8:30am

Yes, it works!
I will try @guido.gunther 's branch soon to change the alarm sound

p.s. be careful if decided to apply my backports. It works for me, but @ASwyD2 has a problem with boot after upgrading. Looks like it is better to use apt install ./*.deb' rather than apt dist-upgrade` and remember that you should NOT be asked to remove some critical packages.

galilley · November 22, 2024, 8:03pm

Mesa 24.2.4 - Epiphany works much better with some websites. I’m able to take a taxi and look to online maps from my librem5 for the first time ever!

galilley · November 22, 2024, 8:20pm

Amazing!
I’ve just apply three latest commits from the branch to gnome-clocks 47 and voila - custom sound and haptic works! Just copy your sound as ~/.local/share/sounds/__custom/alarm-clock-elapsed.oga

There is the minor issue - I can not change the sound profile for the clocks, only global profile does matter (silent, vibro, full). It will be also very nice to keep a sound only (without haptic).

p.s. repo is already updated!

spacemanspiffy · November 23, 2024, 3:26am

I just updated and…

The good:
Holy crap it’s WAAAY snappier, and it fixed some of the window sizing issues I had before (ex the Timer screen in Clocks was always too wide).
Pages that took 20-30 seconds or more to properly load in FF now load instantly. What the hell happened here ???

~~The bad:~~
- I have no sound, and I cannot playback audio or video. I tried Lollypop, Freetube, and videos in Firefox. No media will play, and I don’t get any sounds from the system. Even testing speakers in the GNOME Settings will not work, the buttons are disabled.
~~- Phone calls connect, but I cannot hear the other end and they could not hear me.~~

~~I just hope to be able to resolve whatever I have missing. Please if you have suggestions~~

~~Relevant log statements:~~
> Nov 22 22:36:31 voyager pulseaudio[1479]: Failed to create sink input: sink is suspended.
Nov 22 22:36:31 voyager gnome-control-c[2338]: Failed to play sound: Invalid state

~~After renaming ~/.config/pulse…~~
> Nov 22 22:49:29 voyager pulseaudio[1467]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Nov 22 22:49:29 voyager pulseaudio[1467]: Most likely this is a bug in the ALSA driver ‘snd_soc_simple_card’. Please report this issue to the ALSA developers.
Nov 22 22:49:29 voyager pulseaudio[1467]: We were woken up with POLLOUT set – however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Nov 22 22:49:29 voyager pulseaudio[1467]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Nov 22 22:49:29 voyager pulseaudio[1467]: Most likely this is a bug in the ALSA driver ‘snd_soc_simple_card’. Please report this issue to the ALSA developers.
Nov 22 22:49:29 voyager pulseaudio[1467]: We were woken up with POLLIN set – however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Nov 22 22:49:30 voyager pipewire[1465]: spa.alsa: ‘hw:1,0’: capture open failed: Device or resource busy
Nov 22 22:44:47 voyager wireplumber[1472]: spa.alsa: Error opening hctl device: No such device
Nov 22 22:49:32 voyager pipewire[1465]: spa.alsa: ‘hw:L5’: capture open failed: Device or resource busy

Final edit:
@galilley ignore me… and THANK YOU!!!
I am exhausted from a long week and I don’t know what the hell I did to fix it. Maybe renaming ~/.config/pulse did it, maybe something else. But I now can play back video and get audio too.

Final final edit:
Hmm… no. Audio didn’t work with my BT headphones, and after a restart, I am back to the same state above where I crossed everything off. Either way I’m done for the night.

galilley · November 23, 2024, 4:23am

Just to confirm your issue with the sound :).

It may be related to pipewire, that should be configured for video-only streams. I believe it must be configured automatically in case you you do not install pipewire-pulse (not included into the repo), but something went wrong (as usual ).

So, try to reconfigure it by yourself (link):

systemctl --user disable wireplumber.service
systemctl --user enable wireplumber@video-only.service
systemctl --user status wireplumber@video-only.service

spacemanspiffy · November 23, 2024, 4:29am

Seems to have made no difference.
I don’t see pipewire-pulse in the repos to install. Related packages that I do have installed are:

gstreamer1.0-pipewire/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libpipewire-0.3-0/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libpipewire-0.3-common/now 1.2.5-1~bpo12+1 all [installed,local]
libpipewire-0.3-modules/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libspa-0.2-bluetooth/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libspa-0.2-libcamera/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libspa-0.2-modules/now 1.2.5-1~bpo12+1 arm64 [installed,local]
libwireplumber-0.5-0/now 0.5.6-1~bpo12+1 arm64 [installed,local]
pipewire/now 1.2.5-1~bpo12+1 arm64 [installed,local]
pipewire-bin/now 1.2.5-1~bpo12+1 arm64 [installed,local]
pipewire-libcamera/now 1.2.5-1~bpo12+1 all [installed,local]
pipewire-v4l2/now 1.2.5-1~bpo12+1 arm64 [installed,local]
wireplumber/now 0.5.6-1~bpo12+1 arm64 [installed,local]

I started seeing Failed to create sink input: sink is suspended. so I deleted ~/.config/pulse again… We will see.

Edit:
Before going to sleep I rebooted once more and… sounds works. Video playback works. I just tried my BT headphones again and they work!

Only one issue remains that I’ve noticed now:
When the phone goers to suspend, instead of the screen blanking, it drops to TTY and the screen stays on. I can share the message I see later.
I was still able to unlock by pressing the power button, then unlocking my disk, then going to the Lock Screen and unlocking from there.

guido.gunther · November 23, 2024, 4:30pm

There is the minor issue - I can not change the sound profile for the clocks, only global profile does matter (silent, vibro, full). It will be also very nice to keep a sound only (without haptic).

Maybe there’s something off in your stack? gnome-clocks is flagged as important so it is explicitly allowed to override the global feedback level (otherwise I’d miss my wakeup alarms when the phone is set to silent mode). This is used by clocks for alarms.

The user can drop gnome-clocks from the list of apps that are allowed to do that to get “normal” behavior (no alarms when phone is set to silent).

These patches are also part of the phosh nightly builds btw; Phosh Nightly Package Builds · Phosh

galilley · November 23, 2024, 6:50pm

May be some problem with cryptosetup-suspend (link) or old libraries like libphosh or mutter that may have remained in the system?..

galilley · November 23, 2024, 7:34pm

This exactly I observed right now - no sound when in the silent mode… My stack is follow:

libphosh-0.43-0/unknown,now 0.43.0-1 arm64 [installed]
phosh-antispam/unknown,now 3.5-1 arm64 [installed]
phosh-core/byzantium,now 5 arm64 [installed]
phosh-games/byzantium,now 5 all [installed,automatic]
phosh-mobile-settings/unknown,now 0.43.0-1 arm64 [installed]
phosh-mobile-tweaks/unknown,now 0.43.0-1 all [installed,automatic]
phosh-osk-stub-doc/unknown,now 0.41.1-1 all [installed]
phosh-osk-stub/unknown,now 0.43.0-1 arm64 [installed]
phosh-plugins/unknown,now 0.43.0-1 arm64 [installed,automatic]
phosh-tour/unknown,now 0.43.0-1 arm64 [installed,automatic]
phosh/unknown,now 0.43.0-1 arm64 [installed]
phoc/unknown,now 0.43.0-1 arm64 [installed,automatic]
feedbackd-common/unknown,now 0.5.0-1 all [installed,automatic]
feedbackd/unknown,now 0.5.0-1 arm64 [installed,automatic]
libfeedback-0.0-0/now 0.5.0-1 arm64 [installed,local]
gnome-clocks/unknown,now 47.0-2 arm64 [installed,automatic]

What else I could check to fix the issue? Where I could check that the important flag is really setted for the clocks?..
Thanks a lot!

Looks like the list of special apps that can override a global profile is fixed for me…

spacemanspiffy · November 23, 2024, 7:55pm

I have libphosh 0.43-0 and mutter 47.0-3 installed.
Are you suggesting to remove them?

I should probably add, I installed your .debs by apt install ./*.deb.
Doing this added in the full GNOME desktop, which I now have an option (not tested yet) to log in from greetd, which is also new. I am guessing that GNOME is why I have mutter installed.

galilley · November 23, 2024, 8:25pm

Your libphosh and mutter are Ok!
greetd is installed in my case just because it was mentioned as a related component, but I do not remember where…

p.s. when I told about old packages, I meant the versions older than the installed phosh version (0.43 for today).

guido.gunther · November 24, 2024, 2:46pm

Thanks. Just to give some context: That’s the version numbers of the some components but doesn’t tell me about the rest of the system nor the patches applied. There’s lots of stuff like libgsound, pa and others that come into play (and that’s only for feedback, it’s complete different story for e.g. call audio, emergency calls, …). There’s also lots of details that can be off in support packages like meta-phosh or mobile-tweaks (which Purism calls librem5-base and which targets way older Phosh). But If it works for you, great!

One thing: I’d try to avoid the ~bpo suffix as that is what Debian uses so you might clash with versions there, maybe switch to ~bpu for your next round of updates?

carlosgonz · November 27, 2024, 3:08am

Dear @galilley
I will pay you a Dulce De Leche Frappé from Mcdonalds for you great backports work. Can you share ur paypal?

galilley · November 27, 2024, 4:47am

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?

ASwyD2 · December 2, 2024, 4:14am

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.~~ Edit: Suspend is not working. It wakes up from it immediately
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

spacemanspiffy · December 2, 2024, 12:42pm

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 phosh version; 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)

Ick · December 2, 2024, 12:49pm

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.

galilley · December 2, 2024, 12:59pm

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?

spacemanspiffy · December 2, 2024, 10:45pm

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')