Related
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.
Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk
i installed the set cpu app from the market. i purchased it a long time ago when i was using the G1. i figured i would give it a try for ****s and giggles. it seems to work. i dont have all the governors i do with the kernel on my evo shift running cm7, but i do have a few to choose from: hotplug (?), on demand, userspace, performance. the min speed is 300 and the max is 1008. i dont have the skills to test this to see if it's actually working or if i'm fooling myself, but it seems to be.
i thought someone with know how might give it a shot to see.
I think you need a custom kernel...
As Lacokako stated, you need a custom kernel to set/change CPU speed.
that's what i thought, but i set the min and max to 1008, and it never came down from there. before it was showing the speed increasing with any interaction, but when set to max, it stayed steady at 1008. i have never been one to do the speed tests on roms/kernels so i dont know the method or process, but if someone does, i would be interested in the results.
Someone has overclocked nook tablet up to 1.2.
While i knew the official sony update slows the phone down i tried it anyway and i really regret doing that. The phone was really slow. So after quite some time spent rooting and flashing it with a custom kernel I overclocked it. The problem now is that SetCPU ignores what I set to minimum. Im using the smartAssv2 governor (it is the same with all the other governors) and when I'm not using any apps It quite oftenly sets the cpu to 200mhz slowing the phone to a crawl. So is there a way to fix this and make it so that it doesn't clock it at 200mhz at random ?
try no frills cpu controller or rom toolbox pro to overclock
Hi there to all!!! I've been flashing various Android Roms for a few yrs now & really enjoy trying out new custom roms etc... Now i have a weird problem, Most customs Roms I have tried for my S3 i9300 are great & most 4.3 Roms come with a Custom Kernel such as Beoffla, GoogyMax, devil kernel & so on.... Now the problem is when leaving the CPU at defualt governer & settings everything is fine eg: min 200 & max 1400 but games lag now & again, When setting the CPU min & Max settings to 1400MHz, the results are much better but not for long, The CPU always drops to 800MHz when gaming as i notice the lagg, I've noticed this same thing with just about every kernel & rom ive tried wether its set to 1400 or even overclocked to 1500 or 1600max, I've also tried every trick to make them settings stick , like trickster mod etc, none seem to work for long, its like another system service is interfering with the settings or so.....im pulling my hair out to figure out what this is, I just want the CPU min & max to stay firmly at 1400Mhz or 1500 etc....without changing at all!!!
Any help or suggestions would be really appreciated.... FlashJunkie83
Sent from my NeatRom'ed Galaxy S3
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
~ RazorMC
RazorMC said:
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
hey yea would make sense but when running rooted stock 4.1.2 with stock kernel, this doesnt happen at all, i can set performance governer in set cpu & it stays at 1400 Mhz throughout, also i would of thought a Cpu thats ment to run at 1400 would be fine to do so all the time as its ment to be able to... even with a little heat behind it... its still only doing what its ment to lol, i remember in the days of my s2, i could push the cpu to 1200mhz & it would happily stay there even tho it got hot lol, im really sure its a system thing that upsets the cpu frequency, other than that there must be a way to stop the cpu/gpu from under-performing with a little heat..... thanks for reply tho dude....
Sent from my NeatRom'ed S3 i-9300
Click to expand...
Click to collapse
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
RazorMC said:
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
Click to expand...
Click to collapse
thanks mate will give it a go
sent from my NeatRom'ed S3 i9300
finally fiqured it out, it seems that cynogenmod has a diffrent approach to thermal throttling as ive flashed CM10.2.0 Android 4.3.1 along with Boeffla 2.1 for CM & the issue seems to have gone completely, have been running a performance test on games for best part of the day at 1600MHz with 4 enabled cores & just going back to normal settings for normal daily use, & not 1 issue with throttling, so now im very happy with the smoothness in games although its gets warm, but most high performance CPU's do anyways,So ive come to the conclusion that thermal throttling must be handled more by sammy roms it seems, but got the result i wanted in the end, thanks for all replies tho guys
Sent from my blazing S3 i9300 now running CM10.2.0