Database Develop

[Q]Anyone having delay issues with twisting your wrist?

Sometime I twist my wrist to view the watch and the screen doesn't turn on..so I have to twist my wrist a second time for the watch to react.

yes twisting isn t very good. sometime yes sometimes no

daigoro76 said:
yes twisting isn t very good. sometime yes sometimes no
Click to expand...
Click to collapse
Damn and I love this watch.

I had same problem with my ex galaxy gear. I thinks it concern all smartwatch

daigoro76 said:
I had same problem with my ex galaxy gear. I thinks it concern all smartwatch
Click to expand...
Click to collapse
My G watch doesn't have those issues. LG G watch R problems: http://youtu.be/24USeBUjlVk

Mine is worst :crying: waiting a lg Update or asking a new watch ?

I want to turn it off completely, dont see the point of it if im running screen always on. Damn thing turns on every time i move.

jrvenge said:
I want to turn it off completely, dont see the point of it if im running screen always on. Damn thing turns on every time i move.
Click to expand...
Click to collapse
same here, it keeps turning on everytime i move my hand, and then sometimes when i want it to turn on it doesn't. I wish i could just deactivate this and use the power button / tap the screen

The answer to this problem is simple. When turning your wrist, simply flick it down with a quick rotation toward yourself and the screen will activate every time. There is nothing wrong with the accelerometer. It is just set to not turn on from random movement.
The wrist flick toward you and down is the key.

Funny mine turns on every time I even move my arm

I returned my first one and the second one is MUCH better.

i would prefer an option to calibrate this behaviour or even disable it^^
It's okay to me to tap on the screen for activating

[Q] Ok Google Voice Command doesn't work when Device is Locked

Hi everyone,
I got a new Moto X (2014) recently (through the Motorola Cyber Monday deal). It's really a great phone.
I have one small question: The "OK Google" voice command doesn't seem to work from the lock screen (yes, the option is enabled in settings and yes, I've 'trained' it to recognize my voice). It works fine when the screen is unlocked. Initially I thought it was because Moto Voice was activated and I tried deactivating/turning off Moto Voice (both in accessibility as well as in the 'Moto' app settings). Still I can't get the phone to respond to the "OK Google" command when screen is locked. Am I missing something somewhere?
PS., I have tried using Moto Voice and it works too (I tried with one of the suggested phrase, "OK Moto X"). But for some reason, it doesn't recognize properly and if I say, for example, "Call Mom", it opens up a contact whose name has "Mohan" in it (Google opens my mom' contact details perfectly every time).
Thanks.

I can't test it right now, but if I remember correctly, the default command is "OK Google Now," not "OK Google."

Thanks,
It works with "OK Google" once the screen is unlocked and I'm on the home screen (or any of the home screens). and not when the screen is locked.
Edit: Funny (and weird). I tried with "OK Google Now" few times and then went back to repeating "OK Google" and it's now recognizing the command from the lock screen. As mentioned in the initial post, Moto Voice is inactivated (both under settings > accessibility and the Moto app).

Well, it's stopped working again this morning (after working for a while last night). The voice command "OK Google" doesn't do anything when the screen is locked (yes, the option "when locked" in 'voice settings' is turned on).
Though, the Moto Voice command that I set up works when the screen is locked. It's just the "OK Google" command which isn't working properly.
Any ideas on how to fix this? Thanks.
PS., I can use Moto Voice instead but as I said, for some reason it's not recognizing my voice / accent as well as Google does. Google voice gives an almost 100% perfect voice recognition.

I believe the "locked" is in reference to the "lock screen", not screen off "locked". Definitely diminishes its functionality, though...

Yeah, they mean the screen is on but locked, not that the phone is locked.

"Locked" meaning when the screen is locked or screen is turned off. There is an option in Google Now voice settings to enable the device respond to the "OK Google" command even when the screen is turned off or locked (precise wording - "Allow OK google to start a voice search or action from a secure lock screen").
Does that mean when the screen is 'locked' with either a PIN or pattern (and not just swipe)? I have tried "OK Google" both with just a 'swipe' setting or a 'PIN' lock setting. Doesn't work in either case (it did work for a short while though, last night, when I had the screen lock set to just 'swipe').
Edit: Thanks, @chrisrozon . So it doesn't work when the phone is 'locked'? Does the screen have to be turned on? Meaning, even if it's locked, does the lock screen have to show up before having it respond to the "OK Google" command?
When I tried (and when it worked intermittently) last night, I was able to see the device respond to "OK Google" from when the screen was locked and when the screen was turned off.

Alright. I checked again and it works when the screen is locked but the lock screen is on. Does it make sense? I mean, when the screen is locked and then I activate the display so that the lock screen shows up, then the "OK Google" command works.
This kind of defeats the purpose of 'works even when the screen is locked', isn't it? Or is this a known issue?
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.

That's how it is supposed to work, the screen needs to be on.

fonduekid said:
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.
Click to expand...
Click to collapse
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.

Were you plugged in? Because it always works when you are plugged in.

Well, looks like that's how it works - screen needs to be turned on. For sure I am not doing a factory reset for this!

bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
I haven't checked when it's plugged in. I'll do that later this evening and get back. Thanks.

dazz87 said:
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.
Click to expand...
Click to collapse
I see the ability to use the launch phrase when the screen is off, locked (use swipe) when connected to a trusted bluetooth device. Otherwise, the screen need to be on, but can still be locked. When no trusted bluetooth is connected, I'll wave, wake the screen, then say the launch phrase.

bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
Amazing. Yes, it works when plugged in. It also works when connected to a trusted bluetooth device as sailindawg mentioned.
Otherwise I have to wave to turn the screen on (still locked) and then use the "OK Google" command.

The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app

stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Tried this. Doesn't work for me.

stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I think you're talking about the MOTO Implementation, NOT the pure Android "OK Google" that we are talking about in this thread.

Bug in Smart Lock?

This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.

spark001uk said:
This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.
Click to expand...
Click to collapse
It happens to me, not within 30 minutes, but if i leave it overnight while i sleep. I'm not sure if its a bug or a feature to deep-lock the phone after x-amount of time of not being unlocked.

Happens to me.
spark001uk said:
This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.
Click to expand...
Click to collapse
I've got home wifi set and car set to smartlock but even after logging on to them, the first time I use phone after log in I have to enter code, after that everything works. Also after sleeping during night, in morning have to enter code first time upon waking up. So I think it is a bug.

vvveith said:
I've got home wifi set and car set to smartlock but even after logging on to them, the first time I use phone after log in I have to enter code, after that everything works. Also after sleeping during night, in morning have to enter code first time upon waking up. So I think it is a bug.
Click to expand...
Click to collapse
Same here with a Nexus 5. Smart watch and home location set as smartlock but each morning a manual unlock is required. Maybe it is designed to work that way.
Sent from my Nexus 7 using Tapatalk

bug or not
did this get resolved ?

I've noticed that smart lock automatically locks after 4 hours of non-use.

Evolution_Tech said:
I've noticed that smart lock automatically locks after 4 hours of non-use.
Click to expand...
Click to collapse
Now it even puts a pull down notification saying that too.

"OK Google" hotword detection ONLY when screen is on?

Hey everyone. I previously used hotword detection all the time. On my old LG G2, I used the Nexus 5 mod to enable hotword detection from any screen. It only worked when the screen was on, which eliminates false-positives.
However, with the Nexus 6, I can only enable hotword detection on ALL THE TIME, even when the screen is off. It's extremely inconvenient due to the sheer number of false-positives I've encountered. I'll be listening to a podcast or music with the screen off. Even if the audio doesn't even resemble "OK Google," my audio will pause and I'll hear that trademark ping as my screen turns on, awaiting a command. How can I disable hotword detection when the screen is off?
It's trivial to turn the screen on before using it. It's annoying to have to dismiss the Google Now and then turn my screen off. Even if I could dismiss Google Now by saying "cancel" or "never mind", it still doesn't turn the screen off. I have to go and turn it off myself. Right now, my only option is to allow hotword detection from my homescreen but that's suboptimal. If I'm in an app and want to use it, I have to first tap-and-hold on the home button to bring up Google Now, then I say "OK Google."

I've been having this problem since 6.0. The thing is, I can say OK Google and sometimes hear the chirp but the screen doesn't kick on, but it's useless in most cases because I need the screen on to see directions or a phone number for a place I'm looking up. It's frustrating.

Hung0702 said:
Hey everyone. I previously used hotword detection all the time. On my old LG G2, I used the Nexus 5 mod to enable hotword detection from any screen. It only worked when the screen was on, which eliminates false-positives.
However, with the Nexus 6, I can only enable hotword detection on ALL THE TIME, even when the screen is off. It's extremely inconvenient due to the sheer number of false-positives I've encountered. I'll be listening to a podcast or music with the screen off. Even if the audio doesn't even resemble "OK Google," my audio will pause and I'll hear that trademark ping as my screen turns on, awaiting a command. How can I disable hotword detection when the screen is off?
It's trivial to turn the screen on before using it. It's annoying to have to dismiss the Google Now and then turn my screen off. Even if I could dismiss Google Now by saying "cancel" or "never mind", it still doesn't turn the screen off. I have to go and turn it off myself. Right now, my only option is to allow hotword detection from my homescreen but that's suboptimal. If I'm in an app and want to use it, I have to first tap-and-hold on the home button to bring up Google Now, then I say "OK Google."
Click to expand...
Click to collapse
Those false positives were positively driving me batty as well. I managed to cut them down by going into a closet and performing three REALLY good recordings in Google Now hotword voice training.
There is something else to try: Benzo ROM is a custom Marshmallow ROM that has hotword detection from any screen (NOT always on). I can't link it in XDA, but if you were to Google "Benzo ROM" you'd find the Google+ community that has download links for the ROM. Good luck!

OK Google, working fine from screen off , but

I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?

but what ?
this is good news.

Ok Google works, but....
if screen can turn on, it would be 100 %
Best scenario will be to try youself and see what your results is.?
Same or otherwise?
As in past,
Xda members using Samsung devices
eg Note 5 or S8 etc could not get Ok to wake from
sleep /off. Samsung restricted ?
I posted OK Google results as there's
been a few threads on older to current devices
try to get Ok Google to wake/respond, from sleep.

Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")

I've been using Bixby and everything seems to work OK and if she has a hiccup I help her with it (trying to build my pay points lol) but yeah try with Bixby and see if there is a difference

willcor said:
I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?
Click to expand...
Click to collapse
is this with the stock launcher?

danon.brown said:
is this with the stock launcher?
Click to expand...
Click to collapse
I'm using Nova Prime.
However, i switched over to stock launcher, TouchWiz /Samsung Experience, and it was working fine.
As stated in previous threads (in past) you could not
wake device with Ok Google.
Yes with the Note 4 or previously you could.
With Note 5 etc it was suddenly not possible.
(Samsung ?)

harveydent said:
Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")
Click to expand...
Click to collapse
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?

willcor said:
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?
Click to expand...
Click to collapse
there is an option in the Google settings "Say ok Google anytime"

danon.brown said:
there is an option in the Google settings "Say ok Google anytime"
Click to expand...
Click to collapse
Yes, all my settings are correct.
The option you refer to, I'm aware of, it's enable.
My take on Ok Google waking screen, (which
it had never over past years done) , is Samsung
restricted it in favour of S voice and now with Bixby.
However somewhere they let it "slip" and Ok Google
wakes up from sleep.
My take on this us if Samsung realizes
it, they will again restict Ok Google wake up.
Even though on other handset brands, Ok
Google wakeup works fine.
Just on Samsung phones i believe it's a issue.?
Otherwise my Ok Google and Google Assistant and Bixby is working 100 %.
No other issues with them.

I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?

This is also on my s7,s8. I don't think it's note 8 specific.
Sent from my SM-N950U using Tapatalk

When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.

SiNJiN76 said:
When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.
Click to expand...
Click to collapse
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk

danon.brown said:
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Nice! That worked. Prior to it...I guess if I unlocked the phone real quick, it would give me the answer. But now it just does it with the screen off. Thanks. :good: Now is there a way to get a chime instead of a buzz?

After setting up voice and resetting data. Google assistant was reset and setup. Now the Screen turns on when I say OK Google. Ok. Worked Once.

I just wish it would by pass my pin and or fingerprint but I understand anyone that may sound like me could say ok Google and get into my phone....but it would be dope if I say ok Google and it bypasses locks because it knows my voice specifically

peacey8 said:
I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?
Click to expand...
Click to collapse
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.

danon.brown said:
This is also on my s7,s8. I don't think it's note 8 specific.
Click to expand...
Click to collapse
Yes i agree.
It's not just Note 8.
I had this issues since Note 5 days.
This is why i maintain Samsung
had something to do with it (over the years)
Maybe as result of Knox and security issues.,who knows?
But now on Note 8,
Ok Google is able to wake from sleep again.

willcor said:
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.
Click to expand...
Click to collapse
Try clearing the cache of the Google app and setting it up again.
Sent from my SM-N950U using Tapatalk