OTA-13 call for testing
The expected release date for Ubuntu Touch OTA-13 is
Friday, Sep 4 Wednesday, September 9Monday, September 21.
This forum post is a companion to the upcoming OTA-13 call for testing blog post.
Please post any general observations you have while testing the current image in the rc channel, as compared to OTA-12, in this thread. The current release candidate (rc) is
If you have any comments on any of the specific issues in the OTA-13 tracker, please post them in the issue thread so they are easier to track. OTA-13 tracker: https://github.com/orgs/ubports/projects/17
Please note that only critical and security fixes will be able to enter OTA-13 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.
A big thank you to everyone that made this possible! I'm super happy to see these release being bigger and bigger with contribution from so many beautiful people! Thank you everyone!
- Much love!
Edit 2: On the 7th of September the release date for OTA-13 was moved from the 9th of September to the 16th of September
Edit 3: On the 15th of September the release date of OTA-13 was moved from the 16th of September to the 21st of September.
This is the link to the OTA-13 blog post https://ubports.com/blog/ubports-blogs-news-1/post/call-for-testing-ubuntu-touch-ota-13-3717 if needed.
This post is deleted!
OSK is missing the word suggestion, even though is activated in the settings.
This post is deleted!
Issue that seems to be fixed: the screen alignement after reboot is ok now.
@C0n57an71n I can confirm the word ribbon not present in the browser. I checked it on my device with OTA-12 and in it's displayed there. Probably caused by the QtWebEngine upgrade. Or perhaps, intentionally disabled since it's broken in QtWebEngine anyway? The keyboard has a few known issues since the migration from Oxide.
is this also relevant for VollaPhones? Because, these devices might be on channel "Edge" .
If there is a need for testing here, how to switch to RC or do we receive the corrections?
@Tellina System Settings, Updates, Update settings, Channels should do it.
@Tellina Volla Phone might not be relevant for OTA-13 since OTA-12 wasn't really available on it, or does it? Does it already have the stable channel?
@kugiigi No only edge channel
What is the nature of the collaboration between the UBports team and the Volla team concerning the porting of UT ? To what extent will the Volla updates follow the cycle of regular UT updates? If not here, this is a question for the Q and A.
Hi, I installed the image for volla phone on my device. So my request is not related to the volla project.
But ok, I have learned that because OTA-12 was not existing for the underlying volla hardware a test for OTA-13 is not relevant.
@manland Thanks for your clarification.
@kugiigi n danger of going very Off Topic for here but if Volla is arm 64 then it should now have devel and OTA-13 will be the first stable release for arm64.https://forums.ubports.com/topic/4816/arm64-devices-have-devel
I noticed some missing translations when pulling from indicator menu:
- Pulling «Network» icon, label «Cellular data» is not translated.
- Pulling «System» icon, label «Report a bug» is not translated.
Tested with Nexus 5, OnePlus One and various languages.
Tested with device FP2, I found out that the possibility to connect and disconnect to Wi-Fi via indicator menu or Wi-Fi settings went away. I can only do it via the terminal Here's the log if relevant : http://paste.ubuntu.com/p/dj7zrnK523.
And as for the translations, I noticed this in the address book app :
- "Import from vcard file" isn't translated
- "Export all contacts" isn't translated as well
But in general, it seems that the OS runs faster, which is really appreciable, and it becomes better and better with time passing. Thanks for the huge work
OTA-13 RC seems to improve OnePlus One carkit telephony compatibility. With OTA-12 I was able to connect via HFP. During calls, voice was transmitted only for a second or less. After that, there was only silence.
With OTA-13 RC, incoming and outgoing calls work just fine. (Didn't do too extensive tests, but I did several calls in succession.)
I didn't test Nexus 5 with OTA-12, but with OTA-13 RC only. For incoming as well as outgoing calls, carkit speakers play only metallic sound. On the remote end however, voice is always OK. That is, outgoing audio routing is OK, whereas incoming audio routing is bad.
Tested with Volkswagen Composition Media carkit.
Are Pinephone/Pinetab included in OTA-13?
Do you need testing on these devices?