Develop Bugs

[Q] Nebula ROM - Bluetooth

I upgraded from 1.0.6 to 1.0.7 and found that my bluetooth was no longer syncing with the car. I Odined back to DI18 and found that bluetooth was fine..I deleted the pairing from the car and the phone...installed DK28 and reinstalled Nebula 1.0.7 and still have the same problem. I am not sure why the bluetooth thing stopped working. The car syncs with the rest of the bluetooth enabled devices I have.... Nebula 1.0.6 was working fine...

I don't know anything about nebula rom. The.best thing you can do is post this on The roms thread and people familiar with the rom could help you. Sorry I couldn't help you anymore.
Sent from my Evo Killer!!!

I had a similiar problem. My bluetooth devices would show up as a mac address instead of the model name and would not connect. I couldn't find an answer for this and odin'd back to DK28 and put ACS signed ROM on and Bluetooth is fine so not sure if it was one of the files removed from Samsung or Sprint in 1.0.7 but decided not to try it until someone else has the same problem. But yours sounds a little different then my problem. I read somewhere that your Bluetooth device might need a hard reset since you are only having trouble with one. Find out how to that for that device. Each is different.

Thanks for the help guys....i was not able to post in the dev section earlier but was able to now. Posted it there.
Sent from my SPH-D700 using XDA App

[Q] 2/22/11...bluetooth not work after installed eb13?

i installed eb13 froyo and rooted my phone with cwm3.0.0.5 , then flashed viper rom trinity 2.0 with the eb13 genocide 1.2 ghz..everything seems to be very good and fast, but so far i have noticed that the blue tooth is not connecting. does anyone have any answers to why bluetooth is not connecting?

so i toggled around with my settings and now my bluetooth is working allowing me to answer phone calls and talk on the phone but the only thing that my bluetooth doesnt do is allow me to give voice commands when i tap on the button on my blue tooth!!! any advice anyone?

How did you get the headset to take calls?

Bluetooth Issues - Summary of Testing Results
This is a problem that goes away if I simply go back to a DK28 based ROM (which I have no plans of doing), but appears with any flavor of the EB13 update available.
On a day when I didn't have a lot to do, I decided to do some testing to see if I could find the magic combination of EB13 loading (upgrade.apk, ODIN .tar/.pit load, Samsung SWUpgrade and the DEODEXed [stock-ish] ROMS available) to get my bluetooth working like it does on DK28. I have upgraded to EB13 stock, EB13 deodex, deodex w/EXT4 (no member ROMS yet) along with stock/Genocide/Daemon's kernels ... essentially every mix of install, ROM and Kernel available. Add to that, I also cleared data on the OPP application --- I tried to cover every base I could. That being said, I have narrowed down my list of issues with bluetooth on EB13 to:
Paired devices are not saved. I have a Jawbone ICON and I have to add it everytime my phone is rebooted.
(Only add once on DK28)
Unable to Pair and Connect on first attempt. It always takes at least 2 and most of the time 3 presses of Pair and Connect to get the Jawbone paired and connected.
(Paired and connected on first attempt on DK28)
When my Jawbone pairs up, if you watch the notification bar closely, my wifi will also do a quick off/on right after the notification shows "Paired" on the Jawbone. Before you ask - yes, I ran tests with the various radio's on and off just to see if that was the cause. Nope.
(Never saw this on DK28, but then again was not watching for it either)
Like others have said, I can voice dial using the Voice Dialer application on the phone, but I cannot voice dial by pressing and holding the voice dial activation button on the Jawbone (the start/stop/quick disconnect happens on the application).
(Press button, state name, call on DK28)
It did not matter what combination of the above I used, the result was always the above. I'll gladly assist in troubleshooting this issue, so if anyone out there knows what to look for in the logfiles, I'll gladly run a pair/connect sequence and capture the adb logcat output for review.
Thanks in advance ... None of these are showstoppers, in fact I love EB13 and also appreciate all the hard work done by the devs and contributors in these forums (plus I guess I need 10 posts now to add anything relevant to a dev thread ).
- Dan

If you use Titanium Backup and have backups from before the update, please read this:
I was having the same problem with bluetooth on EB13. Just before ODINing back to DI18, I decided to try this:
1. In Titanium Backup>Backup/Restore, find these three items backed up from a previous kernel: Bluetooth Pairings, BluetoothTest 1.0, BrcmBluetoothServices 1.0. --Touch and restore each one of these.
2. Go to Home>Menu>Settings>Wireless and Network>Bluetooth Settings (turn on bluetooth): If your device is listed as paired, unpair it. Pair it again as a new device.
This worked for me, except voice-dial through my Jawbone is force-closing (but I honestly don't know if it ever worked right anyway). At the very least, it is now pairing and connecting fine and staying connected for calls and music.
P.S.
I suppose if you don't already have a backup of these items you could ODIN back, get Titanium Backup, backup all apps and system data, then update to EB13 all over again and restore the bluetooth data.

If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.

I've been having problems with Bluetooth on MidnightROM 4.2. The Bluetooth is extremely flaky -- sometimes pairs, sometimes doesn't -- doesn't stayed paired.
I haven't struggled with it too much because I never used Bluetooth much, but I would like to know if there's a fix.

jbadboy2007 said:
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
Click to expand...
Click to collapse
ACS has these same issues. It is a EB issue and I find I am having the same problems.

Bluetooth and 2.3.4

It seems like since I have been using gingerbread 2.3.4 I am having some major bluetooth issues. My devices seem to disconnect at random both my headset and car system. I will check my phone setting in bluetooth and it is not showing any devices even paired, or even there at all. I have to reboot the phone and then they may or may not show up. Another issue is contacts taking forever to show up in my car pioneer system. They show up sometimes and sometimes they don't. When they don't I look in the settings and sure enough even though my phone is connected to the car there are no devices showing in the settings. Another thing that happens is even though I have gotten out of the car and shut it off, my phone will stay connected to the pioneer system. It does this on our truck's system as well so it is not the pioneer. The truck is a Ford f150 and uses sync. When I was on 2.2 SF 1.2 I had zero BT problems, in fact I am back on it and my contacts show up on my car instantly now.
My question is this, is this a know problem, is anyone else having BT issues. I searched but could find nothing on this.
Thanks.

I have had zero bluetooth issues on the Gingerbread leaks but only use a cheap Samsung earpiece, no fancy car docks or anything. Have you tried different leaks and installed the EG22 modem?

I have a Moto Finiti Bluetooth and another cheaper one. They have seemed to be working perfect for me
Sent from my SPH-D700 using XDA Premium App

This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?

redram38 said:
This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?
Click to expand...
Click to collapse
Wow, good question. I believe it was Go Green and Scrambled Eggs
Sent from my SPH-D700 using XDA Premium App

redram38 said:
This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?
Click to expand...
Click to collapse
If you Odin'd that in then you probably also have the EG22 modem as your baseband. I am on Bonsai B14 EG22 based ROM.
Yes try it from scratch and check it each step of the way to find out where the issues develop.

I have the same problem periodically with my Audi. I'm on SRF 1.2 Genocide kernel, EC05 modem.

elevans said:
I have the same problem periodically with my Audi. I'm on SRF 1.2 Genocide kernel, EC05 modem.
Click to expand...
Click to collapse
Any ideas of what could be causing this problem or how to resolve it?

Since I went back to SF 1.2 I am not having near the issues I did. My contacts show up within seconds now.

[Q] [solved] Bluetooth ICS 4.0.4 (sandvold) VW RCD 510

Hello,
may me be helped here? I have a HTC Desire with ICS 4.0.4 of Sandvold.
In the car always I have to confirm the bluetoothpairing twice until it is coupled. I have a handfree-kit for Volkswagen with a RCD 510, in the simple version (supports handsfree profile). In my opinion, it is no problem with rSAP!
With Android vers. 2.3 the pairing was automatically...
Thanks in advance
BR
Sauerland
HTC Desire with [BETA 0.11][03.06] ICS for Desire[ALL HBOOTS][4.0.4]
VW Golf VI RCD 510

Hello,
next problem with Bluetooth.
I've tested to pair my ics desire with a galaxy s2, it doesn't work and pairing with a galaxy
s3 doesn't work also.
Does someone know a solution or a hint/tipp?
BR
Sauerland

I found nothing wrong with Bluetooth.
I can connect easily with my Car using Bluetooth and tried sending files to 4-5 different phones without any error.
its worth mentioning which Version of ROM you are using.
usually Full Wipe before flashing ROM Removes 99% Troubles

Hmm,
I've done a full wipe before.
But I'll do so again next weekend with version 0.13, hopefully that it works better.

So, I've done a full wipe and reinstall Version 0.13,
pairing is ok, but the telefone in my car rings but I can't speak/hear anything.
The phone goes always in "private mode". Change it to "hands-free", to "private mode" and return will not solve the problem. Eyerytime a call comes in the radio "rings", but the phone stays in "private mode".
The same problem after a full wipe and version 0.13.1 install

Ics 4.0.4 v.13.1 Bluetooth
Hello!
I've done a full wipe and install Version 0.13.1. After activating/disactivating bluetooth the systems gives me an error (com.android.phone). After pressing the ok button I have to reboot the phone, because there is an sim card error as well. After rebooting the phone runs normal, but everytime I use bluetooth I have the same problem again.
Before I had installed the ICS 4.0.4 v.12 and never occured an error like this. Anybody there with the same problem or the solution?
Thanks for help and greetings
Dami7

Hello,
i have also a problem with pairing.
My BT from the car does not find my hone at all. yes i made it vissible.
BT in the car works, can pair with other phones. BT on the phone works, can connect to my laptop.
But no connection to my car??
with android 2.x it worked??

R0yke said:
Hello,
My BT from the car does not find my hone at all.
....
But no connection to my car??
with android 2.x it worked??
Click to expand...
Click to collapse
Same for me.
My car does'nt find the phone, telefonbook can't sync, handsfree does'nt work, but I can answer the call without handsfree.
with Android 2.3.x no problem

Me too. Any help?

Had exactly same issue with 0.13.1: no audio through bluetooth headset or car handsfree + com.android.phone crashing when disabling bluetooth.
Downgrade to 0.12 seems to have fixed both problems for me.

Known issue reported in the development thread for 0.13.1.
Sandvold says he should have a new build (0.14) soon, no news on whether that fixes it or not however.

Yes, the new release will fix something:
Sandvold:
....and start working tomprrow.
Usb tether is fixed pluss adhoc. But its a bit unstable so wont release it and need to build a new one.
Click to expand...
Click to collapse
He says nothing about BT, but I'll hope it will fixed too

Hey, good news, the version 0.14 fixes the problem with audio through the headset/car speaker.
The last problem is phonebook sync with my car audio system, always the error message "phonebook sync incomplete" appears at the audio system display.
I'll hope sandvold fixes this issue too...

[solved] Bluetooth ICS 4.0.4 (sandvold) VW RCD 510
I've solved the phonebook-access with the Phone Book Access Protocol (PBAP)-Addon,
found here: http://forum.android-rsap.com/viewtopic.php?f=33&t=221
Now I can hear the audio through the speaker, and the RCD 510 always sync the phonebook with my HTC Desire ICS.
Tested with VW Golf VI, RCD510, "low-cost" original Handsfree-Kit from VW.
ICS Vers. 0.14 from Sandvold

Upgrading to .014 has also resolved this for me

Hi
Same phone same ics version 4.0.4, car audio is clarion fb-288 and for me I get asked to reenter the code every time. Also worked fine with 2.2.x and 2.3.x.

ludagad said:
Hi
Same phone same ics version 4.0.4, car audio is clarion fb-288 and for me I get asked to reenter the code every time. Also worked fine with 2.2.x and 2.3.x.
Click to expand...
Click to collapse
I had that too, did a factory reset on sandvolds rom, and reflashed the latest. Problem solved. But i moved on now. You should try nikez 4.2.1 rom, its about as far as sandvold was with 4.0.4. Also an evervolv rom. Its amazing how smooth it is, and latest release is quite stable too. I assume sandvold stopped devving, as he is vanished for several months now. So time to move on!
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!

pair to clarion fb-28* works again
PuffMaN said:
I had that too, did a factory reset on sandvolds rom, and reflashed the latest. Problem solved. But i moved on now. You should try nikez 4.2.1 rom, its about as far as sandvold was with 4.0.4. Also an evervolv rom. Its amazing how smooth it is, and latest release is quite stable too. I assume sandvold stopped devving, as he is vanished for several months now. So time to move on!
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!
Click to expand...
Click to collapse
I managed to fix the problem in the original from by replacing the Bluetooth.API with a download from Androidforums. There is a post there that has 3 versions attached. I used the 4.0.1 sz 407 KB. Works like a charm.
I hadn't checked for other ICS rooms since I got this one. I didn't know there was something else.... THANKS! Time to backup now

ludagad said:
I managed to fix the problem in the original from by replacing the Bluetooth.API with a download from Androidforums. There is a post there that has 3 versions attached. I used the 4.0.1 sz 407 KB. Works like a charm.
I hadn't checked for other ICS rooms since I got this one. I didn't know there was something else.... THANKS! Time to backup now
Click to expand...
Click to collapse
Nikez 4.2.1 is not an ICS rom, but the latest and greatest JB
ROM thread found here:
http://forum.xda-developers.com/showthread.php?t=1766550
Q and A found here:
http://forum.xda-developers.com/showthread.php?t=1944226
Almost all ROMs for desire are found here:
http://forum.xda-developers.com/showthread.php?t=809328
Take a look
Sent with my HTC Desire with Red Tapatalk because my XDA premium app is beeing a female dog!

After AT&T JB update, Bluetooth connection keeps dropping (paired with car)

Since I upgraded my AT&T Galaxy S3 with the official Jelly Bean update last week, my bluetooth pairing with my car has not worked.
At first, I was continuing to use the existing pairing which was set up and perfectly working in ICS. Whenever I made a call from my car ('09 BMW 3-series, bluetooth phone via built in nav system), there would be a loud pitch sound when the call was answered and then connection lost.
So I unpaired, and re-paired.
But now it does not work at all. Connection keeps dropping every few seconds. I have not even managed to get the data sync (transferring of contact data from phone to car) to complete.
This is beyond me. Jelly Bean is great, but it is not worth the price of not having properly functioning bluetooth.
Any suggestions? Anyone with similar issue? Is it possible to somehow roll back to ICS?

I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.

nsmith4 said:
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Thanks for your response.
I have not (yet) tried a factory reset, was sort of hoping to avoid the hassle of having to restore my data and apps. But I will eventually resort to it, if nothing else can fix it.
Good suggestion with regards to erasing from car memory. I am not sure if or how that can be done, but I will try and look through the settings to see if I can. (what I have done so far is just "remove" the device from the list of paired devices...

nsmith4 said:
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Pretty sure this is the actual cause of your problem.

HiKsFiles said:
Pretty sure this is the actual cause of your problem.
Click to expand...
Click to collapse
I went through all possible options in my car's nav system (xDrive) and I do not see any options to delete the car's memory.
So the only option as far as I know is to remove the device from the list of paired devices before pairing it again. And I tried that already...

Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.

Ok. So I resorted to restoring to factory settings.
With it clean, before restoring backup (made with Titanium), I went to my car and paired.
It worked - it synced the (very few, AT&T default) contacts, and no dropping (as far as I waited, a few minutes).
This was good news.
So I went back up and restored all app data, signed into Google account to sync all contacts etc.
Then back down in car and connected.
Problem is back It won't sync the contacts and continously drops and reconnects.
Well at least I have a reference point to go back to now and perhaps take one step at the time.
I was thinking next step is to restore to factory settings again, then ~only~ add google account to sync up contacts, then try. If that works, restore one app at a time to see if I can isolate the issue.
I will do this tomorrow.
mrhaley30705 said:
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Click to expand...
Click to collapse
I just did this. I am however too tired for the day and will check first thing in the morning, if this resolved it (as I am back in the problem state) - before resetting and starting all over (ref. my above mentioned thoughts of how to do a gradual restore)...
Thanks all for your input so far - I cannot tell you how much I appreciate it. This forum rocks so far.
/Lars

Progress this morning:
First of all, I tried as suggested clearing data for Bluetooth Share. Didn't fix the problem.
I know now that if I pair the phone and connect after factory reset, with the contacts list on the phone at default/almost empty (11 pre-defined AT&T numbers), it works.
So what I did this morning:
I factory reset the phone again. Then I added my Google account to sync up contacts list from my GMail account.
I ~only~ did this. No apps installed or restored.
Paired and connected. And I have the problem.
So this seem to somehow be caused by my contacts list after it has synced up with Google.
Any suggestions?
I am thinking that if I cannot get this resolved, I want to roll back to ICS. Having no functional bluetooth pairing with my car is not an acceptable tradeoff, no matter how great JB is. Is there a way to roll back? Can I get the official ICS ROM from AT&T, if needed?
But of course - this will be my final solution; I much prefer to get this resolved. I am open to any suggestions re. my contacts/google account.

You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app

Deoxlar said:
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your feedback.
Can I ask, if you know where this problem is perhaps discussed?
I looked in the developer forum, but must admit I am confused which thread/which ROM you are referring to. Are you talking about a modified stock ROM? I would greatly appreciate a link if it is...

Today's update:
At work we have a Galaxy S3 AT&T device (identical to my own) for testing purposes.
I just upgraded it to Jelly Bean today and then added my gmail account to it, paired to my car - and the same problem.
So at least that rules out an issue with my specific hardware/phone.
I also tried using a Galaxy Nexus (Verizon version) from work. Issue did NOT happen.
I then flashed my own phone with the stock Jelly Bean ROM downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1739426
Same issue happens
So my final solution (at least for now):
I flashed to the stock Ice Cream Sandwich ROM (downloaded from same place as listed above).
It works now.
Funny how one can be so happy with a downgrade, but I am
Thanks all for all your input.
I am still open to any suggestions (as I would love to be on Jelly Bean in the future), and I have an easy way to test possible solutions on my work test device...
Thanks again!
Lars

Hey, I am having Bluetooth problems as well. I have the sprint s3 stock jb. My blue tooth will not connect to my moga controller. Everything I have been reading points at it being a software issue on Samsung JB devices. Can anybody else confirm this?
Sent from my SPH-L710 using xda premium

Aren't the bluetooth "drivers" in the kernal? Perhaps using a different, or going back to a stock kernal.
I was having a similar issue with my phone not automatically connecting with my car. It would connect if I cycled BT off then on. All this on Tasks 4.1 rom & KT's kernal.
Flashed with the new 4.2 rom & kernal and it seems to be fixed.

Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.

crazililazn said:
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
Click to expand...
Click to collapse
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.

Bluetooth in car only has voice audio, no ability to control the phone
Ansextra said:
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Click to expand...
Click to collapse
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!

rohanverma said:
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
Click to expand...
Click to collapse
It's a know JB problem. No solution right now

Ironically, I had the same exact bluetooth problem the OP describes, but it happened with my stock ICS ROM. Made trying to call someone extremely frustrating since I have a stickshift!
The problem disappeared with my upgrade to the 4.1.1 stock ROM. I have also had no issues at all with any 4.1.2 JB custom ROM.
I believe it is a generalized issue with Android, because the problem I had with ICS was not reproducible when using a different bluetooth headset. Only my own would cause the problem. As soon as I realized that the problem no longer existed in 4.1, I began using my own headset again, and have done so without a single dropped call.

BWolf56 said:
It's a know JB problem. No solution right now
Click to expand...
Click to collapse
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!

rohanverma said:
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
Click to expand...
Click to collapse
Umm just to clarify, firmware goes like this (in order): Eclair, Froyo, GB, ICS, JB. So JB is the latest.
Here's a JB fix for BT: https://dl.dropbox.com/u/28275651/REVERT-MY-ALSA.zip
Flash it in recovery, clear cache and dalvik and hopefully it will work.