24.04-2.x how does it work at this point for you ?

[Vlad Nirky]

@domubpkm
Both are working but still with the old morph support. The QT6 support is coming.
Ambot (and the corner and notch are not working).
I don't use Webber much anymore because native apps like Greenline or Disports work better (in my opinion)

[Linus67]

@Moem How to get Ubuntu Touch 24.04-2.0 ?

[domubpkm]

@Linus67 only using UT installer at this point

[Linus67]

Okay, I've now switched from 1.3 rc to the daily channel. (Pixel 3a)
Version 507
cat /etc/os-release
returns:
Version= "24.04.4 LTS (Noble Numbat)"

My first impressions are all positive.

[lsitongia]

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.

[gpatel-fr]

@domubpkm said:

only using UT installer at this point

err, why fiddling with an Usb cable and a quirky software when having a script launching system-image-cli is a lot faster and easier ?

[domubpkm]

@gpatel-fr I'm talking about flashing os easily, non-technical user friendly. The aim of UT installer.

[gpatel-fr]

@lsitongia said:

Both fail the automatic update that occurs after the install when using the installer. Both run out of disk space.

I think I understand now why for some phones the root partition is larger than needed. I had noticed this on my Fairphone 5.

24.04-1

phablet@ubuntu-phablet:~$ df -m
Filesystem           1M-blocks  Used Available Use% Mounted on
tmpfs                      727     6       722   1% /run
/dev/sda17              214675 30510    181957  15% /userdata
/dev/mapper/system_a      4366  2894      1412  68% /
/dev/loop0                 450   450         0 100% /android
tmpfs                     3634     1      3634   1% /etc/fstab
tmpfs                     3634     1      3634   1% /dev/shm
tmpfs                        5     0         5   0% /run/lock
tmpfs                     3634     0      3634   0% /media
tmpfs                     3634     1      3633   1% /tmp
tmpfs                     3634     0      3634   0% /var/lib/sudo
/dev/mapper/vendor_a      1418  1414         0 100% /android/vendor
/dev/mapper/odm_a            1     1         0 100% /android/odm
/dev/sda15                  12     1        11   2% /android/metadata
android_mnt               3634     0      3634   0% /mnt
/dev/sda6                   27    11        16  42% /mnt/vendor/persist
/dev/sde4                  220   181        40  83% /android/vendor/firmware_mnt
/dev/sde9                   59    31        28  53% /android/vendor/dsp
/dev/sde5                   64     4        61   6% /android/vendor/bt_firmware
/dev/sde23                  30     0        30   0% /mnt/vendor/qmcs
android_apex              3634     0      3634   0% /android/apex
tmpfs                      727     1       727   1% /run/user/32011
/dev/mmcblk1p1           29560     2     29559   1% /media/phablet/6745-7CC0

24/04-2

phablet@ubuntu-phablet:~$ df -m
Filesystem           1M-blocks  Used Available Use% Mounted on
tmpfs                      727     6       722   1% /run
/dev/sda17              214675 30544    181924  15% /userdata
/dev/mapper/system_a      4366  2927      1379  68% /
/dev/loop0                 451   451         0 100% /android
tmpfs                     3634     1      3634   1% /etc/fstab
tmpfs                     3634     1      3634   1% /dev/shm
tmpfs                        5     0         5   0% /run/lock
tmpfs                     3634     0      3634   0% /media
tmpfs                     3634     1      3634   1% /tmp
tmpfs                     3634     0      3634   0% /var/lib/sudo
/dev/mapper/vendor_a      1418  1414         0 100% /android/vendor
/dev/mapper/odm_a            1     1         0 100% /android/odm
/dev/sda15                  12     1        11   2% /android/metadata
android_mnt               3634     0      3634   0% /mnt
/dev/sda6                   27    11        16  42% /mnt/vendor/persist
/dev/sde4                  220   181        40  83% /android/vendor/firmware_mnt
/dev/sde9                   59    31        28  53% /android/vendor/dsp
/dev/sde5                   64     4        61   6% /android/vendor/bt_firmware
/dev/sde23                  30     0        30   0% /mnt/vendor/qmcs
android_apex              3634     0      3634   0% /android/apex
linkerconfig              3634     1      3634   1% /android/linkerconfig
tmpfs                      727     1       727   1% /run/user/32011
/dev/mmcblk1p1           29560     2     29559   1% /media/phablet/6745-7CC0

if system_a was used 100% when using stable, installation of 24.04-2 would fail.

[gpatel-fr]

@domubpkm said:

user friendly. The aim of UT installer.

that's a goal yes. You'll see in this thread that is not always effective on the ground. Convoluted indeed.

[lsitongia]

@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.

[gpatel-fr]

@lsitongia said:000

That depends on the phone model, right?

certainly. Try to use df -m on your phone under 24.04-1.x to see what is the available space. Some phones are said to have a very small rootfs and used almost completely.

@lsitongia said:

is there a way to reset my Oneplus N10 back to a configuration that would let me install 2.x?

well, I think ro remember from a Q&A that there are efforts to allow the instaljer to resize partitions. I have no idea how all of this work.