...aaaand I was back! And in time for lunch! 😂

The experience with #postmarketos and #gnomemobile was really not bad, but with some catches. Here's some considerations:

I used #Podcast app for #Gnome to listen some podcasts. I downloaded them in a spot with 4G connection and listened while pedaling. It worked okay, but it seems that the pause command originating from the button on the bluetooth headset is ignored.

Also used #Monophony as a #Spotify replacement. It worked very well: when the playback was suspended due to lack of connection, it was resumed automatically when the connection returned available (this doesn't work well even for Spotify on Android...!).

About #GnomeMaps, it was okayish... It obtains a GPS fix in a matter of seconds, and the directions seems accurate (and there's support to bicycle directions), but there's no way to tell it to follow the GPS marker: you have to press the "center on gps position" button every few seconds. If you keep the phone in hand and inadvertitely touch a part of the screen, it selects that position and hides the track you were following. This is very inconvenient: the directions are still there, in the directions list, but the track is hidden from the screen and the only way to make it reappear is to cancel it and re-insert all the fields... There's also no support for #turnbyturn navigation...
But I must say the new #vector #map is awesome: crisp even in hi res displays and very legible, it should be set as the default imho.

I could download #gpx tracks I had already in my cloud (using #gnome file manager configured with my #nextcloud #webdav address), but I couldn't transfer to my #bryton cycle computer, because it seems that #usb #otg is not supported on my #oneplus 6T, and the bryton device wasn't recognized nor mounted.
To this, it would be beautiful if Gnome Maps could allow to save some directions as .gpx file to be sent (once the usb otg thing is fixed) to a cycle computer.

Gnome Mobile behaves very well. The experience in the files app is not very touch friendly, but it kinda works. The lockscreen bug happened again, but this time I could manage to unlock the device without force restarting it. I believe it's some kind of focus snafu, because I could drag the numeric keypad up and down, but it didn't snap to the full open/full close position, it just moved with my finger. The keys were highlighted when pressed, but no character was inserted. The key for opening the alphabetic keyboard or the one for the emergency call didn't do anything when pressed. At last, playing with the upper droprown, I was able to somehow make them to work, insert the code and unlock the device.

Maybe tomorrow I will try to write this braindump in a more legible way and file some bugs to the relevant projects...