This is gone with the new 24.04-1.1 update and voLTE support.

SOLVED !

Hopefully this way it is easy to get a variety of images such as stable or daily rather than just the devel channel on GitLab.

Hy all, In update 224 it is fixed. Glad i din't rush things... Ernst-Jan

I've updated the kernel to 4.19.242 now locally, will test further and merge this ASAP.

After messing with it for a good while, I was actually able to get it working with 5G/4G on the T-Mobile network by flashing the Android 13 stock image, then using the UBports installer. Note: it did seem to have some issues entering the fastboot mode, so that took some finagling. Also, it didn't seem to like it the first install, and I think I flashed Android 15 before Android 13, THEN installed Ubuntu Touch. But mileage may vary, obviously. Now to run some documentation of all loaded kernel modules and firmware versions from dmesg, and potentially try to debug why sound doesn't work on PostMarketOS, enough eyes, every bug is shallow, etc, as I'd prefer Plasma Mobile over Loromi. (Lorimi?) [But any FOSS system over Android, so I'm happier than I'd be without Ubuntu Touch]

hi guys, thanks for your posts, it open a window to me. i set and use an esim on android before flashing to ubtouch. i cannot find any ways to use this esim now on my Pixel3a. can you give some tips to do so? regards Marc

Even better news: The wipe won't be needed. Existing v1 policies continue working and should even be compatible with Waydroid once they're stored in the filesystem keyring. Even if they're not, that's not a blocker for v2 to land early, as existing users can enjoy their devices with the same feature set as before. I'll go ahead and merge this.

@gpatel-fr said in Status of the Location Service (GPS, A-GPS, GLONASS, BeiDou, Galileo) ?: See an analysis here: https://ti.qianxin.com/blog/articles/Analysis-of-the-Hidden-Backdoor-Event-in-Qualcomm-GPS-Service-EN/ TLDR: backdoor is too strong a word, but there are privacies issues. If the software is rewritten as open source, this could be less problematic. Thanks for all these details about the AGPS privacy issue, I understand the idea behind this. It seems it's hard to have a good signal when the phone is inside a car (all satellites were red in GPSTest). I think I need another device as navigating system for my car. I'll check next days if my device could have locaiton fix with Glonass, Beidou and Galileo satellites. I expect using more data sources should improve measurment quality, isn't it ?

VoLTE is working on the FP4 on 24.04-1.1 RC1, thanks everybody!

@Ernst-Jan15 Same problem here with my new Signal UT app, seems to be a limitation with Xmir applications, as the icon never makes it to the left panel.

@kari I just wanting to point out that "daily" is the experimental channel and "stable" is usually the channel for the end user.

@arubislander I followed your path (Android 11 -> UT 20.04) and it feels a lot better now in terms of battery lifetime, random shutdowns etc, so thanks a lot for that! The phone call quality is still a bit mediocre but no disconnections and no weird artifacts/noises, so better on this problem too! Thanks for helping!

Hi again, I flashed Android 11 and UT 20.04 after that and I am really happy for now. I switched on WiFi and 2G only, no other connections. The battery went from 89% to 86% within 7 hours, so that is very okay for me. Check! Thanks everyone for helping! greetz Chev Chelios

@cristodcgomez sorry I was unclear: I have also tried selecting "restart" from the bootloader screen as per your hint above, and that also didn't result in the phone being recognized by ADB. My extra attempt was to go through the recovery menu, which just locks the device when I select the fastboot option. At this point I feel like something went wrong in the UT install that has messed up my phone's ability to access fastboot.

I couldn't really leave it, so I just tried again, and now it worked? I did: Double Checked: Android is version 11 (Build fp4.fp4k.a.179.20230116 $ fastboot flashing unlock FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed $ fastboot flashing unlock_critical FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed Checked All three boxes (Including User Wipe)... Maybe you were right, Luksus (and thanks!), that I somehow missed the first check box, but alas, I'm a happy camper.. Regards Grisen

Hi MrRoughwood, Congratulations! And it's a very good decision to start with “stable.” Greetings Mario