@AdFundum thats essentially what i did, ill upload my implemention once i get home to my laptop in roughly 3h.

@PerlMax Well I don't know, I've not done anything in particular, with 24.04-1.3 there should be only one window by default for a Xwayland program. Make sure to do export GDK_BACKEND=x11 export DISABLE_WAYLAND=1 before you start your app

@gpatel-fr said: I don't know what this could mean for Volla phones. Neither do I -- I just created a support ticket with them that includes all the troubleshooting info I have. We'll see...

@pparent said: Yes I plan to work on fixing that soon! this would be great At the moment I study your content-hub implementation. Also great work there

I've published the new revision (0.1.8) with the following improvements: -Fix layout problem coming from changes upstream -Improve ContentHub handling -Improve call icons layout I should also not crash on 24.04-2.x, although it will probably not be usable yet, as for now it seems that On-Screen-Keyboard does not work on any XWayland app. I will try to investigate more about that soon. I next revision I will try to add an option to configure scaling with fine grain, and few improvements/fixes in the UI.

@Blackbomber 1GB of RAM would make the experience not good especially when using multiple apps. But I think the biggest issue is the very old Android version. Older halium is basically left behind to older UT versions. Old kernel would also be a big blocker since Ubuntu requires features that are only on newer kernels.

@Vlad-Nirky thanks I anonymize the IP routes log but I quickly realized it woude baisicly be useless when anonymized So I just deleted it since it had no value

@Privacy-freedom I understand totally. That's why best would be, if UT Tweak Tool doesn't work, to contact volla directly. You can also try their forum : https://forum.volla.online/

@Linus67 I think this got on a wrong turn and sadly he got quite upset about what happened here. That put him off. This should never happen anywhere, but here (UBPorts forum an open-source community in general) in particular.

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

@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.

@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.

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

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.

0.5.4 - 2029-06-07 New / Improved Updated Electron/Chromium engine and related packages. Start Page shortcut layout improvements. Fresh coupon shortcuts now lazy-load in 12-entry batches, so large merchant catalogs do not render all shortcut tiles up front. Mobile toolbar now includes an expandable actions tray with Messenger, Back, Forward, and Reload controls. Telegram deep links (t.me, telegram.me, telegram.dog) now open in the built-in Telegram messenger tab instead of trying to launch an external app. Fixes: Password unlock duration controls now apply correctly from both the unlock dialog and Passwords settings section. Anti-bot and captcha checks are more reliable on Ubuntu Touch and Linux ARM devices. Mobile text selection handles now work inside editable web content such as Telegram and Gmail compose fields. Telegram Web internal redirects no longer show the browser error overlay during normal app navigation.

I only had this issue start when moving from stable 1.2 to 1.3

@ChromiumOS-Guy Thanks for the Reply. Do you mean the UB Installer? Because that doesn't find anything. And the Phone isn't found using "fastboot devices" since doesn't boot into the Fastboot Environment.

@Vlad-Nirky https://xdaforums.com/t/cant-unlock-the-bootloader-on-redmi-note-9-pro.4790995/

@brenno.almeida Hello Brenno, Could you explain where the deamon is installed? Becaused I notice that when I disable the account inside the app and then uninstall the app, I still have some greenline deamon running, and creating some logs: Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'. Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC Jun 07 10:06:30 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service. Jun 07 10:06:30 ubuntu-phablet systemd[2675]: greenline.service: Scheduled restart job, restart counter is at 5123. Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'. Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC Jun 07 10:06:20 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service. Jun 07 10:06:20 ubuntu-phablet systemd[2675]: greenline.service: Scheduled restart job, restart counter is at 5122. Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'. Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC Jun 07 10:06:10 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service. Jun 07 10:06:10 ubuntu-phablet systemd[2675]: greenline.service: Sch eduled restart job, restart counter is at 5121. Jun 07 10:05:59 ubuntu-phablet systemd[2675]: greenline.service: Failed with result 'exit-code'. Jun 07 10:05:59 ubuntu-phablet systemd[2675]: greenline.service: Main process exited, code=exited, status=203/EXEC Jun 07 10:05:59 ubuntu-phablet systemd[2675]: Started greenline.service - Greenline Sync Service. Thank you very much!