Database Develop

Problem with Bluetooth and OUTGOING calls

I'm running into a somewhat frustrating problem with making bluetooth calls on my AT&T Tilt.
(For reference, my Tilt has been reflashed with austinsync's 145mb bigstorage ROM, but the problem I'm going to describe ocurred on the original stock ROM, as well)
Periodically, when I make outgoing calls, the call will disconnect within the first minute. Upon watching the problem closely, I realized that my bluetooth kit (Acura HFL, preinstalled) always showed the calls as "Connecting" and not "In Use" when the problem ocurred. Any time the display said "In Use" I found the calls were not disconnected (unless I hit an actual dead spot)
What I've concluded is that the Tilt is not consistently setting the bluetooth flag that indicates that a call is in progress but, instead, conitnues to transmit that the call is connecting. For many bluetooth headsets, this is an irrelevant distinction; however, some handsfree kits (such as myself) will disconnect on their own if a call is not connected (or reported as connected) within a certain time. A variation of this problem has occurred with random calls initiated from my handset - in those cases, the call gets transferred to my handsfree only if I initiate a "transfer" command from the bluetooth kit; however, if the "call in progress" flag is not set corretly, the handsfree kit assumes that there is no call to be transferred.
In all cases, when my outgoing call was answered, the Tilt, itself, displayed that I was connected, and began running the timer. The problem seems to be limited to having that status transmitted via bluetooth.
I've already tested my handsfree with several other phones; the anomaly appears to exist with the Tilt only.
Incoming calls appear to be immune from this wierdness.
Has anyone else encountered this issue? I'm assuming this isn't a hardware problem but, instead, a bug in the BT stack. Any thoughts on a workaround? Anyone try Jetware with the TIlt/Kaiser? Any guess if that might solve the problem?
Thanks for any thoughts on this!!!
AMG

Spent an hour on the phone with AT&T and then HTC today - they were able to replicate the problem - So I guess there's a fighting chance of getting this resolved somehow, some day... Anyone here think there's a chance of a homegrown fix from this community??

BMW i_Drive has this problem
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on, and it stays that way until I do a soft reset. It also seems to freeze the BMW system. It is not every time, but often enough to be frustrating.
We W8z I guess

No issues on my 2003 5 series BMW. I'm running the HTC TyTN II ROM however. I wonder if this makes a difference...

Camstech said:
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on,
Click to expand...
Click to collapse
I've noticed an intermittent failure to connect on bluetooth on my Honda too. If I soft reset the Kaiser - I get a BT connection no problem.
Odd!- Lets hope some brightspark in these forums fixes it ASAP! I'd been blaming PhoneWeaver - Ooops
Graham

I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.

fermin said:
I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.
Click to expand...
Click to collapse
No luck. Whether it's connected to the power or not, screen off or on, no change in behaviour.

I"d like to chime in on this but I know I probably shouldn't, mainly because I haven't used the phone to make a call in my car long enough.
I had an '04 TL and my Tilt paired and worked fine on it. In the 3 weeks I had the phone, there was only one instance where the phone dropped its BT connection and I had to pick up the handset. All of my calls have been anywhere from 1 min. to around 5 min. I can't recall making any calls longer than that.
Just recently, I traded my '04 for a '07 TL. It paired up easily, voice recognition is a lot better, and my calls come in more clearly than in my older TL. Again, no conversations longer than 5 minutes. I may try to have a longer conversation on my drive home today to see the response.
Thanks for the heads up. I'll definitely keep an eye out for some of the symptoms you're experiencing.

I too have this exact problem. I have an '07 TL Type-S, and an AT&T Tilt. My phone worked fine until the 2nd official WM 6.0 release back in February, then it started exhibiting these exact symptoms. I'm now using Dutty's WM 6.1 and it is still happening but not as much. Hopefully we can get this fixed someday!
Does Bluetooth relate to the radio version? I wonder if I could get a WM 6.1 with an older radio if that would fix the problem?

Call waiting on Bluetooth

My phone is connected to my car and whenever i get call waiting, it will switch to phone's speaker. It bugs me out so much. Any solution?
Thanks guys.

Bump
No one else has this problem?

doanthaitu said:
Bump
No one else has this problem?
Click to expand...
Click to collapse
I am also experiencing this problem. I previously had a Note 3. After a software update on the Note 3, I started experiencing the problem that you describe. When wearing my Plantronics Bluetooth earpiece I would lose connection with the phone whenever I received another call (call waiting). If I ignored the incoming call it would lose connection right after the incoming call went to voicemail. If I attempted to answer the call, the Bluetooth connection would also disconnect. After much frustration, I contacted customer support. Customer Support advised me to upgrade to the Galaxy Note 4 claiming that it would solve my problems. Unfortunately I am still having the issue. Not only do I have issues with the Plantronics earpiece but also in my car. I never had these problems until the update from 4.2. I am on the verge of returning the phone and trying my first Apple product. Frustrated!!!

All over the net I'm reading about Bluetooth issues with the Note 4 and G3. From what I've read I'm thinking there's an issue with the new Bluetooth 4.1 standard. Meta data problems with a range of vehicle head units and device discovery issues. Not isolated to any one carrier or Bluetooth device.

So I went to the T-Mobile store today with a new Bluetooth earpiece that was dropping connection when a call waiting call came in. The associate there turned off the "Voice over LTE" setting and my Bluetooth connection began working correctly on my earpiece and my car. Weird....

I think i fixed it by clearing cache and data under Bluetooth sharing app. No need to turn Volte off.

I was good for a few days after turning off the "Voice over LTE" setting but then my Bluetooth issues started occurring again. Went back to T-Mobile store and after some research by the store rep, he cleared the cache in the "Bluetooth Share" application and everything went back to normal. So yeah, clearing the "Bluetooth Share" cache will fix this issue.

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.

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?

Help with bluetooth for calls

I am having a problem getting bluetooth to work with calls. When I pair with a BT device, it will often only connect for audio but not calls. I can go into the bt device settings and tap the Calls switch to turn it on but it will immediately turn right back off. This is happening on two devices that previously had no trouble connecting for calls. If I unpair the bt device then pair again, calls will work for a little while but then the calls option turns off and I have to unpair the device to get it to work again. Very very annoying.
Any idea why this is happening?

uscpsycho said:
I am having a problem getting bluetooth to work with calls. When I pair with a BT device, it will often only connect for audio but not calls. I can go into the bt device settings and tap the Calls switch to turn it on but it will immediately turn right back off. This is happening on two devices that previously had no trouble connecting for calls. If I unpair the bt device then pair again, calls will work for a little while but then the calls option turns off and I have to unpair the device to get it to work again. Very very annoying.
Any idea why this is happening?
Click to expand...
Click to collapse
i had that same problem on my A8 for a while and out of the blue one day it just stopped doing that and it worked properly ever since that day. I didnt do anything to remedy it, it just stopped effing up on its own somehow. No OTA update or anything like that either. The exact same bt headphones (Tozo 10L's) have worked seamlessly on my S9 since the day i got it. Matter of fact, i never even had to pair them as the info carried over from my A8