"Doze" feature?

[AllenRulz]

I know there isn't much info on it from what I seen. But I know this feature is mostly for when the phone is just set on the desk and not moving. Has anyone found out if it's possible to have this battery saving feature while having the phone in your pocket also? Sounds like an amazing feature to have and going to save much needed battery hopefully but as for users like me who mostly has their phone ON them and not on their desk, I'm hoping it works with this too.

Posted via the Android Central App

 

[Aquila]

Right now it seems like movement, such as in your pocket, will probably keep it out of the deep sleep.

 

[LeoRex]

Well, you are out of luck since Doze is designed to only kick in when the phone is left alone. Though, I suspect that this is really just the start of many related features. They wanted to reduce the wakelocks that apps generate, but not to the point where you lose functionality. The lowest hanging fruit here is to reduce background usage when the phone is sitting, stationary. There's no need for Google Services to poll location if the phone isn't moving, for instance (and the Network Location Protocol is one of the more common wakelocks you'll find).

So you are out of luck on the initial get-go... but perhaps this is a sign that Google may introduce more enhancements.

Maybe someone modifies something to fool Doze into thinking the phone is still. The source will all be out there once M gets sent into the wild. If someone can figure out how to apply that to all screen-off conditions, not just when stationary....

 

[AllenRulz]

Well, you are out of luck since Doze is designed to only kick in when the phone is left alone. Though, I suspect that this is really just the start of many related features. They wanted to reduce the wakelocks that apps generate, but not to the point where you lose functionality. The lowest hanging fruit here is to reduce background usage when the phone is sitting, stationary. There's no need for Google Services to poll location if the phone isn't moving, for instance (and the Network Location Protocol is one of the more common wakelocks you'll find).

So you are out of luck on the initial get-go... but perhaps this is a sign that Google may introduce more enhancements.

Maybe someone modifies something to fool Doze into thinking the phone is still. The source will all be out there once M gets sent into the wild. If someone can figure out how to apply that to all screen-off conditions, not just when stationary....

Yeah definitely man. I'm hoping for sure it sets up for something good like that for in pocket type of situation. The normal battery saver mode is okay on the Nexus 5 but slow at times. Was looking forward to the Doze but I guess have to wait lol. Appreciate the responses.

Posted via the Android Central App

 

[LeoRex]

Yeah definitely man. I'm hoping for sure it sets up for something good like that for in pocket type of situation. The normal battery saver mode is okay on the Nexus 5 but slow at times. Was looking forward to the Doze but I guess have to wait lol. Appreciate the responses

Well, Google doesn't want to put out something that causes a regression in functionality. I've played around with those background services... manually, using apps like Tasker and Llama to turn things on and off, as well as tools like Amplify, which kind of gates how often wakelocks can fire. It didn't take all that long to see how things like Google Now get affected when their background tasks are limited. But I use Google Now quite a bit, so I gladly pay the power cost..... when I am out and about.

I am sure that Doze started out inside the Google Play Services team as a way to limit its power usuage... there's no need for it to do a ton of work when the phone is sitting on a table. I can imagine a meeting where someone asked "Can we just roll this into the core OS?" after seeing Facebook take a huge wakelock riddled dump on his phone the day before.

So for me, Doze is an awesome first step.

 

[AllenRulz]

Well, Google doesn't want to put out something that causes a regression in functionality. I've played around with those background services... manually, using apps like Tasker and Llama to turn things on and off, as well as tools like Amplify, which kind of gates how often wakelocks can fire. It didn't take all that long to see how things like Google Now get affected when their background tasks are limited. But I use Google Now quite a bit, so I gladly pay the power cost..... when I am out and about.

I am sure that Doze started out inside the Google Play Services team as a way to limit its power usuage... there's no need for it to do a ton of work when the phone is sitting on a table. I can imagine a meeting where someone asked "Can we just roll this into the core OS?" after seeing Facebook take a huge wakelock riddled dump on his phone the day before.

So for me, Doze is an awesome first step.

Very well said.

Posted via the Android Central App