Related
Okay, so lots of people have problems with their bluetooth. I am too. I have a JVC KW-XR810 car stereo and the bluetooth keeps shutting down on one or the other. My questions are:
Does anyone else have this stereo and problem? If so, whats the situation?
Is there a ROM that works flawlessly (or close to) with the bluetooth?
Its odd though, that my headset works perfectly and I didn't have many problems with another stereo I've used. Makes me wonder if its the stereo or the phone. Still, many others have bluetooth problems with this phone...
Thanks for any responses.
Stock Froyo
Rooted
One click lag fix
My last 3 phones (including this one) have all worked flawlessly with my Sony MEX-BT3700 head unit. Phone calls, BT dialing, streaming music, all work perfectly.
Yep, same here - AT&T replaced my Captivate under warranty about 2 or 3 weeks ago due to the random shut-down issue. Took the new one home, installed Froyo, and rooted it. Everything works well, except lately I've been getting frequent bluetooth disconnects from my car stereo (Pioneer AVIC-X920BT).
The usual pattern seems to be it's good for about one call, and then shortly after ending that call, I notice that they are no longer connected. I usually turn off BT on the phone (seems to take a while to terminate) and then turn it back on, but it will usually only be good for a single call. It's been frustrating, and I'm leaning toward the problem being on the phone side, since that's where there have been recent changes.
Must be a problem with Stock Froyo. Glad I'm not using it.
I've had this issue with certain roms I was running. I have a Kenwood KDC-X993. So far on CM7 it stayed connected.
Sent from my SGH-I897
i have the same (or similar) problem with my OEM headunit on a VW Golf. BT randomly disconnects but my music (pandora) still plays through the BT stereo, unless I stop it. Then its completely disconnected and I'll have to reconnect the phone to the car.
annoying but I just deal with it.
I'm running Paragon 6 and have a Dual head unit. I haven't had any disconnect issues, my problem is the crappy Pandora app.
mdaudioguy said:
Yep, same here - AT&T replaced my Captivate under warranty about 2 or 3 weeks ago due to the random shut-down issue. Took the new one home, installed Froyo, and rooted it. Everything works well, except lately I've been getting frequent bluetooth disconnects from my car stereo (Pioneer AVIC-X920BT).
The usual pattern seems to be it's good for about one call, and then shortly after ending that call, I notice that they are no longer connected. I usually turn off BT on the phone (seems to take a while to terminate) and then turn it back on, but it will usually only be good for a single call. It's been frustrating, and I'm leaning toward the problem being on the phone side, since that's where there have been recent changes.
Click to expand...
Click to collapse
Same here, I have a Parrot mki system in my car, but I found a workaround that I hope works for you too:
Unpair with the device, and when you re-pair it, when it asks you to synchronize contacts, do not let it. It will bug you every time it connects, but just ignore the requests.
I haven't had a single disconnect since doing this weeks ago.
I've read about the contacts request from other users but it doesn't happen with mine. Another thing, when I lose the connection and I turn off bt one the phone out shuts off. Completely. Pushing the power button does nothing. Holding the volume up and power buttons together for a few seconds seems to restart it but theres no animation. Just the lock screen, media scanner, etc. Maybe its restarting on its own and the button pushing has nothing to do with it. Also, I listened to my bt headset for hours last night with no probs at alI. Idk. Is bt different for head units? I thought it all used the same protocals.
So it seems that its not my head unit, but the phone. Are there any good solutions for us?
Sent from my SAMSUNG-SGH-I897 using XDA App
My head unit never asks to download contacts. Could it be that some do because they store that info in order to identify and announce incoming calls? That would mean there's more going on than just a simple BT connection.
Yeah. One post I read said something about it using a data connection the hu for contacts. I have no idea what he was talking about though.
Sent from my SAMSUNG-SGH-I897 using XDA App
My head unit have the ability to sync contacts. When I first paired it, the phone asks me for permission and there's a check box to always allow.
Sent from my SGH-I897
nahrah said:
My head unit have the ability to sync contacts. When I first paired it, the phone asks me for permission and there's a check box to always allow.
Sent from my SGH-I897
Click to expand...
Click to collapse
The only purpose I can see for this is if the head unit has an integrated nav system. That would allow you to bring up a contact as a nav target independent of the phone.
Okay, gettinging back to my original questions. So far we've established that this is endemic to the captivate, mostly. There have been two replies saying that cm7 and paragon 6 have stable bt connections with head units. I read in another post that axura works as well. This is so frustrating that I'm just about willng to learn how to flash this thing.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
Okay, gettinging back to my original questions. So far we've established that this is endemic to the captivate, mostly.
Click to expand...
Click to collapse
We have? My first post says I have zero issues with this on my head unit with my phone on Eclair, Froyo and now Andromeda. If it is a phone issue mine is not suffering from it. Sounds more like it has something to do with head units that store contact data. Mine apparently doesn't.
Hmmm.
Yet in your second post you posited that it must be a Froyo issue.
Regardless of whether it is the phone or OS, a lot of Captivate owners seem to have bt issues of one kind or another with various devices. Maybe this is just a bt issue in general that everyone deals with (not just Captivate owners) and I'm just being sensitive because I haven't had much bt exposure.
Any help is appreciated here. I'm just looking for suggestions on what to do short of buying a new phone or head unit. It would be great if other users experiencing this problem would benefit from the discussion as well.
So far it appears that flashing a different ROM may be a solution but which one? Is there any way to change only the bt stack?
Sorry if that sounded short, but I'm REALLY frustrated with this.
My hu will store contacts as most do these days, but it doesn't ask for them. I don't think the problem is related to the contacts. I guess its just a random incompatibility thing.
I said it "might" be a problem with stock Froyo. I didn't see it the 3 days I was running it and my current ROM is Froyo-based and working without issue. The only other variable I can see is that others posting problems have reported having to deny access to contacts, something my head unit never asks for, in order to get it to work. That would appear to indicate the difference is in the head units and not the phones, but unless I could connect to one of these other head units to verify, I'm only guessing. Sorry.
i notice that if I toggle the bluetooth on my phone right before connecting it to my car, it works flawlessly
Installed a Kenwood X994 and had all kinds of issues with BT. Worked for awhile but would never auto connect. Only vehicle and area where I had BT issues. I realized it was due to the downloading of contacts at every connect. sometimes it would download than immediately disconnect. frustrating. Was on serendipity, Tried a native Cappy ROM, Cognition and now Phoenix..
The unit has the Parrot system in it so it should be ok. Finally decided to update the Firmware on the HU. So far so good. I like the contact download so I don't need to use the phone at all to make a call. Receiving calls is no problem.
Will test further tomorrow.
BTW I have a BT Garmin mounted in the truck and used it before getting the head unit. no problems connecting. The only issue with that was a delay between pressing the call button and the call being made. Hanging up was an issue as well.
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 been unable to make phone calls after connecting to your vehicle's bluetooth? Most of the time, I can make phone calls without issue. Sometimes, I can't even hear the call ring when I'm connected to bluetooth. Occasionally, when I turn my vehicle off, the call goes silent instead of transferring to the earpiece on the phone. The only way I can fix the issue is rebooting the phone. This has become increasingly frustrating for me, since the issue is so inconsistent.
I'm running the stock ROM, rooted and un-encrypted.
Thanks!
Same here
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.
robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I just got my N6 today and I'm having trouble with My Ford Touch as well. I can get it to pair and play music, but it won't "connect" to my phone. It's odd because my N5 works fine with it. I would assume the N6 wouldn't be different.
We probably have to wait for an update from Ford, which will probably take months...
EDIT: Well I decided to try it again. I deleted the Nexus 6 entry as well as the Nexus 5 entry. Went through the pairing process again and it worked as intended. Not sure what happened the first time.
I ran into the same problem as others where my N5 worked flawlessly with my Ford Sync in my fusion, but the N6 is terrible.
I love the phone, but this is really annoying. I get into the car and sometimes it connects immediately, other times I have to turn off and back on the bluetooth about 3 times for it to finally connect. Very weird. Ford offers an upgrade to my Sync system, but wants $50 to do the upgrade. Pass.
I might try what the other person did and delete all entries for phones and pair it again. Unfortunately, the weather is pretty bad outside, so it might need to wait a short bit.
Has anyone else had luck re-pairing with their car and had reliable connections?
I use Ford Sync.
robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I use Ford Sync, and everything works as expected. I am Stock and unrooted. I guess it would come down to what version of Sync. Mine is from 2012. No touch screen. I also delete all other entries on the system and start from scratch making sure that the N6 is the main device.
If I can wake up the screen on my own, outgoing calls work fine
PaisanNYC said:
I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.
Click to expand...
Click to collapse
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.
androidfan91 said:
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.
Click to expand...
Click to collapse
Since I last made that post you quoted, i purchased and installed a 2015 model of the Pioneer AVIC-8100NEX. It has Android Auto, but can be used with the regular Pioneer UI also. I have had no issues anymore with this new radio. Maybe the BT protocol in the radio is newer? Im not that tech savvy to know. But the 2015 radio had no issues with BT calls anymore, on Pioneer's UI or Android Auto's UI.
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
Received PIE OTA today. Everything seemed great until I got in the car to drove home from work. Phone connects to Bluetooth fine and stayed connected until I tried making a call. When I dialed a contact it started ringing properly over the car speakers then dropped and the status stopped showing on the car display. Phone still said it was connected to BT and phone audio routing through the Handsfreelink. I couldn't hear anything. Switching the call audio to Phone I was able to hear the person through the phone handset.
I've tried repairing to the car and restarting phone. I did not try calling through Android Auto I interface on the car, but will try that tomorrow.
Looking for similar issues I saw some hit for the Pixel devices, but it was on older beta builds of PIE.
Anyone else have this issue?
I don't have your exact issue, but my Bluetooth keeps disconnecting on my car. It worked fine on 8.1.
I also have the problem through the Android Auto app. I cleared cache from recovery and still have a problem. This makes Android 9 unusable for me...
ilatimer1 said:
I don't have your exact issue, but my Bluetooth keeps disconnecting on my car. It worked fine on 8.1.
Click to expand...
Click to collapse
Are you using a Galaxy watch? I used to have the same problem until I reset my watch then everything worked fine.
I would recommend you find out what's disconnecting the bluetooth through bluetooth > Advanced > Bluetooth control history and see if there are any apps turning off the bluetooth. Galaxy Wearable was constantly disconnecting my bluetooth when it was disconnected to my car's bluetooh and that's why I reset it.
I hope that helps.
---------- Post added at 01:40 PM ---------- Previous post was at 01:15 PM ----------
EzEddie said:
I also have the problem through the Android Auto app. I cleared cache from recovery and still have a problem. This makes Android 9 unusable for me...
Click to expand...
Click to collapse
I recommend you delete your phone 's profile from your car and reestablish it all over again after your reset your phone's bluetooth as well through settings > general management > reset > reset network settings. Bear in mind that this will erase all your bluetooth connections as well as wifi data.
Good luck.
Moe100021 said:
Are you using a Galaxy watch? I used to have the same problem until I reset my watch then everything worked fine.
I would recommend you find out what's disconnecting the bluetooth through bluetooth > Advanced > Bluetooth control history and see if there are any apps turning off the bluetooth. Galaxy Wearable was constantly disconnecting my bluetooth when it was disconnected to my car's bluetooh and that's why I reset it.
I hope that helps.
---------- Post added at 01:40 PM ---------- Previous post was at 01:15 PM ----------
I recommend you delete your phone 's profile from your car and reestablish it all over again after your reset your phone's bluetooth as well through settings > general management > reset > reset network settings. Bear in mind that this will erase all your bluetooth connections as well as wifi data.
Good luck.
Click to expand...
Click to collapse
I have already tried deleting my profile in car and clearing Bluetooth and network connections. I dont have a smart watch. The only thing left is a factory reset. But I've been reading the same problem has been reported on Pixel devices on Android Pie. I didnt see a fix though.
I have issues while playing music on Spotify and black player ex via Bluetooth on my pioneer deck in my car. The music will stop playing for like a second or two then resume. Reverting to 8.1 fixed it. I've tried a clean wipe as well.
enzyne said:
I have issues while playing music on Spotify and black player ex via Bluetooth on my pioneer deck in my car. The music will stop playing for like a second or two then resume. Reverting to 8.1 fixed it. I've tried a clean wipe as well.
Click to expand...
Click to collapse
Reverting will only fix it until the OTA installs it again though.
Wow. Thats definitely a deal breaker for me..Kind of glad Sprint hasnt received it yet! hope they fix it as I know how annoying that is.
Car BT disconnects after 5 min
EzEddie said:
Received PIE OTA today. Everything seemed great until I got in the car to drove home from work. Phone connects to Bluetooth fine and stayed connected until I tried making a call. When I dialed a contact it started ringing properly over the car speakers then dropped and the status stopped showing on the car display. Phone still said it was connected to BT and phone audio routing through the Handsfreelink. I couldn't hear anything. Switching the call audio to Phone I was able to hear the person through the phone handset.
I've tried repairing to the car and restarting the phone. I did not try calling through Android Auto I interface on the car, but will try that tomorrow.
Looking for similar issues I saw some hit for the Pixel devices, but it was on older beta builds of PIE.
Anyone else have this issue?
Click to expand...
Click to collapse
I have the same issue, Phone will connect fine initially but after like 5 minutes of playing music or calling Car will lose connection all together to BT in Phone (phone says it still connected for a couple of secs then drops as well) If I leave alone BT will connect again after a minute or so then disconnect again in a couple of minutes
I'm using Android Auto on my phone (My car does not have AAuto so use the phone as a display) so everytime BT connects disconnects AA launches
Tried resetting BT cache and data and repairing but everytime same thing.
EzEddie said:
Received PIE OTA today. Everything seemed great until I got in the car to drove home from work.
.....
Anyone else have this issue?
Click to expand...
Click to collapse
Are you using Android Auto on the phone by any chance?
What brand Car do you have?
I tested today after some BT resets and in the morning everything stayed connected so I thought it was fixed but in the drive home it disconnected 3 times while in a call !
I can confirm that this is happening specifically for me as well. Long time lurker/reader.
I'm confident I've isolated the issue to the Pie update. My Google search bringing me back 180° to here supports that.
I have that sinking feeling that this is gonna be an ongoing bugaboo. Let's hope I'm wrong!
I'm not an Android Auto user. The accompanied "drop signal" notification from my Galaxy Watch losing BT signal to phone to every few minutes is slowly eroding my sanity. Most recently on official AT&T CSAA clean wipe.
Cheers!
What's the current version of Pie on our Note 9 at the moment? From the looks of all these posts describing issues, I may have to permanently remain on Oreo for the entire life of this phone.
Hi, Annon here. Here's a real quirk... After receiving the update on my phone, I was happily driving home with music streaming through spotify via bluetooth and my husband decides to call me. The phone rings, I try to answer from the steering wheel and instead of answering the phone, it looks like it's connected the the car is still ringing the phone at me while not connecting to any voice. On my husband's end, he gets this really loud and annoying screeching sound so obviously he hangs up. But it doesn't stop there. Even though the call is disconnected (not that it ever stopped ringing on my end or connected), the phone continues to ring through my car UNTIL I GET HOME AND TURN OFF MY VEHICLE. Even after I turn off blue tooth and the radio console. It was the cherry on top of my crap day.
PIE in the face
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Anybody have a fix yet besides revert to oreo firmware?
Note 9 At&T on latest pie. Can confirm Bluetooth disappears from memory. Happens to car, headset, watch and have to re-pair over and over. Pretty frustrating. Was working perfectly prior to pie.
sledwich said:
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Click to expand...
Click to collapse
Same same my Note 9 constantly drops from my Discovery sport, I'm thinking about Odin flashing back to 8.1.
---------- Post added at 09:18 AM ---------- Previous post was at 09:06 AM ----------
sledwich said:
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Click to expand...
Click to collapse
dave5777 said:
Same same my Note 9 constantly drops from my Discovery sport, I'm thinking about Odin flashing back to 8.1.
Click to expand...
Click to collapse
I chatted with Samsung+ after I told them I already FDR'd my phone and everything else they asked about they recommended I get in contact with the warranty Dept so I can get another phone that will have the same issue once it updates to Pie
same issue here . Before describing issue please e-mail me if anyone has a fix ([email protected]) .
I have Galaxy Watch and a Honda Accord 2017. Everything went fine until upgrading to Pie. Now when phone is connected to the car system it rings but cant answer the call. Not on my steering wheel nor on my touch display. Furthermore if I try calling back It rings until person answers call and then it totally drops the call from my car system. Very annoying . If anyone comes with an answer to that please e-mail me the solution
Flashed back to 8.1 and no issues, I removed system permissions for the software update app and so far it hasn't automatically updated, I just get the persistent notification.
Same here - I just migrated from my oneplus 3t to the Note 9. And as a constant User of Android Auto, this is really a big big issue for me. Any hints besides Re-Odin?