Important Update: /e/OS is moving from AOSP 13 to AOSP 14 for 100 Community devices

/e/OS Smartphone Operating System Development Updates
21

From what I understand from Manoj’s posts in this thread it is not clear yet whether every official- upgrade will be OTA. If technically possible: Yes (otherwise: No).
No ETAs have been shared so far.

For being able to receive OTA-upgrades for your community-FP3 in general you need to change over to the same official-version first anyways.

(Edit: Not sure though whether it is very likely or not there will be another upgrade to 15 or beyond for the FP3 AND future updates for community are likely to be OTA as well … so not sure what’s better or less prone to being time-consuming for your case: manual upgrade or manual change to official …)

1 Like
22

But that’s exactly what I want to do, see above. The obstacle here is that, as far as I understand, Rollback Protection prevents me from installing IMG-e-2.6.3-t-20241217455358-official-FP3, because I am already on IMG-e-2.6.4-t-20250103459146-community-FP3.

So I either have to wait for U Official or for the T Official version to overtake the Community version. Even if OTA Upgrades are not necessarily provided in the future, I at least could do a “dirty” upgrade, as in the past on the Community branch, which would be much less complex :innocent:.

Regarding your Edit: OTA Community Upgrades would be great, but let’s see how things work out. The (Android and /e/OS) future is unwritten, policies and procedures have changed in the past and will in the future :wink:.

.

1 Like
23

Just to avoid misunderstanding: I meant to say that in case You do a manual upgrade (T → U) for the installed community-build … I’d expect that the following community-updates will come OTA (they do least for my pixel4a, might be different for the FP3). And since it is unclear whether there will be further upgrades for the device (like U → V…) anyways, it might just be a reasonable route to go…

24

This problem has been discussed on the Forum before, maybe try to add a comment in one of thoose.

25

All relevant topics are closed due to inactivity.

OMG, I was lucky enough to have some qualcomm flashing tools, I was able to upload original Fairphone OS and fixed the bootloader, now I can explain some stuff so:
Devices mentioned which will have an upgrade to U will have an OFFICIAL version of U. COMMUNITY versions are lacking certificates which are allowing to lock the bootloader.

To upgrade, even manually, we need to wait for U to be OFFICIAL on each device.

2 Likes
26

I’m really delighted for you! :partying_face:

Oh, that’s news to me. I’m not quite sure if that’s true in any case, but since I have an unlocked bootloader on my FP3 and want to pass it over locked, it’s a second reason to switch to Official on that occasion.

Anyway, has anyone any info about the ETA of U Official for FP3? Or about why there is not a single device in the “Testing” segment of “OS OTA Related Information”? After all, FP3 was also sold via Murena. @Manoj?
(EDIT: I know this is not the right place for the questions above, please everyone ignore at will. I will ask again in the upcoming “Week 3, 2025: Development and Testing Updates”.)

27

Totally confused…all I came to the forums for was to see if the Files feature is sorted out and now this…

28

oh really? It doesn’t say that in the installation guide (e.g. FP5 - at the bottom of the page)
I guess it should then be mentioned in the install guide because I recently ran into this issue

29

This topic was automatically closed after 7 days. New replies are no longer allowed.