I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
Related
For some reason when my phone connects to a headset that supports both audio and phone the audio will not auto connect. I have to open the bluetooth options and hold down on the device i want to connect to then check the audio box.
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
It worked before fresh 1.1 so maybe it was just a change in something.
I'm using the stock software and I have the problem so it is not freshrom
man we need an update HTC!!!!!!!
q1 almost over so we're that much closer to getting our official 2.1 update.
I've also got a bluetooth problem - would really appreciate any help you can offer.
I have a Tomtom and headphoned in my Bike Crash Helmet. I want to connect so I can hear music and phone calls through the phone in my helmet and also hear the TomTom.
The Tomtom connects to the Helmet, the phone connects to the Tomtom and I can get calls through the speakers via the Tomtom but music won't play (apart from an annoying second or two after dropping a call).
If I can get the phone to advertise headset features I could connect the Tomtom to the phone and the phone to the speakers (think that would work), otherwise I believe the Tomtom is not advertising media audio, only phone audio and don't expect I can change that.
Any thoughts...?
PS - Have tried the market headset app - unfortunately it doesn't fix the problem...
Time_Lord said:
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
Click to expand...
Click to collapse
well now the source for the CDMA hero is out so shouldnt be long till a lot of the little bugs arre resolved.
Hi
I have been trying to pair my N1 to my nissan altima 2008 bose bluetooth system but it wouldn't pair. I tried countless number Of times but it won't work.
Does anyone else have this problem?
I think I read in the Google Nexus One forum that there are issues with Nissan/Infiniti cars and the bluetooth of the Nexus one.
hmmm... I have got mine paired with Chinese all in one DVD/SATNAV/DTV unit... it works very well.. It even automatically switches on the unit when It detects a bluetooth signals from my paired Nexus One....
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Weees said:
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Click to expand...
Click to collapse
Well the other option you have is to change your car... and get a car which is compatible with Nexus One...
see here: http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
this issue is known to carry through android 2.0 and 2.1.
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
jeffokada81 said:
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
Click to expand...
Click to collapse
Yeah, I have the 2010 Mazda 3i touring and no problems either.
ID have a kenwood deck in my mazda and all works good. is there some kind of factory reset switch on your stereo, that's what I have to do t get new phones working on mine.
I have a Parrot Mki9100 and I have some problems...when I am on the car my Nexus One connect itslef with the Parrot, but it disconnect and try to reconnect many times. At the end it stops trying...
So every time I have to go to Settings->BT->Long press on Parrot device and click connect. After that it works...very annoing...
Hm... I have an '08 Infiniti G37 with the Bose system and it pairs and works just as well as it did with my G1. I would have assumed that Nissan is using the same or a similar unit for the audio system for most of their cars.
Mazda 6 gt-m 2009 here, BT carkit has no probs with the N1
Tried to pair it with the parrot in my gf's car, but same probs as described by other users. Seems it's the Parrot; my iphone had issues with it as well.
Ah well, i'd rather drive my car then hers, so good excuse to use mine
I dont get how they end up making things worse by upgrading rather than making things better !!! I mean according to : http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
This problem has been known since 1.6 and I can defenitly confirm that since It took me forever to pair my G1 previously. But with my N1 , it just never pairs, so they even made it worse. Such an important option, you would think Google would have fixed it in 2.0 but to drag it to 2.1. This is just messed up.
That is very frustrating.
@OP, someone mentioned changing your car to accommodate your nexus one, that sounds like a great idea, but if you can't get it to work you can always go with a bluetooth add on option.
At Volkswagen there were some phones that were not connecting with the manufacturer add on and customers were pissed because they paid over $400 for the option. Another thing just as bad is purchasing the unit and not being able to use the bluetooth steering wheel controls because of compatibility issues.
My conclusion is that there are too many products out there and sometimes they are just not compatible with each other. In this case it sucks that it was your car...or should I say your phone?
Well, the Nexus connects fine to my VW premium bluetooth (from 2005) but the cars system can not access the phonebook.
Not even the sim contacts which the HTC Hero could do.....
Google support suggested importing the sim contacts into the Nexus.
I wonder if they read the mails before they answer....
I've always found OEM bluetooth to be pretty uncompatible, and yet to see an update for one.
I've got a kenwood unit, which works with my steering controls, connects handsfree and audio when I turn on my ignition, and it syncs the phone book fine, showing the callers name when the phone rings. (it cost £80....) and I updated it (it's a parrot bluetooth unit in there) from my laptop via bletooth.
The N1 works best of all the phones I've had (6 htc's in 3 years) with it.
I never had an issue with my old g1...until I flashed a 2.0 ROM. Everything pairs fine, music player worked, stereo would switch over, but no sound came from speakers on phone calls. Now my nexus is the same way. I've asked Cyanogen if he would be kind enought to look into it and hopefully he will.
My N1 (locked bootloader, not rooted) routes the audio just fine, did it work before you cyanogened it?
ck3100
Wel I tried to connect my N1 to the parrot ck3100. it will see it fine, but the moment I try to link it it says paring failed. Anybody had any better luck with the ck3100 and N1?
mgymnop said:
Yeah, I have the 2010 Mazda 3i touring and no problems either.
Click to expand...
Click to collapse
I've got a 2010 Mazda 3 sport - it pairs/plays fine etc with my Nexus, but the person on the other end of the line always complains that I sound *really* quiet. I never had that problem with my G1. Do you get any complaints?
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
czechmate said:
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
Click to expand...
Click to collapse
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Monu123 said:
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Click to expand...
Click to collapse
That is weird... When I switch back to Eclair, it works OK, back to Froyo, no HF after one phonecall...
I dont know how to work with ROMs, I managed to find out how to flash firmwares, I even handled many problems with Odin and its moods, incomplete flashes, etc... But I dont know how to use these custom ROMs...
Anyway, i would appreciate if someone told me how to resolve it without custom ROMs, as I plan to use offical Froyo when it becomes available, but with this issue, it is useless for me, as I travel a lot...
No one else?
I'm having a related problem.
I'm getting music stream cut outs (1 sec max) when streaming bluetooth to caraudio WHILE wifi on.
If i disable wifi, bluetoothaudio works fine. I know they share range bt/wifi, but this is unacceptable. They should negotiate. Everytime wifi scans, i get cutouts. Unusable. Only workaround is disabling wifi (and thats annoying because i have to be constantly activating/disabling it everytime i enter somewhere with wifi etc.
Using Docrom xxjpo v8 with voodoo.
Anyone has some software fix that makes wifi behave better when bluetooth musictream on?
Here is what I see:
1. 1st time pairing - Both phone and media audio work fine.
2. Next time whenever I would get in the car: Nothing connects automatically. I try to connect manually from the phone, and it takes a while, and media audio connects. Phone audio fails.
3. Now if I go to advanced options and uncheck and re-check phone audio, it seems to connect most of the time.
4. If I unpair and delete the phone from the car's memory, and do it all over, it works for the first time, same as above.
Phone is running stock HTC stuff, no root etc.
Car is Subaru Impreza 2011.
My HTC Aria used to connect both phone and media automatically each time flawlessly. (Running CM6 and 7, <never got a chance to try with stock )
Any pointers would be great!
Thanks
Might be a car problem. My last 2010 VW GTI had a finicky bluetooth. You could stream audio and take calls, but if you walk out of range of the BT while the car is on and walk back in range it won't connect until I reset the head unit. However in my 2011 BMW, I can walk out of range and it instantly connects to my phone when I'm back in range. Connects every time without a flaw (even though I did have some occasionally difficulty with my iphone and bluetooth in the BMW)
I have exactly the same problem as described by the op. Not sure what to do but I don't talk much on the phone so it's not that big of a problem for me. If it was the other way around it would be much bigger problem. Anyone has suggestions? I woud like to make it work as it should.
Whafrodamus said:
Might be a car problem. My last 2010 VW GTI had a finicky bluetooth. You could stream audio and take calls, but if you walk out of range of the BT while the car is on and walk back in range it won't connect until I reset the head unit. However in my 2011 BMW, I can walk out of range and it instantly connects to my phone when I'm back in range. Connects every time without a flaw (even though I did have some occasionally difficulty with my iphone and bluetooth in the BMW)
Click to expand...
Click to collapse
I'd have thought that but the aria worked fine!!
dacho said:
I have exactly the same problem as described by the op. Not sure what to do but I don't talk much on the phone so it's not that big of a problem for me. If it was the other way around it would be much bigger problem. Anyone has suggestions? I woud like to make it work as it should.
Click to expand...
Click to collapse
For you also, does nothing connect by itself? I'd be somewhat happy if atleast media connected automatically
Once we have a good permanent root solution I'll play with tasker to see if I can create a workaround...but this sucks!
Raider
I have a Rogers Raider and it works really well with my Kia Sorento. I think it is the vehicle or both. Both meaning compatibility issue. I had a Samsung Vibrant (i-9000) and it worked but sometimes it doesn't connect and always seems to upload my address book which takes a long time. With this Raider, it works like a charm. The Raider works before and after root.
Did you check your vehicle Bluetooth vehicle compatibility chart? They might have one.
sohoxda said:
I have a Rogers Raider and it works really well with my Kia Sorento. I think it is the vehicle or both. Both meaning compatibility issue. I had a Samsung Vibrant (i-9000) and it worked but sometimes it doesn't connect and always seems to upload my address book which takes a long time. With this Raider, it works like a charm. The Raider works before and after root.
Did you check your vehicle Bluetooth vehicle compatibility chart? They might have one.
Click to expand...
Click to collapse
I have a 2010 Hyundai Sante Fe (similar to the Sorento). After initially pairing my Vivid to the car's bluetooth, the two have always connected, reagrdless of whether I turn on BT before or after I get in the car. I also had no problem with the old HTC HD2 (WM6x) and the Santa Fe's bluetooth.
Have you tried un-pairing the phone and car and re-pairing?
Everything works fine with mine too. I have a Toyota with BlueLogic. I used to have this problem with my old device, Motorola Atrix, didn't connect most of the times. I checked many forums and I found out it is a Gingerbread problem, with Froyo everything worked flawlessly.
Sent from my HTC Vivid via Tapatalk
connectivity issues
I have a Subaru impreza 2011 which has Bluetooth in it, and I just bought an htc rezound. I run all my music via Bluetooth so this is a pressing issue... It pairs and connects just fine the first time but I have to erase the Bluetooth memory on my phone and my stereo and re pair everytime I get in my car. I used go have an iphone and it worked fine. I checked my phone with a Bluetooth headset and it acts just like its supposed to. Any suggestions?
dangeruponu said:
I have a Subaru impreza 2011 which has Bluetooth in it, and I just bought an htc rezound. I run all my music via Bluetooth so this is a pressing issue... It pairs and connects just fine the first time but I have to erase the Bluetooth memory on my phone and my stereo and re pair everytime I get in my car. I used go have an iphone and it worked fine. I checked my phone with a Bluetooth headset and it acts just like its supposed to. Any suggestions?
Click to expand...
Click to collapse
Same symptopm..
My only hope is that the BT libs of CM9 will do some magic
What's CM9?
Mine seems to automatically connect just fine. However from time to time, very few times, the sound won't work right off the bat. If I press the volume rocket it will play a sound. Sometimes I have to press it twice then the sound will come through the speakers and music will play just fine. It's strange and quirky, but eh. Lol so if you're suck without sound, try to adjust your ringer volume to stimulate the sounds before repairing. See if that works.
dangeruponu said:
What's CM9?
Click to expand...
Click to collapse
Cyanogenmod 9, based on AOSP 4, Ice Cream Sandwich. Www.Cyanogenmod.com.
Sent from my HTC PH39100 using xda premium
I've had my Nexus 6 since Jan. 1, upgrading from an HTC One M7 GPE running 5.0 Lollipop. I experienced Bluetooth connectivity issues with the HTC One after upgrading to 5.0L from 4.4KK, and I knew they were 5.0 related, so I expected somewhat of the same when getting the N6. My problem is, even after upgrading my N6 to 5.01 and then 5.1, most of my Bluetooth issues still exist. I'm trying to figure out if they are indeed software related, or if maybe I have a defective BT radio. I'm rooted, running stock 5.1 LMY47M, with ElementalX Kernel and Nova Launcher. Here is a list of the issues I'm having with my N6 and Bluetooth:
1. Constant dropped connection to my car's bluetooth. Will connect when car is first powered on, then drops connection after about 20 seconds only to reconnect 30 seconds after that, then drop again within 30 seconds. Sometimes it will connect and stay connected for hours. This issue didn't exist with my HTC One running 4.4KK, but did happen intermittently after upgrading it to 5.0L. This issue also doesn't seem to exist when connecting my wife's N5 running 5.1 LMY47D.
2. Problem #1 also seems to exist when connecting my N6 to my Nvidia Shield Tablet running 5.0L, but not as persistent as with Car BT.
3. When my N6 does connect to my Nvidia Shield Tablet, I can send messages using joaoapps' AutoRemote over Bluetooth from my N6 to my Tablet, but not from my Tablet to my N6. Both phone and tablet are configured correctly. This one has me completely stumped and I've spent hours troubleshooting it before just giving up.
3. Audio stuttering when connected to my BT headphones. Again no issue when using said headphones with HTC One 4.4KK or wife's N5 5.1 LMY47D.
3. Bluetooth seems to turn off randomly. At first I thought it was one of my Tasker profiles, but problem still exists even after uninstalling Tasker.
4. My N6 will not connect to my BT OBDII adapter. N6 pairs with adapter, but adapter does not work with Torque or any other ODBII app. HTC One 4.4KK, wife's N5 5.1 LMY47D, and my Nvidia Shield tablet running 5.0L all connect with no issue.
I have tried every suggestion on threads (Reboot, clear Bluetooth Share cache, clear Bluetooth Share Data, forget all connections and re-pair, Bluetooth Auto Connect app) with no luck. I love my N6, but I've hated these BT issues since day one and I've crossed my fingers with every Lollipop update that they would be resolved, to no avail. I'm wondering if anyone (or everyone) is experiencing similar issues with BT, or is it just my N6, and I should return it for a new one before warranty expires. Thanks.
I only use my N6 Bluetooth with my car (ford sync) and occasionally my home phone. I haven't had any issues. Use it everyday on my commute to and from work.
Since you're experiencing this with multiple devices id assume its you phone too. Maybe contact google for warranty replacement?
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Bluetooth is different on the Nexus 6 for sure.
lords8n said:
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Click to expand...
Click to collapse
I also use Ford Sync system. For years it has been reliable and worked flawlessly. But starting with the Nexus 6, some of the common applications I use when mobile started crashing the bluetooth stack and giving the error, "Bluetooth Sharing as stopped working."
Before the Nexus 6 which is the first device I've owned with Lollipop, this never happened. The developer of the SMS texting app that is the main one affected by this, has tried everything to resolve the issue but he and I are now beginning to believe it is something baked either into the phone or lollipop, but before this device I never had any problems with bluetooth. I even went as far as to replace my HU in the car with the new pioneer that supports Android Auto, but to my chagrin, it still crashes on that head unit whenever the SMS reader trys to log off and switch back the stream to media. And unfortunately Android Auto currently does not support Pandora which is a must have for me. Pandora runs perfect on the new HU as it did on the Ford Sync as well, but the SMS reader causes BT sharing to error on both devices since the Nexus 6 and Lollipop, so there is something going on with the bluetooth stack and unfortunately no one I can find has any information about what has changed. Hoping Android Auto will soon add Pandora, but Pandora has not given any time estimation about when that will happen.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
Funny that you mention that. Previously used my Nexus 6 in the car with no issues. Only thing that changed is that I started pairing with a smartwatch in addition, and now my Nexus 6 crashes a few minutes into using Spotify over bluetooth. Complete automatic reboot.
EDIT: Yep, can definitely confirm the combination of the smartwatch and bluetooth audio device kills my phone. Had no trouble without the smartwatch.
EDIT 2: Turns out Google just sucks at bluetooth. Phone can crash regardless, it's just more likely with the smartwatch.
EDIT 3: RMA'd the phone and the new one works perfectly. Turns out it wasn't the software after all, or maybe the watch update helped.
I don't know if this is the same issue or not, but....
Ever since I got my Nexus 6 I have had bluetooth issues with both my cars. One has a Pioneer headunit (2014 model, not Android Auto), the other is a 2014 Subaru Forester with stock head unit.
In both cases there are days when it works perfectly. Then there are other times when it's a nightmare.
With the Pioneer headunit, bluetooth audio will be playing for a brief period (maybe 30 seconds?) and then something will happen and the headunit will play a repeated beep (bing bing bing bing bing bing) till I turn off bluetooth on the phone, wait a minute or two and reconnect.
With the Forester's headunit, similar situation - i'll be playing audio and it will just drop out. Maybe 60 seconds later it may come back (sometimes). Same applies to telephone calls via the headunit with bluetooth.
The same 'issue' appears with both headunits with one playing a beep when it happens the other dead silence, but both dropping in and out whether it's bluetooth audio or a call.
N6 running latest firmware. Problem has existed since I got it last year. Recently unlocked and rooted, but hasn't made a difference.
I don't know if this is the same as my problem, but it is the closest thread I could find, so I'll post here.
I've had my Nexus 6 about a week. Running 5.1.1, unlocked bootloader and rooted. I've been using a bluetooth headset for phone audio and media audio. It had been working, though I have experienced some audio dropout and stuttering with media audio. I had not been able to determine if that was a bluetooth problem or an app problem, but now I am leaning towards thinking it was a bluetooth problem because of what is now happening.
Today, media audio just stopped playing through my headset. Phone audio is working. I've tried rebooting, I've tried forgetting and re-pairing, I've tried a different headset and I cannot get media audio to play over bluetooth.
I am having the same problem with Nexus6 I have tried two different Plantronics voyager bt headsets and a Motorola Sliver. Motorola said it may be a bluetooth antenna problem
Did a resit on phone and Motorola Bluetooth
I really need bluetooth connectivity so I am stuck
Only other option is either find someone to open up the phone and check the antenna or do it myself maybe replace it myself or look for another phone and use this one as a backup
What would you all suggest?
Thanks