20.04 Pixel 3A

Lakotaubp

TELEports now on 3a so guessing now on 20.04 in general

Rondarius

Hi @Lakotaubp
Do you know if we have to reinstall the phone to make the updates go through automatic and not end up in recovey? I tried to update the phone just now, update version 387, and it ended up in recovery. I am on a clean 20.04 install and not through 16.04.

Lakotaubp

@rondarius That is the issue I keep getting. You can try the installer, it should work but it does not always work for me, see comments above. @arubislander has it working as it should but I will test again tomorrow on the next update.
Edit:Will post back here as soon as I know so maybe hang on to see if tomorrows update works as it should.

Lakotaubp

@rondarius Udate 388 installed as it should this morning with no issues. Give it a try fingers crossed it works for you.

arubislander

@lakotaubp so you had installed 20.04 over 16.04 with no wipe and no bootstrap?

Lakotaubp

@arubislander Needed bootstrap it would not do anything without that. As to why no idea. Everything was wiped to install 16.04. Lets see what the next update does.

Lakotaubp

Just got and installed another update as you would expect it to go. Great, all looking good.

lsitongia

I don't see how to install 20.04. I'm running 16.04 on my Pixel 3a. I downloaded the latest installer from the usual place. The channel pulldown in the installer only has 16.04 choices. How do I get to the hidden choice for 20.04? Thanks!

EDIT: never mind. I see the Settings menu in the installer, to allow hidden channels.

lsitongia

Install went well. I have a lot of trouble with the USB connection to my Ubuntu 22.10 laptop, but after that, the install was a success. I couldn't get a login to OPEN-CUTS working, so I hope it was reported correctly from the installer.

Rondarius

@arubislander @Lakotaubp
Hi
I tried to update to version 392 just now and I ended up in recovery again. I am still on a pure 20.04 install.

Lakotaubp

@rondarius hmm mine installed that without a problem very odd. Not sure on that if a restart does not fixit I can only suggest the installer or wait till the next update and try that. Never found out why it was happening myself but still early days for 20.04.

lsitongia

@rondarius I also was able to upgrade without trouble. I did it about 7 hours ago.

Rondarius

I suspect that I am on a older version that somehow blocks the updater to peform as it should. I reinstall the phone tomorrow to see if the updater works after that. Happy Christmas to you all

Rondarius

@arubislander @Lakotaubp
Hi
Before I reinstalled my phone, I tried to switch to rc channel, I ended up in recovery. After I reinstalled the phone the updater worked as it should because I could switch channel, from devel to rc. So a heads up to all of you that cannot update your phones, it ends up in recovery. you need to reinstall your phone, first to android and after that to the latest version, either devel or rc, to make the updater to work as it should.

Rondarius

Hi
Things that I have noticed since the latest RC update:
Initial setup from a clean install is working with multipule languages to choose from.
Pixel 3A RC-channel pure 20.04 install
Phonecalls is working in and out
Sms and mms is working in and out(check that mobiledata is activated and it still depends on which carrier you are using. I am lacking some settings to make incomming mms to work)
A lot more apps in the Openstore
fingerprintreader works

Some bugs that I noticed:
The phone doesn't detect any networks over wifi during initial setup, it finds networks in settings after setup and it keeps the network after reboot.

If you change screenlock to 4 digit code it will change it to passphrase after reboot. It sticks after reboot when you go under settings and change it to 4 digit code again.

I don't know if this is a feature but when you try to login after a reboot using the fingerprintreader it will not work if you don't unlock the phone with the 4 digit code or passphrase first. Fingerprintreader works after that.

Edit 1
The Camera app is working, both photo and video with sound.
Bluetooth is working. I was able to connect a speaker model JBL GO 2.
You are able to output sound through speaker during phonecalls.

More to come.

Lakotaubp

@rondarius The fingerprint reader does that on 16.04 as well.

Rondarius

@lakotaubp
I haven't used a phone with a working fingerprintreader before.

lduboeuf

@rondarius said in 20.04 Pixel 3A:

@arubislander @Lakotaubp
Hi
Before I reinstalled my phone, I tried to switch to rc channel, I ended up in recovery. After I reinstalled the phone the updater worked as it should because I could switch channel, from devel to rc. So a heads up to all of you that cannot update your phones, it ends up in recovery. you need to reinstall your phone, first to android and after that to the latest version, either devel or rc, to make the updater to work as it should.

sure that we have to reinstall Android ?.Any howto somewhere ?

Rondarius

@lduboeuf
This is the steps that I have done to reinstall Android:
Install latest version of adb and fastboot on your pc.
Install the ubports installer
Download the android 9 factory version sargo-pq3b.190801.002 from here:
https://developers.google.com/android/images#sargo
Connect your phone to your pc
In terminal run
adb devices
to check if everthing is working as it should, a serial number will show up after the server is started.
In terminal run:
adb reboot bootloader
Extract the archive sargo-pq3b.190801.002
Open the sargo folder, right click on an empty space and choose Open terminal here(or type the path manually in the terminal to the flash-all(dot)sh script)
In the terminal run:
fastboot devices
to check that the phone is recognized by the pc, the same serial number will show up as the one that adb output
In the terminal run
sudo ./flash-all.sh
enter your sudo code and it will take a moment to reinstall Android.
After the phone reboots, enter developer mode and tick Usb debugging
Once again run in terminal
adb reboot bootloader
When the phone enters the bootloader run the ubports installer and follow the steps.

arubislander

@lakotaubp and the behavior is by design. Same happens on Android if you have fingerprint reader enabled.
There are plans to add iconography to make this more obvious to the user.