@arubislander Fresh install. I used the image listed on the Pixel 3a page on ubuntu-touch.io. I solved the issue yesterday with a clean install, everything works now. I still can't get to that app permissions screen but apparently I don't need to (not yet anyway). So for anyone else experiencing this issue, all ya gotta do is re-flash back to Android 9 and then reinstall UT, easy fix.

@ToxyPoxy Thank you all for the quick response! After I woke up I tried to reinstall UT 20 and that did not do anything so I installed older version UT 16.0 with the same result. I tested the camera app and the sound for the video was not working. This issue is now solved, and all I had to do was turn off bluetooth and restart my phone (why on earth is bluetooth and location on after installing UT should be off) After running search on the web I saw many people had some issues with the microphone on the Pixel 3a. So I found my solution in this article: https://support.google.com/pixelphone/answer/9706190?hl=en#zippy=%2Cothers-cant-hear-me-on-app-calls-like-meet-or-skype So I hope this will help someone in the future.

@ckrnkfrnchmn it's a known issue related to the fact that on xenial branch that toggle is trying to modify a property provided by underlying Android layer but it cannot be done properly as it's complicated to manage appropriately. Hope that this will change in the future with the brand new focal image. Regards. Matteo

@Luke-0 Glad you sorted this. Can you please now proceed like mentionned there : https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved THX ^^

@keneda said in New RC update fixed flight mode: Really?!? Never had issue with flight mode on my MX4 Neither have I on any device, including the Pixel 3A.

@lduboeuf indeed i don't let this counter grow anymore ^^ i've got some ideas i'll propose

@moriarty Before using apt-update, make sure your device is up to date ( system-settings->update). apt upgrade work most of the time, but some updates are expected to be installed in recovery only, making the update broken. In that case, often a re-install from the installer is ok.

@tux17 Indeed, probably not impossible, but also not supported either. So if you run up against any issues you would probably not find any help here.

@keneda Thanks. I live in Canada so that should not affect me. Having said that, I reset the phone and now it seems to work...weird

@normmmm Please follow @arubislander's directions and use a laptop/pc to follow the links and download the correct android version and android flash tool. Non of thiscan be done on the phone as it needs to be connected to the pc/laptop via a usb cable to flash the correct android 9.

@lduboeuf For testing, i send sms to myself regularly.

@lodhi Please note going back and forth from 20.04 to 16.04 may throw up some issues. Treat them as 2 different OS. The apps can be completly different as is the OpenStore the main idea is that when you move you stay there. My 3a had a few issues with installing after a few back and forths. There will be another RC soon for 20.04 and I would recommend that for the 3a which runs great on 20.04.

@orchard800 As @Moem mentioned, the code you set to unlock your device (pin or password) becomes the password for your user. Ubuntu Touch is set up like regular Ubuntu with a locked root account and the main user with sudo privileges. So doing things like su - will not work. If you really need to start a root session (not for using apt, that is not supported) you could do sudo su - instead. What happened to you was that you set up a pin via the GUI, and then went and changed that to an alphanumeric password from the command line. Since the GUI still thinks you have a numeric password it presents to you the numeric keypad for easier entry. This leaves you with no way to enter the other characters of your password, effectively locking you out of your device via the GUI. (ADB access might still have been possible if you had set that up previously.) The takeaway is this: if you want increased security, set a password via the settings, not a pin. Having said that, a change is in the pipeline to allow setting of longer pins than the four digits that is currently the case.

Seemed to have resolved itself? However, upgraded to the RC of 20.04 and camera works fine. Battery life still poor (but that may be my device).

Thank you! I'm using Debian 11 - I can't work Windows - and the recognition is...? spotty? I'll try to find another cable... seems to me the same thing happened before but i got up the next day and it just worked. Haven't had a new new phone since the Galaxy S4 so my cables are suspect anyway. Really appreciate the feedback.

@tupelohoney Flashlight toggle doesn't work yet in 20.04. I have heard the uTorch app does work though. Check if it is in the OpenStore all. If not you might need to download it from the open store website. What the picture transfer is concerned, do you mean via Bluetooth? Bluetooth is know to be finicky on Ubuntu Touch at the moment.

@carl Hi, I want to buy an pixel 3a xl too for daily driver. Before I buy it i want some kind of feedback about battery life with waydroid, whats work and where are the problems. Also I thinking between pixel 3a xl and poco x3 nfc, and for now I don't know which one to choose. If someone could give me answers, thanks a lot!

@emphrath thank you so much for answering all the questions! From everything you've written, I've decided to save more money and get an Xperia instead of a Pixel. In order to use it as a daily driver, it has to fulfill all the basic things and still be able to last through a day (and a half).