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...

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.

[Q] Underclock - usefulness AND values

I am playing a bit with underclocking my DS (Using UNITY v4 kernel atm, will update to v9 later).
However, I'm figuring out the usefulness of it (to extend battery life mainly).
Does it really save battery life? I'm already using JuiceDefender, and its SetCPU function.
Or is it not very useful since the most batterydrain comes from radios anyway.
What are the best values for it?
What's the standard clockspeed for the DS? And what is the best Max IDLE clock speed?

Well, i wont underclock at all.
First of all there is no need to do that to get good battery life. You can do lot other stuff to do so.
Under-clocking is risky as it might now have enough power that needed to the phone. that means that some stuff might not get processed like calls and stuff.
Right now with me using miui i get life for about 3-4 days.

Standard clock speed is 1,000mhz.
I have mine underclocked to 600mhz during idle times and it's perfectly fine.
Never had any issues at that speed and it keeps my Desire S much much cooler which can only be a good thing.
As for it's ability to extend the battery, I don't think it does so much in my case. I typically run WiFi overnight and G/3G/H during the day and my display usually chews up 60-70% of my overall battery usage even on a very dark screen.
I'd pick a setting that you feel comfortable with but have low expectations of the benefits.

The only time I use underclocking is for using Google Navigation.
On a hot day using Navigation for over a couple of hours, my DS would over-heat and restart (usually as I was approaching my motorway exit). So I have Tasker dialing back CPU to 768Mhz when using Navigation, and it does seem to help the phone run a little cooler. I no longer have to take it out the case for example.
Using the smartass governor (I believe) automatically knocks the CPU back to 240Mhz when sleeping. Not 100% on that though.
I'm currently testing a new kernel, and I spent an entire charge cycle on 'Smartass' and then an entire charge cycle on 'Powersave'. Aside from lots of lag on the latter one, the battery life was pretty much the same!

[Q] Question about Kernels

Hi, my Triumph should be arriving in the mail in just a few days and i was wondering which is the best kernel or ROM and Kernel combination that is best for battery life? I've heard that battery life on the Triumph is not so good. Maybe it's false but i would still like to know.

jerenater10 said:
Hi, my Triumph should be arriving in the mail in just a few days and i was wondering which is the best kernel or ROM and Kernel combination that is best for battery life? I've heard that battery life on the Triumph is not so good. Maybe it's false but i would still like to know.
Click to expand...
Click to collapse
I would go with CM7

That's what i was planning on. Does your Triumph give you battery problems?

jerenater10 said:
That's what i was planning on. Does your Triumph give you battery problems?
Click to expand...
Click to collapse
The battery life is a lot better now with the latest builds of CM7 and MIUI.
I just use CM7 and leave wifi and bluetooth off, no juice defender or anything like that and I can easily go all day with no charge, typically about a day and a half and my battery is getting low but it really depends on what you are doing like games, wifi, videos and whatnot.
Before I think there was a problem with the battery draining while in idle but things have cleared up since then, There are also third party kernels you can OC and everything, but you can use them to undervolt as well to save some battery if you know what you are doing. over on androidforums there is a lot more chatter about this phone, just so you know.

ketjr81 said:
The battery life is a lot better now with the latest builds of CM7 and MIUI.
I just use CM7 and leave wifi and bluetooth off, no juice defender or anything like that and I can easily go all day with no charge, typically about a day and a half and my battery is getting low but it really depends on what you are doing like games, wifi, videos and whatnot.
Before I think there was a problem with the battery draining while in idle but things have cleared up since then, There are also third party kernels you can OC and everything, but you can use them to undervolt as well to save some battery if you know what you are doing. over on androidforums there is a lot more chatter about this phone, just so you know.
Click to expand...
Click to collapse
Thanks. I got my phone today and im loving it so far. Do you know which of those third party kernels are good for battery life and that i can install over stock? I'm not quite ready to install a ROM yet but i already did the HTC Thunderbolt Build.prop tweak and obviously im rooted.

It's usually not the kernel but whatever governor you have it set to use. Even the stock can get improved performance if you switch the governor to such--”performance”--but I'm probably not the guy to tell you about which one is best.
I also have the silly feeling a lot of misconceptions abound here...in the form of ”I changed this setting and now my device lasts longer..., oh btw I no longer play with it 24/7.” In other words, use drastically impacts battery performance. JuiceDefender is an amazing tool but it won't do you a bit of good if you're testing out your phone's Adobe Flash capabilities regularly.
Sent from my Wildfire S

The Savagezen and interactive (not sure if interactive is on any of the kernels for this phone.) gov isn't that great. At least not in my experience. I had SmartassV2 on my girlfriends phone and it got ~3600 on Antutu benchmark at 1.5 and when I used Savage at 1.5 she got ~1700. The interactive gov made my friends Dinc2 noticably slower. Just switching home screens it lagged to the point it was hard to get into the app to change the gov.

CM7 + TheOC kernel allows adjusting voltage & overclock or underclock. You really should flash a CM7 ROM. Having it just rooted can be dangerous because you're not using a custom recovery to make a backup image, and if something messes up, you don't have a backup ROM to restore. Going to a different ROM forces you to make a backup, then there's a backup to restore if you mess things up.
Governors just tell the CPU how fast to ramp up to a certain frequency, & how long to stay there. It's hard to balance fast ramp up (less lag), and low battery drain (spend more time in the lower frequencies). I like interactive/x, find that smartassv2 spends too much time in the mid frequencies (~500) even for light work. Using the app CPU Spy helps a lot to see what's going on. Also it tells you whether your phone is sleeping properly when screen is off, which is a big factor for battery drain.

Clemsyn 1.9 Ghz Kernel - Cold booting in 30s, insane benchmark, no downsides

Delete

lucius.zen said:
This is not for the faint of heart.....
I flashed Clemsyns 1.9 Ghz kernel this morning and it has cut boot times down by about 15s, I am able to cold boot in less than 30s. I know this kernel isnt working for everyone, however, just thought Id mention it is working very well for me so far. Didnt need it for lag as that was gone with the 1.5-1.8 kernel, but it is worth it for the boot improvement, which was my only gripe with this device. In a truly mobile productivity device boot times SHOULD be less than 30s.
Will report later today after more stress tests and temperature checks.
Oh ya, I am running CleanROM Inheritance 3.0.4, fsync disabled, scroll cache disabled, and force GPU rendering.
Cant wait to see how this flies after Data2SD Mod (cant apply until i get back home to Halifax - East coast represent)
Best of luck
Click to expand...
Click to collapse
Just finished stressing the machine quite hard, everything is stable so far, temperature hasnt gone up at all either
Just thought id mention.....
GOT A SCORE OF 7524 IN QUADRANT.....BEAST MOOOOOODE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
MUUUAAHAHAHAHAHAHAHAAH! I VILL TAKE OVER ZE VOOOOOORLD

LOL okay let's see how much this drains on your battery!
Preferably show battery screenshots instead of just words

xFrozen said:
LOL okay let's see how much this drains on your battery!
Preferably show battery screenshots instead of just words
Click to expand...
Click to collapse
Good call, I forgot that most ppl would be interested in the battery drain.
I was fully charged before flashing new kernel, I have used for over 4 hrs, been doing heavy browsing, stress tests, and benchmark tests....all in performance mode.....im at 67% dock, 76% tablet...I keep screen brightness around 20%-25%. Havent noticed any more drain than usual.
Ran a benchmark test in balanced mode and got the same results as I used to get with 1.5-1.8 Ghz/700 GPU kernel....if you are worried about stressing your system leave it in balanced and switch to performance mode when needed.

Troo that overclock to 1.9 is a battery killer.
Have to say I didn't stay on it very long

Thats OK said:
Troo that overclock to 1.9 is a battery killer.
Have to say I didn't stay on it very long
Click to expand...
Click to collapse
That sucks I havent seen much of a battery hit at all. For the past 2 hrs ive left it in balanced mode and there is no diff b/w 1.5-1.8 kernel at 1450mV. I didnt use the 1400 mV kernel for very long bc i didnt notice any battery improvement, maybe the 1400 mV kernel is much better, are you using 1400 mV kernel?
Ive been using my tab for 5 hrs in performance and 2 hrs in balanced and im still at 33% dock and 87% tablet. Thats essentially the same as it used to be, should get at least get a full day of heavy use, especially considering I have been running stress tests, benchmarks, and repeated cold boots to make sure its up to snuff.
The screen and wifi are the biggest battery consumers, overclocking from 1.5-1.8 to 1.9 shouldnt hit battery too much.

maybe
maybe the 1.9 isnt kicking in, maybe try playing some shadowgun or something to see ur battery time,

killerdan56 said:
maybe the 1.9 isnt kicking in, maybe try playing some shadowgun or something to see ur battery time,
Click to expand...
Click to collapse
I dont have any games. Games are cool, I just dont play them, and will never put a game on my tablet lol. I really cant say how battery would be affected by this kernel when gaming.
You might be wondering why I even bother with this kernel if I do not game. Well, my good sir, I happen to be a performance junkie, and cant stand lag of any sort lol. Multitasking is what i focus on, this tab has replaced all my other devices, and am happy to say my workflow is smoother and faster.

From my personal use I think the kernal rocks! I have used it before and just went to it again recently. The only reason I switched was because the Rom I used didnt have the option to install that Kernal and I was too lazy to flash it again. On a regular everyday use I keep it in balanced mode and really dont see a hit in battery. I personally only saw a little bit of battery drain in gaming however in the graphic and CPU heavy games there was battery drain anyways. I can deal with plugging it in more to get more performance out of my tab. I am one of those people that has 5 home screens, ones dedicated to all of my games and its fully filled with 6 different folders each containing atleast 10 more games. This would definitely slow down my tablet however with this Kernal its different. I also get around the same results in quadrant 7436 to be exact.I do see a temp increase but its not too large so I can deal with it.
Over all I think its the best Kernal out right now hands down.

Just curious - why do you even power-off your device to begin with? Normally, "mobile devices" are meant to be on always-on anyway, so I just don't see why the cold-boot time is such a big deal. The device goes into a deep-sleep state when in standby with very little power drain, which pretty much eliminates the need to constantly power off and back on the begin with.
Do you really completely power-off your device on a regular basis?
Again, just curious - obviously, that's completely up to you...
Personally, I only reboot my TF700 when flashing kernels and/or ROM's - otherwise it's always on. That way you never have to wait for it to boot!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

I don't think the boot time has nothing to do with 1.8 or 1.9 kernel, my cold boot is about 22 sec. They should be about the same depended on how many app services you have running on your device.

jtrosky said:
Just curious - why do you even power-off your device to begin with? Normally, "mobile devices" are meant to be on always-on anyway, so I just don't see why the cold-boot time is such a big deal. The device goes into a deep-sleep state when in standby with very little power drain, which pretty much eliminates the need to constantly power off and back on the begin with.
Do you really completely power-off your device on a regular basis?
Again, just curious - obviously, that's completely up to you...
Personally, I only reboot my TF700 when flashing kernels and/or ROM's - otherwise it's always on. That way you never have to wait for it to boot!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I cold boot all the friggin time lol just my personal preference. It feels snappier after cold boot and I am constantly deleting stuff and trying new things/setups/setting configurations to eek out more performance, after each change I cold boot to get an accurate assessment of the changes that I have made. Lately ive been spending several hours a day trying to improve tab, which has meant a lot of cold boots. For the past few weeks ive spent more time optimizing and assessing this tab than acually using it, kind of nuts, i know lol, but i really enjot it and im off school right now and my hometown is in the middle of nowhere, less than 100 ppl live in my town lol. I normally shut down before bed, and do another cold boot after I finish classes around 7, boot time matters to me.
Oh and I will not charge this thing if it is on, I figure that draining the battery (no matter how little) while charging cant be good for its life long term.

buhohitr said:
I don't think the boot time has nothing to do with 1.8 or 1.9 kernel, my cold boot is about 22 sec. They should be about the same depended on how many app services you have running on your device.
Click to expand...
Click to collapse
I honestly dont know if it should or shouldnt, all i know is that i was booting in about 40s-45s before flashing 1.9 kernel, now i boot in 30s, Ive seen results by doing this. I time my boot times with stopwatch on my phone, i monitor everything going on in this tablet very heavily. Every time i change anything i like to be able to assess its overall impact on performance.