20.04 Pixel 3A

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.

Lakotaubp

@arubislander That's what I meant to put, but it doesn't read like that. Long day time to stop I think

Rondarius

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

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

kimo

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

Rondarius

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

kimo

@rondarius 20.04 RC-channel candidate with update

Rondarius

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.

Lakotaubp

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

Rondarius

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

Lakotaubp

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

Rondarius

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.

Lakotaubp

Weather app is working

lsitongia

@rondarius I think I was running 16.04 RC channel on my Pixel 3a. I did not see an option to upgrade to 20.04 in the System Settings Update Settings for channel selection. So, I ran the installer and selected the hidden channel for 20.04 dev channel in there. I selected wipe.

I would not call that a clean wipe, such as @Lakotaubp was having to do previously, reinstalling Android. On the other hand, I did wipe the OS from the installer.

I like this approach because I know exactly which apps work for 20.04. Namely, then ones that are installed by default. Also, the OpenStore only has apps which have been ported to 20.04. I'm not running 16.04 apps on 20.04.

Now that I'm running the latest 20.04 and the devs have released on RC, I see both RC (going back and forth between 16.04 and 20.04) choices.

Are you saying that in 16.04 you saw the RC channel for 20.04 and could select that AND all the apps you had installed are still there?

Lakotaubp

@lsitongia Only done this on FP4 but the process is the same. There should now be two RC channels showing in update channels on 16.04 devices that are 20.04 compatible. The bottom one will install 20.04. As there is no wipe option all your old data will remain. Including your apps. Some may work to a point others will not and you need to install 20.04 ones. TELEports is one.
The issue is that it is more complex than a swop of channels in 16.04 if you plan on going back from 20.04 to 16.04. It is two different OS after all.
20.04 is much better at this stage on a clean install from my opinion. The least you should do is make a complete backup of your device first before trying.

kimo

@rondarius Today I tried a clean 20:04 installation with the option to clear data in the installer and found the same problems that I mentioned above when installing it with the upgrade from 16:04
I have returned to 16:04 with the upgrade of the channel candidate
It seems that the pixel 3a xl has its own problems, we are waiting for the fix, especially the problem of sound interference, the rest I can deal with

lsitongia

Battery drain is fast. Can't see how to add a screenshot here.

saveurlinux

This is my experience with Fossa ON Pixel 3A XL

Installation worked flawless

Actors

Manual brightness: ok
Torchlight: ko
Vibration: ok

Camera

Photo: ok
Video: ok
Switching between cameras: ok

Cellular:

Carrier info, signal strength: ok
Data connection: ok
Incoming, outgoing calls: ok
MMS in, out: ko
PIN unlock: ok
SMS in, out: ok
Change audio routings ok
Voice in calls: ok
Volume control in calls ok

Endurance

24+ hours battery lifetime: ok
7+ days stability: -

GPU:

Boot into UI: ok
Hardware video playback: ok

Network:

Bluetooth: ok
Flight mode: ok
Hotspot: ok
NFC: (detect but not tested)
WiFi: ok

Sensors:

Automatic brightness: ok
Fingerprint reader: ok
GPS: ok
Proximity: ok
Rotation: ok
Touchscreen: ok

Sound:

Earphones: ok
Loudspeaker: ok
Microphone: ok
Volume control: ok

USB:

MTP access: ok
ADB access: ok

Misc:

AppArmor patches: -
Battery percentage: ok
Offline charging: ok
Online charging: ok
Recovery image: ok
Reset to factory defaults: ok
RTC time: ok
Shutdown / Reboot: ok
Wireless External monitor: -
Waydroid: ko (install but remain with launching icon) I used the following steps https://forums.ubports.com/topic/5907/open-ubuntu-touch-to-all-android-applications/116

using command line

sudo waydroid session start

return

XDG Session is not "wayland"

Additional infos:

alarm sound settings: ko
alarm clock it not at same time zone as clock: ko
UI language is in English after reboot (It is set to French on my phone): ko
Calendar is not sync with the configured Nexcloud account: ko
Contact is not sync withe the configured Nexcloud account: ko

Lakotaubp

Had an issue on my 3a where incoming ringtone did not sound, a reinstall without wipe on the installer fixed this. 20.04 Focal devel.

Codenul

Pixel 3a XL

Ive noticed that when i launch the clock App, if i chose not to use location, it crashes and cant open it at all after that. Havent tried selecting location to see what happens

Confirmed flash doesnt work
Fingerprint functionality is nice, when it works (works more than not)
App store is bare as of now
No Waydroid
Deezer Music Player!!

Excited to see where this goes. UT was working very stable over on 16.04 and couldnt wait to see what happens on 20.04.

Three things i need for daily driver usage

DUO Mobile support (havent tried within Waydroid, also believe there is a terminal "workaround", but havent tried it yet)
MMS Support (PLEASE!)
Waydroid

Lakotaubp

@codenul Just checking that when you say the OpenStore is bare you mean there are not as many apps as the 16.04 version and not that there is nothing in it?

May as well use this to remind all app developers to move their apps over to 20.04 https://forums.ubports.com/topic/8318/update-ubuntu-touch-apps-to-20-04-focal-fossa?_=1671610951770&lang=en-US things are moving along very quickly now.