I've recently been having a play with the Voice Tag function on my Wizard. I can call any of my contacts by voice, and I can perform a plethora of functions on my phone by voice (helped by the added hardware button functions that Pocket+ provides). Now i'm wondering if I can do even MORE by voice, i.e. a spoken password, dialing by saying each number, that kind of thing?
Yeah,
Dump the cheezy Cyberon Voice Dial and get Microsoft Voice Command or Cyberon Voice Commander.
Both allow you to access PDA functions such as launch programs, access calander etc.
Additionally they allow "Dial 444 555-1234"
In my opinion MS Voice Command is better.
I've played with Cyberon Voice Commander because it will read e-mail and text messages but I've found it to be useless. Also Cyberon has too much of a delay from activation to ready for voice input for my tastes.
Oh yeah, neither of these requires "Voice Tags", they work by recgonizing your spoken voice!
Cyberon Voice Commander costs about $20,
MS Voice Command is about $40.
Both can be purchased at Handango.com
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Danny-B- said:
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Click to expand...
Click to collapse
Maybe that's why none of these products supports it!!
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
jimmyhauser said:
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
Click to expand...
Click to collapse
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Same for me. Sometimes the recgonition isn't the same over bluetooth, but I never have to try more than twice. I use my VC for everything.
jimmyhauser said:
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
Click to expand...
Click to collapse
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
VC Usage Vs. VS VC Memory Usage
I've had VC on and off of my 8125 since I bought it in April.
The main problem I have with MSVC is whether its use (or lack there of) validates the amount of memory it uses.
For someone that makes calls primarily off of his recent call list, I find that the usability benefit does not outweigh the memory usage.
Wish there was a way to disable / enable the functionality, as to release that memory for other applications.
JNGold said:
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
Click to expand...
Click to collapse
Believe me, I am not an expert on this, I am just trying to figure things logically. But I would bet it has to do with the fact that you are probably using a different bluetooth handsfree device than I am. Maybe that was what you were referring to when you said it was a bluetooth issue. Or maybe it is the fact that you have a different model of phone.
What I am saying is that it cant be the bluetooth software on my phone, because the cyberon voice dial works fine over bluetooth, where the MS voice command does not.
And I have voice command on the phone also. All my programs are. I only keep music and videos on the storage card.
And voice command works great when using on the phone itself. I am amazed at how well and how quickly the recognition works. It just doesnt respond well to my Nokia car kit. And maybe that is the problem.
My wife's car has the same bluetooth kit as my car, I am going to try it in her car one of these days to see if I have the same problems there. She has a Nokia 6682, and her bluetooth voice dialling works great.
And also, does VC really use that much memory? If so, I think may take it off the phone. (I use it a little when not in the car) But if it is considerable, then I agree that it is not worth it.
the problem is that without any BT headset i can't get the microsoft voice command to work.
i installed it, dedicate the button. the problem is that when i press it the mic sign appers, i hear the bip and if i say "HELP " it does absolutly nothing.
NOTHING
it just stands there, then another bip comes and the mic sign disappears .
what should i do?
did you turn your mic auto-gain off like the instructions said?
problem solved.
don't know how ...soft reset and bam ! it worked.
the problem is that it hardly recognizes 0 ( zero )
well...i think the old voice dial would do the trick for me...
Keys to success:
1. Load in main memory. (Yes, it's a hog, but to me it's worth it.)
2. Be patient. Sometimes it takes a moment or two to activate.
3. Make sure your volume is not muted. (I admit it, I often walk out of a meeting and get frustrated with why it isn't working... oh, volume is off.)
4. Experiment. Watch the phone while you are playing.
Here are my results with Motorla hs850 .
1. Usually I push once to open the gateway and a second time to activate VC. (Note, I only wear my headset when I need it.)
2. Sometimes the gateway is open for whatever reason and I'll get an immediate bong. So after the first press, I give it a second to see if it will come up.
3. Otherwise, I may get into three presses. One which I think is opening the gateway but is actually opening VC before the bong sounds. A second which I think is activating VC but apparently is closing it. The third press usually then does the trick, but sometimes I'll even have to go to number 4.
So my strategy is:
1. Push button.
2. Wait a slow count for response.
3. Go back to #1 until success is achieved.
Related
Are they compatible?
I've changed the registry to use the voicecmd.exe file instead of the inbuilt Voice Dialer (which I must admit, I never tested with the Jabra!)
But when I press the Jabra button, I hear a noise in my ear but it doesn't seem to activate anything on the MDA Pro itself...
What am I doing wrong?
Have you got the lid closed? If the screen is closed it doesn't work.
This is mad.
If I press the button on my Jabra, I now hear that the voice path is activated but saying "help" into the Jabra mike doesn't do anything. No "mike" icon on the device (lid is open) and nothing happens.
However, with this voice path open, if I then press the voice command button on the device, everything works through BT. I hear the woman and can speak to her.
However, pressing buttons on each device seems a very silly way of doing it.
I should be able to press JUST the headset button, right?
I use the same hardware without issue
I find some commands dont work so well over bluetooth - but call seems to work OK!
I find the built-in mike is better to practice with first THEN try with the headset
I use DIAL <name> at HOME or on mobile etc and this seems OK
My only ***** is than on both BT and the device the VC voice is too low!!
While I remember to 200 Headset supports two profiles - I find the basic one works better with VC (that way you dont accidentally redial if you double tap the button!)
Found the problem. I reinstalled the VC software with no joy, so checked the reg entry. I was missing the space between "Voice" and "Command", so no wonder it wasn't working...
I would have expected an error of some kind instead, maybe... but at least it is solved now.
I have a Cingular 8125 (2.17 ROM, I believe) and recently got a Motorola HS850 BT headset. It's setup and works great, but I want to know if there is a way to reprogram the call button on the headset so that when you hit it instead of opening the Voice Dial on the phone it can instead open Voice Command (which I use for everything else.) I tried poking around on the boards and didn't see anything specific, any help (or just knowing it's not possible) would be greatly appreciated!
Thanks!
Doug
Found it
I found the answer with a little more searching. It turns out to be a registry entry for Voice Command - and it DOES work with Bluetooth (even though MS' description says it does not.)
Just change this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path
change the value from \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Soft reset the phone and voice command will work when you hit the connect button on your phone.
Credit to HowardForums where I found it: http://wiki.howardforums.com/pocket...ice_Command_via_Bluetooth_(HTC_WM5.0_Devices)
I heard that it does not close the audio gateway however when you are done with the call...
is this true?
thanks a lot man, this was buggin the hell out of me! quick forum search and i found ur post. thx for doing the leg work
I placed a call with it and when the call was done used the button on the headset to terminate the call...it seemed to work okay.
i just tried it and it seemed to work just fine. the only thing i don't like, and it probably has to do with my headset, is how long i have to hold down the button for...but i can deal with that, so that i don't have to take out the phone!
I guess that the issue is with the regular voice dialer, you can just press the button to dial out, and when the caller hangs up, the audio gateway closes, you dont have to hit the button to close it.
I'm gonna give this a shot to see if I like it.
I did notice that it seems like I have to hit the call key twice in order for it to recognize the key press....maybe the first is to close the old channel and the second opens a new one? I don't have enough knowledge to say for sure, but there is no visual indication on the phone that the voice channel has not been closed.
That's probably what's happening. If you forget to close the voice channel after your call, you'll run down your headset's battery faster. I can tell that the channel is open because I can hear very faint hissing.
Of course, the point is moot for me because on my device (like many others) this trick only works until a call has been placed and ended. After that the button no longer triggers voice command. :-|
Anyone here use VC1.6 with Bluetooth?
Has anyone else noticed that the confirmations don't work?
I've seen threads on other forums about this, but no solution yet over there.
Figured I'd bring it up in case folks here have the answers.
Basically, here's my conversation:
Press BT button
Device: *Beep*
Me: "Call John"
Device: "Call John?"
Me: "Yes"
Device: *Timemout Beep*
Now, the confirmation works when used on the device just fine.
When on the headset, its like it gives up without trying to hear me.
MS Voice Command v 1.6 works almost perfectly on my Sprint Mogul. It has one flaw - when the button you map is first pushed it does not give off the beep, but the small microphone on the top bar shows up. When the little mike shows up, you can say your commands and it works perfectly.
The next time the button is pushed, the beep is heard and the mike shows up.
Also, VC is activated by my Motorola S9 stereo BT headset. If I push the right button on the headset, I hear the beep and can give the command into my headset even if the headset is in my backpack.
The failure to beep on the first button push is a small problem I'm sure can be worked out. For me it is no problem at all. I just push the button and begin speaking.
I own many other HTC products and VC works as well on the Mogul if not better than any of them and I haven't even hacked it yet.
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
ImCoKeMaN said:
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
Click to expand...
Click to collapse
Yeah, this makes browsing media impossible!
I used to say "Play music" wait until it asks me what type to sort by "Artist"... wait again "Dream Theater"... and then the music would start.
Now, I can't get past the first prompt because the mic is shut off. Very weird indeed...
Voice Command 1.6
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Traumtanzer said:
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Click to expand...
Click to collapse
Scratch that, I wasn't able to duplicate this, so seems to be a random occurrence, I know that every once in a while it does seem to work correctly, but that's very rarely.
List of Voice Commands
Has anyone got a list of voice commands, and is there any way to add new commands?
My VC 1.6 bluetooth problem is even more frustrating. It always recognizes my contacts, but the confirmation doesn't work AND I CAN'T DISABLE IT!
I uncheck the confirm box on the VC settings, but it still tries to confirm.
Is there something I'm missing?
Sprint does it again
WM6 has voice command built-in, but Sprint decided to disable it and not make it part of the ROM, so when you install 1.6 over the already there application, is when you lose part of the functionality.
Ha! I found my voice command problem -- I had a duplicate contact.
What voice command said (even after I turned off confirmation) was "Joe Blough at Home 3 found" and then it displayed one of them. When I removed the duplicate and turned off confirmation -- IT WORKED!
Now, if they would just fix the confirmation to work properly...
Ok.....my problem is it will not announce incoming calls, no matter what i do...everything else seems to work fine, but it will not announce incoming calls threw the bluetooth nor speaker, am i missing something???
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
TC1 said:
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
Click to expand...
Click to collapse
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Is there an echo in here? What part of "needs to be updated to work 100% with WM6" didn't you understand?
I was saying it isn't buggy as you said, it works great for the OS it is intended to be used on.
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Shaska said:
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Click to expand...
Click to collapse
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Dishe said:
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Click to expand...
Click to collapse
And also doesn't always confirm commands. At least from my experience.
primenall said:
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Click to expand...
Click to collapse
I have the Alltel 6800 with WM5 and am experiencing the same problems as you WM6 folks.
It seems to be an issue with the Mogul/MSVC combo like you said, also a friend of mine put the WM6 Rom on his 6700 and he says MSVC confirmation works fine.
Maybe a Radio incompatability, I'm just a novice though?
Looks like I'm having another strange "quirk" of my Xperia.
For some reason my ringtone goesu p and down when it rings.
It starts loud for about half a second then goes quiet, then after a second or two goes loud again, then quiet and so on, so forth.
Anybody got any ideas why it does this? The damn thing is too quiet as it is let alone with the volume wobbling up and down all over the place.
I'm using an mp3 that I trimmed with mp3 trimmer, the mp3 volume is normal, i have tried it on PC and bluetoothed it to several other phones.
Of note, after a hard reset it worked normal for a little while, but then started doing this again.
A friend suggested it might be a feature of "something" i have installed so you can tell the difference between the ringer and your music that's playing.
I just find it annoying and would like to fix it.
Any suggestions, ideas welcome. Thanks.
P.S. It happens with other ringtones already on the device also.
If you have installed Microsoft Voice Commander, uninstall it.
I had the same problem, after uninstalling Microsoft Voice Commander its working fine.
I have the same problem, but I kind of like how it varies.
Correct
You are correct, I do have voice command installed. I wonder why the voice command would be made to change the ringer volume though, it's not like it's to prevent the system thinking the music is a voice command, because a key has to be pressed first, in which case the music would pause.
My only other idea is that (like nokias etc) the part where the volume decreases, the system (voice command software) is supposed to "read" the contact name out loud to you. (but it doesn't).
so if you uninstall microsoft voice command, does it mean the phone will not have the feature for VOICE DIALING?
cause i use microsoft voice command in order to make phone call while im plugged into my wired headset
alias_neo said:
My only other idea is that (like nokias etc) the part where the volume decreases, the system (voice command software) is supposed to "read" the contact name out loud to you. (but it doesn't).
Click to expand...
Click to collapse
Yup - go to Settings and MS Voice Command, select Phone, Options and untick "Announce incoming calls".
Thank You, i was terribly worried
I guess there is enough software around, that provides you the feature of voice dialing. I for instance use VITO Voice Dialer.
Hi guys,
I have been trying to find answers for this problem ever since i bought my Galaxy S2..but no luck so far.
The problem is trying to voice dial someone while the phone is paired with a bluetooth headset and on standby/screen locked mode. In other words i want to be able to voice dial someone when my galaxy is in the pocket instead of having to unlock the screen and go for voice dial and then say command which negates the whole point of having voice dial.
So far when i press the bluetooth's button, the phone goes - "what would you like to do" and then i try saying ''call (person)" but the phone seems to be doing nothing after that..but when the screen is unlocked and i do the same thing, it actually does dial(no point because if i am able to take the phone out and unlock it, i might as well dial it instead of voice). What really hits me is that the bluetooth actually does trigger the voice talk application and the phone requests me to say what i want to do but after that nothing happens.
Can you guys tell me whats going on? This problem is really making me hate this phone because the phone boasts so many ads about voice dialling but it cannot do a simple voice dial which is possible on ancient phones. Cheers
I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.
BarryH_GEG said:
I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.
Click to expand...
Click to collapse
Thanks for this detailed reply. I think at some point I have tried these settings but not sure if they were in the exact matching order. I will give it another go with everything set up to the way you have mentioned and see what I get. I am sure I am very close to actually getting it to work though..fingers crossed ..and yes if anyone else have different combinations of settings or ways they got it to actually work from a locked screen, please share it here. Thanks.
BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.
vijith555 said:
BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.
Click to expand...
Click to collapse
If you do what I suggested you don't have to push the command button. The phone will be listening for the "hi galaxy" command all the time.
Sent from my GT-I9100 using XDA Premium App
I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away
connectsys said:
I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away
Click to expand...
Click to collapse
I was thinking of trying this next as I have run out of options..so you say it worked? Then I will get widget locker and see how I go. So let me get this straight - i get widget locker and use the lock screen that comes with that or using widget locker i disable the stock lock? Or I should disable the stock lock from settings and then use widget locker? Cheers
yea disable stock lock in settings and then use widget locker only for lockscreen
connectsys said:
yea disable stock lock in settings and then use widget locker only for lockscreen
Click to expand...
Click to collapse
Tried this last night and unfortunately its still doing the same thing. On holding the bluetooth headset's button while the phone's screen is off I can hear the phone go "what would you like to do" and right after this i say commands like "call (someone)" but nothing happens. When the phone's screen is on, it actually works when i do the same thing which just surprises me to as why. Also when the screen is off and voice talk not on the front screen the wake up command doesnt work. So again a person has to leave his screen on (without letting the phone go to standby) and leave the voice talk app running for voice dial to work.
And to make things worse the double tapping with motion turned on settings doesnt bring up voice talk when the screen is off..again putting me in the same situation. The only way voice talk work on this phone is when the screen is on so far which isnt really practical in situations you would want to use voice commands..i hope samsung or google brings a better solution to this issue because this phone's got so much boasting about being able to voice command but isnt able to perform what an iphone or old nokia do
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
I cant agree more about it being counter-intuitive..and yes its not nice the voice prompts coming through the phone but i remember once somehow the voice prompts did come through the bluetooth headset i dont know how. Like you said something is not letting it operate properly, like blocking it. I havent used this Tasker but have used task manager like apps in the past. So you believe you could try to figure out a fix for this..i appreciate your efforts because I am just lost at the moment. Let me know how you go mate. And I will let you know if I get around this issue too. Thanks mate
k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
Ok i found a way to get this voice dialling to work when the screen is off but not using a bluetooth headset, instead the wired headset for the time being.
So I can trigger voice dial when the phone is in the pocket and voice prompt comes to the headset, i say command and it works . I dont mind it working for the wired headset as that is good enough for the time being while driving. If you need to know how i got this done just give me a buzz. There are two pieces of software that I got to set this up. Cheers.
I just deleted built in vlingo crap and took generic Google voice dialer apk from my nexus s. Plus side you don't have to be connected to net to dial contacts and I can hear reply in headset as well.
Sent from my GT-I9100