ubuntu-touch
ubuntu-touch copied to clipboard
ubports
Roll back updates
We need a way to roll back updates. Since updating to OTA-21 I have encountered three bugs of which two make the phone unusable compared to on OTA-20.
Please is there a way to install OTA-20? I do not care if it takes terminal usage I just need a working phone.
The first two are the ones that make the phone unusable currently.
Call volume not adjustable and REALLY loud (Loud enough to use as a speaker phone, on Speaker phone is changes to the bottom speaker and gets even louder) https://github.com/ubports/ubuntu-touch/issues/1749
Auto brightness minimum level https://github.com/ubports/ubuntu-touch/issues/1905
Morph Keyboard https://github.com/ubports/ubuntu-touch/issues/1907
Hi, you can open an issue on 6T port repo for UT: https://gitlab.com/groups/ubports/community-ports/android9/oneplus-6/-/issues.
Thank you!
@Intrinsically-Sublime I've got an 6T myself volume calls are ok, same for the bottom spearkers. Also more two people confirmed it is working as expected. Tested on Portugal and Spain networks with SIM card in slot 2.
Well that makes things worse. I have tried on Stable, RC and Development and I get the same results on all channels and it did work before OTA-21.
My phone is an A6013 8GB 256GB in Canada and I am using slot 2.
Do you know which logs I should be collecting for such a problem?
I will log an issue on gitlab once I have some logs to attach.
That issue is fixed for the Google Pixel3a, maybe it can help other porters to accomplish the same. Idk which logs may be useful for this situation.
You can always open the issue there and ask the ports which logs they may find interesting, otherwise you can join the telegram group for 6T: https://t.me/ubports_op6
Hi @Intrinsically-Sublime, thank you for your feedback.
I agree that the following things are true:
- The issues you are experiencing are real, frustrating, and should be fixed
- Being able to roll back Ubuntu Touch to an earlier version to avoid breakage seems enticing
However, I would like to balance these with more true things:
- You received this software for no charge, out of the goodness of our hearts
- The people working on this software are primarily volunteers
- The total time spent answering your requests so far would cost any normal US organization over $400 in developer and support time
- In the case of the Morph Browser change, we asked for opinions and heard silence.
- We asked people to test OTA-21 before it appeared, and the result was either silence or "all good!"
The last two are particularly poignant: we had no idea that any of your issues were issues until you posted them.
I agree; it is frustrating that your phone is unusable with OTA-21. I also agree that it would be easy for you to roll back to OTA-20 and ignore the problems as long as possible. But this won't really help: without your testing, we would have never known about these problems. So you would have just postponed your experience: sure, you can roll back now and everything is better. But what happens in a month when we release OTA-22 with the same problems? And OTA-23? What happens when app developers make an app you use incompatible with OTA-20 because OTA-23 is out? Now you have a choice between accepting the problems that make your phone unusable or getting rid of the app you rely on.
We need people like you: People who are interested in the success of the software, enough to let us know when things are broken. We need you to be using newer versions of Ubuntu Touch, not older. That way you can warn us about problems before they get released to stable. Importantly: We would not have released OTA-21 if we knew it broke call audio on the OnePlus 6T.
This is especially important for devices like the OnePlus 6T, which have only a single person or a tiny group of unpaid people working on them. I don't own an OP6T, nor does anyone on my team. There was absolutely no way we would have ever known about this if it was not for you.
This is not a WONTFIX message. I think that a rollback is a good feature that we should implement in Ubuntu Touch for when things slip through. But it will not be implemented faster than the fix for the issues you've posted, and it will not resolve the underlying problem.
@UniversalSuperBox Thank you for your reply. If what I have said sounds like a demand I am sorry. I am an Aspie and communicating is not my strong point.
The issue is not with problems but rather the fact that anyone that wants to run stable on a daily phone is the one at risk rather than the people running RC or development. The people running RC or development all the time can move channels when a serious bug comes up but the people running the channel marked stable end up with the issues.
So if bugs need to be reported before they reach stable and get locked in for months and testing is only a (week?) long than everyone needs to run RC all the time and treat Stable as a safety net which I would guess is the way almost every developer involved uses UT.
I have no issues reporting bugs as soon as I find them and I am willing to provide information and logs as needed which is what I have been attempting to do but I would rather not have to run on the edge all the time.
Maybe a way to deal with this is to show a notification when an RC candidate comes out for testing that pops up on the device the way an update notification does. This would allow a lot more people to test that are not involved in development and get bugs reported faster.
RANT: Everyone always says things like "it is open source you can change it yourself" and then when you ask for information where to find the correct files, where things are stored or where to find resources you get vague answers making it near impossible for an outsider to get involved (simply because those involved in any project are so close they assume everyone knows what they are talking about and they are not to blame). Or worse you get told to join a Matrix or Discord etc channel where the question has been asked before and answered but it is not indexed on the web by search engines so can not be found by those searching for the answer. To me I see those places as black holes of information that only help a small group and end up making all the work fall on that small group since those looking to get involved can not find the information and give up. For me being an Aspie and not being social I will never join a group like those and I am stuck with publicly available information and official docs which I am sure from our interactions you can see is for the best.
The stable release cadence is ideally four to six weeks, not months at a time. Testing occupies two weeks of the release cycle and is announced on our blog and social media, with accompanying project boards on GitHub and GitLab and an accompanying forum post. Saying that any issue is locked in for months, or that contribution data is locked behind a platform, is a gross overstatement.
The reality is that this is software being developed at the redline: too many things to do and not enough resources. In that manner, everyone is at risk for bugs, not just people on stable, rc, or devel. In this specific case, everyone should be seeing the same bugs as you (which Ivo has already commented is not the case, and you'll need to help him to get more information). The bug had to flow from devel, to rc, to stable.
We need your help to make sure that people who are on stable aren't at risk for bugs. If you wait for someone else to do it, then you are by default the person at risk. This is a classic "tragedy of the commons" problem. Will you be the one to break that neverending cycle?
I noticed that you haven't filed a new issue report for the call volume issue on the OnePlus 6T as Ivo requested. Could you please do that, so he can work with you to get more data (especially as to why you're the only person reporting this problem so far)? Then if you run the rc or devel channels, you'll receive the fix faster than anyone else too!
@UniversalSuperBox I will file the issue soon.
As for all the places the releases are announced I have to say I do not see any of them. I do not participate in any forms of social media at all. So if I am to help report bugs before stable I have to run RC and not have a stable phone. This makes the stable branch moot.
Maybe the release frequency is the issue if you say it is really often. I have been a linux user for 15 years and I always end up back running Ubuntu after trying other distros because it is the most stable. I can live with things being behind even if running ubuntu means needing to strip the distro of all the Ubuntu modifications to get to Gnome Vanilla like I would on most other distros just a few versions behind. At least it is stable and if anything breaks I can always roll back individual packages or even run a ten year old distro if I want.
Here is a another scenario. Lets say you are testing RC and find a bug right before it gets pushed to stable. You report the bug and then stable gets released before it is fixed because it it deemed unimportant or only effecting you. You have stayed on Stable because the bug is one you can not live with but you can no longer test RC or development to help with possible fixes because you can NEVER get back to the old stable that works for you. This means you no longer help and stay on the working one forever.
My oneplus one is on a very old release because of that exact scenario and I keep it as a WORKING backup even though newer may be better on it but the risk is far too high to test a newer release and risk breaking my backup. I do not even remember what the issue was and it had been reported by others so I have no way of tracking it.
I understand why someone would want to roll back their device, and I have never said that it is a bad idea. You don't have to convince me of the merit of rollbacks and running old software. I get it.
And I suppose you are right. People who do not want to help will continue running old software releases regardless of what we do.
But if you want to help Ubuntu Touch by reporting bugs and giving feedback on all the things you don't like, it is a bad idea for you to roll back to an old version or even to run stable instead of running something newer than stable.
You, of course, are free to do whatever you want, but that is what I'd encourage you.
Eventually, there will be a way to roll back to a previous release of Ubuntu Touch. But it won't be before the issues you're experiencing right now are fixed. We can talk about designs for a rollback system another time of course.
Everyone always says things like "it is open source you can change it yourself" and then when you ask for information where to find the correct files, where things are stored or where to find resources you get vague answers making it near impossible for an outsider to get involved (simply because those involved in any project are so close they assume everyone knows what they are talking about and they are not to blame). Or worse you get told to join a Matrix or Discord etc channel where the question has been asked before and answered but it is not indexed on the web by search engines so can not be found by those searching for the answer. To me I see those places as black holes of information that only help a small group and end up making all the work fall on that small group since those looking to get involved can not find the information and give up.
I agree with this so much! I don't blame anyone. When you are in "the inner circle", all your energy goes into the actual building, the writing of code. But I totally feel you on this one.
Everyone always says things like "it is open source you can change it yourself" and then when you ask for information where to find the correct files, where things are stored or where to find resources you get vague answers making it near impossible for an outsider to get involved (simply because those involved in any project are so close they assume everyone knows what they are talking about and they are not to blame). Or worse you get told to join a Matrix or Discord etc channel where the question has been asked before and answered but it is not indexed on the web by search engines so can not be found by those searching for the answer. To me I see those places as black holes of information that only help a small group and end up making all the work fall on that small group since those looking to get involved can not find the information and give up.
I agree with this so much! I don't blame anyone. When you are in "the inner circle", all your energy goes into the actual building, the writing of code. But I totally feel you on this one.
There's no one to blame. We always try help as much as possible. There are things, sometimes, that we don't know ourselves.
We do as much we can, sure there's space for improvements.
In this case, we've asked the person to open the issue report in gitLab because is the place where the repo of the 6T is living. So for this time, the user came in here, was pointed in the correct direction, he opened the issue and one of the problems got already fixed. His action was essential, a contribution was made. It's always like this? No. But neither is like was described above.