Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
View Poll Results: Battery life after rooting
No change in battery life 6 23.08%
Small decrease in battery life 6 23.08%
Significant decrease in battery life 14 53.85%
Increase in battery life 0 0%
Voters: 26. You may not vote on this poll

Post Reply

[Q] Rooting - effect on battery life

OP Randy Lahey

9th April 2012, 11:43 AM   |  #1  
OP Junior Member
Thanks Meter: 1
 
14 posts
Join Date:Joined: Mar 2006
I'm trying to decide whether to root my NST or just leave it as is. I would certainly like to have the extra functionality, but not at a large cost to the battery life. After all, I did buy it as an e-reader first and foremost, so battery life is a very important factor.

I've searched the thread a bit and have seen some people complain a great deal about battery performance after rooting, however perhaps this is down to programs they decide to run, rather than the rooting process itself with the latest touchnooter.

So, could one of you veterans please comment on your experience with battery life after rooting?

Cheers,

R
9th April 2012, 04:03 PM   |  #2  
brendan10211's Avatar
Senior Member
Flag Cary
Thanks Meter: 12
 
200 posts
Join Date:Joined: Feb 2012
More
From my experience, most battery is wasted when refreshing the screen. When you root, most of the time your goal is to use some random android app. This means you are going to be refreshing the screen often, which uses battery.

Someone else tell me if I am wrong, thanks
The Following User Says Thank You to brendan10211 For This Useful Post: [ View ]
9th April 2012, 06:54 PM   |  #3  
Member
Thanks Meter: 4
 
61 posts
Join Date:Joined: Oct 2010
I don't think that root itself has any impact on battery life, but as you can do more with rooted nook, you consume more. Last week I've used mine almost 100% as a reader and battery is at 50%... and I read much more than 1 hour a day (that's the presumption for "2 months battery life" from B&N :))
The Following User Says Thank You to fufutos For This Useful Post: [ View ]
10th April 2012, 02:49 AM   |  #4  
Member
Flag Raleigh
Thanks Meter: 31
 
57 posts
Join Date:Joined: Jul 2011
I've accidentally voted 'significant decrease' whereas in reality I have seen no change. An issue I've run into is that I have 'Keep Screen On' checked in EBookDroid so the page doesn't go away, but then when I'm done reading I forget to hit the power button to sleep it. This has drained the battery on me more than once.

Incidentally, it would be superfly if someone hacked together a script that copied the framebuffer to a file in the screensaver directory so when it went into sleep mode it would keep displaying the page while not wasting batteries.

I might hash that up when I have time.
The Following User Says Thank You to klausef For This Useful Post: [ View ]
10th April 2012, 05:30 AM   |  #5  
Senior Member
Thanks Meter: 47
 
419 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by klausef

I've accidentally voted 'significant decrease' whereas in reality I have seen no change. An issue I've run into is that I have 'Keep Screen On' checked in EBookDroid so the page doesn't go away, but then when I'm done reading I forget to hit the power button to sleep it. This has drained the battery on me more than once.

Incidentally, it would be superfly if someone hacked together a script that copied the framebuffer to a file in the screensaver directory so when it went into sleep mode it would keep displaying the page while not wasting batteries.

I might hash that up when I have time.

There is system/bin/screenshot
Code:
screenshot /media/001.png
Donít know how to hook it up to sleep event, hopefully should be very difficult.
Dirty hack Ė delete all screen saver images, than use screenshot, so itíll be the only one to pick...
10th April 2012, 02:03 PM   |  #6  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 822
 
2,000 posts
Join Date:Joined: Feb 2012
Quote:
Originally Posted by ApokrifX

There is system/bin/screenshot

Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.

Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture
10th April 2012, 04:13 PM   |  #7  
Googie2149's Avatar
Senior Member
Thanks Meter: 54
 
288 posts
Join Date:Joined: Jan 2012
More
Quote:
Originally Posted by Renate NST

Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.

Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture

Same thing was happening to mine. More of a cyan/teal, though. :P
11th April 2012, 12:30 AM   |  #8  
Member
Flag Raleigh
Thanks Meter: 31
 
57 posts
Join Date:Joined: Jul 2011
we don't even need it to hook to the sleep event; i was considering just having a service that waits for two minutes of inactivity, clears out the screensaver directory (as mentioned) and then writes a screencap to it.
11th April 2012, 05:34 AM   |  #9  
Senior Member
Thanks Meter: 47
 
419 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by Renate NST

Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.

Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture

I've never tried it, actually...
11th April 2012, 01:29 PM   |  #10  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 822
 
2,000 posts
Join Date:Joined: Feb 2012
I've seen something happen randomly, I addressed it in another post:
http://forum.xda-developers.com/show...18&postcount=9

On occasion the touch screen sensors do not turn off when the Nook goes to sleep.
Whether this indicates that nothing has gone to sleep or just that the sensor has not gone to sleep is unclear.
Still, you can lose about 4% of a charge per hour overnight.

If you run into this, there is something that you can try:

Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db

sqlite3 settings.db
sqlite> update system set value=0 where name='stay_on_while_plugged_in';
sqlite> .q

adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
3 is the normal value, telling the Nook to stay on always with USB or charger power.
Unfortunately, once a charger/USB is plugged in it gets its state all confused.
Even with this set to 0 the screen sensors stay active while plugged in.

Post Reply Subscribe to Thread

Tags
battery, nook simple touch, rooting
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes