Related
TKSGB KERNEL HAS BEEN RENAMED TO KGB KERNEL!
NEW THREAD HERE
PLEASE DISREGARD THE REST OF THIS POST
----------------------------------------------------------------------------------------------------------------------------
There aren't very many tweaks in yet but it should be stable again and a lot of ext4 and lowmemkiller lag issues should be gone! Here's an incomplete list of features.
Voodoo: Lagfix and sound. No color for now
CPU governors: The same ondemand, ondemandX, interactive, interactiveX, smartassv2 and ondemandX as default
I/O schedulers: The same cfq, bfqv2r1, sio, deadline, vr and deadline as default with the last three being optimized for flash
jhash3, OC/UV, BLNv9, 3rd-party batteries, boot animations
LED flashlight, CIFS and TUN
zram
User-adjustable in-call audio boost, no boost by default!
Preliminary dock audio support, need more feedback
Autogroups and Tiny RCU removed pending performance evaluation
How to adjust in-call audio and zram
Run callboost or zram from a root prompt (AS ROOT). To manually tweak zram size or call boost volumes, look in /etc/init.d/ for the startup scripts they drop after enabling. The filenames are 05zram and 91callboost.
Recommended settings for callboost are 1 or 2, 0, 0, and 0 or 1. zram is 12.5% of available RAM by default.
The zram script crashes when enabling if there isn't enough RAM free. Don't run zram enable unless you're sure you have enough RAM on hand, such as right after a fresh reboot.
How to use dock audio
Preliminary testing (thanks ACLakey even if you do have a Mesmerize ) indicates it does something right. I have no way to know if it's doing something wrong or even if it doesn't work at all so give me feedback.
How to use your phone as an access point
Get the latest Wireless Tether for Android (3.0b6 last I checked), and set mode to Samsung softap in the settings. It won't be peer-to-peer and WPA2 encryption will work.
"STABLE" DEVBUILD 1027
CWM zip: http://www.mediafire.com/?tjsadn6v0cocqy6
Odin: http://www.mediafire.com/?redm61dt4uwjpt2
Oh, and just because...
"BLEEDINGEDGE" DEVBUILD 1116
CWM zip: http://www.mediafire.com/?mg78n9a77sje6e4
Changelog: Drivers/kernel settings from EI20, except for the dpram driver which is still from EH09. Removed carrier hotspot tracking code in init.rc (doesn't make hotspot tracker directories in /system), ARM and memory and RCU updates/tweaks, changes to scripts in ramdisk.
Still pretty untested
P.S. Don't confuse one for the other, thanks
Please excuse the mess below.
----------------------------------------------------------------------------------------------------------------------------
Kernel is alpha and untested for the most part, and I cannot guarantee stability or robustness of features. Still, I've been using it every day for a few weeks now, and it's pretty stable for me. It should work on most EH09-based ROMs out there, including PowerWashed, GeeWiz and TSM Resurrection, just to name the ones I know as I am a Fascinate user. It works with Mesmerize and Showcase too, I'm given to understand, with the proper ROM tweaks (which I don't claim to know anything about).
FEATURES
Voodoo: Lagfix, Sound v10, and Color v2. Use with Voodoo Control.
CPU governors: conservative, performance, ondemand, ondemandX, interactive, interactiveX (ondemandX as default)
I/O schedulers: Noop, CFQ, BFQv2-r1, SIO, V(R), Deadline (deadline as default). The last 3 are optimized for use with flash memory.
Autogroups, jhash3, Tiny RCU for responsiveness.
OC/UV up to 1.7GHz, with Voltage Control/Pimp My CPU.
Third-party battery support allows use and charging of aftermarket batteries and batteries for other Galaxy S phones.
No hotspot monitoring with the WiFi driver from the i9000.
In-call audio boost: Higher volumes and mic gain settings. Works OK as of 10/18.
CIFS and TUN included in base kernel. UTF-8 native language support was already there.
BackLightNotifications v9 with a ported touchkey driver from the i9000. Automatic installation of the proper liblights. Use BLN Control and/or Blinky to get down to business.
Bootanimations: Works with /data/local/bootanimation.zip, /system/media/bootanimation.zip, or /system/media/sanim.zip. Automatic installation of the proper bootanimation binary.
LED flashlight: The camera LED makes a surprisingly good flashlight. Activate with any of a number of flashlight apps from the Android Market.
zram from Linux 3 (credit imoseyon). Open up a terminal and run "zram" to get started. By default "zram enable" will use 12.5% of total RAM as an LZO-compressed ramdisk and set up swap space on that. Don't run the script unless you have at least 50MB or so of RAM free. To change the size of the zram, edit the relevant line in /etc/init.d/05zram (it's in bytes, do your own math) and reboot.
Other standard features: init.d support, adb shell gives you a root prompt
Various behind-the-scenes tweaks: A growing list of ARM and Samsung kernel/driver patches for hardware errata and Linux kernel patches to enhance interactivity
CHANGELOG
For complete changes refer to github.
Code:
[size=4][B]1018[/B][/size] Most changes on this one are behind the scenes.
[b]In-Call volume boost changes[/b] +12dB at earpiece only & mic gain boosts
[b]Update interactiveX and ondemandX CPU governors[/b]
[b]ondemandX as default[/b] i'm pretty sure this is a backport from linux 3 too
[b]Use CodeSourcery 2010q1 toolchain[/b] bad Linaro, bad!
[b]zram backport[/b] and add zram script to initramfs
[b]Memory tweaks[/b] optimize memcpy functions, tweak lowmemorykiller
[b]Bugfixes[/b] to autogroups and a couple other things
[b]initramfs changes[/b] probably falls under bugfixes actually
[size=4][B]1012[/B][/size]
[b]In-Call volume boost changes[/b]
[b]dvfs lock fixed[/b], no more pegging CPU at 1440MHz with bluetooth
[b]lowmemkiller settings[/b] changed in init.rc
[size=4][B]1010[/B][/size]
[b]In-Call Volume boost[/b] numbers were chosen arbitrarily, need detailed feedback
[b]Autogroups, [strike]Tiny Preempt RCU[/strike][/b] woopz
[b]Bootanimation support[/b] install required binary on boot
[b]Add ondemandX CPU governor[/b]
[b]ondemand as default[/b] interactiveX pegs the CPU high on hw video playback
[b]optimize sio and vr[/b] for flash devices
[b]Voodoo Color fix[/b] no more green tint at low brightness
[b]More tweaks[/b] ARM, Samsung, buildflags; see github
[size=4][b]1006[/b][/size]
[b]Third-party battery support[/b] apparently works fine as of 10/10
[size=4][b]1005[/b][/size]
[b]BackLight Notifications[/b], neldar-flavored, finally!
[b]Installs liblights on boot[/b]
[b]deadline scheduler[/b] tweaked for flash memory
[b]interactiveX governor is default[/b]
[size=4][b]0927[/b][/size]
[b]Initial release[/b]
KNOWN ISSUES/TO-DO LIST
Dock audio: I've almost got this merged but have no dock and no way to test.
Lots more tweaks and testing. I know it isn't fully polished and some things could use cleanup and updating. There is also a veritable sea of tweaks out there that I haven't even started parsing through.
Autorooting, autoinstall of busybox, bash, nano, and a bunch of obnoxious init.d scripts
Recovery with crazy rainbow colors and logos, etc.
TKS does not yet come with CWM. The version most of you are using is probably the blue ClockworkMod Recovery 3.0.2.8x by I believe times_infinity. It's pretty compatible with my kernel with a couple of minor bugs. Mirrors: http://www.mediafire.com/?91cq99066cwph4d http://www.multiupload.com/QEP9U2MC2G
CWM-FLASHABLE ZIPS
NEW 1018 http://www.mediafire.com/?07nero2764ktcn4 http://www.multiupload.com/V81P3FNJOD
1012: http://www.multiupload.com/JFLEF7U7EH
1010: http://www.mediafire.com/?9f58oks4a988a7o http://www.multiupload.com/PDXE2U08IG
1006: http://www.mediafire.com/?ev1g554de7ab9g0 http://www.multiupload.com/KB7833E0E4
1005: http://www.mediafire.com/?em8md8yxq7o61ny http://www.multiupload.com/EHJFAPYW51
0927: http://www.mediafire.com/?76ea7izaqc3e7a2 http://www.multiupload.com/O1HRXNCQQW
ODIN TARS
NEW 1018: http://www.mediafire.com/?didta4h7vk0uh8p http://www.multiupload.com/EXS2REYBAI
1012: http://www.multiupload.com/W8VZQGA3AG
1010: http://www.mediafire.com/?2tiiwoeav61ha0f http://www.multiupload.com/4XORWQIQIZ
1006: http://www.mediafire.com/?p9u3ow2mw70n26c http://www.multiupload.com/58XYU7OF86
1005: http://www.mediafire.com/?5ojvasq4lurvxnp http://www.multiupload.com/4W2GPSZHU7
0927: http://www.mediafire.com/?rqwe26c1pi4766r http://www.multiupload.com/JST3N8AAIP
GITHUB
All I do is kang other people's work, get it?
https://github.com/kangtastic
Also where you can see the full changelogs.
THANKS
imoseyon: Merged Voodoo Lagfix by hand. Also, he and the next two guys and I are like the only ones doing anything with the TW GB kernel on this phone.
ccampos784: Merged Voodoo Sound, and some other dev work before I forked his branch.
djp952: Ported the i9000's Wi-Fi driver and killed VZ's hotspot monitoring dead. It wasn't the only thing he ported from the i9000 to get EH09 building. And on that note...
The Samsung Galaxy S i9000: It is truly the gift that keeps on giving. Comparing good work i9000 people have done on the i9000 and CM7 repos with the EH09 code makes broken things work again, period.
TeamSbrissenMod & Supporters: The TSM-Resurrection ROM got me to try EH09, but they've done lots of great work over the last year.
jt1134: Got me started with cross-compiling my first kernel, and he is responsible for most of the innovation on this phone.
Other "historically important" people: adrynalyne, imnuts, SirGatez, nemesis2all, navenedrob etc.
IRC people too numerous to list and random people too numerous to list from whom I have taken all sorts of ideas and code that ended up in this kernel
DISCLAIMER
I am not a developer and the sole reason I started was so that I could be happier with the kernel I use on my own phone. If something does not get added or fixed, you are welcome to do it yourself.
I take no responsibility for exploding phones, voided warranties, missed appointments, dead babies and the like which are claimed to be related to your decision to use my kernel in any way. You're in the "development forum."
That said, feel free to leave useful feedback and suggestions. For bug reports, link logcats and dmesg output. And enjoy!
INFORMATION REGARDING OC/UV VALUES
The default values in the Samsung source are as follows:
1000MHz arm_volt=1275mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1100mV
400MHz arm_volt=1050mV int_volt=1100mV
200MHz arm_volt=950mV int_volt=1100mV
100MHz arm_volt=950mV int_volt=1000mV
arm_volt_max=1350mV int_volt_max=1250mV
Of these the values that everyone talks about are the arm_volt values. arm_volt is what is modified by Voltage Control, Pimp My CPU, etc. int_volt is a secondary line that is not reported or directly adjustable by the user. The Glitch kernel plays around with int_volt for their different "leakage" versions, demonstrating that int_volt, too, plays a significant role in max overclock, but this isn't a concern of mine at the moment.
arm_volt_max is set to 1350mV which would then be the theoretical "overvolting limit". In this example you could overvolt 1000MHz by up to +75mV before running into driver limits.
Here are the default values in TKS.
1700MHz arm_volt=1500mV int_volt=1250mV
1600MHz arm_volt=1500mV int_volt=1250mV
1500MHz arm_volt=1500mV int_volt=1225mV
1440MHz arm_volt=1500mV int_volt=1200mV
1400MHz arm_volt=1450mV int_volt=1175mV
1300MHz arm_volt=1400mV int_volt=1150mV
1200MHz arm_volt=1350mV int_volt=1125mV
1000MHz arm_volt=1250mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1050mV
400MHz arm_volt=1050mV int_volt=1050mV
200MHz arm_volt=950mV int_volt=1050mV
100MHz arm_volt=950mV int_volt=1050mV
arm_volt_max=1500mV int_volt_max=1250mV
Let's look at 100-1000MHz first. At 1000MHz there is a slight -25mV arm_volt undervolt (or just plain old undervolt) as well as a -50mV drop in int_volt for all frequencies <1000MHz. In other words, for stock frequencies there is already an undervolt built right in that you should take into account.
At higher clock settings the values are essentially best guesses at the proper settings for that speed, refined by community experience, so talking about a "proper" undervolt level is a little bit inaccurate. Note that voltage is maxed out at 1440MHz and above, but the secondary int_volt values keep increasing. The effect is a ramping up of total power supplied with increasing clockspeed, as it should be.
So I wouldn't be at all surprised to see 100-1000MHz benefitting from a couple +25mV boosts compared to "the settings I used to use on my old kernel" here and there and I'd pay attention to differences between the default voltages, especially 1200MHz+, of the old and new kernels. With different defaults, seemingly different undervolt settings could translate into the exact same amount of mV supplied.
awesome man...great to see eh09 finally getting some kernel love
hopefully once imoseyen gets his i500 from someone sending it, u can get some more help as well
(if u bet bln working ill reactive my fascinate for awhile lol)
I can give feedback about what DOES work despite being in alpha stage:
Voodoo color is working (personally, I like to go "punchy" on gamma hack)
OC is stable at least to 1400 for me with default noop/interactive, and with 100mhz state disabled (I could only go up to 1200 on MIUI without immediate instability on Glitch)
My phone is quite stable (so far) on this kernel, more so than what you'd expect on an alpha release
I'm glad you posted your own thread for this kernel comeradesven
Another Fascinating post by my XDA app...
This kernel is what I've been looking for
With a battery fix and in-call volume fix, I think I'll have a permanent GB solution! I'm hard of hearing and most of these GB kernels just don't cut it for me. CM7 (MTD) works, but Slacker caching doesn't work because of the file system. Slacker says tough s**t, we're not supporting it. So here we are. I'll put this on my spare Fassy and test it out today.
I'm also hard of hearing, but in-call isn't too, too bad for me on speakerphone... Media volume, on the other hand... IDK if media volume has anything to do with this kernel or if it's an EH09 issue...
Another Fascinating post by my XDA app...
Does this kernel use the Nexus S color source like on Glitch's kernel?
FDro said:
Does this kernel use the Nexus S color source like on Glitch's kernel?
Click to expand...
Click to collapse
If you're talking about mDNIe values, then no. I tried adding some new values earlier and it didn't work. It does have a ported Nexus S framebuffer driver like all Voodoo Color kernels AFAIK.
Awsome work sir!!
which one is better... voltage control or pimpmycpu?
now i use voltage control oc up to 1400 with uv 50 all way down. so far run smooth.
i use noop and ondemand, if i use conservative then phone get lag
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
djblu said:
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
will this eventually have a -100uv kernel. i've the best battery life using pbj kernels with that setup. hope this gets it too. will switch kernels once all the kinks get worked out.
thx for your efforts.
mgrimmenator said:
will this eventually have a -100uv kernel.
Click to expand...
Click to collapse
Voltage Control = roll your own undervolt
The only real missing feature is BLN.
Can't seem to get it to download on my fiancee's phone.
Just flashed 9-27 through cwm and flashlight confirmed working. Awesome job
sent from my SCH-I500 PWGB 2. 0b3 voodoo , shot v7
Does this kernel support non OEM batteries?
Idea: RAM optimization, if feasible
Another Fascinating post by my XDA app...
So far this kernel is working out great for me. Loving voodoo color. Makes me wish I waited on buying that Thunderbolt off eBay. The cwm file didnt work for me (probably a bad download, stayed on bootanimation for WAY too long, lagging the animation) so I used the Odin version instead. Booted instantly. Many thanks for putting this together.
Sent from my SCH-I500 using Tapatalk
Originally Posted by djblu
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
Click to expand...
Click to collapse
Thanks for the clarification. next question:
how do keep from getting stuck in boot loop? Do I need to reflash my recovery immediately after flashinging the kernal?
Sent from my SCH-I500 using xda premium
[ Info ]
RC-1 Released
[ WARNING ]
Use this at your own risk!!
I am not responsible for any damange to your phone, pc, that you will get fired because alarm doesn't work
[ Features ]
- Overclock up to 1,15GHZ DON'T OVERCLOCK, JUST SELECT THE 1GHZ OPTION IN OVERCLOCK APP
- Cpu governess
- I/O Schedulers
- Recovery
- lots of new drivers
- Smooth
[ How to install ]
1. Download the boot.img
2. Flash it with fastboot (Fastboot flash boot boot.img)
3. Go to recovery, advanced and wipe dalvik cache!
4. reboot
5. ENJOY!!
READ THE FULL THREAD BEFORE ASKING ANY QUERIES OR REPORTING ANY BUGS/ISSUES
Credits:
Krabappel2548
Doomlord
KeiranFTW
Kamarush
ThJap!
Deepunknown
Shaan (S Advance)
Munjeni
my sources: https://github.com/nickholtus
Nick
If you want to user abt of thuis files, pm me first
Downloads:
Kernel: RC-1 Boot.img
just realised: this is my 1000ste post here on xda
RC-1
-Totally rebased the kernel
-Mainstream update 3.0.69
-Updated st-ericsson drivers
-Added lots of fixes (more then 80!)
-Added governers
-Added I/O schedulers
-A lot of other things!!!
-DONT USE OC, JUST USE THE 1 GHZ OPTION, otherwise system will lag. Will be removed in next version, this oc option was for test purposes)
last one
reserved..
just in case
Are the sources for Xperia P and U out?
yes they are
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
cezarL said:
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
Click to expand...
Click to collapse
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
krabappel2548 said:
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
Click to expand...
Click to collapse
Choice is good, but so many governors? I am no expert on this matter, which is exactly my point. Someone with a good understanding on how governors work should add options for, say, three scenario's:
- Performance. When needed, throttle to max. overclocked speed and switch to faster speeds sooner
- Medium, scenario between energy saving and performance.
- Energysaving. Do not overclock, set the clock the lowest setting possible when screen off, sleep mode and use moderate throttling just enough to ensure the device doesn't feel laggy but isn't as snappy as Performance.
Or.. post the settings for these scenario's here
hi,
i just added 4 governes
most of them are stock
ok good news
After a lot of testing, editing etc with Krabappel2548 we have got more frequences
normally we have 4 freq, now we have got 7 working
Release: Soon
also added 1.2ghz (if everything goes well)
Awesome work guys!
Just a couple of days of struggling with study, and then I''ll finally have some time to experiment with the phone. Hopefully this new kernel will allow a nice improvement in battery life
have a little improvement in battery life.
working on that...
nickholtus said:
have a little improvement in battery life.
working on that...
Click to expand...
Click to collapse
Yes, we are working on the kernel, we just added extra governors, I/O schedulars and extra CPU freq
ICS kerrnel v2 is released and on the Fileserver now Nick, maybe a little changlog?
quick panel
--
krabappel2548 said:
ICS kerrnel v2 is released and on the Fileserver now
Click to expand...
Click to collapse
Flashed v2, very slowly, even in his native launcher in ondemand mode.
On V1 was ok, only 2 times rebooted itself in sleep mode.
select another governer
conservative is fast
v2b or v3 will be released today or tomorrow without any lag
nickholtus said:
ok good news
...
also added 1.2ghz (if everything goes well)
Click to expand...
Click to collapse
Is there any problems with 1.2 GHz freq that you didn't include it to the ROM For now the highest freq is 1.15GHz...
no didn't add it
maybe in the next update (if we get some things figured out)
LuPuS Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello there, I was reading about Governors on a thread
and was curious about these governors that I hadn't seen before and wanted to try them.
So then I came across this great thread by paxChristos and decided I would try compile a kernel with new Governors and io-scheduler.
I've taken out a couple of things while compiling the kernel as well. I have been using it for a good few days now
and thought I should share these Governors to other Xplay users.
I googled for a name and came across LuPuS :highfive: that is why the boot logo is what it is
Well hope you all enjoy and I will be adding more governors soon when I get time
Thanks to all those who have helped me making this, paxChristos for his advice & tutorial.
Lightnindude, FXP and Cyanogenmod for their sources :good:
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"]<std_disclaimer.h>[/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/
[COLOR="Magenta"]#ifdef[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience you [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR][/COLOR]
What Works --
Wifi - (flash modules)
Data
Camera
Panorama
Video Recording (720p now works)
Video Playback
Front Camera
Bluetooth
Everything Else that works on FXP & Mjolnir
What doesn't work --
ALS (Disabled)
Anything that doesn't work on FXP & Mjolnir
Included in kernel
[/LIST]
Added Io-schedulers --
- Noop
- Anticipatory
- Deadline
- CFQ
- BFQ
- SIO
Added Governors --
- lagfree
- brazillianwax
- smoothass
- scary
- savagedzen
- smartass
- smartassv2
- interactivex
- minmax
- powersave
- performance
- conservative
- ondemand
- interactive
- userspace
+
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
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.
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Superbad -
A "superbad" super smooth rendition of a highly optimized "smartass" governor!
Darkside -
A "slightly more agressive smart" optimized governor!
What else-----
-SLQB - (SLAB allocator with Queue)-(both)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
- Added Cleancache
- Supports ext 2,3
- Updated zRam
- Lzo compression/decompression speed has doubled on average.
- Init.d support
- Fudgeswap
- And much more
- O/C and stable upto 2ghz, although I do not recommend O/C to 2ghz for long periods of time, do so at your own risk.
Show your support for the kernel and my work by putting this in your signature, its only a quick one I done up with my limited time
Code:
http://i.imgur.com/xtWNL.png
Downloads in post 2
Instructions for the CWM Recovery And Aroma File Manager--
--When phone vibrates tap the back key to enter CWM Recovery v6.
--When phone vibrates tap the volume down key to enter Aroma File Manager
I would like to say a big thanks to -
paxChristos - Tutorial / Help
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Jerpelea
KeiranFTW - for his PNG to RLE conversion script
Lightningdude - Sources / Help
FXP - Sources
Cyanogenmod - Souces
DooMLoRD - Everything he's done for XPLay
Supervenom - For the amazing AOKP rom
Solomon4400 - For helping me test (there where a few dodgy ones before I got it to work random reboots and stuff )
CosmicDan - For the amazing CWM / Aroma File Manager - AND LuPuS MIUI[CM9 BASED]
tempest918 - For the New Logo
amarullz - For Aroma File Manager
Kernel sources -b ics
https://github.com/garwedgess/LuPuS-CM-iCs
Changelog
*** Previous changelog was messed up so I'll include everything in here ***
Code:
[B][U]v9[/U][/B]
- Improved Battery Life alot :)
- Thumbee support
- EXT 2/3 & 4 supported
- Init.d supported
- Init.d scripts added (run at boot)
- SLQB Memory allocator
- ARM7 optimizations
- Brought OC back down to 1.6 max (no need for it above 1.6 unless u want to kill your device)
- Kernel sources completely reworked started from scratch o Sony xx.587 sources
- Tiny RCU
- Updatedd patched and fixed LZO
- lowered vfs cache pressure
- Increased Wifi- Range and added support for channel 14
- 0 % Battery patch - Thanks @ Bazoocaze
- Better memory copy
- Better memory move
- Deep sleep issue fixed
- LMK Optimizations (LowMemoryKiller)
- VDD support (voltage conrol)
- Linaro Optimzations
- Compaction added
- KSM
- CIFS (improved support)
- NTFS
- Updated to newest SIO Io-Scheduler
- Google Snappy Compress & Decompress
- Added Vibrate To Recovery (Notification to enter CWM)
- Wifi module size drasticly reduced
** Possibly missing a few things **
Downloads
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
So zRam does not work on them, below i've added a zram enabler .zip to flash via CWM[/B]
- If for whatever reason you want to disable Zram after you have flashed the .zip, just go to ect/init.d and delete 00zram
Wifi-modules included - Thanks @ CosmicDan
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
v9-LiNaRo-480p Recording
LuPuS-v9-480.img
MD5 = 3b33c08252a845e7cd8374d112f05e9f
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
v9 LiNaRo-720p Recording
LuPuS-v9-720.img
MD5 = 225f5abdfc30643e9763ff3ad95c17af
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
People will ask so i'll just post it here---------to check if zRam is enabled go to terminal emulator or similar and type
Code:
free
or alternatively
Code:
cat /proc/swaps
Please Click Thanks :good:
Great, I'll try it! :good:
Alejandroch said:
Great, I'll try it! :good:
Click to expand...
Click to collapse
Cool make sure you download and flash the the wifi modules in CWM!!
Yo I highly rate this kernel and the dev he is really great! Gratz wedgess do your thing.
Sent from my R800i using xda app-developers app
Cool thanks for the great work, the Intellidemand governor sounds very interesting.....!
Thanks for sharing your source, I like to strip system down to 240MB to give data some more space.
EDIT: I have shared with you my RAMDisk image for your consideration wedgess, maybe you will like it. It is taken from latest CM9 Ramdisk with the following changes:
- Replaced FreeXperia Recovery with DoomLords' Recovery
- Changed Recovery key to Back (instead of Volume-Down) and added a short vibration (just like DoomKernel)
- Bootlogo unchanged, still original FXP one
- Maybe some other small things, can't remember. Tree-compare it to FXP Ramdisk if you like to make sure.
I would release my own kernel with these changes but we already have two CM9-based kernels now, I don't really want to!
CosmicDan said:
Cool thanks for the great work, the Intellidemand governor sounds very interesting.....!
Thanks for sharing your source, I like to strip system down to 240MB to give data some more space.
EDIT: I have shared with you my RAMDisk image for your consideration wedgess, maybe you will like it. It is taken from latest CM9 Ramdisk with the following changes:
- Replaced FreeXperia Recovery with DoomLords' Recovery
- Changed Recovery key to Back (instead of Volume-Down) and added a short vibration (just like DoomKernel)
- Bootlogo unchanged, still original FXP one
- Maybe some other small things, can't remember. Tree-compare it to FXP Ramdisk if you like to make sure.
I would release my own kernel with these changes but we already have two CM9-based kernels now, I don't really want to!
Click to expand...
Click to collapse
Thanks intellidemand is great, its the governor I'm using at the moment. Recovery should already be the BACK button as I edited the ramdisk with my own boot logo and sbin. I used dooms touch recovery before but just wanted something simple if people want I could change eventually
Sent from my Xperia Play using xda premium
wedgess said:
Thanks intellidemand is great, its the governor I'm using at the moment. Recovery should already be the BACK button as I edited the ramdisk with my own boot logo and sbin. I used dooms touch recovery before but just wanted something simple if people want I could change eventually
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
Did you add vibrate too? I always miss the trigger on FXP kernel lol. I don't like the full Touch Recovery either because you can't see long filenames properly, but the one from his ICS Beta kernel is just like CWM Recovery.. but it does have the touch-enabled buttons down the bottom, or is that the same one you mean...? I understand it can be annoying bumping the screen on that and making a mistake selection, but DoomLord Recovery has some useful features... power-off is a good example, I hate having to pull the battery out to power off (seems dangerous).
Well yeah let the crowd decide, nothing is stopping me from repacking it myself for my use of course Cheers.
CosmicDan said:
Did you add vibrate too? I always miss the trigger on FXP kernel lol. I don't like the full Touch Recovery either because you can't see long filenames properly, but the one from his ICS Beta kernel is just like CWM Recovery.. but it does have the touch-enabled buttons down the bottom, or is that the same one you mean...? I understand it can be annoying bumping the screen on that and making a mistake selection, but DoomLord Recovery has some useful features... power-off is a good example, I hate having to pull the battery out to power off (seems dangerous).
Well yeah let the crowd decide, nothing is stopping me from repacking it myself for my use of course Cheers.
Click to expand...
Click to collapse
Haha ye that's the one I mean just personally prefer the original CWM, I agree with the power off but I just reboot system now and don't battery pull I'm open to suggestions though maybe I could make a version for people who prefer it that way??
Sent from my Xperia Play using xda premium
wedgess said:
Haha ye that's the one I mean just personally prefer the original CWM, I agree with the power off but I just reboot system now and don't battery pull I'm open to suggestions though maybe I could make a version for people who prefer it that way??
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
Here's an idea. Keep Vol-Down as FreeXperia Recovery (as it is originally), Back key as DoomLord Recovery, and Menu key as Aroma FileManager? That would be KICKASS. Looking at bootrec and bootrec-device scripts in sbin, seems easy enough to do! If you like that and would like a hand, send me a PM! Or we can keep bumping the thread discussing it :laugh: (Why not, valid dev. discussion that everyone can learn from)
CosmicDan said:
Here's an idea. Keep Vol-Down as FreeXperia Recovery (as it is originally), Back key as DoomLord Recovery, and Menu key as Aroma FileManager? That would be KICKASS. Looking at bootrec and bootrec-device scripts in sbin, seems easy enough to do! If you like that and would like a hand, send me a PM! Or we can keep bumping the thread discussing it :laugh: (Why not, valid dev. discussion that everyone can learn from)
Click to expand...
Click to collapse
this would be great, two days ago i was just looking on how to insert the doomlord recovery in the FXP kernel XD
Good work
Good work man.
:good:
I was reading your post and I thing governor: Lulzactive is not very effective.
I'm not phone deveolper, I'm only normal programmer.
So if I am wrong please explain.
I think it will make cpu freq very jumping, in every interval.
x=>60 - higher state
x<60 - lower state
so in average load it will do something like: ^v^v^v^v (higher->lower->higher->lower...)
what about:
x>60 - higher state
x<60&&x>40 - stay
x<40 - lower state
Gh61 said:
Good work man.
:good:
I was reading your post and I thing governor: Lulzactive is not very effective.
I'm not phone deveolper, I'm only normal programmer.
So if I am wrong please explain.
I think it will make cpu freq very jumping, in every interval.
x=>60 - higher state
x<60 - lower state
so in average load it will do something like: ^v^v^v^v (higher->lower->higher->lower...)
what about:
x>60 - higher state
x<60&&x>40 - stay
x<40 - lower state
Click to expand...
Click to collapse
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency. THIS IS THE VERSION IT IS NOW
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
I WILL CHANGE TO THIS ONE IN A COUPLE OF DAYS
I will leave the old version in there and put the newer one as v2
Click thanks if you like this
wedgess said:
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency. THIS IS THE VERSION IT IS NOW
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
I WILL CHANGE TO THIS ONE IN A COUPLE OF DAYS
I will leave the old version in there and put the newer one as v2
Click thanks if you like this
Click to expand...
Click to collapse
Sounds good, yeah the whole stay-at-current-if-between-60-and-40-percent is not really the nature of lulzactive, it's designed to have very responsive ramping. If you want a "stable" governor give the ondemand a go (or one of the ones it's based on, such as interactive or interactivex). Lulzactive is like a mix between interactive and smartass. Reference: http://forum.xda-developers.com/showthread.php?t=1369817
At the moment I'm having problems with lulzactive2 but if I can't fix it I still have other ones which I've added and am currently testing some of them. More to come....
Sent from my Xperia Play using xda premium
wedgess said:
At the moment I'm having problems with lulzactive2 but if I can't fix it I still have other ones which I've added and am currently testing some of them. More to come....
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
...such as bfq scheduler and all three FXP-Recovery/DoomLord-Recovery/AromaFM ;D
EDIT: It should be noted that this kernel is based on the official CyanogenMod 9 RC2 release for the Xperia Play, not FXP-CM9. I don't know how different it will behave but there are a lot of sourcecode changes compared to the FXP-CM9.
CosmicDan said:
...such as bfq scheduler and all three FXP-Recovery/DoomLord-Recovery/AromaFM ;D
EDIT: It should be noted that this kernel is based on the official CyanogenMod 9 RC2 release for the Xperia Play, not FXP-CM9. I don't know how different it will behave but there are a lot of sourcecode changes compared to the FXP-CM9.
Click to expand...
Click to collapse
Fxp is CyanogenMod for xperia.
Sent from my R800x using xda app-developers app
idiotzach15 said:
Fxp is CyanogenMod for xperia.
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Yes I know that, but FXP is an unsupported and unofficial fork. This kernel however, based on official cm9 for zeus, has been modified for inclusion into the official CM9 device tree. There are a LOT of source-level differences, for example the official CM9 for zeus (including this kernel) has no bfq scheduler and revised netfilter code (which wifi tethering relies on, it needs to be tested). And many other things. The reason I'm stating this is because the tutorial we have for building a zeus kernel uses the original fxp-cm9 kernel as a base.
It was info for those who want to use/examine the Lupus source for whatever reason. I for one can't build the kernel from source, I get ipt_ecm.c errors (trying to sort it out with wedgess help, seems to be case-insensitive source and/or mismatched netfilter code from different kernels). Either wedgess has committed an untested source change or my toolchain (from Doomlord) or Linux environment is borked.
Seems that mounting USB Mass Storage in Recovery is broken with this kernel, or is it just me? Can anybody else test it?
CosmicDan said:
Seems that mounting USB Mass Storage in Recovery is broken with this kernel, or is it just me? Can anybody else test it?
Click to expand...
Click to collapse
I know for a fact that DooMLoRD's recovery doesn't call the UMS properly with CyanogenMod. Last time I looked into it, I read that it's something to do with whatever rom you're running, in conjunction with the kernel, itself. In other words, DooMLoRD makes his stuff to work with stock, and because of that, there will be differences when using his stuff with CyanogenMod.
Change log:
http://faux.romhost.me/grouper/kk44/changelog.txt
kernel files
http://faux.romhost.me/grouper/kk44/
ES - http://faux.romhost.me/grouper/kk44/
Mainline - http://faux.romhost.me/grouper/kk44/
Ultimate - http://faux.romhost.me/grouper/kk44/
my op has issues.. can't do much...
github: https://github.com/faux123/Nexus-grouper
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 1.6 GHz for performance, 1.3 GHz for battery
Min clock - MHz 100 MHz for both
CPU Governor - Interactive for performance and for battery
CPU Quiet Governor - userspace for performance, Balanced for Battery
Tegra3 Freq Cap - Off for performance, On for battery
Set On Boot - On
Voltage Control
Set On Boot -
Global CPU Voltage - Your preference
Interactive gov control
Hispeed - 85 for both
Hispeed Frequency - 1.6 GHz for performance, 1.3 GHz for battery
Timer Rate - 20000 for both
Min Sampling Rate - 50000 for both
Set On Boot - On
GPU Control
GPU Governor - ondemand for both
GPU Fast Response - 80% for Performance, 40% for battery
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - SIO for both
Readhead Size (eMMC) - 768 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
Above is what I use personally. MAY NOT be optimal for all :fingers-crossed:
DUE TO MY EXTREMELY BUSY SCHEDULE BOTH @ WORK AND @ HOME, I WILL ONLY MAKE MAJOR ANNOUNCEMENTS ONCE PER WEEK
Open Beta may not be stable and may cause issues with your phone!
By loading open beta you have agreed to:
1. To report all random reboots with associated /proc/last_kmsg
2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps
3. Participate in Forum discussions for the beta software with others without FLAMING each other or post useless information such as:
a) Phone doesn't boot (without providing any additional information, ROM versions etc)
B) phone is too hot (without providing any additional information, ie OC freq, UV etc)
The Open Beta system is designed to have the community help each other and the developers. This way, all potential bugs are flushed out so the final released version will be stable and error free. The more actively you participate in Beta Testing the better the final product will be (you are really helping yourself to create a better community software).
If you do NOT agree with the statements above, DO NOT load my Open Beta software.
Kernel 015 Open Beta 1 is out! (BETAs ARE ALWAYS ULTIMATE VERSION unless I stated otherwise)
JB ==> http://faux.androidro.ms/grouper/beta/grouper-faux123-kernel-v015b01.zip
JB ES version ==>
[ build 1 ]
Merged with Google Mr1.1 source updates!
Added 2 interactive governor patches
Hey Faux123, what's up Nice to see you here!
Omg I'm the happiest person right now. Faux made my phone usable, going to make this tablet even better.
Keeping my eye on this.
Sent from my LG-P999 using xda app-developers app
Accidentally uploaded a test version 2 (broke wifi)... re-uploaded the correct file now...
Woohoo faux!
Sent from my SGH-I727 using xda premium
Welcome faux123! Good to see more & more developers.
Used your kernels on matrix and gnex, awesome work thanks so much
Sent from my Nexus 7 using xda premium
awesome
love the AP33 title
GPU unlock?
Very impressed with performance and feel so far. Thank you.
We're only missing franco now!
Sent from my Nexus 7 using xda premium
Wow very happy this morning you did wonders for my g2x and I know you will do the same for the n7 thanks bro downloading now... and if you ever need a tester I'm in
Sent from my Nexus 7 using Tapatalk 2
003 is out. Fixed bootlooping for some users.
I know I know faux from somewhere.... Atrix or Xperia Play....
Sent from my Galaxy Nexus using xda app-developers app
faux123 said:
003 is out. Fixed bootlooping for some users.
Click to expand...
Click to collapse
Great, I've only just checked back and seen v003 is out.
I had what appeared to be bootloops on v002, but it still boots fine. It just loops onto the initial splash screen about four or five times and then the bootanimation starts up and the boot is fine.
But thanks for v003!
Running great on paranoidandroid.
Sent from my Nexus 7 using XDA Premium HD app
omg , just got my nex7 today and at the same day faux brings out a nex7 kernel !! awesome !! love your work on my gnex
does this kernel have gpu oc?
*edit*
Sent from my Nexus 7 using XDA Premium HD app
LuPuS Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This kernel is based on the LuPuS Kernel for Arc/S by wedgess. All the changes in the kernel are done by him. A big thanks to wedgess. I have made this with his permissions and support. The Ramdisk is modified by me using the Stock from the ftf files.
Disclaimer
Code:
[SIZE=4]
[FONT=monospace]
[COLOR=DarkOrchid]#include[/COLOR] [COLOR=Magenta]std.h[/COLOR]
[COLOR=Blue]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone*
* bootloops and alarm does not go off. Please do some research if you have any *
* concerns about features included in my kernel before using it! YOU and only*
* YOU are choosing to make these modifications.
*/
[COLOR=Magenta]#if[/COLOR]
You have a [COLOR=DarkGreen]question[/COLOR] post it in the [COLOR=DarkRed]thread[/COLOR],
Instead of [COLOR=DarkGreen]Pm'ing me[/COLOR], as other users may experience your [COLOR=DarkRed]problems[/COLOR]
[COLOR=Magenta]#endif[/COLOR][/COLOR]
[/FONT][/SIZE]
Included in kernel
Added Io-schedulers --
- Noop
- Anticipatory
- Deadline
- CFQ
- BFQ
- SIO
Added Governors --
- lagfree
- brazillianwax
- smoothass
- scary
- savagedzen
- smartass
- smartassv2
- interactivex
- minmax
- powersave
- performance
- conservative
- ondemand
- interactive
- userspace
+
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
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.
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Superbad -
A "superbad" super smooth rendition of a highly optimized "smartass" governor!
Darkside -
A "slightly more agressive smart" optimized governor!
What else-----
-SLQB - (SLAB allocator with Queue)-(both)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
- Added Cleancache
- Supports ext 2,3
- Updated zRam
- Lzo compression/decompression speed has doubled on average.
- Init.d support
- Fudgeswap
- And much more
Show your support for the kernel by adding this to your signature
A big thanks to -
wedgess - for the source and a lot of help
sandy7 - for downloading the cm9 roms and sending me the kernels(mini pro & active)
VitorMSA - for LWW Kernel
awriefwumbo - for Mini Kernel
Downloads and Changelog in post 2
Please Click Thanks, Its Better Then Saying It :good:
Please Thank wedgess in Post #3 :good:
Guys if you wanna donate to me then Please follow this method
login to your paypal account
in sending money enter email id [email protected]
enter the amount and transfer.
Accepting donations in India is Prohibited so you have to transfer in above way
Changelog
Code:
[B]v1[/B]
- All previous boot issues / issues fixed
- Improved Battery Life alot :)
- Thumbee support
- EXT 2/3 & 4 supported
- Init.d supported
- Init.d scripts added (run at boot)
- SLQB Memory allocator
- ARM7 optimizations
- Brought OC back down to 1.6 max (no need for it above 1.6 unless u want to kill your device)
- Kernel sources completely reworked started from scratch o Sony xx.587 sources
- Tiny RCU
- Updatedd patched and fixed LZO
- lowered vfs cache pressure
- Increased Wifi- Range and added support for channel 14
- 0 % Battery patch - Thanks @ Bazoocaze
- Better memory copy
- Better memory move
- Deep sleep issue fixed
- LMK Optimizations (LowMemoryKiller)
- VDD support (voltage conrol)
- Linaro Optimzations
- Compaction added
- KSM
- CIFS (improved support)
- NTFS
- Updated to newest SIO Io-Scheduler
- Google Snappy Compress & Decompress
- Added Vibrate To Recovery (Notification to enter CWM)
- Wifi module size drasticly reduced
** Possibly missing a few things **
DOWNLOADS
http://www.mediafire.com/?ai1h8vmg09kzp
Zram is not enabled by default- to enable it flash the zip
If for whatever reason you want to disable it after you have flashed the .zip, just go to ect/init.d and delete 00zram
Current version has been tested on the Mini Pro and LWW. Others are untested. Plz check and report.
Though I am sure they will work fine.
Another good one, LuPuS taking over :good:
Wowww really fast !! Thanks for your work singh .
Sent from my Xperia Mini
awriefwumbo said:
Wowww really fast !! Thanks for your work singh .
Sent from my Xperia Mini
Click to expand...
Click to collapse
was it faster than fxp kernel?how was it performance on gaming or others?
Hell Yeah!! LuPuS All The Way!! Good Work for Singh and Wedgess :thumbup: :good:
Sent from my Xperia Mini using xda premium
scorpion 13 said:
was it faster than fxp kernel?how was it performance on gaming or others?
Click to expand...
Click to collapse
No i mean he build the kernel so fast
Sent from my Xperia Mini
I tried it on cm9,very fast and good act on gaming and performance
Thank you
Sent from my ST15i using Tapatalk 2
At last, I got a rider to ride my CM9, FAST LIKE HELL, long live Lupus :beer::thumbup:
scorpion 13 said:
I tried it on cm9,very fast and good act on gaming and performance
Thank you
Sent from my ST15i using Tapatalk 2
Click to expand...
Click to collapse
what games did you tried?
maybe somebody tried nfs most wanted, vice city, gta3 ?
thinking to come back to cm9 :fingers-crossed:
I tried it yesterday. Gaming is faster, but in benchmark I had 5100 points. So I have came back to FXP, where I have 5500. But good work! There aren't many kernels for CM9. All are for CM10
Accelometer not working in temple run but works in other games.
It is kernel bug because that solved by flash Fxp kernel
Sent from my ST15i using Tapatalk 2
Vynikal said:
I tried it yesterday. Gaming is faster, but in benchmark I had 5100 points. So I have came back to FXP, where I have 5500. But good work! There aren't many kernels for CM9. All are for CM10
Click to expand...
Click to collapse
Benchmarks don't matter. What matters is actual performance you experience.
scorpion 13 said:
Accelometer not working in temple run but works in other games.
It is kernel bug because that solved by flash Fxp kernel
Sent from my ST15i using Tapatalk 2
Click to expand...
Click to collapse
Just checked the Temple Run on my both devices and its running perfectly fine with this kernel.
and if the accelerometer is working in other games it couldn't be a kernel bug at all.
singh_dd93 said:
Benchmarks don't matter. What matters is actual performance you experience.
Click to expand...
Click to collapse
Completely agree, dont see why people go by benchmarks if you run them 4times in a row u get different scores everytime anyway.
Only if people spent more time testing performance instead of running benchmarks
Sent from my GT-I9300 On Official JB
wedgess said:
Completely agree, dont see why people go by benchmarks if you run them 4times in a row u get different scores everytime anyway.
Only if people spent more time testing performance instead of running benchmarks
Sent from my GT-I9300 On Official JB
Click to expand...
Click to collapse
True.
Excelent work!!!! Thanks for making this possible to CM9.1 users like me.
Now I have one trouble. Which governor I should use?
VitorMSA said:
Excelent work!!!! Thanks for making this possible to CM9.1 users like me.
Now I have one trouble. Whice governor I should use?
Click to expand...
Click to collapse
I think it depends what you want. For me smartassv2 & SIO scheduler it's a good combination for battery & performance. Most people use that combination. Try it for a few days and you will see
here fxp 201 kernel http://code.google.com/p/afk-tkj/downloads/detail?name=201.boot.img&can=2&q=
awriefwumbo said:
here fxp 201 kernel http://code.google.com/p/afk-tkj/downloads/detail?name=201.boot.img&can=2&q=
Click to expand...
Click to collapse
Not needed. I has asked for kernels initially to take the ramdisk.
Driver007 said:
what games did you tried?
maybe somebody tried nfs most wanted, vice city, gta3 ?
thinking to come back to cm9 :fingers-crossed:
Click to expand...
Click to collapse
its so smooth , i play modern combat 3 and backstab