Thank you for taking our concerns seriously .
With the switch under the Bluetooth settings of the headphones, as in the picture above, it can disable the HD Audio aptx option without the developer menu.
Thank you for taking our concerns seriously .
With the switch under the Bluetooth settings of the headphones, as in the picture above, it can disable the HD Audio aptx option without the developer menu.
I have those ear buds, too.
EDIT: Sorry I misread your comment: I do have the Liberty Air 2 Pro.
I updated them to use LDAC and that is still working for me.
You have to explain that to me in a little more detail. What is LDAC mode? And how can I activate it?
I have firmware v1.28 on my Liberty 2 Pro. Under the Bluetooth settings I have no LDAC function. I don’t have access to the DEV menu.
Had the same problem and same solution today.
I think Aptx is really not important, so shocking bug but no real problem at least.
You have to explain that to me in a little more detail. What is LDAC mode? And how can I activate it?
I have firmware v1.28 on my Liberty 2 Pro. Under the Bluetooth settings I have no LDAC function. I don’t have access to the DEV menu.
My firmware version is 5.63. You can upgrade it via Soundcore app from the playstore. Then there is an option to use LDAC as codec for better sound quality.
EDIT: Just found the possible reason: I have the Liberty Air 2 Pro. Sorry for the confusion.
I have the same issue with Aptx not being able to play audio. Instead the media is constantly pausing and unpausing.
Does anybody know if there’s a way of disabling Aptx as an option?
Just found this thread while having the same issue with my new Fairphone 4 and Sony WH-1000XM3s. Pleased to see that Fairphone team are already on it!
SBC audio not terrible in the meantime but it will be nice to have the LDAC setting persistent
Same here : since my FP4 upgraded to Android 12 FP4.SP1Y.B.041.20230109, my Sennheiser Momentum 2 don’t play any sound any more.
Am very looking forward to hearing Sennheiser Momentum 2 playing sound from my FP4 again.
BTW: Bose SoundLink Mini is working fine, and so does an old Plantronic PLT_M55 headset.
Update: switching off HD-Audio aptX does work around the problem for me.
Try this
change Bluetooth-A2DP-Hardware-Offload in developer settings. a reboot is required.
This can only be a temporary solution, no mini jack and no aptx support are a definite exclusion criterion for me.
Welcome to the forum!
This can only be a temporary solution,
For me the words In the meantime and temporary workaround describe it as a temporary solution here…:
In the meantime, disabling HD Audio in the Developer options is a viable temporary workaround.
Simply not true.
Was working with aptx adaptive until Android 12.
No clue on how you can tell it like that. See feedback from Fairphone.
I’m not lying, maybe misinformed. AptX is not listed as a codec for the FP4 and FP support did mention to me once that AptX is not included due to licensing or something.
@Yasen_Tomov, sorry to drag you into this. Could you confirm or deny this? Does the FP4 have support for AptX? And if not, why did it work before? Was that just a transparent fallback in the background to e.g. AAC? And thus users may simply not notice that they’re actually using AAC. And perhaps this fallback mechanism is now buggy/broken in Android 12?
This supported codec list you show is for playback. Not for Bluetooth.
Otherwise it would say you can play AAC+ or FLAC via Bluetooth, what is not the case.
I find it confusing as well, because SBC would be missing in that case. I’m just repeating what support told me with this list. If we cannot trust that as a source, then I don’t know what is.
I am sorry but this time the support was wrong to you.
I trust the Fairphone answer in one of the threat that dev team is taking care of it to correct.
And as I have a 4 - I can tell you that aptx - until adaptive, (TWS I could not try), AAC, LDAC was working. Even AAC is still working with 12. Prove by the receiver that show the type of codec used - in addition to the message in Fairphone 4.
To my knowledge:
In case you have a SoC from Qualcomm - you get by default aptx support as it is built-in in hardware.
If you get aptx adaptive or hd do more pend on type of chip and modem used.
Aptx is qualcomm proprietary content - and so I can understand you need license if you do NOT use SoC from Qualcomm.
Here Fairphone do have Qualcomm - and so you have aptx support.
I do not have heard of any smartphone with Qualcomm NOT having at least one aptx codec. This since my first - HTC Desire.
It would be more questionable for LDAC support as SONY proprietary Codec. But even this runs with the Fairphone 4.
As even the aptx is not working - that must be a configuration error in the kernel modules in Android12. The behaviour of Video playback (slomo) is for me a clear indicator.
To complete:
LDAC is still working with Android 12.
Only aptx - in all version - fail.
So I can still use my PX7 with appropriate codec - but need a Fiio M5 in the middle.
Hi there,
I also can confirm that aptX did work on FP4 Stock Android 11 with 2 different bluetooth audio devices capable of aptX. Since update to Android 12 only silence if I use HD-Audio and aptX is shown in the properties of the bluetooth connection. Switching off HD-Audio immediately solves the problem.
I’m not happy with this solution. Audio quality has significantly degraded
Please solve this issue, dear FP-Team!
Robsn
Hi and welcome to the forum.
As this is a user forum with Fairphone only really reading responses to their own posts you may find it more satisfying to contact Fairphone via their support page or by email to support@fairphone.com
See also
This guide is a #wiki, you are free to edit/update it using theicon in the bottom right corner of this post.
First things first: here is the fastest and best way to contact support: Send a request to support Please fill in the required fields for case to be handled faster If you didn’t buy the device directly from Fairphone provide proof of purchase in your request Write down your ticket number Only use one email address when mailing Fill in as much data as possible, then …
Fairphone already accepted this bug and confirmed to work on it, no need to bother support with this