Thanks for this reaction. Looking at the repowerd source explains why I did not find more hits for "FastDormancy": most of the time, it is "fast_dormancy", with an underscore . I'll check if this brings me any further.

@sixwheeledbeast What you are describing is the same as I have. GPS: I still need to test (for you it works). Camera Glitchyness could be happening, did not have that myself. USB Dac and similar stuff can be tricky even on Android. For me it works better in UB-Touch then Android. Desktop mode / USB Video is clunky and/or broken depending on the Hardware used. Vibration and Notification is more about Waydroid then the os (It is part of a sublist in the waydroid row). The Libertine issues is FP5 unrelated. Waydroid and Vibration, Notifications passthrough and GPS are know limitation or issues. I just noted them down so if I check back on my own website later to check if something changed its working state i can know for sure. This list is just a copy of my website entry and you are right, a redundant list of "working" in the forums is no longer needed at this stage. Someone here asked for an updated and I was testing at the moment anyway so I just updated the first entry in this topic by copying my personal list to it. Calling waydroid a stopgap is a little hard that's right... I just use it that way on my phone. It is great and makes Ubuntu Touch extremely powerful in software compatibility but is mostly used to fill in for apps that are not ported or supported by the makers of the apps. On platform's like PCs it is more used as a "emulation" tool.

Screen Recorder in the OpenStore. It doesn't support sound yet though.

@uwahl This was the place. By writing a new file named places.conf in /home/phablet/.config/filemanager.ubports/, I was able to get the File Manager app to access the server. Thanks all. Technically solved issue. And yet, performance is incredibly poor. Very slow to load, and read-only.

On two Pixel 3a devices I have access to, I'm unable to reproduce the issue without Waydroid (Waydroid is installed but disabled using sudo systemctl disable waydroid-container.service). However, once Waydroid is started, the problem occurs after recording the first video. I don't have definitive proof that Waydroid is the cause in every case, but the correlation is strong enough that I attribute most of the video recording issues I've experienced to Waydroid running in the background.

@Caedem perhaps a bit late. But I installed the focal branch and tested a few things, mainly the wireless display using AnyCast device and it works bit of lagging here and there can't determine my device is too damaged. Waydroid also works pretty well. I can't test the sim or the fingerprint. And the device charging board was fried if I replaced it I won't mind testing or help port features I can test. Pretty happy to see this device alive again thanks buddy.

@frifo Windows 11? Check optional updates in Windows updates.

@TotalSonic thanks for that, really I'm interesting to see what possible solutions might be available.

@haagch im currently working on the nix-manager project + in between somethings, so it will take me a while to test. LibreWolf is secure by default like that and i will not change it, maybe a call out that this is an extremely hardened version of firefox. location is not something i can fix, this is something for librewolf devs/ ut devs to work on. UI bugs relating to clipboard are due to xwayland and will be "fixed" by running under wayland when subsurface support is introduced.

Currently only the subcategories "Volla Phone", "Volla Phone 22", "Volla Phone X" and "Volla Phone X23" exist. For example: the Volla Phone X23 has comments in this forum in https://forums.ubports.com/category/118/volla-phone-x23

To progress further with the initial flashlight idea, controlling the flash directly appears to work fine in the following way. #!/usr/bin/env bash flashOff() { printf '%s' "0" > /sys/class/leds/led:torch_0/brightness printf '%s' "0" > /sys/class/leds/led:switch_0/brightness } flashOn() { # 2 appears to be the minimum brightness value possible printf '%s' "2" > /sys/class/leds/led:torch_0/brightness printf '%s' "1" > /sys/class/leds/led:switch_0/brightness } So with a loop I can have a nice flashing pattern at the minimum brightness. Just need to find what to hook into so I can have it only running only while there is a green notifications icon. As for using the screen, I think the green envelope icon, possibly slowly moving along the top edge of the screen (to minimise any burn in); would be a nice option there.

finally got it resolved, deleted ~/Pictures (it was a symlink to other place on sdcard) and rebooted

@Alain it's great to read your good news! Thank you and I hope your daughter will enjoy her tablet for a long time.

I'm interested in an example, too.

@hankschwie hi mate, so at long last the latest update has sorted the reboot problem - this is version 280 of Ubuntu 24.04 as of 26/06/2025. I don't know about Fairfax phones but have a Gigaset GS5 which I used the Vollaphone 22 with new screen install. Phone works, Ubuntu works, and now Waydroid is back..... These folks are truly amazing

@johndoe we are working on a plugin to lomiri system settings like Libertine plugin. I already have most things implemented in backend, mostly lack some generation control over nix/home-manager left other then that mainly implementing the main UI, I have a design ready just need to implement it.