Every night since I got this amazing phone I've been using the command "wake me up at..." or "wake me up in..." or "set an alarm at..." to set alarms for the next morning. Few days ago I noticed that the command stopped automatically setting alarm and instead prompts me to click the "Set alarm" button instead. Why is this happening? Every other commands seems to work - play music, open camera etc, etc. It's not a major problem but it bugs me. Do you guys have this problem? Can I fix it somehow or is it a server-side bug?
Apparently Google fixed the issue as of now, but it was definitely not working these past few days. Just to let you guys know, it was probably a bug in their servers or something
Related
Is anybody else having problems with doing voice commands on the lockscreen since the last Google app update? It'll register the voice command, but won't start the activity until I actually unlock my phone. For example, if I ask it to play a song, it'll register it, but nothing happens until I unlock my phone. It will briefly have a white screen that says "Google App" at the top, and then it'll jump to the music app to play my song. It also does this when using voice commands with the screen off and charging.
I'm on Cloudy 1.2, and was having the same problem on Darkwulf Beta. Both Kit Kat ROMs.
Does your phone have a lock on it? It could be interfering with google now.
Nope, just the swipe unlock. No password, pin lock, or knock code.
So nobody else has had this issue? I still can't figure it out. I've gone through all my settings, disabled Xposed, and looked at any other apps that might be interfering, and I'm still coming up empty.
I have this problem also!
I tried to find a solution but all I got was people saying that is how the lock screen is intended to work... Anyone know of a fix?
I'm running stock 5.1 but I first noticed this on 5.0.1
I have some problems with my Z5, and they are starting to get really annoying.
Now, i havent looked for an answer for this one yet, but since i'm making a post, i will just throw it in here. The fingerprint scanner stoppes working sometimes, and i get this error message saying that "the hardware is not available" or something like that. It is in norwegian, so i just have to translate it myself. My device is rooted, but this occured while my phone wasn't rooted or anything like that. The problem fixes itself when i reboot. This is not a huge problem for me, since i can live without the fingerprint scanner, but i like to use it, and it is very annoying.
I have looked for an answer to this, and i have not found any other threads than for Z5 Compact, and there was no solution in that thread. 1 or 2 times a day i get this error message that says that it is unable to play the video. This is extremely annoying, as i use the app often, and the only way to fix it is to reboot the phone. This was also a problem before i rooted the phone. It stopped doing it for some weeks, but now, the last week or so, it has started again and it is driving me insane.
I have tried to:
Reinstall app
Force close app (and all other apps to see if that helped)
Clear cache
Factory reset
The only thing that helpes for a few hours is to reboot the phone.
Right now i'm using build 32.1.A.1.185 with androplus kernel. But i had the same problem the first days i had the phone before i rooted.
Sorry for possible bad grammar as english is not my main language
Nice to have someone raised this issue. I have the same issue from time to time and yes, the only solution for now is to restart your phone but it gets annoying. I think this is not related to if you're rooted or not. This may be hardware related or decoder related? After watching several videos from YouTube, all other streaming videos does not play. Fingerprint scanner stops functioning as well until you restart. Hope someone can find the solution.
I have the same problem when I watch 3 or more videos, and the "hardware fingerprint not avaliable" message appears after youtube report an error on reproduction, when I press the button "try again", the fingerprint won't work anymore (only reboot fix the error)
For the YouTube problem: have you tried turning WiFi on and off instead of rebooting?
that's your solution, if your phone is rooted: http://forum.xda-developers.com/xpe...back-issue-t3290793/post64763489#post64763489
not sure if it only works with unlocked bootloader.
Go to settings > apps > google play services > permissions. Then turn off body detecting. Worked for me.
I've been battling this since Android 5.0
Ok Google worked well for the first year it was out. At some point Google updated the app and all hell broke loose. Right now I have a Google Pixel with stock 8.0. I wiped my custom ROM because the issue came back and I really want to solve this. I have set up very little at this time. A few apps and signed into Google. Fresh setup for less than a week now.
What used to happen or the problem? Saying ok Google there would be an audible tone. Then when it stopped making that tone, I searched all over the place for a solution. Switch access. That worked but when that app was updated it broke again. With switch access on, volume buttons do not work. Every time I start up the phone or come back to it after a few hours, the setup wizard opens. And occasionally it will just pop up TalkBack has crashed. Another side effect of Switch Access is the YouTube video ui won't fade away. You have to tap the "X" ; and sometimes there is no "X" there at all.
It's a cycle. No audio que? Turn on switch access. With Switch access on, volume buttons do not work. TalkBack crashes occasionally. Setup wizard opens.
I'm so unspeakably frustrated this has been an issue for so long. What the hell do I do!? I have ran into this issue since Google updated their app years ago, not longer after I got an HTC One M7. Since then I have had this issue on that phone, a Samsung Note 5, Moto G, Nexus and Pixel.
I have not made any changes to my phone settings but recently I noticed Tasker stopped working when the screen is locked. I use AutoRemote to receive a timed message from IFTT which is used in a profile in Tasker to execute some tasks. This has worked flawlessly for months but recently it stopped. The profile and task work correctly when the screen is on though. I have tried all the various battery and Tasker settings but cannot seem to fix this new problem.
Anyone else having this problem?
After April update I bumped several times into new strange behavior of Clock app in Alarm section - it shows blank screen and it stops creating new alarms until reboot. I tried to switch between screens of the App, shot it down and relaunched, but with no luck. It happens not every time, but at least a couple times. At least twice after a message that Stand App stopped work. I put my P3 at stand and when I needed to set alarm, it did two things in different order - showed blank Alarm screen and a message that Stand App stopped working. Can not say for sure it's connected. I don't use Assistant for setting alarms after it sets alarm for the next day. Luckily I woke up myself and decided not to take risks with artificial intelligence - look like it tries to be too smart for such a simple task, so not sure if the same problem can arise with Assistant.
Just wondering if anybody's got similar problem and fixed it?