-
It remains strange. After describing my problems earlier, I left the phone for a few hours. After that I tried again to reproduce the behavior. Since then everything works without reboots...So maybe now I can start testing
-
When I press on a link to send sms in a website the permission is asked but sms does not open. For calls it works
-
@marius-ciclistu I think this also doesn't work on stable? It's not clear what permissions dialog you are speaking of, but messaging-app does not register as a URL handler for
smsprotocol, and therefore there is nothing on the system to handle such URLs. -
@dobey RFC then
-
After my yesterday's post, I tried to reproduce this issue:
https://github.com/ubports/morph-browser/issues/374
After a few seconds, the display froze, and the device went rebooting again.
So I switched to stable again - the device runs without any problems.
Is it maybe possible, that there is a greater issue with this OTA for the Oneplus One? Can somebody confirm this strange behaviour? -
OPO: In contacts, when searching, the keyup trigger does not fire ok, I have to detele and retype many times to get it to work. Also the search is made like 'contact%' and it does not find a contact named 'acontact'. Why not search like '%contact%'?
-
@unisuperbox thank you very much for your answer, and for pointing me to this issue I have not found. It seems to be very complicated to solve...
Since 2021-W07 (17th of February) I didn't get the wifi switch back, except when I got back to stable channel to check on it, and once when rebooting from 2021-W07 to 2021-W08. But at least I've read the workaround to turn on wifi from battery settings, which is quicker than with the terminal
-
Without a way of installing older OTA's I think there are far fewer people willing to test these builds out of fear of being locked into them. If you are on the RC channel when it gets pushed to Stable there is no way back. If you stick with Stable there is no way of testing the newer Stable to see if you are ready to move forward.
I myself love testing things but was only willing to test a little the first couple of days on my daily driver because of all the software not updated to work with the new QT. This is NOT the UT teams fault or responsability, but it is certainly a deterant from using the next release version until the software that people are used to and still need catches up.
This will be made worse with all the breaking changes coming with the 20.04 updates. We need a way of installing older versions. Just a manual way of or by selecting which one to fetch in the installer. We do not need an OTA way.
I have a development device but it doesn't have an OTA or current GSI so I can not test any of these changes.
OnePlus One with UT OTA-15 daily driver. I would be testing the Halium 7.1 port if I could roll back to OTA-15
OnePlus 6T PostmarketOS Custom Gnome on Mainline Kernel -
@antidroid You can always install an older image from the image server by using ubuntu-device-flash.
-
@nikfrager And where do we find this information? This is the first I am hearing this and I have read many people ask how to downgrade without response.
-
@antidroid said in OTA-16 Call for Testing:
because of all the software not updated to work with the new QT.
What software? Most all apps in the store which needed any changes to work were already updated months ago. The majority of webapps that no longer work, were using deprecated API, which we announced would be removing for like a year at this point, and a few months ago announced that OTA-16 would be the stable release it gets removed from.
Unfortunately, there are some late discovered issues in core apps, but we are working to get things fixed as fast as possible. This is why it isn't released yet.
-
@nikfrager said in OTA-16 Call for Testing:
@antidroid You can always install an older image from the image server by using ubuntu-device-flash.
Really? That looks to me like the old Canonical software from 2019, not Ubuntu Touch.
-
@dobey said in OTA-16 Call for Testing:
What software?
I just reinstalled to test again since it has been almost a week since testing last. I am not like most people and I do not use the same apps as most people so my experience will be different than most peoples (ZERO social apps on my phone). From the day the RC was announced and I tested it most of my apps have received updates and the only ones left not working are uWriter and a few games. I am sure others have apps that are no longer maintained that they want to keep using. None of that is really relevant in whether people should be able to install an older version. There can be countless reasons why someone may not want the current version or to skip it.
I can not be the only person that has used an OS past its life because of some personal reason that stopped them from upgrading that outweighed the safety or missing new features.
XDA is riddled with different android versions down to every point release because people want/need a certain version and it is their choice which version they want to run. The developers are then relieved of any responsibility as it pertains to the OS's usability, security or general bugs or problems when someone uses an old version.
OnePlus One with UT OTA-15 daily driver. I would be testing the Halium 7.1 port if I could roll back to OTA-15
OnePlus 6T PostmarketOS Custom Gnome on Mainline Kernel -
@AntiDroid as has been said before, it is possible to install an older image... but it's not easy. You need to use ubuntu-device-flash on an Ubuntu computer (which means downloading a package from repo.ubports.com) or manually stage the files in
/cache/recovery/. I agree that people will want to revert to an older version of the operating system. There just isn't an easy way to do it right now.This is a problem that would need solving in the system-image client on the device first. It needs to be possible to tell it "Install this older version." From there, the interface needs to be implemented.
I'm not sure this is something we'll be able to do in the near future, but it is certainly a change I'd accept. If you've got some Python knowledge, I'd love to show you where to look to implement this in system-image's client.
-
@cliffcoggin Yes, it is (old) Canonical software, but you can use it for UT.
-
@unisuperbox said in OTA-16 Call for Testing:
If you've got some Python knowledge, I'd love to show you where to look to implement this in system-image's client.
It never hurts to point it out. If you look through my github you will see I dabble in everything. And scripting is always easier to figure out than walking in to some huge C++ project with bit of every other language mixed in.
I just read the minutes of the latest news/blog and see this was brought up. No solution but still at least it is being talked about.
-
Won't this command work for switching to old versions?
system-image-cli -b <old build #> -
@kugiigi It should, but I suppose does not. Otherwise it would be the given answer for how to accomplish the task.
-
@antidroid I was simply asking what specifically is broken, so that we can examine and fix problems, if it is our fault. I was not asking or talking about keeping to older versions if you so wish. I just want to know what is actually broken by upgrading to Qt 5.12 so we can either fix things now, or plan some way to have them fixed.
I also was pointing out there are two separate things coming in OTA-16, and that the removal of Oxide is not necessarily related to upgrading to Qt 5.12, thought they both happened at the same time. Oxide is still in the repository though, so currently if anyone does need to use an app based on it (on an armhf device, since there is no Oxide build for arm64), one can do the necessary steps to make their rootfs writable and install it, even though this is not supported, and may be broken by future updates.
-
@dobey As I said after retesting the only important app I have installed that still hasn't been updated and doesn't load is uWriter (and some games like Snowball World).
The uWriter Github repo has had recent work to switch it over to Morph but the open store has not had an update since 2019.
Sorry it was my mistake thinking it was a QT issue since that has been subject of this release and not the fact that oxide had finally been dropped (talked about it coming in the last few announcements). I was mostly using it as an example of big changes that would lead to someone needing/wanting a way of rolling back to an older version.
