MMS users: call for testing

lduboeuf

@jezek just as a reminder, the issue that i've found last time:
https://github.com/ubports/nuntium/pull/8#issuecomment-861480575

Emphrath

@jezek I don't use that phone, and it's just sitting there with no wifi or cellular, so I guess what you'll see in the logs will be rather plain, mostly background daemon routines. I'll try to get them tonight. Now for the questions:
-I think I sent four mms in total and all of them displayed this behavior.
-I did reboot, since ubports-qa explicitly asked me to (and you did as well) but I saw some errors while passing the commands. I can't remember properly, but sth about sth not being sandboxed, and also about the system being ro... I didn't have to make it
rw beforehand, right ? Anyway i'll get you these errors asap
-no message got lost

lduboeuf

@emphrath ubports-qa script often output errors even if ok

@jezek it seems nuntium received two wap push don't you think ? That could explain the two mms notif.
In case of bad signal if the wap push couldn't be acknowledged, the provider might send it twice t

Emphrath

@lduboeuf Quite frankly I wouldn't look any further. My fairphone has so many hardware issues it's hard to get a proper idea about the culprit - noticeably network issues, so...

lduboeuf

For the use case "cellular data off", it is working nicely except when i'm with bad signal ( see issue above ) .

This is already a huge step for MMS users, in its worst case scenario we will have the same state as it is today on Devel/RC/Stable ( just ask user to resend)

jezek

@lduboeuf said in MMS users: call for testing:

For the use case "cellular data off", it is working nicely except when i'm with bad signal ( see issue above ) .
This is already a huge step for MMS users, in its worst case scenario we will have the same state as it is today on Devel/RC/Stable ( just ask user to resend)

I think it is not a showstopper for deploying to next OTA. It's working better than before and there are no regressions. Also it will motivate me more to fix the bad signal issues, when the changes land to stable. I will definitely tackle the issues, but I had to change my HW and installed manjaro on it and now I have a little fight with crossbuilder and the lack of apt and dpkg[-architecture,-parsechangelog] commands on the system.

Thank you all for support.

jezek

I've discovered, that the patches are already in RC, so if you are on RC channel (and dev channel too), there is no need to apply the above mentioned ubports-qa commands. This also means that the patches will probably be in the next OTA. Just saying. I'm happy. Thank you all.

I've been wrong. Read furher, why.

AppLee

@jezek said in MMS users: call for testing:

Thank you all.

Thank YOU :thumbs_up:

lduboeuf

@jezek humm i probably miss something, i don't see the PR already merged

jezek

@lduboeuf Or am I wrong? Is there a possibility that the patch is not in RC (and dev) and the applied ubports-qa changes persisted 2 RC upgrades and I drew a bad conclusion? Can anyone answer this conundrum, or do I have to do full reinstall to check?

lduboeuf

@jezek

I'm not 100% sure, but debian packages could be not totally overwritten. I already noticed that when working on Lomiri, where RC or devel updates didn't overwrites my modified files. It would overwrite it though if the same file was modified.

jezek

So I red the OTA-19 call for testing and after browsing though the github QA page I have come to the conclusion, that I've been definitely wrong about the patch landing in RC and maybe in OTA-19 update. I'm sorry for putting your (and my) hopes up. Maybe next time.

Does anyone know how to be in the next OTA update?

lduboeuf

@jezek

Does anyone know how to be in the next OTA update?

idk, maybe @UniSuperBox or @Flohack can say ?

Keneda

@jezek said in MMS users: call for testing:

Does anyone know how to be in the next OTA update?

Very sad you're not in OTA 19 as MMS is one of smartphones key features regarding phone part...

flohack

Well there is always a next OTA
If you want to make sure your stuff is in, best is at the beginning of a cycle to drive this topic forward. We have reduced personnel these days, its easy that stuff slips...

domubpkm

@jezek Such your personal investment in the essential MMS reliability mechanism is worth this very usefull nechanism be incorporating as soon as possible.

Keneda

@lduboeuf said in MMS users: call for testing:

@keneda no idea

Now we know, so sad...

jezek

@flohack said in MMS users: call for testing:

Well there is always a next OTA
If you want to make sure your stuff is in, best is at the beginning of a cycle to drive this topic forward. We have reduced personnel these days, its easy that stuff slips...

OK, the OTA-20 cycle starts around these days. Where to push, to land the MMS patch in OTA-20? Thanks.

flohack

@jezek its more than one patch probably, @lduboeuf can propose the order - its a bit delicate to not make it wrong.

lduboeuf

@flohack the initial issue ( amongst others ) is here:
https://github.com/ubports/ubuntu-touch/issues/17

The top related PR is in messaging-app https://github.com/ubports/messaging-app/pull/260 and you can see other pre-required
PRs in the comment in the correct order.

[Edit]:
Well the very first issue post is here https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1603957

I think you can add it to your tweet :)...
That time please thanks @jezek