Hi everyone,
since updating to Android 16 on my Fairphone 6 yesterday, I’m experiencing a consistent Bluetooth issue in my car (Mazda 5 CW, ~2013).
Behavior:
-
Bluetooth connects automatically when starting the car
-
Calls (HFP) work immediately
-
Media audio (A2DP) is shown as enabled, but no sound is played
-
Only after disabling and re-enabling “Media audio” in Bluetooth settings, audio starts working normally
Important details:
-
This happens on every connection (also after disconnect/reconnect)
-
Re-pairing the device on both phone and car → no change
-
Rebooting the phone → no change
What I already tried:
Workaround:
- Manually toggling “Media audio” off and on fixes it until the next reconnect
Assumption:
This looks like an A2DP initialization issue in Android 16 (connection is established, but audio routing is not triggered until re-initialized).
Is anyone else experiencing this or found a permanent fix?
Thanks!
i nave the same issue on my Iode Os 7.3 latest version.
Thanks for confirming!
Good to know it’s not Fairphone OS specific.
Seems like a general Android 16 / AOSP Bluetooth A2DP issue.
Are you also using a car head unit (older Bluetooth)?
Hi all,
quick update from my side:
I’ve reported this issue in the official Android support forum as well:
https://support.google.com/android/thread/421465418
Given that the same behavior has now been observed on different Android-based systems (e.g. Fairphone OS and iodeOS), this does not seem to be vendor-specific.
At this point, it looks like a potential Android 16 Bluetooth / A2DP regression, especially in combination with older car head units.
I’ll update here if there’s any official feedback or progress.
Would be helpful if others experiencing the same issue could confirm it there as well 
1 Like
On second thought, my issue is not really the same as yours, but close-ish. What happens on my car is that HFP doesn’t route sound. I used other android phones in the past and iphones and never had this sort of issues with bt.
Not sure what’s going on, or if related to A16,but it’s a very annoying issue.
Hi all,
quick update on this topic:
As you know I’ve reported the issue in the official Android support forum as well:
https://support.google.com/android/thread/421465418
The response there points towards a software-level issue in Android 16, where Bluetooth audio routing is not properly initialized, especially with older car head units.
In my case, this affects A2DP (media audio):
Interestingly, another report here indicates a similar issue with HFP (call audio) not routing correctly.
So while the exact symptoms differ, both cases point in the same direction:
Bluetooth connection works, but audio routing fails to initialize properly
Given that:
-
the issue is reproducible
-
occurs across different Android-based OS (e.g. Fairphone OS, iodeOS)
-
and now affects different Bluetooth profiles (A2DP and HFP)
this strongly suggests a broader Android 16 Bluetooth / audio routing regression, rather than a Fairphone-specific issue.
I’ll keep this thread updated if there’s any official feedback from Google or Fairphone.
If others are seeing similar behavior (either media or call audio), it would be great to collect more confirmations.
Hi all,
quick update after some deeper analysis:
I captured a full bugreport with Bluetooth HCI logging enabled and reproduced the issue directly before generating it.
From the logs, the behavior looks like this:
On initial connection, the Bluetooth device is connected (HFP works), but A2DP (media audio) is not properly initialized
The system explicitly marks the A2DP device as unavailable and removes the corresponding audio Route.
Only after manually toggling “Media audio” off and on, Android disconnects and reconnects the Bluetooth profiles, after which A2DP works normally.
So this is not a pairing or configuration issue — it’s more like the A2DP audio path is not correctly initialized on connect.
Combined with:
- reproducible behavior on every connection
- confirmation from other Android-based OS (e.g. iodeOS)
- and now log evidence
this strongly points towards a broader Android 16 Bluetooth / audio routing regression, especially with older car head units.
I’ve also updated the issue in the official Android forum accordingly.
I’ll keep this thread updated if there are any findings from Fairphone or Google
Hi all,
quick update:
I’ve opened a support case with Fairphone and shared a full bugreport (including Bluetooth HCI logs) with them for further analysis.
Reference: Fairphone support ticket #1407835
Given the reproducible behavior and the log findings, this is now under investigation from the Fairphone side.
I’ll keep you posted as soon as I receive any feedback
Quick update:
I’ve filed this issue in the Android Issue Tracker:
Based on logs, A2DP is not properly initialized on connection.
Media audio only starts after manually toggling it.
This might indicate an Android 16 (AOSP) regression rather than a vendor-specific issue.
Would be great if others affected could confirm or add their findings there.
Quick update based on the latest findings:
The issue has been picked up by Google and assigned to an engineer.
More interestingly, it is now linked to another (internal) issue on Google’s side.
This suggests that the behavior is not an isolated case, but part of a broader problem currently being investigated.
Given that:
- the issue is reproducible
- logs show A2DP not being properly initialized on connection
- and similar behavior has been reported on other Android-based systems
this further strengthens the assumption that this is likely not Fairphone-specific, but related to the Android 16 Bluetooth stack.
I’ve also opened a support case with Fairphone, 1407835, so both sides are aware.
Will keep you posted as soon as there are updates.
There are very similar problems with Android Auto for quite some time now, in my personal experience at least since Android 10. To me these are signs that we’re getting caught up in a growing web of complexity. Security (and some other) considerations are being addressed independently in several different places at once which inevitably leads to compatibility issues. Hardly anyone has a complete overview anymore and even if you manage to get a system running smoothly things can look completely different again after the next update …
Update:
Google has picked up the issue and an engineer is now actively investigating it.
They reviewed the initial logs and asked for a more detailed bugreport with full Bluetooth logging enabled (HCI snoop + verbose stack logs). I’ve provided that, including a reproduction exactly at the moment the issue occurs.
The case is still linked to another (internal) issue on Google’s side, which suggests this might be part of a broader Android 16 problem rather than something device-specific.
I’ll share updates as soon as I hear back from them.
1 Like
