OTA-13 call for testing
-
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.
-
@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.
-
@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).
-
@padu That comment was not aimed at anyone in particular. Just a bit of a pointer. There has been a lot of Bluetooth action on the forum of late and this was just a general re direction.
-
Don't know if this would better be tracked in GitHub bug Add birthday field to contact #128. When adding a birthday to a contact, in the item drop down list translation is missing for «birthday».
Tested with OnePlus One and several system languages.
-
Another one from the contacts app: swipe actions are not translated.
-
@mariogrip I have Oneplus 3T and everything work fine,but camera does not work, only with gsdroid, and the videos are frozen
-
Same here on OP 3T
-
@3T_Ed, @portu51, it's a known bug for your specific device.
It has nothing to do with OTA13.
Check out what needs testing on github: https://github.com/orgs/ubports/projects/17 -
@AppLee : Thanks, I was aware of that fact, just confirming. I wish the bug would have gotten more priority that's all....
-
@3T_Ed
Priority from whom ?It's a community port, so it depends on the will and time from volunteers.
If someone considers it too hard to solve, they won"t do it.The UBports foundation integrates the work done if it is advanced enough. Support is provided by the community.
You probably already know that but what is suggested in your comment is that there is some kind of authority willingly blocking efforts on this issue.
There is nothing to be done except wait until a good soul takes upon itself to try and fix it. -
@AppLee
I know it works that way and I'm grateful to all developers the 3T has come this far. I Would love to use this device as my daily driver, not having that native camera app working is just frustrating..... If I'd have the skills necessary to fix this issue nothing could stop me, especially since it seems to be working fine on the majority of UT supported devices.It wasn't my intention to bring up the issue in this thread, Iet's leave it to this.
