20.04 Pixel 3A
-
@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.
-
@rondarius I also was able to upgrade without trouble. I did it about 7 hours ago.
-
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
-
@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.4 Google Pixel 3A
1 Google Nexus 6P
2 Google Nexus 5
2 Pinephones
2 Sony Xperia X -
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 worksSome 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.
4 Google Pixel 3A
1 Google Nexus 6P
2 Google Nexus 5
2 Pinephones
2 Sony Xperia X -
@rondarius The fingerprint reader does that on 16.04 as well.
-
@lakotaubp
I haven't used a phone with a working fingerprintreader before. -
@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 ?
-
@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. -
@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. -
@arubislander That's what I meant to put, but it doesn't read like that. Long day time to stop I think
-
@rondarius said in 20.04 Pixel 3A:
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 worksSome 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 - It is a feature
Edit 1
The Camera app is working, both photo and video with sound. Switching back and front camea works.
Bluetooth is working. I was able to connect a speaker model JBL GO 2.
You are able to output sound through speaker during phonecalls.Edit 2
Pixel 3A pure 20.04 install, RC-channel
Feature
Flashlight is working under the battery indicator
Gesture, double tap on screen to wake phone is working
Hotspot is working(connected to it right now when I am typing this)Bugs
The OSK doesn't always show up in the messaging app and in the contact app, you have to reopen the app for the OSK to show up. This happens more often then on 16.04Sometimes you can't end an ongoing phonecall. It doesn't react to touch input at all. This happens more often then on 16.04
Selfies from the front camera is mirrored in the Gallery app.
-
My first note with focal in pixel 3a xl for two days is the ringing sound when accepting call disappeared completely
If the sound of the phone is present, the sound of the call disappears, and vice versa, there is interference between.
My daily use of the phone so I went back to xenial I hope the problem will be resolved in the next update
other notes
-no Volume indicator
-loudspeaker calling not work- Alarms not work
-flashlight not work
- Alarms not work
-
Hi @kimo
All of the things that you mention here works on my phone. What update channel are you on? Devel or RC? A pure install or upgrade from 16.04?
I am on a pure install of 20.04 RC-channel
Sound indicator works
Sound during calls works, with or without the sound indicator.
Flashlight works.
Alarms works
Loudspeaker during calls works.
Sim works -
@rondarius 20.04 RC-channel candidate with update
-
Is there anyone else that have the same problem with going from 16.04 to 20.04? I myself haven't used my Pixel 3A with 16.04 at all.
-
@rondarius Devel396 no volume slider(known issue) Alarm vibrates very short sound beep, Tourch not working I have no sim in so cannot comment on call stuff. No updates today. Clean install of 20.04 lets see what next update gives on devel. Not tried RC on Pixel.
Edit Volume control work you can see it in System Settings. -
@lakotaubp So things seems to be more stable in RC then? I am using my phone as a daily driver and so far I am very pleased with the experience.
-
@rondarius Things on RC should not change for a while as with any RC update and this one was a Beta. Devel will keep moving forward and there will be the odd hick up along the way as with all Devel channels. These issues will get fixed and improved with future updates.
-
I think I have to clarify things here.
The right way to go with 20.04 is FROM 16.04 TO 20.04 and NOT reinstall the phone with a pure/clean install of 20.04. The Ubports team have stated from the beginning that the users that is on 16.04 will not notice the transition from 16.04 to 20.04. For me that have installed a clean version of 20.04 on the RC-channel(Ubports calls it Beta), I might to have reinstall my phone to 16.04 when the next RC will be released to have a working phone. Why? The right way for the transition is from 16.04 to 20.04 and not 20.04 to 20.04. This might actually brake things for me instead
Only the futute can tell. The point here is: If you are on 16.04 keep calm 20.04 will come to you and you will hardly notice anything. Of course you will notice improvements
So the question from me is: should I keep on posting the things I have noticed regarding my clean install or not? Should I post it here or in another thread?
Edit: We need people to go from 16.04 Stable to 20.04 RC in the update settings to point out what is working and not, because this is the right way to do it and this is what the developers is working on.
