@Linus67 said:

In that sense, it could very well be an issue that was triggered by the installation of 24.02

It's a dekko problem referenced on the gitlab repo, see the links I provided.

@Linus67 said:

it's not a problem specific to 24.04-2.x.

if you care about that, you can add your voice to this issue. Since 6 years it has been opened, there is not a single 'like' button clicked.

@Linus67 said:

Dekko 2 -> Forwards emails, but without attachments

I tested this and can confirm it... well, I'm currently on 24.04-1.3 so is this a 24.04-2.x problem ? No it's not.

• billie
• billie2
• pro1x
• miatoll (mine)
• cheeseburger
• dumpling
• enchilada
• FP3
• sargo
• X605

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

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.

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

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

My first impressions are all positive.

@pparent said:

If someone has tested maybe you can say if it is better now.

you posted this while I was laboriously using the OSK in intouch to say that no, it's not.