This phone (stock, non rooted) was working with BT fine under 5.01and Kit Kat before it for mostly calls. I know it is the phone because I have tested it now in three different cars, my 2014 Prius, a new Chrysler and Ford. It exhibits the same behavior. Pairing is not a problem. If the screen in on when I enter the car the connection is made. When the screen dims (sleeps) the connection drops shortly thereafter. If I swipe and get the screen back on I can manually re-connect through the car's radio. If I enter the car with the phone in my holster, likely asleep, it will not connect.
Keeping the screen from sleeping appears to "remedy" this issue but that is hardly an option in terms of battery life. Normally I keep the phone in a holster and never had this issue. I have tried every remedy on the Internet. I am using safe lock and have the radio as a trusted device. I have removed safe lock and the same issue ensues. I have unpaired, cleared cache, re-paired etc.
last night I hooked up the phone to my Garmin Nuvi via BT. No disconnect issues.
Any suggestions on further troubleshooting? Any advice on this problem would be greatly appreciated. Thanks..
Work around found
I found an app called Bluetooth keepalive. It appears to have solved my problem for now. Since installing it the connection has not disconnected. The app uses very little battery power
Colvinhurst said:
I found an app called Bluetooth keepalive. It appears to have solved my problem for now. Since installing it the connection has not disconnected. The app uses very little battery power
Click to expand...
Click to collapse
what kind of car do you have? you might wanna look into updating software in your car or at least try it with another phone (preferably the same) just to rule it out
Is anyone else having problems with Bluetooth after the 5.1.1 update? Bluetooth crashes after about a minute when I connect to my car (2015 Mazda 3 - Mazda Connect Infotainment system). It will reconnect and disconnect again over and over. Once it crashed in the middle of a phone call. It dropped the call but then glitched the phone speaker settings. After I left my car and tried to make a call, there was no sound from the phone speaker. This was about 5 minutes after my phone had disconnected from my car and I was well out of range of any Bluetooth device. When I pressed the volume up, the Bluetooth volume increased instead of the speaker volume. This continued even after I turned Bluetooth off completely so I couldn't hear my calls. I had to reboot the phone for the speaker to work again.
I found a partial fix to this problem by going into the Bluetooth settings and under "Allow access to", selecting "Messages" to off. This prevents Bluetooth from crashing but also prevents me from getting texts to my car as well. I was able to get texts just fine before the 5.1.1 update.
Is anyone else having a similar problem and is there a fix? I have not rooted or installed any mods or custom roms to my phone. Bluetooth works fine with every other device I have connected to as well, but I haven't tried any other cars.
Here's what I have tried with no success:
- Unpairing and repairing on both my phone and car.
- Clearing Bluetooth application Data and cache.
- Wiping cache partition.
- Resetting car infotainment software to factory settings.
- Updating car infotainment software. I am now using the most current version 55.00.750B.
- Booting the phone in safe mode.
Any help or suggestions would be appreciated. Thanks!
[https://forums]
posted 8:32 AM*by*klobkelosh[https://forums]EditDeleteActionsReport AbusePermalinkQuote this Comment
Anyone else? I posted this on the Moto forum -
https://forums.motorola.com/posts/e3ade3c5ba
Definitely having bluetooth issues with newest 5.1 *attached to my Rav4 entune system. I've narrowed *down to the handoff from low quality/low latency phone bluetooth connection back to audio bluetooth connection. Often it will not complete the handoff and there is no sound but phone still thinks it is playing audio and bluetooth on the phone needs to be switched off and back on a number of times to reestablish the connection and sound. This usually happens after a phone call. Sometimes bluetooth will play audio over phone stream during phone conversation. Here's what I've tried : updating car firmware, toggling bluetooth settings in moto app under voice, removing and readding connection in car and phone, disabling Moto functions, disabling message functions. I should note that everything worked fine before update except message access. That works now.
Sent from my XT1060 using Tapatalk
Have the exact same problem after updating to 5.1. Worst update I've ever done. I've yet to find a fix for any of these problems I keep having.
Verizon Moto XT1060, with 5.1.
No issues here. The phone is connected to my car stereo's Bluetooth Headset/Hands Free profile. Since my car has only an AUX input, and doesn't have other BT audio profiles, I'm using a Blackberry Stereo Music Gateway (i.e. bluetooth receiver) connected to my AUX port to stream music..
Phone calls and streaming music work fine. Including while streaming music, it auto pauses for an incoming call, then streaming continues when I hang up the phone call.
You didn't mention in your post if you factory reset as an attempt to fix or not. If you didn't, you might want to consider trying it. I know there is a slight chance it wont correct the issue, but there is enough chance that it might. I'd suggest doing a fastboot erase cache and fastboot erase userdata... then manually setting everything back up, installing apps manually, etc.
KidJoe said:
Verizon Moto XT1060, with 5.1.
No issues here. The phone is connected to my car stereo's Bluetooth Headset/Hands Free profile. Since my car has only an AUX input, and doesn't have other BT audio profiles, I'm using a Blackberry Stereo Music Gateway (i.e. bluetooth receiver) connected to my AUX port to stream music..
Phone calls and streaming music work fine. Including while streaming music, it auto pauses for an incoming call, then streaming continues when I hang up the phone call.
You didn't mention in your post if you factory reset as an attempt to fix or not. If you didn't, you might want to consider trying it. I know there is a slight chance it wont correct the issue, but there is enough chance that it might. I'd suggest doing a fastboot erase cache and fastboot erase userdata... then manually setting everything back up, installing apps manually, etc.
Click to expand...
Click to collapse
Yeah, I did not factory reset, but I may if the problem persists. I may try running safe mode first to see if that makes a difference. I really don't want to set all the things back up...
My threads here and on Motorola's site aren't getting many responses, so I assume it is a specific conflict between Moto x and my cars Bluetooth (that, or since the x is now so old no one that cares uses it in cars any more). Too bad because everything worked prior to the update. Oh well, that's one way to get you to buy a new phone...
I'm continuing to diagnose things bit by bit but I can't find a real pattern or trigger that always disconnects Bluetooth.
Same here.
I'm having the exact same problem. I've set up a tasker profile to trigger on phone idle which toggles the bluetooth off, waits 5 sec, then toggles on again. While this doesn't address the cause, it at least automatically resets and restores my bluetooth audio after a phone call.
Also, it doesn't just happen with my car bluetooth. Also happens with my wireless bluetooth speakers in the house.
Occasionally, when a bluetooth call disconnects, the entire phone locks up and I have to force reboot. This randomly triggers the dreaded "setting up apps" process like a first install. Cleared caches, deleted and reestablished bluetooth devices, even factory reset. All seem to be very short temporary fixes.
I'm trying to connect with my bluetooth speaker (iHome) and now every time when I press the search for devices on my phone it crashes. I tried not turning on the bluetooth speaker to see if it would crash when it couldn't find anything to connect and it behaves normally - it says it couldn't find any device, but then I turn on the device and set it to discovery then the phone app crashes again.
I've tried clearing the data and cache to no avail. It still has my headphones when I go back to the app even after a restart and still can't connect.
Anyone have any solution for this?
If I have my bluetooth headset on when I get to work it then crashes several times in a row because it restarts then crashes again over and over until I just finally have to turn the darn thing off - this is a real hassle. : (
Thanks for any help
Does it work for sure? I read that it's a permanent problem and that maybe some apps are involved (like track Id)
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?