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.
Related
i search for help before posting this, whats the difference between savaged zen CFS OR BFS cuz i flashed the latest Savaged-Zen CFS on my evo running cm7 but when i set the max cpu to 1190 it automatically restarted my phone but my phone was stuck on boot never came on so before that one i also the savaged zen fr 3/30/11 n it was real fast it would load the internet fast or get to where ever real fast but once there on the page it was real laggy n sluggish which let me note that thats what i want, speed, i dont really care too much about battery cuz i carry 5 with me but i havent try BFS cuz i dont want to keep messing up my phone, which one u guys would b best for performance but that would also b response like cm7 running 1113 i would like to run 1190 cpu but keep my responsiveness thank u
CFS = completely faie scheduler. Better background app performance.
BFS = brainfuck scheduler. Better foreground app performance.
Some people swear by either. BFS /seems/ faster to me. Try both.
hey router54g thanks a bunch ama try BFS now thanx
router54g said:
CFS = completely faie scheduler. Better background app performance.
BFS = brainfuck scheduler. Better foreground app performance.
Some people swear by either. BFS /seems/ faster to me. Try both.
Click to expand...
Click to collapse
to add to this a bit...
cfs: guaranteed to work well. stock scheduler. smooth. works better for some than others.
bfs: not guaranteed to work well. for some, terrible. for others FANTASTIC. this is a luck of the draw sort of thing. this scheduler is usually not as smooth as cfs, and can sometimes have really bad performance, but for some people this is much much better. it isn't the stock scheduler, so it has to be built in manually. try it.
dkdude36 said:
to add to this a bit...
cfs: guaranteed to work well. stock scheduler. smooth. works better for some than others.
bfs: not guaranteed to work well. for some, terrible. for others FANTASTIC. this is a luck of the draw sort of thing. this scheduler is usually not as smooth as cfs, and can sometimes have really bad performance, but for some people this is much much better. it isn't the stock scheduler, so it has to be built in manually. try it.
Click to expand...
Click to collapse
Would also have to add in to change ur governors around as well. On smartass mine is very laggy but on demand and its perfect.
Dam I just finish trying both of them and everytime I set my Max to 1190 my phone keeps on booting n freezing and it stops working n stays on reboot n my buddy is running the exact same thing, cm7 with the dark horse theme v1.2b n his works nicely I have my min at 1113 n Max at 1190 n performance n it just doesn't work, I don't knw what's going on
Flip35 said:
Dam I just finish trying both of them and everytime I set my Max to 1190 my phone keeps on booting n freezing and it stops working n stays on reboot n my buddy is running the exact same thing, cm7 with the dark horse theme v1.2b n his works nicely I have my min at 1113 n Max at 1190 n performance n it just doesn't work, I don't knw what's going on
Click to expand...
Click to collapse
All your gonna do is kill your battery and instability with those settings keep the min at somewhere halfway at the most. 1152 has been the average stable maximum. Anything higher than that will just cause problems.
Just because the speedometer goes to 150, does not mean you should take the car that fast.
Lol ur right I ride a sportsbike so I'm used to living on the edge but I like the speed, I don't really worry about batt cuz I carry five with me but reading ur post helps me cuz if 1152 is really the stable than I should just keep the kernel fr cm7/rc4 cuz is one step down n smooth I just thought I would b able to run it at 1190 but guess not, thanx though
Flip35 said:
Dam I just finish trying both of them and everytime I set my Max to 1190 my phone keeps on booting n freezing and it huccstops working n stays on reboot n my buddy is running the exact same thing, cm7 with the dark horse theme v1.2b n his works nicely I have my min at 1113 n Max at 1190 n performance n it just doesn't work, I don't knw what's going on
Click to expand...
Click to collapse
Set your min to the lowest possiblle. Your governer will scale it up as needed. Min freq is only really hit when your CPU is idling to save battery. When this happens the CPU isn't really being used. Imagine it as your car's RPMs. You wouldn't want to idle at 6000 RPMs, it'll only kill your tranny/engine (CPU/power circuitry) quicker and guzzle gas (battery) like mad.
Also experiment with governers. Savaged-Zen worked best for me at first but lately it's slowing down (it's supposed to learn your behavior over time; same results on my brother's phone so obviously it doesn't work well). I'm using straight-up OnDemand right now and it seems to be pretty responsive.
Lastly those crashes are from overaggressive clocks (speeds). Not every CPU on the wafer is createe equal. Some phones can't sustain 1190, some can sustain more. It's luck of the draw when you buy your phone.
dkdude36 said:
to add to this a bit...
cfs: guaranteed to work well. stock scheduler. smooth. works better for some than others.
bfs: not guaranteed to work well. for some, terrible. for others FANTASTIC. this is a luck of the draw sort of thing. this scheduler is usually not as smooth as cfs, and can sometimes have really bad performance, but for some people this is much much better. it isn't the stock scheduler, so it has to be built in manually. try it.
Click to expand...
Click to collapse
I think BFS vs CFS comes down to how many background processes you have running. But you gotta be careful with task killers. Only kill the apps you won't be opening again for a while, and only autokill the tasks you rarely use. It ends up costing more battery and performance-wise to kill and the later reload many tasks than to just let them idle. Remember most tasks won't eat up any CPU whennot in use, and Android handles their RAM usage well enough for most cases.
I have recently rooted my dhd and currently running CM7. Using the cpu setting within the performance menu I am wondering what peoples thoughts are on a noticeable but safe increase of cpu speed. its set as 1017MHz which i believe is default. I am told I can run anything up to 1500 safely. can anyone confirm this and also tell me what kind of result (performance and battery life) i should expect.
thanks
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
hmohammed43 said:
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
Click to expand...
Click to collapse
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
darude0306 said:
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
Click to expand...
Click to collapse
nice one dude
I'm running cm7 and I'm overclocked to 1.5 ghz. It's been totally fine for months.
Sent from my Motorola Startac running Atari 2600 software!
rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
Lucky you picked a linuxhead!
The system itself has a daemon (background process built into the system) that handles overclocking. It's all explained on the page and also on this thread:
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
You can use another app (like SetCPU) but the daemon usually handles screen off's quicker. The governors basically determine how the processor frequency is changed. I'll explain the common ones:
Performance - Runs at highest speed, so if you have a range of 200 to 1.3G, it'll stay at 1.3G all the time, not usually the best
Ondemand - The universal default for phone overclocking, it only changes the speed up after a certain percentage of the CPU is used, and it switches on the fly, so if the CPU is used too much at 400MHz, it'll ramp it up to maybe 600 or 800, and if it's still overused, it'll put it up to maybe 1 or 1.2G
Conservative - This is like ondemand, except it makes the changes more gradual. It can give noticable lags in the foreground at times, so this is mainly used when the phone is asleep (screen off)
Smartass - This governor is like ondemand, except it'll less readily switch frequencies to higher values when it detects the screen off. This isn't really used because the overclocking daemons take into account the phone being awake or not
Basically, there isn't really a need to change governors, only really frequencies if anything. The thread, however, does tell you how to change governors.
Im using latest LeeDroid GB 3.2.1 and to be honest with the work he's done with the Kernal (3.1.8BFS) I have found that the ROM is a lot MORE responsive without me overclocking the CPU.
Im not really sure how it all works, but I guess doing this on different ROMS has its own different out comes.
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
toby_lerone said:
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
Click to expand...
Click to collapse
There is a benefit when you use certain apps, or even sense itself. For example, I've never had sense ui freeze, or go slow. The under clocking helps to improve the rubbish battery life when your phone is asleep.
In terms of measuring the gain, I have no idea. Really, I'd think you could use a process heavy app, or benchmarking app and see.
There's also loads of guides on overclocking to help out! (that's how I got the hang of it! )
Sent from my Desire HD using XDA Premium App
For the need on OC, it depends on the kind of apps u're using. If u're happy w a non OC DHD, its totally up to u.
But for the UC, it works as a terrific battery saver, mich better/effective than other battery saver soln on market
The safe range depends on the DHD as the manufacturing changed even though same part, i'm OC 1.5GHz "On Demand" profile and under clock 245MHz on screen off "Power Save" profile.
Getting approx a day usage on Lee 2.1.
I wanted to know some more about undervolting and was hoping someone could help and explain a bit. Basically, what I'm seeing is when I undervolt my device on the max side of things, eventually the device freezes and needs a battery pull or reboots. When I don't touch the max voltage values and only drop the min values the phone seems more stable and doesn't reboot. Can someone explain if my thinking of only undervolting the min values is correct and why this may be happening. Also, what would be the proper way to undervolt the phone? I have been using system tuner to do so on deck's 1.3 ROM using the Lee +sbc kernel. Thanks for taking the time to read this and for all the helpful responses.
Sent from my Decked Evo running Lee+sbc... It's easier this way.
I have this same question! I was trying to figure this out becuase the freedom kernels have something to do with under and over voltage to allow better OC? not sure on why the you would need and over voltage to over clock?...
What is your ROM/Kernel setup?
Remember that undervolting and underclocking are two different things. Over/underclocking, via apps like setcpu, raise/lower the frequency at which your processor operates. Over/undervolting raises/lowers the power voltage available to your processor at any given frequency. This can potentially cause problems if you have a kernel set to undervolt your processor while running an app like setcpu to overclock it. This may be why you are seeing issues with your phone.
pmacevad said:
[snip]
I have been using system tuner to do so on deck's 1.3 ROM using the Lee +sbc kernel.
[snip]
Sent from my Decked Evo running Lee+sbc... It's easier this way.
Click to expand...
Click to collapse
Concordium said:
What is your ROM/Kernel setup?
Click to expand...
Click to collapse
OP clearly states he's running Deck's 1.3 and Tiamat 3.3.7 (aka LEE kernel)
OP should also state Deck's ROM version but I'm assuming 1.3d as it's most popular next to 1.3 Stable.
I'm running the same setup - Deck's 1.3d with LEE SBC. I'd like someone to explain (as the OP also asked) the difference between the MIN and MAX sides of the undervolting equation please.
(I do understand underclocking AND that it is a separate and different animal and for the record, my EVO is UC'd to 128/499MHz and using Smartass governor)
I'm just not sure what I'm looking at in the ST interface (what's the first number and what's the number in [] brackets?) and also not sure just why there is both a min and max voltage for each frequency and how it affects performance.
Thanks much for any inputs.
J.
I use vipermod and terminal emulator for aosp roms its much more stable than using system tuner and you can drop all voltages with a single command it all depends on your particular hardware but typically around -100 the phone will lag or freeze i usually stick to -50 at stock voltages and -25 on overclock i never overclock over 1075mhz as anything higher and my phone tries to cook my fingers however now im oc to 1.6ghz on my et4g with a 200mhz min and it stays nice and cool like it was clocked at 1.2ghz stock the exynos is capable of clock speeds up to 2 ghz but the phone doesnt handle those speeds well similar to the evo not liking anything over 1.19 at 1.2 on the evo theres a good chance of frying the logic board or bursting the battery from heat if you overclock dont undervolt too much as it makes the processor get really really hot due to it having to work harder from lack of energy to power it
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
To answer the min/max at each freq min is the lowest voltage that freq will run while idle max is the highest voltage the freq will run while in use the voltages are depenedant on the load running at the particular freq ie how many process' are running the more process' the higher the voltage required to power the processor
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
Is there an app the will show actual voltage the CPU is using in real time?
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
bmw pro will u can set the mv on the widget or set recording in the app and it will log the info
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
I had a similar issue with undervolting and underclocking. I was setting my CPU min/max to 128-499 MHz and undervolting to -75 or -100 using Lee with Smartass v1. But I was getting too many random reboots and freezes on each ASOP rom I tried (e.g. Deck 1.3d, CM7).
I've been playing around with these settings. I changed my CPU to 128-576, no undervolting, and SZ 2.2.1 with SavagedZen governor. I haven't had any random reboots and my batter life is about the same...plus my phone is MUCH snappier. I'm still getting a little screen on lag but not nearly as much as I was at 128-499 and undervolted.
As a note, I normally run Deck 1.3d as my daily driver but for the last couple days I've been running KWIQ. It's definitely giving 1.3d a run for its money as becoming my daily driver.
Anywho, are there any rules of thumb with undervolting and underclocking? Like is 128 MHz is too low with -100 undervolting? Or are these things pretty much phone dependent? I know each phone seems to respond different to these things.
-EViL-KoNCEPTz- said:
To answer the min/max at each freq min is the lowest voltage that freq will run while idle max is the highest voltage the freq will run while in use the voltages are depenedant on the load running at the particular freq ie how many process' are running the more process' the higher the voltage required to power the processor
Click to expand...
Click to collapse
Thank you. That made good sense to me. Question then: is it suggested/typical to drop min and max by equal amounts or is it typical to drop min more (so there's juice for the proc under load but maybe being more aggressive with the sleeping/idle side of things or can the proc run at a given frequency at different voltages)?
jackfrost909 said:
I'm just not sure what I'm looking at in the ST interface (what's the first number and what's the number in [] brackets?)
Click to expand...
Click to collapse
Are you familiar enough with ST to shed some light on this? Please if so. Thank you.
detcup4evr said:
Is there an app the will show actual voltage the CPU is using in real time?
Click to expand...
Click to collapse
-EViL-KoNCEPTz- said:
bmw pro will u can set the mv on the widget or set recording in the app and it will log the info
Click to expand...
Click to collapse
Though I have to recheck this I don't remember BMW showing the voltage being used at each frequency just the overall voltage draw. If you know otherwise or another tool that does, please share
Thanks for all the help.
J.
--
Tapa Tapa Tapa..
Let's see.. My phone flies, my battery doesn't suck.. and your point was.... ?
OG EVO - Deck'd and LEE'd because it's just better this way.
Lionfish kernel
Has anyone tried undervolting with lionfish kernel on SENSE Roms, is it stable?
einstein562 said:
Has anyone tried undervolting with lionfish kernel on SENSE Roms, is it stable?
Click to expand...
Click to collapse
I use aggressive and it works well but some phones don't like it, hopefully I can get vipermod to work, and that will allow you to adjust each frequency independently
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
I actually just got rid of lionfish aggressive on MikG3.11
I had a lot of lagginess, but battery life was really good... Back to anthrax for me, lionfish was based at one point on freedom kernels I thought, maybe one of those would be better...?
What's the best thing to use to control undervolting on sense roms?
Sent from my PC36100 using Tapatalk 2
Is the battery life improvement substantial when undervolting?
I have governators set at 240-650max and am getting decent life on my ics savoca kernel.
What % improvements are obtained?
Well I don't have logcats and scientific evidence, but I saw about 12 hour days, with moderate use, everything syncing, lots of text a few calls, hotspot for an hour or so, some web browsing, but the random revolts and lagginess on that was horrible, freedom was better.... It's worth it to underclock
I have everything set to 384-1152.
Different governors for profiles, screen off @ conservative because I have a lot to sync
Sent from my PC36100 using Tapatalk 2
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
shinesthru said:
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
Click to expand...
Click to collapse
Hopefully more people respond to this, as I'd like to know more details around the msm-dcvs governor. I had it enabled in Clark's 0.0.6 ROM, and I noticed it was pretty much locked at right around 1000-1500mhz. It wouldn't scale below that. I don't know if it was something in the ROM or not, but I used Voltage Control to scale the min down to 352mhz or whatever it is.
I changed the governor to ondemand and set as boot as service (was getting errors creating the init.d script) and it seems to be functioning fine now.
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
EndlessDissent said:
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
Click to expand...
Click to collapse
What has your battery life been like?
jhavron said:
What has your battery life been like?
Click to expand...
Click to collapse
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
EndlessDissent said:
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
Click to expand...
Click to collapse
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
hayzooos said:
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
Click to expand...
Click to collapse
With the stock CM10 kernel, as soon as I touch the screen, the frequency jumps to 1134MHz and stays there until you turn the screen off. Then, it drops to the min. speed until you turn on and touch the screen again, at which point it jumps back to 1134MHz and locks itself there.
With the KT747 kernel, the speed more-or-less limits itself to 702MHz, and it's nearly impossible to make it scale any higher. KToonsez refuses to acknowledge the problem, so it won't be fixed anytime soon.
I've gotten CPU Spy graph screenshots to illustrate the problems (comparing the stock ROM to AOSP ROMs while doing the same task), but all parties still deny the problems exist. I don't really know what to do to get them to fix it at this point, so I just gave up. I'm hoping it's just some JB driver issue and it'll be fixed when the official JB kernel source is released.
Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but Im not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
J
Sent from my Nexus 7 using xda app-developers app
I've got elementalx on my nexus 7 2013 : it works perfectly on 1.7ghz... And this kernel has some cool features like double tap to wake... For the battery, you can underclock but while you overclock just a bit, the battery life will be OK
So, flash it ! ?
Térence
Sent from my Nexus 7 using xda app-developers app
JackHanAnLG said:
Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but I'm not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
Click to expand...
Click to collapse
I didn't know there was any kind of a fuss! I think that we are all lucky in the sense that we have multiple good choices for kernels on the Nexus devices and most others in general.
It goes without saying that any custom kernel is going to give you the ability to overclock and it just boils down to what the max MHz is that any specific device can handle. Not that I've tried it but I've seen claims of 1.9 MHz and higher (ElementalX) running fine but each device is going to be different and I personally don't see the point of overclocking that high. I've had mine at 1.7 and 1.8 MHz to run some benchmarks, try different governors (elementalX & ondemand) and get an idea about battery life at those frequencies. Did all that so I can get a comparison to what I see running 1.6 MHz which is what I use everyday, that plus the gpu is set at 450 MHz while using the ondemand governor for both cpu and gpu. I do have to say that my N7 ran very well at 1.7 and 1.8 MHz but "my" goal is to get the best combination of performance and battery life, for my use. I generally see 7- 10 hrs of screen on time which includes watching video and some gaming. Not using any third party apps to control the kernel, mostly default settings when using the aroma installer, slight undervolt for 384 MHz, I don't use DT2W or S2W,. Basically... it's just too easy to install the ElementalX kernel, not worry about having to dial it in and still see a noticeable improvement in performance and battery life. No fuss, no muss!
What are your settings?
!PimpedOutNexus7!
shaolinz said:
What are your settings?
!PimpedOutNexus7!
Click to expand...
Click to collapse
Aroma installer;
Set each core separately = no
Max Cpu Frq = 1620Mhz
L2 cache and bus = elementalx
Undervolt = 850 min
Thermal = run hot. Mine never gets hot at 1.6 MHz and this way you don't have to worry about thermal throttling.
Max GPU = 450 MHz
Gpu governor = ondemand
i/o scheduler = deadline.
Sleep/wake settings = None
Other settings = use stock ondemand settings. enable max screen freq, enable usb fastcharge, disable magnetic screen off, disable fsysnc, all other options unchecked,
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
You can use the elementalx governor which does a great job and does improve battery life. In the other settings page leave "use ondemand governor' unchecked and check the box for "gboost." For gaming I personally like to leave mine set up with the ondemand governor, seems just a little bit smoother with less frame drops. You can try both to see which works better for you.
Thanks a lot in will let you know how it goes ....great help +1
!PimpedOutNexus7!
Hmmm feels like its running hot
!PimpedOutNexus7!