How to downgrade OTA-15 ?

stanwood

@povoq So you mean to push an intermediate stable release containing critical patches?
It sounds good, however stable releases are supposed to be fully tested at least 2 weeks before being deployed.
But if a rare case of regression is announced after the deployment of the update, I don't know how is this currently managed.
Potentially this type of problem could become more frequent in the future in view of the increase in the number of supported devices. (?)

domubpkm

@povoq I think you misunderstood me: my goal is to know IF the bug was present one or two versions ago. So this is a bug that we couldn't test because the device was bought at the time of the last OTA that would have caused regressions for many but not all. downgrader for diagnostic purposes and as an help so as to solve the problem !

Fla

@domubpkm said in How to downgrade OTA-15 ?:

The request makes sense to me. I will go even further.
Generally speaking, it would be interesting to be able to reflash the two previous versions STABLE to see if the malfunctions were present in the previous version(s) for such and such / smartphone(s) that we bought late for example.
For me, for example, i would like to test OTA-13 and OTA-14 for cellular data on Volla Phone.

Could this be a credible request for the installer?

You can fix cellular data in Volla by running /usr/share/ofono/scripts/set-context-property 0 Protocol ip.

I tend to agree with @poVoq, if you have problems, contribute to see them fixed for everybody instead of holding upgrades.
Though I understand the point about comparing to stable to see if this is a regression. But for a new phone like Volla, more recent should always mean better.

kugiigi

@fla There is a way to switch to an older version
There's a command for that but I need to look for it

In any case, it would be good to file any issue you're encountering so that they can be investigated and tracked.

UPDATE: Maybe try this? Do this with your own wrist!!!
sudo system-image-cli -b <build number> --progress=dots

AppLee

@domubpkm
I see your point and this is done during the RC stage.
If a bug hasn't been seen during this stage then too bad I guess one would have to switch to devel and maybe an early RC for major issues.

I guess my point of view on this topic is that if a bug is blocking an important feature then the fix could be merged to RC. That can work as a hotfix while waiting for the next Stable OTA.

Just my 2 cents

domubpkm

@fla Thank you for the suggestion. You are close. Just opened https://github.com/ubports/ubuntu-touch/issues/1657 Hope..

mito77

@domubpkm so for use or report on Ubports, Does I need to be advanced user of computer, or linux ? Because, I'm not developper. And I'm not good with computer. I use everyday Archlinux, but I never learn at school how to use computer. I can't create bash line, or code line. And of course, I read a lot of tutorials or watch video on Youtube for beginner on linux. So maybe I need to create movie tutorial for Ubports or write on my blog some tips.
*

list item

domubpkm

@mito77 I'm not sure of the meaning of your question. If i understand it well :
There is no need to be a developer (i am not) even if it can help in understanding, to report (or comment) bugs. ANY non-developer user can participate in bug reporting by opening a free account on Gitlab and/or Github. You must still be able to report the problem encountered and have first verified that a issue is not already open. Additional information (and logs) may be requested by the developer(s) in charge of solving the problem.

mito77

@domubpkm yes it's okay. I create and participate an issue on github ( https://github.com/ubports/ubuntu-touch/issues/1663 ) , for know how to continue with some little bugs. This is not encouraging maybe for developers. But if I can help like that. Why not ? For me, it's a little bit crazy, because I'm realy noob with Ubports. Thank you for your answers and your help. Have a good following in your ideas.

domubpkm

@fla Unfortunately, this very useful command line (thanks again) fixes the internet but doesn't solve the problem of MMS that don't leave (spinning wheel). The APN MMS is well configured though. Should it work with this command line ?
Do you have another patch to try that could fix this MMS issue (assuming that the cause of the MMS issue is similar to the internet cellular data issue) ? Thanks in advance.