hey there,
today ive tried to connect to aptx device, in logcat i see that the other device is offering aptx, but it seems that it wont be used. Anyone here who can help?
Ive also tried this, somone wrote there that it is working on his MI6 device which has the same chipset:
https://www.mobilefun.co.uk/blog/20...our-oneplus-xiaomi-pixel-or-nexus-smartphone/
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.
So our phones have a Qualcomm 845 SoC, which afaik supports Qualcomm's TWS+. This would allow an individual bluetooth connection to both left and right earphones, if you have a pair of bluetooth TWS that also supports TWS+.
I finally updated to the latest Feb update of 10/Q from the Aug 9/Pie software on my phone yesterday, just to see if TWS+ was available and working. I've been hoping for it for a quite a while now, really since I got this phone. It will potentially give 1.5-2x more battery life for some of my BT earphones.
I'd like to enable this feature or know if it's going to finally be added to the Pixel 3 XL. Is there a way and I've just missed it?
Check Bluetooth settings in developer options
ktmom said:
Check Bluetooth settings in developer options
Click to expand...
Click to collapse
Not an option in developer options.
I do have # of BT connections set to 5, which is the same as default.
You don't have a codec or channels configuration in developer options?
ktmom said:
You don't have a codec or channels configuration in developer options?
Click to expand...
Click to collapse
I do. Codec or mono/stereo isn't what TWS+ does. Codec is how the audio is encoded, mono/stereo mode is whether is sending mixed/mono audio or L&R stereo audio.
TWS+ is Bluetooth being connected to each earphone directly. Instead of the older method of connecting to a single 'master' earphone which then transmits to the second 'slave' earphone.
https://www.qualcomm.com/products/features/truewireless
assassin10000 said:
I do. Codec or mono/stereo isn't what TWS+ does. Codec is how the audio is encoded, mono/stereo mode is whether is sending mixed/mono audio or L&R stereo audio.
TWS+ is Bluetooth being connected to each earphone directly. Instead of the older method of connecting to a single 'master' earphone which then transmits to the second 'slave' earphone.
https://www.qualcomm.com/products/features/truewireless
Click to expand...
Click to collapse
What earphones are you trying to use this with? I'm thinking you might have to download their specific app to enable the feature
KUSOsan said:
What earphones are you trying to use this with? I'm thinking you might have to download their specific app to enable the feature
Click to expand...
Click to collapse
Mavin Air-XR, no app but does have TWS+.
It's not an app or 3rd party software that is the issue. TWS+ support on BT earphones is part of the chipset and with or without a supporting app it will work. It just has to be supported and enabled on the source device, as it's the source device that connects directly to each earphone.
If you can get the files from another device that has 845 SoC and has it enabled you could use magisk to make a module to enable it. Seems the lib files are not on our device. Not sure what all the libs needed are, sorry.
assassin10000 said:
Mavin Air-XR, no app but does have TWS+.
It's not an app or 3rd party software that is the issue. TWS+ support on BT earphones is part of the chipset and with or without a supporting app it will work. It just has to be supported and enabled on the source device, as it's the source device that connects directly to each earphone.
Click to expand...
Click to collapse
So how do you know it's not already enabled? Are you able to connect just the left one and hear sound? I believe if it's just regular Bluetooth wireless it's usually always the right headset that handles the connection that's how it was for my Jabra and my brother's bragis
Under the Qualcomm website for the SD845 SoC it just says true wireless stereo and I don't see any mention of true wireless stereo Plus
(((((EDIT)))))
Here's the link for the true stereo 'plus' filter and I don't see any of the flagship SoC's listed. Oddly enough it's the budget style ones that seem to have it lol
https://www.qualcomm.com/products/c...yZW8lMjBQbHVzJTIwdGVjaG5vbG9neSUyMiU1RCU3RA==
I think you are SOL
wangdaning said:
If you can get the files from another device that has 845 SoC and has it enabled you could use magisk to make a module to enable it. Seems the lib files are not on our device. Not sure what all the libs needed are, sorry.
Click to expand...
Click to collapse
A bit beyond me. But that would be awesome if I can figure it out.
KUSOsan said:
So how do you know it's not already enabled? Are you able to connect just the left one and hear sound? I believe if it's just regular Bluetooth wireless it's usually always the right headset that handles the connection that's how it was for my Jabra and my brother's bragis
Under the Qualcomm website for the SD845 SoC it just says true wireless stereo and I don't see any mention of true wireless stereo Plus
(((((EDIT)))))
Here's the link for the true stereo 'plus' filter and I don't see any of the flagship SoC's listed. Oddly enough it's the budget style ones that seem to have it lol
https://www.qualcomm.com/products/c...yZW8lMjBQbHVzJTIwdGVjaG5vbG9neSUyMiU1RCU3RA==
I think you are SOL
Click to expand...
Click to collapse
If TWS+ was working when connected BOTH earphones would show up as connected (only one active) in the Bluetooth list.
As it stands, only the Left shows connected and if turned off music turns off on the right. My Tronsmart, Mavin and Sabbat all use the left as the main connection. Other MFG such as Jabra use the right.
Tws + does not work either.
The same problem, only on another phone (Xiaomi mi 9t). On MIUI firmware, tws + works fine, but when I install the Pixel Experience firmware, tws + stops working.