So I have tried several Kernels over the last 6 months or so. I did not always have SetCPU on my Vibrant so never noticed what the Minimum clock speed was on most Kernels. I recently test drove the new DOW kernel and installed SetCPU to mess around with OC. I went back to what was my daily driver kernel KA7 W/Voodoo. Then I noticed KA7's minimum clock speed was set at 100 MHz?
I have read that some phones have a hard time waking up at 100 MHz. KA7 has been the best performing kernel I have used to date. Battery life has been amazing and never had a wake issue. Is this just a similar situation with OC kernels some processors can run at a lower clock speed then others and also is it normal for the stock kernels to have a minimum clock speed of 100MHz?
Thanks in advance for any info on this subject...
Yes it is normal.
OC Kernels work differently. Some will allow 100Mhz. Others have problems with 100Mhz and can only go down to 200Mhz. It's about the same thing as far as you and your phone are concerned. You won't notice it and neither will your battery.
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.
On CM7 I dont have ondemand governor with the tiamat or savage. Only with stock CM7 kernel. What should I use instead?
Also does it take a while to notice improve me with these kernels?
Also those with awesome battery life on stock battery are you leaving wifi on? I get about half those times but I leave 3g on all the time.
I wish I could get through an 8 hour work day with 5hrs of screen on time on my battery.
Usually on my yoobao 3000mah I get 4.5hrs on screen time with no charging throughout the day lasts about 17hrs that way.
If I switch back to my stock battery I wouldnt be getting that would I?
CM7.1 nightly
yoobao 3000mah battery
tiamat 407 kernel. Everything under volted by 50mV but I do not think it is sticking.
churro7 said:
On CM7 I dont have ondemand governor with the tiamat or savage. Only with stock CM7 kernel. What should I use instead?
Also does it take a while to notice improve me with these kernels?
Also those with awesome battery life on stock battery are you leaving wifi on? I get about half those times but I leave 3g on all the time.
I wish I could get through an 8 hour work day with 5hrs of screen on time on my battery.
Usually on my yoobao 3000mah I get 4.5hrs on screen time with no charging throughout the day lasts about 17hrs that way.
If I switch back to my stock battery I wouldnt be getting that would I?
CM7.1 nightly
yoobao 3000mah battery
tiamat 407 kernel. Everything under volted by 50mV but I do not think it is sticking.
Click to expand...
Click to collapse
i prefer the SavagedZen 2.2.1 kernel with savagedzen. but would suggest trying the smartass and interactiveX governors to see which one you and your phone prefer. some folks like the 3.06 version of Tiamat, you may want to ask folks in the tiamat thread about the diff between 4.07 and 3.06 (not positive on the version numbers).
i'd suggest running each for a couple days to see how it feels.
i use Tasker to activate my wifi when i arrive at work and at home...the rest of the time my wifi is off unless i turn it on.
the "5hrs of screen on time" may be an issue, the screen draws a lot of juice. perhaps if you verify your undervolting is sticking, used no widgets, do not use live wallpapers, set everything to sync once or twice a day you'd get further...but thats kinda no fun and i still don't think you'd get 5hrs.
i've had a light day on my phone...1.5hrs of screen on and i'm at 16hrs w/ 44% left. standard battery.
How can I verify the UV settings?
smartass is laggy
You guys should d/l System tuner. You can change your Governor with that app
Some guys swear by the SavagedZen kernel but it's reached the end of it's development life, the SavagedZen team is no longer supporting or updating the kernel and it hasn't been updated in almost 3 months. My personal experience with the kernel notwithstanding, I think that's reason enough to stick with Tiamat.
Turn brightness to 30 or 40%. Get a mugen 4500 mAh. Problem solved...your welcome.
Oh and there is ondemand in sz221. I am currently using tiamat 407 SBC conservative governor and my settings. No undervolt and working very nicely
I own a stock, gailio 2000mah, and siedio 3500. My 3500 never has a problem making a heavy day of use. I'm guessing that 4500 def wouldnt
churro7 said:
How can I verify the UV settings?
smartass is laggy
Click to expand...
Click to collapse
you can use vipermod to set and verify your uv settings. there are other apps as well. but i find the script works well.
in CM7 you can set your governor and clock speed via:
menu -> settings -> Cyanogen Settings -> Performance -> CPU Settings
no 3rd party app is required. (unless you wish to use "profiles" like those available with SetCPU)
you may find interactiveX to be more responsive.
yes, SZ is not currently being developed and tiamat just released v407.
i may try the new tiamat kernel to see if it plays nice with my phone.
note: the new tiamat is based on 2.6.38.8 and SZ is based on 2.5.38.7.
thus far my EVO has shown a definite preference for SZ over Tiamat. /shrug
i always feel like i'm carrying around a pregnant EVO when i put on the 3500mh battery. LoL
My Evo also never ran tiamat well after 337 but 407 is running great
I avg five hours display on time. I have Deck's AOSP ROM and I turn off background data and sync twitter and email manually. I use Gemini App Manager to prevent apps from auto starting. I'm using a S-Z CFS kernel interactive x governor with SBC. I rely on 3g during my commute and wifi while at work and at home. I use the web, youtube and the xda app extensively. I don't think it is possible to have five hours screen on time using 3g only. Sprint's network is not that strong.
Sent from my PC36100 using XDA App
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.
I'm in a huge dilemma right now, I want to install the "Ultimate" version of Faux's kernel but when I'm using it, my N4 always reboots on start up. From this, it's obvious that that my N4 cannot handle the OC at 1.8ghz and every time I attempt to lower the CPU frequency in trickster mod, my N4 reboots before I get a chance. Anyone out there have a version of Faux's Ultimate kernel that doesn't come at 1.8ghz by default when you install it?
You could try waiting for your device to cool down then booting it up and changing the frequency. I'm undervolted -100 and I'm using intellidemand and I have no problems with 1.8. The battery life is still unbelievably good - 88% with 1h SOT right now (ran quadrant 5 times).
Sent from my Nexus 4 using Tapatalk