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:
Known issues
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.
It worked for me, thanks a lot !
Is there any information if the AptX/AptX adaptive bug has been fixed with B.065? Desperately waiting…
Could now test it myself. Bug is NOT fixed. Neither AptX nor AptX adaptive work. VERY disappointing. 
It wasn’t in the script, . . . . slowly slowly
This was not mentioned in the change log, so it was pretty obvious, that this bug is not yet fixed, IMHO.
Many thanks for your enlightning comment. Now I finally understand what this change log is good for. Thanks! Thanks! Thanks!
However, I’ve been waiting to use my fine in-ears at full potential again without needing the transmitter case since FP4 got the upgrade to A12. Reason enough to check if something has happened without notice. The partial fix of the AptX bug was incorrectly reported as well.
You’re used to mansplaining in real life, right?
What is your problem?
If you know how to read a changelog your comment here is completely unnecessary.
And yes you are right, that the fix for AptX was announced but not done for all codecs. But this time there was not even a mention of any other error fixed in this release.
It was announced only for the correction made ( Aptx HD) and not overall for all AptX codecs.
A bug that was causing the Bluetooth audio to stop working when the aptX HD codec was selected, has been fixed.
Are you kidding us right now?
Where does it say that only PART of the problem should be solved?
It was clearly stated that the fault was taken care of. And the error is still there!
The fact that only aptx HD was fixed does NOT mean that the problem has been fixed. The feedback from the forum should be more than clear that it is not so.
No one complained that aptx HD didn’t work, only that their headphones with HD audio stopped working.
The underlying protocol cannot be less important for the user. He just wants to be able to use his expensive headphones to the full extent with his even more expensive Fairphone 4, just like he did with Android 11. Is that an exaggerated demand from the customer?
We need a solution to the problem for our headphones!
Completely independent of which version aptx is required. The feature was available in Android 11.
I really have the impression that only aptx HD protocol was fixed because the new Fairphone XL headphones support this feature. So far, this is the only bug that was fixed directly after the Android 12 update.
Fairbuds XL: Fairphone bringt reparierbaren, modularen ANC-Kopfhörer - ComputerBase
Als Audio-Codec werden AAC, SBC und aptX HD geboten – uneingeschränkter HD-Klang wird somit nicht plattformunabhängig geboten, ein freier HD-Codec nicht unterstützt.
