So now that you've rooted.. how's your battery life?

after flashing adrynalynes debloat rom and the attached kernel I am see a few more hours of battery
 
after flashing adrynalynes debloat rom and the attached kernel I am see a few more hours of battery

That's really good to know. In my case, life wasn't TOO bad to begin with (only on 3G until later this year), but a few more hours on 4G (which probably equates to being about another 30% more when applied to 3G) would make it a COMPLETE non-issue for me. Awesome!
 
  • Like
Reactions: samuraifortruth
8 hours, 41 minutes since unplugged, 53% battery left, display 71%, cell standby 9%, phone idle 7%, voice calls 5%, android system 4%. This is with light usage throughout the day: check my email many times, read some facebook, browse the web a little, etc. On 4G all day. Display brightness was at ~33%. I am running Adryn's debloat. I don't have any task killers, but if the battery usage is right, I don't know it'd matter. SetCPU might help. Waiting on new ROMs!
 
My battery seems the same since I rooted, but I haven't really been having battery issues like some other people. I'm still running the stock ROM and kernel and I only disabled some of the bloat with root explorer. I also use a task killer to kill apps only once right after bootup (when everything unnecessary loads), then I generally don't use it again

Once HTC releases the source code we'll start seeing a lot of undervolted kernels come out that will greatly improve battery life - another perk to rooting ;)
 
I havent had a chance to really look at my battery, I've been plugging in the USB to transfer some apps. So I'm going to let it die tonight and have a fresh battery tomorrow to test battery life. I'm just happy to get rid of all that vzw crap that was on there. Freed up some memory.
 
I suggest using setcpu, its a huge battery saver. As it is right now your processor is running at 1ghz no matter what, but if you use setcpu you can have it run at 1ghz while the screen is on and underclock it to 200ish MHz when the screen off with no ill effects. Make sure to hit menu and perflock disabled if youre on the stock kernel, this will allow underclocking.

On my evo, without setcpu I get 8-10ish hours (cm7), with it I can get 18+ hours. It makes a world of difference for me.
 
Wow 5 replys only! Look like no too many tunderbolters are willing to root yet.


got sdk installed and adb, I am goign to try, but the debloat "rom" is an older kernal? right?

All i want is root to get rid of bloat for now. baby steps, ut I dont see how yet?
 
I suggest using setcpu, its a huge battery saver. As it is right now your processor is running at 1ghz no matter what, but if you use setcpu you can have it run at 1ghz while the screen is on and underclock it to 200ish MHz when the screen off with no ill effects. Make sure to hit menu and perflock disabled if youre on the stock kernel, this will allow underclocking.

On my evo, without setcpu I get 8-10ish hours (cm7), with it I can get 18+ hours. It makes a world of difference for me.
I did this as well and its making a difference, I was down to 78 when i got home at 5pm and I unplugged it at 7 am, and well its a new toy and i have been playing with it
 
i installed setCPU on this phone (purchased for og droid) and now i bet my battery will be atleast 20% more efficient because i can set profiles. i have three profiles right now: charging = 1ghz, , < 50 = 768mhz, and screen off = like 360 or something (dont have phone so cant give actual numbers right now)

I cant wait to test tomorrow. screen shoots, etc to come.
 
I suggest using setcpu, its a huge battery saver. As it is right now your processor is running at 1ghz no matter what, but if you use setcpu you can have it run at 1ghz while the screen is on and underclock it to 200ish MHz when the screen off with no ill effects. Make sure to hit menu and perflock disabled if youre on the stock kernel, this will allow underclocking.

On my evo, without setcpu I get 8-10ish hours (cm7), with it I can get 18+ hours. It makes a world of difference for me.

Why wouldn't HTC just do this to start with? It would seem like a logical way to solve alot of their battery issues.
 
got sdk installed and adb, I am goign to try, but the debloat "rom" is an older kernal? right?

All i want is root to get rid of bloat for now. baby steps, ut I dont see how yet?

Curious if the bloatware apps have an effect on battery life.

It will have very little impact on battery life. The Verizon bloatware includes apps that are never truly running unless you open them. The Widgets are the same way. If you aren't using them, they aren't using any power either. Actually this is true with everything on this list.

Gunthrem, that same post summarizes what steps you need to take.
 
Gunthrem, that same post summarizes what steps you need to take.

I understand that point, but i beleive he is using an older kernal or a older radio??

Also if you do this how do you un-root. I know all newbie questions, but I for one can;'t find that oneplace that explains all of this is laymen tearms for us newbies that want to take that plunge..
 
it's a reliability measure

constant clockspeed = constant voltage
that's a good thing from what I've heard

I'm new to android, but I spent (wasted) years hacking the living BS out of webOS. Screwing with clockspeed "states" basically decimates the life of your processor.

but I think some middle groud is worth having
I used to cycle 500mhz with screen off, and 1.2ghz otherwise on a pre plus

it's lasted a while before I melted it due to unrelated(?) issues

I'm unrooted and when I look at set cpu it seems that the cpu speed does cycle by stock down to 245mhz constantly on it's own, but the app could just be showing this and it not be true, I'm not sure
 

Forum statistics

Threads
956,393
Messages
6,967,995
Members
3,163,534
Latest member
Chauncey the Gardener