Feedback for v3.0

/e/OS Smartphone Operating System Build Feedback
44

Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 2.9-t Official
Is the device Rooted / Not rooted: rooted (Magisk 29)

Basic functionalities seem to work. :wink:

1 Like
45

Vendor Name: Murena
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 2.9-t Official
Is the device Rooted / Not rooted: not rooted

Everything seems ok, thank you dev team.

46
  • Pixel 7a Lynx
  • Previous version e/os 2.9-a14
  • Update OTA
  • non rooted

Installed flawlessly, phone works as usual.

47

That’s not quite how it works, there should be an OS. But, of course, things can go wrong.

You have a so-called A/B device with two slots for the OS called A and B.
An initial install of any Android OS should install both slots with the same OS version, then one slot will be chosen as active and will be in use.
In case of an OS update the updater will then install the updated OS in the background on the unused slot while the user can still use the phone, and the necessary reboot will only switch the actively used OS slot to the updated one.
User data doesn’t have slots and stays the same.

So, it is normal that the OS is installed on a slot A or a slot B. The slot which is in use switches with every update if everything is going according to plan.

But is this the updated OS version now, or the old one?

2 Likes
48

Installé hier soir sur mon Fairphone 5 hier soir.

Rien d’anormal à noter. Les fonctions introduites dans cette maj sont globalement inutiles pour moi.

J’aurais apprĂ©ciĂ© plus de nouveautĂ©s de qualitĂ© de vie, quelques options de personnalisation de l’interface en plus.
Changer d’icones, desactiver les applications stock telles que Mail (qui n’a jamais fonctionnĂ© correctement chez moi), pouvoir deplacer mes icones oĂč je veux sur l’écran plutĂŽt que de me voir imposer comme sur iOS, etc


Idem, pouvoir dĂ©sactiver la barre de recherche et app suggĂ©rĂ©es lorsqu’on glisse vers le bas serait cool. Ça ne me sert pas et m’empĂȘche d’accĂ©der Ă  mes notifications auquels j’accĂšde par ce mĂȘme glissement.

J’ai Ă©tĂ© aussi Ă©tonnĂ© de rester en Android 13 et sans maj de securitĂ© rĂ©cente.

Mais en soi, le telephone fonctionne donc c’est l’essentiel. Merci pour votre travail :ok_hand:

49

Do you know this:

Not sure what your ‘like’ meant

50
  • Vendor Name: Murena One
  • Device name: Murena One
  • Device CodeName: Murena
  • Version of /e/OS or Stock which existed previously: 2.9-s
  • Not rooted

installation no problems, phone works fine

51

[GUIDE] How to manually switch the active slot




1 Like
52

The forum’s search feature is your friend


1 Like
53

I liked the question, as I have the same question :wink: .

1 Like
54
  • Vendor Name: Oneplus
  • Device name: 9 pro
  • Device CodeName: lemonadep
  • Version of /e/OS or Stock which existed previously: 2.9-u
  • Not rooted

OTA update ok. Phone seems to be working without problems. Thank you team!

55

That was also spinning in my head, it could be that. A user on Telegram group will try it and tell me how it goes.

1 Like
56 
Vendor Name: Google
Device name: Pixel 8
Device CodeName: shiba
Version of /e/OS or Stock which existed previously: /e/OS 2.9-a14
Is the device Rooted / Not rooted: Not rooted

OTA update without problems.
After the installation I had to re-enter the Murena account password because it couldn’t connect.

57

I’m pretty certain I’ve seen manually switching slots reported not working on Fairphones with a locked bootloader, but maybe it could be dependent on the bootloader implementation per device, so it could work on other devices? Let’s see.

1 Like
58

My memories tell me that my FP3 with stable on 0.15 was not able to switch slots because it was locked. But that was years ago.

My guy will check with Murena 2.

59

Hello,

Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9-u Official (A14)
Is the device Rooted / Not rooted: Not rooted

I updated my Fairphone 4 to version 3.0. The download went well, and so did the update. However, I had a problem after rebooting. The system rebooted twice, and I got a message telling me that the system couldn’t load and that I was in recovery mode. By pressing ‘Try again’, the system booted, and I got the interface. At one point, it rebooted, and I got recovery mode again. I pressed ‘Try again’. I’m afraid my device might crash at any moment. The recovery mode offers me two options: ‘Try again’ and ‘Factory data reset’. Could you please fix this problem urgently because I didn’t have this problem on the official 2.9 U version?

Thank you.

Note: If you got a Fairphone 4, be carefull with e/os 3.0 version.

2 Likes
60

You are not the only one but a lucky one it seems. Is your bootloader locked?

I don’t know what the issue is but usually after couple of other updates (3.1, 3.2) I works to update. Still keep a backup routine if you don’t hane any, for others it looks like they have to reinstall


61

Same problem with my Fairphone 4. :frowning_face:

62

No, you are lucky as I told you. The other user has a unusable device, it doesn’t boot anymore properly.

63
  • Vendor Name: Nothing
  • Device name: CMF Phone 1
  • Device CodeName: Tetris
  • Version of /e/OS or Stock which existed previously: 2.9 community
  • Not rooted

Notified of update, installed without issue, everything seems fine (apart from eye-searing hyper saturated colours, but I think that’s a LiveDisplay / LineageOS thing that will never be fixed)

1 Like