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.
Related
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?
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.
Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
xof9999 said:
Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
Click to expand...
Click to collapse
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
I also have the N6 with the P Legend. I am having issues where the caller can barely hear me. Do you know if you have this issue at all?
shrimants said:
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
Click to expand...
Click to collapse
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
shrimants said:
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
Click to expand...
Click to collapse
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
scap99 said:
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
Click to expand...
Click to collapse
Same here. Also have a problem where, when on a call, an incoming call will kill bluetooth. This makes it unusable in my car as it becomes a real safety issue. I have to turn off BT and use the speakerphone which luckily is good enough for the job. Even switching the source and switching back doesn't always work for me.
I regret not sending the phone back for this problem. I'm waiting on v5.1 this month as rumored, hoping that will solve the problem. May just go back to my Lumina 925.
Has anyone tried going into Google settings app -> Search & Now -> Voice and turn on Bluetooth Headset (records audion through bluetooth headset if available).
I have Nexus 5 and Jabra Stealth and I had the same problem. I could solve it thanks to these indications: hackerspace.kinja.com/reassign-your-bluetooth-phone-button-to-open-google-n-1507391132
Same issue with calls not having audio through the car Bluetooth unless I switch to speaker/handset then back. I guess Marshmellow really messed up Bluetooth on a lot of people's phones not just us. Tried different rooms(AOSP, CM, stock) no help even tried updating the radio which helped Bluetooth crashing completely and requiring a restart but the phone issues remain.
I previously owned a Sony Z3v and had no complaints. I run and workout regularly so I often use bluetooth headphones while doing so. These in particular http://www.plantronics.com/us/product/backbeat-fit. I'm been having issues since day 1 with these disconnecting. I have to power them down and power them up again to reconnect. Even when they lose connection, they show they are connected but are non responsive. I had not trouble whatsoever with my sony experia.
Anyone else having these kind of issues? I've checked the forums and I don't see any reports. Is this isolated?
I only use Bluetooth when I'm in the shower with the beats pill but it works great for me.
Sent from my SM-G925V using Tapatalk
Not entirely related but I have had issues with my original Galaxy Gear disconnecting somewhat frequently when I disconnect my BT head unit or at other seemingly random times that sometimes require me to turn BT off and on again. It's not that huge of an issue usually but BT on my S6 is not perfect for sure.
Sent from my Galaxy S6 Edge
I am having Bluetooth disconnect issues with my car. Will connect and disconnect repeatedly for about 7 minutes and then stay connected. Very annoying. Have tried several fixes but nothing has worked.
I haven't had an issue with mine when using it for my gopro.
The issue is with Android using Bluetooth 4.0 and WiFi simultaneously. I've had these issues since owning the phone. For whatever reason if you connect your phone to a bluetooth speaker where both devices are BT 4.0, the WiFi will be extremely slow or not work at all.
If you don't believe me, try it. As soon as you connect the device, try to load something like a video or song over WiFi. Or even send a Facebook message. It'll stall. As soon as it stalls, turn off WiFi and it'll magically start working again over cellular data.
No issues here, usually stream to a Bose Color Sound device, getting connection through WiFi
I have issues with mine pretty regularly with my car. A reboot of the phone will sometimes fix it. It's annoying, sometimes it will disconnect from audio but not phone or vice versa. Or it will work perfect, I'll get a phone call and it all goes to crap. The remainder of the drive will generally result in fighting with it. Maybe it will reconnect, but most of the time it won't. Never have I had a phone with so many bluetooth issues.
Had issues with my truck head unit / phone BT. Phone would continually disconnect.
Tracked it down to the Messages transferring to head unit.
If I disabled Messages in the Bluetooth / Allow Access To area, it worked fine, but obviously messages wouldn't go to my truck.
I cleaned all messaging apps, factory reset truck head unit, no fix. eventually factory reset the phone, havn't had any problems since.
Deuces said:
Had issues with my truck head unit / phone BT. Phone would continually disconnect.
Tracked it down to the Messages transferring to head unit.
If I disabled Messages in the Bluetooth / Allow Access To area, it worked fine, but obviously messages wouldn't go to my truck.
I cleaned all messaging apps, factory reset truck head unit, no fix. eventually factory reset the phone, havn't had any problems since.
Click to expand...
Click to collapse
Stopped working again.
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