Over Clock Options - Eee Pad Transformer Q&A, Help & Troubleshooting

Running kernel that OC's - can someone explain what the different options do? If set at conservative or performance what happens while using the tablet? How about interactive.....etc??

Performance gov keeps the cpu at top clock speed
Conservative keeps it low
Interactive runs it at a variable speed automatically setting the clock as needed (best option atm)
On demand also runs at a variable speed but has more options for manual control
Powersave wacks the tf into sleep mode faster than all the other gov's
For IO i set blck0 to 512kb read ahead and blck1 to 1024kb
For IO schedular depending on what kernel your'e running the best options are BFQ SIO VR NOOP in that order (personal experience)
VM settings oom grouping's and other bits you probably wont want to play with till later on
Have fun !!!!
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel

can we do this on a none routed transformer?

PL-S said:
can we do this on a none routed transformer?
Click to expand...
Click to collapse
its rooted and No you can not

See here;
http://www.everythingabouttablets.net/2012/01/22/android-overclocking-governors-explained/
Although there are some frequency governors not listed they are usually variants of these with minor tweaks, once you understand these you can google the other ones (like lagfree, for example) that aren't listed and it should be easy to understand.
Also, check out the link in my signature if you are still a noob at Android and the TF101
(Should have read the original question, I realize this is about two weeks out of date now that I posted it lol)

Related

[KERNEL][GB SENSE][05/10-2011]tristan202-gb-desire v05 (OC/UV/HAVS/BFS/CFS/V(R))

This is my personal kernel, that I decided to release now. It is extremely lean to minimize memory footprint and optimize perfomance. It is built from HTC official GB sources, with some of bananacakes, siberes, snq-s and my own patches. I intend to keep it at 2.6.35.10, as I see more problems than advantages in upstreaming to newer revisions.
Features:
-Hybrid adaptive voltage scaling (HAVS)
-V(R) i/o scheduler
-TinyRCU
-Overclock up to 1190
-Undervolt
-Ondemand, Virtuous and SmartassV2 governors (I use Virtuous for wake and Ondemand for sleep)
-AXI
-Lowered WiFi voltage
-EXT4 support
-snq-'s Autobrightnessmod (Enable all 10 levels)
-sibere's Battfix
-USB fast charge
-Optional 2 way call recording
-Hardcoded SD Speed Patch to 2048. No need for init script anymore
-Hardcoded highly tweaked Lowmemkiller (3584,4096,8192,20992,23040,25088). Throw away Autokiller and/or init scripts.
To make it more lean, I have disabled EXT2 support. SWAP isn't supported either, as I find it completely useless.
I have added CIFS and TUN as modules. To install, download and extract the file and push it to /system/lib/modules like so:
Code:
adb remount
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
And add the following line to your modules init script:
Code:
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/tun.ko
The kernel comes in 2 flavors. BFS and CFS. Differences between them are here:
BFS - Brain F**k Scheduler
The scheduler essentially handles CPU resource allocation. It controls how the CPU ramps up in frequency and down again when not needed. The BFS version is generally very snappy (possibly more so than CFS) but is an older scheduler. It is designed to minimise latency on low spec'd machines (desktops generally)
Further details here:
http://en.wikipedia.org/wiki/Brain_****_Scheduler
CFS - Completely Fair Scheduler
This particular scheduler is newer than BFS. It is designed to make the best of High end machines (desktops again). In the early days, CFS seemed much laggier than BFS but now there is not too much in it. I am quite happily running a modern CFS kernel and I don't experience any lag issues.
Further details here:
http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
I am aware that the BFS version throws some errors about 'bad cgroup data' in logcat, I haven't been able to get rid of them. I have disabled everything cgroup related in the kernel, but vm still throws the errors. Don't know why. Doesn't seem to impact performance.
I personally use the BFS version, as I find it somewhat faster than the CFS one. I have absolutely no wake lag, and I get good battery time.
Thanks go out to: snq-, bananacakes, sibere, tobi01001, thalamus, eviollet. If I forgot anyone, pls inform me.
CHANGELOG:
V05:
XZ compression
Fixed Wifi sleep
Tweaked OJ settings for better responsiveness (bananacakes)
Changed ramdisk compression method to gzip.
Rebuilt tun.ko and cifs.ko
v04b:
Fixed WIFI. (My bad. Forgot to adapt install script after including new ramdisk.)
v04:
Added Lowmemkiller tweak to ramdisk (3584,4096,8192,20992,23040,25088) No need for Autokiller or init scripts anymore. Over time I will move more tweaks into the ramdisk to minimize the need for init scripts.
Updated BFS to 0.406
Reverted battery gauge polling to 60 secs.
Added Virtuous governor. Virtuous is a highly tweaked SmartassV2.
Removed Lagfree governor again, as I found OndemandX better.
v03:
Hardcoded SD Speed Tweak to 2048. No need for init script anymore
Made 2-way call recording optional. Check downloads
Reduced battery gauge polling from 60 to 5 secs. (Untested)
A few bits more, can't remember it all.
v02:
Added Lagfree governor. Gives me a wee bit better battery, but sometimes lags when listening to music. Maybe I'll remove it again. Tell me what you think.
Added a minor change from tobi01001 to the lightsensor driver. Details here
Hopefully fixed USB fast charge.
Compiler optimizations
Link to my github: https://github.com/tristan202
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
k3lcior said:
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
Click to expand...
Click to collapse
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
I'll give you feedback soon.
Thx and congratz.
Tapatalking.
tristan202 said:
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
Click to expand...
Click to collapse
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
beanbean50 said:
is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
Just ask HTC they know everything about your phone
beanbean50 said:
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
tristan202 said:
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
Click to expand...
Click to collapse
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
ziggy1001 said:
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
Just ask HTC they know everything about your phone
Click to expand...
Click to collapse
haha...!
Yes, HTC, Google and every other Tom, **** and Harry...
beanbean50 said:
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Click to expand...
Click to collapse
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
tobi's autobrightnessmod is included. Adding to OP.
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
tristan202 said:
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
but we only have the first two governors to choose from, Interactive is not an option (in setcpu) or am I being stupid as per usual ...?
is usb fast charge enabled?
ZeGuitarist said:
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
Click to expand...
Click to collapse
where can I find the patched framework ?
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You have to patch your own framework-res
Tapatalking.
ironjon said:
You have to patch your own framework-res
Tapatalking.
Click to expand...
Click to collapse
can you guess my next question ...? hehe
Here you go i like helping the aged especially when, poor eyesight, liver damage, and tropical diseases have taken their toll
[How to] Adjust auto-brightness on GB Sense ROM
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You can't find it anywhere, you need to patch your own framework. The framework apk differs for each ROM, and contains each individual user's UOT kitchen mods too... So to be safe, you really shouldn't use someone else's framework.
Anyway, here's how to do it:
http://forum.xda-developers.com/showthread.php?p=17713587
It's pretty easy, as long as you know where your ROM's framework apk is (in internal /system, or in /sd-ext). Also, the thread suggest you put your framework mod in a flashable zip, but it's easier to just boot in recovery, and use adb to remove your old framework and push the new one.

[KERNEL][DEFUNCT]CM10/CM9/AOKP Kernel v6.3.6 [8/23] - UV/OC/GPU-BLN-Governors

This kernel no longer works with current CM10/AOKP ROMS - PLEASE DO NOT USE
PLEASE READ THIS ENTIRE POST THOROUGHLY BEFORE PROCEEDING...
This is a customized kernel built from SGH-I727 (aka Skyrocket) source code. This ROM has all the fixes from CyanogenMod & Team Chopsticks tree along with some other stuff.
It's very simple to install.
Ensure you've already installed a working ROM
Install Zip from CWM.
Wipe both caches (just to be safe)
Reboot
FSync Control - Courtesy of Ezekeel
FSync Control which can be used to disable the fsync system calls for single files and filesystems (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled). These fsync syscalls are used by kernel modules and user space programs to flush an I/O buffer (which is in RAM) to disk to make sure that this data is actually savely stored on the disk before executing the next step. Disabling fsync can result in data loss on a crash/freeze since the data is still in the I/O buffer and has not been saved to disk as it should be and can also lead to problems due to race conditions if two or more processes access the same file. On the other hand disabling fsync reduces the number of I/O operations which potentially could reduce the battery drain and also improve I/O performance.
Click to expand...
Click to collapse
Governors
Wheatley Governor - Courtesy of Ezekeel
http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__90__p__405813#entry405813
Badass (default)
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 1080Mhz and therefore use less power. To trigger a frequency increase, the system must run a bit @ 1080MHz with high load, then the frequency is bumped to 1350MHz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 2-5 seconds, depending on the load your system is experiencing).
You can tweak the Phase 2 (1080MHz) and Phase 3 (1350MHz) via sysfs (if you don't know, then just leave it alone).
NOTE: Due to it's nature, this is not a benchmark governor. It is meant as a governor that gives you a smooth experience while saving battery.
InteractiveX
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Lazy
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
GPU Overclocking
GPU is stock clocked at [email protected] & [email protected] (default).
Example: To increase maximum GPU frequency in 3D mode to 320 MHz:
echo 320000000 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk
Example: To increase maximum GPU frequency in 2D mode to 266 MHz:
echo 266667000 > /sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/max_gpuclk
echo 266667000 > /sys/devices/platform/kgsl-2d1.1/kgsl/kgsl-2d1/max_gpuclk
Available frequencies:
3D: 320000000, 300000000, 266667000, 228571000, 200000000, 177778000, 27000000
2D: 266667000, 228571000, 200000000
Kernel-based MPDecision
100% kernel-based multi-core decision! (should cpu1 be online or not?)
This replaces your /system/bin/mpdecision binary which is disabled by the CWM flashable.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (70000)
delay = time between checks (500)
pause = if something else plugs in the cpu, fall asleep for 10000
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
nwns_threshold_up = runqueue threshold, if this is reached cpu1 will be hotplugged (35)
nwns_threshold_down = runqueue threshold, if this is reached cpu1 will be unplugged (5)
twts_threshold_up = time threshold, this amount of time must have passed (250)
twts_threshold_down = same as above (250)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
(all times are in ms)
CURRENT
Version 6.3.6 - http://tinyw.in/L1BW <-- JB: CM10 or AOKP 4.1.x
Version 6.3.4 - http://d-h.st/L8K <-- JB: CM10 or AOKP 4.1.x
Version 6.2.1 - http://d-h.st/NWo <-- JB: CM10 or AOKP 4.1.x
Version 6.0.3 - http://d-h.st/hEI <-- ICS: CM9 or AOKP 4.0.4 <- Updated 8/22 - WiFi fixes
Version 5.4.5 - http://d-h.st/ngT <-- ICS: CM9 or AOKP 4.0.4
Governor scripts
NOTE: Not needed for v6.0.2 or v6.2 and beyond
These scripts will set the CPU0 & CPU1 governors correctly. Using a tool like System Tuner only sets CPU0 to the selected governor, but leaves CPU1 running the default. This was the only way I found to ensure both CPUs had the correct governor set. Basically this overwrites your init.qcom.post_boot.sh script with one that sets both CPUs to the same governor.
SmartAssV2 - http://d-h.st/zeQ
Badass - http://d-h.st/2CU
OnDemand - http://d-h.st/GAH
Non-CM9 Camera Fix
http://db.tt/vvMoadEo <-- Thanks endlessevo for this and thanks eliminat for pointing it out!
Battery life problems?
Read this first...http://forum.xda-developers.com/showthread.php?t=1759541
Then go here to grab Better Battery Stats (BBS) ... http://forum.xda-developers.com/showthread.php?t=1179809
Mega thanks to...
Team Chopsticks
Cyanogenmod Team
showp1984
gokhanmoral
faux123
TamCore
Ezekeel
FraciscoFranco
h0tw1r3
...and the other many countless kernel devs that I've Kang'd from
I don't claim credit for any unique code. I've managed to cobble this together from the following sources with various tweaks of my own to get it all running.
Faux123 (OC/UV code) - https://github.com/faux123/msm8660-htc-ics
Tegrak (Lulzactive governor) - http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
Erasmux (SmartAssV2 governor) - https://github.com/erasmux
showp1984 (BadAss, mpdecision, some very cool stuff here) - https://github.com/showp1984
TamCore (GPU OC) - https://github.com/TamCore
Hope I'm not violating any form of informal code of conduct in grabbing your guys' code.
CHANGELOG
Version 6.3.4
Removed Governor's that just plain do NOT work on our devices
Upgrade Adreno GPU drivers
Removed WiFi PM
Various CAF updates
Added ROW I/O scheduler
OnDemand Governor enhancements to support better battery usage - Applied to OnDemand-based governors (Badass, Wheatley, Lazy).
Added Gallimaufry, Aggressive, and Scary governors
Version 6.2.1
Merged Kernel up to 3.0.41
InteractiveX and Interactive screen off max freq set to 594Mhz
ram_console added to help debug CM10 - post /proc/last_kmsg to pastebin and link here
Version 6.2
Added new Governors: Lazy, Lagfree, InteractiveX (this is V2), Interactive updated to V3 (Imoysen didn't change the name for V3)
Fixed governor change not setting CPU1 (thanks to Imoysen) - No more governor setting scripts!
Added BFQv4 i/o scheduler
Version 6.1
Merged Kernel up to 3.0.40 (works great this time)
FSync control
WiFi PM control
Added fixes from Team Chopsticks git to get Alpha 2 working...not everything, but some of the juicer pieces
LMK from 3.4 kernel
Wheatley governor added - Please test and report back
As always see Github for all the bit/bytes
Version 6.0
Reverted back to 3.0.8 kernel core
Incorporated JB necessities
See Github for the bits/bytes
Version 5.5.3
Disabled ZRAM, Westwood, and LZO kernel compression
Removed some frequency steps - UnderVolting should be a little easier since there will be less knobs to turn
Changed some GPU iofractions
Updated pegasusQ governor - Works pretty good. Disable mpdecision, though. See OP to set "enabled" to 0.
Added some JB compiler options - Would be curious to see if this works OOB if someone wants to try on JB ROM
Version 5.5.1
Big update - Merged Linux kernel up to 3.0.39 (latest and greatest fixes/enhancements)
Enable ZRAM
TCP congestion control changed to Westwood (Google it)
jRCU for small systems
WiFi tweaks for battery life and flexiblity
Check out my Github commit log for a complete list - There's just too many
Version 5.4.5
Fixed 2D GPU bus speed
Implemented fixed ala Team Chopsticks to prevent emmc erasure to prevent bricking
Minor tweaks - Trying to fix vbus_present wakelock
Version 5.4.4
Added kernel-based 3-phase thermal management
OC GPU by default
DVFS disabled
Version 5.3.2
Updated OC code to default to 1.512Ghz, but OC up to 1.89Ghz (doesn't work for me very well, but ymmv) - Thanks to jjiggens for the help!
Volume bug fixed (would remain max or silent)
New BLN code
Check Github commit log for full details
Version 5.3
Really removed 1.836Ghz OC this time
UTF-8 support added back in
Reverted voltages back to the default - should fix instabilities for some. I would suggest under-volting as they start pretty high
Version 5.2z
Removed 1.836Ghz OC - Use 5.2 if you reallllly want that extra juice.
Version 5.2
SGH-I717 (Note) Source code base
GPU Overclocking support (see OP)
Upped max OC to 1.836GHz (defaults to 1.782Ghz)
Version 5.1
UTF-8 support
Various fixes
Compiler optimizations
BLN support
Version 5.0
UCLF6-based Source (e.g. official SGH-I727 from Samsung)
BadAss, SmartAssV2 Governors
OC to 1.782Ghz
Added GPU-level control to BadAss
Lowered BadAss Phase 2 Freq to 702Mhz (you can chance ala sysfs)
Hopefully reduced wifi wakelocks by filtering more unnecessary packets
VR and SIO schedulers added (let me know how they work out)
Version 3.3
RAMDISK updates from CM9
Badass tweaked for better battery (e.g. lowered phase2/3 frequencies)
Installs init.qcom.post_boot.sh with badass set as default for CPU0 & CPU1 and disables mpdecision <-- IF YOU MADE CHANGES TO THE ONE INSTALLED, MAKE A BACKUP OF YOUR'S AND COPY OVER MINE AFTER YOU INSTALL
Added support for HFP 1.6 wideband speech
Disabled GENTLE_FAIR_SLEEPERS
Version 3.2
BLN added back in
Governors: Badass (thanks showp1984), PegasusQ, SmartAssV2, standard ones
Toolchain updated to 4.6.3
Compiler optimizations
Raised max OC to 1.782Ghz
Kernel-based MPDECISION (thanks showp1984)
Various fixes (you can check my github commit log)
WiFi: WiFi wakelock reductions (tell me if things are out of whack)
WiFi: Power off wlan interface when wifi disabled to save battery
Touchscreen lock fix (ala Team Chopsticks)
Version 2.8
Non-standard governors removed - Not really aSMP aware and caused all sorts of funky weirdness
Underclocking enabled
Clock voltages tweaked - UV for some battery savings
Version 2.5e
Reverted back to fixed max freq @ 1.728Ghz (temp until I get some other things fixed)
SmartAssV2 tweaks
Fixed L2 Frequency inconsistencies (I think this was causing the freq to stick at 1.242Ghz)
Updated PegasusQ code
Version 2.4d
Added Pegasusq governor
Version 2.3
Min/Max CPU Frequency can now be set
SmartAssV2 Governor tweaked for battery life
Version 2.2.1a
Reverted early suspend/late resume driver mod
Version 2.2
Tweaked SmartAssV2 and Lulzactive governors
Added some other power tweaks
Disabled BLN - I think this is causing some problems atm. Will add back once they're ironed out.
Version 2.1
Tweaked Lulzactive and SmartAssV2 governors
Added OC/UV code from Faux123 repo
Version 2.0
Added Lulzactive governor
Version 1.0
Stock Kernel compiled from source with SmartAssV2 governor
My Github - https://github.com/InstigatorX
First good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Downloading. Will report back in a few minutes.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Downloading! Gonna test this on Chimera beta 2 flashed over CM9 A5. Will report back shortly, stay tuned...
Sent from my SGH-I727 using xda premium
Edit/Update.... Running GREAT! Set to smartass V2 and set min freq to 192. I used NSTools to set and double checked the govenor and frequencies with Rom Toolbox pro and Set Cpu, everything is sticking and running smooth. Been running this for an hour now, will report back if I find any issues in the future. Thanks again for the kernel, InstigatorX, GREAT WORK!!!!!!!!! (high 5)
Nothing broken
Set to smartass v2 min 192
Feels smooth. Really smooth. Hopefully this means i can leave my charger at home now
Edit: holy crap! Phone is on usb charging from laptop. This is the first time on cm9 its actually charging FAST while I'm using it!
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium
No.
Btw-loses backlight after screen off. Not every time though, weird.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Kole_Ackerson said:
I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
dont do it.
But yeah this kernel rocks!
Ok I'm on chimera flashed over aokp where are the performance settings at on here?
Edit: Using rom toolbox to set it. It seems to be sticking..
Sent from my SGH-I727 using Tapatalk 2
Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
mindmajick said:
Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
Works for me on CM9. Will check it out.
Sent from my SAMSUNG-SGH-I727 using xda premium
Am running cm9 too. I can set it, but when i go back in to performance its back to 1512.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium
BaconStep said:
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
hahaha
So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp
softballjunkee13 said:
So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp
Click to expand...
Click to collapse
I'm running it just fine
Sent from my SGH-I727 using Tapatalk 2
tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA
sk8erwitskil said:
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Read the last two lines, he's obviously kidding.
You change/add a color filter btw? Noticing the colors are a bit warmer than usual.
Sent from my SAMSUNG-SGH-I727 using xda premium

"No-Frills CPU control/Pimp my Rom" for different speed governors and I/O schedulers

"No-Frills CPU control/Pimp my Rom" for different speed governors and I/O schedulers
The custom Kernel for A110 is coming. But till then, you can try out some different clock settings to get you more speed when on games and experiment with speed governors and I/O schedulers with the stock kernel.
Install No-frills CPU control or use Pimp my ROM to change the Min clock(limited to 250 MHz) or Max clock (limited to 1.001 Ghz now) and 5 governors (ondemand, userspace, powersave, hybrid, performance). For optimal battery and speed use ondemand with 1Ghz/250Mhz and noop scheduler. For games, try performance governor. Those who want maximum battery life can try powersave governor....
pradipsoman said:
The custom Kernel for A110 is coming. But till then, you can try out some different clock settings to get you more speed when on games and experiment with speed governors and I/O schedulers with the stock kernel.
Install No-frills CPU control or use Pimp my ROM to change the Min clock(limited to 250 MHz) or Max clock (limited to 1.001 Ghz now) and 5 governors (ondemand, userspace, powersave, hybrid, performance). For optimal battery and speed use ondemand with 1Ghz/250Mhz and noop scheduler. For games, try performance governor. Those who want maximum battery life can try powersave governor....
Click to expand...
Click to collapse
lol..its useless on stock kernel.bdw each and every kernel can be underclocked.
Dj_cool said:
lol..its useless on stock kernel.bdw each and every kernel can be underclocked.
Click to expand...
Click to collapse
I think you have not read the post correctly. See the heading...Its not for changing clock speeds...Its for changing governors and I/O schedulers and there is no way you can do that on stock ROM without an external application as there is no settings for that in the stock ROM. And I am not taking anything about overclocking dude And many of the end users are beginners who do not even know these things...
I have clearly mentioned that the highest freq is capped. And it is not useless. We can play with the governors and the I/O schedulers. Read before you comment pal
but all are useless in stock kernel.ask varun if u have any doubt.
Dj_cool said:
but all are useless in stock kernel.ask varun if u have any doubt.
Click to expand...
Click to collapse
You are totally wrong dude..Get your info right. I have been playing with android right from 2010 and have used a multitude of phones Am not a beginner...I do not have to ask Varun on this...Default kernels come with limited speed governors and I/O schedulers that I have listed above, and THEY DO WORK...When you modify the kernel using sources, you can add many more governors and schedulers and also add other functionalities like over-clocking. Think before you post pal
http://forum.xda-developers.com/showthread.php?t=1369817
Read this dude....
And for your knowledge. The default governor and scheduler that our A110 comes set with is hybrid/cfq. That gives the maximum quandrant score of 3000 and above. Try to change it and you will see the difference in performance. The quadrant scores will go down. The settings DO WORK and to get better battery you can compromise on the performance.
Cheers....
m also not new in android..i also used too many android phones.
pradipsoman said:
You are totally wrong dude..Get your info right. I have been playing with android right from 2010 and have used a multitude of phones Am not a beginner...I do not have to ask Varun on this...Default kernels come with limited speed governors and I/O schedulers that I have listed above, and THEY DO WORK...When you modify the kernel using sources, you can add many more governors and schedulers and also add other functionalities like over-clocking. Think before you post pal
http://forum.xda-developers.com/showthread.php?t=1369817
Read this dude....
And for your knowledge. The default governor and scheduler that our A110 comes set with is hybrid/cfq. That gives the maximum quandrant score of 3000 and above. Try to change it and you will see the difference in performance. The quadrant scores will go down. The settings DO WORK and to get better battery you can compromise on the performance.
Cheers....
Click to expand...
Click to collapse
You mallu?
same here, expand what you are trying to say?
o/c not possible in stock kernel, but yes we can set clock values depending on the stock clock values between 0 - 1ghz (min 250mhz / maxx 1ghz), and even set governers, we need root for doing such actions na? but not possible without root!!!
deadlyindian said:
You mallu?
same here, expand what you are trying to say?
o/c not possible in stock kernel, but yes we can set clock values depending on the stock clock values between 0 - 1ghz (min 250mhz / maxx 1ghz), and even set governers, we need root for doing such actions na? but not possible without root!!!
Click to expand...
Click to collapse
Yes, you need to be rooted
pradipsoman said:
Yes, you need to be rooted
Click to expand...
Click to collapse
so can you give me a clean explanation of everything u said on the 1st post?
Yup..plz explain dude.:angel:
in the stock rom/kernel , what settings in "no frills cpu control" is the best for performance and battery respectively ?
the options seen are governors ( userspace , ondemand,hybrid, powersave , performance ) and I/O scedulers (cfq , deadline, noop) ..
will changing these options be effective in the stock kernel ?

Padfone 2 A68 [Kernel] Stone custom kernel for ASUS Padfone 2 - OC/UV/GPL/etc

Presenting the Stone Kernel for ASUS Padfone 2 (A68), a custom kernel designed to get a little more out of the Padfone 2.
DISCLAIMER: As per all custom kernel disclaimers, while I do test this kernel on my own device, I'm not responsible for you voiding your warranty, or any damage/bricking/weirdness that may occur to your Padfone. If you're not comfortable with this, do not proceed.
v0.9
Main features:
Based on ASUS source code v10.4.16.8, compatible with Android 4.1.1 stock PadFone2 firmwares
init.d support (init.rc busybox runparts)
USB OTG Host in phone mode
UI rendered with GPU instead of CPU, making it very snappy
Lowest CPU frequency set to 162mhz
CPU frequency locked to 162mhz-1512mhz during boot
Undervolted to save power & reduce heat
Undervolt interface (compatible with System Tuner, Kernel Tuner, etc)
Additional CPU Governors: Wheatley, InteractiveX v2, MSM_DCVS
Set InteractiveX v2 CPU Governor to default instead of Performance, to lower battery consumption, maintain snappy performance, and improve CPU freq config
GPU normal freq set to 200mhz to lower battery usage (will still scale upto 266/400/533mhz when busy)
Simple IO Scheduler (SIO) added, and set as default
Increased min/max read-ahead values from 16/128 to 32/2048
USB FastCharge upto 1400mA (enable using Kernel Tuner, sysfs, etc)
Lower minimum brightness to save power
Lower voltage for display (~13% lower voltage) to save power
NTFS USB drives need USB OTG Helper software or similar - working on fixing the NTFS module
Increased file cache ratio to improve storage performance
Standard edition: CPU max 1.51ghz, GPU max 400mhz
Overclock edition: CPU max 1.72ghz, GPU max 533mhz, low voltages
Powersaver edition: CPU max 1.35ghz, GPU max 266mhz, low voltages
Minor tweaks:
Replace Wifi modules with AOSP versions (needed due to the way the stock modules were compiled by ASUS)
Disabled swap
Disabled "Compile the kernel with debug info"
Disabled Debug memory initialisation
Disabled Magic SysRq key
NTFS in kernel (instead of module)
FAT support
Improved CPU multi-core frequency limiting
GitHub: https://github.com/lindsaytheflint/stone
Download:
Stock kernel 10.4.12.24: https://docs.google.com/file/d/0ByOiY1XD_cLvNVFwVi1Yc3lmS2M/edit?usp=sharing
Stock kernel 10.4.15.1: https://docs.google.com/file/d/0ByOiY1XD_cLvVU5KWkJqZzVrU00/edit?usp=sharing
Stock kernel 10.4.16.8: https://docs.google.com/file/d/0ByOiY1XD_cLvaGR2X19RS2hOa28/edit?usp=sharing
Stone kernel v0.1 "Dual": https://docs.google.com/file/d/0ByOiY1XD_cLva0Q3el9VbU1vd1k/edit?usp=sharing
Stone kernel v0.1 "Quad": https://docs.google.com/file/d/0ByOiY1XD_cLvdk9EcTAtdXdDRGM/edit?usp=sharing
Stone kernel v0.2 "Standard voltage": https://docs.google.com/file/d/0ByOiY1XD_cLvUFpSenoyXzFYRVk/edit?usp=sharing
Stone kernel v0.2 "Low voltage": https://docs.google.com/file/d/0ByOiY1XD_cLvclVXdEs4Qm1sb0U/edit?usp=sharing
Stone kernel v0.3 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd28ybVB2MHhXTXc/edit?usp=sharing
Stone kernel v0.3 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvUnI4Z01YYzZBY1k/edit?usp=sharing
Stone kernel v0.4 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd1lOQmI4c2duaGc/edit?usp=sharing
Stone kernel v0.4 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvM2QxdXVFMGcxRm8/edit?usp=sharing
Stone kernel v0.6 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvSm9XQVBqTWtBUEU/edit?usp=sharing
Stone kernel v0.6 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvN3otdjM3elNHYUk/edit?usp=sharing
Stone kernel v0.7 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvbTBralZ4aVZFOVk/edit?usp=sharing
Stone kernel v0.7 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvTGc2YWJFWFYxWGM/edit?usp=sharing
Stone kernel v0.8 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvNGxheldqTThNT2c/edit?usp=sharing
Stone kernel v0.8 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvOWw4cFBGb0xyUEk/edit?usp=sharing
Stone kernel v0.8 "PS": https://docs.google.com/file/d/0ByOiY1XD_cLvemtzSTlMZEpGcU0/edit?usp=sharing
Stone kernel v0.9 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvbUxWRHVPd1cyX2s/edit?usp=sharing
Stone kernel v0.9 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd3FQOXJnbVZVbFE/edit?usp=sharing
Stone kernel v0.9 "PS": https://docs.google.com/file/d/0ByOiY1XD_cLvbm5qNFdHZWcwYjA/edit?usp=sharing
Installation:
1. Copy StoneK_A68_v0.9_OC.zip or StoneK_A68_v0.9_STD.zip to /sdcard/ via USB.
2. Copy StockKern_A68_10.4.16.8.zip to /sdcard/ via USB, in case you have trouble booting, and need to uninstall.
3. Boot into TWRP or CWM Recovery.
4. Perform backup of at least your "Boot" partition.
5. Install zip from step 1.
6. Reboot.
Uninstallation:
1. Copy StockKern_A68_10.4.16.8.zip to /sdcard/ via USB.
2. Boot into TWRP or CWM Recovery.
3. Install zip from step 1.
4. Reboot.
ChangeLog
ToDo:
Possibly faster CPU & GPU overclocking, pending successful testing
GPU undervolt
GPU freq sysfs interface
WiFi undervolt
Enable additional audio codecs: WMA, AAC, etc
BLN?
v0.9 - 2013/08/19
Raised voltage slightly for display, to increase compatibility with other's phones, and prevent flickering
Increase storage read-ahead from 1024kb to 2048kb
Increased file cache ratio to improve storage performance
v0.8 - 2013/07/29
Lower minimum brightness to save power
Lower voltage for display (~16% lower voltage) to save power
CPU lowest freq set to 162mhz (from 192mhz)
GPU idle frequency set to 200mhz (from 128mhz)
Fixed USB OTG for both phone & pad
NTFS USB drives need USB OTG Helper software or similar - working on fixing the NTFS module
Disabled MPDecision?
OC edition: GPU max freq set to 533mhz (from 487mhz)
New edition: Power Saver - lower CPU & GPU limits, useful when travelling
v0.7 - 2013/06/14
Built from 10.4.16.8 ASUS source code
Fixed camera
Removed Faux123 MSM CPUFreq_limit to improve multi-core freq limiting
Modified CPU freq limits so that cores 2-4 will never exceed core 1 frequency
v0.6 - 2013/06/05
Disabled Android Low Memory Killer (2GB RAM is quite a bit, and the perf cost of relaunching processes is annoying)
Enabled USB OTG Host in phone mode
Minor voltage tweaks
Added MSM_DCVS Governor
Added Faux123 MSM CPUFreq_limit to improve multi-core freq limiting
UI rendered with GPU instead of CPU, making it very snappy
Minor init.rc/build.prop tweaks
v0.5 - 2013/05/18
Enabled init.d support (init.rc busybox runparts)
v0.4 - 2013/05/13
Lowered InteractiveX default boost freq from 1512000 to 1350000
Increased USB Fast Charge limit from 1000mA to 1400mA
Fixed LCD backlight during calls
Reverted from GCC 4.7 to GCC 4.6 so ASUS modules load ok
v0.3 - 2013/05/07
Based on ASUS source code v10.4.15.1
Two versions - OC & Standard
Switched compiler from GCC 4.6 to 4.7
Further voltage tweaking
Fixed CPU throttling
Added InteractiveX v2 Governor - very good for properly setting CPU freqs across all cores
Set default Governor to InteractiveX v2
GPU overclock to 487mhz - working
GPU normal freq set to 128mhz to lower battery usage (will still scale upto 487mhz when busy)
Simple IO Scheduler (SIO) added, and set as default
Increased min/max read-ahead values from 16/128 to 32/1024
USB FastCharge (enable using Kernel Tuner, etc) - working
Removed Sysctl syscall support
Removed software controlled Adaptive Voltage Scaling (AVS)
Removed adaptive voltage scaling (AVS)
Removed Generic Dynamic Voltage and Frequency Scaling (DVFS) support
Removed CPU frequency translation statistics details
Reduced max CPU voltage back to 1.30v
Re-enabled "Monitor thermal state and limit CPU Frequency"
v0.2
Removed dual/quad versions - quad-core is running stably for me with revised voltages
Added standard/low voltage versions, for anyone having trouble booting, please try the standard version
Lowest CPU frequency set to 192mhz
Android Logger re-enabled temporarily, for USB FastCharge troubleshooting
CONFIG_SCHED_MC=n (not needed with HotPlugging CPU)
CONFIG_SCHED_SMT=n (not needed)
Disabled "Monitor thermal state and limit CPU Frequency"
Increased max CPU voltage from 1.30v to 1.45v (always monitor your temperature when increasing the voltage/frequency!!)
Further tuned CPU voltages
Added Wheatley Governor, and set to default
Disabled "Use MSM_DCVS for CPU/GPU frequency control"
GPU overclock to 487mhz - not verified yet - I think some kind of ASUS lock may still be preventing this
USB FastCharge (can be turned on with Kernel Tuner etc) - not verified yet - I think some kind of ASUS lock may still be preventing this
FAQ
Q. My phone is running hot!
A. This is usually related to the voltage being too high. Try lower voltage, and try to determine which frequencies are running hot for you. You may need to also restrict your max CPU frequency with SetCPU, System Tuner, Kernel Tuner, etc, if the frequency won't run stably on your phone.
Q. CPU-intensive apps (particularly games) terminate abnormally after a bit of use.
A. This usually means the voltage is a little too low for that frequency. Try to raise the voltage (only 12.5mv at a time) until you find a stable voltage, and let the rest of us know what value is best for you.
Q. My phone won't even boot with this kernel.
A. Sounds like the voltages are too low for you. Try the "STD" version, which uses voltages only slightly lesser than stock.
Q. I want GPU overclocking, but I don't want CPU overclocking.
A. Use the "OC" version, and use SetCPU, System Tuner, Kernel Tuner, etc, to set the max CPU freq you want.
Q. Proximity sensor doesn't work during a call
A. Fixed in version 0.4
How stable is it?
And also, if I read/understood the "main features" right, you limited the CPU to only use 2 cores instead of 4?
I read that you did it for more stability when overclocked, but if this only uses 2 cores out of it's 4, I will be very hesitant to flashing it...
Either way though, this is great progress! We are finally getting a handfull of developers for the Padfone 2! Hopefully we can get Cyanogenmod ported soon aswell!
Great job!
Lidenburg said:
How stable is it?
And also, if I read/understood the "main features" right, you limited the CPU to only use 2 cores instead of 4?
I read that you did it for more stability when overclocked, but if this only uses 2 cores out of it's 4, I will be very hesitant to flashing it...
Either way though, this is great progress! We are finally getting a handfull of developers for the Padfone 2! Hopefully we can get Cyanogenmod ported soon aswell!
Great job!
Click to expand...
Click to collapse
I've been using it for a few weeks, and when I had 4 cores enabled, I found it a bit unstable. With 2 cores enabled only, it flies along due to the higher frequency, and is rock-solid.
Unless you're using the MSM_DCVS Governor (which isn't default even on stock kernel), not all the cores are used except for under high load. Using Interactive, Performance, and other Governors, it usually keeps 3 cores off, and just powers the second one up when doing things. Only when running very CPU-intensive tasks will all 4 cores be used, and the phone will run very hot. If using the MSM_DCVS Governor, it'll continually lower the CPU frequency anyway. These factors are why I've limited the CPU cores - the end-result is a faster, cooler, and less power-hungry kernel.
Nevertheless, I'll upload another one in the next couple of days with all 4 cores enabled, so people can test it out.
First of all nice work here ! Good to see people progressing. As im still bit of a noob and my question maybe quite noobish.
I have NOS installed on my padfone 2 atm and its working flawlessly. Just before I try this I wanted to ask you if this will some way interfere with NOS ?
I would happily be our test monkey if needed
One more time,
Thank you !
Hey first of all this is very nice that you develop kernel to padfone and its nice to see some progress , but i would like that if you make the kernel with 4 cores and little bit smaller clocks ex 1.5 or 1.6 and if you set low freg to somewhere near 100mhz. That would be nice to see
Sent from my PadFone 2 using xda app-developers app
Great work! We finally have our first custom kernel
Great work... I will test soon as possible
Sent from my PadFone 2 using xda app-developers app
Quad core
I've recompiled the kernel with all 4 cores enabled, and will update after I've done some stress testing. (I won't upload it if it's not stable for me.)
When I tested it a few weeks ago, quad core was too hot, but I've tweaked the voltages quite a bit since then, so hopefully it'll be upload-worthy.
How to download link using phone?
Quad core version uploaded
I've uploaded the Quad core version too.
Curious to here other people's experiences on that - I personally find that my PF2 barely uses the 3rd & 4th cores (even on stock kernel), so I prefer the dual core kernel version (faster, more stable, less heat, less voltage requirements), but CPUs differ a little from phone to phone.
Keen to here people's tests from the dual core kernel vs the quad core kernel.
Me currently testing dual core version
Just downloaded and installed the QuadCore version. Will be back here in a couple of days!
Can you say thank you too many times ? NOT!
Thank you once more !
Thank you for quadcore version wil try it out!
Sent from my PadFone 2 using xda app-developers app
Reboots in Padfone Station
I tried to use the dual core version today during some meetings and it was fine when in phone mode, but after using it in the station for a while it would get very hot and then reboot. I was overclocking it to 1.7. Anybody else have similar experience?
sunshine333 said:
I tried to use the dual core version today during some meetings and it was fine when in phone mode, but after using it in the station for a while it would get very hot and then reboot. I was overclocking it to 1.7. Anybody else have similar experience?
Click to expand...
Click to collapse
Usually "very hot" means that the voltage needs to be lowered. Can you try using System Tuner to lower the voltage slightly for 1.7ghz frequency, and advise whether that helps?
i have flash the dual core ver.
But when i boot and at the asus loading logo, it keep shining white screen and some color line.
After booted into system it soft reboot again and again. then i revert to stock kernel it fine.
i already wipe cache/dalvik
i am using TWRP 2.5 and stock rom
Undervolting 1.7
I have not tried it in the padstation yet, but the 4 core version undervolted 1 step down (1125 I think?) was stable when I just played Final Fantasy 3 for about 20 mins. CPU spy shows that it was running at 1.7 during that time. No apparent heat issues and no reboots or anything like that. I will try it in the padstation and report back later.
---------- Post added at 03:49 AM ---------- Previous post was at 03:40 AM ----------
Just to be clear I only further undervolted the highest frequency (1.7). Other parts of the table were default for your 4c kernel.
Which app is recommended to overclocking and undervolting?

[Kernel][3.0.101] faZevoLv.kernel [5.0.x]

faZevoLv.kernel​
This is a new kernel based off the more stable Hashcodes kernel rather than the previous kernel named thomasin kernel which was based off MWisbest's kernel source which was unstable and caused many random reboots for me and a few other users. This is why this kernel was created, fast, feature packed, updated and most importantly STABLE. no random reboots.
Features and Updates
3.0.101 patches from franciscofranco
OMAP4460 overclocking from MWisbest
Makefile: Linaro build flags
Optimised LPDDR2 RAM timising for a 12% throughput increase
tweaked CFQ tunables from franciscofranco
cpuidle: update to saner values and optiisations
binder: fix memory leak
update LZO compression to upstream
ARM: enable unaligned memory access
use GNU implementation of lib/string & lib/memcpy
force kernel to follow unaligned code path
cfg80211: fix memory leak
ARM memset fixes
readahead: make context readahead more conservative
vmalloc: updates and fixes
net/loopback: set mtu to 64k
CPU hotplug: update debug
cpufreq: optimise frequency table verify and updates
vmscan: allow it to sleep if running too long
SELinux: updates and workarounds
omap4-common: activate scu speculative linefills
omap4-comon: enable full zeroes write mode
omap4-common: tune values to fit changes without double linefill
OMAP4: update ARM errata options
OMAP4 NAND updates
Add ultra-KSM
import lowmemorykiller from 3.4 kernel and tune & update
readahead: add dynamic read-ahead
dynamic management of dirty page writebacks
add support for lz4 compressor and decompressor module
add lz4 cryptographic api
use lz4 for kernel compression
add Lagfree governor
SIOplus i/o schedular and tune
ARM: implement optimised percpu variable access
permanent filesystem TRIM
Optimise apply_stack() for size and speed
network speed tweak
wakeup: use irqsave/irqrestore for events_lock
add Hyper governor
interactive governor fixes and updates
net: add APIs for manipulating skb page fragments
random: entropy tweaks
increase clock rate for dpll_core_m6x2_ck for OPP100
use SLUB allocator as default
use RCU boost
lib/sha1: use the git implementation of SHA1 as it is faster
ashmem: fix deadlock when low memory
bcmdhd: decreased wakelocks
mmc: decrease wakelock timeout
bcmdhd: workaround for broken AC video queue in IBSS mode
pcm_native: code fix
OOM tweaks: many oom tweaks and fixes (5 commits)
procfs: speed up /proc/stat
ARM: add optimised swahb32()
ARM: implemented cpu topology for multicore devices (12 commits)
introduce effective timer slack and PR_GET_EFFECTIVE_TIMERSLACK
introduce timer slack control
Dynamic management of timer slack
XDA:DevDB Information
Advanced kernel for lollipop, Kernel for the Amazon 7" Kindle Fire HD
Contributors
faZevoLv, Hashcode
Version Information
Status: Stable
Current Stable Version: 002
Stable Release Date: 2015-03-01
Created 2015-02-27
Last Updated 2015-02-27
Frequencies
> 350mhz (default min)
> 525mhz
> 768mhz
> 998mhz
> 1200mhz (default Max)
> 1350mhz
> 1500mhz
> 1632mhz
> 1747mhz
Governors
> Conservative
> Ondemand
> Powersave
> Interactive (default)
> Performance
> Hotplug
> Hyper
> Lagfree
I/O Schedulers
> CFQ (default)
> NOOP
> Deadline
> SIOplus
TCP Congestion Algorithm
westwood (default), reno, bic, cubic, htcp, vegas, veno, yeah​
Has it fixed battery life? As it was draining significantly than stock kernel..
You rock dude! Flashing right away.
xWolf13 said:
Has it fixed battery life? As it was draining significantly than stock kernel..
Click to expand...
Click to collapse
Yeah deep sleep is fixed, in the other kernel it did not go into deep sleep which was where the battery drained.
So when will it be completed? (And if it is completed, when can we download?) I'm itching to test it out.
Fireator said:
So when will it be completed? (And if it is completed, when can we download?) I'm itching to test it out.
Click to expand...
Click to collapse
Go to the downloads section at the top of the OP (the black bar) and download it
faZevoLv said:
Go to the downloads section at the top of the OP (the black bar) and download it
Click to expand...
Click to collapse
Thanks!
faZevoLv.kernel.002 is out!
Check the features list for the updates, the download link as always is in the downloads section
So how high does the GPU overclock to? And where can I go to change the frequency? Can I use trickstermod app?
BTW, its a pretty good kernel. Nice and smooth. Ever better when I use Seeder. Only thing I noticed was that it reboots every time I try to overclock it to 1747Mhz. 1500Mhz is the most stable for me so I'm sticking with it for now. Keep up the good work!!
Fireator said:
So how high does the GPU overclock to? And where can I go to change the frequency? Can I use trickstermod app?
BTW, its a pretty good kernel. Nice and smooth. Ever better when I use Seeder. Only thing I noticed was that it reboots every time I try to overclock it to 1747Mhz. 1500Mhz is the most stable for me so I'm sticking with it for now. Keep up the good work!!
Click to expand...
Click to collapse
ive not added the option to set your own gpu overclock yet, but it will be implemented in a future release thankyou!
Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.
KLit75 said:
Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.
Click to expand...
Click to collapse
Highest I can go to is 1632. No hiccups so far. Using Interactive Governer with Min Frequency set at 1200Mhz. At the moment I am testing out the new I/O Scheduler that was added, sioplus.
xWolf13 said:
Highest I can go to is 1632. No hiccups so far. Using Interactive Governer with Min Frequency set at 1200Mhz. At the moment I am testing out the new I/O Scheduler that was added, sioplus.
Click to expand...
Click to collapse
That's what I was doing except with a lower min value and it crashed. Not the system just the browser this time. I'm thinking not all kfhds are created equally.
Overall this has been pretty stable though when I keep it at or below 1500
KLit75 said:
Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.
Click to expand...
Click to collapse
This doesn't support double tap to wake as it stopped the device from going into deep sleep which caused the huge battery drain, sorry about that.
And yeah I usually stay at 1500, but the option is there for kindles that can handle higher
Not sure if this is related to kernel or ROM (beanstalk) but I'm getting incompatible a lot in play store. I tried market helper but apparently its not ready for lollipop yet. Is there a workaround or like I just considered now--lots of the apps aren't compatible with 5?
KLit75 said:
Not sure if this is related to kernel or ROM (beanstalk) but I'm getting incompatible a lot in play store. I tried market helper but apparently its not ready for lollipop yet. Is there a workaround or like I just considered now--lots of the apps aren't compatible with 5?
Click to expand...
Click to collapse
Yeah its because a lot of apps don't support lollipop, however most of them can be downloaded from your browser with a quick google search
I know this is way out there a year later, but any plan on updating to 5.1.1 CM based?

Categories

Resources