@TheTrench You need to delve deeper into 5G and what 5G is, plus what Android version supports 5G on that device. 5G falls into two categories - 5G Non Stand Alone (NSA) and 5G (SA). 5G NSA piggybacks of the 4G LTE infrastructure end to end in simple terms. 5G SA is full 5G end to end. This can be affected by available networks, service providers, Android versions and vendor BLOBs and device hardware. You cannot expect newer firmware files to work on an older version of Android without issues or just not working. I bought a 5G device when 5G was in its infancy and always got 4G LTE indicated and 4G speeds. 5G has a better infrastructure now and it still shows 4G LTE in a lot of cases. My new device is 5G and always shows 5G and is a bit quicker, but not in all cases.

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.

Is it possible to modify eSIMs via apps in Waydroid?

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

Thank you @Keneda !!

@ MrT10001 I’ll wear that badge proudly. @ johndoe Thanks for the advice. I’ll keep it in mind and won’t change anything. @ liam Sorry to hear that. I’m really not an expert. So I can’t understand the issue you experienced with the battery and Postmarket on your device. Perhaps you should try again some time with UT? (Possibly a real expert should say something to that suggestion) With me the installer showed some flaws. I was absolutely not sure about how successful the install would be since it didn’t show anything like “Congratulations! Ubuntu Touch is now installed.” The final screen just showed that formatting was still at work. I could only see on the mobile itself that it was possible to start UT (since there was a reboot and I was asked to define a passkey) and that the amount of free space on the device was big enough to believe that everything was more or less OK. Hope you can still use your device somehow.

@ikoz I think i have found the solution. After allowing outgoing traffic to 188.166.175.79 port 5001 the notifications seem to work. lsof, netstat and a little bit more googling helped me. After disabling ufw; lsof and netstat were showing the IP and port after a notification came in. Port 443 is needed, too. Unfortunately logging with ufw does not work, but who cares, i didn't need it. Thanks for pushing me into the right direction, this warning app could save a life.