What is AptX?
Click here to find out
I noticed that the custom bluetooth codecs( like the aptX, aptX HD, LDAC, etc.) are not working even if we have devices that support it( like earphones, headphones, soundbars, etc.) For example, I own a Samsung Level U wireless headset, which is compatible of aptX codec, but whenever I connect it with my Mi A1, the codec in Developer options switches itself to SBC.
So, I found a workaround for it on OnePlus 3/3T Device Forum. @theduke7 has created a Magisk module which enables aptX/ aptX HD on One Plus 3. I flashed that module, and Voila! The codecs started working on my phone.
How will this help you?
AptX increases the quality of audio transmitting over bluetooth considerably. So you will be able to hear nearly lossless, CD quality audio from your device.
Just flash the below given Magisk module in Magisk 14.0+ and reboot.
For those who can't find the option,
Go to Settings >> System >> Developer Options >> Bluetooth Audio Codec
Link to the thread
Just thank @theduke7
Before posting, please check whether your wireless bluetooth device supports any of the above mentioned codecs.
Screenshots:
Doesn't works for me...
Codec stills revert to SBC every time I connect my BT headset.
It's a Driftin DBE-301BGY. But I don't know if it's apt-X or apt-X HD compatibe.
No matter wich codec I choose, always revert to SBC....
Gurx said:
Doesn't works for me...
Codec stills revert to SBC every time I connect my BT headset.
It's a Driftin DBE-301BGY. But I don't know if it's apt-X or apt-X HD compatibe.
No matter wich codec I choose, always revert to SBC....
Click to expand...
Click to collapse
Your wireless earphones are not aptX/aptX HD compatible, mate. I googled them just now.
Also, the module is sometimes unstable. It reverts back to SBC even when we choose aptX or aptX HD. A simple reboot should solve that problem. After rebooting, before connecting the wireless, go to developer options and manually select the supported codec, and then connect.
guy_infinity said:
Your wireless earphones are not aptX/aptX HD compatible, mate. I googled them just now.
Also, the module is sometimes unstable. It reverts back to SBC even when we choose aptX or aptX HD. A simple reboot should solve that problem. After rebooting, before connecting the wireless, go to developer options and manually select the supported codec, and then connect.
Click to expand...
Click to collapse
Oh, I see... Thanks!
guy_infinity said:
I noticed that the custom bluetooth codecs( like the aptX, aptX HD, LDAC, etc.) are not working even if we have devices that support it( like earphones, headphones, soundbars, etc.) For example, I own a Samsung Level U wireless headset, which is compatible of aptX codec, but whenever I connect it with my Mi A1, the codec in Developer options switches itself to SBC.
So, I found a workaround for it on OnePlus 3/3T Device Forum. @theduke7 has created a Magisk module which enables aptX/ aptX HD on One Plus 3. I flashed that module, and Voila! The codecs started working on my phone.
Just flash the below given Magisk module in Magisk 14.0+ and reboot.
For those who can't find the option,
Go to Settings>> System>> Developer Options>> Bluetooth Audio Codec
Link to the thread
Just thank @theduke7
Click to expand...
Click to collapse
can you solve earphone noise
projectkom said:
can you solve earphone noise
Click to expand...
Click to collapse
Dude, I'm not a developer. I just found out that this module works for our device, and so I posted it here, giving necessary credits.
And I don't get any noise in my earphones. Can you try a fastboot rom flash without wiping data?
Does it work on custom ROM?
On Oreo 8.0 all works fine, aptx and aptx HD.
At Oreo 8.1 (July Update) - only aptx is working. U can select aptx HD in the Developer/Audio settings, but dos not have any effect.
Any suggestions?
it only works if the xiaomi was rooted. Without root the APT doesn't work even more if you installed the drivers and modified the build.prop
What do U mean? Pls explain.
Magisk 16 Up and running....
Think ist's a 8.1 Bug, HD get -1 priority
//666kb.com/i/ dvpuaig5thf0xk7vi. Png
Cant Post Image from Cat log here - U know how toll View Pic
Roadwuzel said:
What do U mean? Pls explain.
Magisk 16 Up and running....
Think ist's a 8.1 Bug, HD get -1 priority
//666kb.com/i/ dvpuaig5thf0xk7vi. Png
Cant Post Image from Cat log here - U know how toll View Pic
Click to expand...
Click to collapse
I did it manually and I added into the build.prop located in system:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
Regards.
sidbyron said:
I did it manually and I added into the build.prop located in system:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
Regards.
Click to expand...
Click to collapse
This way you have to flash stock system.img before ota will work again. Just to keep in mind.
Does this work for Pie? I recently updated my MiA1 to Pie a few nights ago.
I'm trying to use this on my Sennheiser 4.5BTNC headset.
can anyone confirm whether it's working on latest Pie STOCK rom for mia1 or not? I want to install this, can anyone confirm & help me?
Xiaomi mi A1..aptx or ldac on Pie
Anyone got a guide for getting aptx or ldac working on Pie...
Hi.
I've seen barely any mention of this issue.
I've tried several ROMs like Bliss, Havoc and Evolution, all of them Q.
I have an EarStudio E100 DAC which supports AptX and AptX HD, which were working perfectly well on Android 9.
I was able to select the right codec from Developer Options and the sound would be much better and SBC or AAC, but now on Android 10, there is no difference whatsoever. I can select AptX HD it does not stick and reverts back to the lowest quality codec.
Any idea on how to solve this?
EDIT:
On Reddit, from user CoolGeek71, I found out that selecting the capabilities FIRST and only after that selecting AptX HD inside Developer Options, Android will use the requested codec. So, instead of selecting AptX HD only as it was on Pie, I have to select before the "Bluetooth Audio Sample Rate" to 44.1kHz or 48kHz and "Bluetooth Audio Bits per Sample" to 24 bits. Only then, stupid Android 10 will use it.
Once again, Google making simple things harder to use.
I noticed that if I change the developer settings for Bluetooth codec it automatically changes it back to defaults after I close out of the settings.
Sent from my GM1917 using Tapatalk
This stupid problem is also present with LDAC quality settings as well. I use the Fiio BTR5.
Interestingly, Beta 8 fixed this issue. However this bug has reared its ugly head on the newest 1.0.3.1 again.
Hey Folks,
Can any one help me figure out How to enable AptX Codecs on my OnePlus 7 (GM1900 running OOS 10.3.3.GM57AA)?
I tried many times in Developer settings, but they get reverted the next moment always. Any workaround???
I bought a pair of Earbuds but cannot enjoy this feature. Any help is appreciated. Thanks in advance.
jeticson said:
Hey Folks,
Can any one help me figure out How to enable AptX Codecs on my OnePlus 7 (GM1900 running OOS 10.3.3.GM57AA)?
I tried many times in Developer settings, but they get reverted the next moment always. Any workaround???
I bought a pair of Earbuds but cannot enjoy this feature. Any help is appreciated. Thanks in advance.
Click to expand...
Click to collapse
They are auto tuned if your hardwares(earbuds) are not supporting AptX codec then it always uses default codec you can't do anything about it...
At least not in Oxygen Os
Soundpeats Trueair earbuds are equipped with QCC3020 which is capable of AptX codecs. It must be a bug in OOS. I tried to force use AptX codecs in Developer settings but only to fail.
Link to buds features here: https://www.soundpeatsaudio.com/en/true-wireless-earbuds-trueair.html
jeticson said:
Soundpeats Trueair earbuds are equipped with QCC3020 which is capable of AptX codecs. It must be a bug in OOS. I tried to force use AptX codecs in Developer settings but only to fail.
Link to buds features here: https://www.soundpeatsaudio.com/en/true-wireless-earbuds-trueair.html
Click to expand...
Click to collapse
Maybe you are right
have you tried the magisk modules to enable aptx and other codecs?
jeticson said:
Soundpeats Trueair earbuds are equipped with QCC3020 which is capable of AptX codecs. It must be a bug in OOS. I tried to force use AptX codecs in Developer settings but only to fail.
Link to buds features here: https://www.soundpeatsaudio.com/en/true-wireless-earbuds-trueair.html
Click to expand...
Click to collapse
for me only AAC codec worked because my earbuds only supports AAC codec you can see in the screenshot my earbuds is AAC enabled,check yours also if it is AptX enabled after connecting to phone or not. i thought that you want to switch to AptX codec to remove latency issues...or may be i am wrong ?
Danaosthedemon said:
have you tried the magisk modules to enable aptx and other codecs?
Click to expand...
Click to collapse
Am not rooted.
Prinçe çharming ap said:
for me only AAC codec worked because my earbuds only supports AAC codec you can see in the screenshot my earbuds is AAC enabled,check yours also if it is AptX enabled after connecting to phone or not. i thought that you want to switch to AptX codec to remove latency issues...or may be i am wrong ?
Click to expand...
Click to collapse
I do not get this extra option in ear buds settings.
But I got the AptX enable menu when I connected the same buds with a Oppo Reno device. So it's a Op7 device OS issue. I have taken the issue up to the OOS Team in OP forums. They have taken logcats and said they are working on this issue. Hope to get it solved.
Hi Guys, Any solution to enable the audio for galaxy buds?
i tried developer options like disable miui optimisation but it does not work.
Try doing a network reset.
Clear system cache.
I fixed it. It chose the SBC codec by default.. you have to turn on the bluetooth AAC in the bluetooth setting for the pairing
Zessak said:
I fixed it. It chose the SBC codec by default.. you have to turn on the bluetooth AAC in the bluetooth setting for the pairing
Click to expand...
Click to collapse
They should work with the SBC codec. Depending what the source is on my 10+ it will either use the SBC or SSC codec when set to default.
So there's still an issue... that's strange.
If you had a Samsung device you could use their SSC codec which has superior resolution.
Hi, Can i use LDAC codec with s22 ultra and Sony WF-1000XM4 ? In the developer options i can't, even if I select LDAC, it remains on AAC ? Any ideeas please ? Thanks a lot
You don't need to go to developer options. Open Bluetooth settings, find the XM4, tap the settings wheel and select LDAC codec (you need to have the headphones connected to activate this option)
That stumped me as well when I first tried activating LDAC as well on my Soundcore Liberty 3 earbuds. xsam123 is correct
Perfect, it works ! Thanks !
Hi!
If you have any other problems with LDAC, even with using developper option, don't waste you time any further.
(I've spent so much time to correct the issue in this way)
Developer solution's won't work.
And you'll not have the choice to enable LDAC in Bluetooth normal user setting
Reboot your Xiaomi with hard reset.
Everything will become clear and operational.
LDAC Choice will appear correctly again.
Best regards
Be sure HD audio is enabled as LDAC codec in the bluetooth device info, in the bluetooth connection app.