Yes
Everything seems to line up with my DD.
8.8.8.8 pings just fine. As does 0.0.0.0
I did that and nothing changed.
Yes
Everything seems to line up with my DD.
8.8.8.8 pings just fine. As does 0.0.0.0
I did that and nothing changed.
Please try to check if systemd-resolved
has been installed and other systemd- related packages, located in the archive, too.
systemd-container
can also be required by waydroid, I’ve forgot the list of the new packages that must be installed manually…
@ASwyD2 , @spacemanspiffy , could you check gnome-calls
when calling to short numbers (3 or 4 digits)? It stopped to work for me and I can not understand the reason…
gnome-calls 46.3-1 arm64
(my current version)…
The only “short” numbers I could think of was 911 and 411… I tried calling 411 right now and a machine picked up on the other end asking for my city and state.
So I think it’s safe to say that “short” numbers are working for me.
The people told me that the problem depends on an operator and mode of the network. Short numbers could fail in 4G but should work in 2G/3G mode, and it really works for me!
Did I read correctly that you have Phosh 0.43 in your backports?
Sidenote: On your Codeberg instance, how would I download all the files in one zip?
Could someone who knows such things teach?
Edit: @galilley , you should create a read.me
to tell people how to use your packages.
Thanks for your work
With git tools installed:
git clone https://codeberg.org/galilley/librem5-byzantium-backports.git
The link is available to copy from codeberg page. It copies you the folder and all containing files without zip. You also can use the web-GUI and hit right to the link I spoke before on the ...
button - everything else is self-explanation.
And Phosh-version is 0.43, not 43.
ZIP:
https://codeberg.org/galilley/librem5-byzantium-backports/archive/main.zip
TAR:
https://codeberg.org/galilley/librem5-byzantium-backports/archive/main.tar.gz
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
…
Have you had any luck resolving this issue yet?
Manual installation of systemd-resolved
package should resolve the network issue :). But it is better to wait some independent confirmation
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)
It you have a problem during apt dist-upgrade
please send me the log in PM.
upd: I’ve lost one package, right now everything must be Ok!
p.s. be careful when upgrading! Make backups and/or second sd-card bootable os for inspection.
You could use this branch to make it use feedbackd which then allows theme configuration and also to use haptic.
So can you confirm that alarm works now on Purism when phone is on suspend ?
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.
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!
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!
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.