I have a 2013 Chevy Spark with bluetooth. It has the voice control activation button on the steering wheel. When I had my Galaxy Note, this would activate S-Talk and I could use voice controls through the car. When I try with the One, an app pops up and quickly closes on the phone, then the radio says voice control isn't supported, but half the time if I start talking, the voice control works anyways. Does anyone know if there is a way to fix this? I am on ARHD, but I had the same issue when I was still completely stock with a locked bootloader. This could be a deal breaker because I do a ton of driving and use voice control a ton.
Hello everyone,
I'm a recent convert from an iPhone 5. Work took over everyone's cell contracts so I thought why not try it. So far it's been a mixed bag. The hardware is great: nice big screen, loud speakers, decent camera. But, there are somethings that have me scratching my head, like the lack of unified email, on-screen notifications, etc. I've managed to work out most of them but one that is really bugging me is voice control in my car.
I have a JVC X50-BT stereo. With my iPhone, I could hold the call button and it would invoke Siri. With Siri I could send messages, ask for addresses, or pick music to play. With the One, the voice button says "Not Supported". I'm able to stream music and use the next/prev buttons, go through the phonebook, recent and missed calls, but the call/voice control button doesn't work.
Does anyone know of a work around or way of achieving this? I know it may sound like a small thing but leaving the phone in my pocket and being able to do these tasks without taking it out or looking at it while I'm driving is important. I didn't think that it could support all the other features over bluetooth except for this one.
I'm running HTC Sense 4.2.2 (flashed) on a Telus phone.
Thanks.
I've had this problem in the past with my old GNex, but it seems much worse on my new Moto X. i've been unable to find a solution, so it's come to asking the XDA crowd.
I use bluetooth audio to stream music from various app's through my Jeep's stereo (Using UConnect if that has any bearing on the situation).
I've had the moto x for about a month. When i first got it, this didnt seem like a big problem, but within the past week or so, maybe even since the most recent update (though i do not have solid proof of that) its become a real problem.
When my phone associates to my UConnect, it immediately opens up google music, and starts playing whatever it can get its mit's on. If it has local cached content it plays that, if it doesnt, it'll go out to google music and get something to play. Even if i have nothing queued. Its like its on a mission to entertain me (even at the cost of my monthly data allowance). If i close google music in the notification area, about 50% of the time, it'll just open itself right back up again. If i pause it, it'll start playing again in a few seconds. If i open google music, clear my queue, and close google music, it'll put something back into queue, and start playing that.
All of this would be fine, if i only listened to google music, and had something queued all the time. but i dont. Sometimes i do use google music, other times i'm listining to di.fm, or some other media app, like podcasts or whatever. or sometimes, i'm not even listening to media from my phone, rather satellite or something. In which case i may not even realize that the phone has started playing media, until i check the phone for some other reason.
I assumed that this was my UConnect asking my phone to play something. Like an auto "play" command sent to whatever bluetooth device is connected. However, i cant find any way to tell UConnect not to do this, and the more i fight with it. the more i think its something on the phone, not the UConnect.
I found this thread, while starting this one. http://forum.xda-developers.com/showthread.php?t=2564580 which is the same issue, on a different device. Unfortunately it doesnt look like it's gotten a good answer. It links to an app that is supposed to kill off media apps that start right as bluetooth does, but that seems like a hack rather than a fix. Regarless, im going to try the app. I'd like to know if there's a better fix though.
Ive tried looking through google music's settings, nothing in there about turning this off.
Has anyone had this issue? Have you found a decent solution?
Thanks!
gangrif said:
I've had this problem in the past with my old GNex, but it seems much worse on my new Moto X. i've been unable to find a solution, so it's come to asking the XDA crowd.
I use bluetooth audio to stream music from various app's through my Jeep's stereo (Using UConnect if that has any bearing on the situation).
I've had the moto x for about a month. When i first got it, this didnt seem like a big problem, but within the past week or so, maybe even since the most recent update (though i do not have solid proof of that) its become a real problem.
When my phone associates to my UConnect, it immediately opens up google music, and starts playing whatever it can get its mit's on. If it has local cached content it plays that, if it doesnt, it'll go out to google music and get something to play. Even if i have nothing queued. Its like its on a mission to entertain me (even at the cost of my monthly data allowance). If i close google music in the notification area, about 50% of the time, it'll just open itself right back up again. If i pause it, it'll start playing again in a few seconds. If i open google music, clear my queue, and close google music, it'll put something back into queue, and start playing that.
All of this would be fine, if i only listened to google music, and had something queued all the time. but i dont. Sometimes i do use google music, other times i'm listining to di.fm, or some other media app, like podcasts or whatever. or sometimes, i'm not even listening to media from my phone, rather satellite or something. In which case i may not even realize that the phone has started playing media, until i check the phone for some other reason.
I assumed that this was my UConnect asking my phone to play something. Like an auto "play" command sent to whatever bluetooth device is connected. However, i cant find any way to tell UConnect not to do this, and the more i fight with it. the more i think its something on the phone, not the UConnect.
I found this thread, while starting this one. http://forum.xda-developers.com/showthread.php?t=2564580 which is the same issue, on a different device. Unfortunately it doesnt look like it's gotten a good answer. It links to an app that is supposed to kill off media apps that start right as bluetooth does, but that seems like a hack rather than a fix. Regarless, im going to try the app. I'd like to know if there's a better fix though.
Ive tried looking through google music's settings, nothing in there about turning this off.
Has anyone had this issue? Have you found a decent solution?
Thanks!
Click to expand...
Click to collapse
I had this on my GNex, Nexus 4 and my Moto X and it's very annoying. I'm not sure if it's not just related to the type of bluetooth device you are connecting to though as I don't remember this happening when connecting to a set of BT headphones or a portable radio, only in my car. I'm rooted so I have just either uninstalled Play Music or used Titianium and froze it which is what I did on the Moto X since I want to easily have a stock system for OTA's.
FSRBIKER said:
I had this on my GNex, Nexus 4 and my Moto X and it's very annoying. I'm not sure if it's not just related to the type of bluetooth device you are connecting to though as I don't remember this happening when connecting to a set of BT headphones or a portable radio, only in my car. I'm rooted so I have just either uninstalled Play Music or used Titianium and froze it which is what I did on the Moto X since I want to easily have a stock system for OTA's.
Click to expand...
Click to collapse
I've thought of doing just that. The problem is, i use google play music. Just not all the time. I'd rather it didnt just pop up and start playing.
On my GNEX, it was Apollo player in Cyanogen that kept popping up. But all I did to solve that was delete all local music. Google play music was never a problem on that device.
Your right about Apollo player doing that also. What's so screwed up is I could be playing a podcast get out of my car for a few minutes then get back in and once I connect BT Pay Music starts even though the podcast is active and paused.
Have you noticed it happening on other BT devices other then your car?
Beamed from my Moto X
FSRBIKER said:
Your right about Apollo player doing that also. What's so screwed up is I could be playing a podcast get out of my car for a few minutes then get back in and once I connect BT Pay Music starts even though the podcast is active and paused.
Have you noticed it happening on other BT devices other then your car?
Beamed from my Moto X
Click to expand...
Click to collapse
Im a relatively light bluetooth user. My Jeep is really the only bluetooth device i use for media output. I do have a headset (media headset, not phone headset) that supports bluetooth, that I could test with that.
I have 4 bluetooth devices (two headphones, and two receivers hooked to audio systems) and have never seen this behavior on my moto X, Nexus 4, or Nexus 7.
However, Assist has a setting to resume playback when it detects you are driving; have you checked that?
Solutions Etcetera said:
I have 4 bluetooth devices (two headphones, and two receivers hooked to audio systems) and have never seen this behavior on my moto X, Nexus 4, or Nexus 7.
However, Assist has a setting to resume playback when it detects you are driving; have you checked that?
Click to expand...
Click to collapse
Nope, not set to do anything while driving. I dont have that profile enabled.
One thing I did do, which may or may not be related, it tell google now what to use to handle my music (and i set it to google play music) requests. Maybe i'll try turning that off to see what happens.
OK, i just tested it with my headset.
Connected bluetooth, it didnt do anything automatically.
I fired up DI.FM's app, and played some music, it played through the headset as expected (verifying that the phone and the headset were actually successfully paired).
I turned off the headset, the phone disconnected bluetooth within a few seconds.
Turned the headset back on, bluetooth reconnected, nothing happend.
So, i figured i'd try to emulate a "play" command. I pressed play on the headset, and it fired up DI.FM (the last media app i had open) NOT (this is important!) NOT google play music!
Every time i get in the Jeep, its google play music that opens, regardles of what the last app i was playing media on was. Why would this be different? Also, it only tried to start anything after I pressed play.
Is there any way to diagnose whether my UConnect is sending a play command? Some sort of bluethooth debugger or something?
Just for grins, try setting a different app than Play Music in the Assist settings to see if that app is then opened.
Solutions Etcetera said:
Just for grins, try setting a different app than Play Music in the Assist settings to see if that app is then opened.
Click to expand...
Click to collapse
Tried switching it to beyond pod, the podcast app i use. We'll see what happens next time i'm in the Jeep.
gangrif said:
Tried switching it to beyond pod, the podcast app i use. We'll see what happens next time i'm in the Jeep.
Click to expand...
Click to collapse
Switching didnt help.
Also, removing the google play music check from the google now search options, didnt help.
Im going to give the auto-kill app listed in that other thread a try, see what happens. Still seems like there should be a better solution here. Its not like android to make an assumption like this and not let you turn it off.
the issue is not how you're connecting. the issue here is Google Play Music if i'm remembering correctly. on an SGS4, if, for example,Google Play Music and Spotify are installed alongside each other, even if the last app i was using was Spotify, when i reconnect to BT Google Play Music takes precedence and will start playing something. this is why i do not have Google Play Music on my device.
Hello everyone! I have been trying to track down a problem with my Galaxy S4 Active that has been driving me nuts for a while. I figured that making a new thread would probably be best because I did not find my particular issue listed.
Basically, what happens is that I will make a call over Bluetooth and everything will be fine. Once this call has ended, all audio related to phone calls dies. The phone still behaves as if it is making and receiving calls, but nobody can hear me and I cannot hear them. Not over Bluetooth, through the earpiece, nor over the loudspeaker. It’s all dead. I also cannot hear it ringing if I dial out, but the phone itself still rings.
I have tried turning the Bluetooth device on and off, disabling Bluetooth and turning it back on, going into Airplane mode and back out again, turning speakerphone on and off, muting and unmuting the call, and muting and unmuting the phone itself. The only thing that fixes this situation is restarting the phone.
I recall this situation first started presenting itself after updating to the ML2 firmware, but it didn’t happen all the time. It became much more apparent after updating to the NE3 firmware. At that point I spent some more time looking into it and became able to readily duplicate the issue.
I have gone so far as to reflash the NE3 firmware with Odin 3.07 to see if the issue remained. Interestingly enough, this appeared to correct the issue until I started updating and reinstalling a few apps. So now I’m trying to track down exactly what did it.
I suspect that it may be the “OK Google” hotword scanning from Google Search because I had it set to detect “From any screen” as well as “From lock screen”. Although I did not have the “Bluetooth headset” setting enabled because I wanted to take that out of the equation. Once I turned off “From any screen”, the Bluetooth appears to be working normally.
Another possibility is that I had frozen S-Voice because it got in the way of the normal voice dialer. This has been restored. I also have to mention that the voice dialer appears to be more stable after disabling “From any screen” as well.
I also can’t say for sure, but it also seems to happen more frequently when charging. Although that may just be a coincidence as I normally do charge my phone when I connect it to Bluetooth. Also I have duplicated the issue when not charging and gotten it to work fine while on the charger. So it is probably just a coincidence.
Here is what I’m working with:
AT&T Galaxy S4 Active (SGH-i537) reflashed back to I537UCUCNE3 Android 4.4.2 stock firmware.
Jabra SP700 - Main device I’m testing with. Old Bluetooth 1.1 speakerphone that clips on a visor. Supports A2DP for an FM transmitter to stream music, but I have Media disabled on it. I tested with and without this setting and it made no difference. It worked great back when I was on MF3, but started having problems since I upgraded to ML2 that are easily replicated now on NE3.
Jabra BT620s - Secondary device that I tested with that also demonstrated the same problems. Although I haven’t tested as much as the SP700. This is a pair of stereo headphones that uses Bluetooth 1.2 and A2DP for streaming music. Also worked better with older firmwares, but I haven’t used it much lately save for testing this problem.
Installed/Updated Programs:
Facebook
Facebook Messenger
Google Authenticator
Google Chrome
Google Maps
Google Play Newsstand
Google Play Services
Google Play Store
Google Search
Google Voice
Google Hangouts
Jift
SuperSU
Titanium Backup
Titanium Backup PRO
towelroot
YouTube
Other apps that I updated and then I rolled back to get things working:
AllShareCase Dongle S/W Update
Amazon Kindle
ANT Radio Service
ANT+ Plugins Service
Antivirus & Security | Lookout
Beaming Service for Samsung
Beats Music
Blurb Checkout
Gmail
Google Drive
Google Play Books
Google Play Games
Google Play Movies
Google Text-to-Speech
Google+
GROUP PLAY
HP Print Service Plugin
Lux
myAT&T
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Samsung WatchON (Video)
Samsung WatchON (On TV)
YP - Yellow Pages local search
I also tested it quite a bit right before and after rooting it and it was working fine at the time, so I don’t believe that it’s related to root.
I would like to know if anyone else has encountered similar issues or can duplicate what I’m seeing?
Thanks!
After spending some more time testing it, I can verify that it IS in fact the “OK Google” hotword scanning from Google Search 3.6.14.1337016.arm. When it is set to detect “From any screen” and well as “From lock screen”, the audio will die after the first call over Bluetooth. Once I turned off “From any screen”, the Bluetooth works normally.
Now that I've finally found it and can easily replicate it, I'm still curious if other people can replicate it or if this is something isolated to my phone and/or Bluetooth devices. Would anyone be interested in testing this with me?
I'm planning on writing up some feedback on it once I have a better idea of how big an issue it is. I think it would also help anyone else that runs into this problem. I've been fighting with this off and on for over a month because it seemed so random.
Thanks.
I am having the exact same issue with the 2 s4's that I own. I suspected it was either svoice or Ok google, I will try to turn off the from any screen setting and see if it fixes the issue on mine as well. That is a shame because I really like using the ok google feature from any screen.
I've been having the same issue, but did not realize it was ok google from any screen. I've turned it off now, let's see if it works. Thanks for the heads up.
It looks like a recent Google Search update re-enabled the "From any screen" OK Google hotword detection setting. This still is not fixed and it killed all call audio while I was trying to lead another vehicle. I didn't find out until I parked that it was turned back on.
I have sent feedback to Google on the Search app and recommend that everyone else who has had this problem do the same. If this continues to happen, I will resort to negative reviews if I must. Please help get the word out if you are having the same issue. Thanks!
EDIT:
There are apparently several other people having the same problem on other Samsung devices (particularly Galaxy S4's):
https://productforums.google.com/forum/#!msg/websearch/mEhHyCs6F5o/HVArojlzIrAJ
http://forums.androidcentral.com/sa...-sound-phone-calls-after-using-bluetooth.html
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.