I have a new pair of bluetooth headphones (Aukey EP-80) which support both AAC and Aptx protocols. AptX sounds noticeably better than AAC but my LG v35 always defaults to AAC when headphones first connected. It's a huge pain in the @SS to manually switch to AptX in developer settings. My Nexus 6P (8.1) and Huawei Mediapad (8.0) both correctly select AptX as expected.
A few google searches indicates this is LG behavior across many if not all phones. True? Arrg. Is there any way to fix, either permanently or with some app like tasker?
Well, at least LDAC Codec capable headphones always default to LDAC, if under their respective Bluetooth devices settings the connection type (which setting actualy only can be found for AptX HD and LDAC devices) is set to optimal instead of stable.
Yeah, I have a pair of headphones that support Aptx HD as well as AAC so I get the connection setting to select Aptx HD. It's only when just std Aptx and AAC are the available codecs that we're screwed and have to manually select Aptx every time in dev options. So frustrating for a phone that touts audio quality as it's primary selling point....
StephenMSmith said:
Yeah, I have a pair of headphones that support Aptx HD as well as AAC so I get the connection setting to select Aptx HD. It's only when just std Aptx and AAC are the available codecs that we're screwed and have to manually select Aptx every time in dev options. So frustrating for a phone that touts audio quality as it's primary selling point....
Click to expand...
Click to collapse
Just found this topic via Google. I have an LG V30 and just bought Sennheiser Momentum True Wireless in ear headphones. They support AAC as well as AptX. My V30 always defaults to AAC. I can switch to AptX no problem while they are connected but as soon as they are disconnected or put in their charging case and then reconnect, AAC is the default system choice again. This is pretty annoying. I have no clue why AAC is the default choice between the two options. My brother has a Note 9 and there AptX is the default option (as it should be, actually).
Has there ever been a fix for this? Thanks.
Tenlow said:
Just found this topic via Google. I have an LG V30 and just bought Sennheiser Momentum True Wireless in ear headphones. They support AAC as well as AptX. My V30 always defaults to AAC. I can switch to AptX no problem while they are connected but as soon as they are disconnected or put in their charging case and then reconnect, AAC is the default system choice again. This is pretty annoying. I have no clue why AAC is the default choice between the two options. My brother has a Note 9 and there AptX is the default option (as it should be, actually).
Has there ever been a fix for this? Thanks.
Click to expand...
Click to collapse
Nope! You need headphones that either support AptX but not AAC, or headphones that support AptX-HD. I have the B&W PX Active over-ear which support AptX-HD and am sticking w/my Aukey EP-B40 (original version) for earbuds b/c they got AptX but no AAC.
I upgraded at one point to better earbuds that supported AptX but also AAC and tried for a week to get some automated task script to work with would auto-select AptX in dev options but no go. Hopefully, more AptX-HD phones will start arriving but I'm only aware of the new Bullets so far and those are neckband.
I'm also not sure if AptX-LL (low latency) might work, ie. LG will default to AptX-LL rather than AAC. So that might be some hope.
StephenMSmith said:
Nope! You need headphones that either support AptX but not AAC, or headphones that support AptX-HD. I have the B&W PX Active over-ear which support AptX-HD and am sticking w/my Aukey EP-B40 (original version) for earbuds b/c they got AptX but no AAC.
I upgraded at one point to better earbuds that supported AptX but also AAC and tried for a week to get some automated task script to work with would auto-select AptX in dev options but no go. Hopefully, more AptX-HD phones will start arriving but I'm only aware of the new Bullets so far and those are neckband.
I'm also not sure if AptX-LL (low latency) might work, ie. LG will default to AptX-LL rather than AAC. So that might be some hope.
Click to expand...
Click to collapse
I have the PX as well. Once set to AptX HD, they remain there no problem. They are great headphones! I didn't even know this issue existed but once I got my new Sennheiser Momentum True Wireless buds it started to become apparent as they support both AAC and AptX...
Gesendet von meinem LG-H930 mit Tapatalk
Yep, I didn't know either until I upgraded to better earbuds that included both AptX and AAC. Luckily for us and our PX's, LG is kind enough to select AptX-HD over AAC. Presumably, same for LDAC on the Sony's.
And hard to find others that have discovered the issue too. Most probably wouldn't know unless they were aware of dev options.
StephenMSmith said:
Yep, I didn't know either until I upgraded to better earbuds that included both AptX and AAC. Luckily for us and our PX's, LG is kind enough to select AptX-HD over AAC. Presumably, same for LDAC on the Sony's.
And hard to find others that have discovered the issue too. Most probably wouldn't know unless they were aware of dev options.
Click to expand...
Click to collapse
Yeah it's quite a specific issue. Most probably don't know and/or even care. You have to have an LG device, a headphone that supports AAC as well AptX and know what dev options are, where they are and where to find the Bluetooth codecs (as well as what they mean actually). No surprise this isn't a very common or widespread issue
Gesendet von meinem LG-H930 mit Tapatalk
A bit late to the party but you can add _NOAAC to the end of your Bluetooth device name and it will skip AAC codec and use the next best option, in my case AptX.
ie "Lagoon ANC" becomes "Lagoon ANC_NOAAC".
It didn't work when I first got my phone but since the JAN 2020 update it started working, on a LG V40 (Android 9).
I've since switched to only earbuds and cans w/APTx Hd codec to get around this LG issue. Will try on my v35. How on earth did you figure out that adding this text to end of BT device name prohibits AAC crap?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone tried this? It's in developer options in stock Android 9. I don't use wireless earbuds, but you try it.
[email protected] said:
A bit late to the party but you can add _NOAAC to the end of your Bluetooth device name and it will skip AAC codec and use the next best option, in my case AptX.
ie "Lagoon ANC" becomes "Lagoon ANC_NOAAC".
It didn't work when I first got my phone but since the JAN 2020 update it started working, on a LG V40 (Android 9).
Click to expand...
Click to collapse
Seems I've got rid of all my headphone that had APTx and AAC (but not APTxHD) so can't test. Anxious if someone else will and report back.
Changing the BT codec in developer option doesn't stick and defaults back to AAC when your headphone reconnects, which is super annoying (ie everytime I get a drink or go to the bathroom). The _NOAAC trick gets past this annoying behaviour.
I found it in another XDA thread but didn't seem like a well known option, plus it only recently started working for me (assuming it's update related).
[email protected] said:
Changing the BT codec in developer option doesn't stick and defaults back to AAC when your headphone reconnects, which is super annoying (ie everytime I get a drink or go to the bathroom). The _NOAAC trick gets past this annoying behaviour.
I found it in another XDA thread but didn't seem like a well known option, plus it only recently started working for me (assuming it's update related).
Click to expand...
Click to collapse
So it won't work on stock then, as there's been no recent updates?
I own H930DS on stock firmware & unrooted. When my FW was still in stock Oreo, I also had this issue. Then when I upgraded to stock Pie (using LGUP, dirty upgrade), I only needed to select my preferred codec once from the developer settings, then it'd be my default setting. Hope this helps.
I don't have this issue. Only selected AptX once and it stayed there. H930 Stock Pie.
Quote:
Originally Posted by John Park;
"A bit late to the party but you can add _NOAAC to the end of your Bluetooth device name and it will skip AAC codec and use the next best option, in my case AptX.
ie "Lagoon ANC" becomes "Lagoon ANC_NOAAC".
It didn't work when I first got my phone but since the JAN 2020 update it started working, on a LG V40 (Android 9)."
Many thanks John. This trick worked on my LG G8s!!!
Fix works on LG Velvet 5G phone
[email protected] said:
A bit late to the party but you can add _NOAAC to the end of your Bluetooth device name and it will skip AAC codec and use the next best option, in my case AptX.
ie "Lagoon ANC" becomes "Lagoon ANC_NOAAC".
It didn't work when I first got my phone but since the JAN 2020 update it started working, on a LG V40 (Android 9).
Click to expand...
Click to collapse
Did exactly what you said and it works. My phone no longer reverts back to AAC codec and stays on aptX when turning earbuds (with AAC and aptX codecs) on. Thank you!
Related
Dear users who already decided to try Oreo roms, have you seen any settings related to Bluetooth codecs? Any signs of aptx or LDAC codecs?
Yes, seen but not tried.
Rishabh1x said:
Yes, seen but not tried.
Click to expand...
Click to collapse
Thank you. Can you report later if it's working or not?
LDAC works
mehrshad.shafaghi said:
Dear users who already decided to try Oreo roms, have you seen any settings related to Bluetooth codecs? Any signs of aptx or LDAC codecs?
Click to expand...
Click to collapse
Don't know sure about aptX as i didn't feel the difference in quality, but i can confirm that LDAC is working on Nitrogen OS (in pretty much all versions since it came out with Oreo). I am using the Sony MDR 1000X and it uses LDAC by default now, after oreo update. You can also manually change the codec from Bluetooth settings (turn LDAC on off for that audio device) or through developer settings, where you can choose the codec and even the bitrate, sampling rate etc etc. And it changes on the fly, so you can really feel the difference. LDAC is well worth it. But I've seen that on the highest quality, you need to be close to your device, else the sound can drop out sometimes.
agambhandari said:
Don't know sure about aptX as i didn't feel the difference in quality, but i can confirm that LDAC is working on Nitrogen OS (in pretty much all versions since it came out with Oreo). I am using the Sony MDR 1000X and it uses LDAC by default now, after oreo update. You can also manually change the codec from Bluetooth settings (turn LDAC on off for that audio device) or through developer settings, where you can choose the codec and even the bitrate, sampling rate etc etc. And it changes on the fly, so you can really feel the difference. LDAC is well worth it. But I've seen that on the highest quality, you need to be close to your device, else the sound can drop out sometimes.
Click to expand...
Click to collapse
Thanks for making effort and clearing things up.
LDAC is working perfectly on my OP3T with OS Beta 16.
Viper4android doesnt work though when headphones are connected with LDAC. I am using MDR-100ABN. Thye have LDAC and OP3T is streaming perfectly on that codec.
When I use my Jaybird X2s, codec switches to SBC automatically. Viper4android works on my X2s. I am not seeing AptX option in developer settings.
Hi
I have been searching for a way to enable aptx HD bluetooth codec for use with my aptx HD headphones, my model is an Eynos model and at the event Samsung stated it is compatible with aptx HD. My headphones only connect to my S9 plus in aptx but not HD like they do with other phone's. Does anyone know if the s9 plus actually has aptx HD or were we lied to? It's not even an option in developer's options menu. Any solutions? Thank you in advance
I've only been able to enable LDAC (which is fine since I have Sony headphones). I can't see any option on the SD model for APTX HD.
WorldIRC said:
I've only been able to enable LDAC (which is fine since I have Sony headphones). I can't see any option on the SD model for APTX HD.
Click to expand...
Click to collapse
There's no apxhd on exynos either.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No aptx HD
seezy said:
No aptx HD
Click to expand...
Click to collapse
I noticed that too, why did Samsung state it in their event when its not on the handsets?
So is there any announcements for aptx had? Can't find any statements on Samsung website or blogs.
So a friend own the SD S9+, Mine is exynos and since I noticed SD nor exynos got aptx hd.
seezy said:
View attachment 4443344
No aptx HD
Click to expand...
Click to collapse
Do you have any idea what 'Samsung HD' is? I presume it's something proprietary, but I've found loads of nothing via Google - even on Samsung's own site.
The lack of AptX HD is strange on a flagship like S9+. At least we have LDAC but you need to go in Developer Mode to enable it. Why? Don't get it. Anyway their history of bluetooth stack is less than stellar to say the least.
ixman said:
The lack of AptX HD is strange on a flagship like S9+. At least we have LDAC but you need to go in Developer Mode to enable it. Why? Don't get it. Anyway their history of bluetooth stack is less than stellar to say the least.
Click to expand...
Click to collapse
It is there, among a long list of others.
1. Enable Developer Options
2. In Developer Options, scroll down to Bluetooth Audio Codec
The list is:
SBC (this was selected when I went into the menu)
AAC
aptX
LDAC
Samsung HD
Scalable Codec
All codecs
Default codec
Now, I have no idea how the system (manages) theses - especially if you select (All codecs), or if you select one (like aptX), if it will only work with that.
Good luck.
Where is AptX HD in that list?
I can't get aptx to stay in Dev options. You can switch it to it. But when you leave and come back. It's back at sbc
Same for me... What's the point in enabling these options if they don't work. Samsung fail.
For me, if I'm connected to an aptx enabled device it selects itself automatically (and the option stays selected in dev options). Also, only while connected to an Aptx device, can I switch between SBC and Aptx.
For some reason I can't select AAC over Aptx, while the device I'm connected to does support both aptx as well as aac.
Edit: I can also confirm it supports AAC. Just tested it with an AAC only device (so no aptx support). Again, it just autoselects and doesn't use SBC.
S9+ here, looking at Monster Sports headphones.
Did anyone get AptX or any kind of quality codec going..
same
ramheer said:
Hi
I have been searching for a way to enable aptx HD bluetooth codec for use with my aptx HD headphones, my model is an Eynos model and at the event Samsung stated it is compatible with aptx HD. My headphones only connect to my S9 plus in aptx but not HD like they do with other phone's. Does anyone know if the s9 plus actually has aptx HD or were we lied to? It's not even an option in developer's options menu. Any solutions? Thank you in advance
Click to expand...
Click to collapse
Same issue, I have the Sony BX950BT and I hold down the volume up when I turn them on and it activates ACC / aptX Mode.
However on the SGSP+ even messing with developer options, I cannot get it to connect/stay active.
DroidBois said:
S9+ here, looking at Monster Sports headphones.
Did anyone get AptX or any kind of quality codec going..
Click to expand...
Click to collapse
My LG's support AptX, my S9+ (and my old S8+) both default to that coded by default. When using my home received it defaults to SBC. I think it should use whatever the BT device supports.
I agree this was a major oversight by Samsung in the current firmware. Why not just enable it native like LG.
Guys samsung as far as i can see on qualcomms website doesnt state aptx hd supoort only aptx quite unfortunate tbh
Honestly how can a "flagship" phone from the top mobile maker not include aptx HD. My pixel 2xl, LG v30 had it. Hell a oneplus 6 has it. Honestly between this and the USB-C audio issues this will be my last Samsung phone.
Sent from my SM-G965U using Tapatalk
I'm just using LDAC with Sony which is heaps better anyway.
Sent from my SM-G965F using Tapatalk
I have read the the device is support LDAC Bluetooth.
But when I change Bluetooth codec in developer setting to LDAC it got no sound. Testing with my fiio btr3 the indicator light change to white thae mean I using LDAC but got no sound.
The only codec that work is just sbc, aac and aptx.
Anyone know how to enable LDAC or just tell me that it not supported LDAC yet.
PS. When using the other codec it has worst quality than it should tho compare to my Nokia8. Why this happen?
sadin911 said:
I have read the the device is support LDAC Bluetooth.
But when I change Bluetooth codec in developer setting to LDAC it got no sound. Testing with my fiio btr3 the indicator light change to white thae mean I using LDAC but got no sound.
The only codec that work is just sbc, aac and aptx.
Anyone know how to enable LDAC or just tell me that it not supported LDAC yet.
PS. When using the other codec it has worst quality than it should tho compare to my Nokia8. Why this happen?
Click to expand...
Click to collapse
Bluetooth speaker/device should support also LDAC. Not only the Smartphone that have a LDAC capability
philipjan26 said:
Bluetooth speaker/device should support also LDAC. Not only the Smartphone that have a LDAC capability
Click to expand...
Click to collapse
i have the same issue. I have Sony wh-1000xm3 headphones. When i switched the LDAC codec. Sound just gone. Is anyone found a solution for this?
I search for it and found the samsung s9 s8 etc. phones have similar kind of problem. They have a solution for this. They just turn off the "dual audio" feature. But i cant find that setting in A3.
kaelthasxx said:
i have the same issue. I have Sony wh-1000xm3 headphones. When i switched the LDAC codec. Sound just gone. Is anyone found a solution for this?
I search for it and found the samsung s9 s8 etc. phones have similar kind of problem. They have a solution for this. They just turn off the "dual audio" feature. But i cant find that setting in A3.
Click to expand...
Click to collapse
Same thing, @kaelthasxx. I'm also trying to setup my wh1000xm3 with the Mi A3 and there's just no way of making ldac work. Not to mention that using aptx gets me an awful quality. If I run a frequency response test I get a lot of crackling at frequencies around 17-20khz with aptx.
The best quality I managed to get out of this setup was using sbc, which is a shame since the headphones support all the way up to ldac.
I think this is some issue with the OS (I'm using the phone's native Android One), since in theory the BT soc of this phone should support these technologies. Hope they fix it for Android 10.
I had install custom rom and it work just fine. Can't wait for official release tho
Sent from my MI A3 using Tapatalk
sadin911 said:
I had install custom rom and it work just fine. Can't wait for official release tho
Sent from my MI A3 using Tapatalk
Click to expand...
Click to collapse
What ROM are you using? The official one doesn't even support aptx properly (I get a lot of distortion using it with Sony's WH-1000xm3). Not sure if I should flash a custom ROM or pray for a fix in Android 10.
Anyone have a solution for this, just got some Sony Bluetooth cans for xmas and bow have same issue...
Is it confirmed fixed in Android 10 (ie a month or so factory fix all going well) or should I just go custom rom and fix it now (although the whole reason I went a3 was to get a stock Android device)
If I was to go rom route what's the suggested rom? I'm assuming a3 and a3 lite use the same base rom package?
Thanks to all in advance
G.
does anyone know if this problem has been solved with android 10?
sitolupion said:
does anyone know if this problem has been solved with android 10?
Click to expand...
Click to collapse
I can't confirm for LDAC, but AAC doesn't work, it always revert to sbc. For now is better to try a custom as bluetooth codecs never worked for me.
here you go! was also waiting for long months to access any better then SBC...
A3 with A10 stock, April version + Sony XM3, latest app version
--> AptX is on!
checked developer settings and this confirms. AptX is shown on (its not AptX HD by the way). trying to select any better eg LDAC wont stick when return from setting, also no codec effect.
at least something... good luck guys!
No
sitolupion said:
does anyone know if this problem has been solved with android 10?
Click to expand...
Click to collapse
No
Any update on this? How does the phone do with the latest firmwares?
(I plan to get Sony headphones)
Mi A3 with Android 11 here. No LDAC option, best is aptX but the WH-1000-XM4 dont support it so... best codec is AAC.
Our phone was announced to be capable of aptx and aptx HD. I own two different bluetooth receivers with aptx HD enabled. But when I connect the phone to them, it uses only aptx, as the connection info on our device and the LEDs on the receivers reveal. This behaviour did not change from Android 9 to 10.
My wife has a Mi A2, and with this device aptx HD works on both devices under Android 9 and 10. Is there a hidden way to activate aptx HD on our phone? Meanwhile I think our phone is heavily neglected by Xiaomi because such features present in a Mi A2 mysteriously vanished.
zapper19 said:
Is there a hidden way to activate aptx HD on our phone?
Click to expand...
Click to collapse
It's on developer settings.
Also, if forcing aptx HD is not working or has bugs, remember to report it.
This was the first thing I tried, but predictably switching to aptx HD in developer settings has no effect (I wonder what use these settings have - I never heard that someone succeeded in activating codes this way which his phone didn't choose automatically).
Update: I changed to crdroid 6.6 - and now aptx HD works flawlessly.
Hi sir, today I've got issue with connection to Fii0 BTR3K - no sound from PowerAmp which I was using for weeks without problems before. I did security update from May yesterday (yep late a bit) and got this issue. Fortunatelly to me I have SBH50 from Sony to test everything on low profile SBC connection. Lucky to me, I did another update to August security patch for Android 10 today.
Now I have Aptx LL ([email protected]) working with BTR3K (purple indication on LED). What I learned from today: Do not touch Dev settings! By misstake Dev settings could store your input as wrong data in 'system default' for application (PowerAmp in my case) and lead to missfunction. In my case PowerAmp was reading [email protected] even from non-aptX device. Second: actual condition of connection could be changed during SW initialization. So test your player SW and try to reset it as I did.
For specified [email protected] I am using Hi-Res output of PA. I am pretty sure in numbers as I can hear the difference between SBC and aptX, and hear difference with 16 to 24 bit resolution change (by enabling\disabling tone processing in ounput pipeline). To enable 24 bit in PA you should disable \reset to default dithering method.
I think AptX-HD isn't fully supported by 2 reasons: no real benefits over LL profile + licensing catch.
Hope you will learn something from my evidence
I have haylou gt1 plus earbuds. Apart from bad connection , the buds are aptx-HD compatible, one of their selling points. When i go to developer settings to check, aptx is used. When I change it to HD, it detects the change, nothing happens, and when I go back, and enter dev settings again, it is still on aptx . I think that's time to throw it in the sea... it's already blue
Sapper Morton said:
Your earphone doesn't support AptX-HD, that's why when your manually change to it using Developer Options, the codec isn't selected; use AptX or AAC, as advertised by Haylou.
Source:
https://haylou.info/gt1-plus.html
Click to expand...
Click to collapse
It's weird cause all reviews I read, specifically said aptx-HD, but you are right. It's only aptx. Nevermind. My mistake !
JaKats said:
I have haylou gt1 plus earbuds. Apart from bad connection , the buds are aptx-HD compatible, one of their selling points. When i go to developer settings to check, aptx is used. When I change it to HD, it detects the change, nothing happens, and when I go back, and enter dev settings again, it is still on aptx . I think that's time to throw it in the sea... it's already blue
Click to expand...
Click to collapse
Are you on android one?
Cause I'm on miui 12 and i have lots of issues. First left and right connects to the phone at the same time and then i have volume problems
I am almost ready to pull the trigger on buying this phone but just wanted to be sure of the audio options first.
If I pair my BT headphones and go into developer options then I can set the Bluetooth codec to aptx. Does this mean that the phone supports this? I have seen reports that aptx is not available on Samsungs but this seems to contradict that.
If I have to go into dev options and enable it myself - that is fine.
abaranov said:
I am almost ready to pull the trigger on buying this phone but just wanted to be sure of the audio options first.
If I pair my BT headphones and go into developer options then I can set the Bluetooth codec to aptx. Does this mean that the phone supports this? I have seen reports that aptx is not available on Samsungs but this seems to contradict that.
If I have to go into dev options and enable it myself - that is fine.
Click to expand...
Click to collapse
In the dev settings, there are these options:
SBC (active for me)
AAC
aptX
LDAC
Scalable Codec
But I'm not sure if aptx works. I'm using SBC with the Buds+
abaranov said:
I am almost ready to pull the trigger on buying this phone but just wanted to be sure of the audio options first.
If I pair my BT headphones and go into developer options then I can set the Bluetooth codec to aptx. Does this mean that the phone supports this? I have seen reports that aptx is not available on Samsungs but this seems to contradict that.
If I have to go into dev options and enable it myself - that is fine.
Click to expand...
Click to collapse
I tried it with my Haylou GT1 Xr that supports aptX recently and it worked just fine. Looked under dev settings and aptX was showing as currently used codec. You should be fine.