This kernel uses AOSP camera driver so it's most likely compatible only with Redux 2.0 (tested) and Oxygen (not tested)
Before you do anything- make a backup
It's my lame attempt (I'm a modder, not a dev) to get more battery life without loosing stability of original kernel.
Kernel is based on current thalamus 2.6.35.14 sources
What is changed (mod8):
-Vdd levels sysfs interface is back, this time seems to be stable
-default voltages for CPU clocks <700 MHz are lowered a bit- keep this in mind when playing with UV
-headphone volume boosted a little- needs to be tested
-more optimized compilation- kernel should use CPU in more efficient way (and kernel is 500 bytes smaller )
-big thanks to paul8944 for testing
What is changed (mod7):
-removed sysfs Vdd levels interface- it seems that it was responsible for instability and FC's in mod6
-USB transfer speed is higher (was ~800kB/s, now ~2MB/s for write operations)
What is changed (mod6):
-added sysfs Vdd levels interface- VDD_MIN is set to 800 mV, VDD_MAX to 1300 mV, step is 25 mV (this works fine with IncrediControl)
-available governors: ondemand, powersave, conservative, performance and smartassV2
-conservative governor is tweaked a little (should be a little less conservative)
-USB transfer speed tweak- needs testing
-other fixes
What is changed (mod5)
-lowered minimum cpu clock to 128 MHz
-more clock speeds are available up to 1113 MHz
-added smartass and smartassV2 governors
-tinyRCU replaced with preemtive tinyRCU
-enabled call recording (not tested)
-many other fixes and improvements mainly form ch33kybutt's and elevendroids' sources
Note about smartass governor- after longer period of inactivity you have to press Power button for about 2 seconds to wake up the phone
Installation:
-make a nandroid backup (just in case)
-put zip on SD card and flash in recovery, I suggest also wiping dalvik-cache (just in case)
Download:
thalamus 2.6.35.14 mod8
md5: E526C99D4326F5B11D02DB60FEFA169F
Previous versions:
thalamus 2.6.35.14 mod7 (description above), md5: 7AB623BCC5E28D9BC8A012EDD9E9BBC7
Mod6 is not available due to instability
thalamus 2.6.35.14 mod5 (description above), md5: 7DC3E94E56FD00C49FEB5C713033DE33
thalamus 2.6.35.14 mod4 (128 MHz min cpu clock, default governors set, non-preemptive TinyRCU) md5: E7DD4637D8838A6E1A64E763C8A4D549
Kernel sources available on Github
I'll give it a try, seems good. I have one question and one suggestion:
the question is: what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
and the suggestion is to add the syscf interface for being able to change the voltages. It could save some battery life if our Desire stands it (mine does even at 800 mV )
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
blackhawk_LA said:
what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
Click to expand...
Click to collapse
I was not satisfied with default cpu clock table
-128 MHz uses ~20 mA of current less than 245- it's about 10% saving for iddle not locked phone
-for me 691 MHz max clock is really enough for my needs, it was not available in stock version
-more speeds make governors able to better match cpu speed (and save some juice)
-there are some performance fans so why not enable also 1113?
soronk said:
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
Click to expand...
Click to collapse
Looking what caused this, I'm not sure if it's wlan driver or preemtive tinyRCU (not present in mod4)
Download temporarily removed
EDIT:
It was wlan driver.
Corrected, reuploaded package
gen_scheisskopf said:
EDIT:
It was wlan driver.
Corrected, reuploaded package
Click to expand...
Click to collapse
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
soronk said:
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Me too.....
Sent from my HTC Desire using XDA App
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Tones1971 said:
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Click to expand...
Click to collapse
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
gen_scheisskopf said:
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
Click to expand...
Click to collapse
Yes it work! But without camera. MIUI needs the 720p camera drivers.
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
h_misc said:
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
Click to expand...
Click to collapse
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Click to expand...
Click to collapse
Too bad, with screen off laggy behaviour when raising the CPU-clock is exactly what I want.
With the conservative governor reaction to the power button is instant, smartass was really irritating me when pushing the power button the days I tried it.
I used setcpu with a screen off profile with conservative and ondemand with screen on (on gingervillain) which was just perfect.
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
blackhawk_LA said:
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
Click to expand...
Click to collapse
I use the FTP server with screen off, a script that functions as webserver to name two examples. So I need it to be possible for the CPU to be at more than minimal speed.
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
blackhawk_LA said:
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
Click to expand...
Click to collapse
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
So which governors do you think should be in kernel? I don't want to include all available
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
So which governors do you think should be in kernel? I don't want to include all available
Click to expand...
Click to collapse
The ones I like to use are ondemand and conservative.
You should include what you like off course
h_misc said:
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
Click to expand...
Click to collapse
I couldn't agree more
I think that the most used governors are conservative, ondemand, interactive and smartass (don't know about the new governos: smartass2 and others)
But for me, having ondemand it's enough
blackhawk_LA said:
But for me, having ondemand it's enough
Click to expand...
Click to collapse
Do you want a dedicated build?
So as for now governors will be ondemand, performance, conservative, powersave (even more conservative than conservative ) and smartass- more likely v2.
I plan to release mod6 when I'll implement SVS
Related
First things first...
MAKE A NANDROID BACKUP.
I take NO responsibility for ANYTHING that goes wrong with your phone, life, job, home, car, sex life, dog, cat, turtle, pet rock, etc. as a direct or indirect result of your use of this kernel.
Features of kernel for Sense ROMs:
Based on HTC source code - this should work on any stock-ish ROM
Features of kernel for CM7 ROMs:
Based on Toast's fork of the Cyanogenmod kernel
Common features:
BFQ I/O scheduler
Smartass governor
Undervolted (battery savings)
Overclocked - up to 1.8GHz (WHY?!? lol)
Underclocked - down to 184Mhz (battery savings)
By default, the kernel will clock up to 1.2GHz with the smartass governor. I personally just flash the kernel and run it as-is. If you want something different, use an overclock utility like "No-frills CPU Control". Be aware that some of these utilities run background processes and SUCK battery life.
Troubleshooting:
ON CM7.0.2
You will need to flash the kernel *AFTER* booting up the ROM for the first time. If you do a clean install of CM7.0.2 + the x99kernel, turning on wifi may make your phone go into a "boot loop" (restarting the shell, over and over).
If you're stuck in a boot loop, go into recovery (yank battery then vol down + power OR "adb reboot recovery"), flash the 7.0.2 file again, let it boot, make sure Wifi works, then go back into recovery and flash the x99kernel.
If anyone has further input on this, I'm all ears.
My phone is locking up!
Try a slower clock speed and/or a different governor. I have run this kernel reliably at 1.55GHz for a long time, but different phones can have different results. I have personally experienced lock-ups at high speeds with the interactive governor. Again, I have been running this kernel "as-is" without making any clock/governor changes... IMO, 1.2GHz is plenty fast for day-to-day use.
My phone is running hot and/or the battery is draining quickly!
Most likely, you're running the CPU at a HIGH speed and/or there are some over-active processes.
I suggest downloading OSMonitor from the market to see what processes are active. In the options, you can choose to sort the process list by CPU Load and also check the "Order" box to have the active processes shown at the top of the list. The "Misc" tab will show the current clock speed and phone temperature... you can also use it to change the speed or governor if you'd like.
"adb logcat" can reveal a LOT about what your phone is doing in the background.
Credit:
bcnice20 - I followed a lot of what he was doing with his own kernel, but removed bits that didn't seem to work right for me.
toast - CM7 kernel is forked from his github
cloverdale - Proper root in Sense kernel
Old, out-of-date changelog:
20110414
Step up to 2.6.32.36 from 2.6.32.33 in CM7 kernel
20110411
camera fix for bcnice20's Desire ROM in Sense kernel
20110408
Proper root in sense kernel
20110404
Added BFQ I/O scheduler
Misc compiler tweaks
Added version for CM7
20110323
Lowered voltage on 184MHz and 245MHz speeds
20110322
Re-tweaked the smartass governor (see current strategy below)
Slightly increased voltages for CPU speeds between 768MHz and 1.55GHz (may help some people with lock-ups)
Added an additional low speed... 184Mhz (power savings?)
20110321
Tweaked the smartass governor
Added the interactive governor
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Added conservative governor (untested, but should be OK).
Current smartass strategy:
Max sleep speed is 245MHz
CPU load under 35% = step down. Can step down as much as is determined to be OK at once.
CPU load over 70% = step up. Will make steps upward of as much as 384MHz at a time.
If CPU is at 100%, jump up to at least 1.1GHz.
Current versions:
Download x99kernel-GBSense-20111030 #1 FOR GINGERBREAD SENSE ROMs, NOT FROYO. No smartass governor yet. Uses improved flashing script.
md5sum: 1973b881d09796f16c2ab7a485c1b6df
Download x99kernel-cm7-20111003 #5(?) This is a 2.6.35 kernel! Slightly incomplete... no underclocking yet. Improved flashing script to avoid missing module files (fix WiFi errors). Max smartass sleep speed is 368Mhz.`
md5sum: a215897e48f26a1d03510f5e632f59bb
Download x99kernel-cm7-20110530 Still #2 This is a 2.6.32 kernel! For CM 7.0.3.1, CM7 nightly #87, or earlier.
md5sum: 9569a39d5746756b9f6a3a5bfcc63a9b
Download x99kernel-sense-20110411 #8 FOR FROYO SENSE ROMs, NOT GINGERBREAD.
md5sum: 2e94b170f3976cdc44dcecbfb21f9157
Old versions:
Download x99kernel-cm7-20110615 #4 This is a 2.6.35 kernel! Slightly incomplete... no underclocking yet.
md5sum: 1318f22887322cefca3ebafd44043bb6
Download x99kernel-cm7-20110611 #3 This is a 2.6.35 kernel! Slightly incomplete... no undervolting or underclocking yet.
md5sum: 3d36a18e7590dd29689d216028452137
Download x99kernel-cm7-20110414 #2
Download x99kernel-sense-20110408 Still #7
Download x99kernel-cm7-20110404 #1
Download x99kernel-sense-20110404 #7
Download x99kernel-20110323 for Sense #6
Download x99kernel-20110322 for Sense #5
Download x99kernel-20110321 for Sense #4
Download x99kernel-20110318 for Sense
Download x99kernel-20110317 for Sense
GPL Source
So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Sent from my PG06100 using XDA App
Nice job on the kernel. Been running it for bout two hours clocked to 1.8ghz on performance in setcpu. Temp hasn't reached over 80. Hitting steadu 2400 in quadrant.
Sent from my fast as **** Evo Shift 4G using Tapatalk
so which one would u guys recommend? this or bcnices1.8 kernel? what are the differences
x99percent said:
MAKE A NANDROID BACKUP FIRST.
I take NO responsibility for ANYTHING that goes wrong with your phone, life, job, home, car, sex life, dog, cat, turtle, pet rock, etc. as a direct or indirect result of your use of this kernel.
Click to expand...
Click to collapse
My sex life instantly was overclocked!
Sent from HTC Knight using Mikrom..because CM7 got overrated like CWM
Lol
Sent from my Htc Evo Shift 4G
K running this now and hitting 53 linpack score 1.8 perf..pretty nice so far
Sent from HTC Knight using MikShift..because CM7 got overrated like CWM
DWake014 said:
So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Click to expand...
Click to collapse
There *shouldn't* be any issues with 4G or GPS, since this is based on the original HTC source code. I have used it successfully over NFX's ROMs before... I think I'm running one of his now.
I have edited the orignal post to be a little more clear.
Just a heads up - the smartass governor doesn't scale below 768 mhz. I believe bcnice mentioned he had the same issue on his kernel.
Sent from my PG06100 using XDA App
so this kernel seems to have solved my issue with loading pages in the browser locking up the phone. Nice.
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
EVO Shift and XDA app
abanh said:
Just a heads up - the smartass governor doesn't scale below 768 mhz. I believe bcnice mentioned he had the same issue on his kernel.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
With the smartass governor, it won't scale below 768 when the screen is on... that's for sure. (<-- NO LONGER TRUE)
If you use SetCPU, the "Info" tab will show you that the phone is happily running at 245MHz when the phone is off... and I'm not forcing it to 245MHz, either.
I actually posted in bcnice's thread about this issue, along with a solution for it. However, I do think that adding an extra step between 368Mhz and 768Mhz will help things.
EDIT: Added a couple of lower speeds, and things seem to be improved. Will post a new zip file during the day.
adamr240 said:
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
Click to expand...
Click to collapse
I don't think that's handled within the kernel... from everything I've seen, that's a patch to a file in /system/framework/
adamr240 said:
so this kernel seems to have solved my issue with loading pages in the browser locking up the phone. Nice.
Is there anyway you can add the wired tether patch so I can just use that? I'm not to keen on switching roms and having to start over.
EVO Shift and XDA app
Click to expand...
Click to collapse
If you're talking about wired tether for root users needing ip filtering, that's on in all kernels for the shift, even stock. However, some bug or difference in framework doesn't let or phones tether on that or wireless tether on 3g, only on 4g
Sent from my PG06100 using XDA App
DWake014 said:
So 4g, gps, and all those other bugs are worked out on this kernel? And can i apply this over nfx stock rom?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I'm running this over the nfx stock Rom, running smooth so far
I was running bcnice's kernel, but could only hit 1.1 max using on demand and the phone wold still hit 105 degress at times. Just installed Mik's rom and at this point am not using any kernel. Should this kernel work with this rom?
Aaargh! said:
I was running bcnice's kernel, but could only hit 1.1 max using on demand and the phone wold still hit 105 degress at times. Just installed Mik's rom and at this point am not using any kernel. Should this kernel work with this rom?
Click to expand...
Click to collapse
I use it so yes
Sent from HTC Knight using MikShift..because CM7 got overrated like CWM
Changelog:
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Added conservative governor (untested, but should be OK).
x99percent said:
Changelog:
20110318
Added two additional clock speeds between 768MHz and 368MHz. By default, the smartass governor can't make the "jump" down from 768MHz to 368MHz, because the step is too large.
Click to expand...
Click to collapse
Nice update. Do you think you could also add the Conservative governor?
abanh said:
Nice update. Do you think you could also add the Conservative governor?
Click to expand...
Click to collapse
Done. Re-download the same link.
My frequency keeping ramping from 245 to 1.8 when idle, bouncing up and down on both ondemand and smartass. Flashed back to bcnice20's bfs bfq for now.. but I'd like to make this work as I love running the smartass gov. Any ideas?
Read the thread before posting bugs or issues or questions
Table of contents:
Intro
Features/what this includes
Quirks of the kernel
Why it's labeled unstable
Disclaimer
Latest kernels
Methods of flashing
Benchmarks!
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Old links, go here for other aosp roms with older video drivers & older builds
Intro: I'm scaryghoul
What this includes
It's scary!
Swap
Deadline I/o scheduler
Extreme undervolt
Overclocked & underclocked values
Sleepers disabled
Toast's new video drivers
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of toast's kernel)
Quirks of this kernel:
Sometimes when changing speeds with something like setcpu, they take a few seconds to actually clock to that speed, turning the screen on and off fixes it and clocks it right away though.
I would advise against using the speeds 66mhz->180mhz during real usage. It's a little laggy, but works =)
This doesn't work with sense based roms like mikshift, yes it needs to be said more than once
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles - I'll keep my current speeds in my signature.
Mirrors of kernels uploaded by VICODAN
Super SUV
http://www.mediafire.com/?47perl0d43n1nyr
Super Stable kernel
http://www.mediafire.com/?9qmtzuu35cpr8yz
Super Girly kernel
http://www.mediafire.com/?1s4z4y7bh78e04j
Methods of flashing
Joeykrim's "flashimage gui" app on the market using one of the zImage files from the zips. http://forum.xda-developers.com/showthread.php?t=1045797
Teamwin's "Kernel manager" app on the market. http://forum.xda-developers.com/showthread.php?t=1030500
Flashing via recovery using one of the zips here.
Benchmarks! - All done at 1.8ghz on cm7
Quadrant standard 1.1.7 - 3900 is the highest I've seen so far I believe.
Smartbench(2runs) - 2150/1850 - Mine were around there
Linpack(3runs) - 61, 63, 63 - These won't change much at all.
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Nofrills - App to manage I/O scheduler, clock speeds & governors.
Adw ex or go launcher ex
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel or girly kernel
Question: My phone's graphics are running really lagishly, why is this happening? It worked fine on version 1.4 and before.
Answer: You are likely running an outdated version of your rom not supporting the new video drivers in version 1.5+, you will need to roll back to v1.4 and before
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: My wifi/wifitether and other stuff is broken and wasn't before I flashed your kernel
Answer: READ THE BIG BOLD STATEMENT AT THE TOP OF THE THREAD THAT SAYS THIS IS NOT FOR SENSE
Question: How do I flash this?
Answer: You probably shouldn't be flashing a kernel labeled unstable if you don't know how
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
or if your rom supports it htop is much better(Without grep, so just "htop")
Then look for items with high amounts of cpu% while the phone is idle.
changelog:
Release1:
Swap support enabled
Unlocked 1.6-1.8ghz
Superundervolted
Release 2(1.1):
Unlocked 3 new underclock values
Took the undervolt farther.
Release 3(1.2):
Added hw3d
Release 4(1.3):
Removed interactive governor since it only causes trouble
Overall undervolt taken farther. May be unstable for some
Release5(1.4)
Disabled sleepers
Changed kernel name
Added an alternative voltage kernel
Release 6(1.5)
Cleaned up the source
Updated to toastcfh's new video drivers, greatly improved video performance and fixed a lot of issues with aosp video. - Thanks toast =D
Release 7(1.6)
Still cleaning up source
Addeed smartass governor && tweaked it, Down thresh: 70, up: 90
Added a real kernel name
Added lulz
Added two new clock speeds && modified voltage table
Tweaked conservative governor(Should be less erradict now, so scaling less==less power consumption==Yay =D)
Release 8(1.7)
Added Scarygov 0.5
Removed userspace governor
Release 9(1.7.2)
Tweaked scarygov to 0.6, removing a bug
Release 10(1.7.3)
Fixed a lag issue on scary governor by slightly optimizing the code.
Tweaked smartass.
Release 11(1.8)
Optimized scary governor's code
Safe voltage kernels && Stable kernels(come here if you can't handle the super undervolt
NEW VIDEO DRIVERS
1.8
ScaryKernel 1.8 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.8safe.zip
Girly Kernel 1.8 stable http://dl.dropbox.com/u/15373824/GirlyKernel1.8safe.zip
1.7.3
ScaryKernel v1.7.3 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.7.3Stable.zip
v1.7.2
ScaryKernel v1.7.2 safe uv http://dl.dropbox.com/u/15373824/Scarykernel1.7v2Safe.zip
v1.6
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/ScaryKernel1.6SafeJesusNoSleep.zip
v1.5
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableJesus.zip
[UNTESTED]1.5Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableNoJesus.zip
OLD VIDEO DRIVERS(1.4) - For roms that don't support the new video drivers.
1.5Ghz safe voltage kernel no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5NoSleepers.zip
1.5ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5Sleepers.zip
1.8ghz safe voltage kernel, no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8NoSleepers.zip
1.8ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8Sleepers.zip
Notes:
Nothing for now.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: Toastcfh/bcnice20 - For 99.8% of their kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
Just curious but what rom?
Sent from my PG06100 using XDA App
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
CrashV2010 said:
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Click to expand...
Click to collapse
Glad you can handle it.
smoothtaste said:
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Click to expand...
Click to collapse
Thanks =O
jjb61 said:
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
Click to expand...
Click to collapse
Thanks for sharing here =)
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
What rom and which kernel....
threeFiftyLi said:
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
Click to expand...
Click to collapse
Interesting. Never had that issue, what range of speeds are you using?
JKILO said:
Just curious but what rom?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Scaryghoul said:
What rom and which kernel
Click to expand...
Click to collapse
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Scaryghoul said:
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Click to expand...
Click to collapse
Well I guess that would explain why I was having issues..
crump84 said:
Well I guess that would explain why I was having issues..
Click to expand...
Click to collapse
Version 1.5+ is meant for cm7's nightlies from 31+.
When I first tried it, I felt a little lag but after I wiped it ran better than before.
Scaryghoul said:
Interesting. Never had that issue, what range of speeds are you using?
Click to expand...
Click to collapse
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
threeFiftyLi said:
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Click to expand...
Click to collapse
Okay.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
I thought that was the problem
Sent from my PG06100 using XDA App
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Scaryghoul said:
Okay.
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
Click to expand...
Click to collapse
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
DWake014 said:
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Click to expand...
Click to collapse
Thanks for sharing =D
smoothtaste said:
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
Click to expand...
Click to collapse
Thanks =)
---------------------------------------------------
1.6 is out for the unstable voltage.
I'll compile the stable ones later, already made the commits to the github for what I can remember I changed
Check the changelog people =D
I know this is probably a noob question and has been asked before (i've tried searching but to no avail). How does Smartass V2 go about setting cpu speeds? What is it comparable to?
Thanks in advance.
-Vin
Sent from my HTC Sensation Z710e using xda premium
Vineares said:
I know this is probably a noob question and has been asked before (i've tried searching but to no avail). How does Smartass V2 go about setting cpu speeds? What is it comparable to?
Thanks in advance.
-Vin
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 600/245 kernel, it will sleep at 245. No need for sleep profiles any more!
Thats the definition of SmarAss Gov, some kernels support smartass other dont, where smarass is not supported your choice is ONDemand its kind of the same with less tweaks
Hi, sorry for an even noobier question, but I just started with all this rooting and custom ROM stuff. How do I go about setting the kernel to use the SmartAss V2 algorithm?
I just flashed this kernel [Kernel]CM7/AOSP[2.6.35.14](v0.1.2)OC~1.78GHz/BFQ/SLQB[Sep-11]. The dev states I cant use setcpu, but then goes on to mention the use of SmartAss V2 among others. I tried to access the Performance tab in cyanogensettings->performance->cpu settings, but it FC. Tried looking around the forums, but can't find anything. Tried posting in that thread, but apparently i'm too much of a noob.
Edit: Kinda went digging through the root explorer, does /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = ondemand mean that its using SmartAss?
As some of the other threads are getting a little bit chaotic, I'm opening this thread 'bout kernels. I'm trying to list all available kernels for the I9001 here in this first post. You may discuss kernel related problems here.
Right now the kernels are included in a bigger package. That's why there are the links to those packages and not to a "single" kernel file.
Available kernels:
FeaCore_Phoenix_OC: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore_Phoenix_nonOC: http://mediafire.com/?5unogie5i58x85r
Cranium Kernel_OC:http://www.multiupload.com/5QC10CJZK6
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Nice..
Sent from my GT-I9001 using Tapatalk
pyronia said:
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Click to expand...
Click to collapse
It's less fluid for me ... Back to 1.3.1.
pyronia said:
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Click to expand...
Click to collapse
I use 1.3.1 non OC.
Its stable and has a good battery use
Sent from my GT-I9001 using XDA App
manveru0,i got confused when i saw ur commit 'revert,re revert blah blah'
what's the current status of jhash3 in phoenix kernel?
sakindia123 said:
manveru0,i got confused when i saw ur commit 'revert,re revert blah blah'
what's the current status of jhash3 in phoenix kernel?
Click to expand...
Click to collapse
Current status is that jhash3 is reverted back to standard jhash in the OC version. Yesterday I had a loss of about 10% battery power over a time period of ~ 8 hours, which is too high. oudbrood has the same issue. Right now I'm testing the latest build. If it turns out that the battery drain is lower, I'm definitely gonna send jhash3 into nirvana
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
vitaliy_y said:
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
Click to expand...
Click to collapse
hey can u post ur kernal. would like to try it out. thanks
Could you upload a non-OC Fly High kernel? Or is Fly high still a test-kernel?
Sent from my GT-I9001 using Tapatalk
vitaliy_y said:
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
Click to expand...
Click to collapse
with or without jhash3? I guess without it, right?
the high default ramp up step value was because i once had stability issues with lower values. But that may have been something else. Anyway, did lower it for a test. Okay, I've now also SIO as I/O scheduler included. Need to test that as well. Thx for your input
Yes, without jhash3
I have included support shed debuggin in kernel, and now testing a little commands sach as echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
I maked temporarily dssconfigure JFS anf CIFS.
Now testing kernel
vitaliy_y said:
Yes, without jhash3
I have included support shed debuggin in kernel, and now testing a little commands sach as echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
I maked temporarily dssconfigure JFS anf CIFS.
Now testing kernel
Click to expand...
Click to collapse
hey man,cud u try adding xz boot compression ,cleancache?i cudnt do it.....compilation errors
EDIT:manver0 added cleancache!
I check the battery expense after that I will search for initial codes for BLN
vitaliy_y said:
I check the battery expense after that I will search for initial codes for BLN
Click to expand...
Click to collapse
there are plenty of codes for bln around. That ain't the problem. But, you need to change the liblights library which means, you need to recompile it and push it onto your phone. Now I don't know what happens if I push the new library with an update package, everyone gets it and after that somebody reverts to an older version without bln. You know what I mean?
https://github.com/neldar/kernel-2.6.35-nexusS-bln
Edit: By the way I've lowered the DEFAULT_RAMP_UP_STEP down to 249600 which leads to shutting off the device every time it goes into sleep mode. Exactly this was the reason why I have 345600 in it. I'm gonna revert the sources again...
Edit2: I had a reply on the german board android hilfe about jhash3. I'm definitely not gonna reimplement it as the battery drain is definitely higher:
He checked the battery drain with and without 3g data connection
2 hours Wlan off (and 3g on) = 11% battery drain
4 hours Wlan on (thus 3g off) =2% battery drain
I used DEFAULT_RAMP_UP_STEP adn down step 128000, and device worked normal,
Ideal sleep speed was 246000 instead of 128000
vitaliy_y said:
I used DEFAULT_RAMP_UP_STEP adn down step 128000, and device worked normal,
Ideal sleep speed was 246000 instead of 128000
Click to expand...
Click to collapse
ok, gonna check it out.
Why would you choose a higher frequency on the ideal sleep speed?
Edit: echoed your values to the ramp up and down node and it immediately killed my device when going into sleep state (aka hit power button)
i used instead a generic concept.............min and max
Hello, I flashed ARHD 6.5.5 with faux kernel.
I want to know how to set this kernel with System Tuner or Faux Clock.
My smartphone is Sensation XE. Thanks
Actually is set:
max clock 1,512 ghz
min clock 192 mhz
governer on demand
global voltage 0mV
GPU IO Fraction 33
I don't understand your question. What do you want to set, the CPU frequency or the voltage?
Faux in its kernel thread write : "For frequency control and voltage adjustments use SystemTuner by 3C or FauxClock app by Romanbb". What it mean?What can i do with this apps?Can i get better performance setting this values?
Thanks
Hi,
With this app you can test different frequency from 1.52 to 1.8 Ghz.
You can see witch one is better for your usage and batterie life ...
Sent from my HTC Sensation using XDA
amsterdam88 said:
Faux in its kernel thread write : "For frequency control and voltage adjustments use SystemTuner by 3C or FauxClock app by Romanbb". What it mean?What can i do with this apps?Can i get better performance setting this values?
Thanks
Click to expand...
Click to collapse
It means you can overclock/underclock and undrevolt.
Overclocking can lead to better performance, unvolting may increase battery life a little.
Ok, but in your opinion which is the best combination?
What happens if i set the governer performance?i don't see any difference!
amsterdam88 said:
Ok, but in your opinion which is the best combination?
What happens if i set the governer performance?i don't see any difference!
Click to expand...
Click to collapse
I'm still experimenting really, I leave it at 1.5GHz but I've undervolted by about 50 but haven't really noticed that much difference in battery life.
For governor I just stick to On Demand. Here's an explanation of governors: http://forum.xda-developers.com/showthread.php?t=1369817
maybe is better if i keep the stock kernel
now i reflash with stock.
IMO to have a custom kernel with default setting have no sense!