As changing it in the developer options is not permanent, its maybe better to turn off HD Audio
Rather than go without HD I guess I would first use Dev options to check that a usable codec is available and then install the Bt Codec Changer mentioned several times in this topic. Dezponia’s post is a good summary!
I have very high hopes that this issue will be FINALLY fixed with the upcoming update.
I recently switched to LineageOS 20, which is based on Android 13. With that AptX works fine. So it can be fixed and I think it’s just a matter of time when the stock Android version of Fairphone will also work properly.
I have no doubt that it runs on original FP OS
Sadly the latest update with build number FP4.SP25.B.058.20230318 does not appear to change the status of this Bluetooth “HD audio” issue with aptX introduced with the FP4 Android 12 upgrade. I’ve re-ran all my testing on this update to confirm the status is unchanged. As such the workarounds and status of my previous posts are still applicable.
Bluetooth Audio issue TL:DR:
- aptX and aptX Adaptive remain broken for now.
- SBC, AAC, aptX HD, and LDAC works.
- Workarounds linked below.
Bluetooth Audio Workarounds can be found here:
My troubleshooting of this issue can be found here:
Looking forward to seeing the remaining aptX codecs fixed in a future version. Thanks for the other fixes and security updates in this update.
It’s really an indictment that such problems just don’t get fixed.
Article is wrong regarding LDAC. If you go to developer options, you can select 4 options for Bluetooth Audio LDAC Codec Selection: Playback Quality:
- Optimized for Audio Quality (990 kbps / 909 kbps)
- Balanced Audio And Connection Quality (660 kbps / 606 kbps)
- Optimized for Connection Quality (330 kbps / 303 kbps)
- Best Effort (Adaptive Bit Rate)
LDAC is proprietary (Sony), but it works well. The only downside is the latency (however something like video gets offset to audio latency, so it Just Works ™.)
The only time you want low latency is when you are phoning or perhaps when you are video calling (then the video can offset as well, at the cost of a latency of say 200 msec).
For people who don’t have Sony headphones, AAC is still a serious improvement over SBC. Whenever you use your mic, I believe Bluetooth automatically switches to SBC anyway.
Some Anker/Soundcore Headset support LDAC, too. For example my Soundcore Liberty Air 2 Pro
It is really more than high time to solve this now quite embarrassing problem. According to the feedback here in the forum, even custom roms have no problems with it. it’s just rude not to fix it. Everyone expects the one company to deliver the one working product.
Do you really think “spamming” the forum every other day with the same broken record will speed up anything? You are free to do so, and still you are adressing your complains towrads other uses not FP, so most likely not at all helpful neither for you nor for others…
A saying I read the other day (in German);
Das ärgerliche am Ärger ist (selbst wenn berechtigt), dass er einem selbst schadet ohne anderen zu nutzen…
Yes they do. Calyx moved to the Android 12 blobs a few days ago (still in beta I believe) and firmware based bugs like this one or the screen dimming issue are totally there as well.
A lot of the other stuff isn’t, because it got patched, or solved with Android 13, but the blobs can and sometimes will effect custom ROMs as well.
I don’t understand why the behavior of FP is also being defended here. It was once said it will be fixed, again half-heartedly. Since then there has been no more feedback. What does this have to do with spamming? Why isn’t trading transparent here?
Es ist kein Ärger sondern eine Enttäuschung.
Wer selber keine versprechen hält, wird wohl selbst damit zu frieden sein, gebrochene versprechen zu akzeptieren.
Die Hoffnung stirbt bekanntlich zuletzt…
I talked about the Bluetooth problem, that’s also the thread about it.
This is still a user forum, posting the same sentiment in different topics doesn’t achieve anything and I’d consider that spamming as well.
I do agree that Fairphone has to fix this and there’s no reason to defend this behavior, but you are addressing the wrong people.
As I said …
… here’s the current CalyxOS changelog:
AptX is temporarily disabled because it’s broken.
AptX HD is still available
There might be occasional audio cracks
It’s interesting to read, does this apply to all custom roms?
If they updated to the Android 12 blobs and haven’t found a workaround, yes.
Since most are based on Lineage or at least adjacent to it (Calyx is AOSP with some LOS), once there is a fix everyone should benefit, but if Calyx doesn’t ship a fix, there probably isn’t one yet.
So if it’s possible and others can manage it, shouldn’t Fairphone also be able to solve the problem?
Yes, of course. But if I understood right, there is no solution from others, yet.
BTW: some short research brought up, that there are Aptx (HD) failures in Android 12 also with other devices. For example OnePlus 8T had a problem with Aptx HD. So this does not seem to be solely Fairphone specific. Of course I do not know wether the other producers already fixed it. Oneplus had the problem in April 2022, though.
And Samsung does not provide the support at all for Aptx HD, at least for the rather old S20, if I remember correctly.
A post was merged into an existing topic: Remarks by the software update FP4 20230318
2 posts were merged into an existing topic: Remarks by the software update FP4 20230318