Thanks for providing so many details . That should certainly help. So, it's good to know your phone is not draining much while the screen is off. While that probably means the phone is sleeping, your awake usage seems high for that amount of uptime (around 50%). You didn't provide a screenshot for partial wake usage since last unplugged in spare parts. That might be useful. I know your pone seems to sleep fine, but covering all the bases doesn't hurt.

So, I think what you're going to need to do is try out a few more kernels. What all have you tried? I suggest you try a few of these combinations (all using conservative governor):

1) NA 4.3.2 CFS HAVS with no profiles (in theory they should work as long as you're not using the smartass governor, as you said, but try it without. screen off profile should be fine, though)
2) NA 4.3.2 CFS noHAVS with profiles.
3) NA 4.3.2 BFS HAVS with no profiles
4) NA 4.3.2 BFS noHAVS with profiles
5) Ziggy's - Ziggy471.com Life's too short, have fun while you can.. This seems to be more of a performance driven kernel, but you should see how it goes, anyway.

Give that a try, and see how it impacts screen on battery life. Just remember, if you use the phone a lot, it's going to drain the battery quickly. That's just the way it is. Granted, it does seem like you're not getting as good of battery life as you should, but I've found that being paranoid about it makes me check my phone more often, which makes the battery drain faster... Just something to think about.

 

1) It's hard to know if that's a problem with maps or not without knowing how long ago you unplugged the phone. If it was minutes ago, that looks normal enough. If it was hours ago, maps did not stop properly, and is still running. In which case, you need to go force stop it. It happens to me with maps from time to time.

2) BFS *typically* has slightly worse battery life (at least for me), but you have to try both. Every phone is different in that case. Some get better battery life with BFS.

3) Your profiles look fine. The only comment I have is that the frequency steps you've taken are so small that you're not likely to see *that* much of a battery savings, but you might get something out of it. Also, unless it's below the fold and I can't see it, you may as well throw in a profile to not underclock (normal min/max) when the phone is plugged in. No reason to underclock in that case; just give it a higher priority (even higher than screen off if you like). Also, a > temp profile can't hurt either. Neither of those have anything to do with battery life, but you asked .

4) HAVS is meant to save battery life, pure and simple. BUT, not all phones react in a way that actually saves battery. For one, it can make your phone a little unstable. That instability can range anywhere from obvious problems such as screen tearing to something not so obvious such as...say...bad battery life. Since you're getting good battery life while the phone is sleeping, that's not terribly likely, but keep it in mind. Also, it has the same issues that something like auto-brightness has (though maybe not as apparent). What I mean by that is, you're constantly adjusting something that is normally a battery hog with the attempt to save battery life. But the fact that you have to constantly adjust it means that the CPU is working to do so. Just something to think about. Basically, this is what I would suggest as a general rule for everybody:

a) If you use your phone constantly, and it spends more time awake than it does sleeping, use a non-HAVS kernel. The phone will be at higher frequencies most of the time, anyway, so, HAVS is just making your phone have to think about what to set the frequency at constantly.

b) If you use your phone with moderate usage or less, and it's idle potentially a few hours here and there at time, use HAVS, as you'll get better battery life with constant lower frequencies.

Maybe you'll notice better/worse battery life out of those things or maybe you won't. It's just a general rule, and you have to test it for yourself.

5) Well, like I said, each phone reacts differently to different types of kernels. There is a possibility that there could be other things going on. The best way to get a base line is to make a nandroid backup, then wipe cache/dalvik/data from recovery, reflash your ROM, then use the phone for a couple days with no other apps installed or any mods applied. If it's better, then something you installed or flashed could be an issue. Also, use something like OS monitor to see in real time if some process or another is running hot.

6) Yeah 3-4% per minute is a bit much if you're not doing anything like browsing the web or watching videos (then, well...don't expect much ). Try some of the above suggestions, and see what happens.

 

No problem. Let me know how it goes.

 

Just for sake of clarification, I'll give a brief description of all voltage effecting options (don't mean to patronize, but it could help others reading this):

HAVS = Hybrid Adaptive Voltage Scaling.

HAVS - The voltage supplied to the CPU is variable. As the frequency goes up, the supplied voltage increases. Likewise, as the frequency goes down, so does the supplied voltage.

non-HAV/no-undervolting (aka stock behavior) - Constant voltage is supplied to the CPU. That amount of voltage is about what is supplied in the stock kernel.

non-HAVS/static-undervolting - Constant voltage is suupplied to the CPU, but that amount of voltage is lower than what is normally supplied.

Basically, HAVS means lower frequency/lower voltage and higher frequency/higher voltage. non-HAVS with normal voltage means lower and higher frequency with a higher voltage. non-HAVS with undervolting means lower and higher frequency with a lower voltage. Try both and see how it goes. Likely, you'll get better battery life with static undervolting, but it *could* cause instability.

 

Haha, I'll never patronize on purpose; I just have a hard time telling how much information some people already know. I'm glad it helped

 

Buy a bigger battery?

Sorry.. I just had to.

 

Give it at least two charge cycles. What you might want to do is charge it all the way up, unplug it, turn it off, plug it in until the light turns green, unplug it, plug it back in until the light turns green again, then wipe battery stats. That's basically a bump charge. The battery stats wipe is a formality. There's no real proof that it does anything. From there, see if you get better battery life.

 

Hehe, that is an option too. Let's consider that the last resort .

 

definitely give it longer. That drop appears about normal during that length of time on a non sbc kernel, then it should slow down quite a bit.

I got much better results on my phone by killing all of those profiles. I went simply with a screen off profile/conservative and noticed much better results than a slew of other profiles.

are you overclocking/underclocking under normal use ie what are your settings on the main screen of setcpu

 

Sometimes there is no (good or easily explainable) rationale. It's actually a good suggestion. Try it both with and without profiles, and see if one works better than the other.

 

ok not really scientific....but I compare it to an ac unit constantly cooling a really really hot area that cools quickly...

the rapid scaling of several scenarios seems to make a difference. in my case...I had much better battery results with just the screen off profile, and performance was stable.

performance really took a beating when I had all of the profiles set up. the phone was rather confrused

 

Well, that's sort of relates to what I was talking about with HAVS, and how it can be worse for the battery when you use the phone a lot. Profiles, though, should just change the max/min under certain conditions. I guess it boils down to how setcpu works. If it's constantly having to check profile conditions, then that does make sense. On that note, I don't use a whole bunch of profiles for the same reason, but some people have had better results using them, so it's worth trying both, for sure.

 

Im going to try these as well, because i dont always have what i think is the best battery life either.

So im starting with 4.3.2 noHAVS with static undervolting. Same one JP is trying out.
And i set up some profiles with setcpu. From the top down:
Charging........245/998
Screen Off......128/245
Temp>44c......128/729
Battery<50%..128/691
Battery<35%..128/499

My "main" is set at 245/998..conservative.

Im going to try with then without profiles.
When i try without, should i stay on conservative or switch to smartass?

(I chose noHAVS because i tend to be on my phone frequently. I have great battery during [rare] longer periods of sleep. But like JP, when i am using the phone and in need of the battery, such as while im out, it drops like a brick)

 

If you're going to try with, then without, keep the same governor. Changing too many things at once will not give you a good idea of what is causing battery drain, or what actually fixed an issue . I'm starting to think Mr. Ed might really be on to something with a lot of profiles not helping. If you think about it, when you use profiles, it constantly has to poll to see if it should active. Try it with both, and see how it goes, but certainly keep the same governor. Even if you don't keep the other profiles, and screen off profile can't hurt.

 

That sounds pretty good. Ill give it a day or two, then take the profiles off except for screen off and leave it on conservative.

 

Hmm, unfortunately, it's going to be hard to tell without you having looked at spare parts partial wake usage, first. I'll tell you what - don't reboot the phone. Unplug it whenever you get a chance, then let it sit for an hour or two. Whatever caused the problem before might still, but certainly rebooting it will screw that up. Check partial wake usage after that. For a better idea, still don't reboot, see if it does it again tonight, then check spare parts, first thing. Unless you have some bad combination of kernel/mods/profiles, this must be something else.