Related
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"
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.
I just picked up a my new Note II yesterday, have done nothing to it except install the latest update. This thing is STOCK. My issue is with the Bluetooth connection in my car. I have a 2009 BMW with IDrive which has the Bluetooth integration built in to it. My HD-2, Sensation, GNexus, original Note all connect very nicely to the Bluetooth but my Note II is struggling. I paired it yesterday on the way home from the AT&T store and it worked fine. When prompted to allow the phone book during my initial pairing I checked the box "Don't ask me again" and clicked "Yes", same thing I've done on all my other phones. This morning however it would continue to drop out. It would connect for 15-20 seconds and I would see the little icon that tells me the phone is transferring the contacts then it would simply drop out. 15 -20 seconds later it would recycle and do the same thing again. When I was looking at the contact list on my car's screen it was showing AT&T address book which I do not use (it was just one contact, "something" AT&T) and in fact froze everything AT&T I could through the settings menu . I then deleted the phone from the car's menu and repaired it to the IDrive but this time I said no to allow the phone book. It was not dropping the connection but was constantly trying to obtain the contact data based on the icon on my car's screen. Then all of sudden I received an alert stating an "SOS Call System Failure", my car has a built in SOS function like Onstar....I deleted the phone again and the warning in my IDrive regarding the SOS failure went away.
I searched the BMW forums and found other people with this problem but these were from the '07-'08 time frames and that fix was software to the car. The software in my car is updated and so is the B/T profiles I also found a thread here regarding a similar issue but there was no resolution. Has anyone else had this experience with the Note II? I know enough to get myself in trouble but not enough to figure this out. Is it possible the Bluetooth in the phone only wants to transmit the AT&T address book vs. the Google contacts?? I guess it could be the software in the car but my other Note, whether running stock or CM 9/10 ran flawlessly with regards to the Bluetooth.
Weird, yesterday it's fine and today not so much. Did the last software update have anything in it that affected the B/T?
Any insight would be much appreciated, thanks.
UPDATE-appears my car cannot handle a Bluetooth profile of 4.0. All my previous phones were no higher than 3.0. Hoping BMW will offer a software update at some point but in the mean time if I go with a custom ROM will they probably keep the Bluetooth profile the same as stock or is that something they change??
There are various threads on this forum concerning bluetooth connectivity to the GN 10.1 2014. Most notably, keyboards that keep disconnecting.
I ran into this problem with my Logitech K810 keyboard, which works perfectly on my PC, as well as my Ipad 2 and my Galaxy S4. Three different units, three different operating systems, and with flawless performance.
Then I buy the pinnacle of Tablet technology; a spanking new Galaxy Note, and realize that the keyboard disconnects every three to five seconds.
This is something like buying a shining new bike, coming home full of expectations, and unpack it. Only to discover that the wheels are stuck. They won't turn. It would have been hilarious, if the tablet wasn't so bloody expensive.
I tried various "keep bluetooth alive" and "change to another screen keyboard" apps, to no avail. Then I read a thread from someone who could make the keyboard work if they played music to another unit via bluetooth: I tried this, and voila! As long as I keep my phone paired and connected to the note, the keyboard works perfectly.
This could give a hint as to the nature of the problem; could it be that the keyboard, unlike the Galaxy S4, doen't actively work to keep the bluetooth radio active when you are not typing, and that what ppl assume to be Samsung's new implementation of the bluetooth standard in the GN 10.1 2014 doesn't take such devices into account?
If that is the case, the problem should not be related to hardware issues with the bluetooth antenna, like someone suggested, but is more likely software-related, and hence, a bugfix shouldn't be impossible.
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Finurliig said:
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Click to expand...
Click to collapse
It's a h/w problem. There are plenty of N10.1-14 owners that aren't having any BT issues including with the K810 which comes up frequently. I have a BT mouse and keyboard connected for hours at a time without any disconnects. I leave BT on continually on my N10.1-14 and as soon as the mouse or keyboard are turned on they connect immediately. There's a lot of discussion in the BT thread in the general section discussing possible causes on devices having problems. Exchange it or send it in for warranty repair.
BarryH_GEG said:
It's a h/w problem. There are plenty of N10.1-14 owners that aren't having any BT issues including with the K810 which comes up frequently. I have a BT mouse and keyboard connected for hours at a time without any disconnects. I leave BT on continually on my N10.1-14 and as soon as the mouse or keyboard are turned on they connect immediately. There's a lot of discussion in the BT thread in the general section discussing possible causes on devices having problems. Exchange it or send it in for warranty repair.
Click to expand...
Click to collapse
Thanks for advice, but for an exchange of the device to be meaningful, we will need some confirmation that Samsung has identified the problem and corrected it?
Finurliig said:
Thanks for advice, but for an exchange of the device to be meaningful, we will need some confirmation that Samsung has identified the problem and corrected it? Besides, they refused to do just that when I spoke to their support? Nevertheless: I will mail them again about this. Thanks!
Click to expand...
Click to collapse
If you bought from Samsung, I'm not surprised they told you they would not exchange it. Samsung told me they don't warrant that their product will work with a third-party product. They also said there were no Samsung keyboards at this time that were compatible with this tablet. Fortunately I got mine from a retailer that was willing to exchange. Unfortunately the second unit I got about two weeks ago also has the problem.
Your best bet might be to send it to Samsung rather than play "exchange roulette." Here's what to tell Samsung customer support...
"Hi Mary, I spoke to someone earlier about a BT problem I was having. The BT peripherals I connect work fine initially but can't maintain a connection; meaning they drop the connection and either I have to reconnect them manually or sometimes they'll reconnect themselves only to drop out again. The person I first spoke to was pretty sure it was the devices I was connecting and not my tablet.
Here's what I did. I completely reformatted my tablet to the way it came out of the box. I didn't even allow any of my apps to be loaded on it after I reset it. So it was a clean untouched stock as it left the factory Samsung configuration. The same problems of random disconnection occurred. I went to Best Buy and they were really nice. They allowed me to connect all the BT peripherals I was having problems with to their three floor models. They all worked fine and kept the BT connection active. So clearly, there's something wrong with my individual tablet.
I have a couple of friends with this tablet and while the majority of their devices work fine some are having the same issue I am. There's obviously something wrong with a subset of these tablets for individual examples to perform differently with the exact same BT peripherals."
If you still meet resistance...
"I'm sorry you won't help me get my problem solved. Do you think a supervisor might be able to help me or should I just contact the BBB and my local attorney general's office as you're refusing warranty work I'm entitled to in spite of the steps I've taken to isolate a problem and demonstrate to you that there's an issue with my specific tablet. Also, can you please give me your name again? I didn't write it down when you came on the call."
Thanks BarryH.
engaged ricultsc
Good Evening.
There are new on this issue?
I have k810 keyboard too, and in the beginning the keyboard worked normally, but lately, I have more and more disconnections.
Before, it was enough for me to restart the tablet, and the keyboard walked fine.
But now, I have constantly disconnections, every 5 seconds.
It becomes unusable
I tried to flash roms of over counties, I tried CleanRom, but the problem stays.
I'm worried, because my Knox is on 1, and I just read that Samsung voids the warranty, regardless of the problem...
Do you found other solutions since?
(.. and sorry for my bad english..)
.....
Finurliig said:
There are various threads on this forum concerning bluetooth connectivity to the GN 10.1 2014. Most notably, keyboards that keep disconnecting.
I ran into this problem with my Logitech K810 keyboard, which works perfectly on my PC, as well as my Ipad 2 and my Galaxy S4. Three different units, three different operating systems, and with flawless performance.
Then I buy the pinnacle of Tablet technology; a spanking new Galaxy Note, and realize that the keyboard disconnects every three to five seconds.
This is something like buying a shining new bike, coming home full of expectations, and unpack it. Only to discover that the wheels are stuck. They won't turn. When you call the manufacturer support; which I did in relation to the Note, they politely inform you that they have never guaranteed theat the wheels on the bike would turn. They have only said that the bike HAS wheels,..... not that they can actually be used for anything..... so they refuse to take responsibility, and refuse to give you a refund.
This is, in point of fact, the answer I got from Samsung: they market the unit as having bluetooth functionality, but won't take responsibility if it doesn't work, and the user is stuck with a pieece of equipment that can't be used for the intended purpose. It would have been hilarious, if the tablet wasn't so bloody expensive.
So much for Samsungs costumer support. Now to my own investigation into this problem:
I tried various "keep bluetooth alive" and "change to another screen keyboard" apps, to no avail. Then I read a thread from someone who could make the keyboard work if they played music to another unit via bluetooth: I tried this, and voila! As long as I keep my phone paired and connected to the note, the keyboard works perfectly.
This could give a hint as to the nature of the problem; could it be that the keyboard, unlike the Galaxy S4, doen't actively work to keep the bluetooth radio active when you are not typing, and that what ppl assume to be Samsung's new implementation of the bluetooth standard in the GN 10.1 2014 doesn't take such devices into account?
If that is the case, the problem should not be related to hardware issues with the bluetooth antenna, like someone suggested, but is more likely software-related, and hence, a bugfix shouldn't be impossible.
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Click to expand...
Click to collapse
I have had the same problem with a bluetooth keyboard and mouse not working correctly, I found if I turn off the wifi radio on p600 I have up to 3 co current bluetooth connection going at he same time. when the wifi is on and active the bluetooth is dropping off think it has to do with wifi 4.0 radio in the tablet or the placements of the attennas in the tablet.
What I do is connect a bluetooth device to play music continuesly, so that the connection doesn't drop. Then the BT keyboard and BT mouse will stay connected. Keyboard and mouse disconnect when you stop typing. The music BT device keep the signal alive, and it never drops. You can try this if you want and check if it works for you.
Sent from my GT-N7100 using Tapatalk
I have not experienced this issue and I use a Bluetooth keyboard and mouse abort 20 hours per week.
Via my Note 3
Bit of an old question now, but I'm getting this on my K810 too Did anyone sort it out?
Theres an app called bluetooth keep alive, it works well
Cheers moabizza, I just tried it and sadly it didn't work Oh well, looks like it's going to have to go back for repair.
Don't send your device in for repair- there's nothing wrong with it. I use a BT keyboard and a BT mouse all the time with this device and they work quite well- the issue is pretty obviously the Logitech K810, not the Note 10.1 .
Hello ...
I currently have an HTC One M8 running the TeamVenom rom 4.1.0. When I pair my phone to my car's Bluetooth handsfree, it works as expected. But when I disconnect or turn off the engine, reconnect or restart the car, the pairing is lost. My phone will keep asking for the pair security code. When I enter it, I get an error saying that it's been declined (or something similar). The only way to fix it is to delete the pairing on the phone and the car, re-setup the pair and it works again. Before I Updated to 4.1.0, my phone would connect to the car automatically without issue. Also, when setting a new pair, I get a slew of message on my phone (50+), saying that a new Bluetooth device has been added. Most of the time, it's the MAC address of the car. The rest are MAC address I don't recognize.
Has anyone else had this problem or know how to fix it? Or know how to fix it? Re-adding it every time I get into the car is a huge pain in the arse.
Any help will be greatly appreciated.
See if you car stereo has a way to "re-initialize" or restore to defaults; then pair the phone again from scratch. I had a similar (although not identical) sounding problem with my 2012 Subaru Impreza (I understand their factory head units are made by Kenwood) where I would have to manually reconnect (it was paired, but would not automatically connect on it own) every time I got into the car and started it. Re-initializing the system, then pairing it fresh again solves this issue for me. I need to do this every time I flash a new ROM; on this phone and on my old One X EVITA.
Might not help your situation, but its worth a try.
I believe I remember seeing that option in the settings. I'll give that a try and report back. Thanks. =)
Hi redpoint73.
I was able to get my phone to pair permanently with my car. I wasn't able to locate the factory reset for the radio. I phone my local Honda dealer and they suggested to pair the phone/car via the phone instead of going through the car, which worked. I appreciate your help. Thanks.
Sent from my HTC One_M8 using XDA Free mobile app
I am having the exact same issue. i am on ARHD 34.6 ROM and everytime i am required to repair my bluetooth, it just doesn't reconnect automaticlaly after my engine dies.
I also have this issue with ViperROM.
This issue doesn't show up when i am on GPE ROM so there is nothing wrong with my hardware.
This has been bugging me for a long time as i need my BT audio while i am driving. I never had a problem before the Lolipop with Sense update.
I am driving a Honda City 2014 (Malaysia). Does this only happen to Honda Cars? i have asked people inside ARHD thread but not many reported this same issue.
RedDevils88 said:
I am driving a Honda City 2014 (Malaysia). Does this only happen to Honda Cars? i have asked people inside ARHD thread but not many reported this same issue.
Click to expand...
Click to collapse
I wouldn't assume that. There are lots of combinations of car stereos and phones that work a little differently from each other, with different hardware and software. The Bluetooth "standard" is not as uniform as you would hope. Therefore you end up with some combinations that simply don't play together well.
It partially may depend on who manufactures the head unit. Which is typically not the car company. For instance most Subaru stereo head units are made by Kenwood from what I've read. And the manufacturer may or may not be the same as the previous post depending on model, year, etc. And if you have a navigation head unit or some other "option" upgrade stereo, it might be a different make from the "base" stereo as well.
Did you try the fix mentioned in the post just above yours? Or the fix I suggested?
redpoint73 said:
I wouldn't assume that. There are lots of combinations of car stereos and phones that work a little differently from each other, with different hardware and software. The Bluetooth "standard" is not as uniform as you would hope. Therefore you end up with some combinations that simply don't play together well.
It partially may depend on who manufactures the head unit. Which is typically not the car company. For instance most Subaru stereo head units are made by Kenwood from what I've read. And the manufacturer may or may not be the same as the previous post depending on model, year, etc. And if you have a navigation head unit or some other "option" upgrade stereo, it might be a different make from the "base" stereo as well.
Did you try the fix mentioned in the post just above yours? Or the fix I suggested?
Click to expand...
Click to collapse
no luck. i couldn't find my car's bluetooth through my phone.