Develop Bugs

Bluetooth Connectivity With My Car

After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks

I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.

I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.

I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.

I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d

I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).

If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.

[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!

[Q] Multiple device over Bluetooth issues since ICS

Situation:
I'm using a Xlink bluetooth gateway in my house to connect my phone with and I also have a Mazda CX-5 with integrated Bluetooth system with the latest update from TomTom and Mazda. In the Mazda, I use the Bluetooth mainly for the phone, but occasionally use it to stream audio.
Phone:
T-Mobile samsung S2 x SGH-T989D with ICS 4.0.4 (Rogers leak)
Issues:
At first (With official Gingerbread)... everything was working fine. Both device paired and all functionality worked.
Then, applied official ICS update from Kies software ICS 4.0.3 and Bluetooth issues started. I first paired my Xlink device. So far it worked. Then tried to pair my Mazda, everything was really slow but managed to have it work. Turn the car off, get back in the house and the phone is now able to pair with my Xlink device, but cannot connect as a phone audio. Even if I go manually in the Bluetooth menu and try to activate the Phone audio it wont work. Only way to have it work again is to unpaired the Mazda and reboot.
After reboot, the phone works great in the house with my Xlink device. Going back to my car and try to pair my Mazda. Same issue. The phone does pair with the Mazda, but I'm unable to make a call since the phone cannot activate the Phone audio.
Look online and have tried the ICS 4.0.4 (Rogers leak) and same issue with Bluetooth.
The only way my devices works perfectly is when I only pair with one device at a time. There is something happening when you pair more than one device, even if not both device are turned on or in range.
Anybody got the same issue or a fix to that?
Thank you and sorry if my post is a little long... but that issue is the only thing that make me not enjoy my phone.

[Q] CleanROM Bluetooth Issue

First of all, CleanROM is a wonderful ROM. I have installed it on my ATT Note 2. :good:
However I have one slight problem if you guys can help me figure it out.
My bluetooth connects perfectly to my car stereo (A Brand New Pioneer made in July 2012). I can make phone calls perfectly, but I cannot play media via bluetooth. Meaning, when I try to play music it does not send a signal to the radio.
I made some troubleshooting steps to no avail:
1. The bluetooth Media option is checked under the bluetooth settings.
2. The car stereo works perfectly with my rooted Galaxy S II with Stock ROM 2.3.5 (phone + media)
3. My Note 2 fails to send media signal to my GF's new car Stereo (2013 model). Hence this is NOT an issue of an outdated bluetooth receiver. Again here, the same issue: it connects when making phone calls, but no media playing.
4. I even unpaired all other devices from the stereo to no avail.
I am starting to think it is an issue with the ROM..Is there an app I can download or some patch to fix this, or should I try a different ROM.
It took me 2 days to finally set up everything on my phone and I would hate to have to erase all and start all over.
Thanks a lot in advance for your help.

privatewarrior1 said:
First of all, CleanROM is a wonderful ROM. I have installed it on my ATT Note 2. :good:
However I have one slight problem if you guys can help me figure it out.
My bluetooth connects perfectly to my car stereo (A Brand New Pioneer made in July 2012). I can make phone calls perfectly, but I cannot play media via bluetooth. Meaning, when I try to play music it does not send a signal to the radio.
I made some troubleshooting steps to no avail:
1. The bluetooth Media option is checked under the bluetooth settings.
2. The car stereo works perfectly with my rooted Galaxy S II with Stock ROM 2.3.5 (phone + media)
3. My Note 2 fails to send media signal to my GF's new car Stereo (2013 model). Hence this is NOT an issue of an outdated bluetooth receiver. Again here, the same issue: it connects when making phone calls, but no media playing.
4. I even unpaired all other devices from the stereo to no avail.
I am starting to think it is an issue with the ROM..Is there an app I can download or some patch to fix this, or should I try a different ROM.
It took me 2 days to finally set up everything on my phone and I would hate to have to erase all and start all over.
Thanks a lot in advance for your help.
Click to expand...
Click to collapse
I'm having the same problem different radio.

What custom rom bypass car audio bt issues?

Hi all,
like many 5T users I bothered problems with bluetooth connection in car audio system (spotify and calling). I've tried everything what I found on forums (downgrading software, clearing cache, energy settings etc.) but with no success. Finally I red somewhere that problem is OOS itself and custom rom should do the work. My question is: what custom rom should I use (on my earlier phone (samsung note 3) I used Ressurection ones)? Did someone tried this way and could tell about results?

Im on cnp and everything seems fine when I connect to my truck.

Thank You for fast reply, but did You experience bt problems on car audio system earlier (with official oos)? And what is cnp?

Pan_Hrabia said:
Thank You for fast reply, but did You experience bt problems on car audio system earlier (with official oos)? And what is cnp?
Click to expand...
Click to collapse
Codename Phoenix rom

What problems? I've been running oos all long and no issues with my car bt.

Problems with bt connectivity (spotify does not work - stuttering and disconnects and calling also). On official forum it's a popular problem and has many potentially solution. None works for me so far.

Many problems with my car BT (mercedes w211) with TugaPower ROM (now on v26.0)
After the initial connection car reports no (mobile) signal but I can manually dial. Automatic / voice dialing does not work.
Almost on every call BT disconnects and I have to redial. I make the call and few seconds into it, it drops call back to the phone with the car radio reporting "waiting for BT connection"
I tried to look into the logcat but I see no related error(s).
I'm also looking for a good rom that works with my car BT.