[Q] CM7 + Glitch Kernel not down-clocking - Fascinate General

Been lurking for close to a year, but first time posting, so my apologies if this is not the correct forum or location for this question. I would have posted in the Glitch kernel thread but I'm still stuck in the noob-lockout.
I'm running the latest CM7 with the latest, high-leakage Glitch kernel. I became suspicious after I "calibrated" my battery (charged to 100%, reset stats, drained to 0%) and noticed that my battery life was much better while in deep sleep, but with the screen on it was draining at almost 1% per minute. In deep sleep I will get somewhere between 2-5% drain per hour.
CPU Spy shows my frequency breakdown as 1000Mhz at ~10% and Deep Sleep at ~90% with all other frequencies at virtually 0% (this is with resetting the timers and running for a day).
I would think that even with the screen on, there will be moments when the CPU will be throttled down. Running SetCPU on previous roms, I noticed that when idling, the CPU speed would often drop to 100Mhz, but this doesn't seem to be happening with my setup.
I didn't notice any comments in the Glitch or CM7 threads regarding this phenomenon, so I'm wondering if it's something I failed to setup correctly or some other cause.

As an update, I've switched back to the stock CM7 kernel and it is properly throttling down now. 100Mhz is now showing a much higher percentage in CPU Spy.
I would really like to switch back to Glitch, but unless there's some solution it doesn't seem like it's worth the huge increase in battery usage.
Sent from my SCH-I500 using XDA App

You must have a setting incorrect.
Being clocked at 1.2ghz (BFQ i/o and Smartass) CPU spy is telling me the following
1200Mhz - 4:03 - 0%
1000Mhz - 1:01 - 0%
800Mhz - 9:05 - 1%
400Mhz - 7:037 - 1%
200Mhz - 4:59 - 0%
100Mhz - 21:09 - 4%
Deep sleep - 7:40:15 - 90%
What Governor did you try?

I was using bfq with smartass.
Sent from my SCH-I500 using XDA App

I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?

Cota82 said:
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Click to expand...
Click to collapse
Are you experiencing the same increased battery drain with the screen on?

1. Using SetCPU is asking for trouble (random reboots, etc). The Glitch thread OP says to use Voltage Control instead.
2. High Leakage = fewer problems for those with lower quality hardware build (yes, it varies from Fascinate to Fascinate - all Fascinates are not assembled equally), but poorer battery life. Low-leakage = better battery life, but you better hope your Fascinate was assembled well because if it wasn't, you'll have more fcs and freezes than on medium or high leakage.
3. There is no combination of governors, voltages, and schedulers that is the best for everyone - each combo will work better for some than for others
I hope this helps
Another Fascinating post by my XDA app...

I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.

lagbot7000 said:
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
Click to expand...
Click to collapse
Try an overclock - train your phone to use something other than 1000 Mhz
Another Fascinating post by my XDA app...

I decided to restore back to DI01, and use the OTA updates to bring myself back up to ED05. I then reflashed CM7 and Glitch and this problem has gone away. Not quite sure what caused it, but it's running great now.
Running at a solid 1200Mhz with -50mV.

Yes still draining, locked up in 800 mhz cpu freq. (cpu spy) and no deep sleep mode. I'm going to reflash the kernel soon.
Something went wrong I guess (stucked in glitch bootscreen after flashing).
First cleaning scripts and flash the default cm7 kernel for my sgs to be sure.
It should work well according to a member in glitch sgs topic.

Related

Phone not waking up after Set cpu?

Hey guys any of you running set cpu? i have a profile set so that when i turn the screen off it drops the cpu down to 250mhz. I'm having a issue where sometimes it dosen't wake back up. Anyone else had this happen?
I noticed this Tuesday. They don't play nice together...yet. setcpu needs info about the hummingbird cpu in order for it to work. Setcpu's dev will most likely have an update for this soon. For now, i'd uninstall it and keep an eye out on the program for an update.
sweet glad to know that its not just me.
I had this same problem with the Overclock Widget for the same purpose (shut down CPU while screen sleeps)... After removing Overclock... I have yet to have a blank screen situation.
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
madocs said:
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
Click to expand...
Click to collapse
Scratch that - this morning the EPIC didn't wake. Battery out, back in, screen off, didn't wake.
Uninstalled SetCpu, all is back to normal (except for the crap battery life of course).
Emailed the SetCpu dev, he thinks it is related to the kernel. I'll try out a custom ROM/kernel as soon as one is ready to see if it resolves the issue.
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Chalup said:
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Click to expand...
Click to collapse
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
vavaud said:
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
Click to expand...
Click to collapse
How long have you had it in use? I was cool for a day, then it wouldn't wake up.
From the dev: "The scaling is the issue, I think. Ondemand crashes the Galaxy S, but conservative doesn't seem to."
I'm ready to hit some customs, battery life just isn't good enough so far.
2.0t03speed said:
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
Click to expand...
Click to collapse
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I was using conservative on set cpu when i got the lockup
Sent from my Epic 4G
I have been using setCPU and ATK since 9/2 with no problems so far. I have it set on conservative and 200 when screen is off. I been getting around 10-12 hours with moderate uses. With little use today I am at 9 hours with 50% battery left.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I ended up at with over 15 hours logged and ~15-20% battery remaining last night. Good enough for me. Bluetooth/GPS/Wifi on all day, 4G off, screen turned down, ATK.
No Problem with CPU Set at 200
I kept having the same issue until I changed the lower limit to 200 and used Conservative setting.
Now, no problem at all!
I think I tend to agree with you.... I tried running the phoenix kernel on my epic, and the phone would not wake up (was told it was because phoenix defaults to 100/1000) and was told to use setcpu.. tried it... wow... what a disappointment.. setcpu kept giving me way different readings everytime I ran it.... not nice at all....
I've since tried this again, this time, placing setcpu.txt on my /sdcard will see if this helps..... so far, so good......
I have a screen off profile set for 400mhz max 200mhz min with conservative governor. My main profile is 1200mhz max and 200mhz min. This is with the mixup kernel and I never have any lock up issues
Sent from my Emotionless Beast of an Epic using the XDA App
i have my min at 200 for all of my profiles. My screen max is 400 and it keeps my phone from waking up. It's set to conservative. I'm also using it with juice defender, so i'm not sure if that's the culprit or what. Does anyone else have any suggestions on settings for screen off?

Possible fix for random reboots on Gingerbread

Here are my current stable settings:
SetCPU
Min: 100mhz
Max: 1000mhz
Governor: Ondemand
Profile: Screen Off
--Min: 100mhz
--Max: 200mhz
--Priority: 100
--Governor: Ondemand
Tegrak:
Governor: Ondemand
Scaling: 100-1000mhz
Optimization:
--200mhz Core Voltage: 1025mv
--100mhz Core Voltage: 925mv
Both SetCPU and Tegrak are running side by side.
No random reboots for over a week.
Battery should last between 20-25 hours with normal usage.
Certain phones might need a higher voltage, you may need to do some experimenting to get things stable.
Old text
Anyone experiencing random reboots should try using SetCPU or Tegrak to set the CPU to 1000mhz-1000mhz instead of 100mhz-1000mhz.
I was previously getting 3-4 reboots per day. I set my CPU to 1000mhz-1000mhz using Tegrak four days ago and have not had a single reboot since.
Sure, my battery only lasts about 10 hours vs 20 or so, but at least I can rely on my phone.
Of course I could just be lucky, and who knows it might just randomly reboot any time now.. So, obviously there is no guarantee it will work for anyone else.
Just as a note I also tried 200-1000 and 400-1000, but still had random reboots every few hours.
I am currently testing 200mhz-200mhz with the screen off and 1000mhz-1000mhz with the screen on using SetCPU. I will update this thread in a few days or if it randomly reboots.
Update: 200mhz during screen off causes the phone to not wake up (happened three times). I'm currently testing 400mhz.
Update 2: I got a random reboot last night while asleep using 400mhz. I will see if it continues.
Update 3: Got another reboot at 400mhz. I am now testing 100mhz-1000mhz at 1.275v Core and 1.100v Internal for all frequencies, this should rule out any voltage issues.
Update 4: Made a spreadsheet with my findings, it does not seem to be a voltage issue.
Update 5: Scratch that, I have been using a [email protected] screen off profile for the last 20h... No black screen of death or random reboots. Next up is [email protected]
Update 6: [email protected] is unstable, rebooted after 3 hours. Testing [email protected], 6 hours in and no reboots yet.
Update 7: [email protected] seems to be stable, 24 hours and no reboots yet.
Old text
Click to expand...
Click to collapse
Here is a spreadsheet of my current findings.
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, but for some odd reason this (seems to have) fixed it for me. Although, on EG22 I also got a lot of random reboots, so maybe I have a different issue.
I did not get reboots on ED12, EE03, or EF02..
EG22, EH06, and EH17 randomly reboot for me.
I thought it might be similiar to the sleep of death phones would get going from 100 Mhz to deep sleep and also tried boosting to 200 Mhz on EH17 but it didn't help. It may be related and your discovery may aid Devs in fixing the problem If it is still there when source is released.
Sent from my SPH-D700 using XDA App
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
xopher.hunter said:
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1 That's what I think.
That would explain why my phone never reboots with the screen on.
I think we may be onto something in this thread.
Sent from my SPH-D700 using XDA App
Agreed. My phone has always randomly rebooted when the screen is off. I set the minimum to 400 Mhz as well. Will let you know what goes down.
Someone should point the SamSprint devs to this thread lol. That would be amusing if it was in fact the problem/solution to random reboots.
Sent from my SPH-D700 using xda premium
Ok, so far 400mhz screen off has been stable, 12:56 on battery, and 1:01 screen on time.
I noticed something.. Here is what CPU Spy says:
1000mhz: 00:55:03
400mhz: 1:35:09
Deep Sleep: 9:22:42
I reset the stats once, which is why 1000mhz is 6 min different from the screen on time.
The phone was asleep for 11:55, but it was only in deep sleep for 9:22, what this tells me is when the screen is off and the phone needs to "do something" (I have Skype open 24/7, and 3 accounts in k9)it will jump up to 400mhz (or normally, anywhere between 100-1000mhz) for a time until it is finished, and then drop back into deep sleep.
It might be worth a try to bump up the voltage for 100mhz and 200mhz and see if that helps anything.
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
If its really this simple as far as clock and voltage how the hell does Samsung not find that.
Sent from my SPH-D700 using xda premium
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
ss4rob said:
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
Click to expand...
Click to collapse
SetCPU is free for xda members
Sent from my SPH-D700 using Tapatalk
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
radugb said:
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
Click to expand...
Click to collapse
What scaling are you using?
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
omair2005 said:
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
Click to expand...
Click to collapse
Good catch. Here are the voltages on EH06 (as reported by Tegrak):
1000mhz
Core Voltage: 1275mv
Internal Voltage: 1100mv
800mhz
Core Voltage: 1200mv
Internal Voltage: 1100mv
400mhz
Core Voltage: 1050mv
Internal Voltage: 1100mv
200mhz
Core Voltage: 950mv
Internal Voltage: 1100mv
100mhz
Core Voltage: 950mv
Internal Voltage: 1000mv
Could someone list out the stock voltages on EC05?
Lord-Anubis said:
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
Click to expand...
Click to collapse
That is what I thought at first... But then I tried the EF02, and EE03 modems and still experienced reboots (I am currently on the EE03 modem).
poit said:
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
Click to expand...
Click to collapse
While this is true (for now) it could lead to a more viable fix. If the voltage actually is lower in GB, that could be at least part of the problem.

Quest for the best battery life.

Day 1:
Flashed Simple and Clean v1.3
2.6.35.7 speedmod test3 k2 kernel
Juice Defender Ultimate in Agressive mode.
Batterylife: 11 hours. Lost most of the life when the phone and I were both asleep during the night. It went down from 100 to 38%...
PS: If anyone wants to give me their set up so I don't have to spend so long on this quest, that would be appreciated...
There are 2 more threads with the same topic, with much more info. Also, we know nothing about how you use your phone, except that you have huge wakelocks. Not really helpful tbh.
care to point out those threads for me?
convolution said:
care to point out those threads for me?
Click to expand...
Click to collapse
you could actually use the search function
PS - Ditch Juice Defender it uses up as much battery as it saves, trust me this is fact.
I did. I tried some of the solutions posted in some threads like using speedmod + clean n simple, and also lightning v6.1 and ninphetamine kernel; doesn't work.
I used to have the Galaxy S Vibrant before I got the S2. I swore by Juice Defender. I would get on average 45-60% more battery depending on usage (phone was rooted with OCLF installed). My S2 gets an additional 2-3% more life while running juice defender. Takes more than that to run it. My opinion, remove the app.
I am running sensation 1.9 rom and hardcore speedmod kernel. I work oh average 11 hours a day. Phone isn't used much during that time. Wifi is always on and by the end of my shift, it's at 94% or so.
When I get home, my phone is put through some heavy use. Facebook, youtube, texting galore and internet browsing. I always have 25-30% battery left at the bare minimum written I go to bed at 6-8 hours later.
In my personal opinion, this rom and kernel combination give me the best power (4700 on quadrant), best options (configuration got nearly anything) and best battery life (phone lasts all day with ease). I would recommend this to anyone in a heartbeat.
-Chris
Sent from my GT-I9100 using XDA App
I'd recommend the Hyperdroid rom. A lot of users (including myself) have hit 5 hours screen on time (most I've seen is 7 hours). Phone can easily last a whole day, just need to check for wakelocks using BBS. 60% overnight is ridiculous lol, you should really be losing 1% every 4-5 at least unless you have loads of people ringing you all night
My setup
Rom: Hyperdroid 2.9.0
Kernal: TWD2.5
UV with voltage control
200mhz - 1200mhz
Sio I/O - Lulzactive governer
Max Screen On Time - 5 Hours 28 Mins
Facebook/Whatsapp Syncing
Read the guide i posted yesterday, its a bit long, but will definately save you battery life.
http://forum.xda-developers.com/showthread.php?t=1351663
Also my setup is in my sig - very fast, very slick and above all great battery life (range between 20hrs and 28hrs moderate use)
I read the long thread. It has some points in there I didn't know about.
Will try HyperDroid Rom.
Tried Sensation. Battery life failed for me with that ROM. Will try it againwith speedmod kernel if HyperDroid doesn't work...
btw, what governor is the best for Hyperdroid?
i use
check/leo rom v 3.1.1
siyah kernel 2.2 beta6
ice cream sandwich theme
the kernel is set at smartass v2 governor
1.4ghz - 1300mv
1.2ghz - 1275mv
1ghz - 1150mv
800mhz - 1050mv
500mhz - 950mv
200mhz -900mv
100mhz - 875mv
my sgs2 doesnt like undervolting so them settings should be safe to use on most sgs2 handsets
i then have the following profiles
screen off 100mhz -- 200mhz
charging 100mhz -- 500mhz
in call 100mhz -- 500mhz
battery at 60% set cpu to 100mhz -- 1ghz
battery at 30% set cpu to 100mhz -- 800mhz
battery at 15% set cpu tp 100mhz -- 500mhz
getting excellent battery life with my sgs2
ive also frozen any apps i dont use via titanium and used a start up manager to stop certain programs starting at boot
i used to use juice defender but on the sgs2 it doesnt seem to wrk as well at all
i was getting wakelocks from facebook chat draining my battery so i have installed an app to auto close that when the screen goes off and that has saved me more battery and kept wakelocks down
as other users have said its all about how you use your phone , the settings above might be useless if you have lots of background tasks going on as a screen off profile off 100mhz -- 200mhz may not have enough power to do your background tasks however when my screen is off i want my phone to go to deep sleep and not consume power etc so a very low screen off profile suits my needs as does a low charging profile as i dont use my phone on charge and 500mhz max power suffices my needs for when the phone is charging
same goes for setting a battery % profile i know when my battery is at 15% i wont be playing high end 3d games so it makes sense for me to try and save battery and limit the cpu to 500mhz at that battery percentage but other users may want full power all the way till their battery dies , it all depends on what you want and do with your device
Day whatever:
Used Hyperdroid ROM: Battery Life is AMAZING!
Using their 2.5 TW kernel as well...
The first thing I did was restore all my apps with Titanium Backup, but then I got crappy battery life, so I reflashed the ROM but this time, I didn't restore any apps.
I got amazing battery life!
So it was an APP's fault!
yeah sometimes apps are rogue. Hyperdroid has an awesome kernal though, someones just hit over 8 hours screen on time with stock battery which is amazing. betterbatterystats would show you apps that are causing wakelock problems. I do use some app called gemini just so I can stop apps loading from boot (haven't been bothered to search for autostart apps). Fresh wipe is good sometimes though, fresh and clean is the way to go unless your upgrading from the same line of roms
DramatikBeats said:
yeah sometimes apps are rogue. Hyperdroid has an awesome kernal though, someones just hit over 8 hours screen on time with stock battery which is amazing. betterbatterystats would show you apps that are causing wakelock problems. I do use some app called gemini just so I can stop apps loading from boot (haven't been bothered to search for autostart apps). Fresh wipe is good sometimes though, fresh and clean is the way to go unless your upgrading from the same line of roms
Click to expand...
Click to collapse
DB i manage minimum screen on time with rom/kernel combo over 5hrs.....and it saved me money from getting a extended battery. why you think i aint been back on foxy yet...and even though i love raffaeles work (foxy and androidmeda is the top two) for me its all about battery life and that one has done it for me nxt stop though is ICS

Time spent in (clock) governor discussion

So, I futzed around with NStools, and setCPU, trying to find the ultimate governor combination.
With ondemand, no matter what my max clock was, I always had lag, because while it did scale fast, it sampled too slow, even at the lowest allowed.
A big issue was that governors would scale to high clocks, but took too long before it decided to scale up.
I noticed that smartassV2 was willing to scale at smaller intervals, but was WAY too jumpy for going up... after all, why have unused clock cycles. If you're at 75%, and you jump up a notch, you'll be at like 50-60%.
I came to an idea.
I originally tried init.d script to do this, but for some reason on swagged out stock, init.d scripts aren't working for me. Note, I stripped a lot of components from swagged out stock using titanium backup, or just simple uninstalls. It is SOS N running aggressive lionfish 1.8. The stripping of components lowered my memory usage significantly.
I took setCPU, set max to 998mhz, and min to 128mhz, set on smartassv2 with no profiles.
I took NStools, set as follows
scheduler to SIO
cpu to smartassv2
min freq 128
max freq 998
awake ideal freq, sleep ideal freq, and sleep awake freq to 100,000hz,
min cpu load to 85%
max cpu load to 100%
ramp down step to 38400hz
ramp up step to 38400hz
down rate to 10000
upr rate to 10000
Before I did this, I've never experienced this level of smoothness. The real kicker is what setCPU says my "time spent in" is
I wiped my battery stats last night, and let it run down till 10%
I'm at 97.98% of my time spent in 128mhz after over 24 hours, yet it feels perfectly smooth when I play with it. I think part of this is the fast sampling response time of Smartassv2, and also the fact that my rom is running light.
It clocks up, does what it needs to do, and rapidly clocks back down.
How are you guys doing on that chart?
If your phone spent 97.98 % of 24 hours on 128 mhz is not really good. When you don't use the phone, it should go into deep sleep. Download cpu spy from the playstore. If your phone doesn't go into deep sleep, it means you have wakelock issue.
Sent from my lair.
SetCPU was reporting some of the time as 128mhz when it was actually deep sleep.
I checked out CPUspy, and it reads at 51% 128mhz, and 43% deep sleep, with 1036 to 1228 unused, and 62:45:58 of recorded data time.
Out of that, 32:30:15 was in 128, 27:25:01 was in deep sleep, while most of the rest was between 245 and 449, with 00:26:28 on max speed
Does this mean something is waking me out of the 128hz range, while its asleep, and I need to figure it out? I read something about gtalk with video having a wakelock issue, and I have that.

Frequency and voltage settings.

Caveats: Every CPU and GPU does not come from the same bin, fabricated on the same date and possibly not manufactured in the same facility. They may each display different physical properties and a wider range of stability than others. What works for me may not work for you.
That being said, I've been stress testing my device with different settings for the past couple weeks trying to find a sweet spot of stability, speed, battery life and heat output.
I'm going to share two setups: my current one that I've stress tested for less than 24hrs but has proved stable through all conditions encountered thus far and my tried and true setup I've used for over a week with no trouble.
Tried and true setup:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 800mV
200MHz - 825mV
300MHz - 850mV
400MHz - 900mV
500MHz - 900mV
600MHz - 900mV
700MHz - 925mV
800MHz - 950mV
900MHz - 1000mV
1000MHz - 1025mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1250mV
1600MHz - 1350mV
Experimental but stable battery saver:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 775mV
200MHz - 775mV
300MHz - 800mV
400MHz - 800mV
500MHz - 825mV
600MHz - 850mV
700MHz - 875mV
800MHz - 900mV
900MHz - 950mV
1000MHz - 1000mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1225mV
1600MHz - 1350mV
GPU setup:
Low power state - 100MHz @ 800mV
High performance state - 400MHz @ 1050mV
Notes:
Custom governors were not stable for me AT ALL! I've found ondemand to be the best one for me and my needs, personally.
100MHz @ 750mV was so, SO close to being stable for me but my phone would routinely reboot in the screen off state. I'm assuming the stress of apps updating in the background, notifications etc was just too much.
As much as I love WidgetLocker (and I really do!), I found it to consume valuable resources, have more pronounced wake up lag and generally contribute to instability.
I use Chainfire3D to run my games etc. at x4 MSAA. As previously stated by Chainfire, the Mali can run at x4 with almost no extra overhead. I imagine that if one doesn't use x4 MSAA, one *might* be able to get away with 400MHz @ the stock 1000mV setting. That being said, I consider an extra 50mV to run at 133MHz faster to be a bargain.
Many games can be run with x16 MSAA with minimal overhead but I've found that for some resource intensive ones, especially multiplayer, they'll slow down unless the GPU is fed at 1200mV but this in turn causes a lot of heat generated so I would advise to avoid turning on x16 MSAA for those that you do find slowing down.
I use and recommend Voltage Control (donate version for extra features!) for setting up clock range and voltage for both the CPU and GPU. It also allows one to set boot settings (at setup or init.d script) and create multiple profiles. I do not recommend init.d script for untested settings as it could cause you issues.
Edit: Not everyone's kernels may support GPU OC/UV or the CPU ranges listed here. I am not responsible if you bork your device.
Here's someone else's method for testing settings:
Here's how I test UV settings.
Turn on everything. Wifi, bluetooth, max brightness, the whole works. This ensures the system is at maximum strain.
Start at maximum CPU clock
Lock the CPU clock (set the minimum and maximum allowed clock to the clock you are currently undervolting)
Lower the voltage by one step
Start a benchmark for a few minutes to see if undervolted clock is stable
If it passes, lower it again go back to step 4
When it freezes up your phone, reboot it and increase the voltage at that clock by two steps and consider it safe
Move to next frequency and go back to step 3.
You reached your lowest clock? Congrats, you should have a well undervolted CPU
Your voltages should always be lowering when your go from the highest clock to the lowest. If it happens that you have to increase the voltage at a lower clock, then also increase the higher clock frequency. I had a few hard locks because of this.
Example.
1000mAh (1GHz) > 900 mAh (900MHz) *< 950 mAh (800MHz) * > 700mAh (600mAh)
The 800MHz voltage is now higher than the 900MHz voltage. Also increase the 900MHz voltage to the same or higher voltage of the lower one.
1000mAh (1GHz) > 950 mAh (900MHz) > 950 mAh (800MHz) > 700mAh (600mAh)
Now that you have it undervolted, you may find that it could hardlock/reboot on you. When it happens do this:
Increase the voltage on all undervolted clocks by one step.
Continue using the device for a day
If the device locks up again, go back to back step 1
If its ok for a day, then every day lower the voltage back to what you had of only one clock (I suggest you go from highest to lowest)
You should be able to find which undervolt caused the reboot fairly quickly and still be able to normally use the phone and keep the rest of the "optimal" undervolts.
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Boy124 said:
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Click to expand...
Click to collapse
I'm not sure if you've read everything through carefully or you would have seen that I've covered several of your points.
You also would have seen the method I use for stress testing and would have noted that I aim for four things: speed/performance, stability, power management AND thermal regulation.
While I agree that the display, barring a wonky or misbehaving app, will almost always be the #1 battery drainer - power management will certainly help to conserve battery life.
You also would have seen I mention profiles. There may not be a one size fits all setting for everyone but one can most certainly set up profiles for different scenarios.. Such as TiB backups/restores.
Sent from my GT-N7000 using xda premium
Did you do some benchmarks at the highest speed several times to make sure you are getting extra performance? With this phone I noticed that while the phone wont crash.. .some times performance will drop when running at settings now fully correct.
Sent from my GT-N7000 using XDA
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Edit: guess I was wrong here
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I actually did the test on Gingerbread.
I set min and max to 200 MHz, activated flight mode and had stock music player running for 3 hours - with undervolt and without undervolt.
To my surprise battery consumption was the same.
May be experts who know about our processor architecture can shed some light here.
Boy124 said:
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Click to expand...
Click to collapse
I understand where you're coming from, boy.
I don't have data at the moment though I wish I did. But to be honest, it'd be scrambled anyway since whenever I'm not working or mission critical when I need proven stability, I'm testing out all different sorts of settings leading to lots and LOTS of reboots and such!
That being said, anecdotally, I have seen improved battery life for myself but maybe it's a placebo and I could be wrong about it - I have been before in the past. I do feel though that under my normal usage scenarios, I am experiencing less battery drain. It's difficult to quantify though exactly what this is due to since I experiment with kernels, voltages and frequencies.
But if all I'm getting is a 2% boost, man - I'll take it! Like any modder, whether it's min/maxing in a game, working on a car or whatever else, every little bit of a parameter squeezed out is something.
I also feel that you're too caught up on a single aspect, the battery life thing, to the detriment of my overarching holistic goal - efficiency.
Originally I started undervolting and experimenting with frequencies because of thermal output. I had wanted to experiment with x16 MSAA settings, which led to my GPU needing 400MHz and 1200mV which led to lots of heating up which led to me experimenting with everything I could.
Efficiency is what I want. The best performance at the best speeds at the best battery life at the best thermal regulation I can manage.
Now I'm looking at energy efficiency. I'm seeing suggestions that 100MHz may not be as efficient as 200MHz on our Exynos because the tradeoff in frequency power usage isn't worth the longer time spent completing tasks. I'm also seeing that in some situations, a performance best governor targeting max freq may be efficient because less time is spent completing a task and a quicker return to sleep.
I'm just sharing what I'm doing and hopefully others can benefit.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my GT-N7000 using xda premium
Wow, thats illogical makes me wonder the math behind it.
Sent from my GT-N7000 using Tapatalk 2
While I appreciate the effort thrown into this, I humbly acknowledge the conclusion is incorrect.
When you lower Voltage slightly, without affecting stability, you pretty much put a toll on the processor for extra "wear and tear" and reduce its lifespan. However, this comes at the reward of reduced current.
So, it should be saving you battery. Underclocking it (safely) is also going to save you battery. And the same thing with different governors, like interactivX compared to regular ondemand, by finishing off processes quicker and reducing the frequency and voltage quicker, and going into Deep Sleep quicker.
I don't have the means to run a Scientific Experiment to prove these claims, nor the time to conduct them. But the majority of "hackers" synonymously agree it saves a noticeable power. These include themers, kernel developers and the casual user. I don't think an educated MAJORITY can be incorrect to the scale of this test's claims.

Categories

Resources