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.
Overclock, it means to get about 806mhz, and successful overclock means to run the CPU smoothly and fast on 806mhz. Some roms support the overclock, some don't and other roms say they can not overclock with 806mhz but with 787mhz because of getting frezzed, rebooted and so on. But if you look clearer on the CPU and look at time in spare or with the app CPU spy you can easily see that the values 787 and 768 don't run a percent of the whole time. This means they even run with stock speed 600MHz. It even show you first that the CPU run so fast and bla bla.. If someone tell you to run the CPU not with 806mhz because of freezing, graphic glitches don't believe it, if you change it to 767 or something like that it will run with just 600MHz.
That's life dudes, so don't believe everything you see or hear and be carefully
Regards Matteo
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
i was told that overclocking could reduce the life of your wfs.
this is the reason why i dont overclock.
i did it once and 3d games started showing glitches.
i would recommend ppl to test and read first before setting it to 700-800mhz.
thats just my oppinion.
I know that all of the cdma oc kernels are absolutely stable at 806. I have indeed never heard of a properly flashed kernel freezing under oc in the wfs. (admittedly I don't read the gsm threads too much) And as to shortening the life if the phone, if you plan on keeping it for like 5 years then sure, it might. But your not going to. Your battery on the other hand...
Sent from my HTC_A510c using Tapatalk
BigChillin said:
I know that all of the cdma oc kernels are absolutely stable at 806. I have indeed never heard of a properly flashed kernel freezing under oc in the wfs. (admittedly I don't read the gsm threads too much) And as to shortening the life if the phone, if you plan on keeping it for like 5 years then sure, it might. But your not going to. Your battery on the other hand...
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
I agree.
The freezing I wouldn't put down to kernel's.
More likely to be the processor.
Same with desktop processors, you can't expect every one of them to perform the same.
Because one is a great overclocker it doesn't mean that they all will be.
just because they are the same processor, they came from a different yield which may have been better or worse.
By the way I've been running mine at 806 for over 3 months or more with no ill effects.
matt5eo said:
don't believe everything you see or hear and be carefully
Click to expand...
Click to collapse
Words to live by...
My phone starts glitching in 3d as soon as I clock my CPU higher then 600. Screen turns purple in benchmarks.. so no overclock for me.
Sent from my (s-off + rooted) Wildfire S using XDA app and CM7.2
VitanyLTD said:
My phone starts glitching in 3d as soon as I clock my CPU higher then 600. Screen turns purple in benchmarks.. so no overclock for me.
Sent from my (s-off + rooted) Wildfire S using XDA app and CM7.2
Click to expand...
Click to collapse
The reason ist often the wrong rom for overclock. I tried to overclock CM7 to but without look, now I did my own rom and here it goes antutu benchmark about 1700
Sent from my HTC Wildfire S A510e with JxMatteo_ROM_V1.1 ROM
I run my wfs on 122/768MHz w/o any problems... On CM 7.2 ...
And its not going to shorten life of device for like idk how long... Phone uses 768 only sometimes, when needed and not all the time... So its not such a stress to a cpu.
But i saw one guy for example, complaining that his phone was hot when he turn off or something, and he did overclock to 768/806... so he is constantly running it over 600MHz... I just wan't to see what will happen in few months or...
I have overclocked my phone with m1ndh4x8r's rom.
It running at 245-806mhz with smartass2 governor.
It runs about 10 days now, with absolutely no problem or freezes.
And after of 3-4 hours of constantly use (browsing games), it just gets barely warmer.
That's my 5 cent
My phone currently run with 787/200 with SetCPU and several custom profiles: 320/120 screen off, 480/200 in call, temp>48,batt<15.
With 806 get some visual glitches, but on 787 it run more than 4 hours of stress test in SetCPU.
__DS__ said:
My phone currently run with 787/200 with SetCPU and several custom profiles: 320/120 screen off, 480/200 in call, temp>48,batt<15.
With 806 get some visual glitches, but on 787 it run more than 4 hours of stress test in SetCPU.
Click to expand...
Click to collapse
Did you read my post dude? I don't think so, if you take the values 787 it will run with just 600! First read the post than answer another thing is that 48°C were absolutely to hot! Overlocking should not be just like a game, it's a science.!
Sent from my HTC Wildfire S A510e using xda premium
LOL
Overclocked rom perform better than stock 600/400 even in phone shell itself, removing visual lags. Try and you will see it.
And there are still games..
With such reasons there are no need to buy new CPU for desktop because 99% of time it idling
matt5eo said:
Overlocking should not be just like a game, it's a science.!
Click to expand...
Click to collapse
Ofc, and you will need to interpret and understand results, just like "real" science
matt5eo said:
Did you read my post dude? I don't think so, if you take the values 787 it will run with just 600! First read the post than answer another thing is that 48°C were absolutely to hot! Overlocking should not be just like a game, it's a science.!
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
matt5eo, that info you posted isn't 100% accurate. Overclocking is in fact a science and if you rise the CPU speed, a benchmark should present better results. Right? So let's see some science applied.
I just did a simple test on m1ndh4x8r GB 2.3.5 ROM (updated kernel), with No Frills CPU Control and Quadrant Standard.
320/600, performance, sio score: 762
320/768, performance, sio score: 879
320/787, performance, sio score: 890
320/806, performance, sio score: 925
320/600, performance, noop score: 769
320/768, performance, noop score: 851
320/787, performance, noop score: 889
320/806, performance, noop score: 929
320/600, interactive, noop score: 742
320/768, interactive, noop score: 871
320/787, interactive, noop score: 885
320/806, interactive, noop score: 908
320/600, smartass2, noop score: 712
320/768, smartass2, noop score: 860
320/787, smartass2, noop score: 872
320/806, smartass2, noop score: 898
I couldn't test the other governors now because I ran out of battery...
Anyway it's a waste of time because as we can see the score rises consistently with the selected CPU speed.
The CPU speed used at a given time depends a lot on the governor and on the I/O scheduler you choose.
From what I saw the governor can make the huge difference between the CPU speed increases and decreases. With the performance and interactive governors Quadrant showed the real clock at which the CPU was running (on System Information) and it was consistent with the maximum clock I selected on No Frills CPU Control.
When I selected 787MHz, the actual speed was in fact 787MHz and not 600MHz like you say. The same happened with the other clocks (600, 768, 806).
So what you write might apply to some kernels but definitely not to all.
I don't have the time to put nice screen captures here but I certainly have no interest in inventing scores and contradicting someone just for fun.
Just wanted to let you know my results.
This is off topic but i'll write it here anyway.
I don't have enough posts to post on your thread on JxMatteo_ROM_V1.1.
Thank you for the rom, it's very good.
I was about to get rid of this phone and buy another until HTC unlocked bootloader, your rom made my phone perfect.
Like the font also. Is there some way to change font to something else?
Been wanting to try the Airwolf font, might be cool...
Tested it on my WFS, it was useless!
Lykkis said:
This is off topic but i'll write it here anyway.
I don't have enough posts to post on your thread on JxMatteo_ROM_V1.1.
Thank you for the rom, it's very good.
I was about to get rid of this phone and buy another until HTC unlocked bootloader, your rom made my phone perfect.
Like the font also. Is there some way to change font to something else?
Been wanting to try the Airwolf font, might be cool...
Tested it on my WFS, it was useless!
Click to expand...
Click to collapse
Hello dear Lykkis
I see that you like it very much, It makes me happy to read lines like this anyway thanks for the feedback
In my next update you will be able to choose every font you want, and also every themes you want on your JxMatteo ROM!
PS. JxMatteo V1.2 will make your phone more than perfect
Sent from my Wildfire S A510e with JxMatteo_ROM
Have a quick go at this people - run an oc kernal such as CM7 or something and overclock to 806mhz. For a few hours, do it.
Then switch off your phone. Remove the battery and SMELL IT. SMELL it like you mean it. I'm telling you SMELL it, FEEL it. It smells like one of those electric car toys and it feels relatively hot. I can smell it immediately, I don't even have to go close to the phone. a little scary tbh. however, my phone has had no problems at all, God forbid on 806mhz, so I leave it at that.
I don't think it's that bad for your phone's lifetime, as most of us will not own this for more than two or three years, I'm sure. It might even be healther at times to underclock the CPU most of the time when not using it. This must balance out the effects, right?
*se-nsei. said:
Have a quick go at this people - run an oc kernal such as CM7 or something and overclock to 806mhz. For a few hours, do it.
Then switch off your phone. Remove the battery and SMELL IT. SMELL it like you mean it. I'm telling you SMELL it, FEEL it. It smells like one of those electric car toys and it feels relatively hot. I can smell it immediately, I don't even have to go close to the phone. a little scary tbh. however, my phone has had no problems at all, God forbid on 806mhz, so I leave it at that.
I don't think it's that bad for your phone's lifetime, as most of us will not own this for more than two or three years, I'm sure. It might even be healther at times to underclock the CPU most of the time when not using it. This must balance out the effects, right?
Click to expand...
Click to collapse
I know what you are talking about, I also run my JxM ROM with 806mhz and I have to say that everything works fine, without smelling like sh**
I like developing, and I also like overclock kernels, but with the wrong ussage you won't see what we see, we see a great project in it and also a chance to speed up our devices
Sent from my Wildfire S A510e with JxMatteo_ROM
Lykkis said:
This is off topic but i'll write it here anyway.
I don't have enough posts to post on your thread on JxMatteo_ROM_V1.1.
Thank you for the rom, it's very good.
I was about to get rid of this phone and buy another until HTC unlocked bootloader, your rom made my phone perfect.
Like the font also. Is there some way to change font to something else?
Been wanting to try the Airwolf font, might be cool...
Tested it on my WFS, it was useless!
Click to expand...
Click to collapse
you can change font by making you own theme, with UOT KITCHEN.
if you lest say want just to change font, just choose font change, no need for anything else, and it will update theme with only font ... you have it all in how to ... good luck.
miguelca said:
matt5eo, that info you posted isn't 100% accurate. Overclocking is in fact a science and if you rise the CPU speed, a benchmark should present better results. Right? So let's see some science applied.
I just did a simple test on m1ndh4x8r GB 2.3.5 ROM (updated kernel), with No Frills CPU Control and Quadrant Standard.
320/600, performance, sio score: 762
320/768, performance, sio score: 879
320/787, performance, sio score: 890
320/806, performance, sio score: 925
320/600, performance, noop score: 769
320/768, performance, noop score: 851
320/787, performance, noop score: 889
320/806, performance, noop score: 929
320/600, interactive, noop score: 742
320/768, interactive, noop score: 871
320/787, interactive, noop score: 885
320/806, interactive, noop score: 908
320/600, smartass2, noop score: 712
320/768, smartass2, noop score: 860
320/787, smartass2, noop score: 872
320/806, smartass2, noop score: 898
I couldn't test the other governors now because I ran out of battery...
Anyway it's a waste of time because as we can see the score rises consistently with the selected CPU speed.
The CPU speed used at a given time depends a lot on the governor and on the I/O scheduler you choose.
From what I saw the governor can make the huge difference between the CPU speed increases and decreases. With the performance and interactive governors Quadrant showed the real clock at which the CPU was running (on System Information) and it was consistent with the maximum clock I selected on No Frills CPU Control.
When I selected 787MHz, the actual speed was in fact 787MHz and not 600MHz like you say. The same happened with the other clocks (600, 768, 806).
So what you write might apply to some kernels but definitely not to all.
I don't have the time to put nice screen captures here but I certainly have no interest in inventing scores and contradicting someone just for fun.
Just wanted to let you know my results.
Click to expand...
Click to collapse
Any response for this? Waiting for the final conclusion on it.
d33ps1x said:
Any response for this? Waiting for the final conclusion on it.
Click to expand...
Click to collapse
lol, d33ps1x, may i remember you that matt3o is the one of the fake s-off method? he obviously doesn't know what he's talking about.
I'm using NoFrills CPU and want to find the right balance between overclocking, performance and battery...
What speeds and governors are everybody using for their Plays?
I'm using 1.2 Ghz max 130 Mhz min with SmartassV2 and sio. All seems okay to me.
I'm using 921mhz-122mhz intellidemand2 with sio governor and everything is smooth + battery is great
Sent from my R800i using xda premium
1401Mhz Max, 180Mhz Min (when Screen On), 785Mhz Max-180Mhz Min (When Screen Off)
Noop + InteractiveX
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
1401Mhz Max, 180Mhz Min (when Screen On), 785Mhz Max-180Mhz Min (When Screen Off)
Noop + InteractiveX
So many different settings!
Was hoping there'd be a 'common' setting that everyone kind of determined was best.
Thank though.
Still interesting, and would like to see what more people are using still.
Mines currently 1.613 Ghz Max, 245 Mhz Min. Virtuous Governor, Noop I/O Scheduler.
On intensive apps I change the max clock to 1.901Ghz however this I don't recommend for most people.
I also only use 1.9Ghz when using Android 2.3.7 with DoomKernel, as only that Kernel seems to allow for voltage changes... Which i apply when using that kind of speed, whereas the default voltages are much higher for that clock than I usually set.
Everyone's Play is different, and not all Plays can sustain high clocks at specific voltages. You need to find your own 'sweet spot'.
Spizzy01 said:
You need to find your own 'sweet spot'.
Click to expand...
Click to collapse
Is there an app for that?
No.
You need to increase your clock little by little until you're happy. Then, if you're on GB using DoomKernel you need to lower the voltage as much as you can without it crashing if you want it perfect.
Most people simply oc though and don't bother with the voltages, but it will reduce power consumption and extend the life of your phone with the OC enabled.. As normally running your CPU past its specification will wear it out faster.
Sent from my R800i using xda premium
As DiKeJ said in his ROM thread:
In my opinion, interactiveX, and frequency of CPU 364.8-1305.6MHz gives awesome stability and performance
Click to expand...
Click to collapse
:good:
TRUE FACT.
you should use a kernel that allows you to undervolt... there was some article with the galaxy S3, where they tested different settings with OC+UV and YES, Under Volting gives better battery life!!
A lot of people here say, that UV will have no effect on battery, but they have no idea how a processor works... so they just should stfu!!
I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...
TiTAN-O-One said:
I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...
Click to expand...
Click to collapse
AFAIK, governor's clock speed will be "locked" to the highest possible clock when you are running benchmark. let's take lulzactive as an example. look at this line
DEFAULT_INC_CPU_LOAD 70
Click to expand...
Click to collapse
, 70 means when processor's load is reaching 70% , the clock speed will be increased some steps. in benchmarking, cpu load is always high >>90%(i'm not sure so CMIIW) that means your clock speed will always be locked in that highest possible value no matter what your governor is (even conservative). the only difference is how long they need to get up to the next level of clock speed
so personal experience will be better to get your right value rather than benchmarking. every governor has difference time to reach higher level of clock speed which is not be able to be experienced in benchmarking. this is contrary to personal experience(daily use) which you can feel how your phone react toward a command. let's take example of the most battery saving(conservative) and highest performance(performance). you can feel that conservative is rather slow in executing command while performance will give nice personal experience. both of them didn't give any significant difference in benchmarking score but both of them can give significant difference in personal experience
i hope you get my point here
CMIIW
Thanks alot But according to personal experience, I nvr felt any lag whatsoever... In gaming like shadow gun, didn't feel that much lag compared to the stock kernel from Samsung...
Thanks for correcting me anyway! I appreciate it
Sent from my GT-I8150 using xda app-developers app