Develop Bugs

Noob question about listening to MP3s through Bluetooth headsets.

Is there any way to do so? I did overlook the manual and did use the search feature and unfortunately i'm very much so a noob when it comes to avanced smartphone users. Any tips would be appreciated. Thanks.

imwillzillla said:
Is there any way to do so? I did overlook the manual and did use the search feature and unfortunately i'm very much so a noob when it comes to avanced smartphone users. Any tips would be appreciated. Thanks.
Click to expand...
Click to collapse
If you are running windows mobile 6.0 or earlier - then search on these forums (or google) for "BTAudio". this is a utility that when run, will redirect music to your bluetooth headset. Installing it may be just a tad difficult for a newbie - but it is very simple really.
If you are running 6.1 then redirecting to your bluetooth is an option when turning your bluetooth device on. On mine, when I choose (turn on) my bluetooth device via the connections settings, there is an option for "Set as wireless stereo"
Hope this helps or at least points you in the right direction

cornell2 said:
If you are running windows mobile 6.0 or earlier - then search on these forums (or google) for "BTAudio". this is a utility that when run, will redirect music to your bluetooth headset. Installing it may be just a tad difficult for a newbie - but it is very simple really.
If you are running 6.1 then redirecting to your bluetooth is an option when turning your bluetooth device on. On mine, when I choose (turn on) my bluetooth device via the connections settings, there is an option for "Set as wireless stereo"
Hope this helps or at least points you in the right direction
Click to expand...
Click to collapse
Im just guessing that the headset requires it to be...AD2P i think its called correct? because i have a plantronics explorer 220 and im not able to get that setting.

Use the BTAudio
iamanalog said:
Im just guessing that the headset requires it to be...AD2P i think its called correct? because i have a plantronics explorer 220 and im not able to get that setting.
Click to expand...
Click to collapse
Use the BTAudio. it works with my Explorer 220
BTY it isnt stereo (unless you have two of them)

This will do the trick!
This will allow you to listen to all audio coming from the handset through bluetooth regardless if the bluetooth device is mono or stereo! I love this tool!

[Q] A2DP bluetooth autoconnect immediately disconnects?

Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?

I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!

bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.

jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.

It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.

I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.

I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse

jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!

Force bluetooth "phone audio" from nexus 7?

Nexus 7 2013 WiFi
Stock 6.0.1 rooted with Timur's Kernel v4
For some reason when I BT connect my tablet to ANY pioneer head unit (tried 3 so far) I don't get the check box in bluetooth options for "phone audio" . I am using the Verizon messages+ app to make calls and receive texts over wifi Hotspot from my phone. This works amazingly but for some reason I can't get it to route through to the pioneer bluetooth connection. I tried a set of bluetooth headphones and the phone audio checkbox is there and it works flawlessly.
I did some Google searching and searched this sub but don't see anything relating to this problem.
edit: see below for update
Is there a way to force a bluetooth profile to use "phone audio"? Is there a Config file anywhere I can manually edit?
I've tried Bluetooth Auto Connect and choosing the phone audio option for the head unit but it did not change anything.

I assume your nexus is lte ?

deadgiveaway said:
I assume your nexus is lte ?
Click to expand...
Click to collapse
Sorry should have put that info in the initial post. No, it is the WiFi model.
I would be wifi tethering my phone to get network connectivity. This is a Nexus 7 carputer type build.
Bit of an update though:
Per a website that I cant post a link to until i make 10 posts.... It looks like the nexus 7 2013 lacks the HFP (Hands Free Profile) by default. Now I'm not entirely sure why the bluetooth headset works if this profile is not present other than its possible the headset uses the HSP (Head Set Profile) but I can't seem to find any documentation on if the N7 actually has the HSP.
Through extensive googling, I ended up at posts talking about Bluez bluetooth stack implementation. This is a bit over my head though and cant really find any solid documentation on implementing it on Stock 6.0.1
I also ended up getting directed to the source.android page that mentions at the bottom:
Custom Bluetooth profiles - If you want to add Bluetooth profiles that do not have HAL interfaces provided by Android, you must supply an SDK add-on download to make the profile available to app developers, make the APIs available in the Bluetooth system process app (packages/apps/Bluetooth), and add them to the default stack (system/bt).
Click to expand...
Click to collapse
But like I said, this is over my head.
Anyone with any sort of experience give me some insight?

LG phone always defaults to AAC instead of aptX

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.

Can TWS plus be enabled?

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.