Is google now and "ok google" voice recognition hard on battery ?
michaelopolis said:
Is google now and "ok google" voice recognition hard on battery ?
Click to expand...
Click to collapse
No.
Regards, Zagor
michaelopolis said:
Is google now and "ok google" voice recognition hard on battery ?
Click to expand...
Click to collapse
Google Now "may" use a bit of battery if you're using location services along with it (naturally), but using it without location is somewhat negligible.
Having "OK Google" functionality enabled will use more than having it disabled; it's constantly polling your microphone. If you enable the options to have it enabled on every screen and not just the launcher, it'll use even more. If you enable it while the screen is off, your battery life would be pretty terrible. It requires a wakelock to be able to poll the microphone.
The Moto X achieves such functionality without significant battery drain due to the low-powered core on Snapdragon SoCs (and possibly other hardware). In the Nexus 5, however, that low-powered core is not used for this functionality and cannot be reprogrammed without legal repercussions with Qualcomm and possibly other 3rd parties.
Related
I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
jknolls said:
I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
Click to expand...
Click to collapse
With Location Services activated, it's doing exactly what your allowing. You're giving permission for apps to connect to Google's location services. A lot of apps that don't seem location based are actually doing background processes that are -- thus the wakelocks. And GPS/Location services are battery expensive.
My solution: I use Cyanogenmod that has widgets in the notification panel. When I press and hold the GPS Icon it brings me to the Location Services page. I will toggle the services when I actually need it, and allow for no wakelocks. Press the back button and you're back in action.
What worked for me is just turning off Google Now. Yeah you lose some functionality, but it doubles your battery life. Google really screwed up with this one. I really don't know who to blame, Google, Samsung, or Verizon. I dont get these wakelocks on my Nexus with the same app, so it might be something to do with what Samsung did with TW. No wakelocks on 4.2 either.
aooga said:
What worked for me is just turning off Google Now. Yeah you lose some functionality, but it doubles your battery life. Google really screwed up with this one. I really don't know who to blame, Google, Samsung, or Verizon. I dont get these wakelocks on my Nexus with the same app, so it might be something to do with what Samsung did with TW. No wakelocks on 4.2 either.
Click to expand...
Click to collapse
I've always had Google now off but the battery life still suffers considerably even with it off and just Google location services on.
jknolls said:
I've always had Google now off but the battery life still suffers considerably even with it off and just Google location services on.
Click to expand...
Click to collapse
Really? For me it helps on TW roms.
aooga said:
Really? For me it helps on TW roms.
Click to expand...
Click to collapse
Sure, Google now being off definitely helps but location services still chews up battery.
jknolls said:
I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
Click to expand...
Click to collapse
did you installed 4.2 or note camera, I used to have same problem but after uninstalling it becomes fine. Note camera have a google framework apk inside and I think the incompatibility causing the problem.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I've always noticed a lot of wake locks caused by Location services since upgrading to Jelly Bean. It seems to cause a bit of battery drain for me, primarily because it wakes the device so often (according to BBS). I don't need location updates while the screen is off. Googled for a bit and I found someone suggesting this profile with Tasker:
Trigger is display off
Add a task that runs this command:
pm disable com.google.android.location
Do the opposite when the display turns on, of course (doesn't really appear to cause any lag). I also disabled a few of the Google Now functions that I don't need. Now if I could figure out how to limit the awake time the stock email app uses, and I could see the idle usage dramatically go down.
Any thoughts?
Sent from my Nexus 7 using Tapatalk 2
This sounds like a good idea, has it panned out for you?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
It did work pretty well, but in the end it wasn't enough of a difference from disabling location reporting and all other Latitude functions. Also, I was kind of concerned about the possible CPU time used when disabling and enabling each time the screen state changed.
All in all, just disable Latitude and any functions in Google Now that you don't need. Also, disable location services in any application where you don't need them, like Facebook and Twitter.
Sent from my DROID RAZR HD using Tapatalk 2
RayLovesick said:
It did work pretty well, but in the end it wasn't enough of a difference from disabling location reporting and all other Latitude functions. Also, I was kind of concerned about the possible CPU time used when disabling and enabling each time the screen state changed.
All in all, just disable Latitude and any functions in Google Now that you don't need. Also, disable location services in any application where you don't need them, like Facebook and Twitter.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Yeah I'm pretty good with having nothing use location settings except Maps. Sometimes I won't get a single wakelock all night, other times I will get an hour and Google Now / any latitude apps are fully disabled. That's why I was curious as to your success.
Also, turning on the lock screen hotword detection - will this destroy my battery life, or will it be negligible?
It´s nothingfor the Batterie. You can turn it allways on.
LooksLikeSony said:
It´s nothingfor the Batterie. You can turn it allways on.
Click to expand...
Click to collapse
Erm... If our Z3 is "always listening", it cannot switch to "CPU sleep mode" as it's CPU is constantly busy with analyzing audio streams.
So there MUST be a noticeable impact on battery life.
Chefproll said:
Erm... If our Z3 is "always listening", it cannot switch to "CPU sleep mode" as its CPU is constantly busy with analyzing audio streams.
So there MUST be a noticeable impact on battery life.
Click to expand...
Click to collapse
OK Google does not work when the display is off, so it can go into deep sleep. I use it and have not noticed significant battery drain
'Always' is a little misleading. It's only listening when the screen is on and unlocked.
3Shirts said:
'Always' is a little misleading. It's only listening when the screen is on and unlocked.
Click to expand...
Click to collapse
Not quite true. It is ALWAYS listening when the screen is on. Mine works even from the lockscreen, if you change the language to English US the options are enabled in the "OK Google" detection settings.
gregbradley said:
OK Google does not work when the display is off, so it can go into deep sleep. I use it and have not noticed significant battery drain
Click to expand...
Click to collapse
Ah, I see !
Didn't have the chance of trying out myself, even after using "Ok Google everywhere" and switching the main language to English and activating the feature in the options; just did not work.
But if it doesn't work with the screen off, I don't see too much sense in it: I regard that "always listening" feature as a nice add-on if you're wearing a headset, allowing you to keep the phone in your pocket. As this does not work, I can easily live without it.
Chefproll said:
Ah, I see !
Didn't have the chance of trying out myself, even after using "Ok Google everywhere" and switching the main language to English and activating the feature in the options; just did not work.
But if it doesn't work with the screen off, I don't see too much sense in it: I regard that "always listening" feature as a nice add-on if you're wearing a headset, allowing you to keep the phone in your pocket. As this does not work, I can easily live without it.
Click to expand...
Click to collapse
But how about this, when I have it in my car attached to a Bluetooth speaker and on charge, I can leave the screen on and use OK Google from the lockscreen without having to touch the phone, hence I am not breaking any UK driving laws which basically say you cannot touch the phone to operate it, you need a full handsfree kit (Including when dialing and answering, not just speaking)
Just wondering how much battery drain everyone is getting from having Google assistant running with all its permissions. I'm aware it's one of the biggest causes of wakelocks. Just had it enabled since having it disabled for a month. Also do you have it always listening?
Hello,
I would like to somehow set Google assistant "ok Google" command listening to be active only when screen is on / phone is unlocked. By default phone listens for "ok Google" even when screen is off which is creepy / probably drains battery and its totally useless as assistant cannot do anything when phone is locked and Voice Match to unlock screen is not working anyway. Any advice?
BTW I'm rooted with magisk on OOS 9.5.9 so I'm open to any solution.
I have disabled Ok Google detection for a 1.5 days now and I think standby drain improved significantly, I was getting about 1,5% / h and now 0,5%! So it is big difference but still I would like to use assistant with OK Google when screen is unlocked..
Anybody knows a way do to it? Maybe using Tasker/automate?
spawnn617 said:
Hello,
I would like to somehow set Google assistant "ok Google" command listening to be active only when screen is on / phone is unlocked. By default phone listens for "ok Google" even when screen is off which is creepy / probably drains battery and its totally useless as assistant cannot do anything when phone is locked and Voice Match to unlock screen is not working anyway. Any advice?
BTW I'm rooted with magisk on OOS 9.5.9 so I'm open to any solution.
Click to expand...
Click to collapse
1. It doesn't drain battery because its not handled by the CPU, but by the DSP.
2. You cant turn it off only for screen off.
matze19999 said:
1. It doesn't drain battery because its not handled by the CPU, but by the DSP.
2. You cant turn it off only for screen off.
Click to expand...
Click to collapse
Assuming DSP doesn't use battery?
The assistant regularly polls GPS for updated weather, occasionally sends data to google when idle, monitor it for a day and see what it does.
I sometimes sends snippets of voice before and after ok Google
virtyx said:
Assuming DSP doesn't use battery?
The assistant regularly polls GPS for updated weather, occasionally sends data to google when idle, monitor it for a day and see what it does.
I sometimes sends snippets of voice before and after ok Google
Click to expand...
Click to collapse
I'll say it with other words - you wouldn't notica a difference in battery life if you could turn it off. And if you do => Placebo
virtyx said:
Assuming DSP doesn't use battery?
The assistant regularly polls GPS for updated weather, occasionally sends data to google when idle, monitor it for a day and see what it does.
I sometimes sends snippets of voice before and after ok Google
Click to expand...
Click to collapse
Exactly my point. DSP must still drain battery, of course less than CPU (if it would be handled by CPU then it would never go to deep sleep...) but for sure it takes some + all the stuff around it (gps/data transfer etc).
No workaround? Maybe a widget or something?