Related
I am behind on this OP, I started a business and will fix it up later. Read the post from people to get latest news and opinions..
«»«» «»«» «»«»
I like to jump between kernels. Ok truth be told I jump around builds and 'ROM's all the time too. I test govenors and lockup my phone with OCing all the time. It's like a quest, except I enjoy the journey instead of looking for a holy grail.
So I wanted to start a thread to get people finding and using the different kernels.
This OP will be living!
Devs CORRECT me! Users Debate what you are seeing: PROVE it! Time it! Measure it! Log It!
Anyone Can PM me to change something if I am wrong, and otherwise correct me right in the thread, so we can get the explanations!
(I wish to point out that: all of these devs have both influence on each other and have done independent work. So becareful in stating who fixed what, etc. But also I hope the kernel devs realize most of the population doesnt understand compiled from source vs compiled from a branch, etc.., nor do we always hear the news of who Really resolved something...and go easy on us if we incorrectly identify the brains behind some hotness.)
To my knowledge there are 7 offshoots of the DInc .37 kernel as of 3/14/2011
I will categorize them by their LAST known contributor.
As of 3/14/2011 these are all AOSP, but this thread will gather stats on them all (emphasis on GB+ though)
Slayher No Official Thread
----------------------------------------------
Official CyanogenMod HTC Incredible contributor. His kernel style and concepts are most likely going to be stability and quality because the CM7 for DInc built in kernels will be his or approved by him. He also codes for other CM7 DInc projects, and has really helped Gingerbread on the Incredible be a possibility!
LATEST SPECS ONLY -
(Dismally missing this info, sorry)
2.6.37.3
Deadline I/O
CIFS
Ok Slayhers kernels don't number well, because he puts them in CM7, not always in flashable format. I'll try to take some time and open his kernel fork to get a feel for where he stands.
#C 3/2/11 new kernel... I compiled 3/5/11 and it was 2.6.37.2, not sure what other goodies hes done
#D 3/10/11 2.6.37.3 and deadline I/O
======================================================
NEW KERNEL
userjf (Slayher+AudioBoost) http://forum.xda-developers.com/showthread.php?t=958651
---------------------------------------------
userjf has done us a favor and is recompiling Slayher's DEFAULT kernel with just AudioBoost, everything else is in theory perfectly stock. If you need some more volume out of your phone give his kernel a whirl.
Specs follow Slayher's + Audio Boost, see his thread for more details (Mostly just a download link, as he doesn't mess with the rest of the kernel, and does have a list of acronyms for me to put here )
=============================================================
chad0989 (Incredikernel) http://forum.xda-developers.com/showthread.php?t=848453
----------------------------------------------
Chad is the maintainer of the well know Incredikernel, has many 2.6.32.xx updates, and made a thorough investigation into the CWR touchpoint issue, etc. His kernels were generally Sense. Previously he was coordinating with Invisiblek for AOSP kernels.
I used almost all of Chad's sense Kernels before flipping to AOSP build and picking up with Invis. MY OPINION of Chads and Invis kernels: I found their smartass tuning to be impecable for BALANCING wakeup, batterylife, and everyday performance
[But quality of tuning a kernel can make them 'score low' on things like Quadrant, etc. My personal experience and knowledge of kernels (I am a Windows Engineer...but a kernel is a kernel) tell me it is because the tuning is adapting and not focused on perforance... if you want to test performance, use a HAVSless kernel with performance govenor and probably a BFS scheduler because that one just shoots from the hip ]
LATEST SPECS ONLY - Patched up to 2.6.37.3
Any wake issues should be fixed
Audio boost
http://chad0989.dyndns.org/ 03/06/1...d0989.dyndns.org/sysfsinstructions"]READ THIS
Lowered wifi voltage for increased battery life
If you are a tinkerer and love to tweak your voltages, please PM me the voltage table you settle on as most stable for your phone.
Update on sense: Still working on it. The artifacting issue seems to be more complicated than I originally thought
Fast charging.
Working VPN
SmartAss - you need to set min 128 CPU to get full advantage
Wifi sleep policy fixed
Fixed MultiTouch
Changed to V(R) I/O Scheduler
#6 BETA 2.6.37.2-incredikernel-gb-3062011 [03/06/11] (Has FROYO Version)
#7 2.6.37.3-incredikernel-gb-3132011 [03/13/11] (Has FROYO Version)
=================================================
Invisiblek http://forum.xda-developers.com/showthread.php?t=905873
----------------------------------------------
Invisiblek has probably the most well know 2.6.32 Froyo AOSP kernel. Though this OP is my Opinion, I consider it professional. So without having run the calculations MYSELF, i would still stake that If you searched on AOSP froyo kernel's Invis#28 (FROYO) is probably the most established 2.6.32.x. Any kernel could be created to beat it in a particular category, but it was the best well rounded I have seen for AOSP 2.6.32.xx.
LATEST SPECS ONLY -
invisiblek 2.6.37.2: (still just a modified version of slayher's stock cm kernel.) Changes from stock kernel:
- added smartass governor (max cpu freq on screen off: 384mhz)
- added havs
- fast charge (thanks chad0989!)
- removed debugging options (much smaller kernel size)
#0 2.6.37-nodebug-havs-smartass [Along Time Ago]
#1 invisiblek-2.6.37.2-signed.zip [03/09/11]
=================================================
Cayniarb (Tiamat Kernel) http://forum.xda-developers.com/showthread.php?t=885217
Cayniarb is the well know maintainer of the Tiamat Kernel. I have to admit the only time I used one of his kernels is when he was the other choice for GB that had some backports in it. (told you I like to jump around) I found no issues with it, it ran smooth, had good battery life.
If I had to throw out an OPINION of Cayniarb that i like. If you look at his thread, he is very organized, methotical, and straight up. That is good for the community of users, means he is one to do his homework and release good stuff. He also seems to have no problem pushing the kernel settings and contraints so users have options to lock up their DInc to their hearts content... anyway my thoughts.
Cayniarb likes to list his specs as" rolling information" so I can't translate to 100% latest only, because i could be wrong
- cleanup gitub (cayniarb)
- cleanup code (caynairb)
merged updates/changes from CyanogenMod/cm-kernel - brings 2.6.73.2 and various optimizations for GB 2.3.3 (CyanogenMod Team)
[3/2/11][2.6.37.2 CAYNAIRB says 2.6.73.2 but kernel.org disagrees with him ]
Version 3.1.5
implement fast charging for non-SBC versions (chad0989)
add dedicated SBC defconfigs (cayniarb)
- completely update HAVS implementation (intersectRaven)
- tweak HAVS for stability particular to each platform (caynairb)
- add support for 128Mhz CPU clock speed (cayniarb)
- enable JESUS_PHONE mode by default - enables more OC levels (caynairb) -- (I do not recommend overclocking beyond 1.19Ghz and I will not support any problems caused by overclocking. Each device is unique and may or may not be able to clock to different frequencies)
- implement custom defconfig (cayniarb)
- support for the HTC Evo 4G and XOOM (cayniarb) {DINC USERS PAY ATTENTION TO YOUR DOWNLOAD}
- reapplied custom Tiamat tweaks (caynirb)
•enabled multi-touch support (cayniarb) -- CWM 3.0.0.7 works, 3.0.0.5 and 3.0.0.8 do not
#09 Version 3.1.4 [03/02/11]
#10 Version 3.1.5 [03/05/11]
===========================================
bbedward (Savaged Zen-Inc) http://forum.xda-developers.com/showthread.php?t=938790 - PAGE 11
bbedward seems to have picked up the Savaged Zen kernel from 2.6.32.xx I never used the old kernel. Ok He has his latest in his OP (so don't use the page 11 one). FROYO Kernel Available (at this time it is SBC)
LATEST SPECS ONLY -
- HAVS
- BFS + 2.6.37-ck1 - THIS IS CHOOSE-ABLE VIA WHICH DOWNLOAD YOU CHOOSE
- SBC - THIS IS CHOOSE-ABLE VIA WHICH DOWNLOAD YOU CHOOSE
- SLQB Slab Allocator
- MM Preempt 2.6.37 patchset
- Deactivate Pages 2.6.37 patchset
- I/O Less Dirty Throttling 2.6.37 patchset
- Smartass+Savaged-Zen governors
- Tweaked conservative+ondemand governors
- Fixes from CodeAurora
- Tweaks from IntersectRaven
- Froyo compatible build option
- BFS and memory tweaks
- ZRAM Support (new name for compcache/ramzswap)
#1 2.6.37 Savaged-Zen-INC v0.0.1 (CFS/BFS+AVS+SBC+HAVS) - Page 11
#2 2.6.37 Savaged-Zen-INC v0.0.1 (STILL 0.0.1, but now in the OP with updates..please consider this one the most current)
============================================
NEW KERNEL
mwielgosz (Savaged-Zen-INC noSBC) http://forum.xda-developers.com/showthread.php?t=976580
We have been graced with a new kernel. mwielgosz picks up with a dedicated thread for NOSBC Savaged-Zen
I have not given it a whirl because of RC2 and all my hacking i do for my own comforts, i "got" to redo..., so without further ado:
LATEST SPECS ONLY -
BFS OR CFS
- HAVS
- BFS + 2.6.37-ck1 - THIS IS CHOOSE-ABLE VIA WHICH DOWNLOAD YOU CHOOSE
- SLQB Slab Allocator
- MM Preempt 2.6.37 patchset
- Deactivate Pages 2.6.37 patchset
- I/O Less Dirty Throttling 2.6.37 patchset
- Smartass+Savaged-Zen governors
- Tweaked conservative+ondemand governors
- Fixes from CodeAurora
- Tweaks from IntersectRaven
- Froyo compatible build option
- BFS and memory tweaks
- ZRAM Support (new name for compcache/ramzswap)
Watch your downloads! The download page has multiple devices, dont screw up!
#1 Savaged-Zen-INC [2.6.37] noSBC [03/02/11]
---------------------------------------------------------------------------
Kernel Devs I haven't seen, please keep me posted if they popup with a kernel
HeyItsLou
Ziggy
KiNgxKernel
Hydra-kernel
Adrynalyne
Others
I would like to start gathering Kernel Terms here. Please post the definitions of the most common and not so common Terms or Questions you hear out in the wild and I'll put them in the "Second Post"
=============== TO DO Answer What are advantages of this thing over that... ============
--------------------------------
CPU SCHEDULERS
O(1) scheduler - Outdated by the CFS Scheduler
Completely Fair Scheduler (CFS)
++++++++ WHY I WANT THIS? ++++++++
The Brain **** Scheduler (or BFS)
++++++++ WHY I WANT THIS? ++++++++
DISK I/O Schedulers
Budget Fair Queuing IO Scheduler (BFQ)
++++++++ WHY I WANT THIS? ++++++++
Completely Fair Queuing (CFQ)
++++++++ WHY I WANT THIS? ++++++++
V(R) I/O Scheduler
++++++++ WHY I WANT THIS? ++++++++
Deadline IO
miatamx said:
The goal of the Deadline scheduler is to attempt to guarantee a start service time for a request[1]. It does that by imposing a deadline on all I/O operations to prevent starvation of requests. It also maintains two deadline queues, in addition to the sorted queues (both read and write). Deadline queues are basically sorted by their deadline (the expiration time), while the sorted queues are sorted by the sector number.
Before serving the next request, the Deadline scheduler decides which queue to use. Read queues are given a higher priority, because processes usually block on read operations. Next, the Deadline scheduler checks if the first request in the deadline queue has expired. Otherwise, the scheduler serves a batch of requests from the sorted queue. In both cases, the scheduler also serves a batch of requests following the chosen request in the sorted queue.
By default, read requests have an expiration time of 500 ms, write requests expire in 5 seconds.
The kernel docs suggest this is the preferred scheduler for database systems, especially if you have TCQ aware disks, or any system with high disk performance[2].
Click to expand...
Click to collapse
====================================
MODULES YOUR KERNEL MAY OR MAY NOT HAVE (MODULES CAN BE COMPILED INTO KERNEL, or a .ko file)
BCM4329.ko BroadCom One-shot wonder radio chip: BCM4329 - Low-Power 802.11n with Bluetooth® 2.1 + EDR and FM (Tx and Rx)
cifs.ko ability to connect directly to Windows computer: Server Message Block (SMB), also known as Common Internet File System (CIFS) mainly used to provide shared access to files, printers, serial ports, and miscellaneous communications between nodes on a network. Most usage of SMB involves computers running Microsoft Windows, where it was known as "Microsoft Windows Network"
IPTABLES - Linux Firewall (if it has DNAT, it can be part of an integral part of a proxy also) Mostly compiled these days, but if you don't have it you can't do IP Firewall like Droidwall.
TUN - Tunneling, generally compiled in, VPN software needs this.
daftlush said:
http://forum.xda-developers.com/showthread.php?t=976580
In that thread I found...
SBC - Superior Battery Charging. Google "trickle charging" for explanation.
HAVS - Hybrid Adaptive Voltage Scheduling. Voltage drops as CPU speed goes down in order to conserve power."
Click to expand...
Click to collapse
NOTE FROM OP: Is There a negative to HAVS? If so explain? If not why does slayher, who seems to take the time to do a lot of investigation still not include?
=====================================
OC - Over Clock(ing)(ed), using your operating system [Or Motherboard Firmware] to force the CPU or BUS above manufacturer recommendations. I have over-clocked around 100 desktops, and I goof off with my Android all the time in this area.
When you see a Device with a certain Hertz (Hz) or more likely Megahertz (MHz) this is most likely talking about the CPU multiplier Multiplied by the BUS speed (measured in 'heartbeats'... sortof... per second) In general the days of actually changing the the CPU multiplier are gone (AMD used to be able to), so if a device motherboard 'pulses' at 266Mhz and the CPU Multiplier is 3.5, we often say its a 933 Mhz device. Manufacturers build Chips (CPU, GPU, Memory, and I/O bridges (Chipsets) in huge batches. [I grew up 5 miles from Intel in Rio Rancho, New Mexico ] They spot check about 10% of the actual chips, and whatever is the maximum heat, volts, etc they can handle, or tolerate, before becoming damaged or unusable: The whole batch is rated at that speed! (This is important because many chips can FAR Exceed that without ANY VOLTAGE increase at ALL, and some can barely meet that at all (Meet the Intel Centrino's CPU's that failed level 1 or 2 Cache checks, disabled the Cache, and sold as cheap and neutered CPUs))
Over Clocking is when the user attempts to exceed the rating they were told the chip could handle: We can increase that by pushing the motherboard to 'beat' faster. The overall effect is the all data is acted upon, move to memory, moved to i/o [like disk or sound], etc faster, the NEGATIVE is CPU, GPU, Memory, or Chipsets often have brownouts: they need more electricity to operate faster. So many motherboards allow you to tweak the POWER to CPU and Memory, even some I/O Chips. The negative of more power is MORE HEAT. So eventually it is IMPOSSIBLE to maintain stability because the heat cause the chips to shut down. Hence high air cooling, and water cooling, and such. So for instance I can push a 2.4Mhz rated chip to 3.2Mhz or 1.75x its rated capacity IF I am willing to freeze the motherboard in clean nitrogen (or you would be amazed what you can do in motor oil, but i digress)
UC - ?
UV - ?
OCUV -?
GOVERNOR - ?
DEFINITION OF THE GOVERNORS - Thanks to daftlush
daftlush said:
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings of SetCPU), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace - A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor."
From SetCPU FAQ.
SavagedZen governor is just a modified smartass, should minimize or eliminate wake up issues, perhaps a bit snappier.
Click to expand...
Click to collapse
Interactive Quoted from http://android.doshaska.net/interactive
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Laymans terms: When load starts, it ramps up CPU based on measuring how much IDLE cpu is not used. Versus competing for CPU to measure what everyone else is using. So it keeps increasing speed until the Idle bucket stop being hungrily emptied...thus measuring need without interrogation any process.
Smartass and SZ Governers are Special because they have settings controllable by the kernel Dev. Simply stated they have a range, set by the kernel dev, of MinX to MaxX CPU while screen is off and a different MinY to MaxY while the screen is on. It then operates much like Interactive (however the code was done from scratch)
Quoting http://www.ziggy471.com/2010/11/07/smartass-governor-info/ who was Quoting http://forum.xda-developers.com/showthread.php?t=730471
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!
setCPU, especially in relation to Profiles
nandroid in relation to /boot
---- UNSURE WHERE TO CATEGORIZE ----- This is a file I/O, memory I/O, or DB I/O concept... I'm not sure how to tie it to kernel
"In computer Operating systems, Read-copy-update (RCU) is a synchronization mechanism implementing a kind of mutual exclusion[note 1] which can sometimes be used as an alternative to a readers-writer lock. It allows extremely low overhead, wait-free reads. However, RCU updates can be expensive, as they must leave the old versions of the data structure in place to accommodate pre-existing readers. These old versions are reclaimed after all pre-existing readers finish their accesses."
This should be stickied.
Edit: Suggestion for renaming the title: drop "HTC" and leave it as simply "The Incredible List of .37 Kernels"
just a thought
Hey bud you forgot Tiamat, i see that you have it included in your mirrors but don't have it listed here, still thanks for the post, makes getting at all the kernels much easier
poetzmij said:
Hey bud you forgot Tiamat, i see that you have it included in your mirrors but don't have it listed here, still thanks for the post, makes getting at all the kernels much easier
Click to expand...
Click to collapse
was still writing was a long post and didn't want to lose anything...
Heyitslou has a kernel thread you should check out. He has a number of them listed and some of the Rom dev's are including his in their work.
spence341 said:
Heyitslou has a kernel thread you should check out. He has a number of them listed and some of the Rom dev's are including his in their work.
Click to expand...
Click to collapse
Does he have a 2.6.37.x Kernel?
Thanks for compiling this list!
Sent from my CM7 Incredible.
galaara98 said:
Does he have a 2.6.37.x Kernel?
Click to expand...
Click to collapse
Nope, sorry it s 2.6.32.xx.
In the OP, I'd throw up a link to the respective thread under each individual kernel. Easier to find more info about each kernel.
Just to add to the editorialization, Invisiblek's kernels were regarded as possibly the cream of the crop for AOSP Froyo kernels overall, with a superb balance of performance and battery. Over on the MIUI forums, the #28 was by far the most popular kernel choice to go along with that ROM, and his GB kernel pairs up with CM7 beautifully.
Reopened thread per agreement with OP to increase traffic to Developer's work/thread with providing forum thread link instead of external link. Will continue to moderate as usual.
Incredible list of 2.6.37.xx kernels, Back in Business
Ok, I fixed up the OP... I am happy for now... probably some grammar and typos. But I think this is a great start. Let me know guys!
Aaron
Thanks for this. I was starting to lose track of all the 37.xx kernels.
andrew8806 said:
Reopened thread per agreement with OP to increase traffic to Developer's work/thread with providing forum thread link instead of external link. Will continue to moderate as usual.
Click to expand...
Click to collapse
Seems the sensible solution
galaara98 said:
Ok, I fixed up the OP... I am happy for now... probably some grammar and typos. But I think this is a great start. Let me know guys!
Aaron
Click to expand...
Click to collapse
Kudos. Lookin' good so far.
Yes thanks so much for organizing and explaining these to the best of your knowledge
Now that it has links to all the threads where people can get much more info on the kernels, I linked it to the CM7 Nightly Thread (if that's ok with you, if not, let me know and I'll remove it). Noticed you didn't have the link to your mirror where people can download it on the OP. Was this intentional?
So whats everyones favorite so far? im running the invisiblek kernel, and would like to say it has been the best kernel so far.
It should probably be noted that these are AOSP kernels....not Sense....otherwise a good addition.
cl1ckclack said:
So whats everyones favorite so far? im running the invisiblek kernel, and would like to say it has been the best kernel so far.
Click to expand...
Click to collapse
Been taking Chad's for a test run these last few days.
IMO it's pretty much between Chad's and Invisiblek. The Savaged kernel ANNIHILATED my battery life, and Tiamat just won't turn the screen on unless I hit the power button ten times.
Hi everyone!
I have one question, what is the most stable config. of your device including OC of the CPU and GPU, overvolting and undervolting, governors and VM heap size?
I have CM9 ICS 4.0.3. with devils kernel, in NSTools enabled deep sleep, OC-ed to 1350MHz CPU and 10% LiveOC GPU, Voltages are default, RAM is set to Hard gaming with 64Mb of VM in RAM Manager PRO. Governors are deadline and ondemand (I´ve had cfq and smartassv2 before).
What is most interesting to me is voltages..as I´ve read somewhere that that is the most important part in stability of system running OC-ed settings. How can you accomplish that? Tell me your examples.
Hi there, I use last nightly cm9, sgs is OC till 1,3 and i think it's perfect. Everything is open quick, all games are work stable and fast without freezes. I don't see difference between 1,3 and 1,5 OC. Regards !
Hi, thanks for your reply!
I would disagree, there is a huge difference between 1.3 and 1.5 as it is between 1.3 and 1GHz in the way of speed and handling heavy staff. What is different is that your device heat rises much faster on higher clocks than of those default.
My main concerns about this is because I want to be able to play all the new games (to be specific: Nova 3 , I can play multiplayer but single player allways crashes after few seconds)..and so that is why I wanted to share my settings with all of you, and you also share your settings.
The key to higher clocks speed is voltages, but I have no knowledge about it.
When I normal use phone I don't see any difference between 1,3 and 1,5 maybe it's my sgs charm It is as quickly as possible. When I oc to 1,5 it often freez
Well, that depends on what you mean by "normal use" ..but, no doubt that your phone or any other is much smother when OC-ed.
After getting a little annoyed at the runty, poorly mapped-out, scratchy thicket of real and imagined performance tweaks, I decided to embark on a semi-long term project to determine what's real and what's "zomg mega-booster performance pills".
First project was to evaluate existing performance options on stock CM10 for actual gains using experimental design. (tl;dr: for those geeky enough to want to know, it was a main effects only d-optimal design with 32 design points for the 16 parameters listed, including several lack-of-fit and pure-error replicates. I could go on, but do you really want me to?). I ended up with a list of 16 parameters all together, from the Developer Options and Performance settings, based on their showing up in various performance tweaks discussions.
The main challenge was finding a way to measure actual performance instead of perception. I settled on several benchmarking tools: Antutu, Quadrant, SQL Benchmark, and Chainfire's benchmarking app. One of the parameters being tested ("don't keep activities") actually breaks Antutu at the graphics testing step, so I'm not reporting anything from Antutu.
All told, out of the 16 parameters tested, only 9 showed any kind of effect whatsoever, and combining best settings for all 9 simultaneously, total performance only boosted by ~20%, of which fully half was due to switching max speed from 1000 to 1100. this means the other 8 settings combined for a total boost of ~10%, meaning individually they're peanuts. The remaining 7 settings that showed no effect are only so much fluff and unlikely to do a thing for you performance-wise.
Results are summarized below for your reading/teeth-gnashing pleasure:
Max Speed (1000 versus 1100): Very clear, notable difference between the two settings on all benchmarks. This is the expected result, about 10% improvement in all benchmarks on average. Recommendation: set max speed at 1100.
Governor (convservative vs interactive vs ondemand): This only had any impact on Quadrant benchmark, no other benchmarks appeared to care. In Quadrant, conservative was the worst overall, while interactive provided an ~ 5% boost and ondemand gave ~6% boost. Recommendation: use ondemand.
Scheduler (BFQ, CFQ, noop, deadline): I don't know what schedulers do or the differences between these settings, but the only place they had any effect at all was in the SQL benchmark. There were clear differences here though: BFQ was by far the worst. CFQ and deadline were about the same with a 17% increase in SQL activity performance. noop was the best with ~ 20% increase in SQL activity performance. Recommendation: use noop. [update: some have reported stability issues with noop. If thus us the case for you, CFQ would be the next best choice]
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
16-bit transparency (off or on): Turning on the 16-bit transparency setting gave a smallish 3% boost to Chainfire's java benchmark. It did not have a measureable effect anywhere else, and I did not visually see any differences anywhere during testing. Recommendation: turn on 16-bit transparency.
Kernel same-page merge (off or on): This had a *negative* effect when turned on, resulting in a 1% performance hit on Chainfire's native benchmark. It did not have any measurable effect anywhere else. Recommendation: Keep off.
Don't keep activities (off or on): This was very problematic: it provided a distinct improvement in quadrant score (+8%) when turned on, but behaved poorly with other apps (Antutu being one). Since it didn't seem to help anywhere else outside of Quadrant and didnt' play well with others, recommendation is to keep off:
The following list are the settings that had no measureable impact anywhere. Any attempt to claim they have "zomg" status should be summarily whipped with placebo pills, or else they should let me know the exact details in which they supposedly work and I can test.
Placebo hall of shame:
Surface improvement (since it had no effect anywhere, why not just set it on banding/blur and have the best pictures?)
Background process limit
Disable HW overlays
Force GPU setting
Any of the animation scale settings (although they look snappier at lower settings, so it at least *feels* faster)
minimum speed (seriously? people think this has an effect? keep at 300 for best battery life)
Allow purging of assets
Hope you like this, y'all! Let me know if there's any other mad-scientist experiments you'd like to see.
Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.
Re: [CM10] NC Performance (and) Placebos
NCKevo said:
Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.
Click to expand...
Click to collapse
Thanks for the link. Very informative.
How familiar are you with factorial designs? All parameters were tested simultaneously in such a way that their individual effects can be partitioned out mathematically. That's what allows me to test all those settings with just 32 runs and still get solid estimates of their effects, and more importantly, the amount of variation around them (a requirement for distinguishing real effects from noise).
I suggest googling "factorial design of experiments" if you're interested.
skwalas said:
Let me know if there's any other mad-scientist experiments you'd like to see.
Click to expand...
Click to collapse
Here are some others you could try gauging:
Seeder
http://forum.xda-developers.com/showthread.php?t=1987032
V6 Supercharger
http://forum.xda-developers.com/showthread.php?t=1191747
Lagfix
http://forum.xda-developers.com/showthread.php?t=2104326
OOM/Sysctl tweaks
http://forum.xda-developers.com/showthread.php?p=34123854#post34123854
http://forum.xda-developers.com/showthread.php?p=34448792#post34448792
Re: [CM10] NC Performance (and) Placebos
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!
skwalas said:
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!
Click to expand...
Click to collapse
Have only used V6, from my experiences, restoring a Nandroid or flashing a new nightly will clean out everything it changes other than the files you store on the SDcard. This post details how I set it up http://forum.xda-developers.com/showpost.php?p=34991382&postcount=1234
I never really noticed a huge performance boost from V6, it did reduce the lag that was in the Beta's and early nightlies, mostly seemed to keep memory available and avoid the lag issued in the early builds. Have not used for the last few weeks since performance has improved on the newer builds.
Re: [CM10] NC Performance (and) Placebos
I set all recommendations. I get back to you in a couple of days. I am running 20130120 nightly
Sent from my NookColor using Tapatalk HD
Thank you!
Thank you for your measured and logical approach and recommendations! It is appreciated. I have experimented a little with the third party tweaks and haven't found any that fascinating, honestly.
When I install CM10.1, I also flash a script I made to customize to my preference and delete stuff I don't use like language modules, ringtones, quicksearch, boot animation, etc to free up some RAM. Between that and killing memory hungry apps when I'm done, my old Nook is still holding on reasonably well.
Re: [CM10] NC Performance (and) Placebos
Skwalas:
Got to tell you, your suggestions on settings are paying off. My nook is smooooooth. Is working ok there is sometime that lag liittle bit, but my p3113 also doing the same. I will stay with this 0120 nightly for a while with your settings on perfomance. .
I will report later how i am doing
Sent from my NookColor using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
performance is ok....
Sent from my NookColor using xda app-developers app
Re: [CM10] NC Performance (and) Placebos
Sometimes mook freezes and I have to leave it until it settles. The rest of the time works good
Sent from my GT-P3113 using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
Lakland said:
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD
Click to expand...
Click to collapse
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.
Re: [CM10] NC Performance (and) Placebos
skwalas said:
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.
Click to expand...
Click to collapse
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD
Lakland said:
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have had erratic behavior from schedulers also, especially BFQ, NOOP is not bad, but have had better luck with CFQ.
skwalas said:
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
Click to expand...
Click to collapse
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).
khaytsus said:
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).
Click to expand...
Click to collapse
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?
skwalas said:
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Good question, I'd think it'd require some way to switch activities around and somehow measure their switch rates, but the environment would be quite difficult to keep consistent.
BTW thanks for the scientific work on this stuff, MUCH better than "OMG THIS TURNED MY TABLET INTO A UNICORN" posts we see a lot on tech forums.
skwalas said:
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Since it would help most when memory is low (like it ever isn't), running two memory hogs simultaneously should show an effect if there is one. A custom memory-hog app built under two different names, perhaps?
I have a shell script that creates a swapfile and enables its use that would also be well tested this way, since zram creates an in-memory swapfile. I was never able to see any tangible results except for the output of "free", so I don't use it anymore, and haven't tried it under CM10.1.
Sent from my NookColor using xda premium
Hi guys,
I'm wondering what the best governor and scheduler combination for the XZ on stock 4.2.2. firmware with stock kernel would be?
The reason I'm asking this is, ever since I've upgraded to 4.2.2. I've been experiencing some kind of lag and stuttering when scrolling through album, in websites or apps like instagram, twitter or other lists like under "running apps". I don't think this was there on 4.1.2 or at least not that much. Strangely enough, this stuttering seems to appear mostly when scrolling up and down, so only vertical scrolling seems to be affected, not sideways!
I'm rooted and with locked bootloader + dual recovery. I don't wanna install a custom kernel and also I don't want the battery to empty a lot faster or the phone become hotter just for the sake of less stuttering, if that's possible at all. Performance should stay the same, but stuttering be minimized.
I'm using setcpu. The standard governor is "interactive" and scheduler is "cfg". There are other governors available, which are: "performance" (which makes the phone run at full speed all the time, so certainly not the one I want to use), "ondemand" and a new one "msm-dcvs" which I've never seen or heard of before. The other schedulers are: "noop" and "deadline".
Would be grateful for tips or what else can be done to minimize the stuttering, aside from changing governors and schedulers.
drsoran2 said:
Hi guys,
I'm wondering what the best governor and scheduler combination for the XZ on stock 4.2.2. firmware with stock kernel would be?
The reason I'm asking this is, ever since I've upgraded to 4.2.2. I've been experiencing some kind of lag and stuttering when scrolling through album, in websites or apps like instagram, twitter or other lists like under "running apps". I don't think this was there on 4.1.2 or at least not that much. Strangely enough, this stuttering seems to appear mostly when scrolling up and down, so only vertical scrolling seems to be affected, not sideways!
I'm rooted and with locked bootloader + dual recovery. I don't wanna install a custom kernel and also I don't want the battery to empty a lot faster or the phone become hotter just for the sake of less stuttering, if that's possible at all. Performance should stay the same, but stuttering be minimized.
I'm using setcpu. The standard governor is "interactive" and scheduler is "cfg". There are other governors available, which are: "performance" (which makes the phone run at full speed all the time, so certainly not the one I want to use), "ondemand" and a new one "msm-dcvs" which I've never seen or heard of before. The other schedulers are: "noop" and "deadline".
Would be grateful for tips or what else can be done to minimize the stuttering, aside from changing governors and schedulers.
Click to expand...
Click to collapse
If I'm correct the governors only work for custom kernels and not for stock kernels. (I could be wrong though)
Anyways I guess the choice should be between Interactive and OnDemand, which one is better??? Good question!
Dsteppa said:
If I'm correct the governors only work for custom kernels and not for stock kernels. (I could be wrong though)
Anyways I guess the choice should be between Interactive and OnDemand, which one is better??? Good question!
Click to expand...
Click to collapse
That would not make much sense, I mean they are there to be selected and it's only three governors and schedulers to chose from. Custom kernels have much more than that. Just looking for a way to reduce those stutters.
drsoran2 said:
That would not make much sense, I mean they are there to be selected and it's only three governors and schedulers to chose from. Custom kernels have much more than that. Just looking for a way to reduce those stutters.
Click to expand...
Click to collapse
And they are working on stock kernel
Sent from my C6603 using xda premium
Hi guys!
I'm on eXistenZ 3.0, and everything's perfect, but i wanted to know how can i use the 'overclocking' settings? Do you know an optimal frequency?
Or what exactly can i do with that?
I'm just curious
spicx212 said:
Hi guys!
I'm on eXistenZ 3.0, and everything's perfect, but i wanted to know how can i use the 'overclocking' settings? Do you know an optimal frequency?
Or what exactly can i do with that?
I'm just curious
Click to expand...
Click to collapse
Interesting that you should ask. Coming from windows/intel chips, where overclocking is going beyond the highest value set at the PC bios to speed up the computer (thus generating more heat), I come to understand that "overclocking" in the android world is either to increase the lowest setting or decrease the highest setting for optimal performance (basically to save battery or reduce heat). In android, there is no way to increase the set highest value that I can see...
Of course, I stand to be corrected by long time android users here (I just came into android in Feb this year)
spicx212 said:
Hi guys!
I'm on eXistenZ 3.0, and everything's perfect, but i wanted to know how can i use the 'overclocking' settings? Do you know an optimal frequency?
Or what exactly can i do with that?
I'm just curious
Click to expand...
Click to collapse
Do you want to Overclock the SoC itself or tweak the other options such as the Low Memory Killer, SD Card Read Ahead, etc?
Since I'm running the stock kernel (my bootloader is relocked), I cannot overclock the SoC
I usually use:
Governor: ondemand
I/O Scheduler: deadline
But
Governor: interactive
I/O Scheduler: deadline
Would sometimes deliver higher benchmark scores
With regards to the Low Memory Killer, I'm satisfied with the stock settings but try to experiment with the other presets as you please.
As with the SD Card Read Ahead, I've selected 2048kb as it is said to be the optimal value. You can try to use benchmarks to determine what works best with your sd card.
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
spicx212 said:
Hi guys!
I'm on eXistenZ 3.0, and everything's perfect, but i wanted to know how can i use the 'overclocking' settings? Do you know an optimal frequency?
Or what exactly can i do with that?
I'm just curious
Click to expand...
Click to collapse
Also, if you really want to overclock your SoC; you can choose to unlock your bootloader and flash DoomLord's DoomKernel. :3
Remember to backup your TA Partition first before doing this step as unlocking your bootloader WILL cause you to lose DRM Keys (bye bye Bravia Engine 2 and Download Music Info). You can search for BackupTA 9.10.
DoomKernel allows you to overclock up to 1.8GHz, provides you with a plethora of Governors, Schedulers, and other performance enhancements. e.g. Samsung exFAT Driver, etc.
TechKiel said:
...
DoomKernel allows you to overclock up to 1.8GHz, provides you with a plethora of Governors, Schedulers, and other performance enhancements. e.g. Samsung exFAT Driver, etc.
Click to expand...
Click to collapse
I see - there is a real 'overclocking' after all...
Thanks.
Everything is a bit new to me, new android user too. (i'm on locked bootloader)
Yeah i saw that i can maximize the current minimal settings, and minimize the maximum settings. I tried to increase a bit the minimum settings and did a benchmark, and i saw a difference already (i did 384 MHZ --> 584MHZ). But i dont want my phone to overheat or to decrease battery life.
The other options, i must admit i dont understand a thing, so what do you suggest to improve battery life for example, (or optimal settings if there are)?
spicx212 said:
Everything is a bit new to me, new android user too. (i'm on locked bootloader)
Yeah i saw that i can maximize the current minimal settings, and minimize the maximum settings. I tried to increase a bit the minimum settings and did a benchmark, and i saw a difference already (i did 384 MHZ --> 584MHZ). But i dont want my phone to overheat or to decrease battery life.
The other options, i must admit i dont understand a thing, so what do you suggest to improve battery life for example, (or optimal settings if there are)?
Click to expand...
Click to collapse
I would suggest:
Min: 384
Max: 1512
Governor: ondemand
Scheduler: noop
SD Card Read Ahead: 2048kb
As for the other settings, it's better to leave them untouched.
For additional battery saving,
Install "Greenify" to hibernate power hungry bg apps such as facebook.
Also, turn off location services and auto-sync if you don't utilize them.
You can also go further by using "BetterBatteryStats" to monitor which apps are sucking your battery.
TechKiel said:
I would suggest:
Min: 384
Max: 1512
Governor: ondemand
Scheduler: noop
SD Card Read Ahead: 2048kb
As for the other settings, it's better to leave them untouched.
For additional battery saving,
Install "Greenify" to hibernate power hungry bg apps such as facebook.
Also, turn off location services and auto-sync if you don't utilize them.
You can also go further by using "BetterBatteryStats" to monitor which apps are sucking your battery.
Click to expand...
Click to collapse
THanks a lot dude, i'm gonna try it!
btw if i set max to 1512 Mhz, my performance (while gaming for example) will decrease right?
spicx212 said:
THanks a lot dude, i'm gonna try it!
btw if i set max to 1512 Mhz, my performance (while gaming for example) will decrease right?
Click to expand...
Click to collapse
Yes. But it shouldn't be that much.
Using noop as your I/O Scheduler results to faster SD Card Reads while reducing CPU Cycles, reducing battery drain. Reduced CPU Cycles would seem to affect performance though.
D:
No problem. Just click thanks.
am using "rom tool box" on my XSP (rooted, .201, stock rom, c5303)... when setting up CPU speed, after reboot, settings are back to standard?!
any idea why'S that, or is it normal?
regentonne said:
am using "rom tool box" on my XSP (rooted, .201, stock rom, c5303)... when setting up CPU speed, after reboot, settings are back to standard?!
any idea why'S that, or is it normal?
Click to expand...
Click to collapse
Check out for other apps or init.d scripts that may have configured Processor settings during boot time.
TechKiel said:
Check out for other apps or init.d scripts that may have configured Processor settings during boot time.
Click to expand...
Click to collapse
sry, but, how to do that Oo