OTA-13 call for testing

3T_Ed

Same here on OP 3T

AppLee

@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

3T_Ed

@AppLee : Thanks, I was aware of that fact, just confirming. I wish the bug would have gotten more priority that's all....

AppLee

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

3T_Ed

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

Moem

@padu said in OTA-13 call for testing:

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

Unfortunately I can't reproduce this (with OpO and Jabra Drive carkit). Still no dice.

padu

@Moem said in OTA-13 call for testing:

Unfortunately I can't reproduce this (with OpO and Jabra Drive carkit). Still no dice.

I have opened a new topic about Bluetooth findings with OTA-13 (rc).

Fla

@mariogrip I did find a regression: I am not able to forward SMS anymore. When swipping a message in a conversation to the left and then tapping the "forward" icon, the app goes back to the conversation list but the new message screen with the prefilled text doesn't open. Fairphone 2 last RC.

AppLee

@Fla, @mariogrip
I can confirm this behavior with Nexus5.

Fla

pinging @lduboeuf on this one as he touched the SMS app in that release.

lduboeuf

@Fla
Filed an issue in messaging-app: https://github.com/ubports/messaging-app/issues/230
and a fix here: https://github.com/ubports/messaging-app/pull/231

But i'm afraid it won't land into OTA-13 sorry for that. As a workaround copy/paste should work

Fla

@lduboeuf said in OTA-13 call for testing:

But i'm afraid it won't land into OTA-13 sorry for that

I noticed a few weeks ago already, I should have reported it sooner, sorry.

However that looks like a blocker for me, I don't see all UT users with a regression like this one waiting for OTA-14... Especially if you already have a fix for it. But I guess that'd be @UBportsNews choice.

UBportsNews

@Fla Sorry not sure what you mean. We don't influence what is pushed through the OTA process. There is an update listed in the github link though https://github.com/ubports/messaging-app/issues/230 maybe @universalSuperbox knows more.

lduboeuf

@Fla
Yes, we are lucky, it is accepted for OTA-13

Fla

And the build is already pushed over the air, I now have the last RC and it fixes the problem. That's awesome, thank you @lduboeuf and @UniSuperBox !

UniSuperBox

Due to the need to release a new RC image and the tickets still waiting in the QA column, release has been pushed from Friday, September 4 to Wednesday, September 9.

lduboeuf

@UniSuperBox That is a wise decision, the call for testing was way too short before releasing

UniSuperBox

A critical issue was found in https://github.com/ubports/ubuntu-touch/issues/1556, "Text messages do not wake the phone."

Fixing this issue, releasing the fix into devel, and testing it for inclusion to rc is our highest priority. But given the high profile nature of the issue, we will likely not feel safe in releasing an RC before Wednesday, and we will definitely not feel safe releasing to Stable until after the RC is released and tested.

For that reason, Ubuntu Touch OTA-13 is again delayed, this time at least to September 16. We may need to further delay if the issue is not fixed in time.

Keneda

@UniSuperBox
Take the time you need to fix this without braking anything else, we have time...

Moem

@UniSuperBox We prefer a good release to a fast one!