OTA-13 call for testing



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



  • @mariogrip

    Hello,
    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?
    Br.



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



  • @domubpkm
    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:

    1. Pulling «Network» icon, label «Cellular data» is not translated.
    2. 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.



  • @padu said in OTA-13 call for testing:

    OTA-13 RC seems to improve OnePlus One carkit telephony compatibility.

    Oho! That's potentially great news. I will run a test with the Jabra Drive this weekend.



  • Are Pinephone/Pinetab included in OTA-13?
    Do you need testing on these devices?



  • @Thatoo Not really. Right now, the development for the pinephone/pinetab are kind of separate. I think the pinephone has only 5 stable releases. Also in a way, some parts of OTA-13 are already in pinephone's stable release.



  • @Luna said in OTA-13 call for testing:

    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 😕

    When I booted my phone this morning, the Wi-Fi toggle in the indicator menu was back, as for the possibility to activate and deactivate it via system settings. Seems to be fixed.



  • Nexus 4 carkit telephony seems to work fine as well. For incoming calls, ring tone is played via carkit speaker and phone speaker in parallel sometimes.



  • Just a quick comment but can we please avoid turning this into another Bluetooth thread. A quick works better on ...... is fine for here. Longer more detailed discussions can be had on numerous other threads. Thanks.


  • Administrators

    @kugiigi It's a bit special as it uses halium8 so it's not currently in the devel or edge, we are working on getting it on edge as we speak as its currently on its own channel (like the pinephone).



  • @Lakotaubp I have no intention making this a Bluetooth thread in particular. I'm just posting some «general observations I have while testing the current image in the rc channel». Since OTA-13 contains some technical Bluetooth improvements, I think results of testing out their practical impact is relevant for a wider audience. But I may be wrong.

    As for the Nexus 4, it is indeed a huge improvement over OTA-12 (no voice on both ends).


Log in to reply