I noticed that my OK Google was not functioning the other day so I went into the Google Assistant settings and noticed that "Say OK Google any time" was switched off. I went in and switched it back on, but when I go back in it is switched off every time.
Anyone else notice this? Saying OK google still seems to work, just thought it was odd...
A.
yeah I noticed that too on TMO s7e also causes my battery to drain
I too noticed that as well. I uninstalled updates and then reinstalled app. Same result.
Related
Is anyone having trouble with deep sleep after update of Google Play Services 5.0.77 ?
I've installed the apk from android police and since then my deep sleep is gone. Fortunatelly i've identified the trouble and uninstalled the version, but i would like to know if anyone else had trouble with this update.
Note: I've tried to install it many times and it always vanishes my deep sleep.
prog19 said:
Is anyone having trouble with deep sleep after update of Google Play Services 5.0.77 ?
I've installed the apk from android police and since then my deep sleep is gone. Fortunatelly i've identified the trouble and uninstalled the version, but i would like to know if anyone else had trouble with this update.
Note: I've tried to install it many times and it always vanishes my deep sleep.
Click to expand...
Click to collapse
My phone (Nexus 5, Cyanogenmod 11 M7) update Google Play Services automatically to 5.0.84 and I've had the same issue. Over the course of today, it's used a good deal of my battery and prevented my phone from sleeping. I've tried changing my location settings, disabling wi-fi (and wi-fi location) and nothing seems to allow my phone to sleep.
I remember having this problem before, but I was thinking that I simply restarted it to fix it. That's not doing anything this time.
This is working for me on CM11 M7. Install Disable Service then go to "system apps" > "Google Play Services" and check "SystemUpdateService".
I tried disabling location services and related settings one at a time to try to figure out what exactly was causing the problem, but none of that worked. Eventually I uninstalled the updates to Google Play Services and that let my phone go back into deep sleep. After that, I re-enabled my settings, one at a time, to see if one of them triggered the problem again. Fortunately, I've enabled everything that I had before and my phone seems to be deep sleeping like normal.
Once again note that I am using a Nexus 5 rather than a 4, but I would think that the solution could work on both.
Voice trained it the first time, and it seemed to be working. Waited a few minutes and kept repeating OK Google from off screen and nothing, went in retrained it nothing...deleted voice pattern, tried it again. Anyone else finding its very flakey?
As bas as ok google is s-voice works everytime
So ok google doesnt seem to wake the phone up, at least on mine not working. So i tried hi galaxy, works like a charm all the time so much for ok google.
Mine wakes up when screen is off for about an hour after trained, then it just decides not to.
Works perfectly for me, screen off, screen on, locked screen... perhaps you should not have set up S-voice too? I have not touched S-voice as there is no need for both apps.
abacus0101 said:
Voice trained it the first time, and it seemed to be working. Waited a few minutes and kept repeating OK Google from off screen and nothing, went in retrained it nothing...deleted voice pattern, tried it again. Anyone else finding its very flakey?
Click to expand...
Click to collapse
I didnt set up s voice, i only resorted to it after ok google from sleep wasnt working. I had experience like other op where it worked then waited a few minutes and dint work. One app has nothing to do with other app, theyvare completely independant. Anyway to each their own enjoy ok google, lol
go to settings > Language and input
click on the gear button next to Google voice typing
click on OK Google detection
select the options to have OK google on on lock screen and when screen is turned off
Yeah I was playing with it last night and it seemed to have ignored me after awhile when the phone was off.
So maybe the phone is actually going into sleep mode fully.
The "ok google " hot word was working when I got my phone several days ago, even with the screen off. Now suddenly today, It just stopped working. Now, in the "ok google" detection field under google now settings, the top section is still checked, "from google search app", but "always on" and "when locked" boxes are now both greyed out. The "retrain" and "delete voice model" boxes are also greyed out. They were not when I originally got the phone. This apparently happened today, and I havent messed with any of the settings. Plus I see no sign of an update to google now that might have casued a change like this within the app.
The most interesting thing though, as I mentioned in the title is that the "always on" box is now saying that this feature is currently unavailable for this language....which is english / US....wtf
This will happen if you disable S Voice.
Ohhhh, well **** why does this feature need svoice to work? This some stupid touchwiz thing? I didnt even have svoice on my s4, (titanium backup ftw) and it worked fine. Except for the screen off option, which wasnt available in 4.3
Thanks, I had this issue, at first ok google was working on any screen which was pretty cool, then yesterday I noticed it wasn't working any longer, I forgot S-Voice needs to be working, I disabled it a few days back, better switch it back on
Sadly, the ability of my s5 (Kitkat 4.4.2 SM-6900T NK2) to respond to "OK Google" from any screen is very, very unreliable these days. If I go back to an earlier version of Google Search, sometimes it will work again. If I update to the latest version, sometimes that will work for a day, then it breaks again. Sometimes if I just retrain it to recognize me saying OK Google, it will work for a while.
While it's broken, I can even try OK Google from the screen the widget is on, and nothing happens.
This is really annoying. I've made sure that all the required options are selected, such as audio history on, from google search app, from any screen, and from lock screen.
Is anyone else having this same problem?
Tried clearing data & cache for the actual app itself?
Starting this week I've been experiencing a serious battery drainage in my device.
I've noticed this drainage happens at a time when Location Services appear to be working, for no apparent reason.
Now, I always have Location Services on, but I can never see it in the upper bar (the one where you can see the time, Wi-Fi connection, battery) unless I use an app that relies on it.
However, in the past few days, I see Location Services up there even though I'm not using any app that relies on it. What's worse is that it stays there even after I close all apps. In regular cases it tends to remain there as long as the app that needs it is running. As soon as I close the app, Location Services disappear from the upper bar.
If I turn off Location Services it will go away. However, once I turn it on it will be up there again. It will only go away if I reboot my phone.
Do you guys have any idea what may be causing this? I bought by Nexus 6p by the end of February and hadn't experienced this issue until this week. Before that, my battery usage was normal, and I could go a full day without having to charge my battery.
This issue, on the other hand, can drain my battery in the span of 1 or 2 hours.
Already noticed this problem and found the reason: Maps!
igorrj said:
Already noticed this problem and found the reason: Maps!
Click to expand...
Click to collapse
But I haven't used them.
For example, today I faced that problem solely by opening up Facebook. Then I rebooted my phone, opened up Facebook again but the problem didn't happen.
Now, I'm thinking this isn't happening by simply opening Facebook or Twiiter, but whenever I open them through the notification bar.
This is really odd.
I noticed the same battery drain. One night my phone batter wound up being pretty much dead. Today I noticed significant drain and when I looked at battery use, I saw where the consumption seemed to increase and observed the location services icon at the top of the phone that wouldn't go away even after making sure all apps were shut down. I don't really have many apps on my phone (certainly not ones that need location, so I suspect a recent update to Maps.
My first step was to delete and reinstall the updates. so let's see if that fixes it. If not, I'll just remove the updates and run that way until another version comes out. I suspect is just a goofed install or we would hear far more complaints of this issue.
I was literally getting ready to make a post about this. Sure enough, force-closing Maps stopped the issue. Glad to see it wasn't just me.
I'm having the same issue. I get the location icon on my status bar at random times and it stays there until a reboot. It eventually comes back. Pretty annoying as it is causing my phone not to deep sleep. I'm on stock with Franco kernel.
Sent from my Nexus 6P using Tapatalk
I'm having the same issue on latest stock firmware on both my SM-N910T3 & SM-T700. Started noticing the location icon all the time about a week ago, just about when it came out with the latest update on 4/1.
Well, uninstalling and reinstalling the updates to Maps didn't fix anything. I have uninstalled the updates and will monitor.
ZabiGarma said:
But I haven't used them.
For example, today I faced that problem solely by opening up Facebook. Then I rebooted my phone, opened up Facebook again but the problem didn't happen.
Now, I'm thinking this isn't happening by simply opening Facebook or Twiiter, but whenever I open them through the notification bar.
This is really odd.
Click to expand...
Click to collapse
Facebook is, by far, the worst app you can have downloaded. It is the cause of general phone issues and bad battery life. I uninstalled both FB and FB messaging and my wake lock issue was fixed and, in turn, my battery life is noticeably better
Sent from my Nexus 6P using XDA-Developers mobile app
I did a full master reset of my phone and am only running default applications. I still get the runaway location services. Before I did that, I downgraded Maps and that seemed to help. But then my phone automatically updated it. I know I can probably fix that situation but I'm surprised we aren't seeing more people with the problem.
Nexus 5x owner here (but posting my experience since this is literally the only thread on this anywhere).
Symptoms: Similar to everyone in this thread, location icon was popping up and staying resident in the top status bar. This was happening even without an event launching and causing massive battery drain. This was atypical of usage since my phone is basically not even used (essentially a notification machine with light text usage).
Checking the location menu, everything was listed as light usage, except for Maps as heavy usage (even though Maps wasn't even launched or in the recents menu)
Variables: Unfortunately, since my phone has been perfect since launch, I haven't been paying attention to all the updates granularly to isolate what was causing this. But, I do know for sure it happened after the April Monthly update and after a Maps update.
Troubleshooting: I was hoping it wasn't a system update issue, so I started poking around in the Maps settings to see if maybe a new Maps service was launched that was auto-enrolling users and potentially causing battery drain. Nothing to note, but I did notice I was signed out of Maps, which seemed weird. So I went ahead and re-signed into Maps with my Google Account.
Results: I honestly didn't expect this to have any impact, but the location issue hasn't come up after signing into Maps. It's been ~ 3 weeks and 4 battery cycles since I've had the location issue.
I'm not sure if signing in helped or maybe a server side Maps update fixed the bug, but if you're still having the location issue, it's worth a shot to see if you're signed into Maps (and sign in to try to fix the location issue).
If this does work for you, please report back since it will help in data gathering (and also we can let Google know the exact details of the issue and the potential fix so this bug doesn't hit in future versions).