Database Develop

Bluetooth/Phone Call Issues, Anyone?

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.

Bluetooth issue

I received my new 64gb N6 replacement from Motorola because my previous one was getting hot. Now I'm having intermittent issues with Bluetooth. It connects fine with my LG Watch and Lg HBS900. When I have I connect it to my Hyundai Veloster's radio, it stops working. My previous N6 did not do this and worked perfectly with the exception of getting hot. When paired with the radio, it works for maybe 5 seconds then the radio will say "Initializing Bluetooth Handsfree,". It does this every time the phone is paired. I was thinking it was a software issue so I reflashed the firmware onto the phone and it worked for 30 seconds at first startup then the message about blue device not found. I also took my car to Hyundai to let them troubleshoot my radio and it passed. I connected my N5 to radio with no issues also.
Has someone had a similar problem and fixed it? Any help or suggestions is great. I've searched via Google and haven't found any answers or issues near what I'm experiencing. It's odd that I can pair with my headset and watch with no issues but not my radio.

dhinez said:
I received my new 64gb N6 replacement from Motorola because my previous one was getting hot. Now I'm having intermittent issues with Bluetooth. It connects fine with my LG Watch and Lg HBS900. When I have I connect it to my Hyundai Veloster's radio, it stops working. My previous N6 did not do this and worked perfectly with the exception of getting hot. When paired with the radio, it works for maybe 5 seconds then the radio will say "Initializing Bluetooth Handsfree,". It does this every time the phone is paired. I was thinking it was a software issue so I reflashed the firmware onto the phone and it worked for 30 seconds at first startup then the message about blue device not found. I also took my car to Hyundai to let them troubleshoot my radio and it passed. I connected my N5 to radio with no issues also.
Has someone had a similar problem and fixed it? Any help or suggestions is great. I've searched via Google and haven't found any answers or issues near what I'm experiencing. It's odd that I can pair with my headset and watch with no issues but not my radio.
Click to expand...
Click to collapse
After initial paring with your car there should have been a message about wanting to download contacts (or something like that). And a message on your N6 about adding to trusted devices. See this link > https://motorola-global-portal.cust...prod_answer_detail/a_id/102403/p/30,6720,9293

cam30era said:
After initial paring with your car there should have been a message about wanting to download contacts (or something like that). And a message on your N6 about adding to trusted devices. See this link > https://motorola-global-portal.cust...prod_answer_detail/a_id/102403/p/30,6720,9293
Click to expand...
Click to collapse
I've added my contacts and added the vehicle as a trusted device. I've been doing this since the release of 5.0 on the N5. I should have added that the radio will say there isn't a service connected to but still have the Bluetooth icon on like it's connected. Phone calls will go straight to Bluetooth while this happens but no sound will play. I'm going to re-download the firmware and reflash it. It sounds like a software issue. I keep saying this because I actually had two N6 before this, a 32gb and a 64, that connected just fine.

So I narrowed the issue down. It seems that if I sync my contacts with the radio that's when everything stops working. When contacts syncing is disabled the music streaming and phone calls work fine. Is there somewhere or something I can do to correct the problem? Thanks.

Bump

Finally solved my issue. It seems that my call log and messages backup I made in titanium backup was corrupted somehow. Reflashed firmware and rooted without fishing my backup fixed my issue. Oh well. I have my backup installed onto my N5

The Unofficial Android Auto Thread

Hi All,
I've been extremely excited about the integration of my smartphone with my car for a while. Almost anyone who would be in the market for a motor vehicle with an advanced head unit would also already own a smartphone with data access.
However, like any new use of technology, there are growing pains and Android Auto is no different. I have struggled through a few issues already and continue to grapple with others. A huge difficulty I had was simply finding discussion threads. Do I look on sites that focus on cars? On Android Auto? On Android OS?
So here it is. I'm starting a thread to pull together the most common problems and their solutions. Also, please note - I am not an expert in any of these things, just a user. I will give credit where I have a source but I am just gathering the info into one place and adding it to my own observations.
I haven't decided how this thread is going to look or if it will be small or big, so I will save the first few message placeholders in case and I will add known problems, work-arounds, and identified solutions as they come.
Hopefully this helps out some other users!

Troubleshooting:
I strongly suggest you make sure you have a good quality USB cable and confirm that you are able to connect your phone to your computer and transfer a file (some cables will allow charging but not data transfer).
1. Problem: Bluetooth won't pair, won't connect, etc.
Possible Solution:
It appears that Android Auto will attempt to create a BT profile. So
a) Delete the pairing on your cell phone
b) Delete the pairing on your car head unit
c) Turn OFF bluetooth on your phone
d) Plug your phone into your car's head unit. Depending on your settings, you may need to tell your car to launch Android Auto and you may need to select the device. If so, make sure you are selecting it in Android Auto (NOT Bluetooth pairing). Respond appropriately to any requests for authorization on your phone and car.
This should leave you with a properly paired device and car.
2. Problem: Every time I launch Android Auto, I have to pair my phone again!
Work-around: Once you have a working AA connection between the car and your device, go into the settings in the Android Auto app on your device and turn off the option to "Add new cars to Android Auto."
3. Problem: Android Auto notifies me of a new message but won't read it out loud/but starts to read it and cuts off.
It looks like there is a conflict between Google Now, Android Auto, and the Bluetooth handoff with the car head unit. Kudos to XDA member BuildaWall for discovering that turning off the BT headset option in Google Now fixed it for some people. I did a little more testing and found that forcing Android Auto to make your phone the primary source of audio seems to be the other piece.
UPDATE:I applied the August CM-13 Snapshot and this workaround no longer fixes the problem. I have reheaded it as a possible work-around as it might fix the issue for people on slightly older ROMs
UPDATE Sept 27/2016: I have upgraded to stock Nougat (Android 7). This issue still exists. However, after reading this XDA article, I tested an accessibility option. AA began reading the messages once again.
Possible Work-arounds:
A) Several people reported that their Media volume on their phone was being changed to zero when they plugged into AA. Some also reported that turning USB Debugging OFF fixed this issue. If you don't know what USB debugging is, don't worry about it; you would have to have intentionally turned it on. For volume, tap your volume rocker but then tap the drop down on the pop up volume notification.. It will expand to multiple volume sliders. For simplicity, make sure none are zero.
B) On your phone, go into Google Now, Options, Settings, Voice and then turn off Bluetooth Headset. This was reported to help by some but not didn't help for me.
C) On your car's head unit, in Android Auto, select a music option (I have Spotify and Google Play Music, but I think any audio source app within AA will work). If you don't want to listen to anything, just play and then pause/stop it but you CANNOT go back to the car as a primary source (eg radio or sirusXM).
D) On Nougat (Android 7) go to settings, accessibility, and enable one of the options (I have tested Voice Access, but in theory, activating any accessibility option should reactivate the message reading in AA.
4. Reported with work-around by @ReppinTheSouth - Android auto either being laggy or flat-out disconnecting
ReppinTheSouth observed this on a Pioneer avh 4100 and a galaxy s4 and reported August 7, 2016
Suggested Work-Around: Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
5. Reported by @ReppinTheSouth - When driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive.
I'm not listing this as a work-around, as it doesn't resolve the problem, but is still good to know: @ReppinTheSouth advises: This only happens when voice commands are enabled & Unplugging and replugging the phone gets the head unit out of its frozen state.
More to come!

Tips and Tricks:
I will use this page to list tips to improve performance or usability that don't fit under troubleshooting.
1. Keeping the phone screen alive and accessible.
Please exercise safe driving habits.
TL; DR:
Turn on Developer options
Turn on Stay Awake
Optional: if you have a security lock you may want to add your car Bluetooth as a trusted device for smart lock so it doesn't lock you out.
Details:
Android Auto changes your screen timeout to 15 seconds every time it is activated. When combined with its flaws with hangouts chat notification (no groups, can't initiate a new chat without certain contact book entries, can't access chats that began before connecting to AA) it is VERY frustrating.
Access the Developer Options menu
Settings >>> About Phone
Scroll to the bottom and tap the Build Number option seven times in a row. You will get some sort of message saying you have access to developer options. You only need to do this once.
Settings >>> Developer Options
Make sure they are turned on. Next turn on the Stay Awake option.
Your phone will now allow dimming but won't turn off the display.
Optional:
If you use a security lock on your device, you may want to authorize your car Bluetooth connection as a trusted device under smart lock so it won't lock while connected.
==============================

Links to Other Resources:
https://forums.oneplus.net/threads/...to-connected-to-the-cara-infotainment.488786/

Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work.... I changed my phone Bluetooth Headset setting to off and I was playing my spotify music through Android Auto. Am I forgetting something here? what versions of AA and Whatsapp do you use?

Good thread and it is much needed as far as I am concerned. I have a Pioneer avh 4100 and a galaxy s4. One of the issues I have had is with Android auto either being laggy or flat-out disconnecting for no reason. One of the things I have noticed is Android auto seems to be a resource hog. Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
The other issue I'm having which I can't solve is when driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive. I have to unplug my phone and then plug it back up to get it to work. This only happens when voice commands are enabled. I have not been able to resolve this issue.
Sent from my SPH-L720T using XDA-Developers mobile app

NLatuny said:
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work
Click to expand...
Click to collapse
Hi NLatuny & ReppinTheSouth!
@NLatuny - Thanks for the info. I just updated my Nexus 6p to the latest (august 2016) CM13 Snapshot, and the work-around no longer fixes the problem for me either. I've updated the original post. I think your request for version numbers is probably a good idea moving forward. I will update the original post to suggest that people include that in their posts.
@ReppinTheSouth - Thanks! I will look at adding those problems and your possible solutions for the lag to the top of the thread

Might be good to add a list of things you can and cannot do. For example, I found the other day through just trying you could ask various questions.
How old is (enter famous person here). = Correct answer.
I need to remember some of the other ones I've done. Good thread.
---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------
Perhaps also add how to get into Developer Mode, and what the settings in there do? The Force Day or Night mode thing is super useful.

I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.

duze76 said:
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
Click to expand...
Click to collapse
Check your permissions for Android Auto, you may have missed a few.
You can also uninstall and reinstall it.

I have tried all that, with no luck unfortunately

Having had a courtesy car for a few days that had an android auto system in I'm looking to purchase an android auto headunit for my car, probably after Christmas.
Until then I've been using my handsets connected to the aux input on my factory system. However since I got my Pixel handset last week I've encountered a couple of issues that weren't an issue on my m9 handset previously. I've reported then to the relevant support sites but as yet have received no response, so thought I would try you knowledgeable lot.
Firstly, when making or recurving phone calls with the aux cable connected the Pixel defaults to using the loudspeaker on the handset rather than putting through the aux to my car speakers.
Secondly, when receiving a message on WhatsApp i touch the screen too get it to read the message, it does so fine, then tells me I can press the mic soon symbol and say reply. When I do so I'm told "this chat app is not installed or needs an update". The app is installed and is up to date. I can send WhatsApp messages by saying "send a WhatsApp message to...." but can't reply.
Lastly, when I ask it to play specific tracks on Spotify it often comes back with no search results. Songs that I used to ask it to play regularly on my previous device come back as no search results found. Searching manually the tracks are there and can be played. And it isn't all tracks, some tracks are found without issue.
Thanks in advance.
Also hope this is in the right thread, I notice you seem to be taking mainly about the in car systems but as it can now be used on most android phones without a dedicated in car system I figured many would be doing so.

Hi folks, sorry for the absence. My N6P died on me in November and was sent away for warranty repair. Long story short, I'm very disappointed with Huawei and futuretel. Two months later, the process ended with me owning an unfixed Nexus 6P which is still under warranty until February 2017. It has a defective motherboard according the repair center but they will not repair it. So, after 2 months of making do with an iPhone 6 with a broken screen (wife's old phone), I have moved on to a One Plus 3T.
Irritatingly, Apple Carplay worked flawlessly for that time. Typical of Apple it was very locked down and had limited options. But in fairness, it executed those few features very well. Come on Google!
[/end rant]
I'm back and will try to get the thread up to date.
MM
Sent from my ONEPLUS A3000 using Tapatalk

Hello, thank you very much for this information, is very useful.
In my case, I have a Le Pro 3 X720 and is nightmare with AA, when I plug the phone on my Hyundai car the phone only charge so I had to change their ROM to lineage is 14.1 (Android 7.1.2) and with this AA starts quickly but after 5 minutes the screen is freeze then change the cable but it doesn't work, I change the cable again with the same result, so I back to use the original leeco cable and change their ROM again, with the same result, after 5 minutes the screen is freeze, the last one is AICP 12.1 (Android 7.1.2).
Do you know how to fix this?
Thank you in advance for your response.

Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance

mikefavro said:
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
Click to expand...
Click to collapse
Hi Mike,
You should say what phone and android version you are using. I have used both a One Plus 3T on Oreo beta and an LG V30 on 7.1.2.
The screen timeout sets to 15 sec when I plug in, but returns to normal when I unplug.
Sent from my LG-H933 using Tapatalk

Ford/BT bluetooth issue

OK so occasionally I see threads about BT/Bluetooth issues but although I change my phone frequently I've never had any issues with my Ford Ranger of 3 years... until now.
Worked fine with Note 8, Huawei P20 Pro and anything in between.
The issue recently is when I try and make a call via the Ford pick-up it says no network, but it's playing music at the time no problem and the phone shows up under bluetooth.
If I make a call from the phone it instantly comes up on the car system and I can speak and make the call normally. I unpaired and started over today nut no difference.
Any thoughts?

stewarta13wsb said:
OK so occasionally I see threads about BT/Bluetooth issues but although I change my phone frequently I've never had any issues with my Ford Ranger of 3 years... until now.
Worked fine with Note 8, Huawei P20 Pro and anything in between.
The issue recently is when I try and make a call via the Ford pick-up it says no network, but it's playing music at the time no problem and the phone shows up under bluetooth.
If I make a call from the phone it instantly comes up on the car system and I can speak and make the call normally. I unpaired and started over today nut no difference.
Any thoughts?
Click to expand...
Click to collapse
I don't have the issue with my Verizon N960U and 2018 Subaru Forester, but there is another thread here with the Same symptoms on a few different makes /models of vehicle.

I tried search but didn't find anything. Anybody got a link please?

Bluetooth works fine in my 2016 F150, now Android Auto is another story.

solved!
Tried a new music App - Pulsar+ and although it took ages to get all the right cover photos (about 40 out of 180 manually searching and downloading) all is well again.
Thanks

PIE Update - Car Bluetooth Issue

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?