Feedback for v3.6

/e/OS Smartphone Operating System Build Feedback
23

Motorola

Edge (2021)

Berina

/e/OS 3.5a15

Not rooted

All is well.

24
  1. Fairphone
  2. Fairphone 5
  3. FP5
  4. 3.5 stable
  5. Not rooted

Issue:

No mobile data after Update to 3.6.

Resetting mobile AP to defaults and toggling SIM on/off did not work. No cellular outtage, secondary SIM on my notebook from the same provider works. Provider is 1&1 (Germany).

Solution:

After 3rd reboot cellular data works again directly after unlocking.

I was scared there for a moment one day away from my vacation ! :zany_face:

2 Likes
25

Vendor Name: Fairphone
Device Name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: 3.5-t-official-FP3
Not rooted

No issues so far. Thanks to the team!

26

All fine on Google Pixel 5 redfin (not rooted) after update from 3.5-t to 3.6-t.

I needed a second reboot after the update to bring back full functionality, but this is not new.

28
  1. Vendor Name: FAIRPHONE
  2. Device name: Le Fairphone (Gen. 6)
  3. Device CodeName : FP6
  4. Version of /e/OS or Stock which existed previously: 3.5 a15 official
  5. Is the device Rooted / Not rooted: not rooted
29
  1. Vendor Name: Fairphone
  2. Device name: FP6
  3. Device CodeName : FP6
  4. Version of /e/OS or Stock which existed previously: 3.5 a15 official
  5. Is the device Rooted / Not rooted: not rooted

Still A15 for now. A16 not coming with 3.6 ?

30

The A16 builds are still being built. There is a list of about 200 community devices for which we are attempting A16. I shall share the final list once the build process is complete. Some device builds fail due to various reasons.

4 Likes
31

Teracube 2e (emerald)

Android 15

Previous version: 3.5. Stable emerald

Updated to current version:

3.6-a15-20260312593772-official-emerald

Not Rooted

The phone is working well with security patch March 2026

BP1A.250505.005

Many thanks to all who made this happen.

The Teracube 2e is now a more secure up-to date device

Bill D.

1 Like
32

So for some devices, there will be 2 official variants of 3.6, namely 3.6-a15 and 3.6-a16?

Is there a recommended upgrade path from 3.5-a15? Should we first install 3.6-a15 over it and then 3.6-a16 when it’s released? Or is it irrelevant, and we can wait a few more days to go directly from 3.5-a15 to 3.6-a16?

Also, when upgrading from A15 to A16, are the security dates good enough (apart), that nobody runs into the downgrade check?

33

The A16 builds as mentioned are still running. It may fail for some devices and also take a couple of days to be release. Most probably early next week they will start showing up. Since it will be a manual upgrade better to install first the A15 or whichever version build is available for your device with v3.6 and then do the upgrade to A16 when it is released.

3 Likes
34
  1. Vendor Name: Fairphone
  2. Device name: FP4
  3. Device CodeName: FP4
  4. Version of /e/OS or Stock which existed previously: /e/OS 3.5 official
  5. device Not rooted

Up to now it runs as usual. No additional issues detected at first glance.

Many thanks to the development team!

35

  1. Vendor Name: Fairphone

  2. Device name: FP6

  3. Device CodeName: FP6

  4. Version of /e/OS or Stock which existed previously: /e/OS 3.5 official

  5. device Not rooted / locked bootloader

Super fast download! Everything seems to be running smoothly so far. Still no wifi calling though, but that was already the case with previous builds.

38

Please can you check the dates when you had VoLTE working and the dropping 2G/3G. My Samsung did work fine after the UK change to 4G but only because calls were able (in my case) to fall back to 2G. Effectively I did not notice the change although knowing that Samsung cannot do VoLTE as they have proprietary VoLTE software which does not transition to Custom ROMs.

1 Like
39

Same here. Everything is fine.

1 Like
40
  • Vendor Name: FairPhone
  • Device name: FairPhone 5
  • Device CodeName: FP5
  • Version of /e/OS or Stock which existed previously: 3.5
  • Is the device Rooted / Not rooted: Official /e/OS version

Issue: Android Auto is no longer working. When I plug it in, the following error message appears:

thread-10800395-16359698700013481845
thread-10800395-163596987000134818451080×2152 122 KB

4 Likes
41

Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Previous Version of /e/OS: 3.5-t-20260211580869-official-redfin
Version of /e/OS: 3.6-t-20260312593432-official-redfin
Device: Not rooted
Bootloader: Locked

Congratulations for managing the download speeds, now the updates run nicely.
No problem so far, apart the ‘as usual’ :
The Advanced Privacy “frenzy” is still here, since 3.2.
I have to toggle off the ‘Tracker control’ flag to calm it down.

Congratulations again !

42

Vendor Name: FairPhone
Device name: FairPhone 6
Device CodeName: FP6
Version of /e/OS or Stock which existed previously: 3.5
Is the device Rooted / Not rooted: Official /e/OS version

44

For those wondering about A16, Murena has commented on Mastodon (German language toot) that they are eyeing an Android 16 relase in summer – in response to a question on the Fairphone 6. While this is not a specific date, it might give a slightly better idea of the time scale. The toot does not specify if the summer estimate is for official (OTA) or community.

1 Like
45

from the past years experience, upgrade release was always between July and October

46

Hi,

did you create a ticket in GitLab for this issue?

For some people this may be a dealbreaker for this update.

Best regards

Oliver