Call for testing: Ubuntu Touch 20.04 OTA-6
-
@peat_psuwit said in Call for testing: Ubuntu Touch 20.04 OTA-6:
@lduboeuf Could you please try the devel image? @fredldotme mentioned that he has reverted a kernel change that supposedly cause a kernel panic on sleep. If it's fixed there, we can have another RC, possibly also with a fix for the mentioned above Volla Phone X23 breakage.
No random reboots since 2 days. So fixed, ty
-
-
-
@Charly (and anyone affected by broken mobile data on OTA-6 RC), could you please try resetting APN settings and replace them with the current values from the database?
To do so, go to System Settings > Cellular > Carrier & APN > APN, then select "Reset All APN Settingsā¦". Confirm the action, and then note if the settings change or not. See if mobile data is restored. If not, try rebooting the phone and check again.
In any case, logs gathered using my previous instructions are still valuable.
-
-
Sorry I'm traveling and my X23 is my daily driver. It would be nice if someone else would be able to try it. Perhaps I could try in some days...
-
Update: We've released another RC, which should have tag 2024-W45. This contains the oFono backend revert for VPx23 and VP22_H12, as well as Pixel 3a's kernel fix which should fix random reboot.
If nothing else crops up, we expect to release Ubuntu Touch 20.04 OTA-6 on 8 November 2024.
-
@peat_psuwit Volla 22: not related to this last RC, but I note that quite often, you have to start the smartphone twice for it to detect the SIM card and offer to enter the PIN code.
For example, after the update, I had to restart the volla 22 again for the SIM card to be detected.
-
Hello, I tried to install the new RC V15 5 times. Twice via WIFI and 3 times via mobile data (LTE). Unfortunately, it hasn't worked yet (see screenshot). Is there a problem?
-
-
@Charly the Updates page has been known to have some flakiness that we can't quite figure out yet. Could you please try clearing the updater's cache by pressing the bin icon on the top right (next to the cog wheel)?
-
I had deleted the update cache after each error report. Unfortunately, that did not help.
-
@Charly Hmm Ok. Could you please get the updater's log, available at
/var/log/system-image/client.log
? The file is restricted to root only, so usesudo
to gain access to it.sudo cat /var/log/system-image/client.log >client.log