Database Develop

[Q] Bluetooth AD2P Sound Quality

Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.

I haven't noticed poor quality streaming at all... I have used it a lot.
Sent from my XT1058 using xda app-developers app

nonotechnology said:
Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.
Click to expand...
Click to collapse
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:

I have the same issue with poor sound quality when I stream music to my 2013 Subaru Legacy stereo. The problem seems to be that the sound is overly compressed and when a lot is going on it becomes especially noticeable. Part of the issue revolves around devices that don't support the newer APT-X codec, if the device supports that codec the sound is said to be fine however any device that uses straight A2DP will experience this issue.

djp952 said:
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Click to expand...
Click to collapse
I have had the same experience as you. I have tried my Moto X with about 10 different bluetooth receivers. I have had nothing but excellent sound quality.

djp952 said:
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:
Click to expand...
Click to collapse
I'm experiencing the same crappy BT audio I was with my galaxy nexus prior to your fix (thanks a lot BTW) on my moto x with the same BT receiver in my car. I've got a couple others I will try and report back later.

Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?

hyatari said:
Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?
Click to expand...
Click to collapse
I'm not sure either It's a good bet the Bose one does since its brand new. Seems like a pretty good theory!
I think I still have a really really old Scosche receiver kicking around somewhere I can try for you guys and compare it with an AOSP bluedroid-based phone.

http://www.csr.com/gogroove-bluesync-portable-bluetooth-speaker
Forgot to test on that which does have apt-x though I don't think it specifies in the manufacture or amazon site but that's the actual apt-x website. Can confirm that it definitely sounds better than my other devices.

Some Test Info if it helps
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.

mpkrcl said:
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.
Click to expand...
Click to collapse
I don't see any indication that states that deck supports apt-x. I read on the android bug report page that one user running 4.4 claims they've finally fixed this issue so I guess we wait for 4.4 now.

The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.

seh6183 said:
The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.
Click to expand...
Click to collapse
My Bose Infiniti head unit sounds amazing streaming Bluetooth from my wife's iphone4s and a load of rubbish while streaming from my motoX.
I'm very close to just saying screw it, giving in, and buying an iPhone.

Buy the iphone
Sent from my XT1056 using XDA Premium 4 mobile app

[Q] trusted bluetooth dongle

I would prefer that Motorola gave an option to permit touchless control to work with passwords - but that is not the case
I decided to explore finding a Bluetooth dongle I could carry as a trusted Bluetooth device and found http://www.amazon.com/gp/product/B008NH3IEW/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1 on amazon. While this works, there is a gotcha. What I am looking for is the dongle to keep the moto x unlocked while in my possession. When I am in my vehicle - I want the moto x to pair with the vehicle bluetooth.... The trouble is that the dongle I found presents itself to the phone as a headset, the same device type as the vehicle and I believe that the phone can only use one headset at a time. I could explore prioritizing the vehicle as higher than the dongle - but the dongle acts as an alarm and beeps if it loses connection with the phone....
soooo - does anyone know of a bluetooth dongle that is priced at throw-away prices that I can use as a trusted BT that I can carry - while permitting me to ALSO use the BT in my vehicle? This has to pass the "wife" test and just work without doing anything as it is for her phone.
The BETTER solution would be for Motorola to permit touchless to be configured to work while a phone is locked. I do not understand the security issues with enabling this functionality -- and even if there is to permit a user to make a decision. Afterall the touchless control is supposed to only respond to the owner - and while it is not perfect, it is not so bad. Come on Motorola - give us this option.

http://www.indiegogo.com/projects/gecko-make-your-smart-phone-smarter

murso74 said:
http://www.indiegogo.com/projects/gecko-make-your-smart-phone-smarter
Click to expand...
Click to collapse
Interesting - but a tad overkill for what I am looking for.
I will track it though

simard57 said:
Interesting - but a tad overkill for what I am looking for.
I will track it though
Click to expand...
Click to collapse
20 bucks though.. can't really go wrong.

murso74 said:
20 bucks though.. can't really go wrong.
Click to expand...
Click to collapse
for the webpage
"Works with iOS and Android 4.3 devices" so it wont work on the Moto X until it is updated?

simard57 said:
for the webpage
"Works with iOS and Android 4.3 devices" so it wont work on the Moto X until it is updated?
Click to expand...
Click to collapse
doh... missed that. lemme take a look
after reading it a couple of times it looks like only the gesture control requires 4.3. i can't imagine that just hooking up a bluetooth dongle would require that much

MTCB/MTCC Rom issues with ALPconnect app and Bluetooth

Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse

Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk

shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.

agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?

shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.

Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk

agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second

I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.

I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.

I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk

Does anyone know the location in the Android file system where the Bluetooth pairings are saved?

FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.

This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.

The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!

monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?

multiple Bluetooth speakers?

Hi,
I was wondering if it could be possible to port a feature from Samsung that allows multiple Bluetooth devices to be connected to the same phone? I don't know if this is something that already is implemented in Pie? Developer options show 'maximum connected Bluetooth devices: 5', so maybe there's something I'm missing?

That's a feature of Bluetooth 5.0. Not sure you can add support for a different Bluetooth version like this at all. Look at the Bluetooth version your phone supports.

gk1984 said:
That's a feature of Bluetooth 5.0. Not sure you can add support for a different Bluetooth version like this at all. Look at the Bluetooth version your phone supports.
Click to expand...
Click to collapse
Yes it has Bluetooth 5.0. I'll dig into it. Thank You for Your answer!
Ok so the device has to have the dual audio feature currently on Galaxy s8.
And the peripherals have to be 5.0 as well. So, no dice yet for me.
Someone has made a library:
https://stackoverflow.com/questions/19207033/connect-multiple-devices-to-one-device-via-bluetooth

play an audio on voice call Rooted Android 9

I have a task for one of school project to allow play a short audio on voice call. I've been searching for long time for a solution to that problem or at least a starting point, I found some topics that talking about modifying the kernel of android to allow this but I have no idea how to do The project needs to be done in latest android versions ( 10 or 9) with Samsung devices (S10 for example ) which are rooted Thank you

FearNaiim said:
I have a task for one of school project to allow play a short audio on voice call. I've been searching for long time for a solution to that problem or at least a starting point, I found some topics that talking about modifying the kernel of android to allow this but I have no idea how to do The project needs to be done in latest android versions ( 10 or 9) with Samsung devices (S10 for example ) which are rooted Thank you
Click to expand...
Click to collapse
what is it exactly that youre trying to accomplish?

youdoofus said:
what is it exactly that youre trying to accomplish?
Click to expand...
Click to collapse
Thank you for your replay. I'm trying to stream an audio clip through the system on voice call. Means when I am in phone call talking to someone, I can play a short audio clip that can be heard by the other party too. The project is for personal purpose, it means only me that can be using that option, so I can root my device or make a custom rom, I just need to know how i can do that things
Thank you

FearNaiim said:
Thank you for your replay. I'm trying to stream an audio clip through the system on voice call. Means when I am in phone call talking to someone, I can play a short audio clip that can be heard by the other party too. The project is for personal purpose, it means only me that can be using that option, so I can root my device or make a custom rom, I just need to know how i can do that things
Thank you
Click to expand...
Click to collapse
you shouldnt need root to have an apk play audio at the push of a button while on a phone call at the same time

I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC https://www.google.com/search?safe=...i29i30j0i10i30j0i10i203j35i362i39.7TvHA0zwoeQ)

profi_fahrer said:
I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC https://www.google.com/search?safe=...i29i30j0i10i30j0i10i203j35i362i39.7TvHA0zwoeQ)
Click to expand...
Click to collapse
this is what i was expecting android to do automatically, and in many cases it does it seems. I was reading about this a bit last night and saw where people were indeed able to play something on the speaker of their phone and have the very same phones mic and play on the phone call for both parties to be able to hear. It was a native in the phones where users reported this ability. It was even reported to work on some older samsung phones. I still have a S4 and could test it out, if i remember to do it (my license plate says IFORGOT). @AthieN this is the thread i was talking about

youdoofus said:
this is what i was expecting android to do automatically, and in many cases it does it seems. I was reading about this a bit last night and saw where people were indeed able to play something on the speaker of their phone and have the very same phones mic and play on the phone call for both parties to be able to hear. It was a native in the phones where users reported this ability. It was even reported to work on some older samsung phones. I still have a S4 and could test it out, if i remember to do it (my license plate says IFORGOT). @AthieN this is the thread i was talking about
Click to expand...
Click to collapse
So basically, they told me that they used to record uing Tinyalsa library (tinycap exactly), but they couldn't do it with samsung S10, when I search I found that there is not tinyalsa included in that phone. So I was wondering if I can add it directly to the system or I have to make own rom for that ?
I hope @AthieN can give us hint on that. Thank you both of you for your help
profi_fahrer said:
I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC )
Click to expand...
Click to collapse
That's seems a good idea but idk if applicable to android devices or not

Sorry for the late reply. This used to be possible, but not since API 20 or 21 due to security concerns.