My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Mars104 said:
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Click to expand...
Click to collapse
That won't do any difference. I've tried another Moto 360 with another phone and it works as bad on the "Ok Google" part.
Retrain the command doesn't work when using another language than English so I haven't tried that.
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
kat3k said:
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
Click to expand...
Click to collapse
I haven't noticed any difference and most watch faces have been the stock ones that comes with Moto 360.
in my opinion, the stock watch faces respond faster than custom watch faces
I've had the same problem from Day One, the response to the keyword is far more haphazard than it was with my LG G Watch, but the speech recognition once past that is about the same; changing how I say "Okay Google" seems to be the only thing that makes any difference.
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
Same for me. I had the LG Watch R before (a year ago) and it was working flawless. Thinking about buying the Fossil Q Founder. But new watches will be out soon when Google releases Wear 2.0, I guess.
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Mars104 said:
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Click to expand...
Click to collapse
How do you launch Google Now? It's not available under system apps.
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Mars104 said:
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Click to expand...
Click to collapse
What version do you have?
1.0.26
Mars104 said:
1.0.26
Click to expand...
Click to collapse
Same as me, but I still don't have Google Now in system apps. What could be wrong? Running Android 7 DP5.
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Mars104 said:
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Click to expand...
Click to collapse
I've done some testing and it worked all of the times except one. But that time I just said "Ok, Google" again and it worked. Before it has never worked after a fail without letting the watch be for a long while.
I'll test it more the coming days.
Related
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I'm going to have to try this out. Me and my wife are having this same exact issue where I sound like a robot.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I have the same problem, but still trying to figure out a solution
dgmoodey said:
I have the same problem, but still trying to figure out a solution
Click to expand...
Click to collapse
so did you try disabling the setting that I posted?
workaround
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
MimKoRn said:
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
Click to expand...
Click to collapse
Sure is, but who knows when that will happen
http://forum.xda-developers.com/galaxy-s4-verizon/help/video-call-audio-kit-kit-upgrade-t2856743
I started a whole other thread on this.
Is not just a Hangouts issue, but it's a Skype and any other video chat issue.
Are you guys on 4.4? This might be it, but since hot word detection on any page was a Kit Kat function.
I tried turning off Google Now, but but I didn't turn off the hot word on any page function. I'll try it and let you know if it's the issue.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
Thank you sir. After a week and a half of trouble shooting, you found the answer.
The problem is indeed, and Google Search's new "anytime /any screen" hotword section function..
Go to Google Search, Settings, Voice, Uncheck hotword detection from any screen.
Why this breaks the wifi audio when using a video chat service is a mystery.
I now realize that this wasn't an issue under 4.3, because Hotword detection from any screen is a Kitkat only feature.
I don't know if this a Samsung, possibly or Google Search issue. But I'll submit a ticket to Google under in the play store.
Hopefully, everyone else will too.
I'm on the galaxy s4 from tmobile. I was also having this problem, but I turned off the hotword from any screen and it worked. I first noticed this trying to make a google voice call from hangouts, which is audio only, but it did it with video chats as well. I'll definitely report this.
Thanks for figuring it out!
Delete
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Jonny Kansas said:
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Click to expand...
Click to collapse
Its strictly a kit Kat 4.4 issue. That Google has dropped a serious ball on. But they can care less now, since they are on to lollipop 5.0
Maybe it will be fixed in 5.0
Looks like the issue wasn't fixed in Lollipop either. I'm running Dan's GPE ROM, and I had to disable any-screen hotword detection to return the normal voice.
I looked to see if anyone else was having this issue and found that there was not a thread for it yet. Instead of going into detail, I have simply posted my exchange with LG from online support, since it is all describe there.
David Miller: I preordered and now have an LG G3, which I think is a wonderful device, except for an issue that I have related to the LG voice recognition software. I am frequently in my car and use bluetooth. When I press the bluetooth button, I get the LG voice control software, "Say a Command." When I say a command, it is on the rare occassion that the software actually gets it right. Typically, it says, "command not recognized" to something as simple as "call mom mobile," or when it asks whether I want to call mom mobile and I say yes, it also says command not recognized.
David Miller: The other thing that I noticed is that it is more likely to get the command correct if I do not wake the software by bluetooth, but instead wake the phone and unlock the screen.
David Miller: I previously got the advice to restore factory settings, which I did. No improvement.
Frank: i understand
David Miller: Google Now seems to recognize my commands with no issues whatsoever.
David Miller: Also, the ok genie command doesn't seem to work.
Frank: in this case i can escalate the issue
Frank: to have an update pushed out to solve this issue.
If anyone has experienced this issue and has found a solution, please post here. Thanks.
I am in the same boat.
Any one now how to bypass the LG Voice and make bluetooth trigger Google Now? That should fix our issues....
Broken said:
I am in the same boat.
Any one now how to bypass the LG Voice and make bluetooth trigger Google Now? That should fix our issues....
Click to expand...
Click to collapse
Not a clue unfortunately. Couldn't even do it with my previous Nexus phone. Google had the dialer attached to the bluetooth rather than Google Now. It completely limited the actions that you could perform with bluetooth, but at least it recognized my command to call.
Broken said:
I am in the same boat.
Any one now how to bypass the LG Voice and make bluetooth trigger Google Now? That should fix our issues....
Click to expand...
Click to collapse
You can setup Google Now to record through bluetooth.
Touch the microphone, then the settings. Now choose "voice" .
Now go to the bottom of the page and select "Bluetooth Headset".
Now select "OK Google Detection" and select all the boxes.
You should be good.
OK Google would work everywhere and through the BT headset.
Broken said:
I am in the same boat.
Any one now how to bypass the LG Voice and make bluetooth trigger Google Now? That should fix our issues....
Click to expand...
Click to collapse
I disabled/froze the LG voice command and now mine defaults to Google Now on my Lg Tones. Try this, it worked for me.
Disabled LG Voice Command and Stereo launches Voice Dial, so guess LG Voice is better than nothing... Wish there was a way to make Google now work. Cortana worked just fine with my stereo lol...
faded03cobra said:
I disabled/froze the LG voice command and now mine defaults to Google Now on my Lg Tones. Try this, it worked for me.
Click to expand...
Click to collapse
What is the exact name of the LG Voice Command app, b/c I only have an LG Voice Command Speech Pack.
demill66 said:
What is the exact name of the LG Voice Command app, b/c I only have an LG Voice Command Speech Pack.
Click to expand...
Click to collapse
Voice Command
demill66 said:
What is the exact name of the LG Voice Command app, b/c I only have an LG Voice Command Speech Pack.
Click to expand...
Click to collapse
That just opens the old google voice dialer, not Google Now.
Same issue and I'm SO dissapointed. Upgraded from an S4...and today I get on my motorcycle, paired just fine, pressed the button on my Sena SMH10, and heard nothing for about 10 minutes. Stopped at a light, pulled out my phone, and Voice Command was still "initializing". Put it back in my pocket, and then a few minutes later it scared the crap out of me yelling "Say a command!!!". I said "play music" and it wanted to call someone. I said "No", and it didn't recognize my command. What a POS!
I need the ability to send texts, make calls, play music (select artist or album, etc.).
Really upset... I guess I'll try to disable it and use OK Google, but I know already that when I say "play music" its going to be streaming stuff and not using my local music.
If anyone finds a fix for this, please let me know.
Thanks,
Mark
https://play.google.com/store/apps/details?id=com.nuance.balerion&hl=en ??
Works on my Maxx
PBSDMark said:
Same issue and I'm SO dissapointed. Upgraded from an S4...and today I get on my motorcycle, paired just fine, pressed the button on my Sena SMH10, and heard nothing for about 10 minutes. Stopped at a light, pulled out my phone, and Voice Command was still "initializing". Put it back in my pocket, and then a few minutes later it scared the crap out of me yelling "Say a command!!!". I said "play music" and it wanted to call someone. I said "No", and it didn't recognize my command. What a POS!
I need the ability to send texts, make calls, play music (select artist or album, etc.).
Really upset... I guess I'll try to disable it and use OK Google, but I know already that when I say "play music" its going to be streaming stuff and not using my local music.
If anyone finds a fix for this, please let me know.
Thanks,
Mark
Click to expand...
Click to collapse
This is going to sound a bit odd, but I think that the phone is not initially using the bluetooth mic, but instead that on the phone. When I have the phone near my mouth after hitting the bluetooth button, it seems to get my commands right. I sent an email to LG customer support to see if they have any fixes in the works.
VoiceCommand 1.1.1
HERE'S ANOTHER WORKAROUND BUT YOU WILL HAVE TO MANUALLY PUT PHONE BACK TO SLEEP AFTER USING....
I am using the Jawbone IconHD, shouldn't matter but It works.
Must Be Rooted, Must have Titanium Backup!!
1.Download VoiceCommand https://play.google.com/store/apps/details?id=de.itdevcrowd.voicecommand
2. Open TB, find Voicecommand 1.1.1 - Tap it - swipe to the left - scroll down to CONVERT TO SYSTEM APP
3. Put phone to sleep, hold down button on Headset.....Google Now
FOR WHATEVER REASON THIS WORKAROUND WILL OVERRIDE THE "DIM AND PUT TO SLEEP AFTER SO MANY MINUTES" BUT AS LONG AS YOU DO NOT WAKE PHONE WITH BT BUTTON, PHONE WILL GO BACK TO SLEEP AS USUAL
NoI installed Bluetooth Launcher yesterday, to use with my hbs-800 headset, now get Google now voice actions instead of lg.
The font is ridiculously small on a g3; if you have an HDMI output adapter, use it, to select Google search, them the second voice actions option in the sublist that opens.
I can now use commands like Call, weather in, directions to, start, ...
I'll check out voice command, sounds like it gets to the same result, but without futzing with the selection window.
I didn't know TB had the promote to system app function. Thanks!
I second this app. No frills, but very useful. Can set the button on your headset to launch whatever you like, including Google Now voice launcher. Works great.
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch
markfm said:
NoI installed Bluetooth Launcher yesterday, to use with my hbs-800 headset, now get Google now voice actions instead of lg.
The font is ridiculously small on a g3; if you have an HDMI output adapter, use it, to select Google search, them the second voice actions option in the sublist that opens.
I can now use commands like Call, weather in, directions to, start, ...
I'll check out voice command, sounds like it gets to the same result, but without futzing with the selection window.
I didn't know TB had the promote to system app function. Thanks!
Click to expand...
Click to collapse
I wanted to note that the entry you want to check is different than one you mentioned, at least on my phone.
For me, it is actually the 4th one down, "com.google.android.googlequicksearchbox.voicesearchactivity
markfm said:
NoI installed Bluetooth Launcher yesterday, to use with my hbs-800 headset, now get Google now voice actions instead of lg.
The font is ridiculously small on a g3; if you have an HDMI output adapter, use it, to select Google search, them the second voice actions option in the sublist that opens.
I can now use commands like Call, weather in, directions to, start, ...
I'll check out voice command, sounds like it gets to the same result, but without futzing with the selection window.
I didn't know TB had the promote to system app function. Thanks!
Click to expand...
Click to collapse
Thanks for the correction, memory is the first thing to go
Anyhow, I'm enjoying BT launcher. The one thing I would love is to find a working widget to turn GPS on or off, so I could use "start gpstoggle" as a spoken command. So far the only one I've seen that actuality does this is the GPS part of power toggles, and there is no way to split that element off as a standalone commandable action. Everything else I've tried just acts as a shortcut to the Locations tab, you still have to then press the on/off button.
i have the same problem!
demill66 said:
I looked to see if anyone else was having this issue and found that there was not a thread for it yet. Instead of going into detail, I have simply posted my exchange with LG from online support, since it is all describe there.
David Miller: I preordered and now have an LG G3, which I think is a wonderful device, except for an issue that I have related to the LG voice recognition software. I am frequently in my car and use bluetooth. When I press the bluetooth button, I get the LG voice control software, "Say a Command." When I say a command, it is on the rare occassion that the software actually gets it right. Typically, it says, "command not recognized" to something as simple as "call mom mobile," or when it asks whether I want to call mom mobile and I say yes, it also says command not recognized.
David Miller: The other thing that I noticed is that it is more likely to get the command correct if I do not wake the software by bluetooth, but instead wake the phone and unlock the screen.
David Miller: I previously got the advice to restore factory settings, which I did. No improvement.
Frank: i understand
David Miller: Google Now seems to recognize my commands with no issues whatsoever.
David Miller: Also, the ok genie command doesn't seem to work.
Frank: in this case i can escalate the issue
Frank: to have an update pushed out to solve this issue.
If anyone has experienced this issue and has found a solution, please post here. Thanks.[/QUOTE
I am having the exact same issues, all other v commands work except the LG phones v command for placing call and or opening apps. I hope someone will correct this quickly otherwise I will have to go back to my Motorola, I really like the LG with this exception but it is a serious issue because I really need to be totally hands free.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
I am having the exact same issues, all other v commands work except the LG phones v command for placing call and or opening apps. I hope someone will correct this quickly otherwise I will have to go back to my Motorola, I really like the LG with this exception but it is a serious issue because I really need to be totally hands free.
Click to expand...
Click to collapse
Cats Of Thrones said:
demill66 said:
I looked to see if anyone else was having this issue and found that there was not a thread for it yet. Instead of going into detail, I have simply posted my exchange with LG from online support, since it is all describe there.
David Miller: I preordered and now have an LG G3, which I think is a wonderful device, except for an issue that I have related to the LG voice recognition software. I am frequently in my car and use bluetooth. When I press the bluetooth button, I get the LG voice control software, "Say a Command." When I say a command, it is on the rare occassion that the software actually gets it right. Typically, it says, "command not recognized" to something as simple as "call mom mobile," or when it asks whether I want to call mom mobile and I say yes, it also says command not recognized.
David Miller: The other thing that I noticed is that it is more likely to get the command correct if I do not wake the software by bluetooth, but instead wake the phone and unlock the screen.
David Miller: I previously got the advice to restore factory settings, which I did. No improvement.
Frank: i understand
David Miller: Google Now seems to recognize my commands with no issues whatsoever.
David Miller: Also, the ok genie command doesn't seem to work.
Frank: in this case i can escalate the issue
Frank: to have an update pushed out to solve this issue.
If anyone has experienced this issue and has found a solution, please post here. Thanks.[/QUOTE
I am having the exact same issues, all other v commands work except the LG phones v command for placing call and or opening apps. I hope someone will correct this quickly otherwise I will have to go back to my Motorola, I really like the LG with this exception but it is a serious issue because I really need to be totally hands free.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
I am having the exact same issues, all other v commands work except the LG phones v command for placing call and or opening apps. I hope someone will correct this quickly otherwise I will have to go back to my Motorola, I really like the LG with this exception but it is a serious issue because I really need to be totally hands free.
Click to expand...
Click to collapse
On my Verizon LG G3, I followed the directions in this thread to disable the "Voice Command" app from within the Application Manager and I ensured that "Bluetooth Headset" was on from within the Google Settings app under the "Voice" menu. When I press the Bluetooth button in my Toyota Tacoma, it now calls up the Google app which prompts me for a voice instruction. These steps eliminate LG's crappy Voice Command app. :victory:
Click to expand...
Click to collapse
My D855 with stock ROM is completely unresponsive to the Bluetooth push button.
I set the:
Google -> Search -> voice -> Hands free -> Allow Bluetooth request on locked screen
Google -> Search -> voice -> Record from Bluetooth
The oldest firmware I tried was STOCK ROM v21A.
I am not alone with this problem:
https://forum.xda-developers.com/lg-g3/help/voice-dial-bluetooth-t2826458/page4
May be an older Android version triggers Voice recognition from Bluetooth.
I went into google now search settings and performed the voice training and enabled the option for hot word detection from lock screen and power off but it doesn't work. the only time it works is when i'm at the home screen UNlocked OR at the google now search area. Screen off or from lock screen detection simply does not work.
does anyone else notice this?
I don't have the nexus 9 but I did install the latest google now search and launcher from apkmirror .com and there was an always listening option in 'hotword detection' in voice settings of the google now. There was also the screen off detection option but it was greyed out. I had the always listening in all apps option enabled and it was working greatly but the next day I woke up and the feature wasn't working so I went into settings and discovered that both of those options had disappeared (not greyed out but freaking disappeared), its some kind of google restriction, they are remotely restricting users from using these features for some unexplained reason.
Maybe its the same for u or it might be something else.
Same here, bit worked arter reboot
It works for a while after a reboot, but eventually stops working after a couple hours.
Looks like a common bug, I've seen some threads about this same issue (and I'm experiencing the same problem, too)
Ok, let's hope Google is on it
borchgrevink said:
Ok, let's hope Google is on it
Click to expand...
Click to collapse
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
mackendw said:
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
Click to expand...
Click to collapse
Is it supposed to work on the N4? (I mean when screen off).
borchgrevink said:
Is it supposed to work on the N4? (I mean when screen off).
Click to expand...
Click to collapse
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
mackendw said:
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
Click to expand...
Click to collapse
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
borchgrevink said:
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
Click to expand...
Click to collapse
when I initially set it up, IT DID WORK....but then after a few hours, days (dunno for sure) it stopped. voice recognition works from google now screen, or the home page fine. something not right somewhere...
Hmm. From locked screen? Strange. Absolutely sure?
borchgrevink said:
Hmm. From locked screen? Strange. Absolutely sure?
Click to expand...
Click to collapse
there is an option in Google Now -> Settings -> Voice -> OK google detection ....a check box exists here stating:
When Locked
Allow "OK Google" to start a voice search or action from a secure lock screen
so, it would seem that this is what was intended. perhaps what they meant here was that the screen has to be on and not timed out. dunno.
Yes, but screen has to be on. Only nexus 6 and 9 support GN with screen locked and off
Google search from locked screen works for a while and then stops. It's done this on my s4 and note 3. It is defenetly supposed to work from secure lock screen. In Google now settings there is a 3rd check box and you even get a warning stating anyone may be able to unlock your phone.
Google needs to fix this issue. I'm not sure what's up with these companies making screwed up software. Where are the devs, and why are they getting paid if they can't make flawless software. When I crash My car into a tree trying to unlock my phone and I press a law suit against google I'll bet they will fix it. Always takes a law suit to fix ****.
Oh. Anyone notice every app you've ever paid for or downloaded is under my apps "all" what's up with "all" I'll file my documents in my office under the "all" folder and see how quickly I get fired...Thanks for allowing me to rant.
Happy new year!
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8/discussion[1-25]
Major issue
I recently bought a lg g watch and it was under my knowledge that "Okay Google" is on auto-detection. My watch for some reason doesn't detect my voice or maybe it's the microphone not working. BUTTTTT when I go to the Google search app on the watch i can actually use the microphone to send a text, make a call, and all that Googling stuff. Other than that, "Okay Google" doesn't seem to work when it's on a watchface. Please help.
scream4cheese said:
I recently bought a lg g watch and it was under my knowledge that "Okay Google" is on auto-detection. My watch for some reason doesn't detect my voice or maybe it's the microphone not working. BUTTTTT when I go to the Google search app on the watch i can actually use the microphone to send a text, make a call, and all that Googling stuff. Other than that, "Okay Google" doesn't seem to work when it's on a watchface. Please help.
Click to expand...
Click to collapse
I guess I'm the only one with this kind of problem. Everybody else's device works out of the box.
You made sure the watch is active fist, right? Like by bringing your wrist up so the screen lights up more (at least :/ mine). If you have wrist gesture disabled then it will never work. Try to enable that and bring the wrist up and say okay Google again.
frigidazzi said:
You made sure the watch is active fist, right? Like by bringing your wrist up so the screen lights up more (at least :/ mine). If you have wrist gesture disabled then it will never work. Try to enable that and bring the wrist up and say okay Google again.
Click to expand...
Click to collapse
on or off doesn't work. I returned the device and got a refund. It was disappointing experience. I'll be sticking to my Pebble until the next iteration of Android Wear smartwatches come out.
It's official:
Confirmed new navigation gestures, new voice commands, and call support (not our G Watch, obviously...).
http://officialandroid.blogspot.com.es/2016/02/android-wear-designed-for-your-wrist.html
https://plus.google.com/+WaynePiekarski/posts/JSWwVdcqAp3
How are we going to be able to restart our watches on the go if Marshmallow is going to removed the Restart button?
Where did it mention the restart button will be removed?
Look at the part in bold
Hi everyone!
We are happy to announce a new update for Android Wear, rolling out starting today which will include the following features:
New ways to get your information: Android Wear is launching even more wrist gestures so you can navigate your watch by just moving your arm. In addition to scrolling through your cards, you can now expand a card, bring up your apps, or return back to the watch face by just moving your arm.
New ways to communicate: Your Android Wear watch already saves you time by letting you see who’s calling. Starting today, with speaker support for Android Wear, you can take calls and make calls too. Just make sure your watch and phone are within Bluetooth range.This will be available on Android Wear watches with speakers, starting with the Huawei Watch and ASUS ZenWatch 2 (49mm - large). Also, for those using Google Messenger for SMS, its new watch app allows you to see your full message threads right on your wrist.
New supported languages: Android Wear is now available in six new languages: Dutch, Polish, Chinese (Traditional and Simplified), Indonesian and Thai. Set up the language on your phone under settings. .
New apps experiences: With the new Google Now app experience on your watch, never miss important notification cards, such as reminders or flight delays. Launch the Google app from your apps list to see all of your notifications. The new Reminders app allows you to create, view, and archive reminders. Also, now send instant messages with just your voice from the following 3rd party apps like Google Hangouts, Nextplus, Telegram, Viber, WeChat, and WhatsApp
Settings update: With the new Date and time setting, you can now choose to sync your watch’s time and date automatically or change it manually. For watches with integrated speakers, control Sound including media, alarm and ring volumes, as well as ringtone! Finally, we’ve made some other changes to keep in mind. Restart has been dropped in the latest update. If you do power down be sure to use your power button on to restart your watch. And if you need to reset your watch, now select Unpair with phone.
Conserve power - When your watch is not worn for a long period of time it will go into a mode to conserve battery by restricting what your apps are accessing and running. To exit this mode just move your watch, turn on the screen or connect it to a charger. To also help conserve battery, individual apps that have been unused will go into a standby mode until you start using the app again.
In preparation to receive this update on your watch, please make sure you have the latest version of the Android Wear app on your phone, by opening the Play Store, searching for “Android Wear”, and opening the app’s Play Store page. If an [Update] button is visible, make sure to update the app.
To successfully receive the update on your watch, please make sure your watch is on its charger overnight and connected to your nearby phone by either bluetooth or Wi-Fi (Android phones only).
The release will roll out gradually in the coming days and weeks. As always, feel free to ask questions on this forum or share feedback and let us know if you encounter any issues!
For more information, you can read our blog announcement.
Cheers!
The Android Wear team
Click to expand...
Click to collapse
Source for that.
Or you could just look at the new Android Wear help section here.
mm_david_mm said:
It's official:
Confirmed new navigation gestures, new voice commands, and call support (not our G Watch, obviously...).
http://officialandroid.blogspot.com.es/2016/02/android-wear-designed-for-your-wrist.html
https://plus.google.com/+WaynePiekarski/posts/JSWwVdcqAp3
Click to expand...
Click to collapse
Any OTA?
Has someone just received the OTA?
weeks and soon... thats the problem!
Seriously? No reboot option on 1.4? Who came up with that stupid idea? Hopefully we'll get some kind of ROM with that option restored or at the very least they will add it back in officially because the last time I checked we don't have a proper power button on the G Watch it's a small thing on the back that you need a small toothpick or something to use.
Stupid dumb idea Google.
There is a restart button on the back
Sent from my VS985 4G using Tapatalk
Anyone get the update?
zul8er said:
There is a restart button on the back
Click to expand...
Click to collapse
Yeah and you need something small like a toothpick to use it. Again terrible idea to take away what should be a basic function in the software itself. I will refuse to upgrade to 1.4 based on principal of this alone.
Can't you start your watch with the watch button?!
They removed the restart function, but as they say you just have to shutdown then restart your watch. Not a huge change.
cedricberger said:
Can't you start your watch with the watch button?!
They removed the restart function, but as they say you just have to shutdown then restart your watch. Not a huge change.
Click to expand...
Click to collapse
Have you tried to physically turn on the G Watch without the charging dock on hand? You need something small and pointy like a toothpick.
And to me it's the principal of the matter. Taking away a basic function for no good reason. Why is it okay for us to just shrug our shoulder and be like "okay that's fine." No it's not.
AngryManMLS said:
Have you tried to physically turn on the G Watch without the charging dock on hand? You need something small and pointy like a toothpick.
Click to expand...
Click to collapse
ok... I was just surprised the main button could not turn on the watch, like on my G Watch R.
cedricberger said:
ok... I was just surprised the main button could not turn on the watch, like on my G Watch R.
Click to expand...
Click to collapse
There is no main button.
Bushrod said:
There is no main button.
Click to expand...
Click to collapse
Yeah, the g watch sqaure has no physical buttons accept for the tiny one on the back
Anyone received OTA?
jmadotme said:
Anyone received OTA?
Click to expand...
Click to collapse
Nope.
AngryManMLS said:
Have you tried to physically turn on the G Watch without the charging dock on hand? You need something small and pointy like a toothpick.
And to me it's the principal of the matter. Taking away a basic function for no good reason. Why is it okay for us to just shrug our shoulder and be like "okay that's fine." No it's not.
Click to expand...
Click to collapse
A pen works fine.
Sent from my VS985 4G using Tapatalk
zul8er said:
A pen works fine.
Click to expand...
Click to collapse
Still doesn't make taking away software reboot any more okay. Not that your idea is bad or anything that is a good idea. It's still the principal of the matter to me.