I am currently Runing "ondemand' OC'ed at 800/1460, noop/ondemand with the CNA 1.4.0 ROM and Matr1x v17.
Just a question, which would be better for gaming? (smooth/better battery). Basically I ran SmartarseV2 and I feel ondemand is better.
The game I used to test was Shadowgun as this game is a heavy duty/performance heavy game.
Any tips or suggestions?
The matrix kernel offers BFS and CFS. I'm pretty sure its CFS I could be wrong about which one it is but... it is made for things like gaming so I'd go with that version of Matrix. You may want to turn down the Min and Max OC. I can play shadow gun with VERY LITTLE/ mostly NO lag whatsoever with my setup and retain a lot more battery.
Try the Lazy, Intellidemand, and even Lulzactive (if you got the right settings) governors. They'll work better than Ondemmand as they do similar things but.... better and they save more battery.
You'll notice changing that 800 (Min) ---> 100 alone will save mass battery. And you don't really need 1460 GHZ lol . That set up is only used to show off how awesome your phone is for like 10 minutes. Or videos and what not. Maybe go for 1300. If matrix supports it use Live OC to 110. You'll get a speed boost without epicly draining your battery.
Nexus S (GSM i9020a)
AOKP (Build 25)
Eugene's Kernel (Speedy 7)
OC 800/100 (Lionheart)
Live OC (105)
I think it's bfs that's more suitable for gaming since it targets resources on the app running in the foreground. Cfs is for multitasking; it evenly distributed resources to all running apps. Cfs tends to be more stable of the two.
You without me is like Harold Melvin without the Blue Notes
309041291a said:
The matrix kernel offers BFS and CFS. I'm pretty sure its CFS I could be wrong about which one it is but... it is made for things like gaming so I'd go with that version of Matrix. You may want to turn down the Min and Max OC. I can play shadow gun with VERY LITTLE/ mostly NO lag whatsoever with my setup and retain a lot more battery.
Try the Lazy, Intellidemand, and even Lulzactive (if you got the right settings) governors. They'll work better than Ondemmand as they do similar things but.... better and they save more battery.
You'll notice changing that 800 (Min) ---> 100 alone will save mass battery. And you don't really need 1460 GHZ lol . That set up is only used to show off how awesome your phone is for like 10 minutes. Or videos and what not. Maybe go for 1300. If matrix supports it use Live OC to 110. You'll get a speed boost without epicly draining your battery.
Nexus S (GSM i9020a)
AOKP (Build 25)
Eugene's Kernel (Speedy 7)
OC 800/100 (Lionheart)
Live OC (105)
Click to expand...
Click to collapse
Thanks for that mate, just a question, I am using the Air Kernel now. It seems to be a little more stable then matr1x when it come to live oc. What would be the best settings do you use when you live oc? I am liveoc to 110%. basically running at 220/1100. I have not increased the speed. 2ndly i think I will try lazy for gaming. Heard lazy is good. I see you are using Lionheart. is that only for your stanby time for basic phone usage?
I always use conservative for gaming because my phone runs too hot with any other governor
Sent from my Nexus S 4G using Tapatalk
ashwin988 said:
Thanks for that mate, just a question, I am using the Air Kernel now. It seems to be a little more stable then matr1x when it come to live oc. What would be the best settings do you use when you live oc? I am liveoc to 110%. basically running at 220/1100. I have not increased the speed. 2ndly i think I will try lazy for gaming. Heard lazy is good. I see you are using Lionheart. is that only for your stanby time for basic phone usage?
Click to expand...
Click to collapse
For gaming I think 110 is good. I use Lion heart for everything. Gaming standby music browsing. And my Live OC is 105. I've tried Lazy 1000/200 with Live OC at 110 (so 1100/220) and got really good results too. But yeah UC Lion heart is working nicely. I'm not sure what governors Air Kernel supports because I haven't used it for more than a few hours. I hear its really good but my voodoo colors don't work on it so I'm holding off
Nexus S (GSM i9020a)
AOKP (Build 25)
Eugene's Kernel (Speedy 7)
OC 800/100 (Lionheart)
Live OC (105)
If you want the best gaming performance, then use performance mode (your phone might not be able to stay at 1460 on performance though, you should lower it 1200-1300). Just remember to change it back after you've finished gaming.
If you dont want to do it manually, you could set up a tasker profile to automatically change the governor to performance and back to normal, when opening and closing your games.
ashwin988 said:
Thanks for that mate, just a question, I am using the Air Kernel now. It seems to be a little more stable then matr1x when it come to live oc. What would be the best settings do you use when you live oc? I am liveoc to 110%. basically running at 220/1100. I have not increased the speed. 2ndly i think I will try lazy for gaming. Heard lazy is good. I see you are using Lionheart. is that only for your stanby time for basic phone usage?
Click to expand...
Click to collapse
I think Lazy is not that good for gaming. Lazy is meant to be more battery saving than Ondemand, at the cost of little performance.
I don't play heavy games that much, and I'm just using Conservative, good for me.
Related
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 want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
boimarc89 said:
I want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Why not just not overclock? Also, the kernel that comes in Inspired Ace isn't overclockable.
There are many battery saving options! If you have the Leedroid kernel, in setcpu you have the option of running your proccesor at Powersave, performance,smartass and so on...this is also in a few other kernels but I am not sure which ones at the moment.
And if you are really hyped up on saving battery, shutoff haptic feedback, turn of data when you are not using it, lower screen brightness, Use a task killer to kill stray apps(if you were playing angry birds kill it afterwards).
These are a few things you can do that will increase your battery life significantly...
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Gene Poole said:
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Click to expand...
Click to collapse
This.
Simply underclocking will solve your problems. I prefer to run @1.4 Ghz. I have everything optimized for speed & efficiency and still don't lose in battery performance.
Running CM7 with LordMod UE 2.6 kernel and smartass CPU governor, I can set the max speed to 768mhz with very little performance hit noticed. I might just keep it that way, haven't decided yet. Scrolling is still smooth, Angry Birds is still smooth. The cool thing about running max 768mhz with the pinky undervolt script is the CPU voltage never goes above 900mv.
I'm running CM7 with nightly 91 and on my Vibrant, they made a kernel that was stock uv no oc and u could use it all day, literally....
Sent from my Desire HD using XDA App
I just purchased SETCPU from the market. I know its free here but from what I've read it is well worth 2 bucks (or a lot more).
I'm running bamf 1.0,9 cubed and I verified in setcpu it is set to low of 368 and high of 1 ghz.
I am using stock kernel but thinking of trying adynaline's new kernel.
Anyway should I set a custom profile? Any suggestions on settings? I'm more interested in avoiding screen freeze than speeding up anything.
Profiles are not needed.
They're just usefull if you want to underclock at a certain battery level or temperature to save battery or cool down the device in my opinion.
Sent from my LT15i using XDA Premium App
I just overclocked to 1.28 we'll see how it goes....
recDNA said:
I just overclocked to 1.28 we'll see how it goes....
Click to expand...
Click to collapse
should be fine.
i had some profiles of:
screen on - min was as low as it could go, max = 1.4ghz -ondemand
screen off - min was as low as it could go, maz = 5xx mhz - batt saver or conservative
battery at 50%, put max at 1ghz- on demand
battery at 15% max was at 7xx mhz -batt saver/conservative
temp>115 max was 7xx mhz-batt saver
this yeilded pretty good battery life. i am a heavy data user in a 4g area and on a sense ROM i could easily get 12 hours. pushed it over a day with me trying to get the best battery life possible.
Sounds good. I'm also a heavy user.
Profiles aren't needed with a lot of kernels. Some have built in profiles and in others some governors include profiles such as smartass and interactivex.
The only thing I really use it for is if I overclock, which I rarely ever do, and to change the governor.
Sent from my ADR6400L using XDA App
I use SetCPU with imo's latest kernel and I never let it go above the 1.59GHz mark, but that is where I usually put it when charging via AC.
bamf forever already has the ability to set cpu speeds, its in the bamf settings
It says in the op of bamf kernel thread that bamf setting is unable to retain kernel settings so use setcpu.
What are the difference between matrix kernel bfs and matrix kernel cfs ?? Bfs and Cfs what is better and why?
Bfs seems to work with UI speed better. Meaning what you see directly on the screen will seem faster however when there alot of tasks the rom will lag alot as background tasks are not really concentrated on.
CFS is a completely fair scheduler and every process is treated equally. Everything will seem to be faster and even with lots of multitasking everything will remain smooth.
Its a choice. You choose.
I mighr\t be wrong, so everyone else correct me if i'm wrong
BFS works better when you are using mainly a single app like a game or the browser but CFS works better for most people as it is multitasking. Also BFS can be unstable at times.
Sent from my Nexus S using xda premium
BFS is for gamers. CFS is a more practical use. CFS saves battery, is more stable, and can run more than major apps without lag and choppyness.
Nexus S (GSM i9020a)
AOKP (Build 25)
Eugene's Kernel (Speedy 7)
OC 800/100 (Lionheart)
Live OC (105)
hi,
you will find the answer to your question in this post
http://forum.xda-developers.com/showpost.php?p=22134559&postcount=4
here is the entire thread if you want to read more about governors, etc.
http://forum.xda-developers.com/showthread.php?t=1369817
hope that helps
I have installed rooted stock FP1 with voodoo lagfix and the PBJ 5/24 kernel installed... what else should i do to speed this puppy up....
I would recommend the tweaked rom.
Sent from my handheld Linux computer using electromagnetic radiation.
I recommend not making a new thread just for this.
Sent from my SCH-I510 using xda premium
What launcher is in tweaked Rom.. I love touch wiz... Which is why im asking... Also what the best overclock app to use.. is it setcpu?
Sent from my SCH-I510 using Tapatalk 2
miguel11691 said:
What launcher is in tweaked Rom.. I love touch wiz... Which is why im asking... Also what the best overclock app to use.. is it setcpu?
Sent from my SCH-I510 using Tapatalk 2
Click to expand...
Click to collapse
Wow that's a first but yeah tweaked has tw launcher ad default. Also voltage control is free and works fine for oc/uv.
Sent from my handheld Linux computer using electromagnetic radiation.
SetCPU works for OC/UV, but I find it much less intuitive than Voltage Control.
JihadSquad said:
Wow that's a first but yeah tweaked has tw launcher ad default. Also voltage control is free and works fine for oc/uv.
Sent from my handheld Linux computer using electromagnetic radiation.
Click to expand...
Click to collapse
what is a first.... and does someone have th ebest settings for VC.. i just always overlcocked... never messed with voltage
miguel11691 said:
what is a first.... and does someone have th ebest settings for VC.. i just always overlcocked... never messed with voltage
Click to expand...
Click to collapse
Someone liking TouchWiz
100MHz: -100
200MHz: -100
400MHz: -100
800MHz: -75
1000MHz: -50
Those seem to be good starting points for most people...most phone seem to be stable at that. You can continue experimentally reducing it from there. Some processors handle it better than others (mine can go lower than that pretty much across the board but some can't). The worst that happens is that it's unstable and randomly reboots...you aren't going to permanently hurt it by undervolting.
For higher frequencies, it's more down to experimentation. When you get into the overclocking ranges, it gets really individual to the processor.
wow, I thought nobody liked TouchWiz.
My setup:
-Tweaked ROM
-PBJ kernel (NOT using EXT4...it always makes my phone run very sluggishly)
-The SQL cleanup script found here: http://rootzwiki.com/topic/25072-sqlite3-phone-is-snappier-than-ever/ (I really have nothing but anecdotal evidence but I'm overly convinced that this helps)
-Autokiller memory manager app set to the "Strict" preset. imnuts's new kernel (524) makes similar changes to the values that AKM changes, but "Strict" is slightly higher (60/70/80 vice 50/60/70) and I find it to work better for my phone. The next highest setting seems to be working too much to kill things off, which also slows down the device. This seems to be the happy medium for my phone, YMMV.
-Overclocked to 1.2 using Voltage Control. This doesn't seem to effect my regular operations but I do notice a difference with more intense games (which I don't use very often). I can't go higher than 1.2 and my UV settings are more conservative than those listed in this thread.
-ADWex (the paid one) is the smoothest launcher I've used. I kept hearing this for the longest time but my experience with the trial version was the opposite. Turns out, they are totally different. Give it a shot. ADW has some neat features, too.
-Also make sure you go through and debloat as far as you can. For instance, I only use gmail but the stock email app will always run in the background and eat up RAM...so I uninstalled it. Since I don't use things like the TW launcher or the TW calculator (Realcalc is a better, free alternative), they're gone, regardless of whether it makes a difference to my experience. I'm also a FB user and the official FB app will eat RAM in the background regardless of your sync and alert settings. Friendcaster won't, so I use it (disclosure: I only have the app so I can share things like photos. For status updates and browsing I just use the mobile site in the browser). People will argue, especially when the topics of task killers comes up, that Android handles its own memory management great. It largely does, but this phone is very susceptible to bogging down when you get to the upper limits of RAM usage. That's why I believe changing the minfree values in AKM is so important, an improvement that is maximized by getting rid of superfluous RAM eating processes. Obviously, the more crap you have on your homescreen, the more resources it takes to run your homescreen. Do what you're comfortable with.
My phone is running really well for me right now. I hope you can get the same enjoyment out of yours.
Thanks a lot...
Sent from my SCH-I510 using Tapatalk 2
BleedsOrangeAndBlue took my recommendation to install sqlite but i actually use different OC/UV settings:
100mhz -200
200mhz -150
400mhz -125
800mhz -100 (i'm underclocked at 800 right now and have no issues besides games)
1000mhz -75
1200mhz -50
also I recommend tweaked2.1 because the included tweaktools script comes with a lot of good kernel tweaks like darkly zip-align and renice which speed up application use
also use an auto cache cleaner with the sqlite cleaner because that lowers lag as well
My setup: 100Mhz -200
200Mhz -100
400Mhz - 75
800Mhz -125
1000Mhz - 50
1200Mhz -50
1300Mhz -25
SetCPU: ondemand, sio, up treshold 97, sampling rate 100000
Profiles: screen off- 100 to 200Mhz at 75
In call - 100 to 1000Mhz at 80
Screen unlocked - 100 to 1300Mhz at 99
This works for me. If I put the 200 or 400Mhz any lower my music player stars skipping. Music player mostly uses the 200 n 400Mhz while video n Netflix uses 800Mhz CPU speeds. Its what I noticed. Also am on Tweeked 2.1 with PBJ 524 n this http://forum.xda-developers.com/showthread.php?t=1684997. On Antutu with this setup my score was 3171 I ran it just b4 I posted this. But my best score was 3404 but I forgot what setup I had for that. Anyway this seems to b fast n smooth so I'll stick wirh it, for a while.
p2kmafia said:
BleedsOrangeAndBlue took my recommendation to install sqlite
Click to expand...
Click to collapse
I truly appreciate it, too! It really makes my phone run much smoother and with a widget on my "Utilities" screen for it, I can get back up to speed with one push in less than a minute.
Thanks for the UV settings. I don't underclock, but I do run the conservative governor to stay on lower settings more of the time. I could probably be more aggressive with some of my lower settings, I think I'm going to play around with them now.
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
Lehocki said:
Music player mostly uses the 200 n 400Mhz while video n Netflix uses 800Mhz CPU speeds. Its what I noticed.
Click to expand...
Click to collapse
This could vary based on your governor settings, too. For instance, if I'm using ondemand, Pandora will use my max clock speed most of the time. If I use conservative, it flickers between 200 and 400.
Just putting that out there so you can further optimize if need-be. I've become a bit of a battery fanatic recently.
" This could vary based on your governor settings, too. For instance, if I'm using ondemand, Pandora will use my max clock speed most of the time. If I use conservative, it flickers between 200 and 400."
Yes that is why I have the sampling rate at 100000. It is my stable setting , but the 80000 also works fine and 60000 I also notice some skips but not as much as with the 40000 setting
BleedsOrangeandBlue said:
wow, I thought nobody liked TouchWiz.
My setup:
-Tweaked ROM
-PBJ kernel (NOT using EXT4...it always makes my phone run very sluggishly)
...
Click to expand...
Click to collapse
It's no longer sluggish. The problem has been solved and it's noticeably faster than non EXT4. You should try it.
Ted A said:
It's no longer sluggish. The problem has been solved and it's noticeably faster than non EXT4. You should try it.
Click to expand...
Click to collapse
do you have a link to the fixed version? I did it with the TonsitPBJ ext4 converter package for tweaked 2.1 and it was awful... not to say that its anyone's fault, this is consistent with every ext4 conversion I've ever done.
I posted a method in rootzwiki http://rootzwiki[dot]com/topic/24729-recommend-conversion-to-ext4/
it is a little tedious but if the method you used did not work well I recommend this method because I had no problems during or after the conversion.