- Aug 14, 2013
- 277
- 0
- 16
Coming back from Apple, where I’ve spent a year moaning about Siri and telling everyone how great Samsung and Google Asst are, I’m now having to eat humble pie a bit because I’ve noticed one big problem:
Google Assistant’s beauty is that you can yell at your phone from across the room and it talks back to you and does whatever you ask. Or at least it used to.
Now, I can yell at my Note 10 to play a song or send a message or whatever and it instantly processes what I’m saying. But then I have to physically unlock the phone to follow on, which negates the point.
To say I’m disappointed is an understatement. Even Siri, for all of its many faults, can do simple tasks like that.
Am I doing something wrong here? Research leads me to believe that Google disabled Voice Unlock for security reasons and that’s what’s causing this. But I can’t believe that they would intentionally cripple one of its big selling points.
Can anyone shed any light on this? I’m just hoping it’s me and I’ve made a mistake!
Tks
Google Assistant’s beauty is that you can yell at your phone from across the room and it talks back to you and does whatever you ask. Or at least it used to.
Now, I can yell at my Note 10 to play a song or send a message or whatever and it instantly processes what I’m saying. But then I have to physically unlock the phone to follow on, which negates the point.
To say I’m disappointed is an understatement. Even Siri, for all of its many faults, can do simple tasks like that.
Am I doing something wrong here? Research leads me to believe that Google disabled Voice Unlock for security reasons and that’s what’s causing this. But I can’t believe that they would intentionally cripple one of its big selling points.
Can anyone shed any light on this? I’m just hoping it’s me and I’ve made a mistake!
Tks