@GooglyBear I'll try... Hum. No, the pull don't have access to waydroid data folder. adb pull /home/phablet/.local/share/waydroid /home/phablet/.local/share/waydroid/: 0 files pulled, 0 skipped.

Could anyone that has that kind of issue remember the steps done ? e.g from 20.04 stable to 24.04.x daily, then back to 24.04.1 stable, then.... If there were remote calendars, etc...

@advocatux it's hard to stop myself from doing so sometimes XD

@Shapa Thank you! I hope the porter or maintainer will make it official/supported. Would be cool to have it in the installer!

@padraic For a next time, to verifiy the device, you must enable developper mode in system settings / System information. Connect the usb. Accept the connection on the phone. adb devices must show you your phone.

@gpatel-fr I am glad to say the SIM started working again: I rebooted without the SIM, and then with it again. I also recall the SIM was working the second time I booted UT for the first time ever on the phone (the first time I booted I'd forgotten to insert it). Hopefully it was just a temporary glitch and Fairphone 5 users running 24.04 stable are 'SIM-safe'.

@qrvhh Have you tried reloading the page after signing in? I don't think we really do have proper handling of login popup windows.

It does work better in 24.04-1.1 that it did in 24.04-1.0. I'm using google maps app from @chromiumos-guy If I open the app outdoor when I have access to my location it will usually work. BUT it will freeez/crash very easilly if I try to access the position when I don't have access to it (indoor) or that I click a second time on the position icon. Once it has crashed or freezed it will not work anymore until I reboot the phone.

@amazones Were you able to install any emacs packages? I really want to do PDF, HTML and audio annotation (bookmarks/highlights and comments) with emacs, but I would want it to work universally (not just on my desktop, but on my phone as well). Something else I would like to try is this: https://elpa.gnu.org/packages/kiwix.html

Is it a matter of version 3.4.1 in general or is the bug a matter of Focal or Noble version? Any idea?

For further digging I found An appArmor policy prevents from webapp-container expose MPRIS signal time=1764940153.079286 sender=:1.134 -> destination=(null destination) serial=19 path=/org/mpris/MediaPlayer2; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.mpris.MediaPlayer2.Player" array [ dict entry( string "PlaybackStatus" variant string "Paused" ) ] array [ ] error time=1764940153.079343 sender=org.freedesktop.DBus -> destination=:1.134 error_name=org.freedesktop.DBus.Error.AccessDenied reply_serial=19 string "An AppArmor policy prevents this sender from sending this message to this recipient; type="signal", sender=":1.134" (uid=32011 pid=19620 comm="youtube-web" label="youtube-web.mateo-salta_youtube-web_7 (enforce)") interface="org.freedesktop.DBus.Properties" member="PropertiesChanged" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (uid=32011 pid=15732 comm="/usr/bin/mpris-proxy" label="unconfined")" method call time=1764940153.084393 sender=:1.141 -> destination=org.freedesktop.DBus serial=8 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string "type='signal', path='/org/freedesktop/DBus/Local',interface='org.freedesktop.DBus.Local', member='Disconnected'" method return time=1764940153.084439 sender=org.freedesktop.DBus -> destination=:1.141 serial=9 reply_serial=8 is there any way we can configure app mirror policy ?

said in Enabling MAC randomization: Another could be to stop and disable the mount unit + restarting the phone when staying at home. I have finally decided to finish this matter and found a way to enable randomization (reenable the mount) while keeping the ability to connect automatically to the phone via my local wifi, so i'll be able to test it more seriously. I'll see how it works. With 24.04.1.1 I still don't see any problem with getting the list of networks, I even disabled wifi without intending it and after reenabling it immediately my phone did not crash. Maybe I was lucky this time or the fix for this problem has been merged.

@d4f0 @messayisto thanks for your replies, I'm beginning to think that there is nothing wrong neither in force-adb nor in systemd (!) and the problems comes from the device tree of the FP5, that is, the kernel configuration. Changing force-adb could be an easy work around but mostly wrong. I'll try to explore the FP5 kernel code to see if I can find the problem all by myself (enthusiasm level: ) Edit: created this gitlab issue to make the problem more visible.

@uxes Dobrý nápad