Hello, can anyone who bought Moto Z Play confirm it supports aptX audio codec and successfully play audio through an aptX connection to an aptX supported audio device, or confirm it does not? On the official pages and GSMArena specs I saw only A2DP which is SBC codec.
I wrote to Lenovo tech support and they responded they don't know anything about aptX then suggested me ask aptX team. So wrote another e-mail and seems that the response will be slow. So does anyone can kindly prove it here? Thanks you.
There is another way to confirm, one can check if there is a file named something like libbt-aptX-ARM-4.2.2.so under the path /system/lib/ which means this device supports aptX codec. Can somebody confirm this?
RenoYeh said:
Hello, can anyone who bought Moto Z Play confirm it supports aptX audio codec and successfully play audio through an aptX connection to an aptX supported audio device, or confirm it does not? On the official pages and GSMArena specs I saw only A2DP which is SBC codec.
I wrote to Lenovo tech support and they responded they don't know anything about aptX then suggested me ask aptX team. So wrote another e-mail and seems that the response will be slow. So does anyone can kindly prove it here? Thank you.
Click to expand...
Click to collapse
RenoYeh said:
There is another way to confirm, one can check if there is a file named something like libbt-aptX-ARM-4.2.2.so under the path /system/lib/ which means this device supports aptX codec. Can somebody confirm this?
Click to expand...
Click to collapse
There is a file with the exactly name you said on that folder. So i am inclined to think it has support to aptX codec.
Even the first Moto G supported aptX, last years Moto X Play supported aptX, even though Motorola did not mention it anywhere. Somehow they never talk about aptX but one can take it as granted.
Weird how aptx support almost never seems to be marketed or even mentioned. It costs money to license, you'd think hardware makers would at least tuck the info somewhere. Not that I'm implying that this phone absolutely does support it, as much as circumstantial evidence would suggest. Only way to be sure would have someone with one of those devices that light up some indicator when it's supported test it and chime in.
I'm using Moto Z transmitting to Cambridge BT100, and the LED on the Bluetooth dongle blinks every 2 seconds. That means apt-x is ON!
Recently I bought Huawei Freebuds and it works quite well.
However, 5T can't connect with freebuds by AAC codec even though freebuds supports AAC codec and other bluetooth 4
.2 devices works through AAC very well.
Is there anyone who have connected Freebuds with 5T through AAC codec?
Alredy asked to Oneplus bughunters and submitted my bluetooth logs, but haven't received any replies for a while.
Hey! Same problem here. Shame they don't support AptX... The video lag is horrible...
Same here.
Many problems (1s decal, some bad connexion ...)
wanxu said:
Hey! Same problem here. Shame they don't support AptX... The video lag is horrible...
Click to expand...
Click to collapse
xstu25 said:
Same here.
Many problems (1s decal, some bad connexion ...)
Click to expand...
Click to collapse
Glad that it's problem for everyone, just not for mine. Thought mine is defective.
I sent bluetooth log to Oneplus dev team and it was submitted to JIRA. Hope there would be an relevant fix on future OOS or firmware update for Freebuds from Huawei.
With the global version 9.6.7.0 (OEDMIFD) neither LDAC or aptX are working. Even when trying to enable them in developer options.
I'm using it with my shanling m0 DAP which shows the codec being used. With my other phone running Android 8, LDAC is activated. Here only AAC works.
It also works on my friends Pocophoe running MIUI 10.
Anybody got it running or will I have to wait until MIUI 10 is out?
Hi, did you managed to solve this problem? Have you tried updating to latest V10.0.1.0.OEDMIFH to see if that fixed the problem?
Yes, I updated last week and LDAC is working perfectly fine now. Thanks for asking
If Bluetooth headphones support both codecs the phone will always select AAC. I can go into developer options and change it to aptX but the next time I connect the headphones it changes back to AAC. Has anyone found a solution to this? I definitely prefer aptX quality.
Sent from my LM-G820 using Tapatalk
immerstark said:
If Bluetooth headphones support both codecs the phone will always select AAC. I can go into developer options and change it to aptX but the next time I connect the headphones it changes back to AAC. Has anyone found a solution to this? I definitely prefer aptX quality.
Sent from my LM-G820 using Tapatalk
Click to expand...
Click to collapse
You're doing it wrong. Going in dev options is not the sollution.
You must do this:
After you paired the headphones to Bluetooth, go into Bluetooth settings for the headphones and enable priority to sound quality. Long press bluetooth icon when the headphones are connected, then click on the settings icon of the headphones and select priority to sound quality.
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Inerent said:
You're doing it wrong. Going in dev options is not the sollution.
You must do this:
After you paired the headphones to Bluetooth, go into Bluetooth settings for the headphones and enable priority to sound quality. Long press bluetooth icon when the headphones are connected, then click on the settings icon of the headphones and select priority to sound quality.
Click to expand...
Click to collapse
The only settings available for my headset are toggles to enable or disable call audio and media audio. Are you giving instructions that work on a pure version of Android like a Pixel or Nexus device would have?
Sent from my LM-G820 using Tapatalk
Here
If you don't have it, then headphones are cheap...
LDAC for example
Inerent said:
LDAC for example
Click to expand...
Click to collapse
Mmmkay, yours are using Sony's proprietary codec. The issue arises when headphones support both AAC and aptX. I have a speaker that only supports SBC and aptX HD and I'm able to select between quality or stability.
Sent from my LM-G820 using Tapatalk
This is the solution!
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOACC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
A thousand thanks. It does work!!!!!! [emoji16]
Sent from my LM-G820 using Tapatalk
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
immerstark said:
A thousand thanks. It does work!!!!!! [emoji16]
Sent from my LM-G820 using Tapatalk
Click to expand...
Click to collapse
I'm glad that it works for you guys although it doesn't work on my Sprint LG G8. :silly:
I have the unlocked Amazon version, which incidentally doesn't have the Google Assistant button at all.
Sent from my LM-V450 using Tapatalk
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
Confirming this works on my AT&T LG-G8 with wireless earbuds that supports the codec set {SBC,AAC,AptX}. A huge fix to an annoying problem I've had with these headphones; thanks!
Bizarrely this works on my Boost Mobile Samsung Galaxy S8+, so I'm thinking it's baked into Android. Also work on my Sprint LG V50.
Sent from my LM-G820 using Tapatalk
It boggles my mind that a phone that lives on it's audio quality would fail this miserably at bluetooth.
---------- Post added at 05:22 PM ---------- Previous post was at 05:16 PM ----------
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
I've tried this and it is still defaulting to AAC in the developer options
it works
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
It works on my of g7 thinq Italian version and my cheap but fabulous soundcore life p2 twrue wireless buds supporting aac and aptx.
Thank you a lot.... also more!
Such a supremely elegant solution - can't believe this is the only thread I can find about this. Now, if only I could find out how to get my WH-1000XM3's to connect via AptX HD by default instad of LDAC, I'll be laughing!
_NOLDAC?
Sent from my LM-G820 using Tapatalk
Good news here, I updated my Sprint LG G8 to Android 10 (20a) that was leaked recently, and tested _NOAAC method that didn't work on Pie, finally works now.
Works on LG Velvet
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
Had the same problem with my Sennheiser CX 400BT (has AAC and aptX codecs) and my LG Velvet 5G (has multiple codecs). Changed the codec from AAC to aptX in Developer Options. Powered off my earbuds and powered them back on and LG would default codec to AAC. Did exactly what you said by changing bluetooth name from 'CX 400BT TW' to 'CX 4000BT TW_NOAAC' and codec on Velvet stays on aptX and no longer defaults back to AAC. It works.
Fantastic! Thank you so much. Searched for a solution for a couple of hours.
My G8 thin Q works with an aptx HD headset after I added _NOAAC so thanks for this suggestion.
I see that in the Bluetooth configuration screen for the headset, there is indeed a setting to switch to highest quality (as opposed best connection, which seems to be the default). Changing that may fix the problem, if the name change by itself doesn't work.