No one has another way to check if QT6 is installed?

p.s. I ask this because when I reinstall without wiping, all the apps I've installed are still there.

@wally
If I do a reinstall of 2.x daily (on a phone that is in list 2.) using the installer in order to get the QT 6 Beta AND I do not select the option to wipe, will it preserve the current 1.x version of Morph?

Are there libraries that I can look for using a shell to verify getting the 2.0 Beta (or its daily equivalent)?

Thank you.

Okay, I am going to run 1.x RC on my OnePlus N10, run the gsettings command as above, and wait for notification that 2.x is available.

If our phone is on list 2., how will we know when the new 2.0 is available? By staying on the 1.x RC channel? I’ve been assuming that the upgrade to 2.x will require a reinstall using the installer with a wipe because the partition size changes.

@pparent
I haven’t been able to install 2.x. That error and the log shows it runs out of disk space

Yes, it is in the list of phones that have to be fixed in order to remove it from the list of that will not receive updates. The n10 maintainer has just fixed it.

I’m optimistic that the n10 will start getting 2.x updates installable through the standard installer. Hopefully soon.

@wouterx
This is an aside, but there are a number of phones that do not have enough space to install 24.04-2.x. Would your yaml change work for them? I wonder. Where is that yaml file? How did you decide on that new partition size? Where does it take the space from to make that partition larger? Thank you.

@gpatel-fr
That depends on the phone model, right?

Or is there a way to reset my Oneplus N10 back to a configuration that would let me install 2.x? Ideally without having to reinstall Android.

It doesn't work for me. I haven't been able to install it on my Pixel 3a or Oneplus N10. Both fail the automatic update that occurs after the install when using the installer. Both run out of disk space. 1.x installs fine.

@arubislander
I bought this phone because I'd read about patches for MMS available through the QA Telegram channel. So i originally installed 2.x over Android. I immediately had out-of-space issues when i tried to install the MMS patches. Lionel said in Telegram that they routinely remove unneeded packages in order to make space under 2.x for QA tests.That shouldn't be necessary in order to contribute to QA.

So, there is a known problem with space. My guess is it needs to be expanded. I just saw fredl talk about porting Halium 12 to Pixel 3a and expand the size of root. This looks like a general issue.

There should be a mechanism in the installer or while running UT to free up space. Reinstalling Android and the UT again is a burdensome method. Anyway, that would just get me back to where I started, running 2.x without enough space to do QA.

@oldbutndy Yeah, a saw that, too. In wonder. I’m not in a Telegram channel for the OS itself, so I don’t know what their status reports are or release notes that describe changes. I can’t see what known bugs there are.

(I had reported not enough space on 2.x in Telegram before, but in that case, I was able to install 2.x but ran out of space when installing anything for UBports Quality Assurance.)

I think this phone has a lot of memory and the partition size (or whatever is the case) can be increased for 2.x.

I think there isn't enough space to install 2.x.

I will note that the screen with "Installing update" does come up after installing 1.x stable and booting. So, that's normal.

Bottom line: something is wrong with installing 2.x on OnePlus Nord N10 5G BE2026.

This time I rebooted a couple of times. While running 1.x daily I switched channels to 1.x stable. Rebooted a couple of times. Installed 2.x. Reboot. Again it is "Installing update".

I don't recall ever seeing "Installing update" after installing UT.

Now I'm back to the error "Failed to find block device for partionproduct_a".

So, this process of installing 2.x is unreliable.

When I installed 2.x, upon rebooting, I get "Installing Update". Where is it getting this update? Is that part of the 2.x install?

The Installing Update finished, the phone rebooted, and ended in Recovery mode.

It won't boot past the screen that says "The boot loader is unlocked..." AGAIN. At least I CAN shut it off now. But, it won't boot past that screen.

Installing 1.x again. "Installing Update" again. 1.x is installed.

Maybe the bottom line for all this is that today's daily 2.x is broken or it doesn't work on the N10 now.

Okay, I got back to the point where I could install 1.x and again after booting it up it said it is installing an update. I don't know if this is the daily update from when I started this day. That's when it downloaded the update but I didn't install it.

@oldbutndy I didn't try that, but why I was trying the procedure with unbricking using msmdownloadtool, there was an instruction to hold volume up and down and power together. That seems to have gotten my phone out of that unable-to-power-off mode. I thought for sure I'd try that already, since it's the way to get into the bootloader.

Trying to install 1.x again and the phone is hosed. I can't power it off. It is at screen that show

The boot loader is unlocked...
...
PRESS POWER KEY TO PAUSE BOOT

I hold the power key down for a minute and it doesn't power off.

When I plug it into my KDE desktop in this state I get a KDE alert that says

Halium initrd Failed to boot has been connected

(I can't edit the last post because the button in the lower right that lets you jump to the top or bottom is covering up the controls to like/dislike/...)

I wanted to say that the log file I'm looking at is

/cache/ubuntu_updater.log