Database Users

[KERNEL] SetiroN i9000 SuperOptimized v1.5.6: JPX, 345MB RAM, UV/OC upto 1.6GHz

Sorry for disappearing guys, I wasn't in the mood for posting or working on the kernel: unfortunately it looks like I bricked my phone.
I couldn't believe it myself but as soon as I restarted it phone after CWM-flashing my usual JPO rom, going back from official JPU+803.pit, the screen went black and never came up again, no matter the key combination. No signs of life besides warming up slightly after pressing power or connecting the USB cable. No luck with a JIG cable aswell, tried all the way from 290K to 315K Ohm and nothing happens... I guess there's nothing I can do.
The problem is, I came back to Europe last month and official Samsung centers around here are refusing to offer repair services on US phones because of some kind of freak policy they have, even if I pay myself.
Update Dec 13:
I have no words to explain how thankful I am: PAulyhoffman offered to donate a spare phone he had, and promptly shipped it on the same day.
A special mention goes to Patrick Richter, Pauly's father in law, who just passed away on Saturday: a most generous man in honor of whom he would like to dedicate the donation.
I've already covered the shipping fee myself but customs will add a variable amount in taxes (most definitely 20% of original value as they usually do, although the specified value is just $100).
Hoping customs won't hold the package over the holidays, untested version versions will have to do for now.
HUGE thanks go to every single one who offered help, I really am moved by the affection demonstrated by this wonderful community.
Click to expand...
Click to collapse
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels, including OC/UV support, 340Mb RAM and compiling optimizations.
Being based on the i9000 JPM source, it comes with every issue xcaliburinhand's kernel might have.
As I have absolutely no kernel programming knowledge, all credit goes to the respective coders: I've merely copied, pasted and compiled things, so I won't be able to offer much additional support or modify any of the function unless they provide source.
THIS IS A FROYO KERNEL, USE ONLY WITH A 2.2 ROM, PREFERABLY AN I9000 ONE
DO NOT USE SETCPU
Features:
- Sztupy's Ultimate Lag Fix V. pre-0.4https://github.com/sztupy
Multiple configurable Lagfix options:
Ext4 No-Journal DATA: /data converted to Ext4 with no journaling, everything else stays RFS
Ext4 No-Journal ALL: /data, /cache and /dbdata converted to Ext4 with no journaling
Ext4 DATA: /data converted to Ext4, everything else stays RFS
Ext4 ALL: /data, /cache and /dbdata converted to Ext4
Ext2 DATA: /data converted to Ext2, everything else stays RFS
Ext2 ALL: /data, /cache and /dbdata converted to Ext2
Advanced options: lets you specifically configure each partition and eventually add an Ext2 loop on top of them
Ext3/4 mount options: enables writeback journaling mode
(Using BIND_DATA_TO_DBDATA you might run out of space with many apps installed)
Suggested configuration (Ext4 ALL):
DATA_FS=ext4
CACHE_FS=ext4
DBDATA_FS=ext4
DATA_LOOP=false
CACHE_LOOP=false
DBDATA_LOOP=false
BIND_DATA_TO_DBDATA=false
Use FAST mount opts
You will get a "Configuration has changed" recovery screen at the first reboot after setting lagfix options, it's perfectly normal. If you wish to keep your current data, select the first option and wait (a separate backup is recommended).
- Modded CWM integrated
- CWM pre-installed (no more install from update.zip)
- reboot to 2e recovery
- reboot to download mode
- tweaking options
- root from recovery
- configure lagfix
- raspdeep's OC/UVhttp://forum.xda-developers.com/showthread.php?t=822027
If you do not want to mess with commands, use Xan's Voltage Settings app
- do note that you're subtracting voltage from the default setting, which varies with frequency:
Code:
1600MHz CPU 200MHz GPU 1400mV
1552MHz CPU 194MHz GPU 1375mV
1488MHz CPU 186MHz GPU 1350mV
1440MHz CPU 205MHz GPU 1325mV
1400MHz CPU 200MHz GPU 1300mV
1344MHz CPU 192MHz GPU 1300mV
1288MHz CPU 184MHz GPU 1300mV
1200MHz CPU 200MHz GPU 1300mV
1000MHz CPU 200MHz GPU 1275mV
800MHz CPU 200MHz GPU 1200mV
400MHz CPU 200MHz GPU 1050mV
200MHz CPU 200MHz GPU 950mV
100MHz CPU 100MHz GPU 950mV
the lastest Voltage Settings version includes voltage calculation
- 345Mb available RAM with 720p and JPU support
And improved minfree memory management
- Hardcore's SpeedModhttp://forum.xda-developers.com/showthread.php?t=822756
- jhash3
- Kernel HZ
- startup tweak scripts (available from cwm)
- ext4 kernel patches from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
- compiling optimizations:
(thanks to laststufo)
-O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -fno-gcse -fprefetch-loop-arrays --param l2-cache-size=512 --param l1-cache-size=64 --param simultaneous-prefetches=6 --param prefetch-latency=400 --param l1-cache-line-size=64
- config optimizations: (XT variant only)
CONFIG_UACCESS_WITH_MEMCPY=y
CONFIG_KSM=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
additional config settings found in other kernels are pointless or even counterproductive for performance/stability
- BFQ I/O schedulerhttp://lwn.net/Articles/306641/
Set as default, you may change it using Xan's Voltage Settings app
- supercurio's Voodoo Color&Sharpnesshttps://github.com/project-voodoo
- HSUPA support (with i9000 modems)
Enable WCDMA 850Mhz by dialing *#2263# (COMBI BANDS -> choose WCDMA 850)
- neldar's v2.2 BackLight Notifications supporthttps://github.com/neldar/backlightnotification
Configure with BacklightNotification settings app
To enable BLN it is necessary to flash a CWM zip or enable BLN in CWM from ULK advanced options
- Boot animations support
http://forum.xda-developers.com/showthread.php?t=819686
http://forum.xda-developers.com/showthread.php?t=822955
http://forum.xda-developers.com/showthread.php?t=623960
Once again, none of it comes from me and all credit goes to the original developers, especially xcaliburinhand, raspdeep and hardcore
Nevertheless, if you're feeling particularly generous and have already provided for the developers, I'll gladly accept a token of gratitude (after all, being so ignorant I did have to invest quite a bit of time into it).
Everything comes at your own risk, I offer no support at all.
Thank you aleadam, ReedX50v, junktzu, shaolin95, Shane, krl66, Smokestack76, Henry, Xstop, lpsi200, Arffer, newter55, Lertets, txRangerXDA, id10terrordfw and Bedwa for your donations.
Code:
- v1.5.6
fixed boot-up and CWM instability
updated modules from JPX kernel
new frequency table
full compatibility with Voltage Control 3 (lowering frequency with it seems to cause freezes)
removed update_frequency, making changes to the freq table immediately applies them
- v1.4.7
fixed boot animation issues
fixed init.d script execution
fixed CIFS support
- v1.5.5
lowered default freq to 1000MHz
updated ram disk to late 1.4.x versions
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
- v1.4.6
improved wi-fi performance
fixed internal SD mount as CD-ROM on JPU
Changelog:
- v1.4.5
Frequencies/battery fix
- v1.4.4
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
gained an additional MB of RAM thanks to kernel size optimization
implemented Xcaliburinhand's wired headset fix
optimized RAM utilization (minfree tweaks)
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations, GPS tweaks, CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
HZ=500, PREEMPT_VOLUNTARY
JPU variant with modules and mem config extracted from samsung's JPU kernel: DO NOT USE IT ON FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG JPU AND ONLY THEN FLASH THIS KERNEL
v1.5.4
initial boot and recovery frequency lowered from 1200MHz to 800MHz
reduced voltage change delay
frequency jumps set up more like 1.4 in order to improve performance
v1.5.3
/system mounts as RO
added workaround script inside the update.zip to execute voltage control boot settings directly from the program's data dir, eliminating the necessity to remount /system
corrected frequencies script, should now work on every ROM
only available as a CWM update.zip to make sure everyone has working init scripts
increased default voltages for 1456-1464MHz to 1325mV, 1504-1544MHz to 1375mV and 1600MHz to 1400mV, regulate your UV settings BEFORE upgrading
gained an additional MB of RAM thanks to kernel size optimization
v1.5.2
DELETE USER GENERATED SCRIPTS IN /system/etc/init.d/ BEFORE UPGRADING
(remember it's necessary to unlock higher frequencies from both freq_table and Xan's app)
implemented Xcaliburinhand's wired headset fix
mount /system R/W - could be dangerous, but solves script creation issues
optimized frequency jumps for better battery life
optimized RAM utilization (minfree tweaks)
workaround for the highest frequency step being sometimes briefly used during bootup and recovery operation
effectively set 1200MHz as the default frequency
corrected wrong display of highest frequency in Quadrant
added frequencies scheduler script in the CWM zip package with a visual aid
reorganized performance levels with a few additions
- v1.5.1
skipped, integrated in 1.5.2
- v1.5
updated raspdeep's OC/UV to v300
multiple performance levels:
100
200
400
800
1000
1200
1360 (GPU downclocked, don't worry performance improves anyway)
1400
1440 (GPU slightly overclocked)
1460 (GPU downclocked)
Default clock at 1200MHz, additional frequencies can be enabled by editing /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
in order to update the states table it's necessary to edit to 1 /sys/devices/system/cpu/cpu0/cpufreq/update_states (echo from terminal or by manually editing the file, just like the states table)
added compatibility with Xan's voltage app v2.0 (please update, v1.9x wouldn't work correctly)
reduced 14xxMHz default voltage to 1.3v
updated CWM to include Hardcore's latest additions
slight menus reorganization
updated optimization scripts (now including battery optimizations and CIFS support)
built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)
built-in support for ext4 mount optimizations (writeback mode)
- v1.4.3
fixed 2e recovery, now completely functional
added 1350Mhz, 1400MHz and 1450MHz variants, only available as ODIN packages. The latter two have a default voltage of 1350mV. Keep using Xan's Voltage App v1.98b's 1200MHz setting to undervolt, higher frequencies replace the 1200MHz step, bear in mind the app doesn't show the updated frequency/voltage. Remember to reset said setting before upgrading and please realize how 14xxMHz will only run on few lucky devices
from now on there won't be a CWM version for 1350MHz+ and XT variants as well as a release integrating the modem, just install it on its own if necessary
- v1.4.2
implemented Tiny RCU
re-enabled Samsung's bootanimation when there's no bootanimation.zip
re-added -noatime optimization script
XT variant: 1280MHz, config optimizations: HZ=500, PREEMPT_VOLUNTARY, UACCESS_WITH_MEMCPY, KSM (possibly unstable, slightly higher performance and battery drain, might be necessary to lower UV)
- v1.4.1
fixed BLN (flashing as update.zip or re-enabling it from CWM might be necessary)
- v1.4
raspdeep's OCUV updated to v217
implemented fastscaling for 100-400MHz frequencies
added 1280MHz variant (UV setting for 1200MHz applies to 1280MHz, so reset it)
ULF updated to pre-0.4, modified to support bootanimations
fixed potential /system corruption
integrated JK3 modem in CWM flash package
kernel version updated to reflect frequency variant (#140-1280 / #140-1200)
BLN has issues
- v1.3.5
removed config optimizations
removed -noatime remount script
(should provide stability for those experiencing hangups/reboots/charging issues)
- v1.2.6
removed config optimizations (should provide stability for those experiencing hangups/reboots/charging issues)
HZ=300
- v1.3.4
rebuilt from scratch
even more stability fixes
build # updated according to version (#134->v1.3.4)
- v1.2.5
rebuilt from scratch
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
fixed script execution
kernel HZ back to default
build # updated according to version (#125->v1.2.5)
- v1.3.3
fixed screen lock issue
kernel HZ lowered to 300
more stability fixes
supposedly fixed charging issues (oneclick to JF6, reset battery stats and masterclear)
- v1.3.2
stability fixes
- v1.3.1
included ext4 patches from [url]http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/[/url]
additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script
- v1.3
Corrected a small bug that was preventing scripts from running
updated raspdeep's OC/UV to v2.1
update [url=http://forum.xda-developers.com/showthread.php?t=829731]Xan's app[/url] to undervolt
- v1.2.1
hopefully fixed script execution on Captivate ROMs aswell
fixed CWM option for enabling BLN
fixed 500hz setting
enabled CONFIG_UACCESS_WITH_MEMCPY and CONFIG_PREEMPT_VOLUNTARY as they apparently make no difference in battery use
- v1.2
increased available RAM to 343Mb
updated BLN to v2.2
- v1.1.1
enabled init.d script execution on boot (Xan's app voltage settings are now being kept)
- v1.1
added BFQ I/O scheduler
updated Voodoo color&sharpness
BLN reverted to v2.0, now working (flashing from an update.zip is required to install the Library)
- v1.0.1
fixed JFS filesystem support, added bootanimations, BLN still not working (no clue why not, waiting for xcaliburinhand's upcoming update)
- v1.0
initial release
RESET ALL UV SETTINGS (DELETE INIT.D SCRIPTS) BEFORE UPGRADING TO HIGHER VERSIONS
IF YOU'RE HAVING SLEEP DEATH ISSUES, REVISE UV SETTINGS
Modules and mem config extracted from samsung's JPU kernel: DO NOT USE THIS KERNEL ON JPU FIRST BOOT OR YOU'LL GET AN ENDLESS VIBRATING BLACK SCREEN, BOOT ON SAMSUNG STOCK AND ONLY THEN FLASH THIS KERNEL
The XT variant is slightly faster but can cause instability (which might require higher voltage) and charging death.
Voltage Control 3 supports enabling higher frequencies from the freq table, but doesn't yet let you disable selective ones.
To disable a certain frequency its corresponding value in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table has to be set to '0'.
Changing update_states is no longer necessary. That file can either be manually edited or modified through an 'echo' command, which is much more convenient if you're in front of a PC and able to use ADB.
It's a volatile RAM file, which means changes made to it won't stick through reboots; I've included a script that reapplyies settings on boot in the CWM package (also attached to this post).
Let's say you wish to overclock to 1400MHz and disable 1288-1344:
1344MHz corresponds to the 6th value, 1288 to the 7th:
Code:
#!/system/bin/sh
#SET OC - below are GHz decimals (i.e. 1.60GHz, 1.55GHz, 1.50GHz and so on)
#60 55 48 44 40 34 28 20 00 .8 .4 .2 .1
[color=red]#[/color]echo 0 0 0 0 1 [color=blue]0[/color] [color=blue]0[/color] 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
REMEMBER TO REMOVE # FROM THE LAST LINE
jk3_modem_update.zip
SetiroN_v1.4.7xt_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1600.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7_1552.tar.7z [email protected] frequency - 194MHz GPU
SetiroN_v1.4.7xt_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7_1488.tar.7z [email protected] frequency - 186MHz GPU
SetiroN_v1.4.7xt_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7_1440.tar.7z [email protected] frequency - 205MHz GPU
SetiroN_v1.4.7xt_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1400.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7xt_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7_1344.tar.7z [email protected] frequency - 192MHz GPU
SetiroN_v1.4.7xt_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7_1288.tar.7z [email protected] frequency - 184MHz GPU
SetiroN_v1.4.7xt_1200.tar.7z [email protected] frequency - 200MHz GPU
SetiroN_v1.4.7_1200.tar.7z [email protected] frequency - 200MHz GPU
setiron_v1.5.6.tar.7z
setiron_v1.5.6_cwmupdate.zip
setiron_v1.5.6xt.tar.7z
setiron_v1.5.6xt_cwmupdate.zip
Voltage Control 3 alpha3

FINALLY! Going back to 2.2 so i can try this out. Can't wait for the link.
Sent from my Cappy using mental telepathy, *****ezz.

SetiroN said:
- neldar's v2.2 BackLight Notifications support
coming in the next release
Click to expand...
Click to collapse
Awwww that's a deal breaker for me, need bln badly. But yes finally, sztupy ulf on the cappy.

BLN now included, untested.

Awesome. I've been trying to figure out the how to do all this as well. I edited the code this morning at work and I just thought I'd check XDA while CodeSourcery finished installing...and what do I see?
I'll be flashing this immediately. FWIW, I've actually been running raspdeep's OC/UV 2.0 since Monday. I have it set at -100UVLF, -75UVHF, and I've had absolutely no problems with it at all, but it seems to be a YMMV situation. I don't think all processors can handle the UV. Even with (I think) unhelpful's, JAC's, and kingklick's kernels for the Galaxy S, phones handle the UV fine, some don't. Battery life is amazing with this though.
Also, I've had problems with screen off settings with setCPU. You probably don't want to use them at all.

SetiroN said:
BLN now included, untested.
Click to expand...
Click to collapse
that's some fast support...

Yes please. Link?

DOAlaboratories said:
that's some fast support...
Click to expand...
Click to collapse
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm

so has anyone run this yet? it seems pretty alpha and my phone just went into download mode to test it

By the way everyone - the UV is still what I think raspdeep considers alpha. You will probably want to stress your system a bit to ensure it can handle it. I found that with -100UVLF/-75UVHF flash video was a little bit choppier than with the settings at -75UVLF/-50UVHF.
That said, it has been steady for me over the last couple days, no problems at all with it. I can watch flash video and my CPU temps still stay under 100.
Also, link to xan's UV GUI seems to be missing - so here is another one.
And having alogcat installed and knowing how to use it would probably be the best practice if you want to help raspdeep make this even better.

Athailias said:
Can I get this uploaded in Shep's rom since he is "unavailable" until tomorrow Since you are so fast at making peoples dreams come true
/sarcasm
Click to expand...
Click to collapse
Just get in download mode and flash it over

SetiroN said:
I've compiled a Kernel based on Sztupy's ULF and xcaliburinhand's re-oriented kernels
Click to expand...
Click to collapse
Which version of reorient is this based on?
Thanks!
Since I see the compass patch works, it is at least version 2.1.1...

watch out, i think this may have master cleared me...
simething did at least.
no worries though, i have a whole SDCARD backup, so it's all good

This is freaking sweet. I am undoing voodoo at the moment and then will flash and give it a try. I am on the memory version of reorient at the moment so I will post back when results

it keeps booting intoa recovery loop on me after applying a lagfix

DOAlaboratories said:
it keeps booting intoa recovery loop on me after applying a lagfix
Click to expand...
Click to collapse
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.

BLN doesn't seem to be working. Yes I did enable it in the custom recovery menu, and yes I'm using a version of Mms.apk that supports "led notifications."

Has anyone tried with cogs new b2.3 rom yet? How is the battery life?

glitterballs said:
What lagfix are you trying to install? I got that with trying to use all=jfs, switching to all=ext4 worked.
Click to expand...
Click to collapse
JFS overkill was what did it me and obsessing over having the best ****.
i'll try RFS overkill and see if that works. also, after i got it to boot back up, it wouldn't install any apps

Can I flash this over Tayutama's Tom using ODIN? What slot do I put the file in?

MIUI freezing

Hi ,
I've just moved from cm7 to MIUI
Everything seems to be ok , apart from the fact the whole phone freezes for 2-5 seconds often. During this time the display doesn't change anything on the screen and the hardware buttons do not work.
So for example, if your moving left/right between the home screens - when the freeze happens it will show half of one home screen and half of the other.
It doesn't matter what your doing - there is no pattern to it. Its so annoying.
I've looked in the main thread for MIUI but found anything. Any ideas?

1) are you using latest build?
2) did you wipe cache AND data AND dalvik?
3) if nothing of above helps, then try to change vsel and/or default cpu clock
... I'm using MIUI for a while and I don't experience that problems

thanks for reply:
1) I think so - 1.12.16
2) Yep , wiped factory and cache x2 just to make sure.
3) this could be what Im after.
I've installed Milestone2 Toolbox and the overclock tool is showing
Clock 1 - 300 Vsel 17
Clock 2 - 600 Vsel 32
Clock 3 - 900 Vsel 44
Clock 4 - 1200 Vsel 60
I've tried flashing the Stock cpu/vsel values zip on the first page on the main thread: ( [ROM] [12/18] MIUI 1.12.16 GB 2.3.7 + ICS Multilanguage for Milestone 2!)
It seems that it hasnt worked - but I will try again.
NOTE - My MS2 has not rebooted itself like a lot of people who are having problems.

I tried again flashing the stock values zip from Clockwork - it looked like it worked.
Going into milestone2 toolbox however the values listed above are correct.
As such , I've changed the values manually using the milestone2 toolbox to endless cm7 values as specfied on page 35 of the main thread:
http://forum.xda-developers.com/showthread.php?t=1258073&page=35
After a few mins of use - it hasn't frozen yet.
Will give it a few hours and see how it behaves.

just to let you all know the changes above seemed to have worked

[Q] need help

helo guys i have been using [29 FEB][SD][MAGLDR] Yugoport´s MIUI / STABLE VERSION V2 / DEV VERSION V1
http://forum.xda-developers.com/showthread.php?t=1484003
rom since a week and the heat on the back side of my phone is little high than usual is it normal and when i enter a number and press cal button screen goes blank call connects and i can talk and disconnect using hard keys but screen wont turn on till i end the call please help me on this thanks guys
and this rom is perfect fast stable and full filled all my requirements thanks dev

you need clean install
İnstall teh rom from link again.And make clean install from your phone.Because ı have no same problem with same rom.

i have formatted the sd card and installed again but
thanks for your help
i have installed it again by formatting the sd card but the problem is same and sometimes data also dosent work unless reboot

try other rom bro
http://forum.xda-developers.com/showthread.php?t=1437463 try this rom it working full bro.

sai_kiranb said:
helo guys i have been using [29 FEB][SD][MAGLDR] Yugoport´s MIUI / STABLE VERSION V2 / DEV VERSION V1
http://forum.xda-developers.com/showthread.php?t=1484003
rom since a week and the heat on the back side of my phone is little high than usual is it normal and when i enter a number and press cal button screen goes blank call connects and i can talk and disconnect using hard keys but screen wont turn on till i end the call please help me on this thanks guys
and this rom is perfect fast stable and full filled all my requirements thanks dev
Click to expand...
Click to collapse
Is the CPU load high?
Check the system load with top (command line).
Or check the current CPU frequency with an app as AnTuTu CPU Master (if you don't want to overclock by accident just deny it root rights). When doing nothing, the clock frequency should be scaled back (to 245 MHz).
Even better, this command gives an overview of the relative time the CPU runs at the different scaled clock frequencies:
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

Deleted...

[Kernel][JellyBean] Devil3_1.7.5 [17/10/12] - Cappy

This kernel is based on teamhacksung's kernel for Jellybean
This kernel is meant be working on every Rom based on cm10
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me
Download link and changelog can be found here:
http://www.hellybean.com/jelly.html
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color

Changelog:
changelog 02.08.2012:
- bug fix to bln, to prevent kernel panic in some situations (thx to thalamus)
- switched from deep_idle 2 to idle2 (also thx to thalamus)
- updated kernel to linux 3.0.38
- dockaudio sysfs for captivate and fascinate
IDLE2 can be enabled with the following command:
echo 0 > /sys/module/cpuidle/parameters/idle2_disabled
IDLE2 can be disabled with the following command:
echo 1 > /sys/module/cpuidle/parameters/idle2_disabled
Stats can be obtained from the standard cpuidle interface, which, for
IDLE2 is located at:
/sys/devices/system/cpu/cpu0/cpuidle/state*/time
where * = 1, 2, 3
Click to expand...
Click to collapse
changelog 27.07.2012:
- hack mfc driver, to give all available mem to an application, if the requested mem is more than the max. available (maybe useful later, does not change anything right now (afaik))
- fix execution of boot-patch.sh, disabled twice execution of init.d, enabled tv-out server for all devices (i9000 already had this)
- battery: fix charging display for car dock
- increase read-ahead on moviNAND
changelog 25.07.2012 part2:
- fixed cwm backup and restore for kernels without /datadata partition
changelog 25.07.2012:
- updated recovery (no "sdcard format"-bug anymore, external sd card is named correctly)
- vibrant: hopefully fixed froyo ril
- jellybean: galaxy s settings working now
changelog 22.07.2012:
- updated kernal base to linux 3.0.36
- updated "block" to linux 3.3
- readded fiops io scheduler (kept cfq this time)
- updated cwm recovery to 6.0.1.0 (please create a new nandroid, because of possible incompatibilities between old/new recovery)
- compiled with linaro toolchain (gcc 4.7.1) and O3 compiler flags
- made uksm scan less often (save cpu time and power)
- at first boot: only delte init.d scripts created by other kernels
- increased usb write performance
- lowered ram and display voltages a little bit
- fixed some bugs related to devil settings (they should stick now after reboot, if set by one of the devil apps)
- support for scripts in /system/etc/shutdown.d (thx to Efpophis)
all scripts placed at /data/local/shutdown.d or /system/etc/shutdown.d get executed at shutdown/reboot
you can use this, to play a shutdown sound for example.
by default 00shutdown gets created, which plays a music file, when it is placed at one of these folders/places
/system/media/audio/ui/shutdown.ogg
/data/media/audio/ui/shutdown.ogg
Click to expand...
Click to collapse
- disabled some debugging options
- audio (and for fascinate: camera fixes) by Efpophis+
- patch for improving batterie life by CML
- nfts read/write driver built in (for use with usb host mode)
- reverted refreshrate_mod and gpu_oc mod, as both weren't working
changelog 18.06.2012:
- some changes to load balancing
- added ultra ksm (metioned by zach thx for this my friend)
- readded fiops io scheduler (still experimental and could cause instablilities)
- using snappy compression for zram now (2 times faster, but only 2% less compression)
- added the possibility to change zram size (at /data/local/devil/zram_size, with valid values: 50, 75, 100 and 150 (all in mb))
- fixed the applying of user_min/max freq after reboot
- vibrant: fixed gps
- fascinate: fixed nandroid in cwm recovery
what is ksm? http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)
uksm is more optimized and also working for single core systems. using this should give much better ram usage, but at the cost of more cpu usage
############# most probably not working (yet)##############
i have added seperate gpu oc from jt1134's galaxy_tab (to switch between 200 and 250 mhz), but i did not get any improvements in antutu...further tests needed
echo 1 > /sys/kernel/pvr_oc/pvr_oc (for 250 mhz)
echo 0 > /sys/kernel/pvr_oc/pvr_oc (for 200 mhz), no reboot needed
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
######################################################
changelog 10.06.2012:
cwm recovery:
- fixed mounting of external sd card to pc
kernel:
- picked two commits from linux 3.0.32 (avoid a possible memory leak, small fix to ext4 driver)
fascinate:
- fixed wrong mount points
changelog 09.06.2012:
- updated Zram and Zcache from linux 3.3
- updated android binder driver from linux 3.3
- fixed restoring of backups within TWRP recovery
- added virtual buttons to cwm recovery (Attention: they still don't work!)
- call vol hack from tk glitch (take a look at init.d folder and edit the script to make changes to call vol hack)
- bigmem values get applied at first boot after power on (if there is a value at /data/local/devil/bigmem, 1 for 391 mb and 2 for 403 mb (the last one breaks 720p)
- prevent phantom key presses (from tk glitch)
changelog 24.05.2012:
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- no need for activating/deactivating of selective live_oc anymore --> just change target low and target high
- BLX back in
- fixes to devil idle to be more stable while in call
- 1,5 mb more ram (thanks to mialwe)
- added aroma filemanager to cwm recovery
- added fully working TWRP recovery optional to cwm recovery (to use TWRP, just create a file named "twrp" at /cache)
- added option to select ram config in kernel --> no need for flashing an other kernel to get more ram (thanks to stratosk)
- switched to new initramfs from stratosk and mialwe ( now there will be cmw zip and odin tar file of every kernel version)
- added possibility to use Zram instead of Swap
- no need for flashing/using special scripts to make swap/zram working anymore
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
changelog 01.05.2012:
- all changes from cm9 stock kernel (including mount points option)
- some fine tuning to deadline and sio
- Devil Idle: limiting bus/ram/gpu speed to 100 mhz for 100-800 mhz cpu freq, while screen off (automatic mode) or always (permanet), both modes automatically reduce the int voltages of the affected freq by 50 mV
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
- rest oc_value to 100 while screen off, and back when screen turns on (combined with devil idle automatic, can't be turn on/off without devil idle)
- added posibility for different voltages while screen off (also bundled with devil_idle, with default settings, stock arm voltages are applied, because of live_oc set to 100)
- added the possibility to set freq limits while screen off (min and max freq)
19.04.2012
- even better fix to selective live_oc (last one (in test kernel) generated some overhead)
- fixed sampling rate of ondemand and conservative (have ported mialwe's/stratosk's sleep multipliers)
- new tunables for ondemand and conservativ
sleep multiplier and tunables:
mialwe and stratosk had the great idea, to change the sampling rate of conservative and ondemand governor while display of. for this, he introduced the sleepmultiplier (in his case factor 3). this means, if you set sampling rate to 20000, it changes to 60000 while screen off, and back, when screen on.
for ondemand and conservative:
i have made this multipliers tunable. proper values are between 1 and 5, because one could want a higher multiplier while screen off, if sampling rate is very low while screen on (higher sampling rate means, less checking for work load --> better batterie, worse performance). with this tunables you get better batterie, without making the performance worse while screen on.
two other tunables: up_threshold_min_freq and responsiveness_freq
the first one is a very low threshold while on low freq (by default 40), to make the governor scale up faster, until the responsiveness_freq is reached.
the responsiveness_freq is set to 400000 (400 mhz) by default. while the freq is below this value, up_threshold is the same as up_threshold_min_freq, and freq jumps to responsiveness_freq, with skipping the freq between the actual one and the responsiveness_freq. (conservative governor does not jump up to this step)
responsiveness_freq can be set to values between 100000 and 1400000
up_threshold_min_freq can be set to the same values as the normal up_threshold.
not tunable: while screen off, up_threshold is set to 95, no matter your other settings, to save more batterie.
up_threshold_min_freq is disbaled by default for conservative governor
for lulzactive:
for this governor, i did similar things, but they are not tunable till now.
when screen off:
- inc_cpu_load is set to 90, and back to the original value, when screen turns on
- up_sample_time is set to 50000, and back to the original value, when screen turns on
- down_sample_time is set to 40000, and back to the original value, when screen turns on
other changes:
- fix to touchwake from ezekeel, and another fix from stratosk
- upstream fix to compass
- building for i9000B now, too (big thanks to F4k for the hints by pn )
- removed some typos from recovery
- removed some annoying "no's" and "yes" from recovery in misc menu
- fixed wifi mode switch (pm_fast is the one with better signal)
14.04.2012:
- new b versions (only stock ram) changend to 377 mb, VC version needs the 720p fix from my ftp server. cmc version already patched
13.04.2012:
- updated wifi driver
- added the possibility to switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
- user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel, so it should be ok ), default is off, to be safe
- fixed voodoo color kernels (these have the VC in their names)
10.04.2012:
- added vibrator intensity control (by mialwe), presets can be changend in recovery
- stock ram version now available (348 mb ram), XL (390 mb), XL_bm (402 mb)
- removed 1080 mhz freq for now
- small correction to touchwake
- small correction to selective live_oc (now the low freq really are not live_oc'ed)
05.04.2012:
- fixed bug in selective live_oc, which caused the target high not taking affect to the highest freq, if highest freq equals target high
- fixed another bug in selective live_oc, which could lead to gpu crashes due to overclocking the ram, but not the cpu freq (for low steps)
- added a switch to change between "normal" and selective live_oc
by changing the live_oc mode while using it, live_oc value is set back to 100, to prevent strange things
- added possibility to set max. freq for boot (in recovery). This freq is set until init.d is executeted (it is automatically set to 1000 at this point, to make sure there are no conflicts with other cpu settings from users)
#Already in the last version, but i forgot about it:
- deep idle fixes from stratosk (many thanks)
- added possibility to underclock by using live_oc (limit is 90 now, which means lowering all freq and bus speed by 10%, to save more batterie when really needed)
03.04.2012:
For now there are three different RAM versions:
- stock mem kernel has 379 mb ram, everything working
- "slim ics" (XL) kernel comes with 390 mb, this is breaking playback of some high resolution videos
- XL_BM is coming with 402 mb ram, but breaking 720p
(while flashing the kernel, the modded rom files are also flashed, so you don't need to flash a new rom to get 379 or 390 mb)
-added new frequency: 1080 mhz (1100 does not like live_oc)
- fixed SmartassV2 for live_oc (after changing live_oc value, you have to change the smartass values, too, but then they automatically apply to the live_oc value (although you can only select 800 mhz in nstools (for example))
- touch recovery with custom devil menu (for some reason it takes a few seconds to load the first time, missing virtual keys is a warning, because there are no virtual keys yet)
-fast charge (thx to chad0989 for this), disabled by default.
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
- added datafix script to init.d (this script is deactivated by deafult. to make it work, you have to creat a file named datafix and placed in /data/local/)
- reworking and cleaning many parts to get more ram, speed, and stability
05.03.2012:
- updated sio i/o scheduler to latest version
- small updates to ondemand and conservative governor from linux 3.2
- bettter performance for CFS kernel due to tuning and patches
- tuning to deadline scheduler
- better i/o performance
- changed bootlogo (probably not the last time )
28.02.2012
- finally working bln V9 (no need for LED2 anymore)
- fixed lockscreen freezes
- reverted memory tweaks, which could be the reason for lagging after using a day
- again wlan fixes from tk-glitch
- tweaked conservative and ondemand governor (conservative still is not too aggressive)
- added dm-cache again (who has removed this from my github? )
- improve usb signal quality
- xcaliburinhand's dock audio support (untested, do not have a dock)
- less debugging
- fixed kernel version not displayed under "about phone"
12.02.2012
- Added newest Fiops scheduler (tuned for more performance)
- When Gpu is active, min CPU freq is set to second lowest step
- fixes to live_oc and custom voltage
- default mount parameter NOATIME and NODIRATIME (faster)
- updated Wifi drivers (thanks to tk-glitch)
- tuned intellidemand for better performance
- removed some stuff (zram, swap, tweaks to cpufreq untill I know what was causing the instabilities of last build)
05.02.2012
- added Touchwake
- added BLX
- upgraded BLN from V8 to V9 (working for missed calls, blinking or static light, configurabel by using NSTools or BLN Pro App)
- added Intellidemand governor
- added mdnie settings to voodoo color version
- readded deep idle v2 again (I think it is the best/only working one, although
- version with CFS (instead of BFS) now also available (maybe better multitasking and batterie life, but slower)
- removed BFQ I/O Scheduler
- tons of smaller fixes and improvements
30.01.2012
-revert: Voodoo Sound now to be set with DSP Manager
29.01.2012
- Linux kernel 3.1.10
- Deep Idle from Eugene373 (always enabled, no stats)
- added BFQ v 3.1 I/O Scheduler
- Voodoo Sound now to be set with DSP Manager
- Zram (can be disabled by removing Zram file from init.d)
- Zcache and Cleancache (not working yet?)
- optimized rwsem algorithm
- USB Host V5
24.01.2012
- init.d support (the folder is not created by the kernel. You have to do it for yourself)
- Deep Idle V2 back in
- new Cpu governors: MinMax, Lagfree, Lulzactiv
- LED V2 (you can set blinking by using nstools, also working for missed calls in most cases (sometimes it is not working for missed calls, don't know why at the moment))
- Backlight Dimmer (only LED version): used to turn led backlight of, while screen is on, after defined period of time. Deactivating it, makes your backlight stay on all the time
- I/O-less dirty throttling completely backported from kernel 3.2
- Ext4 with 3.2 patches
- Proportional Rate Reduction for TCP - by Google
- USB Host V 4
19.01.2012
- Usb Host drivers integrated
- Cm9 Color adjustment
- Removed Deep Idle because of Bluetooth problems (hopefully it will come back, still testing)
16.01.2012:
- Updated Kernel basis to Linux 3.1.9
15.01.2012:
- fixed bug in cpu spy, caused by live_oc
- still using voodoo color for now, maybe two additional kernel versions tomorrow
[/quote]
files with .zip have to be flashed within recovery (twrp or cwm)
files with .tar can be flashed by using odin or heimdall (they are placed at the end of post 3)
Downloads:
http://rootaxbox.no-ip.org/divers/jellybean/ many thanks to Rootax
http://devil.haxer.org/ many thanks to SysTem-X (not updatet yet)

just in case ...

First
Sent from my Cappy powered with Jelly Bean using Tapatalk 2

Continuing my discussion from ICS thread here. Either I effed up enabling Idle2 or running a internal Cat of kmsg is not letting my phone drop to idle . Can Idle 2 be enabled from the app or that needs to be implemented?
Edit: Got everything to work. Here is the KMSG that I got. The problem is, if I use ADB the phone doesn't activate Idle2 but i feel like making my phone cat kmsg while I'm trying to crash it might not get the whole txt? I could be wrong. Hope it provides more info.
Idle2kmsg.txt

Wait so what's the difference between deep_idle 2 and idle2? Anyways I'm going to flash it and see what's the difference!
Sent from my SGH-I897 using xda app-developers app

@DerTeufel
Apparently I don't get SoD with idle2, my phone locks up. Screen Actually showed lockscreen this time when I attempted to wake it up while playing music. Sadly my computer doesn't see the device during this state. Any advice? Did you take a look at the kmsg I provided in my earlier post?

Thanks for your contribution .

Can't get to recovery?
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?

Tsaukpaetra said:
Hello all, first time in Devil kernel.
First flash went well, I flashed and tested it was working by rebooting back into recovery. I set a few options (such as vibrate intensity) and rebooted, everything was OK (even better even, because Waze started working finally).
I did a 'touch /data/twrp' to try to enable the TWRP recovery, and rebooted, but now I'm kinda stuck at the kernel logo. Capacitive buttons do light up (but don't vibrate the phone), and I can reboot by holding all three hard buttons for ten seconds.
I noticed in the changelog that "for some reason" it takes a few seconds to start TWRP, but I waited for ten minutes (and dropped by battery 43%) before giving up. Coincidentally, now I'm getting the "android.process.media" has stopped error, waiting to see if a appdata wipe will help on that one...
Thing is, even after deleting the file I touched, it's still not letting me into Recovery (the normal CWM). Are there any hints at this? Or should I look at trying to get Heimdall working to try reflashing the kernel?
Click to expand...
Click to collapse
yes, i think best would be to reflash the kernel, and then try to get to recovery.

DerTeufel1980 said:
yes, i think best would be to reflash the kernel, and then try to get to recovery.
Click to expand...
Click to collapse
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...

Tsaukpaetra said:
Yeah, on the thoughts that it might have been a bad flash, I did try that. Now I've downloaded the 8/1 version for testing, we'll see what results. TWRP should be rom-independent, right?
I just don't know what else I might be doing wrong. Perhaps it's reading the TWRP information from a previous version and hanging up? Oh well, I supposed it can wait.
I renamed the TWRP file from a previous kernel's version and tried to reflash, but still no go...
Click to expand...
Click to collapse
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt

DerTeufel1980 said:
i think twrp is not working at the moment with jellybean. i try to fix this tomorrow.
till then, you have to go to cache and delte the twrp file from there. if this file isn't present, then please attch your /boot.txt
Click to expand...
Click to collapse
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.

Tsaukpaetra said:
Ok. Somehow the Devil Kernel Config app wasn't properly deleting the file, once I used an actual command to delete it, it worked OK to be in CWM recovery.
Just for kicks, I attached my /boot.txt log.
Click to expand...
Click to collapse
Boot.txt is fine now
Gesendet von meinem GT-I9000 mit Tapatalk 2

Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?

Tsaukpaetra said:
Just for clarification, doesn't the boot.txt file get overwritten each boot? So if I'm having issues getting into TWRP, and I reboot to get out of recovery mode, the boot.txt file will only give information about the current boot (not the broken TWRP)?
Click to expand...
Click to collapse
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2

DerTeufel1980 said:
Yes. That's right. It would have been helpful, if you grep it with adb, while stuck. I already did this now, and it wasn't helpful
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
One thing that always frustrated me was the fact that there is literally no way to watch the kernel messages on the display as it boots. That's one of my most trusted debug methods on the computer: Have it show what it's doing on the console.
Of course, there is a serial port somewhere, but it's apparently not easily accessible without special hardware...
Something just occurred to me: What if we could manually load the TWRP ramdisk and chroot into it? Would that allow us to interactively watch it? or (since stuff is already loaded and junk) that may not be possible? I noticed that adb starts, but we can't get a shell, so...

There is 1.1.3 kernel uploaded.
http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/
Sent from my SGH-I897 using xda premium

Search Button not working. Press it, not working, no response.. Have to go to the search app instead.
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.

The search button no longer invokes the normal search function in an app, instead it launched Google Now in Jelly Bean. If that feature is missing in your ROM, nothing will happen when you press it, you must press-and-hold instead.

[KERNEL] [2.6.35] 2157MHz CPU/320MHz GPU Overclocked Touchpad CM Kernel

Here's a custom kernel for you all to try out. It should work with any CM10.1 (some nightlies, but not all), CM10 or CM9 ROM that loads from moboot with uImage.CyanogenMod (if you don't understand what this means, don't use it). Pick your specific ROM. Not tested with all ROM's, so YMMV.
Here's a few facts:
Compiled with Linaro 4.7 toolchain
Complete with jcsullins patches for low power demand, wifi sleep, etc.
Complete with _Dorregaray's_ camera hooks
Improved entropy depletion routines speed file reads
Optimized AES and SHA1 encryption routines speed boot up and file decryption
Overclockable to 2157MHz if your ROM allows frequency settings
Level 2 frequency OC to 1914MHz
Stepped 2D & 3D GPU up to 320Mhz
Additional governors and schedulers
Use Kernel Tuner for tuneable parameters in the kernel
READ HERE FOR INFORMATION ABOUT GOVERNORS AND SCHEDULERS: Guide Link
Instructions: Download and flash the ROM version you currently have installed. No system/full wipes or cache clearing required.
CM9:
http://goo.im/devs/shumash/tenderloin/CM9_OC320-2157MHz_Kernel_08_23_2013.zip
CM10:
http://goo.im/devs/shumash/tenderloin/CM10_OC320-2157MHz_Kernel_08_30_2013.zip
CM10.1:
http://goo.im/devs/shumash/tenderloin/CM10.1_OC320-2157MHz_Kernel_08_22_2013.zip
http://goo.im/devs/shumash/tenderloin/CM10.1_OC320-2157MHz_Kernel_09_08_2013_Fixed_Rotation.zip
[CM10.1_xxxxNightly (should work with any nightly on or after each nightly date (_xxxxNightly part of the filename). It may work with other nightlies):
http://goo.im/devs/shumash/tenderloin/kernel/
[CM10.2_093013Nightly] :
http://goo.im/devs/shumash/tenderloin/kernel/CM10.2_0930nightly_OC320-2157MHz_Kernel_09_30_2013.zip
CHANGELOG
Code:
-> 30SEP13
- CM10.2 nightly build
-> 08SEP13
- CM10.1 build without Dorregaray MPU3050 updated driver (fixes rotation issue)
-> 22AUG13
- Properly enable gpu overclocking (milaq)
- Incorporate updated gyroscope userspace drivers (dorregaray)
-> 02AUG13
- remove abyssplug governor
- enable sysfs for GPU settings
- change to Linaro 4.7 toolchain
-> 26JULY13
- DERP: Fixed frandom number generator module not implemented in defconfig.
-> 25JULY13
- tune savagedzen governor
- add frandom number generator module
- Merge milaq: distinct localversion (nightlies only)
-> 24JULY13
- Add savagedzen governor (a modified smartassv2)
- Merge milaq: link and sync cpu governors (excluding policy refactor)
-> 15JULY13
- Incorporate ramdisk changes in 10.1 kernels
- Change scaled min power shutdown from 3% to 5%
- Allow L2 boost up to 1914MHz
- Remove hotplug governor
-> 27JUNE13
- Update deadline scheduler for improved android performance (milaq)
- Disable GENTLE_FAIR_SLEEPERS (milaq)
- rtc: alarm: Update hrtimer if alarm at the head of the queue is reprogrammed
- Add hotplug governor
-> 15JUNE13
- Change to arm-eabi-4.3.3 toolchain
- Cleanup frequency tables
- Add sio and vr schedulers
- Ramp processors up to 1512MHz at startup to decrease boot time
-> 02JUNE13
- Add lagfree governor
-> 11MAY13:
- Improve read speed of deadline scheduler
- Add badass governor
-> 06MAY13:
- Incorporate version specific ramdisk for CM9, CM10, & CM10.1
-> 04MAY13:
- Allow L2 overclocking up to 1890MHz
-> 22APR13:
- Stepped overclocking of GPU to 320MHz
-> 20MAR13: Initial upload

shumash said:
Here's a custom kernel for you all to try out. It should work with any ROM that loads from moboot with uImage.CyanogenMod (if you don't understand what this means, don't use it. You can, however, modify the update_script in the zip file to change the name to whatever you want.).
Here's a few facts:
Complete with jcsullins patches for low power demand, wifi sleep, etc.
Complete with _Dorregaray's_ camera hooks
Improved entropy depletion routines speed file reads
Optimized AES and SHA1 encryption routines speed boot up and file decryption
Overclockable to 2157MHz if your ROM allows frequency settings
Instructions: Download and flash. No system/full wipes or cache clearing required.
http://goo.im/devs/shumash/tenderloin/SKZ_OC2157MHz_Kernel-032013.zip
Click to expand...
Click to collapse
Just installed it. Running SGA's 03/08 cm10 unofficial. Everything running well.

Should you note that is this for CM10 or CM9? Does it work on both? I would be very surprised if you say yes!
Does it have the GPU O/C?

Gembino said:
Should you note that is this for CM10 or CM9? Does it work on both? I would be very surprised if you say yes!
Does it have the GPU O/C?
Click to expand...
Click to collapse
Don't know, but it's same kernel as CM9
No

shumash said:
Here's a custom kernel for you all to try out. It should work with any ROM that loads from moboot with uImage.CyanogenMod (if you don't understand what this means, don't use it. You can, however, modify the updater_script in the zip file to change the name to whatever you want, but it may not work).
Here's a few facts:
Complete with jcsullins patches for low power demand, wifi sleep, etc.
Complete with _Dorregaray's_ camera hooks
Improved entropy depletion routines speed file reads
Optimized AES and SHA1 encryption routines speed boot up and file decryption
Overclockable to 2157MHz if your ROM allows frequency settings
Instructions: Download and flash. No system/full wipes or cache clearing required.
http://goo.im/devs/shumash/tenderloin/SKZ_OC2157MHz_Kernel-032013.zip
Click to expand...
Click to collapse
I flashed it a couple hours ago over SGA's latest JB ROM. And I can't get the clock to steady step over ~1.89GHz on any governor. And the performance at 1.89GHz is worse than 1.78 as per my Antutu scores. I tried using the built in CM CPU settings, SetCPU and System Tuner and the situation is about the same.
There are times when it looks like I got the CPU to step up to 2.1GHz but when it's actually stuck at 1.188GHz.
So the setting are there but they're unusable. Any suggestions?

Gembino said:
Should you note that is this for CM10 or CM9? Does it work on both? I would be very surprised if you say yes!
Does it have the GPU O/C?
Click to expand...
Click to collapse
FWIW, I'm running the latest CM9 nightly and after I flash this kernel my Touchpad gets stuck on a black screen after the second boot splash image. The bootanimation would never start. I would have to hard reboot into moboot then flash a different kernel to get the TP to boot.

iamsamsamiam said:
I flashed it a couple hours ago over SGA's latest JB ROM. And I can't get the clock to steady step over ~1.89GHz on any governor. And the performance at 1.89GHz is worse than 1.78 as per my Antutu scores. I tried using the built in CM CPU settings, SetCPU and System Tuner and the situation is about the same.
There are times when it looks like I got the CPU to step up to 2.1GHz but when it's actually stuck at 1.188GHz.
So the setting are there but they're unusable. Any suggestions?
Click to expand...
Click to collapse
1. Have you tried setting to the performance governor? I had the same problem when I set to 2.157 GHz it didn't actually go above 1.836 GHz.
2. Also try rebooting and then try to set it again. Try using No Frills CPU Control.
3. Overclocking above 1.782 GHz doesn't seem to present any HUGE benefits right now. It will drastically lower your battery life.
4. Benchmarks don't really equate to real life performance.

Remolten said:
1. Have you tried setting to the performance governor? I had the same problem when I set to 2.157 GHz it didn't actually go above 1.836 GHz.
2. Also try rebooting and then try to set it again. Try using No Frills CPU Control.
3. Overclocking above 1.782 GHz doesn't seem to present any HUGE benefits right now. It will drastically lower your battery life.
4. Benchmarks don't really equate to real life performance.
Click to expand...
Click to collapse
1. I've tried every CPU speed above 1.782GHz in performance. And tried multiple of different speeds on interactive and ondemand. If I set it to anything over 1.782GHz it would get stuck 1.188GHz. Basically, CPU stepping is broken above 1.782GHz.
2. I've rebooted between all runs with different CPU apps. I don't know about No Frill CPU Control, but how would it be any different from the apps I've already used or the built in CM CPU control settings. I will try it out in a bit but I'm pretty sure it wouldn't really change anything.
3. Attempting to overclock over 1.782GHz seems to make the device slower in general.
4. Sure, benchmarks don't equal real world performance, but we're talking about less than half the score. Also, the entire device was just less responsive in general.

I set mine to 1.512 (which is the tp's true capacity), and 384, to deal with sod. I use the unofficial cm10, 03/08.Works well, so far.....

chicle_11 said:
I set mine to 1.512 (which is the tp's true capacity), and 384, to deal with sod. I use the unofficial cm10, 03/08.Works well, so far.....
Click to expand...
Click to collapse
1.5GHz is the TouchPad's true 'factory maximum CPU clock speed'. Who knows what its "true capacity" is. Many devices with very good SoCs have an overclock threshold of about 30-50% and it may get even higher and more stable with proper voltage controls. Right now we only have about a 20% overclock at 1.78GHz so the device should be able to handle a little more stress than we're giving it.

Re: [KERNEL][2.6.35] 2157MHZ Overclocked Touchpad CM Kernel
I flashed this kernel with cm9 but it doesn't mount the sdcard partition. Is there a fix? I really want to use the low power draw fix!
Sent from my Nexus 10 using Tapatalk HD

newellj79 said:
I flashed this kernel with cm9 but it doesn't mount the sdcard partition. Is there a fix? I really want to use the low power draw fix!
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Here is CM9 with the low power draw fix:
http://goo.im/devs/jcsullins/cmtouchpad/testing/cm-9-20130318-UNOFFICIAL-tenderloin.zip

Re: [KERNEL][2.6.35] 2157MHZ Overclocked Touchpad CM Kernel
newellj79 said:
I flashed this kernel with cm9 but it doesn't mount the sdcard partition. Is there a fix? I really want to use the low power draw fix!
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I used an updater script for CM10 that mounts the sdcard as sdcardd0. I should be able to put together a flushable zip that doesn't for CM9 users.
Sent from my skz_tenderloin using Tapatalk 2

jcsullins said:
Here is CM9 with the low power draw fix:
http://goo.im/devs/jcsullins/cmtouchpad/testing/cm-9-20130318-UNOFFICIAL-tenderloin.zip
Click to expand...
Click to collapse
Thanks so much for all your work, and for thinking of those of us still on CM9.
Is there an easy flashable (or pushable) implementation for the lower power draw, that could be applied by us to the nightly builds? Last I heard, the fix was not yet added to the nightlies.

waylo said:
Thanks so much for all your work, and for thinking of those of us still on CM9.
Is there an easy flashable (or pushable) implementation for the lower power draw, that could be applied by us to the nightly builds? Last I heard, the fix was not yet added to the nightlies.
Click to expand...
Click to collapse
Extract the boot.img from jcsullins zip. Take the latest nightly and unzip (when it asks to replace the terminfo stuff, select "no" or "no to all"). Delete the boot.img file in the unzipped nightly. Copy the jcsullins boot.img in its place (you can try copying mine if you want, but it may not boot). Rezip the files and flash.

shumash said:
Extract the boot.img from jcsullins zip. Take the latest nightly and unzip (when it asks to replace the terminfo stuff, select "no" or "no to all"). Delete the boot.img file in the unzipped nightly. Copy the jcsullins boot.img in its place (you can try copying mine if you want, but it may not boot). Rezip the files and flash.
Click to expand...
Click to collapse
Ahh, so essentially a kernel swap? I was unaware the power fixes were solely located here.
Thanks, will try.

iamsamsamiam said:
1.5GHz is the TouchPad's true 'factory maximum CPU clock speed'. Who knows what its "true capacity" is. Many devices with very good SoCs have an overclock threshold of about 30-50% and it may get even higher and more stable with proper voltage controls. Right now we only have about a 20% overclock at 1.78GHz so the device should be able to handle a little more stress than we're giving it.
Click to expand...
Click to collapse
I heard that a touchpad with a good SoC could OC to 2.4 Ghz if we had a proper kernel.

[UPDATE]New Upload
I've uploaded a kernel with CPU overclock to 2157MHz and GPU overclocked at 320MHz. Enjoy.

this was many months ago but i seem to recall that -sga- mentioned he saw no performance gains past a certain point. i think it was 1.7ghz but since it was a while back i don't really recall the exact number. or maybe he said diminishing returns past a certain point.
edit: i found his post about it http://forum.xda-developers.com/showpost.php?p=33883333&postcount=53
maybe he was talking about the ability to o/c past 1.7 was more difficult and not in regards to the performance gains?

HAH!
Flashed this!
in a fraction second by one after one the processes SystemUI And com.process.android.phone is Stopping.
I can't even use a single app.
using SCHIZOID 2.00 JB 4.2.2
plz help