Related
I'm rooted but otherwise on stock 4.2.2.
My battery life is pretty bad, so I keep Google Now disabled (also because I have absolutely no use for any of the cards). I don't know when it started, but recently, whenever I do a voice search for the weather, it defaults to Celsius (see attached picture). Celsius is on the left of the choices for weather, which is not how it used to be. Maybe the Google Now update a few weeks ago did this?
So I turned on Google Now, and disabled every single card. Lo and behold, without changing any settings in the weather card first, or doing anything else, the voice search now defaults to Fahrenheit, and puts it on the left in choice of units.
But this isn't a good solution for me, because if Google Now is enabled, when you swipe up from the software buttons on the bottom to bring up the search screen, it doesn't auto-focus on the search bar itself, so you have to touch the bar to bring up the keyboard. Very annoying.
Why, when Google Now is disabled, does a weather voice search default to Celsius now when it never used to do it? And why does it default to Fahrenheit when Google Now is enabled but all cards are disabled and no weather settings have been touched?
Is there any way to change the default to Fahrenheit without enabling Google Now?
Or, is there a way to make it so opening up the Google Now search area makes it autofocus on the search bar so the keyboard comes up right away?
....is this thing screwing with me?
If I do a voice search "What's the weather in Fahrenheit", it still shows the temperature in Celsius (attached picture).
But, it reads aloud the temperature in Fahrenheit! What the hell??
I really hope this isn't an unsolvable problem
MultiKoopa said:
I really hope this isn't an unsolvable problem
Click to expand...
Click to collapse
Have you tried enabling Google Now, and clicking the small icon that looks like a "i" with a circle around it? When you click that, there will be an option for Weather Units appearing at the bottom of the weather card. Click on that, and change it to Fahrenheit. Then, when you ask "what's the weather" the response will be in Fahrenheit.
amartolos said:
Have you tried enabling Google Now, and clicking the small icon that looks like a "i" with a circle around it? When you click that, there will be an option for Weather Units appearing at the bottom of the weather card. Click on that, and change it to Fahrenheit. Then, when you ask "what's the weather" the response will be in Fahrenheit.
Click to expand...
Click to collapse
I'm having this exact same problem as described. Just discovered it tonight. Running a stock Nexus 4. It's a little thing but AWFULLY annoying.. Would love to get this fixed. I think it's a Google issue. Because I did click the little i and changed the settings. It doesn't stick after you turn off Google Now. :banghead:
Sent from my Nexus 4 using xda app-developers app
Glad I'm not the only one.
This is nuts.
Tried clearing data.
Tried enabling Google Now, setting it as def F, then disabling, but still does C!
I have a stock Samsung Galaxy Nexus, running 4.2.1. Google Voice Search used to work, then it updated. Now I get weather inquiries returned in Celsius unless I enable and run Google Now. While Google Now is active the search returns temperature in Fahrenheit. I tried uninstalling the Google Serach update and when I did that there is no Google Voice Search at all, I get : "unable to connect to Google" , reinstalled the updated Google Voice search works again , but still returns temperatures in Celsius unless I enable Google Now. Has anyome found a fix for this?
bump...
Found out this is a known issue. The only way to fix it is to use Google Now. So. Now I use it.
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
Found out this is a known issue. The only way to fix it is to use Google Now. So. Now I use it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'm just worried about the effect Google Now may have on battery life.
Yeah I understand. I finally just sucked it up and started using Google Now.. Haven't noticed a drastic difference.. Maybe you won't either. Just disable most the cards.
Sent from my Nexus 4 using xda app-developers app
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
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.
Anyone rooted get the update? It's working on my wife's non-rooted mxpe, but my rooted phone didn't get anything yet.
I just got it on rooted stock mxp.
Not happy that it doesn't integrate with Moto Voice at all....And GA with screen off doesn't work despite setting in Google app saying it does.
Do you have moto voice on? I also don't have the option for ok google from any screen under the voice settings in the Google app and my wife's phone does. Weird.
How did you get the update? I for a security update this morning which is weird but I didn't think that was related.
irtrueno said:
How did you get the update? I for a security update this morning which is weird but I didn't think that was related.
Click to expand...
Click to collapse
It's all server side... You will know you have it by long-pressing the home button, if it pops up with Google Assistant you have it, if it doesn't then Google hasn't turned it on for you yet.
acejavelin said:
It's all server side... You will know you have it by long-pressing the home button, if it pops up with Google Assistant you have it, if it doesn't then Google hasn't turned it on for you yet.
Click to expand...
Click to collapse
Does Assistant pop up running the Google now launcher for you? I have feeds on and currently a long press just goes to the left Google now screen.
aybarrap1 said:
Does Assistant pop up running the Google now launcher for you? I have feeds on and currently a long press just goes to the left Google now screen.
Click to expand...
Click to collapse
Yes it does... In both Google Now and Nova Prime.
It does appear that the only way to wake the pure is to have moto voice enabled. When activating moto voice it only starts the classic google now interface, not google assistant. I've tried disabling moto voice -- if you do, you can't wake the device from sleep with just your voice. I'm going to follow this thread, maybe someone will find a way?
Using Tasker (and being rooted with Magisk), I was able to get "OK Google" (my custom phrase) waking Moto Voice, then immediately launching Google Assistant. However, it only seems to work right when the screen is already on. If I turn the screen off and say "OK Google", Moto Voice launches, but Tasker never launches the shell command to launch Google Assistant. Not sure what the problem is.
Profile
Event - App (Moto Voice)
Task - Run Shell (/sbin/su -c "input keyevent 219") - if you use SuperSU or something you can just check the Root box, and can just put "input keyevent 219)
I've tried adding delays to the profile, etc... but it almost seems like the Moto Voice screen that comes up when the screen is on is "Moto Voice", but when the screen is off it's not.
Seems like we'll need an update from Motorola to truly solve this.
Running LineageOS 02/13 build. Got Google Assistant working. But OK Google detection works only when on home screen (Nova Launcher). Also I have set the Home button long press action to 'Search Assistant'.
OK Google detection setting is actually greyed out in Google App. But it's somehow working.
P.S: I have opted for Google Beta in playstore.
Using Rn7 China Rom with 10.3.2 MIUI. How do you turn on access to voice match? I turn it on then it reverts back to being turned off. Anyone know fix?
RumpelKittskin said:
Using Rn7 China Rom with 10.3.2 MIUI. How do you turn on access to voice match? I turn it on then it reverts back to being turned off. Anyone know fix?
Click to expand...
Click to collapse
I think it's a Google bug because until now I had a nokia 7 plus and there was the same problem, present also in the rn7 I just bought these afternoon
I have the same issue.
There is a solution which is to uninstall updates of the Google App, but this is in my case with the Global (PFGMIXM) which already included Google apps, so maybe trying with old apks could work.
But at the moment you update Google App, the issue appears again.
RumpelKittskin said:
Using Rn7 China Rom with 10.3.2 MIUI. How do you turn on access to voice match? I turn it on then it reverts back to being turned off. Anyone know fix?
Click to expand...
Click to collapse
Is a Google bug, Im actually using it, but to configure the voice match dont use the menu, just open Google app and in the main page say "ok Google", the voice match wizard should start automatically, set your voice profile, it should work, dont try to configure via menu, that will disable voice match, in the menu it shows disable but you can use it normally.
:good:
10.3.3 EU, Voice Match in Google Assistant tries to "add devices", while the OK Google toggle in settings starts the wizard, but after finalizing it, the toggle remains in the off position. Saying "OK Google" doesn't work even it the assistant screen when the search bar says "say OK Google"
Any updates on this?