Call for testing: Ubuntu Touch 24.04-1.0
-
Yesterday I received the update. After restarting, the phone gets stuck on the startup screen (Android logo). What can I do? Thanks.
-
@ma said in Call for testing: Ubuntu Touch 24.04-1.0:
After restarting, the phone gets stuck on the startup screen (Android logo).
How long did you wait? First boot after upgrading can take considerable time.
Is currently using an Op5t
Also owns an Op1, a BQ E4.5 and an Xperia X, as well as a BQ tablet and a Pinetab2. Please, someone... make it stop. -
@ma You could try installing via the installer.
-
@Moem True. I found it can take several minutes on logo screen. So give it ten minutes.
-
@danfro After a long wait, the Ubuntu Touch boot screen appeared yesterday, followed by the unlock screen. However, the phone could not be unlocked. So, I restarted it by pressing the power button. Then the Android screen appeared, and I waited for about 8 hours.
When I press the power button again and restart the phone, it remains stuck on the Android screen without any changes.
-
Hopefully, we will still get the separate announcement/post about the long wait after the upgrade so that less people will be confused
-
@kugiigi I posted some messages in our main groups. Not sure if an official announcment will be made
-
@ma so if you saw the unlock screen, it kind did install. But obviously something went wrong. I haven't heard of such a case before.
I suggest using the installer and reinstall. Do NOT tick wipe, that will keep all your data.
-
@danfro I was finally able to install the update using the Ubports Installer. However, I also received a message here that an error occurred. I chose the "Ignore" option, and the update was installed—hopefully without errors.
Thank you for your support!
-
@ma Glad it worked so far. But might be worth giving information about that behaviour and the error message to the porter(s) of your device. Sometjing may need fixing.
-
@peat_psuwit do you plan to support pinephone?
UPD: ok, found the issue: https://gitlab.com/ubports/porting/community-ports/pinephone/-/issues/303
-
K Keneda forked this topic
-
A few questions , on Oneplus n10 5g on 24.04 daily , got updates untill revision 315( or 316,or 317) , now says 2025-10-03 , and did delete updates, look like i deleted them all, i wonder if i broke upgrades checker ?
as i am now missing channels options(daily , rc , stable) .
What is latest revision available to this date ?Experimented a lot and installed a lot of app , including Ambot Installer , which seems to partially worked. Also pushed as far as switching to rc and back to daily , and tested one time restore .
Maybe i'ts time to get back to ubports installer ?
Is there a way to find if updater is broke
before going back to the installer for a ''fresh daily'' ?
Bare with the experimenter me .Thank you all devs for ubports + testers !!
-
Just a follow up , did seems to be fixed with installer , back to having options(daily , rc , stable) , now on 2025-10-10 , which would be version 323 .
Let's add a few observations here , on 24.04 Oneplus n10 5g:About this: https://forums.ubports.com/topic/11396/some-notifications-of-apps-missing-under-24.04-1.0/11?_=1760111989969
Got a bubble notification on message , yes @kristatos , fixed & works.
Ubports Installer is ''wonky'' , is it on this peculiar device or all ?
only got this one so you tell me,
it ''Yikes'' ,go with ignore , and it installed ok !!!?!!Applauses² to Ubports small team again ,
claps³ for your works . -
Could there be a more simple ''trackabled'' way of knowing what in updates ?
as here updating to latest , from system device it says:
version 334,
guess its french for revision 334 ?
Looking for that on github , i dont see any of that version 334 !!?!
Not knowing what is updated make it harder to report any problems ...i did encounter a few glitches from different updates .
Not the topic for that ?
any hints or links?
any one ?
thanks all , for all ,
a happy ''end-user'' enjoying UT .Daily Easyos Excalibur
-
@vverve This number is the daily build for your specific device. All devices have their own number, since some changes may only affect one or few devices, but not all. So one device may get a build, others not. Some core changes may affect all devices, so all get a new build.
With a couple of hundred repositories its surely hard to track changes, but for tracking changes I am looking at merged MR's: https://gitlab.com/groups/ubports/development/core/-/merge_requests?scope=all&state=merged
-
Thanks @danfro , that's a helpful hint to know.
