Related
I am using a handsfree Bluetooth in my car. It is not a high-end device, but it certainly did what it was meant to do with my former Bold 9700. Voice quality is good, it is easy to use.
With my S2 i777 I seem to have issues with it.
If I activate 'Driving Mode', I could hear the Driving Mode On through the BT speaker. If I press the DIAL button on the BT, I could hear the What Would You Like To Do command through the speaker, but only once. If I try it again nothing will come out from the BT speaker.
I then turn Driving Mode off and back on, but it won't help. I TAP & SPEAK on the phone itself, hoping to hear it through the BT - doesn't work.
So I don't think there is anything 'wrong' with the BT itself because it worked perfectly fine with the Bold and it works with the S2 for a minute or two. So what could be wrong? Is it possible that the S2's BT work only with specific devices?
I'd try with a second device. The fly-by-night-company handsfree kit I bought at Frys gave me all sorts of problems, but the Jabra unit I have works well with everything. Bluetooth is a finicky technology, especially in regard to the different implementation between stacks, and BT has been amazing on my i777.
EPC7 said:
I'd try with a second device. The fly-by-night-company handsfree kit I bought at Frys gave me all sorts of problems, but the Jabra unit I have works well with everything. Bluetooth is a finicky technology, especially in regard to the different implementation between stacks, and BT has been amazing on my i777.
Click to expand...
Click to collapse
Then the gods are looking down on you - my S2's bluetooth connection to my Jabra Cruzer2 is one glaring weakness with this phone. My connection drops and reconnect at seemingly random times - this is with the phone in my shirt pocket and about two feet from the Jabra.
Update
I realized something today and I am 99% confident that there is nothing wrong with the Bluetooth.
The Voice Command 'wakes up' when I turn the BT on. When I hit the DIAL button on my BT, nothing happens. If I press any of the Voice Command buttons it works fine (that is - "who would you like to call", or "Who would you like to text", etc.), and I can hear it loud and clear through the BT. However, when I speak to the BT nothing happens.
Furthermore, if I shut down the BT completely and want to use the Voice Command through the phone, I double-tap the HOME button, the VC comes up and asks me what do I want to do, but it still does not respond when I speak.
So it looks like something is wrong with the phone or with the ROM or with the Voice Command or what have you, but it's not the BT.
Any idea?
No one has any idea why Voice Command won't work?
I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?
Ok, I took the advice of using a 3rd Party App for Bluetooth Dialing from the Bug on Jelly Bean.
http://code.google.com/p/android/issues/detail?id=35199&q=bluetooth voice dial&colspec=ID
First I Tried EVA. Which was very nice but it would only work ONCE per boot. 2nd Time it would prompt on the handset when I clicked the Bluetooth button.
Then I tried Cyberon Voice Commander. This works perfectly. But I can't get the Default to Stick across reboots. Every time I reboot I get "Complete Action Using" list. It works PERFECT after that and does not require the Network and does confirmation. There is no trial you have to buy and you have 12 minutes to test it. I think we should start a petition against Google on that. You should have 24 hrs to evaluate.
If I uninstalled Google Search I can get it to Cyberon to Stick (because it's the only choice on Bluetooth and does not prompt at all). But if you do that you lose Voice initiated Navigation which I use all the time. Google Voice Dial also works fine on the handset.
Some folks suggested Slingo, but I hate trying yet another app.
I've tried suggestions of repairing headset I even tied a full wipe.
I'm on MeanBean 1.1 but I doubt that has anything to do with it.
One way to fix it is, I believe, there must be a way to take Bluetooth Voice Dial out of Google Searches "capabilities" manifest. So that Cyberon is the only app for Bluetooth.
It was actually Vlingo not Slingo that someone suggested.
It appears Dragon Speech Folks acquired them or something.
Any way Dragon Mobile Assistant (Beta) and is free
https://play.google.com/store/apps/details?id=com.nuance.balerion&hl=en
It so far is working excellent !!
Never mind Dragon is "Broken" over Bluetooth too.
It doesn't actually switch to the Headset MIC.
It has amazing recognition and still a very nice app.
But if the phone is in my pocket in the Car it's not gonna work which is what I'm trying to fix.
I covered the Mic's to test it over Bluetooth and got Nuttin.
Grrrr.
Back to Cyberon which is the closest to working.
Fixed and works
See http://forum.xda-developers.com/showthread.php?p=35954424#post35954424
Did you try AVX (Android Voice Xtreme)? Works very well....
mswlogo said:
Never mind Dragon is "Broken" over Bluetooth too.
It doesn't actually switch to the Headset MIC.
It has amazing recognition and still a very nice app.
But if the phone is in my pocket in the Car it's not gonna work which is what I'm trying to fix.
I covered the Mic's to test it over Bluetooth and got Nuttin.
Grrrr.
Back to Cyberon which is the closest to working.
Click to expand...
Click to collapse
lostsoul77 said:
Did you try AVX (Android Voice Xtreme)? Works very well....
Click to expand...
Click to collapse
Yes, are you using it on a Bluetooth Headset?
Quick question what is the issue? I am on MeanBean 1.3 and I have no issues with my bluetooth headset(s) or my car radio.
copc said:
Quick question what is the issue? I am on MeanBean 1.3 and I have no issues with my bluetooth headset(s) or my car radio.
Click to expand...
Click to collapse
Read the Google Bug in the OP.
Also read a post I made a few replies up to a work around to get Cyberon to work even better.
Bluetooth VOICE dial over headset cannot find contacts.
Cars do their own voice regonition to their own uploaded contacts.
Once a call is established the Bluetooth headset works fine. Or if a call comes in.
The Handset Voice Dial also works fine.
It's broken on all phones that are on 4.1.X JB. It's said to be fixed in 4.2.X
You can fool yourself into thinking that it works if say you only call your Favorites (because I think it prioritizes those).
It will also work if I Clear Caches for a few minutes. It's like it builds a bogus regonition cache for the headset.
If you only have a dozen contacts it might work.
I have 400 Contacts. It can find my wife every time, but not a single other contact works.
ICS Google Search worked fine.
There are almost 200 replies to the bug on Google all kinds of devices.
It was also broken on ICS ROMs that added Google Now from JB 4.1.
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Have you been able to use any other bluetooth device successfully? And have you checked the compatibility of that device with your phone? From what you're telling me, it seems very much like a bluetooth device compatibility problem, which is the same issue I had when I had a custom ROM flashed with my old HTC Rezound
nrkid9 said:
Have you been able to use any other bluetooth device successfully? And have you checked the compatibility of that device with your phone? From what you're telling me, it seems very much like a bluetooth device compatibility problem, which is the same issue I had when I had a custom ROM flashed with my old HTC Rezound
Click to expand...
Click to collapse
Absolutely not a bluetooth device incompatibility.
All bluetooth devices I have tested (3 different models total: 1 car stereo and 2 different earpieces) work just fine when NOT in CAR mode.
The HTC One (M7) treats a bluetooth button press the same as any other android phone when NOT in CAR mode.
It will bring up a different dialer which uses voice commands and this works fine.
Answering phone calls and dialing out via bluetooth work on both earpieces when not in CAR mode.
The car stereo also starts the voice dialer when NOT in CAR mode, same as the 2 earpieces that were tested.
ONLY CAR mode will start SPEAK when pressing the same bluetooth button.
However as I described above, You can successfully use all 3 bluetooth devices (audio is routed through all 3 devices' microphones and speakers) if you press the SPEAK icon in CAR mode.
Pressing the bluetooth button to start SPEAK causes the fail on all 3. Sounds like the SPEAK app to me but I/we won't know without more feedback.
Thanks for the suggestion but I have now successfully tested 3 different devices that can START and HANGUP and REDIAL calls but the same 3 fail when pressing the bluetooth button in CAR mode hence I am trying to verify if others experience the same results.
Do you have a bluetooth earpiece or car stereo with bluetooth to test yours with?
I sadly don't have a device that I can test with my phone at the moment. I will see if I can dig one up and test it on my own. Have you tried going to your carrier and resolving the issue with them? I'm sure they'll be happy to replace the phone if it's still under warranty (seeing as it just came out, it should be) and the issue is legitimate.
nrkid9 said:
I sadly don't have a device that I can test with my phone at the moment. I will see if I can dig one up and test it on my own. Have you tried going to your carrier and resolving the issue with them? I'm sure they'll be happy to replace the phone if it's still under warranty (seeing as it just came out, it should be) and the issue is legitimate.
Click to expand...
Click to collapse
Replacing a phone with a design flaw just gets me another phone with a design flaw. That is why we need to test it here and verify what results we all get.
I have the EXACT same problem using Bose 2 Bluetooth headset!
IIHomieII said:
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Click to expand...
Click to collapse
Voice dialing does not work on my T-mobile HTC one with my JVC stereo either. I have exactly the same symptoms you describe. My nexus one with CM 7.1 works perfectly and has for the last two years - so I know the issues I have are not related to my stereo.
Other things that work perfectly on my nexus one but are broken on the HTC one include:
AVRCP play / pause commands in music
AVRCP play / pause command in beyond pod
Wifi tethering
Notification light (HTC one light only flashes for five minutes, or not at all if connected to power)
Google voice (resets to T-mobile voicemail every few days)
Does not seem to get push notifications (have to wake the phone to check email, etc – presumably this is for power savings, but despite this nexus one has better battery life)
I think I am going to return the HTC one and wait for the next nexus device. The camera, speakers and screen are great on the HTC one, but every one of the above issues is a deal breaker for me (I use car mode / AVRCP a LOT). I’d consider cyanogen mod, but the lack of native camera support (optical image stabilization, low light performance, etc) due to no HTC camera driver source code / reliance on sense UI removes one of the biggest advantages this phone has over a nexus phone. I think I could stay with sense and root / hack a fix to all of the above problems except for voice commands in car mode (the original topic of this post) – I have no faith HTC will ever fix this. I tried using google search / voice commands as a replacement, but could not get that to work either. If anyone has a workaround for this issue please let me know, as that would be the difference between me keeping and retuning this phone. I have spent a month trying to like this phone, but it has too many software issues (above plus no recent apps button, menu overflow button). My nexus one just works – no need to research hacks on XDA to fix HTC and T-mobile limitations.
IIHomieII said:
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Click to expand...
Click to collapse
The Renovate ROM is fantastic you should really give it a try, the only thing that still does not work is the HTC speak app, but everything else you mentioned above I have not seen any problems with my mine.
They have updated the Renovate rom to 2.0 but I'm still running 1.0 with no issues at all.
I love the rom, the phone is fantastic except for the one issue with the voice dialer which eventually they will release an update for. You need to change the play/pause button when rooted to be the same key (key 200) if thats the problem.
I also set my forward track button to bring up Google search when long pressed, its great for driving to be able to long press a button on the stereo that I don't really use in that way already to do a Google voice search. I then use llama to return back to car dock mode after 20 seconds so that way I can get my results read to me from Google through the JVC so then it automatically goes back to car dock mode after long pressing the foward track key.
I can verify the same behavior. I came in looking for a MacGyver fix for the dock slipping and found this. When just connected to my headset no issues, but also add the car stereo in the mix and even with my headset I get the endless delay. I have always flashed my phones as soon as possible but with this I think I am going to wait and see what ROMS the senseless edition might bring that sounds imminent. Although I think I may be the only one who LIKES blinkfeed.
I like blinkfeed too.. I know some people complain about it, it's a sweet feature if you ask me but can't please all the people all the time..
I've now also an issue with my dock in that when I dock the phone it goes in to car mode, but then straight away opens up "Display Settings" even if i go "home", a few seconds later it opens it back up. Annoying, don't want to do a factory reset just yet.
Hi, I've got this issue too on my European HTC One with plantronic Discovery 975 headset
Hey All,
So, I've been searching all over for an answer to this, I've found a lot of information about S-Voice's problems being used over a bluetooth device but I haven't been able to find any direct discussion of the issue I'm experiencing.
What I've found is that when I have S-Voice's voice wake-up feature enabled, it'll work totally fine with bluetooth off. However, as soon as I toggle bluetooth on the wake-up feature just completely stops working. I don't even need to be connected to a device, as long as bluetooth is on S-Voice Wake-Up does not work. I can manually launch S-Voice and it will hear me just fine, but saying the wake-up command does nothing. As soon as I toggle bluetooth back off, it'll wake up again just fine. I do get that with a bluetooth device connected the microphone on the device needs to be active, so I could understand if this was happening while I was paired with a headset or something, but it seems really odd to me that just having bluetooth on at all would disable the wake-up command feature.
I did try Ok Google and found that it works whether bluetooth is on or off, but I really like the increased functionality that S-Voice offers and I think that for the most part the updates Samsung has done on it are great, so I'd like to get this working if possible.
Has anyone else experienced this, either on the Note 4 or on any of the other Galaxy devices? Anyone have any ideas or solutions?
Thanks!
I'm having the same issue with svoice, thought it was just the bluetooth in the car at first til I red your post
Widespread
I've got exactly the same problem.... Lovely new note 4 which is forcing me to use my hands on the phone whilst driving... Samsung need to think about this.
Apparently an issue for a few years due to Bluetooth /svoice conflicts, but not acceptable to leave it unaddressed.
I can still use my car system to skip music tracks on the phone, or dial numbers from the car stereo touch screen, but surely this is one of the most valuable areas for voice control?!
Bluetooth off then everything works fine, but Bluetooth on and svoice just fails. No wake up or voice recognition.
I don't use a headset, and the car doesn't have an inbuilt mic, so phone mic is used for calls (which is still fine incidentally.. Only svoice which is screwed.)
Looking forward to someone finding a simple solution to this, as I have spent hours in the menus trying to make a difference but Samsung might have just let us down I'm afraid... And if that's the case then I look forward to hearing them fix it, and update our ware to get everyone on track again.
Resolved and simple
After much fckin about I managed to get this sorted and the answer is simple..... You can't have both apps always trying to recognise the voice all the time.
Go to the settings for ok Google and voice detection then always on... Uncheck it and suddenly svoice is working again... On my way to the car for final checking now,but preliminary checking says all should be good.
Nope
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
When driving, set to hands free mode, this allows use of svoice on bluetooth
Ooof said:
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
Click to expand...
Click to collapse
Note 4 and above have it listed as car mode.
svoice works perfectly with blue tooth when car mode is enabled.
Set it up at home before you use it the first time.