Anyone else notice that the new S voice app won't respond to voice commands when the screen lock is on?
This wasn't the case on the Note 1.
With this new behavior, I can't initiate calls using earphones hands free.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Bump
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Slight clarification: it's actually not the screen lock that prevents the S voice app from activating, rather it's the display shutting off. If I press the power key while the screen is locked to turn on the display, the S voice app works fine.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
stuartr said:
Slight clarification: it's actually not the screen lock that prevents the S voice app from activating, rather it's the display shutting off. If I press the power key while the screen is locked to turn on the display, the S voice app works fine.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I noticed that on my lock screen, when I have pushed the home or power button to light it up, I get the "Voice Not Recognized" message, even though I tell it to wake up ("unlock phone") or even launch the camera ("open camera") If I have it set to respond accordingly to those voice commands, why doesn't it? At the moment I have battery indicator pro app which just disables the lockscreen altogether so it is a non-issue at the moment, but I really would like to get the voice unlock thingie to work as it should.
Related
Okay so on my phone I use the pattern lock and on the lock screen it has emergancy number which is 911. I ride bikes so when its in my pocket my phone turns on and starts calling 911 by accident. Also when I put on the swipe lock it doesn't have it but when its in my pocket it turns on and gets passed the lock screen to home screen and won't turn off draining my battery. Is there any way I can change the emergency number so it stops calling 911 or a better option? I don't want to use a different lock screen like go locker. Thanks
Sent from my SGH-I927 using xda app-developers app
ItsMeBdon said:
Okay so on my phone I use the pattern lock and on the lock screen it has emergancy number which is 911. I ride bikes so when its in my pocket my phone turns on and starts calling 911 by accident. Also when I put on the swipe lock it doesn't have it but when its in my pocket it turns on and gets passed the lock screen to home screen and won't turn off draining my battery. Is there any way I can change the emergency number so it stops calling 911 or a better option? I don't want to use a different lock screen like go locker. Thanks
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
try face unlock?
It still has the emergency call button. :/
Sent from my SGH-I927 using xda app-developers app
ItsMeBdon said:
It still has the emergency call button. :/
Click to expand...
Click to collapse
Get a case?
Lol i almost do the same thing everytime!
Sent from my SGH-I927 using xda premium
Its dumb haha
Sent from my SGH-I927 using xda app-developers app
How about get the screen to face away from your leg? It never calls for me.
Sent from my SGH-I927 using xda app-developers app
Because when I do tricks my bars sometimes hit my leg and I don't want to crack the screen.
Sent from my SGH-I927 using xda app-developers app
ItsMeBdon said:
Because when I do tricks my bars sometimes hit my leg and I don't want to crack the screen.
Click to expand...
Click to collapse
In that case I'd go with a belt phone holder. Another option is a sock for the phone - it will add more material between your leg and the phone, preventing accidental screen touches.
Not google voice the actual voice commands like answering or rejecting a phonecall. It was in language and input on ics but I dont see it on Jellybean
Sent from my SPH-L710 using xda app-developers app
Double tap the home button to open s-voice, then go to settings of s-voice. Then go to control apps. I believe that is what your looking for.
Sent from my SPH-L710 using xda app-developers app
Edit: control apps, not voice controls in s-voice settings...
You have to have vibrate turned off too, which makes it a no go for me.
Jimmy50941 said:
Double tap the home button to open s-voice, then go to settings of s-voice. Then go to control apps. I believe that is what your looking for.
Sent from my SPH-L710 using xda app-developers app
Edit: control apps, not voice controls in s-voice settings...
Click to expand...
Click to collapse
Thanks I found it.
Very annoying that text pops up telling you that you can use voice commands within camera, alarm, when a call comes through etc.
BWFBezerk said:
You have to have vibrate turned off too, which makes it a no go for me.
Click to expand...
Click to collapse
I brought this up a while back when the s3 came out.. There has to be a way to modify it to work also when on vibrate.
I keep my phone on vibrate around 80% of the time so I can never use them either.
But I have found out that the voice commands still work on camera even with vibrate on, which leads me to believe it can be enabled on the other commands some how ... I don't know how to program and all that but I would be willing to help in anyway to get it working on vibrate mode
Sent from my SPH-L710 using xda premium
the new update of google search allows voice commands to open apps
My voice commands work with vib. On music plays and stops just fine
sent from my super space phone
Dont know what else to call it really but I know this is happening with all of our devices.. which is when the screen times out and u press home to wake it up it takes u back to default homescreen. The sgs3 doesnt react that way and ive had to get used to hitting the power button instead. Any ideas? This would be amazing and greatfully appreciated.
Sent from my SGH-T889 using xda app-developers app
I can't replicate this issue. I let my screen timeout and pressed the home button and it simply turned the screen back on to where I left it.
Sent from my SGH-T889 using xda premium
I've had it happen. You press he home button immediately after the screen goes black, and it wakes the screen up, but also takes out of what ever you are in and takes you to the home page. I've retrained myself not to go for the home button, but the power button.
stevessvt said:
I've had it happen. You press he home button immediately after the screen goes black, and it wakes the screen up, but also takes out of what ever you are in and takes you to the home page. I've retrained myself not to go for the home button, but the power button.
Click to expand...
Click to collapse
I've seen this behavior too. It's quite annoying.
Sent from my SGH-T889 using Tapatalk 2
j_shelton1988 said:
I can't replicate this issue. I let my screen timeout and pressed the home button and it simply turned the screen back on to where I left it.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
What firmware are you on.. no matter what rom im on if the screen times out it takes me back out of wher is was.
Sent from my SGH-T889 using xda app-developers app
pezlomd said:
What firmware are you on.. no matter what rom im on if the screen times out it takes me back out of wher is was.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Stock rooted. I tried it multiple times and the same thing happens, screen times out, I instantly press the home button and it turns the screen back on but keeps me on the web page, app, etc that I'm using.
Sent from my SGH-T889 using xda premium
No matter what I do wipes roms etc I have this problem..wtf
Sent from my SGH-T889 using xda app-developers app
This is really an issue, "immediately" hitting the home button when it goes to sleep? Why not just avoid letting it go to sleep or hit the power button? This seems like a non issue to me and I've never had it happen.
but my post does not help the OP so good luck with that, sorry for the editorial.
The point is my sgs2 gti9100, and sgs3 tmobile which both had physical buttons didnt react this way.. I find it to be strange.
Sent from my SGH-T889 using xda app-developers app
pezlomd said:
The point is my sgs2 gti9100, and sgs3 tmobile which both had physical buttons didnt react this way.. I find it to be strange.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Are you using stock LEAK ?
I think this is a Jellybean 4.1 issue. My Note 2 has the same problem, but my wife's Galaxy S3 didn't when she was on ICS. Last week the phone updated to JB and now the problem exists.
This is definitely related to Jelly bean but I'm not sure if it is strictly a Touchwiz Jelly bean issue. It happens when I removed S Voice from the home button double press. It happens on the S3 and when my Note II comes in I bet it will happen on there too.
There are a lot of people that noticed it and I even saw someone open an issue with Google, although I'm not sure it is entirely a Google issue.
http://code.google.com/p/android/issues/detail?id=39326
The last line is the issue maybe.
"I want the single tap to be more snappy - for that I must disable s voice, but when I do it this bug raises its head. "
Do you guys have s voice disabled on the home button to save that lag time?
I disabled the s voice on the home button but still have the lag.
Sent from my SGH-T889 using xda app-developers app
Hello, can someone confirm this...? Make sure volumes are all the way up, and simply hold down power button till you get the menu to pop... Do you receive the sound you get when you receive notifications? It's weird because I never ever noticed it before and I'm new to nexus... I just want to know if it's glitching or if it's supposed to do that.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Don't worry.
ahura999 said:
Hello, can someone confirm this...? Make sure volumes are all the way up, and simply hold down power button till you get the menu to pop... Do you receive the sound you get when you receive notifications? It's weird because I never ever noticed it before and I'm new to nexus... I just want to know if it's glitching or if it's supposed to do that.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The pop with your volume up, defending on your notification audio, may just be your Nexus 7 trying to play audio thats slightly frequencies than your speaker is intended to play. It also could be a few other things with the speakers (Volumes too loud with that notification, maybe?), it isn't just the power button and you shouldn't have to worry.
No... It's because I enabled the accessibility shortcut. Thanks anyway haha
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Why when I press dial the screen turns off right away? The screen should only turn off when I put it next to my ear. It's very annoying when I'm dialing automated systems and need to use the keypad because if I manually turn the screen back on and then put it next to my ear to talk the screen doesn't turn off and I end up accidentally pushing buttons.
On an iphone the screen remains on and only turns of when put next to my ear, and turns right back on when pulled away from an ear. Is there a way to duplicate this behavior on GS4?
Go to settings/My device/call settings and select turn off screen during calls. That should do it.
Sent from my SGH-M919 using xda app-developers app
Thanks, the screen doesn't turn off anymore but it also stays on when I put it next to my ear... I don't get why Samsung can't get a basic function like that right.
Sent from my SGH-M919 using xda app-developers app
re: proximity sensor
ilogik said:
Why when I press dial the screen turns off right away? The screen should only turn off when I put it next to my ear. It's very annoying when I'm dialing automated systems and need to use the keypad because if I manually turn the screen back on and then put it next to my ear to talk the screen doesn't turn off and I end up accidentally pushing buttons.
On an iphone the screen remains on and only turns of when put next to my ear, and turns right back on when pulled away from an ear. Is there a way to duplicate this behavior on GS4?
Click to expand...
Click to collapse
In your original post you forgot to let us know what exact rom you are using.
It would be very helpful to know that and other specifics before offering any suggestions.
Good luck!
Well, I tried this on a stock rom with the same result. Are you saying it works for you?
Sent from my SGH-M919 using xda app-developers app
ilogik said:
Why when I press dial the screen turns off right away? The screen should only turn off when I put it next to my ear. It's very annoying when I'm dialing automated systems and need to use the keypad because if I manually turn the screen back on and then put it next to my ear to talk the screen doesn't turn off and I end up accidentally pushing buttons.
On an iphone the screen remains on and only turns of when put next to my ear, and turns right back on when pulled away from an ear. Is there a way to duplicate this behavior on GS4?
Click to expand...
Click to collapse
Download an app from the android market (its free) called AndroSensor and see if that app is saying the proximity sensor is blocked. You might have a spec of dirt causing it to always return that its blocked. Read other threads with same issue, and in the one thread, the guy at T-Mobile took a can of compressed air and blasted out the earpiece and it fixed it.
I downloaded the app and proximity sensor does not show any reading all the other functions have a graph next to them but not the sensor. Does this mean it's broken? And if it is broken does tmobile exchange the phone or do I have to send it back to Samsung?
Sent from my SGH-M919 using xda app-developers app
ilogik said:
I downloaded the app and proximity sensor does not show any reading all the other functions have a graph next to them but not the sensor. Does this mean it's broken? And if it is broken does tmobile exchange the phone or do I have to send it back to Samsung?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Screenshot? Mine says "waiting for event" then after I put my hand over the sensor it changed it's value (but stayed on 0.0) something is wrong with my sensor obviously lol
Sent from my SGH-M919 using Tapatalk
No values change no matter what I try.
Sent from my SGH-M919 using xda app-developers app
ilogik said:
View attachment 2482455
No values change no matter what I try.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
It's definitely a hardware issue which should be covered. You just gotta make sure you get it back to stock and reset your counter with triangle away.
Sent from my SGH-M919 using xda app-developers app
ilogik said:
View attachment 2482455
No values change no matter what I try.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Agreed. Definitely hardware. Your sensor is reporting that the sensor is never covered and always open. Use that app and a test call to show the Rep at T-Mobile.
Sent from my SGH-M919 using Tapatalk
Went to t mobile store, flirted with the chick and she overnighted a new phone without even looking at mine...
Sent from my SGH-M919 using xda app-developers app