You have to manually switch via the installer or from the settings. Wiping isn't required but just like the usual big updates/upgrades in any system, it is ideal to start from fresh to avoid random strange issues.

I'm not 100% sure but if it means just like how normal stable releases are then it means that the update will be offered to devices randoml starting from the day of release until usually within a week. This is done so not all devices will get the device at once and there will be a chance to stop the release and mitigate issues in case there's critical regression found in the update.

In focal's case, I would assume this will only affect devices that are already in focal since switching has to be manually done for now. Honestly, thinking about it, this might be a statement standard in every OTA blog that maybe shouldn't be included in this particular one since it's the first stable release for focal so no one's really in that channel yet 😅

@Keeper Enjoy.

@ricardo65 Not on focal yet, but I have had a few issues with it opening recently.

@arubislander No, I think it might be down to the Android 9 version I rolled the previous Android back to. When I get more time I will investigate it further. The work around works for me and what I want from the device for the time being.

@flint71 I am using it ok, generally don't reboot unless I have to. I did think of trying the down grade and then updating to the las version of Android 9 for the device, but it is working fine. I may try when I have a bit of time. Thank you for your feedback.

@messayisto I tried, but it didnt work

@whoever fixed this - Thank you

Audio works in Dev Version 673.

Sorry @varman
It is supposed to work. Maybe it is a hardware issue with your device.
Does it work on android?

@tusch001 Quite normal on a few devices with OTA-24 ON Xenial and now on Focal. Minor annoyance I agree, but livable.😊

edit: I opened an issue here https://forums.ubports.com/category/114/20-04-focal-fossa
for further discussions

@kimo
On RC (2) and Dev (647 to 653). None of the dev versions are working.
Phone: VollaX
I posted it on github (https://github.com/ubports/ubuntu-touch/issues/2114)
Seems I'm not the only one having problems, at least one other repky there.
The only information I have is the error in the Logcat app from pulseaudio-trust-stored that a directory or file is missing.

Thanks for helping.

@arubislander

Very possible this is a hardware problem. I have reinstalled the original android OS to the JingPad to see. If I have more issues I will start another thread.

@arubislander i created a password app gmail and it worked. Thanks

Development works fine, thanks for the hint 🙂

@kristatos I think these are long standing issues especially in some devices. I experience it more often with bluetooth. I usually just reboot when this happens. Not sure if there's a better solution.

Just to point out you will need Tow-Boot installed to run 20.04 on PP and PPP https://tow-boot.org/devices/pine64-pinephoneA64.html though must admit I need to read the instructions a few more times to understand them.
For instance

dd if=mmcboot.installer.img of=/dev/XXX bs=1M oflag=direct,sync status=progress

the XXX in the above is that as is or should a specific version code be add here. Something to look at over the weekend on the PP.

@kimo Yup seen it
It went back to tall then got fixed for real 😁

@lodhi
For me, I installed focal from the first download on the dev channel, and I can tell you that most of the problems that existed have been solved. I have the same device, pixel 3a xl a question, to make sure that the p3a xl works with a single SIM Do you see two SIM like my?
2023-02-23T12:06:05.130Z.png

@lduboeuf With todays update it's working again. Thanks 🙂