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

@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

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

@PerlMax Sorry but I'm not sure to understand your message, what you want to achieve, or what keyboard issue you are talking about. Can you explain more?

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

@PhAndersson I had this problem at some point but I don't see it anymore. As my logs don't get far back enough, I can't find it in old logs but I remember a time where my logs were always displaying a wrong date at the beginning. the README.md states more completely: Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices, this is needed on devices with read only RTC drivers I don't know what this could mean for Volla phones.

Hi, sorry for the late response, I don't have a lot of spare time so progress on this goes very slowly. @brenno.almeida Not yet, I now going to try running in the app directly because maybe the adb shell is sandboxed differently from an unconfined app. @ChromiumOS-Guy That is an interesting suggestion, I had not thought of it. When I try to interact via the command line with lomiri-system-settings I am getting errors, but I found the background plugin folder in the source code. https://gitlab.com/AdamSchrey/lomiri-system-settings/-/tree/main/plugins/background?ref_type=heads I am going to see if I can bruteforce it by copying the logic from the source code for my own app and running it unconfined. Probably won't work but I might learn something interesting in the attempt.

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.

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

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.

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