Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...
TrueTenacity said:
Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...
Click to expand...
Click to collapse
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2
jmelhus said:
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2
Click to expand...
Click to collapse
THANK YOU so much! That looks like it'll do the trick, now my only problem is how the eff do I install it? I've tried to copy it to the root of the mem card but it looks like the recovery thing on my phone is toast... even though it's got stock firmware on it...
Will it be easier to root the phone?
Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?
TrueTenacity said:
Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?
Click to expand...
Click to collapse
Which bluetooth fix is implemented in leedroid? I would rather recommend you a cyanogenmod 6.1 ROM, or a ROM that's built on CM. For me this fix implemented there has worked. FYI, CM are AOSP and without sense.
Sent from my HTC Desire using XDA App
The fix is "[MOD][21-July] Fix Bluetooth CarKit disconnection" and apparently fixes the issue...
Hmm, I kinda like the sense interface so would be sad to see it go...
My Desire also has a bluetooth problem in connecting with my car. Not the disconnections, but phonebook/callist access fails. Installing an AOSP Rom (or MIUI) fixes the problem, but I do like sense too.
I've concluded the sense-bluetooth stack is the culprit, however I don't have the knowledge to change the stack. Thus, I'll wait until somebody has fixed it or HTC updates the stack or until I'll buy a new phone
I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...
TrueTenacity said:
I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...
Click to expand...
Click to collapse
Hi, as i am having the same issue and dont really want to use a Cyanogen rom , before i do what vehicle did you get it to work with.
cheers
It was with a Pioneer DEH-P710BT head unit with built-in bluetooth...
The strange thing is that it worked absolutely perfectly for MONTHS and now all of a sudden is giving problems...
It is however, definitely the phone giving the problem because the head unit pairs perfectly with any other phone, and when using the cyanogen mod rom, the desire works perfectly with it.
I am using NexusMod ICS Zero - [4-19-12] Modified for T989 - 2nd Release
I try to flash with SuperWipe, without superwipe, Darkside Superwipe, M&S Kernel clenser, with format everything, with clear everything.
Don't know what else I should try.
how come when I come back to my restore (which is easydoes ICS ROM) the bluetooth works fine (I have to re-pair in my car after restore, because I clear the bluetooth system in my car evertime I pair the new rom)?
For me bluetooth didn't work for any of the new UCLD2 ROMS.
The bluetooth worked on the earlier ICS leaks.
Here is the LogCat for the crash
LogCat Link
Thanks,
here is the logcat for the fresh install and fresh test with the car bluetooth.
Can someone tell me what direction I should look at?
just flash your stock rom/ or just radio
there is no ICS Stock Rom available for flashing.
and I did flash the LB7 radio
I tried Gingerbread stock works fine....
then install NexusMod and same issue.
UCLD2 broke bluetooth for me also (Skyrocket). Works fine on the first ICS leak though (UCLC something).
It pairs to my JVC car stereo.
But buzzes/crashes when trying to stream.
Bluetooth will turn on/off over and over.
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Eddie
What is the version of your cmw?
I am on 5.0.2.7
Not cmw touch. Dunno maybe its working with cmw touch only.
Sent from my SAMSUNG-SGH-T989
I read it on skyrocket forum the Dev said on nexusmod thread that you have to be on cmw touch.
I update my cmw to touch and then reinstall the ROM and that didn't help either.
That's weird. Have no clue why Bluetooth is not working...
Anyways back to the first leak for now...
Sent from my SAMSUNG-SGH-T989
As I stated in the NexusMOD thread, bluetooth integration to my car is broken as well. Haven't tried v3.3 yet nor have I tried the make nandroid -restore from nandroid trick mentioned in the T989 NexusMOD thread... Am still hopeful that a new leak will come out with a different BT stack which fixes this
-greenboy- said:
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Click to expand...
Click to collapse
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
wave_sailor said:
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
Click to expand...
Click to collapse
Thanks for the feedback.
I re-install the ROM with 3.8 update and tried your method but that still not stop crashing the BT and transferred the call to the handset and disconnect from the car BT.
I guess I have to wait for the new leak with the hope that it will not have this issue.
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.
It used to work perfectly for me in the car (the only time I use Bluetooth) to use the hands-free stuff with IceColdSandwich 8.8.
I've tried Jellybean 4.2.1 by Randomblame and CodefireX but it won't pair.
In both cases when I power-up the car it tries to connect to the phone, and each time the phone pets out a beep and asks for the pairing code. It then will not pair.
Any suggestions? I'd really like to get the hands-free stuff working again.
Try the latest codefireX SR6 version. Many users have reported perfectly working bluetooth since 2-3 versions ago.
Sent from my Desire HD using xda premium
First:sorry for my bad English
JellyTime 4.2 project, last codfirex sr6, aokp Jbean, unofficial cm10.1, have a fully working bluethoot....
I tried CodefireX SR6 but still no good sorry.
I prefer Randomblame's Jellytime as well, if possible.
*bump*
Anyone please?
Receiveing files by bluetooth on the phone doesn't work for me either.
using CodefireX SR8 now (HTC desire HD)
Just a FWIW if anyone else has the same problem and finds this thread with a search - I have now fixed the problem by going to Jellytime R6.1 but I think the real solution was to flush the cache partition and Dalvik cache.
Bluetooth works just fine now.
I was the kind of guy who want to try some of the new version for this phone...
One issue I saw on each version except the original from bell is ... the bluetooth is not always working propely... not sure if @tdm can see the difference between v20f and cm bluetooth but since i'm back with this one i don't have to fight to have it connected to my car radio!
Anyone else having issue like mine??
Sent from my LG-P930 using xda app-developers app
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
handofstand said:
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
Click to expand...
Click to collapse
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Click to expand...
Click to collapse
I should try that version.
HoNo!'s almost-stock V20F and Sphinx 4.1 are the ones I found to have a reliable BT connection to FORD Sync, automatic connection. Everything else I tried I have to manually connect it and sometimes I have to do it 3-4 times to get connected with the exception of Carbon ROM which is pretty much 1 shot and it would be connected. I wouldn't even care for BT if it is not for the cellphone use bylaw in our town.