@arubislander said in Trying out UT on Pixel 3a XL for review article: Opening an issue about it on the Installer's issue tracker will keep the info from getting lost. Done! https://github.com/ubports/ubports-installer/issues/4177

I casually watched a part of that Q&A session! This thread was mentioned and it will be looked into: https://www.youtube.com/live/XorXLuKl2KE?feature=shared&t=1202 I have a question regarding Liberapay. I'm donating to ubports-foundation: https://liberapay.com/ubports-foundation/ But there also is UBports, which is a team ubports-foundation is a part of: https://liberapay.com/UBports/ What's the difference between them? Perhaps UBports was created first and, when the foundation was established some years later, a new account was created? Should we donate to ubports-foundation? The PayPal, Liberapay and Patreon images on the donate page do nothing when clicked: https://ubports.com/donate

@oli.sax I asked regarding this in the "UBports Welcome & Install help [English]" Telegram channel back in April. Someone responded "oh crap i forgot to fix that". I did not follow up as it was not that important to me.

said in Is there a better browser somewhere?: @Fuseteam could you please give me a clue how to install uFirefox? I downloaded several .click files from builds artifacts and tried to install them with OpenStore, but gives an error "the package could not be installed. Make sure it is a valid click package". As well itried to install the from command line, but there are errors too phablet@ubuntu-phablet:~/Downloads$ pkcon --allow-untrusted install-local firefox.fuseteam_142_arm64.click Installing files [=========================] Finished [=========================] Fatal error: No such file /home/phablet/Downloads/firefox.fuseteam_142_arm64.click, or unknown or unsupported content type phablet@ubuntu-phablet:~/Downloads$ sudo click install --all-users firefox.fuseteam_142_arm64.click --allow-unauthenticated [sudo] password for phablet: Cannot install firefox.fuseteam_142_arm64.click: Signature verification error: debsig: firefox.fuseteam_142_arm64.click does not appear to be a deb format package This is resolved, please ignore the question. Somehow I really downloaded several files corrupted. Simple re-download helped.

Welcome! If you're interested in using Ubuntu Touch, I'd say the best bet is to read around the forums a bunch to see if Ubuntu Touch will fit your needs, and if so which device from the Devices list will suit your needs and try to find one that's available and affordable where you are.

Today I found that someone has a similar problem with the Volla Phone 22 : https://forums.ubports.com/topic/10983/volla-phone-22-very-laggy-performance/5?_=1756284607730 . Maybe both problems are caused by the same thing.

I have a similar problem with my Volla Quintus, see : https://forums.ubports.com/topic/11263/frame-rate-and-slow-animations-movies . I am already in contact with Volla about this. But because "laggyness" or "low framerate" is quite subjective (not easy to measure in technical terms), except you can record the screen in high framerate and without aliasing, it is not easy to talk about and to discuss this problem.

@arubislander I thought directly compiling ofono-binder would offer more VoLTE settings options, but it seems I need to change my approach. I'm flashing the system again now, hoping that this time it will resolve the issue of enabling VoLTE for unsupported SIM cards. Thank you.

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

@RJDan hmm, i may be able to do something about syncing passwords, but it would require cooperation from the UT development team. no promises though I already have my plate full with the upcoming rewrite of uWolf for Noble and NixManager plugin for lss (which i'm waiting on a test device so i can start working on the UI)

@JPC So, I could solve my latest connection issues by doing a waydroid init -f.

@markpousee Your device does not feature on the devices list. What version of UT are you running, and how did you install it originally?

I found the strangest coincidence possibly but I think it potentially solved this whole issue. Here is what happened. Re-downloaded and deleted all images/installers I had been using for both Android and UT After re-flashing the stock 13 Image I was having the exact same issues on Android now. Flashed stock 15 for science and confirmed this was also happening there. After rolling back 13 and playing in settings it turns out that Enabling "Allowing 4G Calls" in Android 13 settings resolved my data issues in Android. Flashed 24.04 Daily (r561) and found that not only did data work and it gets 5G now, MMS also works (with WIFI off) before it constantly said there was a network issue. I am not sure if this is the fix coming in beta 2, but its miles better than my experience yesterday!

@Eric-H It worked It was my fault — I had skipped that step because I thought it was impossible to downgrade the OS version. But it was actually straightforward to just execute the flash_all.sh. Thank you so much!

@Vlad-Nirky Thank you. Done.

@Mabuntu said in wi-fi scan: Hallo, I had the same problem. You could try power off and later power-on the device over bootloader (power+volume-up) but before you do that you have to swtich into flight-mode. Good luck! Additionally you could delete systemsettings cache &settings-data with ut-tweak-tool Thank you. I accidentally figured out another way: after I managed to get wi-fi to work as expected, I left the wi-fi on before turning off the device and next time I power the phone on, wi-fi works. In case I experience any problem, I will try your advice. Thanks again.

Hi @darshpreets I cannot be sure about your specific device. But phones are usually only able to be either an access point or a client, but rarely both. As for Ubuntu Touch being able to handle this case on such compatible hardware, I'm not sure. That would be something to test.