This seems to be caused by aa4mg, which now breaks the bootup until it is properly uninstalled. This is too bad because their android auto solution is better than the e/OS one, since installing google maps literally defeats the whole purpose of using microG and e/OS in the first place.
Edit: Made my own fork of aa4mg that doesn’t install it’s own android auto stuff, but still does the rest of the goodies: GitHub - Maxwell175/aa4mg: Android Auto 4 microG
I did get back to Stock and after a few tries found a viable solution:
I reinstalled the Phone with Stock 15 (it was up to date at 16 before) and all my problems went away.
I do not quite understand how these side effects appeared, but nvm
Hi @bauerber ,
your stock A16 was to “high” for installing /e/OS.
There is no /e/OS A16 yet.
look at the documentation:
/e/OS build : A15 community
/e/OS build : A15 official
To understand the difference between /e/OS builds check this guide
Before following these instructions please ensure that the device is on the latest Android 15 firmware.
If your device is currently using a newer or older version than the required version, please upgrade or downgrade to the required version before proceeding with your /e/OS installation.
The required version is Android 15 , which may be lower than the /e/OS version you are about to install - this is not an error! If there are multiple updates of that version (e.g. security updates), make sure to use the latest!
If you need to upgrade or downgrade your device, please search online for guides. We are unable to provide specific instructions here and on our support platforms.
Hi kokrabe, thanks for the feedback.
I would have expected the install (guided install on /e/OS Installer ) to fail or at least a hint in the installation guide. The information for the necessity to downgrade to 15 is listed only in the cli-installation documentation. As the guided install is available for Pixel 7, i did not read the cli instructions.
Maybe this requirement could be listed in the starting instructions for the guided install on Pixel 7 (in the “lets start” box where all requirements are listed)?
I nevertheless am amazed, that the install in itself was completely normal, i only encountered side effects once the phone was ready to set up…
Hi bauerber,
yes, this would be fine if the easy-installer would be perfect 
To send a request use : Request a Feature - /e/OS community and address with @ at the best to Manoj.
Web installer is not really informative what to do… Some users here on the forum are trying to get that improved. Thank you for pointing out, that there are no hints about recommended Android version
I still have problems with Android Auto. It appears on my headunit, but I can’t use it and my phone then gives a notification that it won’t work with the usb device and provides a link to the Pixel 9. I’m on an FP 5 with V3.3 Offcial and an unlocked bootloader.
Vendor Name: XIAOMI
Device name: MI 10T Pro (M2007J3SG)
Device CodeName: Apollon
Version of /e/OS or Stock which existed previously: /e/OS 3.1.1-a1520250829521751-community-apollon
Is the device Rooted / Not rooted: NON rooted
Same bugs with the camera and torch apps as in the previous version ( Xiaomi Mi 10T Pro /e/OS locked camera )
The phone’s sound doesn’t work via Bluetooth even though I’m connected to the car. And the worst part is that it’s impossible to switch to speaker mode or classic mode…
There are a couple of open issues around FP6 and bluetooth devices.
You can check the issue details and if yours are similar add to the bug report or else create a new issue.
I have a silly bug in 3.3 that was already there in 3.2: “Battery saver” is on 24/7* but I keep getting the warning when the battery level reaches 10% and I’m asked if I want battery saver to be started. It’s already on silly.
*I do this because the battery empties very fast, faster that the one in my Galaxy A14.
Also, I had stopped “ntfy” and it reactivated itself without asking. I’ll never use it: I don’t need it to use up resources in the background. 
Do you know what ntfy is for?
Yes it allows users to write scripts and get notifications, something like that. I don’t need it.
You should embrace it 
, since it could make us users less dependent on cloud messaging from google.
Uh? This? If I use it, it wasn’t my choice.
I finally updated my FP6 to 3.3 and everything is working smoothly. I am able to use Android Auto both via USB and wirelessly!
In fact, I installed a modern head unit in my old Honda the same day and that was the first time I’d ever used AA wirelessly.
Best regards,
FP5 and FP6 (3.3-A15-official, Not rooted, ), unable to receive and send text messages with Orange Belgium, but no issues with Orange France using the same phone.
Thank you
Best wishes for 2026
Did you check your APN?
What is the correct APN setting?
“Text messages are sent via the message centre number: +32495002530. This number is already programmed onto your SIM card.”
I cannot see any APN for text messages on the Orange Be website.