Call for testing: Ubuntu Touch 20.04 OTA-6

peat_psuwit

@Charly Don't worry. We consider loss of mobile data to be a major breakage, and will not release OTA-6 before it was dealt with.

If https://paste.ubuntu.com doesn't work for you (and you still can't upload the file directly to this thread), you may try a few alternatives.

And failing that, you're welcomed to join us on Telegram (https://t.me/ubports_qa_team) too.

Charly

@peat_psuwit
Hello, now it was possible to upload the File. Thanks a lot!

So here is my log file.
The problem is loosing my mobile data with rs OTA-6
on an volla x23.

journalctl.log

Charly

@Charly
I hope it is save and has no private informations?

azkali

@Charly Can you go to your cellular settings and make sure that Cellular Data is activated, that the APN is correctly selected and the connection type is set accordingly as well ?

Charly

@azkali

I have mad the attached!

screenshot20241011_212955638.png screen shots.

Charly

Charly

@Charly
sorry wrong screenshot

Charly

Charly

@Charly

peat_psuwit

@Charly Thank you for the log. This pins point the area of the potential problem. The following commands enable debugging output of oFono, a telephony component, and restart it. The setting disappears after reboot.

sudo mkdir -p /run/systemd/system/ofono.service.d
sudo tee /run/systemd/system/ofono.service.d/zz-debug.conf <<EOF
[Service]
ExecStart=
ExecStart=/usr/libexec/lxc-android-config/ofonod-wrapper -d
EOF
sudo systemctl daemon-reload
sudo systemctl restart ofono.service

Wait around 1-2 minutes for stuffs to settle, then re-run the log collection command again.

journalctl --boot --identifier=ofonod --identifier=NetworkManager >journalctl.log

The previous log does not contain (much) private information. However, this one is going to potentially contain (more) private information. So you probably want to send this log via the forum's chat or via Telegram (@peat_psuwit).

Charly

@peat_psuwit

Unfortunately, I don't know yet when I'll get to it. I use the phone as daily driver. After the test, I always switch back to OTA-5 stable.

lduboeuf

@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

peat_psuwit

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

Charly

@peat_psuwit

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

peat_psuwit

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.

domubpkm

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

Charly

@peat_psuwit

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

@Charly

peat_psuwit

@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)?

Charly

@peat_psuwit

I had deleted the update cache after each error report. Unfortunately, that did not help.