Related
I searched this forum and didn’t see any posts related to this issue directly, please direct me to any existing threads if I may have missed them. Sorry for the length of post, but I wanted to be as detailed as possible to fully explain the issue.
I am having some issues with the Bluetooth connections that I use in my car. I had this setup working previously on my Droid Razr Maxx with no issues, and was really hoping it would carry over to my Moto X.
I use Tasker in my car and have several profiles setup based on my Bluetooth connection state. When I enter my car, I connect to my General Motors Bluetooth for hands free calling. This connection works without issue. I also have a small USB powered Bluetooth audio receiver that converts the Bluetooth stream to a 3.5mm cable and goes into the radio deck for audio. It was a pretty cheap dongle that I got on eBay. It doesn’t have a brand name on it, but it comes up in my phone as “dmzmusic”. I’ve never had any major issues with it before, other than on occasion it fails to turn on when the car starts, but shutting the car off and turning it back on again works fine.
Last week I had my phone in a basically stock 4.4 state. Not rooted, nothing changed, etc. When I would get in the car, General Motors Bluetooth connected just fine. I did not happen to take any phone calls last week, so I’m not sure about how well that was working. I’ll get to this in a minute. My other connection for dmzmusic seemed to connect and then very quickly disconnect. This was evidenced by my Tasker profile launching Pandora, which it is supposed to do when it connects to dmzmusic. However, Pandora immediately exited again, and when I went to the Bluetooth settings, only General Motors was connected. If I tapped on dmzmusic in the list of paired devices, it connected and worked fine.
Over the weekend I rooted my Moto X with SlapMyMoto, which was quite a long process, but in the end, I was rooted and all was well. This morning, I got in my car and re-paired both devices mentioned above. When the Tasker profile fired for dmzmusic, I watched it launch Pandora, and then close it within a few seconds (there is an exit task to kill Pandora). It did this cycle three times, and then apparently stopped trying. As with before, I tapped on the connection and it worked fine. It launched Pandora, music played my whole way to work, and Pandora was killed when I arrived at work.
Now, back to the General Motors issue. Today when I was driving to work in the lovely Minnesota weather, my boss called to see where I was. My music paused, but my radio deck did not show an incoming call on the screen. I pressed the hands-free answer button, but it didn’t work. I picked up the phone and swiped right to answer, but it didn’t come through on Bluetooth. So I started talking on the handset, and after about 30 seconds, it connected to the radio and hands-free worked. When I was done with the call Pandora and music resumed, as it should.
So my question is, has anyone else had any issues with hands free Bluetooth, and/or any issues when using a hands-free device AND a media only device? In the Bluetooth settings, my General Motors connection only has the option for phone. The dmzmusic device has phone and media, but I have unchecked phone so it’s set to media only, if that makes any difference.
I know it’s a somewhat unique situation, but it’s really annoying that it doesn’t work. Tonight I am going to test having a few seconds delay on the Pandora task to see if that helps the repeat cycle that it did this morning.
Thanks!
fury683 said:
I searched this forum and didn’t see any posts related to this issue directly, please direct me to any existing threads if I may have missed them. Sorry for the length of post, but I wanted to be as detailed as possible to fully explain the issue.
I am having some issues with the Bluetooth connections that I use in my car. I had this setup working previously on my Droid Razr Maxx with no issues, and was really hoping it would carry over to my Moto X.
I use Tasker in my car and have several profiles setup based on my Bluetooth connection state. When I enter my car, I connect to my General Motors Bluetooth for hands free calling. This connection works without issue. I also have a small USB powered Bluetooth audio receiver that converts the Bluetooth stream to a 3.5mm cable and goes into the radio deck for audio. It was a pretty cheap dongle that I got on eBay. It doesn’t have a brand name on it, but it comes up in my phone as “dmzmusic”. I’ve never had any major issues with it before, other than on occasion it fails to turn on when the car starts, but shutting the car off and turning it back on again works fine.
Last week I had my phone in a basically stock 4.4 state. Not rooted, nothing changed, etc. When I would get in the car, General Motors Bluetooth connected just fine. I did not happen to take any phone calls last week, so I’m not sure about how well that was working. I’ll get to this in a minute. My other connection for dmzmusic seemed to connect and then very quickly disconnect. This was evidenced by my Tasker profile launching Pandora, which it is supposed to do when it connects to dmzmusic. However, Pandora immediately exited again, and when I went to the Bluetooth settings, only General Motors was connected. If I tapped on dmzmusic in the list of paired devices, it connected and worked fine.
Over the weekend I rooted my Moto X with SlapMyMoto, which was quite a long process, but in the end, I was rooted and all was well. This morning, I got in my car and re-paired both devices mentioned above. When the Tasker profile fired for dmzmusic, I watched it launch Pandora, and then close it within a few seconds (there is an exit task to kill Pandora). It did this cycle three times, and then apparently stopped trying. As with before, I tapped on the connection and it worked fine. It launched Pandora, music played my whole way to work, and Pandora was killed when I arrived at work.
Now, back to the General Motors issue. Today when I was driving to work in the lovely Minnesota weather, my boss called to see where I was. My music paused, but my radio deck did not show an incoming call on the screen. I pressed the hands-free answer button, but it didn’t work. I picked up the phone and swiped right to answer, but it didn’t come through on Bluetooth. So I started talking on the handset, and after about 30 seconds, it connected to the radio and hands-free worked. When I was done with the call Pandora and music resumed, as it should.
So my question is, has anyone else had any issues with hands free Bluetooth, and/or any issues when using a hands-free device AND a media only device? In the Bluetooth settings, my General Motors connection only has the option for phone. The dmzmusic device has phone and media, but I have unchecked phone so it’s set to media only, if that makes any difference.
I know it’s a somewhat unique situation, but it’s really annoying that it doesn’t work. Tonight I am going to test having a few seconds delay on the Pandora task to see if that helps the repeat cycle that it did this morning.
Thanks!
Click to expand...
Click to collapse
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Bluetooth working fine on 4.4 with my Hyundai Elantra. Phone and A2DP. Maybe try repairing?
totempole said:
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Click to expand...
Click to collapse
Thanks. I wasn't able to test it on 4.2.2 (it took right away OTA out of the box) with my Moto X, but it was working fine on my Droid Razr Maxx on 4.1.2 Jelly Bean before I got the Moto X.
I will have to try and see how it works with just the A2DP device without the handsfree. I rarely ever talk on the phone, and with the Touchless Controls I could call people and just pick up the phone. Or turn the phone portion back on for the A2DP device so the sound would come through my speakers but I'd still have to use the mic on my phone...
Still annoying. Thanks again for the reply.
gtg465x said:
Bluetooth working fine on 4.4 with my Hyundai Elantra. Phone and A2DP. Maybe try repairing?
Click to expand...
Click to collapse
Both pair automatically together when you enter the car?
I can get them to coexist, but I have to manually add the A2DP device. The car radio (General Motors) connects fine, but the A2DP cycles and then gives up, it seems.
I will try pairing them in a different order, and temporarily disabling or adding a wait clause to my Tasker profile to see if it works without that.
Thanks,
I have a Dension BT gateway for my car that provides BT audio and hands free. My phone connects automatically as long is bluetooth is turned on. I also connect to a BT OBD2 adapter sometimes, and I tried it today, and I kept playing Pandora via BT and also connected to the OBD2 adapter and had data going from both of them.
fury683 said:
Both pair automatically together when you enter the car?
I can get them to coexist, but I have to manually add the A2DP device. The car radio (General Motors) connects fine, but the A2DP cycles and then gives up, it seems.
I will try pairing them in a different order, and temporarily disabling or adding a wait clause to my Tasker profile to see if it works without that.
Thanks,
Click to expand...
Click to collapse
Yeah, but they aren't a separate connection I don't think. Pretty sure the one connection handles both.
Seems to be an issue with the A2DP device specifically. I unpaired my car and the dmzmusic device and repaired them both, same result. I added just the dmzmusic, and got the same thing.
I changed my Tasker profile to just flash a toast message to show it connecting and disconnecting instead of firing Pandora to see if that mattered and it didn't. I did not try disabling the Tasker actions entirely to see if that worked.
I have a pair of Bluetooth headphones at home that I may try as well to see if it will connect to those. They fire the same task as the dmzmusic does to launch Pandora when they connect, and kill it when they disconnect.
Hoping this gets fixed, because it's VERY annoying.
Is it possible to submit this to Google/Moto as a bug if it is a larger problem with all A2DP devices?
But it's not a problem with all A2DP devices. Works fine with both my 2013 Hyundai Elantra and my Jaybird Freedom buds.
gtg465x said:
But it's not a problem with all A2DP devices. Works fine with both my 2013 Hyundai Elantra and my Jaybird Freedom buds.
Click to expand...
Click to collapse
Thanks. I will try it with the Philips bluetooth headphones as well. The device in my car is pretty cheap. I don't know what version of Bluetooth it has, but it was only about $5. Anyone know of a similar device that can receive a Bluetooth audio signal and convert it to 3.5mm, and is powered by USB?
totempole said:
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Click to expand...
Click to collapse
Well I sort of solved this. There's an app in the Play Store called Bluetooth Auto Connect. This can connect to bluetooth devices with a set of conditions and states, and works as a plug-in to Tasker. I told it to connect to dmzmusic upon connection to any other bluetooth device (in this case, my General Motors hands free). Worked perfectly. Thought you'd like to try it out for your dual device setup.
However, I also have a new issue. It seems the reason my phone call wasn't on bluetooth at first was due to some sort of connection issue with the General Motors unit. While driving home tonight, every few minutes my car radio said Connected. And every time I turned the car screen on to thumb up a song on Pandora, it flashed Connected to a trusted device. Which implied to me that it was disconnecting periodically. No idea why it would do this. Didn't see any setting for it in bluetooth, and battery saver isn't on.
Anyone seen something like this? Will try tomorrow without the trusted device settings to see if that matters....
I noticed a similar auto-connect issue with mine, when I was attempting to troubleshoot the stuttering A2DP issues I'm having. If I have the HFP and A2DP profiles both enabled, they both connect right up when the ignition is on. If I have the HFP profile disabled, and only A2DP enabled, it doesn't connect right away and I usually have to manually force it. Very strange. This whole BT situation on this phone has been a pretty big disappointment for me, since I had everything working great with my GNex (running 4.3) and now it's like I've lost the heart of my car audio system.
I bought the Kinovo BT dongle for my wife for Christmas, so it will be interesting to see how that works with her Moto X. I'm pretty excited about trying out the AptX encoding for lossless audio, but I doubt she will even notice the difference.
Just to give you an update.. I downgraded to 4.2.2 and it connects to my Mazda automatically just fine.. Upgraded to 4.4 and the problem returns.. No apps.. Stock + root. Keep in mind that the problem lies only with the auto connect aspect of it.. Streaming/calls work fine but only after manually connecting.
Sent from my XT1053 using Tapatalk
totempole said:
Just to give you an update.. I downgraded to 4.2.2 and it connects to my Mazda automatically just fine.. Upgraded to 4.4 and the problem returns.. No apps.. Stock + root. Keep in mind that the problem lies only with the auto connect aspect of it.. Streaming/calls work fine but only after manually connecting.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Did you look at the auto connect app? It worked fine for me. My Bluetooth stopped working for a day or two because I froze a process without realizing what it was so BT wouldn't turn on at all. I think I have to remove and repair both of my devices to get the same setup I had on my Razr Maxx on 4.1.2,
The connecting/disconnection and/or 1-2 minute lag from my General Motors hands-free connection was annoying too. Have to see if that persists. I tried making the A2DP device the trusted one to see if that changes anything.
Really hoping this is something that Moto can/does fix, especially through a Play Store push like they've done with Active Display and the camera app.
not that this is much help for the OP, but my subaru auto connects voice (calls) automagically each time. it also auto-pairs/connects with my TuneLink audio (BT receiver for audio output over headphone/FM).
in the bluetooth settings, the settings button next to your device brings up the paired bt device profile. check to see if all of your devices are registered correctly. for example, my subaru says, "phone audio" and my tunelink says, "media audio".
to help complicate/annoy/support above, i also have a soundbar and BT house phone (cordless). both devices behave the same way my car/tunelink do.
640k said:
not that this is much help for the OP, but my subaru auto connects voice (calls) automagically each time. it also auto-pairs/connects with my TuneLink audio (BT receiver for audio output over headphone/FM).
in the bluetooth settings, the settings button next to your device brings up the paired bt device profile. check to see if all of your devices are registered correctly. for example, my subaru says, "phone audio" and my tunelink says, "media audio".
to help complicate/annoy/support above, i also have a soundbar and BT house phone (cordless). both devices behave the same way my car/tunelink do.
Click to expand...
Click to collapse
Thanks. I do have the boxes ticked in the device settings for which stream to use. The General Motors connection only has Phone Audio (and it's checked) and the dmzmusic A2DP device lists Phone Audio and Media Audio, only Media is checked.
Did you have these devices setup on 4.2.2 before taking the upgrade to 4.3? Did you wipe in the process? Wondering if that's why @totempole had the issue if he is rooted, he probably wiped the device in the process SBFing back to 4.2.2. If you aren't rooted and didn't wipe between 4.2.2 and 4.4, that could explain why it works OK for you and not us..
fury683 said:
Thanks. I do have the boxes ticked in the device settings for which stream to use. The General Motors connection only has Phone Audio (and it's checked) and the dmzmusic A2DP device lists Phone Audio and Media Audio, only Media is checked.
Did you have these devices setup on 4.2.2 before taking the upgrade to 4.3? Did you wipe in the process? Wondering if that's why @totempole had the issue if he is rooted, he probably wiped the device in the process SBFing back to 4.2.2. If you aren't rooted and didn't wipe between 4.2.2 and 4.4, that could explain why it works OK for you and not us..
Click to expand...
Click to collapse
not rooted/haven't wiped.
640k said:
not rooted/haven't wiped.
Click to expand...
Click to collapse
Must be something with setting it up AFTER taking the update to 4.4 Kit Kat. Wonder if @totempole tried setting thiers up after going back to 4.2 and before taking the upgrade for the root process with SlapMyMoto?
fury683 said:
Must be something with setting it up AFTER taking the update to 4.4 Kit Kat. Wonder if @totempole tried setting thiers up after going back to 4.2 and before taking the upgrade for the root process with SlapMyMoto?
Click to expand...
Click to collapse
could be completely device specific too. if your vehicle is BT v2.x or whatever. my tunelink specifically has problems with data/audio stream with the X that my X doesn't have problems with on other devices. could be software/hardware incompatibility issues.
FWIW, my vtech BT phone @ home would NEVER pair with other devices. i would always have to manually pair.
I just emailed Moto about this, because I'm having bugs too. I think that you're on to something, 640k. My Pioneer headunit (FH-P800BT) has BT 2.0, and while HSP connects fine, A2DP only works on the first pair, and after disconnecting once and reconnecting, it won't ever connect A2DP. I have to completely unpair the phone and re-pair it to get both A2DP and HSP working. My phone also gets stuck on "Connecting..." under BT whenever it's having issues connecting with A2DP. Here's the email I sent off to Moto"
I've noticed an issue with my new Moto X that I never had with my Samsung Galaxy Nexus. The phone itself performs way better than my older phone, but I've had a specific bluetooth problem. I have a Pioneer headunit that supports A2DP as well as HSP (music playback and headset functionality) and with my Galaxy Nexus, it worked great, I paired my phone up with the headunit, and both A2DP and HSP would pair at the same time, and work perfectly. With my Moto X, when I first pair the phone to the headunit, it pairs both profiles, but after I've disconnected (turned car off or turned bluetooth off) and come back, it only pairs HSP, and when I try to pair A2DP, my phone gets stuck on "Connecting..." under bluetooth to the headunit, and never will connect to A2DP unless I unpair and re-pair the entire phone. I've tried resetting my headunit and phone and still the same problem exists. Looks like other people are having issues with bluetooth too, as per this article on a popular Android forum > http://forum.xda-developers.com/showthread.php?t=2562186 < I'd like you all to check this out. Seems it's just on 4.4, and wasn't present on 4.2.2 (I never checked myself on 4.2.2, as I immediately upgraded to 4.4 when I got my phone. This doesn't seem to be a hardware problem, but more of a software problem. Please check into this, and don't just read this and act like it's only a problem a handful of people are having. I'd like to have this fixed, and while it's not a deal-breaker for me to use the phone, it does make me a bit frustrated. Thanks in advance!
Click to expand...
Click to collapse
Has anyone else had trouble getting the Moto X to automatically connect to Car Bluetooth?
My previous phone (Galaxy Nexus) worked fine, and so did my tablet (Nexus 7) when I tested it. The Moto X only connects if I toggle bluetooth off and back on again or if I select CAR MULTIMEDIA from the Bluetooth device list (I have a Subaru Outback). Other phones always connected automatically as soon as I turned the car on.
Does anyone have a fix or a workaround?
Se7enLC said:
Has anyone else had trouble getting the Moto X to automatically connect to Car Bluetooth?
My previous phone (Galaxy Nexus) worked fine, and so did my tablet (Nexus 7) when I tested it. The Moto X only connects if I toggle bluetooth off and back on again or if I select CAR MULTIMEDIA from the Bluetooth device list (I have a Subaru Outback). Other phones always connected automatically as soon as I turned the car on.
Does anyone have a fix or a workaround?
Click to expand...
Click to collapse
Mine is autoconnecting to my Kenwood HU.
Maybe try deleting all previous pairings on BT unit, and then re-pair the Moto X?
As a workaround, you could get an NFC tag and stick it on the dash or somewhere, and program it so when you tap the phone against it, it forces the BT connection.
jasoraso said:
Mine is autoconnecting to my Kenwood HU.
Maybe try deleting all previous pairings on BT unit, and then re-pair the Moto X?
As a workaround, you could get an NFC tag and stick it on the dash or somewhere, and program it so when you tap the phone against it, it forces the BT connection.
Click to expand...
Click to collapse
I did a full reset of the car stereo settings, and I've removed and re-added a number of times. I had been trying to figure out the Trusted Device thing and I only later realized that it only comes up if you have a screen lock other than "slide".
NFC could work, but that's not much easier than just toggling bluetooth. My goal is to have my phone connect even if I don't take it out of my pocket like my old phone did.
I don't know if the issue is specific to Subaru and Moto X or not. My Galaxy Nexus was running 4.4 and worked fine, but I think Moto and AOSP use different Bluetooth.
EDIT: I just tried poking through the options in the car again. It has a setting where you can pick if the connection is initiated by the car or the device, and I switched it. So far it seems to be working!
Se7enLC said:
I did a full reset of the car stereo settings, and I've removed and re-added a number of times. I had been trying to figure out the Trusted Device thing and I only later realized that it only comes up if you have a screen lock other than "slide".
NFC could work, but that's not much easier than just toggling bluetooth. My goal is to have my phone connect even if I don't take it out of my pocket like my old phone did.
I don't know if the issue is specific to Subaru and Moto X or not. My Galaxy Nexus was running 4.4 and worked fine, but I think Moto and AOSP use different Bluetooth.
EDIT: I just tried poking through the options in the car again. It has a setting where you can pick if the connection is initiated by the car or the device, and I switched it. So far it seems to be working!
Click to expand...
Click to collapse
As it turns out, it *DOESN'T* work. It was a fluke that it appeared to work.
It doesn't matter if it's set to be Car or Device initiated, it does not automatically connect. If I toggle bluetooth or manually initiate a connection from the device end, it will connect and work just fine, however.
Any ideas? Anyone else have a similar experience with the Moto X?
I have a Logitech adaptor in my truck and its behavior is that the phone connects to it fine initially, but when power is removed and restored to the Logitech, it will not reconnect automatically. This is unfortunate as starting most vehicles turns off all accessory power while the starter is cranking.
I have another, cheaper bluetooth receiver that does reconnect, but it does not sound as good as the Logitech (and has ground loop issues).
In my case, the behavior is not limited to the Moto X as I have the same behavior with several Nexus devices as well.
Se7enLC said:
Has anyone else had trouble getting the Moto X to automatically connect to Car Bluetooth?
My previous phone (Galaxy Nexus) worked fine, and so did my tablet (Nexus 7) when I tested it. The Moto X only connects if I toggle bluetooth off and back on again or if I select CAR MULTIMEDIA from the Bluetooth device list (I have a Subaru Outback). Other phones always connected automatically as soon as I turned the car on.
Does anyone have a fix or a workaround?
Click to expand...
Click to collapse
What Android version are you running? If 4.4 - try downgrading to 4.2.2 (I am not responsible if you brick your phone). Google started using new version of Bluetooth stack in 4.4 and it is not compatible with some devices.
I am on 4.2.2 and have zero problem with my car Bluetooth.
JoeSchmoe007 said:
What Android version are you running? If 4.4 - try downgrading to 4.2.2 (I am not responsible if you brick your phone). Google started using new version of Bluetooth stack in 4.4 and it is not compatible with some devices.
I am on 4.2.2 and have zero problem with my car Bluetooth.
Click to expand...
Click to collapse
It's a DE, so I'm not worried about bricking... But I haven't been on 4.2 for a long time and I'd rather not go back, even to diagnose a bug.
The major Bluetooth stack change (BlueZ to Bluedroid) actually happened in 4.2, so 4.2.2 would have already had it. There have been other changes, though, of course, and I imagine any of them could be responsible for the regression. Glad to know I'm not the only one with the problem, at least.
Se7enLC said:
It's a DE, so I'm not worried about bricking... But I haven't been on 4.2 for a long time and I'd rather not go back, even to diagnose a bug.
The major Bluetooth stack change (BlueZ to Bluedroid) actually happened in 4.2, so 4.2.2 would have already had it. There have been other changes, though, of course, and I imagine any of them could be responsible for the regression. Glad to know I'm not the only one with the problem, at least.
Click to expand...
Click to collapse
I think you should be worried about bricking. This is a quote from now deleted thread:
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
Can you guys test the bluetooth and tell me if the pairing bug is still present, under certain circumstances? I've been waiting for bluetooth to actually work properly via OTA's but so far nothing's been done.
The issue is:
On most newer bluetooth devices (2012+ car stereos, A2DP headsets/speakers, etc), the bluetooth will pair both the A2DP and HFP/HSP profiles just fine, at the same time, and if for some reason one or the other doesn't pair immediately, then they will link up within a few seconds of each other. However, I've tried to use bluetooth on my Pioneer Premier FH-P800BT, my bluetooth 99% of the time will only pair the HFP/HSP and not A2DP, and then when I try to pair up just the A2DP portion (or it tries to autoconnect) it fails out and my Moto X gets stuck on connecting, and won't ever leave this. I can manually pair the 2 devices EVERY time I turn the radio from off to on, but it's a pain and sometimes, even that doesn't work. Other users have had this issue with other car stereos and other bluetooth hardware, so I'm anxious to know if this is present. I wish I would've bought the Dev edition for Verizon because now I'm having to deal with a problem that I could've fixed, if I had an unlocked bootloader (missed out on the Chinese middleman)
Absolutely no issues here with linking on my Ford SYNC or KIA UVO, OEM systems.
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
Hi - new here on the site. Thanks in advance for any help and or advice.
I just picked up an NIB unlocked N6 off swappa loaded my sim from my Droid Turbo and everything is going good EXCEPT for the bluetooth. I have the latest Lollipop update and still having issues.
The phone does not sync with any of my bluetooth devices. It's not even "discoverable". I performed some of the troubleshooting methods; clearing cache, factory reset, etc.... and still no luck.
The seller on swappa said it may be because it's on CDMA (Verizon). But that doesn't make sense to me??
Any help would be greatly appreciated!!
@Motivated1,
There is no such thing as a "Verizon" CDMA version. They are all the same. So when you go to Setti ngs/Bluetooth and enable it, it's not visible to other decides, and it doesn't discover other devices?
Thank you for the clarification Cam30era.
Yes, that is correct. I'll turn on the bluetooth toggle and it's not discoverable nor does it discover my BT devices. I tried to pair it with my Bose Colorsound speaker, my Droid Turbo, and some bluetooth headphones...all unsuccessful.
I have had a new Nexus 6 from the Play Store. for 3 days (Activated on Sprint, but I think that is irrelevant.) I am running 5.1.1, build LMY47Z.
My one issue is that the N6 Bluetooth, which I have successfully paired with my 2012 Subaru Forester, does not automatically connect. Also, sometimes it will connect to the car, but only for audio, not for phone functionality.
I usually have to fiddle with it to force a good connection. The easiest method I have found is to toggle Bluetooth on/off on the Nexus. It sometimes takes several attempts.
Thanks boomerbubba for the response.
So, I took it to a friend of mine with a moto watch and a Note 4, the N6 connected with both of them instantly. I went home and tried to pair it with my Bose Color Soundlink and once again was unsuccessful. Since I knew the bluetooth had the capability of working, I just messed around with the speaker, holding down the bluetooth button for several seconds, turning it off and on, toggling my N6 bluetooth, and sure enough it worked!!!
So I tried to pair it up with my Droid Turbo and that worked as well.
So I really don't know what the actual problem was...maybe just a finicky unit. But all is good now!
In my experience with my previous phone (a Galaxy S4), and the same car, the Bluetooth discovery "just worked" automatically. Once I had the initial pairing set up, I never had to do anything but bring the phone into the car and it connected.
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
boomerbubba said:
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
Click to expand...
Click to collapse
I now attribute this to pilot error. I must have screwed up the initial pairings between my car and my Nexus 6. I deleted those pairings and redid them. Now my phone connects automatically when I start the car.
So, in the words of the late, great Gilda Radner on SNL: "Never mind."
I have the same problem. PITA!
My new (10 Dec 2015) 6P will not discover any of my Bluetooth device, must less connect