Hi all. I thought I would look for answer here in addition to the BMW forum.
I can pair and make calls with 2011 BMW.
However, when I accept permission to access phonebook, it attempts to download contacts unsuccessfully, then disconnects after 90 seconds and then reconnects, reattempts the download and the cycle repeats itself. If I deny access to the contacts, the connection remains solid. Unfortunately, I get an annoying connection prompt everytime I restart the car.
The first several times I did this, I permanently allowed access and then realized i had to unpair and start the process over without allowing phonebook access. The Bimmer was behaving so erratically that on a couple occasions when recycling the connection, it actually wiped all previously paired phones from the menu.
The connection is rock solid on Acura with both phonebook and message access.
Using mine on a 2014 BMW without issues here. Perhaps set visibility to always on. This help me with issues on an s4 and my car in the past.
Sent from my LG-D800 using Tapatalk
bri315317 said:
Using mine on a 2014 BMW without issues here. Perhaps set visibility to always on. This help me with issues on an s4 and my car in the past.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Sounded reasoanable but didn' work. I even updated to BMW's latest software. Well, at least I have a reasoanble chance of full Bluetooth if I segue into a 2014 at the end of my lease.
docslate said:
Sounded reasoanable but didn' work. I even updated to BMW's latest software. Well, at least I have a reasoanble chance of full Bluetooth if I segue into a 2014 at the end of my lease.
Click to expand...
Click to collapse
I didn't have any issues with the F30 rental I had for two weeks. Which infotainment system is in your BMW? Do you have the enhanced Bluetooth with BMW apps? The vehicle I was in had the standard iDrive without BMW apps or enhanced Bluetooth. I did notice it made separate entries in the phonebook for each contact's various numbers(cell, home, work, etc.), which was a bit annoying.
I've noticed in my Miata the Bluetooth connection will remain open, the word "phone" remains on the radio's screen and I can't change to the radio or any other input until I've powered the phone off and on.
With UConnect in the 2014 Grand Cherokee the vehicle would lose pairing with my phone every time I shut the vehicle. A UConnect software upgrade took car of this.
RJS5689 said:
I didn't have any issues with the F30 rental I had for two weeks. Which infotainment system is in your BMW? Do you have the enhanced Bluetooth with BMW apps? The vehicle I was in had the standard iDrive without BMW apps or enhanced Bluetooth. I did notice it made separate entries in the phonebook for each contact's various numbers(cell, home, work, etc.), which was a bit annoying.
I've noticed in my Miata the Bluetooth connection will remain open, the word "phone" remains on the radio's screen and I can't change to the radio or any other input until I've powered the phone off and on.
With UConnect in the 2014 Grand Cherokee the vehicle would lose pairing with my phone every time I shut the vehicle. A UConnect software upgrade took car of this.
Click to expand...
Click to collapse
I have the iDrive and updated to the latest Bluetooth software. Behavior is really strange. It asks me first if I want to download messages. If I check no, it usually asks a second time. If I check yes, it uploads messages to iDrive but still doesn't misbehave. If I check yes and also check the ALWAYS box, it usually starts to update the phonebook and that's when the predictable cycle starts of 90 seconds attempting to download the phonebook unsuccessfully, then disconnect and reconnect. And of course, it begins again when I restart the car. The only solution at that time is to unpair, pair again and deny phonebook access.
This is exactly the problem I have with my 2011 BMW 335d with idrive. It could be because the 4.0 Bluetooth on my LG G2 is doesn't want to play nice with the car's older software version. I have tried everything you mentioned and have not had any luck either. I have just learned to press the NO button 6 times every time I start the car, and manually enter names & numbers into the car's phone book that I use frequently.
Sent from my VS980 4G using XDA Premium 4 mobile app
electriclarryland said:
This is exactly the problem I have with my 2011 BMW 335d with idrive. It could be because the 4.0 Bluetooth on my LG G2 is doesn't want to play nice with the car's older software version. I have tried everything you mentioned and have not had any luck either. I have just learned to press the NO button 6 times every time I start the car, and manually enter names & numbers into the car's phone book that I use frequently.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same issue here. I however am having the issue on a 2014 Ram with the Uconnect 8.4a infotainment system. It only seems to be an issue with AOSP roms, I've installed several and they all have this issue. I didn't have it with the stock based roms.
fegar said:
Same issue here. I however am having the issue on a 2014 Ram with the Uconnect 8.4a infotainment system. It only seems to be an issue with AOSP roms, I've installed several and they all have this issue. I didn't have it with the stock based roms.
Click to expand...
Click to collapse
When I originally had the problems connecting I was on a stock-based ROM. I was going to try an AOSP ROM when Kat Kat came out, but unfortunately I bricked my LG G2 trying to update. I ended up getting an HTC One (M8) that is still unrooted but the phone pairs and my contacts sync. Although it refuses to recognize the phone for BT music streaming, I'm happy with it's performance so far.
Related
I have a Bluetooth bug and not just a compatibility issue with my car radio and the N4's BT 3.0/4.0 firmware. I confirm it is not an issue with my car's headunit (Porsche CDR30 w/sound package plus) since the problem is the same with my Note on CM10 but the Note works fine when flashed using pre-CM10 ROM. My symptom is that all pairing completes and contacts export to car and import to car address book. Calls can only be made using phone though. Car does use speakers and mic supporting call but that's it. Handset must be used as dial pad and accept/end/hold/swap calls. I have two other older phones with pre JB OS and younger BT versions working with car no problems.
If you have any N4 BT/car issues, please post.
Hi there.
Parrot mki 9200 here and N4 working good here for contact sync, calls and A2DP. Having trouble with parrot 2.11 update, but that's non phone specific.
Sent from my Nexus 4 using Tapatalk 2
Fully loaded 2013 Soul and mine is fine.
Sent from my Nexus 4 using xda premium
lpasq said:
I have a Bluetooth bug and not just a compatibility issue with my car radio and the N4's BT 3.0/4.0 firmware. I confirm it is not an issue with my car's headunit (Porsche CDR30 w/sound package plus) since the problem is the same with my Note on CM10 but the Note works fine when flashed using pre-CM10 ROM. My symptom is that all pairing completes and contacts export to car and import to car address book. Calls can only be made using phone though. Car does use speakers and mic supporting call but that's it. Handset must be used as dial pad and accept/end/hold/swap calls. I have two other older phones with pre JB OS and younger BT versions working with car no problems.
If you have any N4 BT/car issues, please post.
Click to expand...
Click to collapse
I have an audio-dropping issue with my 06 BMW 330i, factory head unit.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution as my Nexus S worked perfectly before the Nexus 4.
surferdude73 said:
I have an audio-dropping issue with my 06 BMW 330i, factory head unit.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution as my Nexus S worked perfectly before the Nexus 4.
Click to expand...
Click to collapse
Interesting that my issue is associated with my Nexus 4. The bug is on JB stock 4.2, 4.2.1 stock, Modaco custom Jr1 and Jr2, as well as the CM nightlies I am now flashing and using on my phone. I am getting service Saturday and asking Porsche dealer service tech to update the CDR30 firmware to eliminate head unit as problem.
Strangely enough, my N4 BT worked fine for the last two conversations yesterday, 10 and 25 minutes, respectively, and worked fine for a 25 minute convo this morning. I'm definitely waiting on it to drop again. Post an update once your dealer updates the SW and you have a chance to test.
surferdude73 said:
Strangely enough, my N4 BT worked fine for the last two conversations yesterday, 10 and 25 minutes, respectively, and worked fine for a 25 minute convo this morning. I'm definitely waiting on it to drop again. Post an update once your dealer updates the SW and you have a chance to test.
Click to expand...
Click to collapse
Will do
My issue is likely related to my car's head unit Bluetooth radio firmware. Service tech unable to get his ICS Droid to fully interface with car's hands free functions. So it seems........
lpasq said:
My issue is likely related to my car's head unit Bluetooth radio firmware. Service tech unable to get his ICS Droid to fully interface with car's hands free functions. So it seems........
Click to expand...
Click to collapse
OK, the plot thickens I guess. BMW firmware is definitely sensitive to Bluetooth profiles also, but functionality seems to be there so I'll hope for the best in regards to call stability. Good luck and keep us updated.
Sent from my Nexus 4 using xda app-developers app
This issue only seems to occur with my car, a 2013 WRX. I connected fine and typically every subsequent time I get in the car and start up as long as Bluetooth is on my phone will automatically connect. This was the case with my Gnex and the moto x. The G2 connects the first time fine but then the next time it won't connect, almost as if it's a different phone. The cars Bluetooth is pretty basic so it will only save one device so I end up having to delete it and start over.
The phone auto connects to other devices like my obd dongle and my outdoor speakers just not the car. And it worked in the car with other phones so I'm stumped. Anyone have any ideas?
Sent from my VS980 4G using xda app-developers app
Mine auto connects everytime n 2 different vehicles. Doubt its the phone...
Sent from my LG-D800 using XDA Premium HD app
same problem
I have the same problem with my 2011 WRX. G2 will connect fine the first time but every time after that i need to manually connect and that will only work every 3rd time.Very annoying.
zac413 said:
This issue only seems to occur with my car, a 2013 WRX. I connected fine and typically every subsequent time I get in the car and start up as long as Bluetooth is on my phone will automatically connect. This was the case with my Gnex and the moto x. The G2 connects the first time fine but then the next time it won't connect, almost as if it's a different phone. The cars Bluetooth is pretty basic so it will only save one device so I end up having to delete it and start over.
The phone auto connects to other devices like my obd dongle and my outdoor speakers just not the car. And it worked in the car with other phones so I'm stumped. Anyone have any ideas?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Have you tried letting it go for a while? I noticed its very slow to reconnect in my car (Infiniti), but it does eventually reconnect.
I havent tested it yet, but I noticed if the screen is on during reconnect, I get a message box saying the car is accessing the phonebook....Im wondering if it pulling the phonebook every time is slowing down the reconnection process.
Found a Solution
Found a solution, want to thank 2011_ST over at forums.androidcentral.com for pointing me in the right direction. The WRX head unit is very weird. The paired devices it shows you when you use the buttons to see all devices is different from the paired devices it tells you when you use the voice navigation to pair and delete devices. I had to use the voice navigation to delete my last 2 phones, than pair the LG G2. Problem solved, phone connects in the first 10 seconds after car starts.
Could you elaborate a little on where you see the different devices?
Since this I've actually gotten a new G2 due to issues with calls not coming through with the first. Still having the same issue. I cleared everything out today and started navigation and tried connecting after that started but I don't see a difference. After turning the car off and back on it doesn't reconnect. It saves the car in my BT settings and if I go in and uncheck and recheck phone and media audio it then reconnects without repairing but it will not auto connect.
For others the WRX Bluetooth I'd very basic, no contacts syncing or anything like that so I know this isn't the issue.
Thanks
Sent from my VS980 4G using xda app-developers app
I recently purchased the N6P to replace my dying N4. The transition from one device to the other has gone pretty well, except for one issue. My N6P is unable to find the bluetooth signal from my Ford Fusion. Upon turning on bluetooth and searching for devices, the N6P cannot find the Ford Sync signal. I've rebooted the phone many times, Ive tried it many times in safe mode with no success, Ive turned the Sync's bluetooth on and off numerous times, the phone is still unable to detect it. I have also tried deleting all the paired devices on the Sync settings and had no luck with the N6P working. Aside from a factory reset of the phone, what else can I do?
My N4 was able to connect to the Sync right up to when I stopped using it. My fiancee's Samsung Galaxy (something) can detect, connect, and function with the Sync's bluetooth. I am beginning to think its something with the N6P. Ive tried it on all three versions of the OS Ive had on the phone. The original OS version didn't work when I first powered up the N6P, the next version of the OS i updated to didn't work, and this morning the phone ran the latest update and the bluetooth doesnt work.
I'm at a loss, I'm ready to return this phone and go back to my dying N4.
Edit: I am currently running Android 6.0.1.
My wife's N5x has the same problem with our ford sync, I think its related to the bluetooth disconnection bug I've had since the may update.
You can still connect it by opening the bluetooth screen on your phone so that it is visible to other devices and in the sync setup tell sync to search for devices and select your nexus phone.
My wife and I both own Nexus 6p's. I just bought a brand new Ford F-150 and my wife has a 2014 Toyota mini van (forget the model name off the top of my head, but still a fairly new vehicle). Neither one of our Nexus 6p's will connect to with vehicle. Prior to our Nexus 6p's (which I really had to talk my wife in to getting a Nexus 6p) our LG G4 and Note 5 connected flawlessly. I even bought a Bluetooth thing that plugs in to my trucks aux and that works after turning the Bluetooth on and off a few times. Totally freaking unacceptable. We both have Nexus Protect on both devices, but don't think a new Nexus 6p will fix the issue. No problem at all with Google maps other than audio coming through my brand new trucks speakers. Smh. Both of our phones are not rooted or changed in anyway. Out of the box stock.
Sent from my Nexus 6P using Tapatalk
Sent from my Nexus 6P using Tapatalk
Confirm working in Nissan Frontier. Wonder why its certain auto manufacturers?
Works in 2014 Toyota Camry.
Mine works with zero problems in my '13 Fusion Ti. I also have a bluetooth adapter for torque plugged in with no hiccups. Is your sync software up to date?
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
desilva79 said:
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
Click to expand...
Click to collapse
I can verify that I have this experience as well in one of my cars with an aftermarket bluetooth Sony head unit (that supports A2DP streaming). Haven't checked in the Nissan yet (no A2DP), but I will tonight.
Bluetooth on this model sure has some "quirks".....
I have a 2015 fusion Ti & N6P I have had zero issues. however i will say my bluetooth connection is much more stable after updating SYNC to the latest version. Bit of a pain because you have to create a ford account to gain access to the instructions/files. but here is the URL to get you started: https://owner.ford.com/tools/account/how-tos/keep-your-sync-up-to-date.html
I also have a Ford Fusion 2015 and I have no problems connecting to SYNC. It also connects just fine with my wife's Ford Escape. Which month's build are you using? Is your radio up to date? I don't think I've ever updated the SYNC software in either vehicle so I'm not sure it's that. Make sure BT is on and you have the BT page in settings open so that both devices can see each other. Then go into the car's phone menu and add a device. That's how I did it. Make sure the vehicle is not moving or preferably in park. Good luck.
It magically connected right after I posted above. Now I'm afraid to install the June security patch lol. Working flawlessly in my F-150 though.
Sent from my Nexus 6P using Tapatalk
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
Right after the DP5 installation, I had to unpair the phone and car (2016 Mazda) because the phone would never connect. It was no where near as easy as that sounds, took me the better part of 30 minutes because of repeated "unknown errors" coming from the car.
The phone paired up just fine but I still have frequent and completely unexplained dropouts on literally every Bluetooth device I have (headphones, Moto 360, car and the list goes on). So far this has been the absolute worst of the previews for BT that I have ever seen.
But then, if you read around here, it sounds like there were a lot of these that had flaky BT hardware. Have not exchanged mine, but that has certainly been my experience since I bought this back in December.
I have no issues with Bluetooth and the latest DP. I have my phone connected to a Kenwood deck.
Sent from my Nexus 6P using Tapatalk
I wonder if I have flaky BT hardware? Mine was a launch phone and it has worked perfectly in my Toyota since day 1. However I've recently bought a fitbit type band and with that application (veryfit 2.0) installed and connected to the band then if I make a call in car it drops the BT after about 30 seconds with an error message on screen saying 'corrupted probe message'. I can manually reconnect the call (it's still active on the phone) but after another 30 seconds or so it repeats the cycle. Have upgraded to Nougat Dev Preview NPD90G but still the same. Removing the app and its binding (it binds in the app not the phones BT devices in settings) and rebooting the phone resolves the issue. Tried again with a proper fitbit and the issue is identical.
I will RMA it to see if I get another one that works. Now to figure out how to put it back to stock marshmallow. gulp.
I have the same issue pairing to my car's Bluetooth keep pairing failed
bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
I had this same issue, I flashed the system file again and wiped the cache and dalvik. It seems to be ok now.
Check this solution. Pair with '0000' worked for me.
http://forum.xda-developers.com/nexus-5x/help/issue-android-nougat-bluetooth-issue-t3446073
Since switching from my Nexus 5 with 6.0.1 to a Nexus 6P with 7.0 I am also suffering from bluetooth issues. Pairing itself is not a problem but the connection sometimes drops, controls in my car don't work properly, remaining track time is not shown, etc. Haven't even tried to make calls yet. If I can't find a solution I'll probably be going back to 6.0.1.
The proposed '0000' solution is not working for me as I cannot change the PIN on my Seat Leon (2016). The PIN is autogenerated and shown on both displays to be confirmed upon pairing.
Has anybody tried flashing the latest 6.0.1 radio image and use it with a 7.0 system?
I have 3 main devices that I pair to my phone via bluetooth: watch/lg tone/car
The watch stays paired with no issues, but the watch is having issues swapping from the lg tones to the car and vice versa.
Anyone found a remedy for this?
As of now, I have to go into the bluetooth settings of the one I don't want to use and deselect media/phone, then go to the other and select media/phone. And even sometimes this takes multiple times to work.
My previous phone (gs7) had no issues swapping from the two.
Hi,
Did you get a solution ? I face the same problem and can't find any solution...
Just to clarify, when you are in your car and want to connect to it, the headphones are turned off, correct?
Having similar issues... Every time I try to connect to my car (stock Subaru WRX), I have to manually connect and it takes several attempts before it connects. Once it connects it usually doesn't drop though. Very frustrating...
Another poster resorted to getting a whole new head unit: https://forum.xda-developers.com/oneplus-5/help/sony-xav-ax100-bluetooth-issues-t3634940
ArkAngel06 said:
Just to clarify, when you are in your car and want to connect to it, the headphones are turned off, correct?
Click to expand...
Click to collapse
It's not in my car but with the bluetooth device of my motorcycle helmet. The reference is ncom bluetooth kit 3. I have to connect it manually and it takes several attempts before it connects. Sometimes it doesn't connect at all....
I have 2 headset Plantronics Backbeat Pro and Plantronics Backbeat Fit. They both work flawlessly
My Huawei Watch also works.
But my Nokia 616 Car kit wont connect at all.
And my motorcycle hemlet bluetooth kit, Cardo scala rider PACKTALK, connects, but the audio is slowed down to about 80 percent?
Same thing here.
I have been facing problems with a Sony SBH52 Headset and with my Opel Corsa E, stock infotainment system.
It gives me a hard time connecting but when it does it's stable.
I had the same with my gen 1 Moto 360 but after a factory reset to the watch and a reboot it's stable.
Sent from my ONEPLUS A5000 using Tapatalk
yubimusubi said:
Having similar issues... Every time I try to connect to my car (stock Subaru WRX), I have to manually connect and it takes several attempts before it connects. Once it connects it usually doesn't drop though. Very frustrating...
Another poster resorted to getting a whole new head unit: https://forum.xda-developers.com/oneplus-5/help/sony-xav-ax100-bluetooth-issues-t3634940
Click to expand...
Click to collapse
I had the same issue with my TSX. I did some research and cleared the cache. Worked like a charm afterwards. Did not have the issue one week since doing that
suizdude said:
I had the same issue with my TSX. I did some research and cleared the cache. Worked like a charm afterwards. Did not have the issue one week since doing that
Click to expand...
Click to collapse
Ahem, I seem to be unable to find bluetooth in my app settings. Can you please give me a hint?
It's been driving me crazy these days with my SBH-52 and I want to try this too.
Thanks!
P.S.
I'll also give it a shot with a plantronics pro headset I have to see if it does the same.
Bluetooth profiles implementations, even though they passed certification, are not always made equal! So don't end up pulling your hair if a certain BT device doesn't play nice with another.
Just as an example... Head Unit X had big issues with the initial contacts sync, right after pairing with Samsung phones (already known to sometimes play around some other standards). It would only work after several reconnects. After several weeks of debugging (poor development guys) and reproduction test (poor testing guys) it was concluded that it is a phone issue caused by some wrong timing delays in the process of exchanging information between the HU and the phone. Samsung was informed and the ticket was internally closed.
I have similar problem with Bluetooth Earbuds. Phone simple doesn't "see" the Earbuds. But strange - it can see other Bluetooth devices and other devices can see Earbuds.
I'm sure this is a OnePlus 5 software problem.
Version OxygenOS 4.5.10
i have somhow issue as urs, i have Bluetooth pad lock and android watch, it sometimes connected and sometimes not, i do believe its software issue, im on 4.5.11
Yes, it is strange. After some restarts and on/offs connection suddenly appears