@Privacy-freedom I can give you my openvpn server config if you think it could help

@Moem Yes Same path for 26.04-1.x. I had the early update on my redmi then nothing anymore. Porters are working to put those devices on dynamic partition. On one on my Redmi Note 9 Pro, 6 months ago, I have increased (with Eric H help) the system partition to 4.7Gb (far enough) by deleting the (for my phone) unused Product 1.2Gb partition and increased the system one as much as possible.

@lduboeuf Yes, I saw that. I read Ubports Dev (but don't interact usually). Glad to see that!

@gpatel-fr i used the erase and reset all under option under reset

I'm using a Bluetooth headset myself on FP5 with no 3.5mm available. I have found this intermittent on both stable 1.2 and 1.3, sometimes outputting to the speaker and sometimes just to the headset, I'm not sure if this is some volume setting that gets changed somewhere. Personally I would have always preferred if the device made no sound with the headset plugged in but never thought of the use case were you could miss a call if you leave the headset connected.

I've finished a first small test application (a simple video player). You can find it under https://github.com/MaxPerl/pefl.maxperl All in all, it works pretty well. However, there are a few limitations: I haven't yet managed to get the Wayland engine from efl to work (I'm hoping for Mir 2.x). This may lead to suboptimal performance (especially at the moment no hw acceleration), but more importantly, to an error with rotation. In landscape mode there is a well known Issue with Xwayland: Inputs on the right side of the screen do not work in landscape mode (see also the problem in uWolf, fix could come when this is merged: https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/207). I also can't resolve it through settings X-Lomiri-Rotates-Window-Contents=false and/or X-Lomiri-Supported-Orientations=portrait at the moment (see ubports/development/core/lomiri#184) Maliit virtual keyboard does not work at the moment. Apparently, there’s also a way for Xwayland apps to integrate this via the DBus interface. But right now, that’s too complicated for me. In the meantime, I’ve programmed my own little virtual keyboard (though it’s not really necessary for a video player. You can test it in the file-open dialog at the search field. Works pretty well for me). I’m currently working on a connection to the Content Hub (at least receiving data from other apps would be nice). But it doesn't seem that straightforward if an app doesn't use Qt or QML at all. I've already tried launching the app via Qt/QML instead of a Bash script, but apparently that doesn't work with Xwayland apps? If anyone here has experience with this, I'd appreciate any suggestions. Maybe I’ll start a separate thread regarding Content Hub as well. Surely that should work without Qt/QML???? Best wishes, Max

@Keneda said: @pparent Because I think @lduboeuf got a "bug" and missposted here. There is the place where goes this post in first place https://forums.ubports.com/topic/12312/looking-for-testers-ubuntu-touch-26.04-1.x-early-version/30 ouch that comes from InTouch app, it has posted in a random topic lol, will delete it

OK, found the solution on 'WayDroid on Ubuntu Touch' Telegram group channel Thanks "aleasto" for sharing this solution. Start WayDroid session (by either taping "WayDroid" in launcher or waydroid session start in terminal) When WayDroid session loads, open Terminal on Ubuntu Touch Run the following commands (I think the first prop should be fine, but just in case, I set those 2 props) $ waydroid prop set persist.waydroid.cursor_on_subsurface true $ waydroid prop set persist.waydroid.cursor_force_shm true Restart the WayDroid session to apply prop changes. (By either tapping "Waydroid Stop" then "Waydroid" in launcher or waydroid session stop then waydroid session start in terminal) And from now, hovering mouse cursor to Waydroid window will no longer crashes the Waydroid window. And enabling Show taps on developer options no longer crashes Waydroid window but the taps no longer shows when touches.

@gpatel-fr said: @PhAndersson said: the Pixel is able to get its time from the traditional GSM network My memory is a bit dim on the subject and it's all hearsay anyway, however I remember I was said otherwise. After investigating the issue further (see below), I believe you're right. I just assumed it would be possible because my old Nokia N900 running Maemo used to do it (silly me ). It could be that the Pixel is able to save clock and this ability was lost on more recent phones. Yes and no... Looking inside 'journal' on the Pixel, I found the following: Jun 07 22:05:10 hatshepsut systemd[1]: Starting Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices... Jun 08 08:18:54 hatshepsut systemd[1]: Finished Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices. Meaning that RTC support seems to be linked to the Qualcomm chipset. The Quintus starts the same service, but as it uses the MediaTek Dimensity 7050 chipset, I guess retrieving the HW clock just (silently) fails. Further down in 'journal' on the Quintus, I see the following entry that seems to confirm it: May 21 14:28:02 ubuntu-phablet systemd-timesyncd[1401]: System clock time unset or jumped backwards, restored from recorded timestamp: Thu 2026-05-21 14:28:02 CEST What I don't understand is that you said you had the same problem on your FP5, even though that one does have a Qualcomm chipset (a more recent one than the Pixel, obviously). @PhAndersson said: use your phone as alarm clock when you travel not sure it's a huge priority - there is an obvious workaround: do not stop your phone during the night. Right, yes, I agree -- probably not a huge priority. Still, it bothers me because it also means my log timestamps are untrustworthy most of the time, as are the time-related EXIF data fields of my pictures, etc. Accurate timekeeping on anything computer-like is one of the fundamentals in my book So I guess I'll report it to Volla nonetheless and see where it leads...

Just installed this, giving it a try, so far, so good!