OTA-20 Call for Testing Companion Post

flohack

Hello everyone!

The expected release date for Ubuntu Touch OTA-20 is Friday, November 19.

This forum post is a companion to the OTA-20 Call For Testing

Please post any general observations you have while testing the current image in the RC channel, as compared to OTA-19, in this thread. The current release candidate (RC) is 2021-W45

If you have any comments on any of the specific issues in the OTA-20 tracker, please post them in the issue thread so they are easier to track. OTA-20 tracker: https://github.com/orgs/ubports/projects/29

Please note that only critical and security fixes will be able to enter OTA-19 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Moem

@flohack That's odd... I just updated, I'm on RC and I'm running 2021-W45.

flohack

@flohack Sorry my mistake, fixed

Moem

@flohack Thank you, that was fast!

nero355

Question about future BQ devices support :

Since most of them if not all will be declared EOL when 20.04 LTS is released I was wondering if there is any point of letting you guys know that the Battery Level on the BQ Aquaris E5 HD Ubuntu Phone Edition is not reliable at the moment ?!

Depending on your answer I might consider testing this part of the bug in this OTA

flohack

@nero355 there were no changes to the Android part of the E5, and charging is not in the scope of Ubuntu Touch at all. Either its your battery or idk - the device charging driver in the kernel takes care of this, and we only read the percentage.

So, you can test this in the latest OTA and compare devel - rc - stable channels to see if there is any difference, but its kind of an "out of bound" test since there is no issue or code change that could pertain to it. And also, find someone else to confirm this. But it will be hard to fix since BQ´s dervice tree is closed source so we cannot inverstigate or recompile at all to try fixing it, if we would know whats going wrong.

Also those devices are very old, I expect funky batteries happening at some point.

Lakotaubp

@nero355 As @Flohack mentioned there have been a few reports on here and Telegram of odd battery behaviour due to age and then failure.

nero355

@flohack said in OTA-20 Call for Testing Companion Post:

@nero355 there were no changes to the Android part of the E5, and charging is not in the scope of Ubuntu Touch at all. Either its your battery or idk - the device charging driver in the kernel takes care of this, and we only read the percentage.

So, you can test this in the latest OTA and compare devel - rc - stable channels to see if there is any difference, but its kind of an "out of bound" test since there is no issue or code change that could pertain to it. And also, find someone else to confirm this. But it will be hard to fix since BQ´s dervice tree is closed source so we cannot inverstigate or recompile at all to try fixing it, if we would know whats going wrong.

Also those devices are very old, I expect funky batteries happening at some point.

I am pretty sure it's not the battery considering the behaviour and the way and amount I have been using the phone but I know now what I wanted to know : No point in testing or reporting any battery related bugs!

@lakotaubp said in OTA-20 Call for Testing Companion Post:

@nero355 As @Flohack mentioned there have been a few reports on here and Telegram of odd battery behaviour due to age and then failure.
See above!

esoteric

Is anyone else having bluetooth issues? My devices are set to connect automatically, and they do seem to, but the audio never switches over. I have to disconnect, then reconnect to get everything working.
My car, my bluetooth speaker, and my earbuds all have to be manually controlled.
I removed and re-paired to no avail

-pixel 3a xl

flohack

@esoteric Since we did not change anything on the Bluetooth stack thats unlikely to be a regression of OTA-20. Bluetooth in Ubuntu Touch is in general very fragile and prone to errors all over the place. Auto-reconnect only works if you switch on Bluetooth and the devices in the reight order for example. Also, many carkits are not pairable at all. Its a huge mess since over 6 years, but unfortunately we do not have the resources to work on that really much.

esoteric

@flohack I should clarify. Bluetooth pairs, but the audio is stuck on the phone's speaker, instead of the three BT devices I mentioned. I don't see an audio selection menu.
The only way I can resolve is by disconnecting and reconnecting manually. Ota 18 and 19 didn't have this behavior in the same use case

lsitongia

@esoteric, I also see Bluetooth trouble on my Pixel 3a. I can pair, but do not hear any sound through it. I'm testing this using the phone function. I can tap on the speaker icon after I dial, and switch between audio devices. When I switch to bluetooth, I hear nothing, but I can switch to speaker and can hear normally. This is a "JLab BT" headset that is about four years old. Works fine on my Nexus 4 running UT and my Moto G7 running Android 10.

lsitongia

I know this is a old problem, but MMS doesn't send or receive. I'm testing with photos. I've tried with bluetooth and wifi on or off. I just got this Pixel 3a yesterday. MMS had worked with wifi off as described elsewhere by Rik. My phone was probably in the developer channel at that time. Today I decided to reinstall, erasing user data, selecting RC, to really test this and give feedback. I see in Telegram that Rik reported this during the summer and then it looks like it was resolved as not related to wifi. Anyway, from my limited exploration, I see that MMS is problematic. I want to note that MMS works on my Nexus 4 running UT in the developer channel.

Edit: Google Fi SIM

lsitongia

I removed the SIM card and put it back into my daily driver and continued testing on the Pixel 3a using Dekko 2 email. I sent it email from another computer. There were no notifications, by sound, by waking the screen and the toolbar at the top didn't show green in the notification glyph. I switched to the dev channel, and Dekko 2 is behaving normally, with incoming email waking the screen, issuing a sound and showing the green notification glyph at the top. Still, no notification LED. This is a new-to-me phone and I didn't test for the LED on Android before I installed UT.

flohack

@lsitongia Pixel 3a has no physical LED thats the thing...

lsitongia

@flohack Okay, then why does the device page for the phone have a green check mark next to "Notification LED"?
https://devices.ubuntu-touch.io/device/sargo/

oh_the_bob

Hi everyone.
I tested on FP2 rc 2021-W45.
All works fine, only camera is broken.
Camera app is opening but there is only a blackscreen.

flohack

@lsitongia @fredldotme we need to remove the LED from sargo on the devices page then

lsitongia

@flohack, got it. @Fuseteam led me through making the change and submitting it. :grinning_face:

esoteric

Update: so after a couple days of struggle, it started working normally again? Hard reboots didn't help, I did those early on. So randomly decided to start working. Been good for several days now