I apologize if this has been asked and answered already, but doing a quick search of this forum, I didn't find my answer.
I am considering picking up a Moto X because it's frankly an awesome phone (I really like the touchless controls and other pizzazz that Moto added to it, but when it first came out it was too pricey for me).
My question is: is the Moto X plagued with the same bluetooth issues that the Nexus 4 and 5 are on Kit Kat? Specifically I want to know if the 5-second delay, on both calls and stereo audio, is also an issue on the X, and whether the bluetooth process has a tendency to crash on the X when connected either to car audio or bluetooth headset?
If any current X owners on a stock rom could weigh in, I would really appreciate it!
If you'll describe what the five second delay problem is I'll tell you if I ever experienced it. I have never seen my Bluetooth process crash. I have to repair with my car sometimes but not with my headsets so I assume that's my car's fault.
Yes... Bluetooth has a number of issues in Android 4.4 and 4.4.2. Surprising that a search didn't return a number of topics regarding it.
I have issues with crackling/stuttering on bluetooth. If I am driving and using bluetooth, resting my hand on my pants over my phone can even cause it to stutter for a few seconds. Using apps while listening to bluetooth is also not generally a good idea.
I happen to be the type of user that this doesn't impact, but I could see it being a major issue for plenty of users that I know. It may also have something to do with the music player I am using (shuttle), as I haven't tested it out with other players.
I have an att moto x and upgraded to 4.4 as soon as it came.. Trust me on 4.4 there are a hell lot of issues with bluetooth. My headset gets disconnected and reconnects too often.. while talking on phone it is such a pain. I never experienced the same issues on 4.2.2. So i downgraded back again to jelly bean and now its fine again. If you want to use kitkat stay away from this phone from my experience. Baterry life is also ruined with this update. May be they fixed these issues on 4.4.2, i dont know, i didnt dare to update as we cannot downgrade from 4.4.2
I'm another user who has stopped using my moto-x bluetooth with my car because of constant connecting/disconnecting and "picket fencing" of sound....I'm on 4.4.2 and I think it's even worse than 4.4....I'm a bleeding edger though, so I refuse to go back to 4.2. Hopefully 4.4.3 will fix the bluetooth issues if it ever gets here. Otherwise I love the phone.
ghstudio said:
I'm another user who has stopped using my moto-x bluetooth with my car because of constant connecting/disconnecting and "picket fencing" of sound....I'm on 4.4.2 and I think it's even worse than 4.4....I'm a bleeding edger though, so I refuse to go back to 4.2. Hopefully 4.4.3 will fix the bluetooth issues if it ever gets here. Otherwise I love the phone.
Click to expand...
Click to collapse
According to the log, 4.4.3 will indeed address the BT issues that some users in 4.4.2 are experiencing as well as several other bugs.
I'm on 4.4.2 stock and the bluetooth connection to my car for audio streaming is ok. It still stutters randomly, especially if I have other apps running like navigation. Didn't have any problems with disconnects. I was also on CM11 nightly builds but the stutter was really bad and more frequent so I went back to stock Kitkat.
I'm on stock KitKat 4.4 with my second Moto X ( first on AT&T, now on Verizon) and haven't had the afore-mentioned issues. I connect to a Sony MEX-BT in my car and a pair of RF-MAB2 headphones at work; both work great.
I too was worried after seeing all the posts about the Nexus but I think you should be fine with the Moto.
Thanks all for the replies. I know that there are indeed bluetooth issues with Kit Kat, but my research into my Nexus 4 issues seemed to point to issues with the drivers for the bluetooth chipset in the Nexus 4. It's interesting to me that some people have issues on the X, while others don't (perhaps different chipset revisions?).
With regards to my 5-second delay, the amount of time between when something happens on my phone (i.e. skip track, or button press on the dialer) and when I hear the result on a connected bluetooth device can be up to 5 seconds. My concern is mostly for phone calls, being behind on the "real time" conversation, but perhaps this is one of the many issues they plan to fix with 4.4.3.
I guess for now I'll wait until 4.4.3 to see if bluetooth gets any better for me on the Nexus. It's crazy to me that Google has let this go unpatched for so long. Here's hoping 4.4.3 starts rolling out in the next few weeks.
Related
The issue of Bluetooth devices not connecting and speakers dropping out was a hot topic when the 4.2 OTA came out, and to the best of my knowledge, the 4.2.1 update did nothing to fix it. Since then, I've read dozens for reported "Bluetooth fixes" for various Nexus devices (and I've tried most of them), but this is still a major unresolved issue for a lot of people. My gamepad and mouse refuse to hold a connection since the update, so after banging my head against the wall for a few weeks I reverted to 4.1.2.
Has anyone found an actual fix for the Nexus 7, or have there been any reports of when Google might respond (I've read several reports that Google tech support claims to not even be aware that a problem exists)?
For the record, I've tried the following:
- Fix permissions
- Disable all devices, clear Bluetooth Share cache... reconnect devices
- Perform a full wipe and install the 4.2.1 OTA.
- Install custom ROMs or kernals
- Disable wifi when establishing the initial device conection.
- Sacrificed a young goat at midnight on the winter solstice.
ED2O9 said:
- Sacrificed a young goat at midnight on the winter solstice.
Click to expand...
Click to collapse
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
I also had big bluetooth issues in stock 4.2.1. I have since changed quite a few things on my nexus7. Somewhere along the way, something I did seems to have fixed the issue. I didn't do any tests along the way, so I can't tell with any certainty which changes had any affect. All I can say is stock 4.2.1 bluetooth was completely and utterly broken, and what I have now doesnt have any bluetooth issues that I've noticed. I am able to stream music over Pandora (WiFi) and listen to it over bluetooth now without any interruptions.
So, here's a brief description:
CM10.1 nightlies + gapps, using the default kernel, no over/underclocking or anything like that.
wifi is always turned on, gps is always on, nfc is always turned off
About half of the gapps and a few of the default apps I have disabled. I have no proof to back it up, but I believe constant syncing and phoning home from these apps may have something to do with the issue. Calender, Exchange Services, Face Unlock, Calender Sync, One Time Init, Partner Setup, Play Movies & TV, and Play music are all the apps I disabled.
I also purposefully avoid other apps that run constantly chewing up battery and sending data to the internet like the facebook app.
Nope, nothing fixed it for me, aside from downgrading to 4.1 (which uses the Bluez bluetooth stack, rather than the Broadcom one in 4,2)
It's possible that CyanogenMod 4,2 (CM10.1) uses Bluez, and not Broadcom. I asked in the dev section, but nobody knows it seems.
bsoplinger said:
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I have had success with an old Dell XPS bluetooth mouse. Scrolling was fast and paired immediately.
No luck with Plantronics M100 headset. Nexus 7 could see it but no joy...
Maybe we need a list of what really works after 4.2.1?
More bluetooth
ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
Got my N7 2 weeks ago. Never had a chance to run on anything but 4.2.1 since first thing it updated. My bluetooth is not usable. If trying to stream video the audio is so bad that you cannot decipher anything. With music it is better but will start stuttering and becomes unusable. Same devices work fine with my Verizon Galaxy Nexus running 4.1.1.
ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I for one was completely unaware of the 4.2 bluetooth problem until I got a pair of bluetooth stereo earbuds from Audiosynq for Christmas. I got them paired and working, but the audio kept dropping out, only to come back a few seconds later. Very annoying when you are trying to listen to music But the earbuds worked flawlessly when I used them with my Samsung Galaxy Player running Gingerbread. That was my first clue that something was amiss....
Same stuttering for me with my jambox. Clearing blue share data helps it and seems to keep the problem away for a while.
Sent from my Nexus 7 using Tapatalk HD
The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars
I've been using Paranoid Android with my Bluetooth controllers and my new Motorola stereo headset.
Honestly I expected problems with the audio and have not. In fact I'm very impressed by the range. I can pretty much walk anywhere in my house without the music skipping. Of course this is streaming Pandora... so the bitrate may be lowered for streaming but whatever. Still impressed.
I'm not saying Bluetooth doesn't have its problems with 4.2 but perhaps a wipe will fix it. They did change Bluetooth protocols and there could be some remnants leftover screwing with us.
My moga controller had lag but I found that problem being caused by the Moga Pivot app. Using the universal driver fixed it right up.
Sent from my Nexus 7 using XDA Premium HD app
I had the same problems with stuttering Bluetooth over audio, then I thought it was fixed with the latest update - but I was wrong.
In my case at work I have a very weak WiFi signal, and it drops in and out and that's when my Bluetooth over Audio plays up. If I disable WiFi it's better a lot better but still not 100%. I get better results in the same environment with my Desire HD running ICS than the Nexus, which is quite disappointing
gianptune said:
The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
People should click the star and leave it at that, rather than whinging, complaining, and making **** up. But yeah, 620+ stars on that bug.
4.1.2 works, had to go to that
I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
mpkrcl said:
I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
Click to expand...
Click to collapse
I just changed from a 2.3 device to a droid mini running 4.4. I have the same problem. I've contacted Isimple to open a ticket and hopefully see if they will release a patch to flash the isimple connect gateway with. The droid mini works without issue with a bluetooth speaker that I connect to - but does not work properly in the car.
The symptoms are slowed audio, and crackling.
mpkrcl said:
I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
Click to expand...
Click to collapse
Update your device to 4.4.2
MOTO X SLAPPED
jmel said:
I just changed from a 2.3 device to a droid mini running 4.4. I have the same problem. I've contacted Isimple to open a ticket and hopefully see if they will release a patch to flash the isimple connect gateway with. The droid mini works without issue with a bluetooth speaker that I connect to - but does not work properly in the car.
The symptoms are slowed audio, and crackling.
Click to expand...
Click to collapse
I've tried pursuing the problem from both the PAC(ISimple) and Motorola ends. Never got anywhere. 4.4.2 on my Moto X doesn't fix the problem either. I've pretty much just given up on it working. I guess I'm just stuck with using a AUX cable for music. Voice calling works fine, but bluetooth would be much more convenient
mpkrcl said:
I've tried pursuing the problem from both the PAC(ISimple) and Motorola ends. Never got anywhere. 4.4.2 on my Moto X doesn't fix the problem either. I've pretty much just given up on it working. I guess I'm just stuck with using a AUX cable for music. Voice calling works fine, but bluetooth would be much more convenient
Click to expand...
Click to collapse
I have a ticket in with PAC. I told them the whole issue, mentioned this thread, and even offered to beta test a patch.
I suggest you do the same. Call them again, open a ticket. They acted like no one had called before about it.Speak to them on the phone.
I'm using aux for now, but surely this can be fixed. I don't think 4.4.2 would have fixed it... 4.4.3? maybe... isimple isn't the only device that got broken from 4.4 though.
jmel said:
I have a ticket in with PAC. I told them the whole issue, mentioned this thread, and even offered to beta test a patch.
I suggest you do the same. Call them again, open a ticket. They acted like no one had called before about it.Speak to them on the phone.
I'm using aux for now, but surely this can be fixed. I don't think 4.4.2 would have fixed it... 4.4.3? maybe... isimple isn't the only device that got broken from 4.4 though.
Click to expand...
Click to collapse
Unfortunately, I had some issues with technical support this past friday. I have gotten no indication they have even tested the device, nor that they even want to. They have tested ios7 though, and released a document on how to deal with some connectivity issues with ios7 and the isimple.
PAC is blaming google, and says to contact motorola, but we all know that this is futile.
Looks like I might be ditching this thing soon. I am unimpressed with their willingness to even understand the problem, let alone try and fix it. If anyone else has 4.4 and an isimple connect, I urge you to call in and voice any problems you are having.
Just Talked with PAC
So I just got off the phone with PAC as I was experiencing the exact same issues on my 2007 Classic Chev 2500HD. I spoke with tech support and they told me they were unaware of any such issue. I mentioned this forum, but still said that this is the first they herd of it. I do not have the Moto X, but I am having the same problems with my Note 3 Running 5.1.1 CM. If anyone does find a solution this would be truly helpful.
My moto-x Verizon DE with 4.2.2 installed connects to my Mercedes fine and the phonebook is loaded. Then, at random times, it disconnects and reconnects. This can be during a call. I have no clue what is making it drop. This has happened since I received the phone with 4.0 and it's getting frustrating.
I would love a solution....
ghstudio said:
My moto-x Verizon DE with 4.2.2 installed connects to my Mercedes fine and the phonebook is loaded. Then, at random times, it disconnects and reconnects. This can be during a call. I have no clue what is making it drop. This has happened since I received the phone with 4.0 and it's getting frustrating.
I would love a solution....
Click to expand...
Click to collapse
4.2.2? Or 4.4.2? If you haven't upgraded yet, you are missing out on a world of goodness.
If you are 4.4.2, I have no clue why you have issues, as 4.4+ cleared all my issues with Bluetooth. Good luck!
Kenichi
I have had mine disconnect once or twice when i had a lot of apps running.
Sent from my XT1058 using xda app-developers app
Kenichi said:
4.2.2? Or 4.4.2? If you haven't upgraded yet, you are missing out on a world of goodness.
If you are 4.4.2, I have no clue why you have issues, as 4.4+ cleared all my issues with Bluetooth. Good luck!
Kenichi
Click to expand...
Click to collapse
fingers typed the wrong version. I do have 4.4.2 running.
It may be some interaction between programs...for example, I wear a pebble watch (bluetooth) and a host of other programs that probably do on-line updates during the day. If it's interaction, it's going to be hard to find the culprit.....
ghstudio said:
fingers typed the wrong version. I do have 4.4.2 running.
It may be some interaction between programs...for example, I wear a pebble watch (bluetooth) and a host of other programs that probably do on-line updates during the day. If it's interaction, it's going to be hard to find the culprit.....
Click to expand...
Click to collapse
A lot of people reported BT issues with car systems after 4.4 and 4.4.2 upgrades not only on Moto X but also on other phones. Apparently something was changed in BT implementation in these versions. I am on 4.2.2, it is perfectly compatible with my car, so I am never upgrading because downgrade from 4.4.2 back to 4.2.2 is not possible for Moto X.
Mine does the same thing in my Chevy Cobalt. I see it flashing "Bluetooth connected" on my radio screen periodically when I'm driving. Sometimes if I get a phone call it won't be connected right away, so I have to answer the phone with the handset, and after a few seconds Bluetooth picks up.
It also doesn't auto connect to a A2DP bluetooth adapter that I have in my car for streaming music. I have to either connect manually, or use an app to connect once it connects to my car radio deck.
I'm rooted on 4.4. Just bought an unlock code, and will be bumping up to 4.4.2, hoping that makes it a little more reliable...
JoeSchmoe007 said:
A lot of people reported BT issues with car systems after 4.4 and 4.4.2 upgrades not only on Moto X but also on other phones. Apparently something was changed in BT implementation in these versions. I am on 4.2.2, it is perfectly compatible with my car, so I am never upgrading because downgrade from 4.4.2 back to 4.2.2 is not possible for Moto X.
Click to expand...
Click to collapse
If you move to 4.4 it'll be fine. 4.4.2 will change your bootloader however.
Kenichi
Kenichi said:
If you move to 4.4 it'll be fine. 4.4.2 will change your bootloader however.
Kenichi
Click to expand...
Click to collapse
4.4.2 does NOT solve the problem
The Bluetooth stack was changed in 4.4 making it unreliable. I had to downgrade to 4.2.2 because I rely on Bluetooth. On 4.4 the switch off between voice calls and music rarely ever works and you have to toggle Bluetooth off and on to get it working again.
Sent from my XT1058 using Tapatalk
Completely stock here with 4.4.2 and my bluetooth works perfect in my 13 Elantra. No issues at all with disconnecting.
I would really like to understand why my phone audio breaks up when connected to my car....and why it drops the connectivity and automatically re-establishes the connectivity at random times. At this point, I've just disconnected my phone from the car, but that's not a solution.
I am now on 4.4.2 and Bluetooth works much better. If you're still having issues, I'd consider a factory reset or an SBF to see if it helps. I was rooted 4.4 and did SBF to 4.4.2 before unlocking to start with a clean slate.
Auto connect to both of my devices now works, Bluetooth does not constantly connect and reconnect to my car anymore, and stays connected while on calls.
fury683 said:
I am now on 4.4.2 and Bluetooth works much better. If you're still having issues, I'd consider a factory reset or an SBF to see if it helps. I was rooted 4.4 and did SBF to 4.4.2 before unlocking to start with a clean slate.
Auto connect to both of my devices now works, Bluetooth does not constantly connect and reconnect to my car anymore, and stays connected while on calls.
Click to expand...
Click to collapse
I'm hoping to avoid that step backwards. I found on the q&a board a possible solution for the breakup of voice....turn off the internal equalization and clear the cache. I did both and hope that solves one of my problems.
4.4.2 really mucked up bluetooth for me...and 4.4.3 seems to have a number of fixes (apparently I'm not the only one with BT troubles). Has anyone found a way to get it for the moto x (verizon DE) yet?
ghstudio said:
4.4.2 really mucked up bluetooth for me...and 4.4.3 seems to have a number of fixes (apparently I'm not the only one with BT troubles). Has anyone found a way to get it for the moto x (verizon DE) yet?
Click to expand...
Click to collapse
My BT is fine now
http://forum.xda-developers.com/moto-x/themes-apps/voice-search-214-missing-442-ota-t2706208
On 442.
My bluetooth connection with my car could be better. I occasionally hear stutter and/or distortions when I'm streaming to my car, and it happens more often if there's other apps going on. Such as when I'm using google maps navigation and streaming tunein radio. I hope 4.4.3 fixes this...
ghstudio said:
4.4.2 really mucked up bluetooth for me...and 4.4.3 seems to have a number of fixes (apparently I'm not the only one with BT troubles). Has anyone found a way to get it for the moto x (verizon DE) yet?
Click to expand...
Click to collapse
It isn't even out for nexus devices yet. When nexus gets it.....you may still have a bit of a wait. Sorry.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
motoxone said:
My bluetooth connection with my car could be better. I occasionally hear stutter and/or distortions when I'm streaming to my car, and it happens more often if there's other apps going on. Such as when I'm using google maps navigation and streaming tunein radio. I hope 4.4.3 fixes this...
Click to expand...
Click to collapse
Just thought I'd mention this: I frequently listen to music in my car, but mostly podcasts. I noticed a long while back that if I started playing it on my phone BEFORE hitting the BT button in my car, the voices would be distorted and would skip ahead like 5 seconds every 30 seconds or so. However, it works perfectly fine if I hit the BT button in my car FIRST and then start playing the podcast and/or music. It's like if it's already playing on my phone before I hit BT they aren't synced up correctly and there's issues.
Not sure if that's at all what you're experiencing, but I thought I would just mention it since it sounded similar with the distortion and skipping.
somerandomname1 said:
Just thought I'd mention this: I frequently listen to music in my car, but mostly podcasts. I noticed a long while back that if I started playing it on my phone BEFORE hitting the BT button in my car, the voices would be distorted and would skip ahead like 5 seconds every 30 seconds or so. However, it works perfectly fine if I hit the BT button in my car FIRST and then start playing the podcast and/or music. It's like if it's already playing on my phone before I hit BT they aren't synced up correctly and there's issues.
Not sure if that's at all what you're experiencing, but I thought I would just mention it since it sounded similar with the distortion and skipping.
Click to expand...
Click to collapse
Unfortunately, my problems are different. The phone connects and disconnects for no apparent reason as I'm driving along....and when it is connected, the voice stutters. Totally unusable in my car.
I'm having BT problems as well. I'll have my pebble connected and as soon as I make a phone call from the BT in my truck my pebble disconnects. I get distortion also.
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