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.

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

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.

@hisacro - well, the longer term future is never all that clear, but in the more short to mid term, there are ports being worked on for the Furilabs FLX1, and the Brax Phone 3, that should be promising options for those that want to support companies that target their products specifically to be privacy respecting. After that, the Fairphone 6 has been announced and will very likely get a UT port as well. Volla, despite being a small niche operation, has shown some resilience and consistency, with UT support being enabled for every device they have released, so I think we will see more from them in the future as well. Pixel 5, 6, 7, and 8 (and variants of these) should be doable for Halium based ports, it just takes someone that owns one of these devices, that has the needed patience and technical know how, to volunteer for this effort. Regarding Xiaomi phones in the future (which includes brands such as Redmi and Poco), those were already kind of a pain the a to get their bootloaders unlocked, and with Xiaomi's new HyperOS (their new bloated skin on top of Android), they have made it even harder to unlock. I had to use a third party hack called "Hypersploit" in order to unlock a Poco X3 NFC which came with HyperOS 1, and apparently this hack no longer works on Hyper OS 2. Best reagrds, Steve Berson

Sorry for popping out of nowhere, but @kuailexs kudos for the Volte initiation! hope this becomes a trigger for rest of the devices.

@DenMoore Oh thank you! Nice start indeed! I think WayDroid needs some patches to run properly, this is a "porting" stuff. I'm sure it will come further.

@kristatos I concur! There are guidelines outlined by the gsma for an RCS client and from what I read from this reditor there are even Servers outlined in the GSMA docs for sending RCS messages for some carriers. It seems that SixDigitCode has made some great points for how a RCS client could be built. From what I see they have a handle on this spec, and it might be worth seeing if they are still around on the internet? I will post again with the updated documents from the GSMA and work on trying to break them down Helpful Reddit posts Post 1 Post 2

FINALLY!!! had to manually resize the partitions for no particular reason that made sense ....no really iv flashed UT on this like 2 dozen times ....i must have flash a borked rom with that android 16 and did something to the partitions ....idk didnt make a lick of sense to me ....ok it made sense

@stanwood thanks I might revisit in like 6 months time and see if things have improved I actually own two FP5s (got a 2nd one recently very cheap second hand recently to muck around with) and for now I'm having fun using CalyxOS I did rather enjoy UT for my short few days using it. As it matures I'd love to re-visit it

@kugiigi thanks for your information... Better wait a while.