Week 52, 2025: Development and Testing Updates

Which device are you checking for?

1 Like

:man_facepalming: I am sorry, I completely forgot to mention my device. It is a OnePlus 6 (enchilada), currently with /e/OS A15 3.2.
I have also edited the original post.

Checking. Will update.

Update: enchilada A15 build failed. The team will try to make another build and release with v3.4

1 Like

Thanks! I finally managed to lock the bootloader thanks to your suggestion!
What I had to do:

Reinstall stock OS over CLI - and making sure the phone does NOT boot into the OS (e.g. stopping the boot process when the message is displayed after the reboot, that ā€œthe bootloader is unlocked, press power button to pauseā€. Then with power button hold press, and volume down enter bootloader.

There I then got: fastboot flashing get_unlock_ability return 1

Then I had to flash /e/ 3.3V again, and once more make sure that the device does not even once boot into the OS.

I then had /e/ installed and got the fastboot flashing get_unlock_ability return 1

I could lock the bootloader then according to the manual without issues

2 Likes

:christmas_tree: Merry Christmas and happy holidays all :christmas_tree:

29 Likes

Dear anitaz, thank you very much for publishing, helps me a lot to dare updating my s7 after the hollydays! :grinning_face:

1 Like

:stop_sign: These devices will no longer get /e/OS builds. We are dropping them from our release system. We tried to build v3.3 for them but the builds fail. We even tried with the Minimal Apps configuration but did not succeed.

Vendor Device Name CodeName
Google Pixel XL 2 taimen
Google Pixel 2 walleye
Motorola Moto G7 Power ocean
Motorola Moto G6 Plus evert

Sorry for my maybe stupid suggestion, because I’m not a developer. Have you tried with no apps at all, to see if it can be updated or installed separately without updating, just booting?

I can probably buy those phones, that’s why I’m asking if I can help to be a guinea pig.

The intended audience of /e/OS has always been the average non-technical users who would require a standard set of application to use out of the box. Users who are more technically inclined have used adb commands to remove default apps but there is a certain risk in that mode as some core functionality breaks.

1 Like

This is the second time that I have owned a device where system is too small for /e/OS.

For ocean listed above e-3.2 was built as eng MINIMAL_APPS and there was some headroom

~$ adb shell
ocean:/ $ df -h /
Filesystem            Size Used Avail Use% Mounted on
/dev/block/mmcblk0p63 2.6G 2.4G  145M  95% /

but I guess e-3.3 is a bit larger. A generous spirited offer but any amount of testing cannot create space for a build with Advanced features installed to system.

Would ofc be LineageOS. Lineage4microG (after their downtime clears) may be available for some affected devices.

1 Like

Am I understanding correctly, the system uses 2.6 GB?

My FP6 uses, when I check storage in the settings 32 GB. I am wondering why it its so huge (reported on gitlab).

Yes, that is what adb shell → $ df -h / reports on my device is as @Didou’s (thanks) post below (2.4G). Others could try! It will vary by device (it is also possible that certain devices take extra resources to achieve a15 but I did no research on a build machine yet).

Plenty of apps and Advanced features all installed to system.

1 Like

Let’s try this with my Galaxy S7 herolte, freshly passed on e3.3

heroltexx:/ $ df -h /

Filesystem Size Used Avail Use% Mounted on
/dev/block/sda14 4.1G 2.6G 1.4G 66% /system/etc/gps_debug.conf
1 Like

Ouch ! …

e-3.3-a15-FP3

piero@HP-p6-2038fr:~$ adb shell
FP3:/ $ df -h /  
Filesystem            Size Used Avail Use% Mounted on
/dev/block/mmcblk0p30 2.9G 2.7G  106M  97% /

i hope dynamic partition feature could allow to enlarge the /system partition
yes, up to
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3221225472
so 3,2 Go

Pire !
OnePlusNord avicii e3.3

girafe@girafe-HP-G72-Notebook-PC:~$ adb shell
OnePlusNord:/ $ df -h /
Filesystem       Size Used Avail Use% Mounted on
/dev/block/dm-17 1.4G 1.4G     0 100% /

my understanding is that the system use

2.4G

out of a

2.6G

Filesystem

2 Likes

Thanks for detailed reply. I don’t own those phones, just wanted to help to buy one.

The same output with updated v3.3:

āÆ adb shell
heroltexx:/ $ df -h /
Filesystem       Size Used Avail Use% Mounted on
/dev/block/sda14 4.1G 2.6G  1.4G  66% /system/etc/gps_debug.conf
1 Like

Hi @Manoj can you give a status on UP-implementation as it disappeared from device settings in 3.3 and seems to be buggy?

1 Like