Related
This is based on the cyanogenmod kernel, with the main change being the smartass governor has been added and is default.
The zip file is in koush's anykernel format, so it can be flashed just like a rom.
Changes:
Smartass governor by erasmux is default
extra overclock enabled
patch #22 by farmatito
disabled CONFIG_SERIAL_MSM
NO SUPPORT WILL BE GIVEN. ONLY FLASH IF YOU KNOW WHAT YOU ARE DOING. NO ONE IS RESPONSIBLE EXCEPT YOU. BLAH BLAH BLAH.
Newest
2.6.35.14-oc-cm-smartass_g0dd6e8c.zip
source: http://github.com/dumfuq
old versions: http://www.mediafire.com/dumfuq
What does the smartass governor do?
mackster248 said:
What does the smartass governor do?
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 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!
i googled it lol, seems like its a bit more responsive then interactive, and it ramps down quickly too. could give some battery savings
What ROM's will this work with?
keeps cpu at/above 768mhz, will not go below until you switch off smartass gov.
liking the "sleep" enhancement, but seems like it should let the processor scale on down to 245 when idle with screen on
I'm running this with CM7 Nightly #16 and it's running really well. I'm getting a little more battery consumption than I do with zinx's kernel, but that could just be because I've only been using the kernel for around 2-3 hours. It may need a little more time to settle? I'm not sure, but it is definitely snappier! If it does scale down the cpu during screen off, you can't tell at all! It doesn't have any lag when unlocking like setting profiles usually does. So I'm really stoked about this kernel! Great work as always Dumfuq! This will be my new kernel for at least a few days to give it more of a chance.
PS: I'm only getting around 29 on linpack at 1.017 GHz, where as with zinx's I was getting 38's. Smartbench scores are at 1320's for productivity and 1869 for gaming. So those both beat out zinx's kernel. Just wanted to put those out there so people have some kind of a comparison point.
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
dumfuq said:
posted a v2. The difference is frequencies are changed to match glacier frequencies instead of hero's.
The only noticable difference here is that when the screen is off the frequency scales between 245 and 368 instead of being stuck at 245.
Click to expand...
Click to collapse
Damn. Nice!
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
sl1k1 said:
Works with evil's MIUI 1.1.26 r2..Hopefully battery life will increase now.
Edit: breaks video playback in miui
Click to expand...
Click to collapse
Smartass is already compiled in.
Sent from my HTC Glacier
I use this on my GF's Mytouch Slide and she gets 20+ hr's on a charge overclocked @ 825. Was so hoping someone would port the kernal to this phone. thx dumfuq ^^
Trying to decide if I want to flash this over the stock cm7 kernel.
Has anyone noticed any gains from doing this? what about compared with the stock cm7 kernel + setCPU?
flashed this over build 16, cm7. I still use setcpu. no problems, everything is smooth like butter. Definitely smoother than it was before. no wake up problems, no play back problems. thanks for this =]
Does wifi calling also work with this? Anyone know?
brian6685 said:
Does wifi calling also work with this? Anyone know?
Click to expand...
Click to collapse
You could always flash it and find out, and if not, just restore the backup you made prior to flashing it. ;] I don't see why it wouldn't it hasn't broken anything for me.
K ill try it out later when I get home from work. Thanks
whats the mhz setting on this by default? not super fond of setcpu. though i do like this idea of a custom throttle and logic. so i figured if the mhz is high enough then i'll give it a shot.
brian6685 said:
K ill try it out later when I get home from work. Thanks
Click to expand...
Click to collapse
let us know what happens
here's my initial test of the v2 as far as battery goes...
looks like wifi calling works ;]
I've had great battery life with this kernel so far.
Are there any bad things that can pop out if phone is OCed to 768MHz? Does it last shorter, can it screw battery etc..?
Thanks
It's unlikely you will 'pop out' something at 768 MHz. Some Wildfire's will not be stable at that speed, and, that is about the worst it can get, in which case, your Wildfire will lag a lot,and you will have to tone down the frequency a bit.
Battery life may take a hit, but, it wont be anything drastic again, also, as for component life, again, it may take a hit, but, even at 768, it will last till the time you are ready to retire it.
what is the recommended overclock speed, i can overclock to 729mhz and its stable no reboots etc or should i overclock to 691mhz??
Not really necessary, if your phone is not behaving abnormally at 729.
Is the difference with overclocking really that noticeable compared to stock speeds?
It's marginal. Definitely not as much as the overclock %age suggests. The only big difference will be in benchmarks.
3xeno said:
It's marginal. Definitely not as much as the overclock %age suggests. The only big difference will be in benchmarks.
Click to expand...
Click to collapse
i just overclocked to 729MHZ its awesome, the speed is noticable , and its stable i hope its fine and doesn't take more battery life lol
got mine at 710mhz and its stable no problems at all
keep the max overclock value at 729 MHz and the minimum on at least 264 MHz.
This saves battery when phone isn't in use and the speed increase is noticeable, it's rather nippy! (certainly for texting anyway)
------------------------------------------------------------------
Device: HTC Wildfire, 16GB Kingston micro SD
ROM: CM7
Recovery: CWM
Status: Overclocked @ 726 MHz - stable
So guys, i definitely need a sense rom because of the look ( especially the music player, 3.0 lockscreen like in insertcoin and apps) and the fast writing speed of my sd card...
i tried leedroid, rc hd mix, maybe a froyo rom would be better? Or recoment a different kernel?
currently i use insertcoin ( newest stable release), but the battery is so bad i can hardly get a day out with normal use... wifi gps off brioghtness low...
can u tell me a good rom? would appreciate it
I find al GB ROMS have poor battery life then I changed the kernel to MANU's and it was much much better. Maybe try a different kernel?
can u recommend me a kernel?
Yeah this one is really good for me but is different experience for every user...
http://forum.xda-developers.com/showthread.php?t=883598
Gingerbread-HAVS-AXI-CFS
Thx dude, i'll try this.
But i gotta 2 questions:
Can i return to my standart kernel (insertcoin eg) and how can i do this?
Is this kernel also compatible with insertcoin? (sense- based)
With Gingerbread I think the Reflex S is pretty OK for the battery or else it is possible to undervolt further.
Maybe you just need to calibrate your battery, if you change your ROM a lot. I use BatteryCalibration from Market and it seem to do the job.
Do i have to do a full wipe?
Battery calibration does not work for me D the percentage drop fast to 99% percent again and so on
Yeah, I would do a full wipe. Especially if you are moving between different ROM's.
So far, the AuraxTsense 8.4 (Android 2.2) was my favorite in terms of battery usage - but since moving to 2.3.3 based ROM's, my battery drops faster when using the phone, but lasts longer when in standby.
what would u recomment then? returning to froyo or stay with gingerbread?
Well, if Battery Life is your primary concern, you would probably get the best results with a Froyo ROM, since the kernels are further in development.
However, in terms of features etc. I think the Gingerbread is better. I personally like the Sense 3.0 improvements etc. So I am just crossing my fingers that battery life will gradually improve further
My experience is, that Gingerbread ROMs in general are battery hungry. As for sense ROMs i can say that LeeDroid suits me best regarding battery life. At the moment im on oxygen and get a day out of it with normal use.
Best results with battery life i had with LeeDroid Froyo ROM (v2.4 i think). Smartass governor and screen off - 245mhz max/min sometimes got me 2 days without charging.
Maybe this helps you finding a solution.
By the way, you can also improve your battery life by turning off the various Auto Sync features, for example Sense Sync, Facebook, Weather etc...
So i've flashed reflex s now, hoping the battery will do better tahn insertcoin.
If not, i will probably change to leedroid froyo- are there any important disadvantages for froyo roms? like speed or something?
i've tried many sense roms and never got a good battery life
now using MIUI rom .. its GUI is close to sense and good battery life
24h and i still have 40% off battery on InsertCoin 1.0.8 CM7,wifi is always on,data is enable,set brightness to auto. Try charge your desire to 100% turn it off,connect charger again and wait till green led is up,than turn on your phone to fastboot menu (power and volume down) and clean battery stats,reeboot.Also You can use battery calibration app from market
Sent from my HTC Desire using Tapatalk
Hi
I use manu 2.0 cfs kernel and it is batterie efficient, most of time 48h before recharging.
Franck
Sent from my HTC Desire using XDA App
franckleroy said:
Hi
I use manu 2.0 cfs kernel and it is batterie efficient, most of time 48h before recharging.
Franck
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
thx c: which rom do ya use?
At first, the recommended manu kernel won't be working with sense roms, because it's an aosp kernel (so made for aosp roms).
Second, using setcpu and setting a screen off profile for it really improves standby battery power. I set it mine to:
128 - 442 mhz ondemand governor
Third, the display is the biggest and fastest battery drainer, no matter which rom you are using.
k-c-0 said:
My experience is, that Gingerbread ROMs in general are battery hungry. As for sense ROMs i can say that LeeDroid suits me best regarding battery life. At the moment im on oxygen and get a day out of it with normal use.
Best results with battery life i had with LeeDroid Froyo ROM (v2.4 i think). Smartass governor and screen off - 245mhz max/min sometimes got me 2 days without charging.
Maybe this helps you finding a solution.
Click to expand...
Click to collapse
If you use smartass governor, you do not have to set an extra profile for screen off. This governor automatically uses the min cpu frequency when the screen is off.
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 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!
Click to expand...
Click to collapse
http://www.ziggy471.com/2010/11/07/smartass-governor-info/
I am having the same problem with GB roms no matter how many times you calibrate the battery there is no improvement .
What's a safe level to overclock my phone to? I'm running the latest MIUI (1.9.16) with the lastest Tiamat kernel (1.1.3) I'm at about 1344 MHz right now. Can I go much highter?
Sent from my rooted, MIUI DInc2
From my testing, I've found there isn't to much to be gained going over 1.6ghz.
For a safe level I keep mine at 1.2 ghz. This has worked out well for me. Try different frequencies and see what works out for your needs.
I'm running JDKernel with the max set at 1.5 ghz, using the smartass governor. When I look at the "time in state" info, it usually shows about 75% of my time spent at 768 mhz. Seems to be working great.
Sent from my Incredible 2 using XDA App
Well, I tried bumping it up to 1.6, and I locked my phone and the screen turned off, but the keys stayed on, and it wouldn't come back up. So I pulled the battery and went back to 1.3 like it was before. Now its working great. I'm on smartass v2
Sent from my rooted, MIUI DInc2
If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .
PacerguyDon said:
If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .
Click to expand...
Click to collapse
I've been using SetCPU, cuz I couldn't understand Incredicontrol..... What's ideal if I'm running around 1.6 for voltage?
On the Jd Kernal, I'll bump it up to 1450 and go from there.
PacerguyDon said:
On the Jd Kernal, I'll bump it up to 1450 and go from there.
Click to expand...
Click to collapse
So, you don't know about for Tiamat? I'm using that one.
Plus, would anyone recommend using his Incredikernel as well?
I'll go about the same on the Tiamat. I usually will start at 50 mv over whatever the stock setting is on the kernel when running performance runs.
I didn't know that Chad had done a Kernel for Aosp romed Dinc2's. I know his Dinc1 Kernels were great.
I accidently had my phone at 1.9 for a day running jdkernel, no crashes or anything
Atm when my phone is charging, it gets bumped up to 1.4 and i have no issues at that speed.
if anybody was wondering how far a defy can be pushed but still be stable i think ive found the answer.
im running CM 7.1, overclocked to 1.3 ghz and have been at this clock rate for 3 months+ and have had NO problems. i have scored over 2700 on quadrant standard and the OS runs silky smooth. the overclocking program i use is setvsel off the android market.
Cool....
Mine is 1ghz normal CM7.2 NIGHTLY from Quarx. It's very stable and fast for me.
Playing Modern Combat 3 without lag
I have dual boot with CM7.2 nightly (default OS 1.1ghz OC) and CM9 Epsylon 6th April 1 ghz OC.
Both works pretty fine and stable.
BabiesWithRabies said:
if anybody was wondering how far a defy can be pushed but still be stable i think ive found the answer.
im running CM 7.1, overclocked to 1.3 ghz and have been at this clock rate for 3 months+ and have had NO problems. i have scored over 2700 on quadrant standard and the OS runs silky smooth. the overclocking program i use is setvsel off the android market.
Click to expand...
Click to collapse
I'm running
300 mhz/ vsel 18
600 mhz/ vsel 28
1000 mhz/ vsel 49
Am on WIUI stable, but I wanna know what vsels You've set on 1.3 Ghz
fiskenigaten said:
I'm running
300 mhz/ vsel 18
600 mhz/ vsel 28
1000 mhz/ vsel 49
Am on WIUI stable, but I wanna know what vsels You've set on 1.3 Ghz
Click to expand...
Click to collapse
18 @ 300
[email protected]
[email protected]
never get above 32ish degrees celcius unless im gaming for like an hour then its like 34/35