Database Info

HELP! Where did I go wrong?

So I just got a brand new D2G and thanks to the info in this forum I rooted it and installed fission rom and FRM...Im loving the phone, its fast, smooth and beautiful but the battery is AWFUL. I have read all the info about how to get the most out of your battery and everything on these forums but mine is waaaay worse than anyone has said before.
For instance, last night my phone was charging oernight, at 6 am when i woke up to pee it was at 100% so I unplugged it and went back to sleep, come 10 am when i woke up my phone was down to 15%!!! From just sitting there with the screen off...
Ive set the network to CDMA/Evduo automatic, installed Jrummy's overclock app...Can anyone explain in detail what exactly the settings in the overclock app mean? "set scaling frequencies at boot, cpu scaling frequencies etc?" for instance if I set scaling frequencies not at boot to ultra low voltage and 1 ghz and lower, do i need to also go into cpu scaling frequencies and make profiles and stuff?
Any information is greatly appreciated, Ive been reading up for days but this stuff is hard to find clear answers on specific issues. Thanks!

This is probably the most basic first thing to ask/do, but have you checked the battery useage to see which apps are using the most power? try doing what you did where you charged, and then let it sit for 4 hrs, and after that see what's using the battery, I bet there is some app that just nonstop uses the gps or 3g data or something wearing your battery life out super fast.

Yeah i looked at that this morning to see and all it said was suspend took up like 90% of the battery...Doesnt make any sense

1. Set at boot isn't what you're thinking. Set at boot means that whatever your current settings are will be set the NEXT time the phone boots. This is used when you have a setting you like. The reason you DON'T want to set at boot is that if you accidentally pick a setting that your phone doesn't like, and it makes it crash, then next time it will boot up with normal settings. Otherwise, you'd be looking at some work doing a recovery with either CWR or RSDLite... There are better ways to spend 30 minutes. Disclaimer: I use SetCPU, but the settings are all essentially the same.
2. For scaling, unless you're a power user (read: Geek) who's really up on his stuff, you should just stick with ondemand. This means your CPU will run at the lowest frequency possible, but will scale its speed up when processes call for it. This is efficient.
3. Yes, you should still make profiles. The setting on the main screen where you choose "Set at Boot" (Again, I'm speaking from SetCPU experience, but it SHOULD be the same) is just the main profile, setting the global minimum and maximum. You should leave the minimum on this at 300. The phones don't like to run much lower than that, even with the screen off; They start not ringing for calls, not waking up, etc. Set the maximum to whatever you want the max to be. You can overclock, which will obviously hurt your battery life. You could underclock and set the maximum to 1GHz, or even 800MHz, which would have a decent effect on battery life with no noticeable performance decrease to the average user. I run mine at the stock 1.2GHz and it's fast enough for my needs.
4. I wrote this thread to help people maximize their battery life. It's pretty detailed, you should give it a thorough read, it works well for me, and seems to work for others. I'm at 32hrs unplugged and my battery has gone from 90% to 20%. That's pretty light use, and I have an extended battery, but I still see over a day on my stock battery when I use it. There's a list of my SetCPU profiles there too, that might be helpful in setting up your own.

Thanks for the info on overclocking, I think I have it figured out now...
I will definitely read through your thread, but is it possible that I just had a bad battery? due to a shipping error, when verizon sent me my phone they sent 2 by accident so I just swapped out the battery for the other one and it seems to be doing much better already...

What does the 1.5ghz overclock do to the battery?

Meaning, does the battery life take a dip when you overclock to 1.5ghz. Does it get any hotter? Is heat an issue at all on this thing? Also, any performance or battery changes from installing the tiamet kernel itself? I'm in the wifi xoom btw.

Strangely enough battery life seems to be about the same. Heat has not been an issue mainly due to having the dual core, however its something you always want to keep an eye on.

Battery life is affected most by the screen. Screen> Network connections > CPU > RAM
There was a thread that someone made a while back about the things that affected battery life the most. If I can find It ill send it your way. After seeing the charts I figured Id try changing some settings.
things I did:
1. Set my max cpu freq to 1.19 min to 488 same for all my cpu tunner profiles ( I wanted to have my phone running the same all the time)
2. Lower'd my screen settings. I didnt need a pocket flashlight EVERYTIME I unlocked my phone.
3. Turned off un needed network connections. Its not hard to turn them back on when you need them.
4. I then looked for things that were running but were not needed by anything ( google maps are used by a few apps so dont disable it haha) I used Uninstaller for root users to get rid of some things.
After all these steps my battery life went WAY up. I have been doing the same thing on my Xoom now and my batt lasts the same at 1.5 as it did at 1.

I still get VERY respectable battery life at 1.5ghz, I can easily get through the day with normal usage. Yesterday night in fact, I left the house with maybe 75% battery life, used my tablet quite a lot throughout the evening(left the house around 9, went to sleep around 1am) and used it all morning basically constantly from 7am to around noon and came home with 9% battery left.

No problems here either. Woke up around 8:30 yesterday and used it all day sometimes pretty heavy. Finally had to plug it in around 6:30. I'm home all day with a broken hip and femur, so I've been putting it through the paces. Running @ 1.5ghz with interactive gov.
Chris

+1 on 1.5GHz having little effect on battery life. I didn't have to change anything else, either.

thats all great to hear! I suppose ill start looking into rooting my wifi xoom tomorrow then. Thanks for the help!

Im very happy with the battery life on this thing. I expected 4 hours max after a few weeks of use/charges. I never thought that it would keep up with anything Apple, Lets face it.. Apple knows how to make stuff run forever. But I was plesently suprised. Xoom +1000

yeah, the battery is good, but i won't know any damage to the cpu when overclocked ?

I wouldn't worry about any CPU damage- too many people have reported success (and no reports of failure).

Anyone else notice with the tiamat kernel that their xoom becomes very unstable overclocked at 1.5 using setCPU? Mine was essentially a soft brick at 1.5 constant rebooting and never able get pass the unlock screen, I had to rewipe with bootloader. I can do 1.2 no problem but don't even want to try going higher.

All of our chips have variations, so the overclock isn't universally guaranteed. That being said, I've been using the Tiamat kernel @1.5GHz since it was released with no problems.

Should have stated that mine is the wifi model, but yea thanks for info.

Here was that post I was looking for on this stuff. http://forum.xda-developers.com/forumdisplay.php?f=946

Post your Thunderbolt setup here!

Just thought I would start a thread like this considering it hasn't been done. A lot of people are having trouble with battery consumption and stability it seems. I've been having amazing luck with my current setup so I thought i would share.
DasBamf 1.5 Remix
Imoyeson Extra Lean 1.4 Kernel OC'd to 1.4
Governor set to interactiveX
Latest radio found in DasBamf 1.5 thread
With stock battery I have been getting 20 plus hours no problem so far. I downloaded battery calibration from the market and reset stats after installing new rom. Quadrant is in the 2300's, and the phone is extremely smooth. I will post a screenshot later on of how many hours I have been off charge for this run. These numbers are in a 4G area with occasional switches to 3g.

Mind if I ask, do you have autobrightness selected, or set to a specific value? Just wondering, as my setup is very similar to yours, and I use auto brightness - get about 18 hours of regular daily use, 24 hours light use.
Have heard some say setting brightness to a specific value rather than auto makes it last even longer.

spyderman09 said:
Mind if I ask, do you have autobrightness selected, or set to a specific value?
Sent from my Thunderbolt
Click to expand...
Click to collapse
I set it as lighting changes. If I'm home I have it at 25% which is more than enough. Out in the sun it gets switched to whatever works. Easy enough to change with a widget or simply using the pull down that comes with the ROM.

I am using DasBamf 1.6 Beta now. It seems smoother than DasBamf 1.5. Battery life on it looks great so far. I used to get 15 hours with DasBamf 1.5 with reg usage. Texts, internet, forums, calls and emails. I am using the default kernel with the rom and have it underclocked to 1ghz with setcpu. Penty of speed for me. IN addition, I am in a 4G area. NEver switched on me to 3G

Thoughts on OverClocking Sensation

Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt

I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.

I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt

I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.

mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App

Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707

I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...

So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt

I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?

i think at LeeDroid 1.2 you must not use setcpu but Demon control?

BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.

Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.

Racing to 1000 [Q]

Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...

FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en

I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)

FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment

My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s

FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.

My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...

FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.

Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen

is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.

Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..

I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.

Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...