Related
OK, I've read a bunch of these threads but I'd Like to get everyone who is knowlegeable about this together because I though I was doing everything right.
First off I am using Dutty's newest ROM that is supposed to have all the voice command mods "out of the box"
Second I have a sony ericsson HBH-DS980, shameless promo I know but, this is an awsome headset I love it and would recommend it to anyone (all I need is this problem fixed)
OK, for the most part everything was working fine at first. I paired everything and started using voice command with all my music, and random system info (battery level, date and time etc....) but then I wanted to start calling people from it and it seemed to work just fine. I'd say who I wanted to call it would ask for confermation then it would start to dial...then the wierd steps in. my headset then looses stereo connection (usually I would have it in stereo mode) so I'm looking at the handset (it takes a couple seconds to "catch up") and it says everything is fine untill the call gets picked up then it drops the ericsson completely it no longer has it as a stereo bt or even a hands-free mic. And to top things off the call just stops so I can't fix anything.
Another thing I've noticed is after something like this or even looking up a contact via voice for some reason wm and my bt don't like to "play nice" I constantly get disconnects and after a while Voice command stops hearing me through my mic (I know it's not the mic since if I reboot and repeat it works just fine) but it will work if I use it from the handset.
I don't reeally know what's going on but I do run S2U2 very often and I was just on another thread that was saying his problem was S2U2 and I want to know if anyone else has found that was the issue. Hell I'd just be happy to know I'm not alone. If anyone would like to offer help that would be great too.
OK, here is version 2 of the explination:
OK I paired my BT (I did this twice as a stereo bt and a regular handsfree) and made a call via voice command (it hears me fine and dials) after a couple seconds my BT gives the disconnect sound. After that the call ends. Not only that but my phone bars go to 0 for a split second and I get a message saying that my phone couldn't connect to my wireless internet. (most likely due to the "0 bar" issue)
After this whole thing I attempt to call (or do anything) via Voice command and it won't understand a word I say through the mic. Even rebooting doesn't solve this issue. I have to remove the bt from my list and re-pair it.
_________________________________________________________
it looks like when VC errors it takes my entire phone with it. Has anyone else had this issue. and BTW it doesn't seem to be related to S2U2 like I though in my last post since it was disabled
Are you talking about MS Voice Command or Cyberon Voice dialer??
Can you try with another BT? Just to verify that's not the bluetooth issue.
I have a similar issue with my Jawbone BT and the problem is with my BT . I have a logitech BT and it doesn't give me any problem.
Are u using s2u2 v0.99 or v1.0?
If you want (BT handfree + s2u2 + voice commander) all three together, you may need to give up the new version and install back the v0.98.
It works for me on my Elf powered by Cloudyfa's shadoW 2.1 TE
Hope it helps.
Cheers
xcom923 said:
OK, I've read a bunch of these threads but I'd Like to get everyone who is knowlegeable about this together because I though I was doing everything right.
First off I am using Dutty's newest ROM that is supposed to have all the voice command mods "out of the box"
Second I have a sony ericsson HBH-DS980, shameless promo I know but, this is an awsome headset I love it and would recommend it to anyone (all I need is this problem fixed)
OK, for the most part everything was working fine at first. I paired everything and started using voice command with all my music, and random system info (battery level, date and time etc....) but then I wanted to start calling people from it and it seemed to work just fine. I'd say who I wanted to call it would ask for confermation then it would start to dial...then the wierd steps in. my headset then looses stereo connection (usually I would have it in stereo mode) so I'm looking at the handset (it takes a couple seconds to "catch up") and it says everything is fine untill the call gets picked up then it drops the ericsson completely it no longer has it as a stereo bt or even a hands-free mic. And to top things off the call just stops so I can't fix anything.
Another thing I've noticed is after something like this or even looking up a contact via voice for some reason wm and my bt don't like to "play nice" I constantly get disconnects and after a while Voice command stops hearing me through my mic (I know it's not the mic since if I reboot and repeat it works just fine) but it will work if I use it from the handset.
I don't reeally know what's going on but I do run S2U2 very often and I was just on another thread that was saying his problem was S2U2 and I want to know if anyone else has found that was the issue. Hell I'd just be happy to know I'm not alone. If anyone would like to offer help that would be great too.
Click to expand...
Click to collapse
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.
So, this may have been brought up already, I did try to search, but didnt come up with much.
So, i bought a Moto X, even after hearing the lenovo/google news. I figure that they cant ruin the device quickly enough to justify second-guessing my long and painstaking decision process.
Anyway, touchless control is pretty awesome. Ive been tinkering with it since i got it. I'm a long time android user, and have been using google now for some time. The problem is this.
I drive a 2013 Jeep, with a UConnect bluetooth hands-free system. It works for what its supposed to work for, i can make calls, stream audio, all is well. In fact its working better than it did on my old GNex. However, once I connect my motox to UConnect (that is, i get in, turn on the Jeep, and bluetooth associates), touchless control becomes unresponsive. In fact, it seems that even if i try to manually initiate a voice search, google now cant hear me. I can use the voice input for the keyboard, just not voice commands. It's almost like as soon as i'm paired to a bluetooth input, google now voice input/touchless control get turned off. Which to me seems odd.
I tried looking around in my settings, i cant seem to find a setting that tells the phone to do this. It just doesnt work.
Also, if i turn off bluetooth while the Jeep is still running, touchless/voice input starts working again.
I havent tried pairing it to another bluetooth headset to see if it does it then too, i'll update this thread once i've had a chance to try that.
Is this something others are experiencing? Is it supposed to do this for some safety feature, and I dont know it?
Thanks!
Google Now>Settings>Voice>Bluetooth Headset
Solutions Etcetera said:
Google Now>Settings>Voice>Bluetooth Headset
Click to expand...
Click to collapse
Thanks! Just changed the setting. I'll give it a shot as soon as im back in my Jeep!
Ok, results.
I found the Bluetooth headset option was turned off by default. I turned it on. Last night I had a chance to fiddle with it on my way home. At first it didn't work. So i went back into the Google now settings and turned the option back off, and..... It started working! I have no idea why. I'm actually back in the same config I started with, but now it's working. Weird.
Gotta love android...
Solutions Etcetera said:
Gotta love android...
Click to expand...
Click to collapse
I do love android! But yea, i agree. Some weird stuff here.
gangrif said:
I do love android! But yea, i agree. Some weird stuff here.
Click to expand...
Click to collapse
The other day I had a Bluetooth headset on listening to a podcast via Pocketcasts and when I used Google Now, sometimes the response would play over the phone's speaker, and other times over the headset.
Pretty clear Android still hasn't gotten Bluetooth right. )c:
Solutions Etcetera said:
Pretty clear Android still hasn't gotten Bluetooth right. )c:
Click to expand...
Click to collapse
yeah, ain't that the truth! I couldn't get a Moto X to pair with my Lexus when an iPhone 5 can.
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.
5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS
Yes it is happening to others myself included. why? I have no idea. But you are certainly not alone.
Sent from my Google N6 on VZ
I just posted this in the General section ....
OTA'd the 5.1 update on 3/26/15.
Since then, contact addresses fail to appear on vehicle displays over Bluetooth.
Rebooted phone / Forgot and paired phone to vehicle, no fix.
Phone is paired to 2 vehicles with the same results.
Can anyone confirm this?
Having the same issue. If you disable ambient display, the screen will stay off when selecting tracks with Bluetooth. My issue with Bluetooth is that every few days I have to reboot the phone to get the BT to work. I can't even toggle Bluetooth. When I do, it says Bluetooth turning off, it toggles back on by itself. Tried force closing all running apps but dosent help.
Bluetooth...
jeffreii said:
5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS
Click to expand...
Click to collapse
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.
vvveith said:
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.
Click to expand...
Click to collapse
It wasn't perfect, but my Bluetooth was just fine pre 5.1...I can deal with the quirks and avoid spending $$ on Android Auto (for now at least)...but these major bugs need to be fixed ASAP.
Do we know if this is fixed?
Is this fixed in 5.1.1? Is there an issue logged with google? Anyone?
I have my nexus 6 rooted with 5.1.1 stock and the bluetooth doesn't work. I cannot see any device but the other devices can see it.
I have tried to fix it clearing cache and data (only bluetooth) but the problem is still there.
Do you have any idea guys?
This morning I remembered my experiments with my old gt-9100 and I have decided to do wipe cache and wipe dalvik-cache.
And now... bluetooth is alive!!!
[emoji39]