How To Improve Your Nexus 7’s Battery Life in Lollipop - Nexus 7 (2013) General

I got tired of my Nexus 7 draining its battery just sitting there in standby. Even if I turned the tablet all the way off, somehow the battery still drained itself (more slowly, but still…). I came up with the tips below so that I wouldn’t have to turn off the Nexus 7 completely between uses. I believe that a tablet should be in standby and ready to go at all times.
I now get more than a week of battery life in standby. For the first time, I feel like my Nexus 7 is a useful alternative to my iPad Air.
The biggest battery drain culprit during idle time is behind-the-scenes software — continuously running, polling the Internet, or updating. On a Google device such as the Nexus series, most of that power-hungry activity comes from Google itself. So here’s what we're gonna do. Before we get to the Google stuff, let’s tweak some overall settings and Play Store settings to reduce battery drain in those areas:
First, let’s make sure you’re on the latest OS version for the 2013 version of the Nexus 7. (I’m guessing these settings will work in the 2012 version also, but I don’t know for sure.) In Settings, swipe down to About Tablet, choose that, then swipe down to “Android version”. When I wrote this in mid-February 2015, the latest OS version was 5.0.2. Check for updates on the same screen, and update to the latest version if necessary. If rooted, install the latest custom ROM of your choice.
Once updated:
Hit your Play Store icon. Click the three-bar menu at the top left. Select “Settings” near the bottom.
Under “Auto-update apps,” choose “Do not auto-update apps.” (Why? Because that “feature” uses battery juice to download and install stuff whenever it feels like it, instead of whenever you say.)
On the same page, under Notifications, make sure “Notify me about updates to apps or games that I downloaded” is checked. That way you will know if something needs updating.
On the same page, uncheck “Add icon to Home screen for new apps.” Because it’s annoying, not because it uses battery.
Go to your tablet’s Settings.
Choose “Wi-Fi”.
Tap the three-dot symbol at top right.
Tap “Advanced.”
Make sure “Scanning always available” is unchecked.
On the same settings screen, under “Keep Wi-Fi on during sleep,” choose “Never”. (Don’t worry: If Wi-Fi is enabled, it will wake up instantly every time you turn on the tablet.)
While in Settings, let’s turn off some radios:
If you don’t travel with your tablet, disable Location (GPS).
If you don’t use Near Field Communication (NFC) for tap-to-pair features, disable that. You can always re-enable it when ready.
Disable Bluetooth when not using it.
Obviously, keep your device’s screen brightness as low as is comfortable. (The display is the biggest power hog on your device.) You can change the display brightness settings under Settings, Display.
While in Display Settings, disable Ambient Display. (Well, first Google it, because you might actually like the feature. But I think it’s more of a smartphone feature than a tablet feature.)
When disabling or uninstalling Google apps, DO NOT uninstall anything essential to the smooth running of your tablet. That includes:
Google Search
Google Chrome (unless you replace it with another browser)
Google Settings
Hangouts (you can disable Hangouts once you’ve replaced it with an aftermarket texting app)
Google Now (although we will disable many of its features and opt-out later)
Google Play
Gmail
Now let’s clean up a few apps. We will stay away from system apps, such as Email — because people can get into trouble uninstalling essential system apps.
It’s impossible to know every time an app is working in the background or polling the Internet. So, in my opinion, you should uninstall any app that you didn’t specifically put on the tablet yourself (system apps not included). For example, I uninstalled:
Google Earth
Google +
Hangouts (after I replaced it with Textra)
Google Docs
Google Drive
Google Sheets
Google Slides
Google Fit
Any downloaded apps I’m no longer using, such as wallpaper apps.
For smartphone owners, Google Now can be a godsend — always reminding you of what’s next, keeping you out of traffic jams, and keeping you on schedule. But tablet owners might not need the features. Additionally, with Google Now, the Nexus 7 mic is always on and listening for that “OK Google” search command — which obviously uses battery power and is more of a smartphone than tablet feature.
I found that I didn’t need Google Now at home, where my Nexus 7 is 100% of the time. If you’re like me, you can opt-out of Google Now — or at least stop the mic from listening.
We’ll start with the least draconian measure: stopping the mic from listening for the “OK Google” command from any screen:
From your main home screen, swipe up to get to the Google Now screen.
Tap the three-bar symbol at top left.
Choose Settings.
Choose Voice.
Choose “OK Google” Detection.
Uncheck “From any screen.” Leave “from the Google app” checked, then Google can listen for the command only when you have a search window open.
If you don’t want Google Now at all (I don’t like it because it’s always updating something or doing something in the background), here’s how you disable it completely, while leaving full Google Search functionality intact:
Start by disabling “OK Google” voice detection for screens other than Google Search as shown above (or you can disable it in Google Settings below).
Then, in your Applications, open the Google Settings app.
Tap “Search & Now”.
Tap “Now cards.”
Uncheck “Show cards.”
You will see a message that asks if you really want to turn off Google Now. Go ahead and do that.
From now on, you can still easily search by swiping your finger up from the bottom of any Home screen. And you can still do voice searches by tapping the microphone on any Google Search screen.
I hope these battery-saving features do as much for you as they did for me!

Thanks for the tips, always good to know. :highfive:
I'd like to add that "Google Location Reporting," is a battery hog and seems to make little difference if turned off. With it turned off, my devices still know roughly where I am. :cyclops:

In Settings, under Sound and Notification, go to “other sounds.” Uncheck “Vibrate on touch.”
Click to expand...
Click to collapse
Ummmmmmmmmmmmmmmmmmmmmmmmmmm..... So where did you copy and paste this guide from?

khaytsus said:
Ummmmmmmmmmmmmmmmmmmmmmmmmmm..... So where did you copy and paste this guide from?
Click to expand...
Click to collapse
I typed it myself while looking at my own device. It took hours. But yeah, that one I got wrong because I was looking at my rooted Nexus 7 at the time, not my stock one. But no need to get snarky because you found the one error in a four-page Word document--just try to help next time, okay?

Masteryates said:
Thanks for the tips, always good to know. :highfive:
I'd like to add that "Google Location Reporting," is a battery hog and seems to make little difference if turned off. With it turned off, my devices still know roughly where I am. :cyclops:
Click to expand...
Click to collapse
That's a great tip! Thanks for adding it. Hopefully, others will chime in with even more!

TheContinental said:
I typed it myself while looking at my own device. It took hours. But yeah, that one I got wrong because I was looking at my rooted Nexus 7 at the time, not my stock one. But no need to get snarky because you found the one error in a four-page Word document--just try to help next time, okay?
Click to expand...
Click to collapse
Okay, perhaps your custom ROM is incorrectly reporting then, because there's no vibration on the Nexus 7.

khaytsus said:
Okay, perhaps your custom ROM is incorrectly reporting then, because there's no vibration on the Nexus 7.
Click to expand...
Click to collapse
Good catch! I just edited that part out of the guide. I found out where the mistake came from. I'm currently also writing one of these for the Nexus 5. So...my bad...you were right! It was a copy/paste error...from my own guide!
Thank you for clearing that up.

Nexus 7 Draining Big Time
TheContinental said:
I got tired of my Nexus 7 draining its battery just sitting there in standby. Even if I turned the tablet all the way off, somehow the battery still drained itself (more slowly, but still…). I came up with the tips below so that I wouldn’t have to turn off the Nexus 7 completely between uses. I believe that a tablet should be in standby and ready to go at all times.
I now get more than a week of battery life in standby. For the first time, I feel like my Nexus 7 is a useful alternative to my iPad Air.
The biggest battery drain culprit during idle time is behind-the-scenes software — continuously running, polling the Internet, or updating. On a Google device such as the Nexus series, most of that power-hungry activity comes from Google itself. So here’s what we're gonna do. Before we get to the Google stuff, let’s tweak some overall settings and Play Store settings to reduce battery drain in those areas:
First, let’s make sure you’re on the latest OS version for the 2013 version of the Nexus 7. (I’m guessing these settings will work in the 2012 version also, but I don’t know for sure.) In Settings, swipe down to About Tablet, choose that, then swipe down to “Android version”. When I wrote this in mid-February 2015, the latest OS version was 5.0.2. Check for updates on the same screen, and update to the latest version if necessary. If rooted, install the latest custom ROM of your choice.
Once updated:
Hit your Play Store icon. Click the three-bar menu at the top left. Select “Settings” near the bottom.
Under “Auto-update apps,” choose “Do not auto-update apps.” (Why? Because that “feature” uses battery juice to download and install stuff whenever it feels like it, instead of whenever you say.)
On the same page, under Notifications, make sure “Notify me about updates to apps or games that I downloaded” is checked. That way you will know if something needs updating.
On the same page, uncheck “Add icon to Home screen for new apps.” Because it’s annoying, not because it uses battery.
Go to your tablet’s Settings.
Choose “Wi-Fi”.
Tap the three-dot symbol at top right.
Tap “Advanced.”
Make sure “Scanning always available” is unchecked.
On the same settings screen, under “Keep Wi-Fi on during sleep,” choose “Never”. (Don’t worry: If Wi-Fi is enabled, it will wake up instantly every time you turn on the tablet.)
While in Settings, let’s turn off some radios:
If you don’t travel with your tablet, disable Location (GPS).
If you don’t use Near Field Communication (NFC) for tap-to-pair features, disable that. You can always re-enable it when ready.
Disable Bluetooth when not using it.
Obviously, keep your device’s screen brightness as low as is comfortable. (The display is the biggest power hog on your device.) You can change the display brightness settings under Settings, Display.
While in Display Settings, disable Ambient Display. (Well, first Google it, because you might actually like the feature. But I think it’s more of a smartphone feature than a tablet feature.)
When disabling or uninstalling Google apps, DO NOT uninstall anything essential to the smooth running of your tablet. That includes:
Google Search
Google Chrome (unless you replace it with another browser)
Google Settings
Hangouts (you can disable Hangouts once you’ve replaced it with an aftermarket texting app)
Google Now (although we will disable many of its features and opt-out later)
Google Play
Gmail
Now let’s clean up a few apps. We will stay away from system apps, such as Email — because people can get into trouble uninstalling essential system apps.
It’s impossible to know every time an app is working in the background or polling the Internet. So, in my opinion, you should uninstall any app that you didn’t specifically put on the tablet yourself (system apps not included). For example, I uninstalled:
Google Earth
Google +
Hangouts (after I replaced it with Textra)
Google Docs
Google Drive
Google Sheets
Google Slides
Google Fit
Any downloaded apps I’m no longer using, such as wallpaper apps.
For smartphone owners, Google Now can be a godsend — always reminding you of what’s next, keeping you out of traffic jams, and keeping you on schedule. But tablet owners might not need the features. Additionally, with Google Now, the Nexus 7 mic is always on and listening for that “OK Google” search command — which obviously uses battery power and is more of a smartphone than tablet feature.
I found that I didn’t need Google Now at home, where my Nexus 7 is 100% of the time. If you’re like me, you can opt-out of Google Now — or at least stop the mic from listening.
We’ll start with the least draconian measure: stopping the mic from listening for the “OK Google” command:
From your main home screen, swipe left until you get to the Google Now screen.
Tap the three-bar symbol at top left.
Choose Settings.
Choose Voice.
Choose “OK Google” Detection.
Uncheck both “from the Google app” and “From any screen.”
If you don’t want Google Now at all (I don’t like it because it’s always updating something or doing something in the background), here’s how you disable it completely, while leaving full Google Search functionality intact:
Start by disabling “OK Google” voice detection as shown above.
Then, in your Applications, open the Google Settings app.
Tap “Search & Now”.
Tap “Now cards.”
Uncheck “Show cards.”
You will see a message that asks if you really want to turn off Google Now. Go ahead and do that.
From now on, you can still easily search by swiping your finger up from the bottom of any Home screen. And you can still do voice searches by tapping the microphone on any Google Search screen.
I hope these battery-saving features do as much for you as they did for me!
Click to expand...
Click to collapse
This is fantastic -- thank you!
I just upgraded my Nexus 7 (2013 LTE) to Lollipop and its battery usage tanked. I finally got a good view of how bad it was this morning. I plugged it in last night but left it running (all radios except WiFi off (including mobile data off), display off) and it charged all night. When I checked on it this morning it had actually *lost* battery charge overnight. The battery display page shows that it had been charging all night but still steadily, albeit slowly, losing charge (went from about 51% to about 47% by morning).
I turned the device off and plugged it back in; within a couple of hours it was back up to about 70%.
From various forums it appears that people have wildly varying experience with this on their Nexus devices, including the Nexus 7, with some reporting good battery charge retention, so my first guess is that one or more of my roughly 160 apps is sucking on the battery heavily.
I'm doing a factory reset now and will then try the recharge scenario again (wherein I leave the device on while recharging) and will see what happens with the "clean" version. I'm also going to turn off WiFi, which I know will introduce a significant change, but I want to make sure there is no background WiFi activity going on either (e.g., downloading all my Google apps again).
I'll post the results of my "test".
Barry

^160 apps that's the problem. Use BBS to see what's keeping it up. You can leave WiFi on, I have all location, WiFi, now, ok google everywhere etc on and consistently get 8 hours screen time over 2 days or 7 hours over 3 days.

I've seen the difference (in negative way) of the battery in lollipop too.
I have a rooted n7 lte.
In addition to these tips, I installed "disableservice" from play store and disabled all the wear related service in android google play service and Google music.
Now on the list of battery consuming apps the Google play service is no more the first one.
I've read somewhere that the wear parts of play service consumes a lot of battery and I don't have android wear.
Only my two cents.
Bye

xranix said:
I've seen the difference (in negative way) of the battery in lollipop too.
I have a rooted n7 lte.
In addition to these tips, I installed "disableservice" from play store and disabled all the wear related service in android google play service and Google music.
Now on the list of battery consuming apps the Google play service is no more the first one.
I've read somewhere that the wear parts of play service consumes a lot of battery and I don't have android wear.
Only my two cents.
Bye
Click to expand...
Click to collapse
Great tips! Thanks for adding to the discussion!

yosmokinman said:
^160 apps that's the problem. Use BBS to see what's keeping it up. You can leave WiFi on, I have all location, WiFi, now, ok google everywhere etc on and consistently get 8 hours screen time over 2 days or 7 hours over 3 days.
Click to expand...
Click to collapse
Nonsense, he has some other issue. Unless he has 160's "facebook" apps.

Questions: fyi I have stock 2013 5.0.2
When I try to disable NFC, it greys out and then turns itself back on.
I can't find the Google Now screen when swiping left.
TheContinental said:
For smartphone owners, Google Now can be a godsend — always reminding you of what’s next, keeping you out of traffic jams, and keeping you on schedule. But tablet owners might not need the features. Additionally, with Google Now, the Nexus 7 mic is always on and listening for that “OK Google” search command — which obviously uses battery power and is more of a smartphone than tablet feature.
I found that I didn’t need Google Now at home, where my Nexus 7 is 100% of the time. If you’re like me, you can opt-out of Google Now — or at least stop the mic from listening.
We’ll start with the least draconian measure: stopping the mic from listening for the “OK Google” command:
From your main home screen, swipe left until you get to the Google Now screen.
Tap the three-bar symbol at top left.
Choose Settings.
Choose Voice.
Choose “OK Google” Detection.
Uncheck both “from the Google app” and “From any screen.”
If you don’t want Google Now at all (I don’t like it because it’s always updating something or doing something in the background), here’s how you disable it completely, while leaving full Google Search functionality intact:
Start by disabling “OK Google” voice detection as shown above.
Then, in your Applications, open the Google Settings app.
Tap “Search & Now”.
Tap “Now cards.”
Uncheck “Show cards.”
You will see a message that asks if you really want to turn off Google Now. Go ahead and do that.
From now on, you can still easily search by swiping your finger up from the bottom of any Home screen. And you can still do voice searches by tapping the microphone on any Google Search screen.
I hope these battery-saving features do as much for you as they did for me!
Click to expand...
Click to collapse

peaceridge said:
Questions: fyi I have stock 2013 5.0.2
When I try to disable NFC, it greys out and then turns itself back on.
I can't find the Google Now screen when swiping left.
Click to expand...
Click to collapse
If you swipe left on your home screen and don't get Google Now, then Google Now is not activated on your device. If Google Now is activated, when swiping left on your home screen, you'll see a full-screen view of Google Now and its helpful cards.
Sorry, I don't know what to make of your NFC turning itself back on. Of course, NFC won't work at all if Bluetooth is off, so you can defeat it that way.

TheContinental said:
If you swipe left on your home screen and don't get Google Now, then Google Now is not activated on your device. If Google Now is activated, when swiping left on your home screen, you'll see a full-screen view of Google Now and its helpful cards.
Sorry, I don't know what to make of your NFC turning itself back on. Of course, NFC won't work at all if Bluetooth is off, so you can defeat it that way.
Click to expand...
Click to collapse
Thanks, really appreciate your help on the battery issue! I've got Bluetooth off, so that should be fine, then. I'm contemplating going back to 4.4, but haven't had time to research that yet. Again, thanks for your help.

If I remember well, swiping left on homscreen, on nexus tablets do not activate google now, but swiping up from the bottom of the screen, if it's activated it will turn on.

sale 83 said:
If I remember well, swiping left on homscreen, on nexus tablets do not activate google now, but swiping up from the bottom of the screen, if it's activated it will turn on.
Click to expand...
Click to collapse
You're right! My bad, I think I was thinking of my Nexus 5, where you swipe left. The procedures to disable Google Now are the same with both devices, though.

TheContinental said:
If you swipe left on your home screen and don't get Google Now, then Google Now is not activated on your device. If Google Now is activated, when swiping left on your home screen, you'll see a full-screen view of Google Now and its helpful cards.
Sorry, I don't know what to make of your NFC turning itself back on. Of course, NFC won't work at all if Bluetooth is off, so you can defeat it that way.
Click to expand...
Click to collapse
NFC and Bluetooth are completely unrelated.
As for the problem; I don't know but I'd have to guess that NFC is required somewhere, like perhaps Smart Lock is enabled or something else that's needing NFC? Wallet? Something like that. I can turn off NFC on my N7 Flo.
That said.. NFC uses almost zero power, so IMO it's not even worth worrying about having disabled.

khaytsus said:
NFC and Bluetooth are completely unrelated.
As for the problem; I don't know but I'd have to guess that NFC is required somewhere, like perhaps Smart Lock is enabled or something else that's needing NFC? Wallet? Something like that. I can turn off NFC on my N7 Flo.
That said.. NFC uses almost zero power, so IMO it's not even worth worrying about having disabled.
Click to expand...
Click to collapse
NFC and Bluetooth are indeed related, but not in the way I originally thought. NFC uses an RFID-like protocol to make a connection, then Bluetooth to transfer any info (files, etc.). So, a user would need Bluetooth powered on for NFC to work, but not the other way around.

khaytsus said:
NFC and Bluetooth are completely unrelated.
As for the problem; I don't know but I'd have to guess that NFC is required somewhere, like perhaps Smart Lock is enabled or something else that's needing NFC? Wallet? Something like that. I can turn off NFC on my N7 Flo.
That said.. NFC uses almost zero power, so IMO it's not even worth worrying about having disabled.
Click to expand...
Click to collapse
No. They are completely unrelated. They work completely independent of each other.

Related

[APP] Mod to replace S-Voice with Google Voice Search (no root necessary!)

Would it be possible? Including the voice wake functionality "Okay, Google Now" instead of "Hi Galaxy"?
How many would be interested in something like this?
Should not be too hard to do, what do you think?
Probably will need root to achieve it
----
SOLVED: using a very simple tasker profile/action (see here)
UPDATE: Install this tiny free app from the Play store: https://play.google.com/store/apps/details?id=hu.viczian.deathtosvoice (created using Tasker App Factory)
Works on galaxy advancement
vgergo said:
Would it be possible? Including the voice wake functionality "Okay, Google Now" instead of "Hi Galaxy"?
How many would be interested in something like this?
Should not be too hard to do, what do you think?
Probably will need root to achieve it
Click to expand...
Click to collapse
Works on galaxy advancement? thank you
Leonardosilvaa said:
Works on galaxy advancement? thank you
Click to expand...
Click to collapse
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Presjar said:
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Click to expand...
Click to collapse
Any idea how to replicate this?
Presjar said:
For some reason, I can now double tap home button and I get the option for S-voice or Google voice. I think I cleared the defaults in app settings.
Click to expand...
Click to collapse
Yeah I got this too. It happened after I installed SoundHound.
Now I have the options of
Google
S Voice
SoundHound
Interesting but without the option to activate gvoice with screen off its not a huge benefit. I tested open mic+ but it lacks admin rights to bypass the lockscreen etc.
vinokirk said:
Yeah I got this too. It happened after I installed SoundHound.
Click to expand...
Click to collapse
The free version? I've tried that but I don't see a menu after double clicking home.
mgutt said:
Interesting but without the option to activate gvoice with screen off its not a huge benefit. I tested open mic+ but it lacks admin rights to bypass the lockscreen etc.
Click to expand...
Click to collapse
You mean root permissions?
Sorry, I was wrong. I thought S-Voice is able to bypass a pin lockscreen but it isn't. It is only admin (not root) to allow the screen off command.
The problem of open mic+ is, that it is buggy. It seems to freeze after a short time. Sometimes Google Now freezes as well so I think it is because of Open Mic+ but I didn't tested it enough to verify it. S-Voice seems to be more stable, but is not present if you are in other apps like Maps.
But both systems are too weak in rights. e.g. I'm not able to stop apps (ok root would be needed), not able to say my lockscreen pin, stop a phone call, etc.
Tasker
I just had an idea: it should be possible to create a very simple tasker action, which would be triggered by opening s-voice. It would exit s-voice and switch immediatelly to Google Voice Search. This should work even without rooting.
If this would work, all the convenient ways to start S-Voice would become actually useful to start Google Voice search, including voice-wake, home-double-click, headset-long-press.
I will try this as soon as I get my N3
How do you want to exit S-Voice without root
There's the point! Okay, without root we can just switch away (would mic input focus stay? that would be a problem), with root it should be possible to kick s-voice too.
If one app opens the mic the other will display an error.
Tasker solution works well on unrooted phone
mgutt said:
If one app opens the mic the other will display an error.
Click to expand...
Click to collapse
I am happy to report, that the solution I came up with before I had access to the Note 3 works without a hitch.
1. Enable wake-up hotword detection in S-Voice (keep double click Home if you like that too)
2. Create "S Voice" app-triggered tasker profile
3. The activated task should load "Voice Search"
4. Optional step: after starting voice search, my task also kills S-Voice to save memory
(and killing s-voice every time makes you me good)
There is no concurrency problem with the mic (as we were anticipating)
Say "Hi galaxy" while having the screen turned off
(I actually like to "say Die galaxy")
phone wakes up,
home screen unlocks,
s-voice flashes on screen for half a sec (beeps too)
then google voice search appears immediately
it too beeps and listens for the search term or command
Next project: it would be nice to be able to change the "hi galaxy" wake up command
The changeable wake up command is part of the Galaxy S4 S-Voice so I think it will be part in the Note 3 in one of the next updates (hopefully).
Of course I tested your idea, too. But it seems that it works better with Llama than with Tasker as Google Voice starts immediately. As I'm not rooted its not as perfect as yours (I need to tap backwards fast to bypass restarting Google Voice), but the goal is reached
Look:
http://www.maxrev.de/google-sprachsuche-statt-s-voice-mp4-v377253.htm
Update:
Ok I found a better solution. Know I'm using three rules instead of one and this is how it works:
Final Demo Video
The first rule starts Google Voice, but checks if the variable "googleSearch" is not 1 (this is important as it fails, too if the variable does not exist after rebooting the device). The second rules sets the var to "1" if Google Voice is open. The last rule resets the var to "0" with a delay of 3 seconds after Google Voice has been closed. So I'm having 3 seconds to close S Voice before Google Voice would start again.
If you don't want to here the "ping" sound of S Voice after closing Google Voice it would be possible to mute the device for 3 seconds as well, but I don't think this is really important
mgutt said:
The changeable wake up command is part of the Galaxy S4 S-Voice so I think it will be part in the Note 3 in one of the next updates (hopefully).
Of course I tested your idea, too. But it seems that it works better with Llama than with Tasker as Google Voice starts immediately. As I'm not rooted its not as perfect as yours (I need to tap backwards fast to bypass restarting Google Voice), but the goal is reached
Look:
http://www.maxrev.de/google-sprachsuche-statt-s-voice-mp4-v377253.htm
Update:
Ok I found a better solution. Know I'm using three rules instead of one and this is how it works:
Final Demo Video
The first rule starts Google Voice, but checks if the variable "googleSearch" is not 1 (this is important as it fails, too if the variable does not exist after rebooting the device). The second rules sets the var to "1" if Google Voice is open. The last rule resets the var to "0" with a delay of 3 seconds after Google Voice has been closed. So I'm having 3 seconds to close S Voice before Google Voice would start again.
If you don't want to here the "ping" sound of S Voice after closing Google Voice it would be possible to mute the device for 3 seconds as well, but I don't think this is really important
Click to expand...
Click to collapse
thats excellent Mgutt
the note does the transition across to google now/voice commands very quickly.. you have put the note back on the table as an option for my next phone.. im just holding out to see if the LG G2 will use the S800 for always on listening when it gets kitkat..
Im a bit spooked by AMOLED now that my galaxy S2 is marred by burn in
etherspin said:
thats excellent Mgutt
the note does the transition across to google now/voice commands very quickly.. you have put the note back on the table as an option for my next phone.. im just holding out to see if the LG G2 will use the S800 for always on listening when it gets kitkat..
Im a bit spooked by AMOLED now that my galaxy S2 is marred by burn in
Click to expand...
Click to collapse
I'm having one problem left. But I think its because of Llamas limited amount of triggers. The problem is: Google Voice is not able to receive the next command while its open. Instead S Voice waits for the next "Hello Galaxy". To bypass this problem I tried to switch off the display automatically. This works, but only with a fixed delay as I'm not able to trigger "last touch/last talk + 10 seconds" with Llama.
Would this work with Tasker (and without Root)?
The next option would be to activate "Open Mic+" as long Google Voice is open. But I did not tested if this would work.
mgutt said:
Would this work with Tasker (and without Root)?
Click to expand...
Click to collapse
Well we can set the display timeout to 15sec, then restore the default (it's 30 sec for me because of smart stay) when google voice search disappears.
Because of the 30 sec display timeout it hasn't been much of a problem for me, but I was also wondering how to get it to prompt for a next question.
Curious: why doesn't the "ok, google" hotword work in google now? I've just tested the google experience launcher and hot word detection doesn't work in there either.
vgergo said:
Well we can set the display timeout to 15sec, then restore the default (it's 30 sec for me because of smart stay) when google voice search disappears.
Click to expand...
Click to collapse
I'm using this setup (after 20 seconds display is turned off) and this is not good if you press the microphone button. Then the display switches off, too. So we need an additional "on touch" condition to avoid that.
mgutt said:
I'm using this setup (after 20 seconds display is turned off) and this is not good if you press the microphone button. Then the display switches off, too. So we need an additional "on touch" condition to avoid that.
Click to expand...
Click to collapse
Okay, then set the display timeout to 15sec, wait 15sec then set it back to whatever it used to be. Then if the screen was touched (and the display timeout extended) then it will stay on...
I hope to be able to test these with tasker in the afternoon

Could use some assistance with battery.. screen shots attached.

So. Here's the deal. I flashed to a stock rooted 4.4 and faux kernel .. pretty much the same setup that I have always ran apart from being a newer Android build. I have attached some screen shots (haha.. maybe to much) for you guys to look at and tell me what you see.. any advice or anything you notice that is burning my battery so quickly I would greatly appreciate.
Sent from my Nexus 4 using xda app-developers app
1. Download Greenify to stop apps constantly running bg.
2. Nexus 4 auto brightness seems to be very high. Indoor use 0% and outdoor use auto brightness.
3. Always charge your phone to 100% and dont recharge it until it reaches 5%-10%.
4. Switch your GPS to "Battery Saving" instead of High accuracy. To enable this mode, head to Settings > Location > Mode, and enable Battery Saving.
5. If you dont use Google Now disable it. If you use it sometime; just disable Hotword detection feature. Google Now > Settings > Voice, and disable Hotword Detection
6. NFC enable it when you only need it. Settings > Wireless & Networks – More > NFC. Disabling NFC will also disable Android Beam. Same goes for Bluetooth and LTE; enable it when you need it.
7. Stop autosync. With Kitkat google syncs everything purchases, Google Keep, music, books, contacts, and even photos. Each time you snap a picture, Google uploads it to your account to back it up. Go to settings and find your e-mail address under Accounts. Tap the account name again to access sync settings, where you can un-check the items you don't want synced. Included there is that "Google Photos" option. OR, head to the Gallery app > Settings, and disable Google Photos Sync. Now, if you have multiple accounts; make sure to disable it for each.
8. Do you really need live wallpaper? Disable it!
9. Avoid apps with lots of advertisements. Those ads are constantly refreshing, sucking up your precious battery life.
Thank you for your very detailed post ..I appreciate that.
Funny because for the most part I do all of this. Before going to 4.4 I was getting around three and a half hours of screen time in a 13 or 14 hour day and now I'm getting about 5 or 6 hours with an hour and a half of screen time .
looking at your list really looks like the only thing I forgot to do list to disable all of those Google sync things.. And I did have my GPS setting for precision instead of battery saver hopefully that doesn't affect my location services too badly.

Enabling always on Google now voice activation

So I've seen that the Moto x has the Touch less Control that allows the user to have the option to use their phone without even touching it. Little did I know that the same could be done with my Nexus 5. Just head to the Settings on the Google Now page at the bottom, then tap on "voice". From there, tap "OK Google detection". Afterwards you just have to train your voice 3 times and can now have the ability to activate Google now fro. Anywhere, including while the phone is sleeping, if you check the lock screen activation box. From there, you should now be able to use Google now from the lock screen without having to press the power button or from any application throughout your Nexus 5 or device that is running the Google Now Launcher. :good:
lui5_torre5 said:
So I've seen that the Moto x has the Touch less Control that allows the user to have the option to use their phone without even touching it. Little did I know that the same could be done with my Nexus 5. Just head to the Settings on the Google Now page at the bottom, then tap on "voice". From there, tap "OK Google detection". Afterwards you just have to train your voice 3 times and can now have the ability to activate Google now fro. Anywhere, including while the phone is sleeping, if you check the lock screen activation box. From there, you should now be able to use Google now from the lock screen without having to press the power button or from any application throughout your Nexus 5 or device that is running the Google Now Launcher. :good:
Click to expand...
Click to collapse
Only works in US English at present, and I'm sure this is common knowledge by now...
[/QUOTE][/QUOTE][/QUOTE]
EddyOS said:
Only works in US English at present, and I'm sure this is common knowledge by now...
Click to expand...
Click to collapse
also to use the "while sleeping" feature the device must be plug into a power source
Theres already a thread for this, and its hardly useful unless you enjoy battery drain.

Edge 7 Problems

Hello,
I'm starting to hate my S7 Edge, and I'm really missing my Edge 6 Plus. Has anyone else had these problems and perhaps have any advice for resolving them? I've searched around and can't find any other reports of these problems.
First, if I'm traveling, *sometimes* I can't use the Google Navigation App if I'm in motion. For example, if I'm driving home, and I decide to get gas, if I say "OK Google, navigate to the Gas Station" It will of course find a close gas station, and allow me to choose which one. After I do so, the app will plot a course, but then will fail to acquire a satellite. The app will just sit there constantly saying "Acquiring Satellite" (or something to that effect, I can't remember the exact error) but it never does find the satellite. The only fix for this is to repeatedly turn off and on the Location services, until eventually it just works. Which is extremely infuriating not to mention dangerous while driving. I rememeber falling in love with my S6 Edge Plus because it had such an easy time navigating and this S7 Edge is so consistently terrible at locating my position.
Second, this is a problem I did not know I had until today: After mis-placing my phone, I went to the Google "Find my phone" web page on my computer, to force my cellphone to ring. I have used this service before with all my other phones and it never failed to force the device to ring. But this time, my S7 did not ring. Luckilly I was able to find my phone on my own. When I did locate it, i noticed that there was an icon in the notification tray saying "Ringing phone" and yet the phone was NOT RINGING! With the phone in hand, I tried to use the webpage to locate my phone by ringing it again. The same thing happened. It put a notification up that my phone was "ringing" in the phone's notification display, but made no actual noise.
I checked the settings - > Lock Screen and Security -> Find my Mobile, and it asks me for my Samsung Account Password.
Why my samsung account? Why not google? I don't understand.
So I signed in, and google location service is set to ON, as expected. Remote controls is also set to ON. There is a notification at the bottom that says to track and control my device, go to: findmymobile.samsung
So I go there, and I tell it to ring my phone, and what do you know? It rings my phone perfectly. Noise and everything.
How do I switch it over to google's service? I really don't like most of Samsung's software offerings, and would prefer to use native google apps out of convenience. I don't remember ever having this problem with any other galaxy device. Not even my tablet does this.
Can anyone help?
I haven't had any GPS problems with mine (U.S. Sprint version). What are your location settings? Make sure it's set to use GPS, and not just network or WiFi.
Find My Mobile and Android 's service are two different things FMM is Samsung's product. To make sure Google's is active, go to Device Administrators and make sure Android Device Manager is turned on. Then go to Apps, scroll to the bottom and tap on Google, then scroll down and tap on Security. Make sure 'Remotely locate this device' (and 'Allow remote lock and erase' if you want that) are turned on.
meyerweb said:
I haven't had any GPS problems with mine (U.S. Sprint version). What are your location settings? Make sure it's set to use GPS, and not just network or WiFi.
Click to expand...
Click to collapse
I have GPS, WIFI and Mobile Networks turned on.
meyerweb said:
Find My Mobile and Android 's service are two different things FMM is Samsung's product. To make sure Google's is active, go to Device Administrators and make sure Android Device Manager is turned on. Then go to Apps, scroll to the bottom and tap on Google, then scroll down and tap on Security. Make sure 'Remotely locate this device' (and 'Allow remote lock and erase' if you want that) are turned on.
Click to expand...
Click to collapse
-Android Device Manager is turned on in the Device Administrators Section.
-I am not sure how to complete the second instructions. I do not see "Apps" as an option in the Settings panels. Can you advise where to find it?
Thank you!
Kirren said:
-Android Device Manager is turned on in the Device Administrators Section.
-I am not sure how to complete the second instructions. I do not see "Apps" as an option in the Settings panels. Can you advise where to find it?
Thank you!
Click to expand...
Click to collapse
Settings / Applications
Scroll to bottom, tap Google (on my Sprint S7 Edge, it's the very last item).
Scroll down until you see "Security" and tap there.
The first two toggles (on mine) are "Remotely locate this device" and "Allow remote unlock and erase."
meyerweb said:
Settings / Applications
Scroll to bottom, tap Google (on my Sprint S7 Edge, it's the very last item).
Scroll down until you see "Security" and tap there.
The first two toggles (on mine) are "Remotely locate this device" and "Allow remote unlock and erase."
Click to expand...
Click to collapse
Ah, I was able to find the settings under Google, however both are already checked. Are there any other settings I need to check?
{{Edit: I toggled the setting just to test it, and now it seems to be working. I don't know why this worked, because the setting was already properly configured. But it works now. *shrug* Thank you so very much for your help and patience!}}
Glad to help. I seen lots of things get fixed when you toggle a setting. Something in the settings file got corrupted, and toggling the settings on and off rewrote what should have already been there. At least that's my guess.

Various questions

I just moved to the Tmobile V20 from the Nexus 5 (not the 5x), and have noticed a few behaviors that are different than what I expected. Would love some insights.
Is there any way to enable the knock knock turn off feature when using the Google Launcher instead of the default?
Do the "smart" calendar events not work on this phone. On my N5, I could start typing Dentist, and it would slowly prompt me for locations, dates, times, etc..
Is there anyway to quick launch the camera? With the fingerprint sensor, I hvae to turn it on, go to the home screen, then select the camera.
frozndevl said:
I just moved to the Tmobile V20 from the Nexus 5 (not the 5x), and have noticed a few behaviors that are different than what I expected. Would love some insights.
Is there any way to enable the knock knock turn off feature when using the Google Launcher instead of the default?
Do the "smart" calendar events not work on this phone. On my N5, I could start typing Dentist, and it would slowly prompt me for locations, dates, times, etc..
Is there anyway to quick launch the camera? With the fingerprint sensor, I hvae to turn it on, go to the home screen, then select the camera.
Click to expand...
Click to collapse
1. Double tap the notification bar on any screen.
2. No idea.
3. Press the Down volume button twice when the screen is off. (Not applicable when playing media)
vi001101106 said:
1. Double tap the notification bar on any screen.
2. No idea.
3. Press the Down volume button twice when the screen is off. (Not applicable when playing media)
Click to expand...
Click to collapse
Awesome, #1 and #3 down. Thanks so much for the help.
Ahh, here is the official blurb from the Play Store link for the Calendar App.
• Quick event creation - Smart suggestions for event titles, places and people save you time when creating events.
Are you using the built in Calendar, or the Google calendar? You may need to download the Google calendar to get things working the way to which you want.
Yeah, first thing I did was install google calendar. Maybe I should disable the LG one, wipe the googl calendar, and see if that fixes it.
Edit: Doing that allowed the quick event creation to function. Probably was something to do with the permissions it was allowed to grab since I did the app restore instead of installing it manually.

Categories

Resources