Feedback for v3.3

[Manoj]

The initial plan was to release it on 22 Dec. Today. With the release put on hold over the weekend, we do not have a fixed date but it should be in the next 2 days.

[PKT]

Hi all,

Maybe my question is not in the right topic. If it is, I’m sorry and put it in right one.

I have a FP3 which is running v3.2 official A13.

I see that v3.2 official release is in A13 and community v3.2 is in A15. (I see v3.3 community A15 is available).

Could you explain me why official release is still in A13 and not in A15 ?

Is it scheduled that A13 official will go to A15 official ?

Thanks a lot for your answer.

pkt

[mihi]

@Manoj

OS OTA Information

Completed

FP5 -  Fairphone: S (A13) →  V (A15)  

FP5 - Fairphone: U (A14) → V(A15)

FP4 - Fairphone : S (A12) → T (A13)

S9/9+ - Samsung : R (A11) → S (A12)

GS290 - Gigaset : R (A11) → S (A12)

GS290 - Gigaset : Q (A10) → R (A11)

avicii - OnePlus : A12

FP3 - Fairphone : S (A12) → T (A13)

S7/7+ - Samsung : R (A11) → S (A12)

FP4 - Fairphone : T (A13) → U (A14)

S8/8+ - Samsung : R (A11) → S (A12)

Note: OTA upgrades are for official or stable builds only

Under Development and Testing

• zirconia - Teracube : S(A12) → V(A15) (v3.4)
• emerald - Teracube : S(A12) → V(A15) (v3.4)
• avicii - OnePlus : S (A12) → U (A14)
• FP4 - Early 2026

To Be Planned

• FP3
• tangorpro - Google Pixel tablet 7
• Murena One - A12 - A15
• GS290* - A12 - A15
• Galaxy S9* - A12 - A15
• Galaxy S8* - A12 - A15
• Galaxy S7* - A12 - A15

(Devices marked with an ‘*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

Check the section titled A16 Updates below

What is OS OTA Upgrade?

Traditional Process:

Download correct OS build from supported device list

Download stock ROM from vendor site (for some devices)

Back up your data

Install stock ROM, then /e/OS ROM

Restore backups if needed

OTA Benefits:

Simplifies the entire process

Requires significant development and testing

Check this section and from there you might need to get to know what ‘official’ build is and a locked bootloader

Different Build Types

[Deppi]

@Manoj

• Vendor Name murena
• Device name Fairphone 6
• Device CodeName
• Version of /e/OS or Stock which existed previously 3.2
• Is the device Rooted / Not rooted not rooted

I updated my Fairphone 6 to 3.3. and until now everything works like it should.

It is still not possible for me to connect the phone to Android Auto in my car. I tried this explanation: How to setup Android Auto with /e/OS?

I have to say that I don’t know to much about technical things and perhaps I did something wrong. What`s your experiences.

[vincenth]

• Vendor Name google

• Device name pixel 5

• Device redfin

• Version of /e/OS or Stock which existed previously 3.2

• Is the device Rooted / Not rooted : not rooted

3.3 seems to be running fine for the moment.

[msp]

• Vendor Name Fairphone
• Device name Fairphone 3
• Device CodeName: FP3
• Version of /e/OS or Stock which existed previously 3.2 official
• Is the device Rooted / Not rooted: not rooted
• Bootloader locked

Updated my two FP3. During the update of the 2nd device the phone went unresponsive and the screen getting black. Forcing reboot results in corrupted device state. I switched to the other boot slot and the device came up with 3.3 successfully.

Everything works fine so far. Thanks

[TillHH]

• Vendor Name murena

• Device name Fairphone 6

• Version of /e/OS or Stock which existed previously 3.3-a15

Hello,

after updating to 3.3, I get the following message. Where could this come from? I deleted the cache of the MicroG. No change.

[Gaea]

Fairphone 6
Previous 3.2 official
Current 3.3 official
Not rooted
Locked

Update went smooth.
Timer alarm when wearing Bluetooth headphones or earbuds works now.
Casting still doesn’t work, keeps looking for devices.
Where my other phone, a Xiaomi f3 poco immediately find our tv.

Havo to do more testing, but looks good

[PKT]

FP6 official 3.2 updated to official 3.3

Not rooted. Locked. Bought from Fairphone with eos installed.

Upgrade has been done but FP camera app didn’t work anymore.

Edit : no improvement after deleting cache and app data. After switch off / on the phone, camera is working.

[Manoj]

All v3.3 Xiaomi devices builds on A14 have been removed from the image’s server. This is as we detected an issue with the build impacting the camera and torch app. A v3.3.1 specific to Xiaomi on A14 will be released ASAP.

[MatteoV]

• Fairphone
• FP4
• FP4
• Previous /e/OS 3.2
• Not rooted
• Uodated via OTA
• Continues ti ask for Murena account update

[Dinomite]

FP6 official 3.2 updated to official 3.3

Microg services keeps stopping notification is popping up.

[kolkrabe]

2 Devices

• Gigaset

• Gigaset GS290

• GS290

• Version previously installed: 3.2-s (a12)-official

• Not rooted

Update went smooth and fast. No issues so far.

Thanks a lot to the /e/OS-Team and greetings to Manoj.

[TecMar]

Same here, with FP6, but installed via console without easy/web Installer.

FairphoneOS → E/OS 3.3 Official

I killed the Google registration in microG is this the Problem?

[TecMar]

For me, the solution with microG was to reactivate device registration.

[18yt8zhg]

Works on Fairphone 6 too but still problem with Boursobank or Airbnb.

[M.Witte]

• Vendor Name: Murena

• Device name: Fairphone 5

• Device CodeName: FP5

• Version of /e/OS or Stock which existed previously: 3.2 official

• The device is Not rooted

The update was received OTA this morning. Installation went quickly and smoothly. Everything is working fine.

Thanks to the team and Merry Christmas!

[mp82]

• Vendor Name: Fairphone

• Device name: 5

• Device CodeName: FP5

• Version of /e/OS or Stock which existed previously: 3.2 A15 official

• The device is Not rooted

Update went smoothly, no issues with microG as FP6 users reported. I have to test the bank app yet that stopped working with 3.2, it now is atleast available and able to download through the App Lounge.

EDIT: yep it works ! Everything seems to work without issue, so happy !

[rXp]

• Vendor Name: Fairphone

• Device name: 6

• Device CodeName: FP6

• Version of /e/OS or Stock which existed previously: Stock A15 (5th October Sec Patches)

• The device is Not rooted

No issue with installation.
All applications are currently working even the bank and payment ones. No issue with camera, sound, mic or any settings for now. Dev/Debug mode is also working as expected.
I saw some people reporting migroG issues but I am not using any google app so I am not sure how I could help confirm the issue.

[TecMar]

The problem with the microG was probably because I deactivated the phone’s registration with Google, which prevented pop-up notifications from appearing.