OTA-20 Call for Testing Companion Post
-
@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.
-
@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 -
@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.
-
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
-
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.
-
@lsitongia Pixel 3a has no physical LED
thats the thing... -
@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/ -
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. -
@lsitongia @fredldotme we need to remove the LED from sargo on the devices page then
-
-
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
-
Thank you all! OTA-20 rollout has started, so nothing to see here anymore
-
A arubislander locked this topic on
