Gnome-clocks 47 is already available!
It is patched to use waked to resume the phone from suspend. libgtk-4 4.16.5 patched to avoid clock hangs when an alarm is triggered is also included.
The one thing that I can not change - the default alarm sound. No one advice works for me, even direct replace of the /usr/share/sounds/freedesktop/stereo/alarm-clock-elapsed.ogg…
This did solve that issue for me.
However, I still am not able to upgrade phosh yet, (I probably just need to keep installing packages until it finally works)
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.
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).
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.
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 ).
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.
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).
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.
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?