This is a new post, because the previous one was closed without a solution or fix. The issue currently still exists in e/os version 3.7.3 …
1 Like
Good new: I just received an email from the developer in charge of this issue, which says this:
”For those on regular channels, v4.0 build will have the fixes for this issue.
It should finally be fixed now, we got positive feedback from internal testing.
If BLE/LE audio (LC3 codec) was also not working, it should start working now.”
I’m very excited with this new. Let’s hope it will be really fixed in 4.0 
1 Like
I’m also experiencing this on 3.7.3. In my case it’s specifically Bluetooth bond keys not persisting after device separation — my Garmin Venu 2S triggers the Android “for your safety, forget this device and pair it again” system notification every time it goes out of range and comes back.
I’ve already ruled out app permissions, battery optimization, and Advanced Privacy settings as causes. Filed a GitLab issue here: FP6: Bluetooth bond keys not persisting after device separation - triggers "for your safety" re-pair loop (#9417) · Issues · e / Backlog · GitLab
Good to hear v4.0 should have fixes — looking forward to it!
With 4.0 my car system won’t reboot anymore when magicearth wants to give a direction. Same goes for other navigation apps. But the direction is not coming true. Everything else (phone and music) seems to work.
I’m driving a Fiat 500 hybrid (2021)
I tested it this weekend on e/os version 4. The issue has been resolved and, after a year, I can finally make hands-free calls in my car. Thanks to the dev team for sorting it out.
Fairphone 6 / Hyundai i40 - 2012 model
1 Like