I’m going to put in a top-level reply here on my experience with 3.6 but I noticed you were also having Android Auto problems. My Android Auto decided to start showing Error 8. In checking the phone out closer just now, I am finding MicroG appears to be broken or gone - there’s no Settings → System → MicroG.
I’m now kind of frantically looking around to find out how to fix the missing MicroG issue.
Something up with MicroG … there is no longer any Settings → System → MicroG (or anywhere else in Settings). In looking at the Apps there’s a MicroG companion but there must be something else going on or missing as none of the MicroG settings are around.
Android Auto also started failing producing Error 8, but I suspect this is related to MicroG gone/misbehaving (I hate how discourse doesn’t load the contents of the thread unless you visibly slide to it - I see now that others are having AA issues). Has anyone else checked their MicroG?
One other issue in this release that was present previously is that screen brightness does not learn from my pushing it brighter very often. It really likes to be too dark in darker light scenarios.
Its just renamed. Application compatibility or so
oh good lord… why…
More “why” than that, is why isn’t there a big notification on these changes on first boot - this is a minor revision.
Further to that - this wasn’t mentioned even in the 3.6 release notes. Where were we supposed to get these details from?
App Lounge initial launch / home page loading feels really faster in this version, heads up to the devs!
Vendor: XIAOMI
Device name: MI 10T PRO
Device Codename: Apollon
Version of /e/OS or Stock which existed previously: /e/OS 3.5 community
Is the device Rooted / Not rooted: Non Rooted
As I have already written for version 3.5 community Feedback for v3.5 - #26 by VitTh (and also for 3.4 and 3.3) the camera start it freezes and becomes unusable. It is evidently a software problem in /e/OS present since August 2025 and never solved.
It’s not possible for me to insert photos in contacts: if I select a contact, I edit it, I can choose the photo (i cannot take a pic…) but there is no OK button to confirm (and I don’t see any way to confirm). This happens both by choosing the /e/ address book and the address book on my smartphone.
Have a nice day
Thank you
No issues so far. Thanks 
Sounds like a variation of Contact Photo edits: SAVE button invisible in bright system theme (#8876) · Issues · e / Backlog · GitLab.
There are other forum links to the issue like Can't Update Contact Photos
In addition I could drive with AA one time after the update. Before and after I got the Error 14. Now it seems persistently broken
About Android Auto.
In Settings of my car, there is a screen with the list of connected smartphones.
I can there toggle on or off the connection of a tel.
I have put on off then on on again and everything was fine. AA is working again.
Hope it helps some of you.
But I have noticed something else. I went yesterday in a concert. I have made some videos with Fairphone cam app. Audio is noise. Just like the microphone was saturated. Videos from an iPhone are excellent. Video from fairphone in a “normal” environment is OK.
Is there an option to change the “volume” of the microphone in fairphone app ?
“manual” - it sounded as if a16 would be rolled out OTA….”manual install” is not very satisfying - last time - to a15 - the process stopped somewhere in the middle here, whyever, and broke my mobile (FP5). Dead completely after reboot, I had to send it to france. They were quick, under 2 weeks - but…I am very concerned about trying this again.
Edit: Update to OS v3.6 minutes ago OTA was quick and fine btw. But a15 ‘only’ unfortunately.
@Manoj can this sort of changes maybe also be considered in release notes to avoid confusion, especially for the lay user?
It would be good practice to be on time with documentation.
In this case of renaming the integrated MicroG it would help much to update the MicroG-related documentation accordingly (here and here, maybe there´s more) and refer to MicroG as “integrated in eOS as App-compatibility system app” or the like.
Passing on the message to the team.
Vendor Name: 2x Fairphone
Device name: 2x Fairphone 3
Device CodeName: 2x FP3
Version of /e/OS or Stock which existed previously:
2x /e/OS 3.4-a15-20260117570255-community-FP3
Is the device Rooted / Not rooted: 2x Not rooted
No issues with updating, now 2x on 3.6-a15-20260314594305-community-FP3.
The following things work for me (2x):
Hi,
is there anything new regarding Android Auto?
I didn’t install the update yet due to this issue.
Best regards
Oliver
I wonder why I got offered the update for FP6 today and not like others already three days ago?
Vendor Name: Fairphone
Device name: Fairphone 6
Device CodeName: FP6
Version of /e/OS or Stock which existed previously: 3.5 Official
Is the device Rooted / Not rooted: Not
It’s a staggered release as usual, not everybody is getting it at the same time.
I had a blank screen in car and on phone after update.
I toggled off my phone in AA car settings then activated it again.
AA is working now with my FP6 in 3.6.
But I’m maybe just a lucky guy, I don’t know. I don’ see any comment like mine for the moment…
Dedicated issue created to track v3.6 bugs. Links to the forum posts have been added. Users can add logs or details to the issue on GitLab. if they are facing the issue