Develop Bugs

bt audio stream to the pc

I must be blind but I haven't found any info on how to stream sound from my desire to my pc through bluetooth service. I have a bluesoleil installed on my pc and AV Headphone service is activated. Still I cannot figure out how to play sound though the bt
any hints?

Same Here,
I have stereo audio and telephony audio gateway services, but the desire just sees it as a computer. It doesn't see that it can be a headset or a speaker... The bluetooth is really simple, it doesn't list services etc.
How do we get it to work?

make sure u have bluetooth on and discoverable on both devices. on pc add a new device, pair it. if u have w7 go to control panel .view devices and printers, click on the phone nad the bt screen will come up. click connect. on the desire just play a music track

JaykaySLO said:
if u have w7
Click to expand...
Click to collapse
nope, xp here. Devices are paired but nothing happens. Desire simply does not see audio service started. Music goes to dynamic as usual.

more hints needed pls

# Windows XP: Does not natively support A2DP, but newer Bluetooth USB dongles and built-in adapters include drivers with A2DP support.

JaykaySLO said:
# Windows XP: Does not natively support A2DP, but newer Bluetooth USB dongles and built-in adapters include drivers with A2DP support.
Click to expand...
Click to collapse
as I said I've activated audio sink on the pc. I think this is the a2dp profile
and yes it does support a2dp
http://www.mercateo.com/p/C1003-2156959/Gembird_BTD_MINI2_Tiny.html

iphone bluetooth receiver with apt-x

i have a mini cooper, and it supports Iphone docking. it also supports msc drivers, but with newer android phones, MSC isn't really available.
anyway, i just realized there are devices that basically (Bluewave Bluetooth Audio Receiver) that emulate the iphone, but gets it's signal via bluetooth. so i can pair my phone to it, which would in turn relay the audio to my car...and hopefully, my car would think it's an iphone, and all the corresponding features would still work.
has anyone had any experience with these? would i be able to control my phone audio via my car's control? would the headset display song titles?
anyonw know one that support apt-x?

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.

Alternate BT that can connect to XGPS160? [Rockchip PX5 A53 | Android 9.0 | 4GB RAM]

(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!

There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!

deja100 said:
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
Click to expand...
Click to collapse
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.

Bob_Sanders said:
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
Click to expand...
Click to collapse
Yeh I found that threat in my searches, but no one in there quite mentioned this specific scenario (Selecting one of the other options in the Bluetooth settings) so I wasn't sure. And I'm definitely not opening up the unit and cutting on the hardware; hacking config files I can do all day long, but I have no skills when it comes to soldering so I'd probably just destroy the radio in the process of trying to cut that module :laugh:
Yeh I've run the OBDLink EX with Torque as well for data logging temps on track and it worked flawlessly for that as well. BT is definitely more convenient, especially since most are running apps from their phones, but if you have a dedicated radio like these then it's a no-brainer to permanently wire up a USB device.

marchnz said:
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Click to expand...
Click to collapse
When you say "hacked BT implementation" I'm assuming you mean they don't use the standard Bluetooth stack built into the Android OS? That would make sense, as when I try to do anything with bluetooth from the standard Bluetooth settings menu, it doesn't do anything, doesn't see any devices available for pairing, or anything else. You can only see other devices and pair to them from the PUMPKIN Bluetooth app; the funny thing is it will go through the first steps and show the XGPS160 as being paired, but none of the apps that use the GPS actually see it as a paired device (my OBD dongle shows up, but not the GPS).
I don't understand why they didn't just use standard bluetooth that's already part of the OS, rather than use some hacky custom solution

Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/

deja100 said:
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
Click to expand...
Click to collapse
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.

marchnz said:
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
Click to expand...
Click to collapse
Yeh, that's extremely disappointing Does anyone know of any Android based radio units that have full working bluetooth? I don't mind buying a new unit for the car if I know it will work with everything.

The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk

ikerg said:
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Bummer they don't make those units anymore :/ Then again, they may not have been powerful enough to run my track timer apps anyway.