Call for testing: Ubuntu Touch 20.04 OTA-5
-
Battery life doesn't appear to be affected in this RC on Fairphone 4.
-
Ubuntu Touch 20.04 OTA-5 is expected to be released on 29 July 2024.
Is OTA-5 stable actually in distribution by now?
Greetings
Charly -
@Charly It has just been released and will roll out across the devices over the next few days.
-
After a slight delay, Ubuntu Touch 20.04 OTA-5 is released and is now rolling out across devices. Thank you everyone here for testing.
https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-ota-5-focal-release-3933
-
@peat_psuwit Has it merged with Stable. I have swapped one of my OP5T to stable from RC and it didn't do the expected process of downloading the stable image for installation.
-
@MrT10001 It is released today but not to all devices at the same time. Maybe check again in 24hrs or check the OS stable version against the one mentioned in the release/testing blog.
-
@Lakotaubp Will do.
-
@peat_psuwit Hi Peat,
Just a question:
I don't see any devices from the Redmi Notes series (9S, 9 Pro, etc.) on the list of smartphones that will receive OTA-5.
https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-ota-5-focal-release-3933
However, these devices still receive UT updates on the Devel channel.
Would it be possible to add them?Thanks again for all your hard work!
-
@stanwood
The porters have indicated they don't consider the port mature enough for RC and Stable channelsEDIT: The above information is incorrect for any Note 9 that is not merlin. Only merlin is still on devel channel only.
-
@arubislander That's a surprise. This is the first time I see that information. And I must say joyeuse is one of the best ports out there and is not lacking basically anything.
Contrary to what you say, any idea why OTA-5 has been released for it though?
https://system-image.ubports.com/20.04/arm64/android9plus/stable/miatollTo verify the image from yesterday is indeed OTA-5 I just switched to that channel:
sudo system-image-cli -vvvv -p 0 --switch 20.04/arm64/android9plus/stable
-
@zubozrout Argh, I have been stung by the Xiaomi naming conventions again!
What I said above pertains only to the Redmi Note 9 (merlin), not the others.
Sorry for the noise.
-
@arubislander Thank you. So Curtana (Redmi Note 9S) won't receive OTA-5?
Should I switch to RC or Devel to get the latest updates?
Indeed, I did not see any information that this device is "more or less" discontinued, as I just bought it 3 months ago to replace my Nexus 5...It works pretty well on OTA-4 stable, except the vibrator that a fix has already been pushed to devel. That's the reason I was delighted to get stable OTA-5 as well.
-
@stanwood No, those should also get OTA-5. I will update my answer.
-
@arubislander Many thanks Arubislander! That's put my mind at rest!
-
@arubislander Here it goes! Just got OTA-5 Stable on my Redmi Note 9S today!
Update was smooth and no issue at all so far. (except vibrator still doesn't work)
Many thanks for this great achievement!
-
Redmi Note 9pro
Redmi Note 7
Both updated to OTA-5 (stable) . All seems ok so far.
-
Hello
here are my first experiences with OTA-5 stable on my volla X23 cell phone:
New Problems:
-
"crazy volla" now every day (before twice a week)
"crazy volla" means: several programs start on their own, sometimes the configurations are also changed. -
recording videos often causes the program to hang.( before no problems)
still open:
- gps metadata in photos incorrect
-after reboot LTE only possible after airplane mode.
-
bluetooth problems
-
change volume when making calls does not work. and handsfree is too quiet.
-
Birthdays multiple times in calendar and not removable.
-
-
@Charly If your X23 is under legal warranty, contact the Volla team to explain the problem and try to get it replaced for free..
-
supplement
- Rsses has already crashed 3 times today
- Crashed programs cannot be restarted immediately
-
Hi @Charly
For bug report and update, it's best to go to gitlab directly.
This post was created to accelerate things during the RC phase.Now that OTA5 is out in stable it won't be fixed until the next OTA.