Hello,
I have a question regarding Google Assistant light automation. I recently purchased a Philips hue system and its working pretty well. Yesterday, I set up Google Assistant to voice control the lighting at home. Some months ago, I received the Android 10 update for the Note 9 and according to the Internet, since that update, Google Assistant asks to unlock the phone in order to perform the turn on/off functions for the bulbs. Now, I found out that adding my home to Smart Lock works. But the thing is that as long the phone is locked, I only get one response from the Assistant. When I try to activate it again, it activates, then it listens to what I'm saying and then it shows the three dot icon like its searching but nothing happens. If I turn off the screen with the button and activate the Assistant once again, it again works for the first command. I tried to factory reset the phone but it didnt help.
This is certainly a Smart Lock/Android 10/Google Assistant issue since if I'm not home and the phone is locked, I receive response all the time. Likewise, if I'm home and unlock the phone manually, I get response on every command.
Is this a bug? Do anyone have a similar issue?
Thanks in advance
Yes, it is a bug, but not necessarily because of the home automation although I first noticed it when it didn't respond to home automation commands or routines.
i recently purchased quite a few automated lights and switches.
ok google
turn on bedroom
what time is it
tell me a joke
all have the grayed out mic and grayed out dots you refer to.
WHEN the phone is unlocked and home.
It is only noticeable for me when the phone is unlocked but home. I have set the GPS and WIFI to keep the phone unlocked at home, so it theoretically should work since it recognizes my wifi network and gps. but it refuses to respond with a "ok google" when speaking about turning something on and off command.
unlock the phone manually and it works.
I haven't been out much...
Related
Somehow I managed to install MS Voice Command and is working OK.
But, one thing I cannot manage to solve, is using the voice dial button while the cover is closed. It doesn't do anything. It has to be open or the screen facing upwards.
Is there a solution or perhaps not?
Let's say you dialed. How would you talk to the person?
I am having the same problem.. it locks the buttons when lid is closed and there seems to be no way to unlock them... and, you can talk with the lid closed, for the guy who asked.
settings, buttons, lock. you can choose not lock the buttons when the device is closed
I am also suffering te same problem with voice command.
richard
they are all unlock, but still, voice command doesn't activate-
There has to be a way to trick the registry... but I'm no expert at all.
It's on my list of things to look at tonight.
I'll get to it when I've finished my real VGA hack.
Great! We'll be all awaiting your news.
as far as i know then the cpu is not active and normal programs are not running when ones device is turned off
so even if you unlock the buttons voice commander would not respond unless pressing the button wakes up the pda
Pressing the button does wake the device though. This is the bizarre thing.
If the device is off in tablet mode, it works fine.
If the device is off in closed mode, it doesn't work.
Pressing the button in closed mode produced the bing-bong sound indicating the VC is ready to accept commands but nothing happens therafter.
Was there ever a solutio found to this problem??? :shock:
Afraid not.
I'd love to find a solution to this too. I am convinced it is possible, because incoming calls do activate Voice Command with the XDA closed (it tells me who is calling), and the external buttons do wake the XDA when it is open.
But even though I have "do not lock buttons" selected, none of the external buttons do anything when the unit is closed.
I'd be very, very grateful if anyone could come up with a solution to this.
If you switch off in toggle mode then the device will respond after pressing the VC button. But if you have set pda up to close after a certain amount of inactivity, it will stop responding after that period of time expires.
So the solution is concealed under the way you switch off the device. I think if we found a way to switch off in toggle mode instead of suspending when pressing the on/off button, the we would found the solution. However, battery issues may come up...
I am using the European Tab, but that probably makes no difference.
For security, I lock the phone automatically after 3 minutes of inaction. This works fine for all apps except phone. Strangely, after dialling (or after picking up a call) the phone first turns off the screen, and briefly thereafter locks the device, within 10 seconds. I can continue the call, but as the screen is off, I can not hang up, unless I first switch it on and enter the password.
I have not found a parameter to influence this behavior. But I know it is not related to the proximity sensor, as the effect happens the same way even when not moving the device from the desk.
Is this a confirmed behavior or does anyone know a cure? It's ok if the screen goes dark, and even if you must turn on via power button, but the password?!
Thanks for any help,
Rolf
rgbigel said:
I am using the European Tab, but that probably makes no difference.
For security, I lock the phone automatically after 3 minutes of inaction. This works fine for all apps except phone. Strangely, after dialling (or after picking up a call) the phone first turns off the screen, and briefly thereafter locks the device, within 10 seconds. I can continue the call, but as the screen is off, I can not hang up, unless I first switch it on and enter the password.
I have not found a parameter to influence this behavior. But I know it is not related to the proximity sensor, as the effect happens the same way even when not moving the device from the desk.
Is this a confirmed behavior or does anyone know a cure? It's ok if the screen goes dark, and even if you must turn on via power button, but the password?!
Thanks for any help,
Rolf
Click to expand...
Click to collapse
It happens to me lately after I flashed a new Rom but I highly doubt that has anything to do with it...it feels like a proximity sensor issue, and a autolock issue as well . I am Clueless sorry
This video is highlighting a new feature of Android L - trusted devices. Basically, your phone doesn't lock itself as long as it's connected to trusted devices via bluetooth.
I'm more interested in the other smart lock feature shown in the video, though not really explained. It's called trusted faces. Anyone with a Nexus 4/5/7 try this yet? Can anyone confirm if it works differently (hopefully better) than face unlock in previous versions of Android?
Ya it works fine .I am loving it
I wonder if I can do this with my device and my Glass...
Dr Faustus said:
I wonder if I can do this with my device and my Glass...
Click to expand...
Click to collapse
You can do this with tasker. I have it so my phone does not lock when connected to my home WiFi, etc.
Also if you have xposed installed then no lock home works as well.
wwevoxnj said:
You can do this with tasker. I have it so my phone does not lock when connected to my home WiFi, etc.
Also if you have xposed installed then no lock home works as well.
Click to expand...
Click to collapse
That's good to know, I use Tasker normally to switch from Mobile Data to WiFi when arriving home and vice versa.
Trusted face works good, but I wish it would allow multiple faces.
The face unlock seems to work a bit better than in previous android versions... you don't know it's looking for your face, you just swipe to unlock and if it recognises you then it just unlocks, if not, you put your pin in.
I'm having trouble with tasked though, my old method of removing the pinning when connected to my wifi doesn't seem to work... neither does turning off the mobile data... I think it's just that tasked may need an update
I just tried this on my other N5 after seeing your post. The only time I can't get it to work consistently is in very dim/dark lighting similar to the way its always worked. The differences in the way it works on L vs earlier iterations is that it is extremely fast almost instant and it never shows the camera. It's constantly looking but in the background. There is small icon bottom center that changes from a person avatar (to tell you it is looking) to an unlocked padlock symbol to confirm it recognized you upon turning on the phone. Hope that helps. The trusted devices works wonderfully.
So does this "smart lock" only work with bluetooth and NFC? I hoped (and thought it was implied when the feature was first shown off) that you could also set it up to bypass the PIN unlocking when connected to a trusted wi-fi network, but it looks like it only works for bluetooth and NFC. Which kinda sucks for me, because I really don't use any kind of bluetooth things, nor do I have anything that would work with the NFC aspect of that, either.
wwevoxnj said:
You can do this with tasker. I have it so my phone does not lock when connected to my home WiFi, etc.
Also if you have xposed installed then no lock home works as well.
Click to expand...
Click to collapse
How would you have xposed running on L?
Is there a way, to use WIFI as an smart lock device? I mean maybe it is possible to use Tasker to simulate an connectet bluetooth-device if i am connectet to my wifi?
borsty44 said:
Is there a way, to use WIFI as an smart lock device? I mean maybe it is possible to use Tasker to simulate an connectet bluetooth-device if i am connectet to my wifi?
Click to expand...
Click to collapse
I have Tasker setup with Secure Settings to toggle PIN lock when I'm on home wifi, and it doesn't seem to work correctly on L for my N7 2013. The setting is set to NONE in the security settings, but I still have to enter my PIN. If I manually go in and "edit" the setting and select NONE again, then it doesn't ask for my PIN. Once I leave home and Tasker applies my PIN again, if I return home, I have to go manually select NONE again or just enter my PIN.
Not sure if that's a bug with Secure Settings or a bug in L. The setting is changed, but it doesn't seem to register. I guess I could understand if it did something like, require the PIN for unlock the first time after connecting, but that doesn't seem to be the case. I used Trusted Devices on m Moto X 2013 with the bluetooth in my car, but trusted devices are cleared when you disable PIN lock. I use the same profile to turn off the password on my phone when I'm at home, so it clears my trusted devices every time I go home. I use my phone pretty often, so the lock doesn't usually set during the day. My tablet sits on my desk at work all day and I have to unlock if I use it (30 minute lock delay), but at home I am on my tablet most of the night while my phone sits unused (but it doesn't lock, because I'm at home..).
Either way, something isn't working with L and Secure Settings on my Nexus 7.
You'll now be able to add trusted places to smart lock.
Link
Amazing
i'd like to use it to unlock the phone with bluetooth paired headset or NFC, unfortunately i've 4.3... do you know if ther is a mod for 4.3?
Just be aware that if you have ANY app that turns off your screen (for example, Gravity Screen, which can detect you putting the phone in your pocket or face down, and automatically shuts off the screen), the Google API also forces that app to lock the screen as it shuts it off. The lock that the app will do cannot be circumvented by Smart Lock, and you'll have to enter your passcode every time.
I just got the location-based update for smart unlock and it's great!
Sent from my Nexus 6 using XDA Free mobile app
the only thing that sucks about smart lock with Bluetooth, you can't control the distance. My pebble watch goes 30 meters before Bluetooth drops. That means at work i can go to the bathroom and someone still can bypass my lock screen
wwevoxnj said:
You can do this with tasker. I have it so my phone does not lock when connected to my home WiFi, etc.
Also if you have xposed installed then no lock home works as well.
Click to expand...
Click to collapse
I use Trusted Devices for my Nexus 6, but I don't use the other business. The face unlock can still easily be beaten. You can even just hold up another smartphone and get it done. The trusted devices is *really* nice. The only two things I use it for are my car and the sound system in my bathroom. Those are the only 2 devices that, when I use them, I know my phone is right there. I don't have it set up for my Android Wear watch, since I don't want someone to be able to pick up my phone from my desk at work when I'm 20ft away and play with it, and I don't use my home wifi because it extends all over my yard...so if anyone just picks up my phone anywhere within 100ft of my house they can use it.
2swizzle said:
the only thing that sucks about smart lock with Bluetooth, you can't control the distance. My pebble watch goes 30 meters before Bluetooth drops. That means at work i can go to the bathroom and someone still can bypass my lock screen
Click to expand...
Click to collapse
Before you go to the bathroom, just touch the lock icon on the lock screen for a second or so, and it will require a passcode for the next unlock.
jt3 said:
Before you go to the bathroom, just touch the lock icon on the lock screen for a second or so, and it will require a passcode for the next unlock.
Click to expand...
Click to collapse
Good to know and repped. thanks! I have a Moto Keylink coming next week
Today I updated Google and noticed that saying "okay Google" from the home button screen (whatever it's called, the screen shown when you hold the home button for a bit) doesn't work anymore. It works from any other screen from the home screen to the lock screen.
I searched around but found no solution. Anyone have any ideas, or is experiencing the same thing? Could this be just an issue with the update and require another update to fix?
Edit: And now it's mysteriously working again, with absolutely nothing changed or done on my end.
Did you ever get this fixed? Ok google has been very buggy for me. I have a Google Home and wondered if it was messing it up.
So I noticed after the update I couldn't unlock the Axon 7 when it had its screen off and it was plugged in (the feature obviously doesn't work at all if the device isn't plugged in). The way I solved this was to go to the voice activity on Google and I paused (or deactivated) it. By doing this, you essentially reset all Google Voice settings (not the history). Then, just long press the home button which brings up the assistance which will ask you to give it permission to listen to you. It will then ask you to say "Ok Google" three times (as if it's the first time you're using it). When the trusted voice option is toggled (which is automatically will do it for you), the issue is fixed and the phone can be unlocked with you voice with its display off and while plugged in.
I purchased my S8 directly from T-Mobile today. So when I left the store and started using it more, I realized that it had a few bugs. Before and after the OTA(that was immediately found on my phone to download and install), and even after a factory reset.
First I'm experiencing that the Android/Google pre installed notepad or memo, is completely missing from the device. Completely searching the phone, and even going into the Android OS application settings. Also, even having Samsung do a remote screen share via technical support on the phone, and the Tutor app. Even they couldn't even find it.
Second I'm the type of person that doesn't like any type of vibration on my phone. So I turn off all the vibration in the Android OS settings, even for calls. But for some reason the touch screen home button has some type of forced/haptic vibrate. This happens on any screen, including when the screen is off and I'm clicking the touch screen home button to wake up to screen to use the device. Is this even normal, for only the touch screen home button to make some type of vibration(more specifically, some type of forced/haptic vibrate), when you have all the vibration settings that can be turned on and off in the Android OS settings completely turned off?
Then lastly, I'm having a problem with Google Voice to Text, and Bixby voice to text. What happens is, if I turn off Bixby voice to text in the Android OS settings. So I can use Google Voice to Text. But every few minutes, Bixby turns itself on, and is automatically the default voice to text. Then when I go into the Android OS settings, it appears that the circle turns blue indicating that it was on period when I clearly turned Bixby Voice to Text off in the Android OS settings.
What should I do? Should I return the device and get a replacement immediately. I got it from my carrier this morning at there corporate store. They had a bunch in stock, and when I was there UPS even delived more to the store. I even contacted Samsung, all they can tell me was to send my phone in and leave my phone there for a minimum of two weeks and remain completely with out a phone. Which is absurd, after purchasing a new phone and only owning the device 3-4 hours maximum!
Just an update, I went back to T-mobile, after speaking to booth Samsung and T-mobile and exchanged my S8. But still the problems persist on the new exchanged S8. Also, this time around it has gotten worst, because this time around I was unable to even Smart Switch the Memo files. Because on my old Galaxy I was at least able to transfer my Android/Google memos to the 1st S8. But from the returned S8 to the new exchanged S8, I was unable to do so. It was not even an option at all(greyed out or selectable)
I don't think any of these are problems? First it's Samsung notes that is presinstalled second just download a note app. Second the home button has its own vibration setting and their are apps to further customize, I have mine on a super short vibration and changed navigation keys to stay perma black even when keyboard open with an app. Lastly the bixby voice is disabled until they fix it. By default the phone uses Samsung voice but you can enable google voice or get another keyboard. Also don't forget Android is customizable but may have to use an app for it.
I have blacked out my phone, use navbar apps, and use google keyboard.
Sent from my SM-G950U using Tapatalk