Is this happening to anyone else? I changed the device name and added a couple of paired devices. Everything works great for a while. Then if I turn Bluetooth off, the settings revert to stock. When I reboot the phone, my settings reappear. Strange.
With Bluetooth off, my paired devices don't appear in Bluetooth Settings. When I turn Bluetooth back on, they are there, just as I had paired them. I guess that's the way it's supposed to work? I never looked at the settings with Bluetooth off, only when it was on, with my former phone, so I don't know if it's different for the G2x or not.
I want to just chime in and say I cant even pair it with my car (2011 Subaru) I go through the setup and when it gets ready to ask for the PIN, the phone says 'Unable to pair, incorrect PIN.' without me even getting a chance to enter it...maybe the BT has some quirks? (My N1 BT was flawless, and this is by no means a deal killer for me)
smitty24 said:
I want to just chime in and say I cant even pair it with my car (2011 Subaru) I go through the setup and when it gets ready to ask for the PIN, the phone says 'Unable to pair, incorrect PIN.' without me even getting a chance to enter it...maybe the BT has some quirks? (My N1 BT was flawless, and this is by no means a deal killer for me)
Click to expand...
Click to collapse
Mine does the same thing (2011 Infiniti) but after the fail, a pop-up appears on the phone asking me for the PIN and then it pairs.
Resurrecting an old thread, my bluetooth settings all vanished yesterday, and turning off and on the bluetooth power did not restore them. It took a reboot. First time that's happened to me since I've had the phone (April 20).
This seems to be a pattern: things degrade over time. Either the GPS won't get a fix, or Wi-Fi Calling won't connect, or the browser gets very slow, or now the bluetooth settings vanish, and a reboot makes things work right again. This smells a lot like a heap management bug to me -- corruption, or fragmentation, or leak. I hope things are better after the Gingerbread/bug-fix update that's supposedly coming soon.
wmm said:
Resurrecting an old thread, my bluetooth settings all vanished yesterday, and turning off and on the bluetooth power did not restore them. It took a reboot. First time that's happened to me since I've had the phone (April 20).
This seems to be a pattern: things degrade over time. Either the GPS won't get a fix, or Wi-Fi Calling won't connect, or the browser gets very slow, or now the bluetooth settings vanish, and a reboot makes things work right again. This smells a lot like a heap management bug to me -- corruption, or fragmentation, or leak. I hope things are better after the Gingerbread/bug-fix update that's supposedly coming soon.
Click to expand...
Click to collapse
+1 Definitely some poor memory management in the stock kernel is to blame for this.
Try this for a bluetooth fix.. worth a shot...
http://forum.xda-developers.com/showthread.php?t=1117769
I am also having an odd BT issue. The phone pairs just fine with my 2009 Infiniti, most of the time. What i have found is that the phone decides to occassionally change its bluetooth address. After a reboot, it goes back to the original BT address that was originally paired with the car. This is kind of weird, no? Why would the phone change its BT addresss on its own?
I've seen this happen to me too. The address is part of firmware so its possible to change it just not sure why it is.
mikea3000 said:
I am also having an odd BT issue. The phone pairs just fine with my 2009 Infiniti, most of the time. What i have found is that the phone decides to occassionally change its bluetooth address. After a reboot, it goes back to the original BT address that was originally paired with the car. This is kind of weird, no? Why would the phone change its BT addresss on its own?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
did someone found the solution.
I am having same issue on lexus rx350, it will pair and then next day it will not find the g2x. you will have to reboot the phone, disable and enable Bluetooth to get it back or delete the profile and re enter/pair it again.
Fix(es) for Bluetooth dropping and re-pairing on Subaru and Gingerbread question
Had bluetooth settings vanish from my Subaru using lg g2x, but a bit of the history on this might add something to this discussion.
My G2x would not connect with the Subaru. Unlike another android phone the salesman had, no keyboard screen popped up so that the 1234 code could be entered. Called LG, TMobile, no help at all. LG rep was particularly hostile about this, not even seeming to understand/care about what I was explaining. Contacted Subaru corporate who suggested that the G2x had a preset 0000 code that could not be changed, so I needed to change the code on the Subaru bluetooth with another android phone, as described on the last few pages of the bluetooth section of the Subaru manual. So, paired another Android phone using 1234, unpaired that phone, and reset code to 0000 with that phone. G2x now paired rather easily.
Then, phone wouldn't even recognize Subaru bluetooth; 2 days later, spontaneously returned. Several weeks later, again vanished and wouldn't come back. Paired another phone, deleted my phone, repaired my phone, ok for now. The code remained 0000 throughout the process.
Next time this happens, I will delete my phone from the Subaru and go through the pairing process again to see what happens.
I will try the reboot the next time this returns. I appreciate this potential fix. Will alos try the repair program. My phone is not rooted.
In the meantime, can anyone tell me if a Gingerbread install will allow a keyboard to pop up so that different devices using 1234 or 0000 can be paired, and if the phone can handle pairings with 2 or more devices having different codes? Why doesn't a keyboard pop-up to allow this as it does on other Android phones?
Wilcone said:
Had bluetooth settings vanish from my Subaru using lg g2x, but a bit of the history on this might add something to this discussion.
My G2x would not connect with the Subaru. Unlike another android phone the salesman had, no keyboard screen popped up so that the 1234 code could be entered. Called LG, TMobile, no help at all. LG rep was particularly hostile about this, not even seeming to understand/care about what I was explaining. Contacted Subaru corporate who suggested that the G2x had a preset 0000 code that could not be changed, so I needed to change the code on the Subaru bluetooth with another android phone, as described on the last few pages of the bluetooth section of the Subaru manual. So, paired another Android phone using 1234, unpaired that phone, and reset code to 0000 with that phone. G2x now paired rather easily.
Then, phone wouldn't even recognize Subaru bluetooth; 2 days later, spontaneously returned. Several weeks later, again vanished and wouldn't come back. Paired another phone, deleted my phone, repaired my phone, ok for now. The code remained 0000 throughout the process.
Next time this happens, I will delete my phone from the Subaru and go through the pairing process again to see what happens.
I will try the reboot the next time this returns. I appreciate this potential fix. Will alos try the repair program. My phone is not rooted.
In the meantime, can anyone tell me if a Gingerbread install will allow a keyboard to pop up so that different devices using 1234 or 0000 can be paired, and if the phone can handle pairings with 2 or more devices having different codes? Why doesn't a keyboard pop-up to allow this as it does on other Android phones?
Click to expand...
Click to collapse
The LG Gingerbread release did nothing to the bluetooth drivers that are in the Froyo release. Whatever you get on Froyo (including frequent disconnects) will remain in Gingerbread.
I do not have a Subaru, but with my Land Rover if I try to pair the G2x with the car by having the phone discover the car, I do not get a keyboard popup on the phone.
However, if I have the car discover the phone the car gives me the code to enter and the G2x will give me a popup screen on which to enter the code.
The above has been my experience with using either froyo roms or gb roms.
Reconnecting Subaru bluetooth
Previously described my problems and fix for Subaru bluetooth and G2x. Attempts to fix latest disconnect included hard reboot which did not work.
So, I deleted my phone and reconnected like it was a new phone.
I discovered that the keyboard for entry of the 0000 password I had previously changed my Subaru to now popped up for the first time and I entered 0000. I was told by a bluetooth "pro" that there are two distinct conditions 1) pairing the phone to the car and 2) pairing the car to the phone. When the phone pairs to the car, the android password keyboard pops up. When the car is paired to the phone, it doesn't and it apparently assumes the default passwords are the same; if they aren't, no pairing.
This seems correct to me because of the many reports/complaints I've read about the password keyboard not showing up and its sudden appearance on mine. I guess if you can get the sequence right for pairing the phone to the car (rather than pairing the car to the phone) the android password keyboard will pop up and a 1234 password could be successfully used for vehicles that seem unable to connect because of G2x's default 0000 password.
Useful info for some?
Related
I have the Kenwood DNX8120 and it works fine with my Fuze (did have disconnect issues but just updated the Kenwood firmware which should take care of that) but the SMS feature on the radio doesn't work. I know only certain phones are compatible with this feature but on the Kenwood compatibility list there are several HTC devices that work. In any case, does anyone know how to enable SMS over bluetooth on the Fuze?
Thanks
I have the Kenwood DNX8120 in my car and have had no luck getting the Fuze to work correctly. It constantly drops connection. I updated the Bluetooth firmware and that only seemed to make matters worse. It will pair with the Kenwood, but either won't make a phone call or will take up to 60 seconds (or not at all) for the Fuze to recognize I it the call button on the radio. SMS, sent and received call history also do not work.
Have you had similar issues?
I can not get sms working. The only other issue I have is that after a call, it drops the connection. If I get another incoming call, it will reconnect and the radio will ring and handle the call. But, if I want to place a call, I have to either select "set as hands free" of something similar, in the bluetooth settings on teh phone and it reconnects and I can dial. I just upgraded to elite rc3 and the problem is still there. I havn't messed with it enough yet to know if it dials ok without having to bring the phone out of standby yet. I too have updated the bluetooth drivers from Kenwood and that didn't help. I also tried the jetware handfree extension and didn't see any improvement.
I called HTC about this, and they told me it only "officially" supports a hand full of car units. Mostly in the Audi and BMW. They don't "officially" support anything from Kenwood so they were absolutely no help on this. I've also noticed this phone drops all connections except cell and data when it sleeps. Wifi, GPS and Bluetooh all seem to go to sleep with the phone. This seems to make bluetooth pretty useless if the connection drops every time the phone sleeps and needs to be manually reconnected.
I haven't seen it drop the bluetooth connection during sleep. I see that the Kenwood supports some HTC devices but not this one specifically. The other wierd thing is that the first time it pairs it shows the battery indicator but after the next connect it doesn't show it. It shows the battery icon but shows it empty. The jetware extension however does fix that. I will play some more with it and report here.
After resetting my phone to AT&T's original setup, I am experiencing the exact same functionality as you. It now sync's my call history and phone book. No voice dial support or SMS yet. (These have never worked with any of my phones) It will disconnect after a couple phone calls and I have to set as hands free to reconnect. Also, mine still looses the connection to the unit when it goes to sleep. I'm keeping it on a car charger for now and turning off any sleep function when charging. That at least keeps it connected until I make a call. It's almost still not worth using with having to reconnect hands free. Maybe if a hands free quick connect shortcut could be created?
This is all really ridiculous that a phone with this kind of tech can't auto pair and be ready for a call. My LG Chocolate had absolutely no problems with the Kenwood. As soon as the Kenwood finished booting the LG would auto connect and be ready for a call.
I thought I found a workaround at
http://forum.xda-developers.com/sho...ghlight=bluetooth+connection+drops+phone+call
But, once installed an trying to run BT Restart I get an error saying that I need .net compact framework (version 1 or 2) installed. Not sure what to do now, cant seem to find a cab for this.
I've used this package from another post on the forum. It has many useful apps including the latest version of .net compact framework.
http://www.tyguy.net/_xchg/PPC/@essentials.rar
Let me know how it turns out!
I will take a look but I have 3.5 already installed. I guess that app needs the older version. Not sure I want to mess with downgrading it.
Not Kenwood
Hey Guys,
I drive a Jag XK8 and it has the same issues you are mentioning with your Kenwood, but its an Alpine unit, it drops calls, and after the first call connects the second call rings on the stereo but you can only answer on the handset.
I also recently had a new Jag XF for a week. It had a full integration to the phone. It also only showed the battery status when the phone first connected then the battery showed empty. It would drop bluetooth connections constantly on some days (every 90secs) and then somedays it would keep the bluetooth connected without issue. Very unreliable.
The reason I bring this up, is just to let you know these issues are not limited to the Kenwood.
Dave
Just an FYI. I have found it easier to just go into setup in the Kenwood and reconnect the bluetooth from there when the phone disconnects. It's under Setup/Bluetooth/Set, then just click on the device and hit connect. It seems easier than fiddling with the phone while your driving.
Hello,
In my car I have the Parrot CK3000 evolution car kit installed.
I can pair it with my nexus without problems.
After pairing incoming and outgoing phone calls should be routed through the handset but that doesn't happen.
My wife's htc hero, after pairing with the same handset, easily allows to establish the connection beetwen the hero and the handset long pressing the "parrot 2.51C" item in bluetooth settings and clicking the "Connect" item.
Long pressing the same item on my nexus shows a popup menu where the only option available is unpair.
Did anybody manage to make this handset work with nexus one?
For your information my parrot car kit has software version 2.51C and restarting the phone, resetting parrot memory, unpairing and pairing again didn't make any difference.
Regards,
Francesco
have a look at:
http://www.parrot.com/forums/english/viewtopic.php?pid=25879#p25879
Although this is for a ck3100.
I have this kit too. I'm at work so I can't test the link you put up but I don't think it will work. The nexus actually pairs with the device, it just won't connect. and the 3100 has an lcd screen so it runs completely different software
I used Parrot CK3100 with HD2. Everything was good! The sync was working very good with tons of rom. I tried with Acer Liquid. It was good. But when I tried with Nexus One original rom and Cyanogen rom I had a big problem with number. I always store the mobile phone number the following form: +36XXXXXXXX. All other phone managed it perfectly but N1 not.
I can sync the number with Parrot but the number was the following format: 36X-XXX-XXXX
It is WRONG!! I can't call the number without "+" I tried with the latest Desire (A10) rom and everything is fine!!!! Like with HD2!!! But the pairing is horrible with the A10. So I use Desire rom now.
I'm talking about a CK3100 here, but I had a problem when I first tried to pair it yesterday, it said it paired successfully but it didn't connect at all, no matter how many times I tried. The solution procedure for me was (maybe some step are not necessary at all but that's how I got it to work)
1. Unpair and delete the reference to the Parrot unit from the phone
2. Turn off phone bluetooth
3. Turn off car bluetooth (keys off until the Parrot turns the screen off)
4. Turn on phone bluetooth and enable visibility
5. Turn on car bluetooth
6. Pair from the Nexus One to the Parrot, enter pin
7. A request to access the agenda apeared on the phone, accept and you're ready to go.
I don't think it matters but just in case, I'm on stock rom (update1) and rooted.
PS: It's a total pain in the ass to have to re-record all the Parrot voice tags whenever I change my phone...
I managed to connect my CK3000 with N1 using the procedure that danimar1 describes.
No luck in copying my contacts to the parrot :/
Did anybody have success with this task?
F.
I've experienced this on other carkits too - it'll pair, but audio never transfers. Obviously a bug in the N1. I hope they fix it soon
In my case routing phone calls between parrot Ck3000 evolution and nexus one works.
The thing that I'm not able to do is to transfer my contacts.
Francesco
the ck3000 doesnt support contact syncing i dont think. that is the one bummer about android phones and bluetooth, no voice tag support. with my bb, it could use the phones voice recognition to voice dial from the car kit
danimar1 said:
I'm talking about a CK3100 here, but I had a problem when I first tried to pair it yesterday, it said it paired successfully but it didn't connect at all, no matter how many times I tried. The solution procedure for me was (maybe some step are not necessary at all but that's how I got it to work)
1. Unpair and delete the reference to the Parrot unit from the phone
2. Turn off phone bluetooth
3. Turn off car bluetooth (keys off until the Parrot turns the screen off)
4. Turn on phone bluetooth and enable visibility
5. Turn on car bluetooth
6. Pair from the Nexus One to the Parrot, enter pin
7. A request to access the agenda apeared on the phone, accept and you're ready to go.
I don't think it matters but just in case, I'm on stock rom (update1) and rooted.
PS: It's a total pain in the ass to have to re-record all the Parrot voice tags whenever I change my phone...
Click to expand...
Click to collapse
when you unpaired, did you delet the phone from the parrot memory also?
doalittledanse said:
when you unpaired, did you delet the phone from the parrot memory also?
Click to expand...
Click to collapse
No I didn't, everything was done from the Nexus One. But if you have problems connecting maybe it would be a good idea to do so.
danimar1 said:
No I didn't, everything was done from the Nexus One. But if you have problems connecting maybe it would be a good idea to do so.
Click to expand...
Click to collapse
and what firmware is your ck3000 on? im assuming thats an issue for me because ive never updated mine and its still at 2.10 i think
I'm sorry I have a CK3100, but anyway I never updated it. I got it a little more than 2 years ago, so I don't think it would be a firmware version problem.
So I just ran into these problems today and I wanted to find out if anyone else is experiencing them.
#1 My Charge's bluetooth will not stay connected to my Kia Soul's built bluetooth for phone calls, it would connect for literally 3 mins then just disconnect, almost like the phone was transmitting a bluetooth signal to pair with.
#2 I was using a cord to plug in my phone to my radio's auxiliary plug to test the phone as a replacement to my Ipod. However, every time I turned the part plugged into the phone using the headphone plug, or moved the cord or the phone, the phone would stop playing music and sometimes randomly skip to the next song. This is no longer an issue, just me not pushing the cord in far enough.
Im running the custom ROM so I am going to try this with stock, but neither things seems like itd be a ROM issue to me.
1) Does it disconnect during calls? It should go to sleep after a while, but if receiving a call it should reconnect if bluetooth is still turned on on the phone. This is Bluetooth 2.1 + EDR power saving working correctly unless it happens DURING calls, but it should sleep when idle.
2) I have had similar issues with cables no fitting properly, high end cabls likfe griffin/monster/etc have given me less issues, also make sure if you're usinga case that it is seated fully, some cases will keep it from being seated, on a headset with controls it uses a third ring for the mic and controls, and poor fitment can cause a stereo cable to short out on the third pin causing those issues.
I don't use BT, so I'm not much help with #1. For #2 though, I have read from several different users that the WM8994 chip/codec that this phone uses + voodoo sound is one of the best sound audio devices available, and provides a much nicer sound than any iPhone/iPod can. Now if only I could get my kernel config fixed.
warriorprophet said:
1) Does it disconnect during calls? It should go to sleep after a while, but if receiving a call it should reconnect if bluetooth is still turned on on the phone. This is Bluetooth 2.1 + EDR power saving working correctly unless it happens DURING calls, but it should sleep when idle.
Click to expand...
Click to collapse
It does not do it during calls, however, it does not reconnect when a call comes in either, I have to reconnect manually.
If this is how its designed, its actually a HUGE pain in the butt, I am an advertising salesman for a newspaper so I spend half my week driving and part of the reason I bought the Kia was for the bluetooth.
ShotgunSam said:
It does not do it during calls, however, it does not reconnect when a call comes in either, I have to reconnect manually.
If this is how its designed, its actually a HUGE pain in the butt, I am an advertising salesman for a newspaper so I spend half my week driving and part of the reason I bought the Kia was for the bluetooth.
Click to expand...
Click to collapse
Check the ford sync thread for your bt issue
I actually was trying to find it earlier (I did not use search though) seemed it got buried somewhere, but I will look through it.
I have the same problem in my week old Kia Forte. From what I've read it's not the cars. It happens on several types of cars with several types of phones. It has to do with the down loading of the phone books. If you have a lot of contacts on your phone the BT messes up. I read that if you turn off your phone and then turn it back on it will reconnect and stay that way.
So far that DOES work. I do that almost every time I get in.
But that's the bad thing, you have to do that a lot. My suggestion is clean up your contacts. If you have old ones that you don't really use or call dump them.
ShotgunSam said:
I actually was trying to find it earlier (I did not use search though) seemed it got buried somewhere, but I will look through it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1092436
Hughes4123 said:
I have the same problem in my week old Kia Forte. From what I've read it's not the cars. It happens on several types of cars with several types of phones. It has to do with the down loading of the phone books. If you have a lot of contacts on your phone the BT messes up. I read that if you turn off your phone and then turn it back on it will reconnect and stay that way.
So far that DOES work. I do that almost every time I get in.
But that's the bad thing, you have to do that a lot. My suggestion is clean up your contacts. If you have old ones that you don't really use or call dump them.
Click to expand...
Click to collapse
I think I might have fixed my problem because I had my phone set to show contacts that did not have phone #s, just email addresses (I have a lot of those from work), anyways I had the hide those and it may have cleared up my problem, probably confused it trying to download contacts with no phone #
I searched but found nothing in relation exactly. So this is kindof weird, thats why I'm posting. I searched through google, LG forums, jawbone forums and t-mobile forums, nothing exactly in relation (especially dealing with multiple ROM's) or any type of fix to a related issue.
So, I have a jawbone 2 headset device. Stock before I did anything, it paired. Diddnt use it for a while their, and then stared flashing some ROM's. I mainly used cm7 based rom's and paired my headset just fine, very easily actually and fast. I'm having proximity sensor issues, so I had to revert back to a froyo build (EB right now) but the same goes for ultimate rom.
Every time I try and connect initially, i get a force close on the settings. (when jawbone is in pairing mode) Then its in the list of bt connections of course, and i try and re-connect it and it spits out: Their was a problem pairing with Jawbone because the PIN or Passkey is incorrect. Now I havnt been able to find out how to either change the key or the pass. The key is the default 0000, I have even reset the jawbone to when I turn it on, its in auto pair mode. I have done hard-reboots, battery out's almost everything I can think of
So I'm stuck, any information would be completely awesome, and I hope its not super easy... Well I do, but it will not credit my intelligence.
bmann_420 said:
Every time I try and connect initially, i get a force close on the settings. (when jawbone is in pairing mode) Then its in the list of bt connections of course, and i try and re-connect it and it spits out: Their was a problem pairing with Jawbone because the PIN or Passkey is incorrect. Now I havnt been able to find out how to either change the key or the pass. The key is the default 0000, I have even reset the jawbone to when I turn it on, its in auto pair mode. I have done hard-reboots, battery out's almost everything I can think of
So I'm stuck, any information would be completely awesome, and I hope its not super easy... Well I do, but it will not credit my intelligence.
Click to expand...
Click to collapse
There's no answer in this old thread but I am having the exact same issue. It's happening on 2 different phones with different ROMs (Bionix and Weapon). I had the issue before on Weapon 2.8 so I downgraded to 2.7 and it was working. I then when reset my headset to connect it to the other phone, and it's giving me the problem again. Has anyone solved this? I am using a Blu Ant Q2, is that a bad device for this phone? Thanks.
Pairing SGS3 to Jawbone
So frustrating. Hours spent on this. Have 2 Jawbone II s and neither will pair with Samsung Gal S3. Soooooo frustrating. No answers on web to date. Have tried reset of Jawbone. Tried holding TALK button. Tried pairing in every way. No success. Sgs3 does detect many things but not Jawbone. Please answer. [email protected]. Thankyou out loud!!!!!!
I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Reported questions go in q&a and there are threads on Bluetooth issues
Sent from my SGH-I727 using Tapatalk 2
Firedcylinder said:
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Click to expand...
Click to collapse
Yes I have unpaired the connection, restarted the phone and the car, and paired them again. But the problem persists.
Today I tried my wife's iphone 4 with the car the didn't see any problem. I am pretty sure there is something fishy with the phone.
lik88888 said:
I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Click to expand...
Click to collapse
Common problem:
http://forum.xda-developers.com/showthread.php?t=1630021
Also look in the last couple of pages here, there is some explanation for it.:
http://forum.xda-developers.com/showthread.php?t=1701189