Develop Bugs

[Q] Bluetooth compatability

I'm thinking of upgrading to this phone, one of the main reasons is that my current device, which has galaxy S guts, is not compatible with most bluetooth devices. I like to use an app called blueputdroid that turns my phone into a universal keyboard as well as an ELM bluetooth device that turns my phone into a dyno along with the torque app for my car.
For some reason the way samsung built the bluetooth makes it not work with a lot of these things, I know it's not the apps or 3rd party devices as I use my old G1 now for it, but would much rather just have my main phone be my one device.
Have any of you tested blueputdroid or any bluetooth devices? If not could someone try out blueputdroid with this phone (it's free in the market) any help would be much appreciated thanx!!

Says it has detected unsupported Bluetooth stack.. Install cyanogen Rom, etc.

Thanks, at least this phone is likely to get cyanogenmod support which will fix the problem my SK sure as hell won't

My GS2 works perfect with my ELM adapter. It worked perfect with my Vibrant too. I've never had a single problem with any bluetooth device on either of them.

I've had a lot of bluetooth problems with both my vibrant and now my GS2. Both work reliably with my wife's mini cooper bluetooth but they both have had problems connecting to the garmin nuvi I use for handsfree in my car (and forget about the A2DP on it).
I tried a lot of roms on my vibrant (incl stock) and they did lots of cool stuff but never made the BT connect reliably. Then I came across this thread: http://forum.xda-developers.com/showthread.php?t=795691
I made the suggested change to /system/etc/bluetooth/audio.conf and voila! I finally have good BT with my vibrant.
So I got my SG2 last week, rooted it and found that it also had the bad settings in /system/etc/bluetooth/audio.conf. However it also lacked BLN (backlight notification) and few other tweaks I've come to love on my vibrant so I flashed juggernaut 2.6. That fixed all the major foibles with the SG2 but it still won't reliably connect to my garmin.
I opened up the filesystem to find that /system/etc/bluetooth/audio.conf is no longer there! Does anyone know where it went?
Apparently I don't have enough posts to ask in the dev forum where juggernaut was posted http://forum.xda-developers.com/showthread.php?t=1322642 so I'm hoping someone will see this plee for help.
thanks

the phone has BT 3.0, but it is backward compatible with BT 2.0 and 1.0 devices
i haven't had any trouble using it with my car deck (streaming audio & phone), my large collection of stereo BT devices, and other BT enabled phones & PCs/Laptops
the remote control feature from the stereo headsets works properly, for fast forward, backward, play, pause, talk, mute, etc
the only thing i have yet need to test BT on is with a BT smart wrist watch

Bluetooth version & BMW music streaming

I wondered if anyone can help with my query regarding getting music streaming to a BMW 320ED via Bluetooth?
The good news is that I can get my Galaxy Nexus (GSM 4.1.1 stock software) to pair with the car and I can get music playing via Bluetooth, but I can't see the artist information. The car screen informs me that the device doesn't supporting sending track information, or something along those lines.
What frustrates me about this is that my friends iPhone 4S does stream the track information as well as the actual audio. I Googled to see what Bluetooth version both phones use, apparently the iPhone 4S is Bluetooth 4.0 and the Galaxy Nexus has 4.0 capable hardware but only 3.0 features are available due to software limitations.
Is this true? Is once of the differences between Bluetooth 3.0 and 4.0 the ability for track information to also be shared? I was using Google Play Music if that makes any difference.

I've done some more research about this and thought I would update my post, just in case it's of help to anyone facing a similar issue. Turns out the Bluetooth protocol/profile AVRCP is responsible for streaming music tags to the car stereo, but only AVRCP 1.3 and above. Unfortunately the Galaxy Nexus only supports 1.0 by default but CyanogenMod 10 has built in support for 1.3 since roughly the 14th September nightly.
Should be able to test it out next week at some point. Why are Google so bad at supporting the latest Bluetooth features? I've always found this with Google experience devices to lack in this area where other manufacturers support the latest Bluetooth features.

Bluetooth AVRCP 1.3 - Cannot hear media

so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!

RBalber said:
so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!
Click to expand...
Click to collapse
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.

osurferx said:
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.
Click to expand...
Click to collapse
Ok... I've confirmed it has to be AVRCP 1.3
Last night I took advice. I installed Jelly Belly 9 "4.1.2" w/ reverted AVRCP 1.0 because of BT issues, and this morning I went to work, tested connection with BT and everything worked! So... Looks like the issue lies with AVRCP 1.3. I don't see metadata on screen anymore but it doesn't bother me, I'd rather have all other media players working.
To touch on what others are saying, statements Google Music works perfectly fine with AVRCP 1.3 based ROM's as well as voice through BT. It's just the other media players i.e; pandora, slacker, youtube, notifications, etc.... that don't work. I'm guessing from what I read, is that the applications do not support AVRCP 1.3 and will not push to Toyota head units properly. Not sure if this is going to get fixed or not, but sucks because this limits what I can/can't use for ROMs at least a solution was found and reason why. Thanks bud!

You could also try https://github.com/loganakamatsu/PandoraAVRCP for the Pandora patch. Maybe patches exist for other apps as well...

I read on another thread that any app that supports the Scrobble Droid API hxxp://code.google.com/p/scrobbledroid/wiki/DeveloperAPI will pass the meta info to AVRCP. So I assume if you install ScrobbleDroid app hxxps://play.google.com/store/apps/details?id=net.jjc1138.android.scrobbler&hl=en from the play store any app that it is compatible with will also pass the meta info to the display.
As noted, Pandora is not supported as it does not broadcast its intents. I personally had issues getting the PandoraAVRCP github to patch. If anyone has a patched pandora.apk, I would certainly appreciate a PM.
Good luck.

Voice Dictation/ Google Now/ S Voice not working

I've now confirmed this bug on two separate Galaxy S III's as well as a Note II, all running stock software from T-Mobile. When bluetooth is on voice dictation doesn't work, google now sticks on "initializing," and s-voice sticks as well.
Is there a fix for this? I'm reading on google's bug tracker it's a known issue and there a resolutions on xda, but I can't find anything.

Known error with the 4.1 version of GVS. It is reportedly fixed in the 4.2 version, but that one introduces other issues. I have no idea what the status is of XDA work on the problem. The quick and easy fix is to uncheck media audio under your bluetooth pairing, as it seems to be an A2DP initialization issue.

[SOLUTION] Fix for 4.3: unable to power on WiFi and/or Bluetooth

I update my Samsung Galaxy Note 2 to Android 4.3. Sometimes the WiFi goes off without reason and it was not possible to switch on WiFi or Bluetooth. I found that this was caused by two of my Bluetooth devices. I had to go outside out of range of Bluetooth devices and then switch Bluetooth on and then delete pairing I had in the phone (since previous Android 4.1.2 version). Hope it helps somebody as I'm not alone as I saw when digging through Internet forums.
BTW: WiFi & Bluetooth share the same chip, so it seems like a bug in Bluetooth kernel driver or library that manage Bluetooth connections. THERE IS NO NEED TO FLASH ANYTHING!