Call for testing: Ubuntu Touch 20.04 OTA-5
-
@vince-vs New features go into the future release that will be based on Ubuntu 24.04. On a case by case basis it will be evaluated if these features should be back-ported to 20.04.
-
@arubislander thanks for the explanation.
(No bug, for me, with this minor but useful functionality. On Focal stable.) -
@karibooooo Sure, but once rc gets promoted to stable, the feature will be gone there as well.
-
@vince-vs said in Call for testing: Ubuntu Touch 20.04 OTA-5:
So I hope that from ota-6 I will be able to hear the sound after a video recording with the camera.
Would this be related to this bug?
https://gitlab.com/ubports/ubuntu-touch/-/issues/2022
If so, just reboot the device after making a phone call.
Not sure this will be fixed in next OTA.
Otherwise there's a script to fix this permanently.
-
@MrT10001 said in Call for testing: Ubuntu Touch 20.04 OTA-5:
@karibooooo OnePlus5T, option to tap to wake is there, but it doesn't work.
Do you happen to remember if it has ever worked before? That said, the tap-to-wake system is pretty much device-specific. We have to rely on porters to look into it.
@vince-vs said in Call for testing: Ubuntu Touch 20.04 OTA-5:
It says : « only critical and security fixes will be able to enter Ubuntu Touch 20.04 OTA-5 ; Normal bug fixes and new features will need to wait for our next release »
A few months have passed since ota-4, but ..
Ok, since it's like that, … fixed bugs and new features will come in the next one.First, we're sorry for the slow rate of bug fixes in the past few months. We're in the middle of bring our Ubuntu Touch stack to be based on Ubuntu 24.04 LTS, which turns out to take more time than anticipated.
That said, the sentence doesn't mean that non-critical fixes cannot be included in 20.04 OTA's. Rather, it simply means that we're in the freeze period at the moment. There will be at least 1 more 20.04 OTA in the future (to support the change of release system), so it's still possible to get bug fixes in there.
-
@peat_psuwit said in Call for testing: Ubuntu Touch 20.04 OTA-5:
Do you happen to remember if it has ever worked before? That said, the tap-to-wake system is pretty much device-specific. We have to rely on porters to look into it.
I have had a look at a OP5T on 20.04 OTA-4. Tap to wake is available and works without an issue.
-
Update: a new RC image has been published which should fix Waydroid issue for some users. The image should have version
2024-W30/2. Those with Waydroid issue, please take another look. -
Is GPS still working for Pixel 3a users?
Mine was working before the RC, now doesn't error, but also doesn't get a lock. Currently sitting unsuspend for two hours and no lock
-
I would like to help in the little I can, such as testing Ubuntu Touch 20.04 OTA-5 but I am afraid of damaging my phone because my technical knowledge is minimal. I use a Volla X 20.04 ota-4. I changed System Settings -> Updates -> Update Settings -> Release Channel and started downloading an image called Ubuntu touch version 13. I expected something like 2024-W30 and now I don't dare to install... Does anyone know how to help me? Thank you.
-
@rocket2nfinity said in Call for testing: Ubuntu Touch 20.04 OTA-5:
Is GPS still working for Pixel 3a users?
Mine was working before the RC, now doesn't error, but also doesn't get a lock. Currently sitting unsuspend for two hours and no lock
Hello @rocket2nfinity
On Pixel 3a (Focal rc 13): updated the GPS without any bug and tested it with sensor status app 1stly, then with clock, weather, unav and pure maps. OK for me. -
@naizena
Hi, I also have a Volla X. The download for me is also called Ubuntu Touch version 13. After the installation it is the operating system version, Ubuntu Touch 20.04 (2024-W30/2).
Everything worked for me without any problems. Sorry for the bad English.(Deepl) -
@tuXut Thanks a lot. I'll try.
-
@stanwood
Hello,
yes, it does, and we talked about it on https://forums.ubports.com/topic/9803/focal-20-04-is-out-for-quite-a-while-now-you-still-use-xenial-16-04-i-would-like-to-know-what-stops-you-from-upgrading/82
and you sent me your link https://github.com/ubports/ubuntu-touch/issues/2022 which @danfro also gave me.
What I'm noticing is that it works after a reboot, but after receiving an SMS, the audio no longer works, then after a reboot it works again ... I don't know if this also happens after a phone call ...
@peat_psuwit
Hello,
Thank you for your clarification. It would be interesting and necessary for this situation to be dealt with and corrected soon, in the hope that it will be for the ota-6.
A more secure ota-5, of course, so happy ota-5 ! -
Yes. Thanks for the OTA-5 security updates. And since I'm sick of the crazy Volla, I'll totally reflash it to see if that improves things
-
As per telegram post can confirm touch to wake works on the OP5T on OTA-5RC. It won't if you have an OEM screen.
-
@karibooooo Did you try using Waydroid and mobile data only?
-
Quick scan through my settings shows everything remaining as it should be after updating. No issues with websites from my regular sites so far. Will keep an eye on battery usage.
-
@rocket2nfinity I did not.
-
Hallo together,
I am running OTA-5 for some days on OP5.
The double tap wakeup does not work for me, but this has not changed since previous versions.
For me the wifi connectivity seems more stable than before.
Also Bluetooth connections to my freespeech on car also with my earbuds works really better.So far I did not found any problems with this OTA.
Thanks for your work and best regards
Naumi -
Almost everything works fine on the POCO X3 NFC (surya) after switching to the RC channel.
However, there is a sound issue detected by FredFast, thanks to the Telegram app.
When you record an audio message, or during a call, you hear clicks/crackles.
These sounds disappear if you add “--audio-buffer-size=2048” to the QTWEBENGINE_CHROMIUM_FLAGS environment variable.
According to FredFast, this is a new bug, not present in OTA-4.I don't know if this is an important bug, as I haven't had time to test other applications, but as it could affect all QTWebEngine-based applications, including Morph, I prefer to report it here.
