-
OMG now I tried to reproduce the reboots, opened Dekko, then the Camera for making a small Vid and a picture - then the device froze, the desktop went black and the phone didn't react. I waited several minutes,switched it on again. It died again during the startprocess, the next time it went to pin, then irebooted several times. Then it asked for my wpa passphrase. Now I don't dare to tuch it...
Maybe its the device isself, but I was on "stable" -channel before without any problems.
Should I go back to the stable-channel again? -
@messayisto Hmm, I feel like I got the same blanking desktop and reboot on my Nexus 5. I think started happening yesterday or maybe this week...well last week if it's Sunday now
I'm unsure though but since someone's having a similar issue then maybe it's a valid issue. -
@messayisto
I'm on 2021-W08 with the N5, it runs properly since the update.
I didn't had time to test much, but so far it seems OK. -
@messayisto I have also opo but on rc 93 and 94 it happened to me only once, you should open the store and update all apps also from there.
-
With FP2, with 2021-W08, the toggle for WiFi in the indicator menu isn't there anymore. I had this problem sometimes before the Qt upgrade, but I could solve it by stopping Networkmanager and rebooting.
Now this trick doesn't work anymore, and I have to start wifi with the terminal. I also had to do this wif 2021-W07, but I was hoping it would be solved with the current RC... I don't have this problem on the stable channel. Does anyone report this too ? -
Hi @Luna, I also had this problem on my FP2, but I did before this update too. I got the WiFi toggle back upon reboot, as usual. The issue is filed as https://github.com/ubports/ubuntu-touch/issues/168
-
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.
