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
Related
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
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.
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Gooner88 said:
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Click to expand...
Click to collapse
hi you have to flash a kernel (you ll find all the information needed in the ic sunday topic)
i did do that and its far better
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
I'm having wake-up lag too! But I already gave up thinking that the SGA's CPU just sucks. Thanks for this info GerasVille, I did not think to tinker with the System settings of CyanoGen because of the "Dragons Ahead" prompt. I will try this smartass setting to see if the wake-up lag will be removed. It sucks when I have to send an emergency SMS and my phone is lagging like hell.
Anyway so let me get this straight. Does having the minimum CPU clocked at 122mhz mean that if the device is inactive, it dynamically clocks down the CPU to 122mhz to save battery? Hence the wake-up lag is caused by the CPU being clocked back up?
I'm also gonna try out slaidfastmod to see if it makes it even better.
You can put up with the lag and save a tiny bit of battery life, or speed up the CPU and lose some battery life. Whichever you feel is more useful. Personally I don't mind the small unlock delay. Happens on most phones low powered anyway.
Sent from a phone with an app.
Eniac77 said:
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Click to expand...
Click to collapse
The kernel that is currently installed is "2.6.35.7-perf-CL562111" Ketut-lenovo #4. I am not sure if it is an OC kernel.
GerasVille said:
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
Click to expand...
Click to collapse
I installed SlaidFastMod v2, set governor to Smartass and min CPU frequency to 245 MHz and this fixed the issue! It's much smoother when unlocking.
Is it safe to tick the "Set on boot" setting for CPU settings?
I found a solution to fix the Doom kernel reboots for those who are unable to download stock roms from HTC (Rogers Customers). Requires CWM Recovery.
1. Download stock kernel here - http://www.box.com/s/7dc3bf2adc9e2f05b717
2. Unzip archive
3. Move Zip file to SD card
4. Reboot into bootloader fastboot reboot-bootloader
5. Flash the img file fastboot flash boot name.img
6. Go into CWM and install the zip.
This solved my problem, hopefully it works for you guys too.
This should work on ALL devices not just Rogers
it doesn't actually solve the kernel issues...
your just replacing him.
i still think his kernel has a lot more potential than the stock.
It fixed my issue.
I care more about having a functional tablet than a kernel that may have more potential but is buggy as hell.
i agree. and i'm running the stock as well.. just wished the doomlord one would work as well.
Hi there,
Noob user here.
I got HTC JetStream from previous owner with doomlord Kernel on it.
Tablet is constantly crashing for no logical reason which leads me to believe that the kernel is causing this issue.
I would like to flash back to the stock kernel only as my device (Rogers) is running a stock image.
I am having difficulties to follow your instructions.
Wold somebody be so kind to post more detailed process steps to complete this kernel flashing back to stock.
Thank you very much.
I had the same random reboots using Doom's kernel until i overclocked it to the maximum. It's been almost 2 weeks since i experienced any reboots....
Sent from my Inspire 4G using xda premium
could you be more specific?
did you set both the minimum and the maximum to the maximum?
did u change the voltage?
Yes I changed the min & max all the way to max.. not sure if it will have some long term effects on my tablet, but it's been working great for a while now.
Sent from my HTC PG09410 using xda premium
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
craig0r said:
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
Click to expand...
Click to collapse
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
ATT Intruder said:
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
Click to expand...
Click to collapse
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
craig0r said:
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
Click to expand...
Click to collapse
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
globalgpj said:
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
Click to expand...
Click to collapse
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
AlexFG said:
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
Click to expand...
Click to collapse
Thanks for that.
So far, I haven't had anymore reboots.
Increasing the minimum seems helpful.
I get plenty of battery life, so I am really happy about this for now.
Just a quick update.
I've been running 1.944 GHz as my high setting and 756 GHz as my low setting for some time now and I have to say, no reboots, no lag, super fast and stable.
Sent from my HTC Jetsream using xda premium
Nice, I'll try those frequencies on mine. Thanks for sharing.
Sent from my Galaxy Nexus using xda app-developers app