Tweet
Some Android phone and tablet users are reporting a bug with Google Assistant, which causes their device’s screen to stay powered on indefinitely after hearing the wake phrase ‘Hey Google’.
This is seriously frustrating for people who own other devices (such as Google Home smart speakers) that are activated using the same spoken command.
[ul]
[li]Take a look at our complete guide to the best Android apps[/li][li]On a budget? Here are the best free Android apps[/li][li]We’ve also rounded up the best free Android games[/li][/ul]
Several staff members from Android Police noticed that their phones and tablets weren’t going back to sleep after recognizing that the wake command was intended for a different device. This is a serious battery drain (even with dark mode activated), and a potential security risk as it leaves the device unlocked.
It could also lead to images being burned into the screens of LCD devices, causing permanent damage.
Chronic insomnia
The same problem has been reported periodically on the Google support forums since September. It mostly seems to affect Google Pixel and Google Home devices, though one OnePlus 6T owner found their phone awake with its battery at 1% hours after Google Assistant detected the wake phrase.
The cause of the problem has yet to be identified, and it appears to be intermittent, but we’ll keep you updated if a fix emerges. In the meantime, we recommend keeping an eye on your phone every now and then (particularly if you own other devices with Google Assistant) so you can turn the screen off manually if necessary.
[ul]
[li]How to record your screen on Windows, macOS, iOS or Android[/li][/ul]
Via Android Police
Continue reading…
This is seriously frustrating for people who own other devices (such as Google Home smart speakers) that are activated using the same spoken command.
[ul]
[li]Take a look at our complete guide to the best Android apps[/li][li]On a budget? Here are the best free Android apps[/li][li]We’ve also rounded up the best free Android games[/li][/ul]
Several staff members from Android Police noticed that their phones and tablets weren’t going back to sleep after recognizing that the wake command was intended for a different device. This is a serious battery drain (even with dark mode activated), and a potential security risk as it leaves the device unlocked.
It could also lead to images being burned into the screens of LCD devices, causing permanent damage.
Chronic insomnia
The same problem has been reported periodically on the Google support forums since September. It mostly seems to affect Google Pixel and Google Home devices, though one OnePlus 6T owner found their phone awake with its battery at 1% hours after Google Assistant detected the wake phrase.
The cause of the problem has yet to be identified, and it appears to be intermittent, but we’ll keep you updated if a fix emerges. In the meantime, we recommend keeping an eye on your phone every now and then (particularly if you own other devices with Google Assistant) so you can turn the screen off manually if necessary.
[ul]
[li]How to record your screen on Windows, macOS, iOS or Android[/li][/ul]
Via Android Police
Continue reading…