Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
Related
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
DELETE ALL VOLTAGE CONTROL SETTINGS, AND REMOVE BOOT SETTINGS FROM CM SETTINGS AND VOLTAGE CONTROL AND DISABLE SETCPU PROFILES BEFORE FLASHING THE LATEST UPDATE. THIS GOES FOR ALL UPDATES, INCLUDING UPDATING CM.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. Use Xan's UV app to undervolt.It's in that market, search "Voltage Control".
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/andoroid_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not a bug. You're not bricked. Let it boot up.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.
CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4][First Vibrant supported/tested version]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May 6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-new(old) modem_ctl
-tvout stuff
-fsa switch sleep
-overvolting cap
v5.3[May 16]
-upstream initramfs/initial flash changes
-Upstream change to the way battery percentage is calculated
-Lots of little( irrelevant) upstream changes
-Actually fixed the kernel version.
NIGHTLIES/WHENEVERS
#0[May 27]
+Way too many to list. Big changes include an update to 2.6.35.13, voodoo sound v9, and a properly working ril.
#1[May 29]
+States table in voltage control kinda works now, but is herp derp.
+Disabled ext2
+Re added the 1.6Ghz step
+Upped 1.55ghz freq by a few mhz
#2[July 12]
+Up to date with everything
+GPU bus controllable via Control Freak
+Other stuff
TheEscapist said:
NOTE: I need testers, as I dont have a vibrant. There *shouldn't* be anything that breaks specifically on the vibrant, but still.
Click to expand...
Click to collapse
Miui?? Trying it neways thanks
nickmcminn60 said:
Miui?? Trying it neways thanks
Click to expand...
Click to collapse
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
nickmcminn60 said:
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
Click to expand...
Click to collapse
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No worries, ill just flash with miui tomorrow.
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
es7241 said:
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's the custom boot screen. if the kernel didn't boot, you wouldn't have been able to get into recovery.
Sent from my SGH-I897 using XDA Premium App
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
brian(: said:
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
Click to expand...
Click to collapse
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
what settings do you reccomend ?
brian(: said:
what settings do you reccomend ?
Click to expand...
Click to collapse
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
brian(: said:
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
Click to expand...
Click to collapse
Because Quad scores are the be all and end all of a phone. (fyi: I pull anywhere from 1900 to 2600 at 1.55ghz).
If you're concerned, run linpack or some other cpu intensive task. If you keep getting an "Inaccurate" error in Linpack, you're probably unstable at that frequency, which could cause crashing, lag, slowness, etc.
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
es7241 said:
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
es7241 said:
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
nickmcminn60 said:
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
Click to expand...
Click to collapse
Not sure what that is in celcius (Canadian here), but under 45c is a good limit to aim for. Charging cuts off around there, not sure the exact value off the top of my head.
Sent from my SGH-I897 using XDA Premium App
Aperture Laboratories presents
GLaDOS V2.11
The latest innovation in human-smartphone interaction. Our scientist have shown in extensive tests that humans operating our kernel on their devices experience 67% more joy in life while simultaneously the likelihood of being maimed or killed by falling space debris is significantly reduced. Also preliminary human trials indicate that it might offer some protection against lethal dosages of gamma radiation and blows to the head with a rod-like object.
Features:
Based on stock Android kernel 3.0.8 IMM76D
CPUfreq governor 'lazy'
Live OC version 1
Custom Voltage version 1
Battery Life eXtender (BLX) version 1
Power saving state DEEP IDLE version 2
Touch Wake version 1
Backlight Dimmer (BLD) version 3
Backlight Notification (BLN) version 9
Brain **** Scheduler (BFS) version 0.357
SLQB memory allocator
Voodoo Color version 2
Voodoo Sound version 10
CIFS
TUN
Bigmem (+20 MB more available RAM)
USB OTG build 5
Download:
http://goo-inside.me/devs/aperture/GLaDOS-NexusS (thanks to goo-inside.me for hosting)
Always make a backup of your /efs/ directory (http://forum.xda-developers.com/showthread.php?t=1138873) before installing custom kernels or ROMs.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Source code:
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/glados
Do not use profiles, they are unnecessary and only lead to instabilities.
If you experience any problems and are on a nightly or kanged ROM, try the latest stable version of that ROM first. I will not give support or answer any questions if you do not try this before reporting a problem with the kernel.
If you experience stability problems like reboots, freezes, FCs and SoDs and you did OC or UV, first try changing back to the stock settings. If this solves the problems, your OC/UV configuration is not stable. There are some indications that OC/UV settings which run fine at high battery charges might still cause problems at lower battery charges. So to be safe always check that your OC/UV configuration runs fine at low battery like 5%.
I do not offer support/help/recommendations on OC/UV. If you decide to do so and your device is unstable you are on your own. Check http://forum.xda-developers.com/showthread.php?t=1335429 for help.
If you experience the problem that the DEEP IDLE state is not properly used (according to the idle_stats), read the last section of http://forum.xda-developers.com/showpost.php?p=18299324&postcount=1.
When reporting a bug always include information about your ROM and hardware model. Also be as precise as possible when describing the problem. Just because a single person is experiencing a problem, it does not mean there actually is a problem with the kernel. I always wait until at least one other person can confirm the issue before I look into it. So if you see someone posting a bug report, do not be shy and feel free to confirm the issue or if you do not have the problem let me know that too.
When asking for a feature you would like to see implemented in GLaDOS always provide a link with information about this tweak and preferably also a link to the source code.
Aperture bootanimation courtesy of rascarlo (www.twitter.com/rascarlo)
For users unfamiliar with init.d scripts I recommend NSTools by arifhn (http://forum.xda-developers.com/showthread.php?t=1333696) for managing the various tweaks.
Changelog
GLaDOS-V2.11
Added kernel patches for Android 4.0.4 update.
Fixed bug with Touch Wake.
The kernel installer no longer modifies the ramdisk for adding init.d support.
GLaDOS-V2.10
Added USB OTG build 5 by sztupy.
Fixed small bug in Custom Voltage.
Fixed bug in Live OC.
Changed to new bootanimation by Rascarlo (many thanks!).
Changed default V1 gamma values for Voodoo Color to stock settings.
GLaDOS-V2.9
Fixed two small bugs in LiveOC.
Fixed small bug in Lazy.
Reduced display frequency back to stock settings.
GLaDOS-V2.8
Fixed a bug in LiveOC.
Fixed optimized compiler flags.
GLaDOS-V2.7
Fixed TouchWake issue of long powerkey presses causing the touch controls to be disabled without delay on next screen off.
For BLN the blink interval and blink time can now be adjusted in the sysfs interface. Also BLN is disabled by default.
For lazy the sampling rate is initialized to a default of 15000.
GLaDOS-V2.6
Fixed the problem of the CAM module being active all the time preventing DEEP IDLE from being used.
GLaDOS-V2.5
Fixed bug.
Removed several unnecessary kernel drivers and features.
Removed kernel debug and logging features.
Included logger as a module.
GLaDOS-V2.4
Fixed bugs in Live OC.
GLaDOS-V2.3
Fixed the freeze/reboot problems when changing the frequency limits.
GLaDOS-V2.2
Removed the limit of the minimum frequency to 200 when the GPU is active.
Preliminary bandaid to DEEP IDLE compensating for various bugs in ROMs.
GLaDOS-V2.1
Added Voodoo Color version 2 and Voodoo Sound version 10.
GLaDOS-V2.0
Update to Android kernel 3.0.8 for ICS 4.0.3 IML74K.
GLaDOS-V1.12
Fixed the camera problems caused by Bigmem (increases available RAM by 21MB now).
GLaDOS-V1.11
Added Bigmem option (increases RAM available for the system by 26MB).
GLaDOS-V1.10
Added DRAM scaling to Live OC.
Flash memory I/O tweaks.
Added Tiny Preemptive RCU.
Updated the optimized CRC32 algorithm.
Removed CFQ I/O scheduler.
GLaDOS-V1.9
Added OC frequency states 1.4GHz and 1.2GHz.
GLaDOS-V1.8
Fixed the problem of the touchkey backlight lighting up when touched while the screen is off.
Increased display frequency to 72Hz necessary to achieve 65fps.
GLaDOS-V1.7
Fixed the increased battery drain while in SLEEP when DEEP IDLE is enabled.
Fixed the problem on the NS4G of DEEP IDLE not being used while 4G is enabled.
GLaDOS-V1.6
Disabled most logging and debugging kernel config options.
Included logger and TUN as modules.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Removed '98touchscreen' init.d script.
Aperture bootanimation and -sound courtesy of Euphorie (http://forum.xda-developers.com/showthread.php?t=1061627).
GLaDOS-V1.5
Fixed problems with setting voltages and min/max frequency with SetCPU.
Fixed problems with the vibrator and DEEP IDLE.
Improved stability of wireless connection.
GLaDOS-V1.4
Updated to latest toolchain arm-2011.03-41
Optimized compiler flags
Added optimized RWSEM
Fixed BLD bug for i9023 of the touchkey backlights not getting re-activated on touch
Changed to advanced TCP congestion scheduler VENO
GLaDOS-V1.3
Improvements to JHash.
Improvements to CRC32.
Fix memory leak in CPUfreq stats module.
Removed PMEM. I do see any improvement regarding the available RAM, but removing unused code is never a bad idea.
GLaDOS-V1.2
Fixed 'Screen v1 gamma hack' not working for Voodoo Color.
GLaDOS-V1.1
Fixed BLN problems for i9023.
GLaDOS-V1.0
Initial release.
Oh this is going to be good.
...Thanks E
Sent from my Nexus S 4G using xda premium
oh man... downloading now
thank you so much for providing this!
Stock android uses deadline scheduler or VR?
A bit off topic, but did anyone ever toy with SIO, NOOP and CFQ on Nexus S?
Wow
Testing right know
can i flash this on my rooted stock 2.3.6? that is the latest for my country.
Ezekeel's own kernel?
Ezekeel's own kernel?!
I knew you have only provided kernel devs with MODs.
Very tempting... Will leave it a few releases before I jump from Matr1x but expecting this to be very good!
I'd be interested in seeing what people's battery life is like on this kernel compared to others, as that's the main selling point for me!
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
i'm try ...
v3rk said:
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
Click to expand...
Click to collapse
so its better than franco's? and does it include the latest deep idle fiX?
Finally a kernel of a master hehe
Sent from my Nexus S using xda premium
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
After flashing no more lights in soft keys
Edit:
Solved
thegtfusion said:
so its better than franco's? and does it include the latest deep idle fiX?
Click to expand...
Click to collapse
lol
read up who made deepidle-fix. and all those other kernel-tweaks. this kernel comes from the horse's mouth so to speak, or how this is said in English.
now let's see if it's stable.
Yusei said:
After flashing no more lights in soft keys
Click to expand...
Click to collapse
Use bln app to see if it's enable.
MarkVis said:
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
Click to expand...
Click to collapse
If i am in you, I'd have chose which kernel to include in next nexus mv release
Inviato dal mio Nexus S
report: Oh yeah this is awesome syrup, my phone loves it.
Edit : everything good on this side.
Sent from my Kush'd Google Nexus S 4G using xda premium
Ezekeel, can you put this kernel taking around 65fps in 3D graphics globe?
Btw, this rocks.
Current Release: 12/20/2012(JB)/10/03/2012(GB+ICS)
Important, Please read: There are now two kernel versions starting with 8/10/2012 release, one for GB+limited ICS(no HWA) support and another for the ICS branch with HWA. Changes will be loggged separately for each kernel type. If you see no changelogs specifically for that type, then there's no release made. For example, 8/10/12 for GB is a continuation of the 3/21 release with none of the post-3/21 kernel ICS changes made.
Update 9/21/12: As of 9/21/12, jellybean is officially supported with the JB specific kernels.
First of all, I started this thread to make commenting and tracking easier for the incredikernel releases following Chad's latest release (8/15/2011).
I also wanted to make a distinction between Chad's initial kernels and the ones I've updated since that release and this is one way to do it. Initially I didn't want to do that but now I regretted not splitting sooner.
If you want the changelog for anything prior to my first kernel please refer to:
Chad's Incredikernel thread
Changelog:
11/30/2013 JB 4.3
Android 4.3 support
synced with updates from Android 4.3 Evervolv kernel
04/25/2013 ICS Sense+JB 4.2
dynamic fsync control
WiFi driver updates
Interactive governor updates - see Tinykernel
Entropy Tweaks
Netfilter updates
New sysfs location for fast charge for broader app compatibility - still compatible with latest incredicontrol
FUSE filesystem support
12/20/2012 JB 4.2 ONLY
add back governors that were removed in 12/15
12/15/2012 JB 4.2 ONLY
enabled UHID support
updated msm_fb for 4.2
12/11/2012 JB ONLY
cpufreq: enable overclocking of 1.15Ghz and 1.19Ghz
numerous interactive and ondemand governor tweaks
cpufreq: send uevent when governor changes
ondemand: boost pulse for JB's powerHAL
10/11/2012 JB ONLY
defconfig: several config changes to fix data usage not working
10/06/2012 JB ONLY
defconfig: enable conservative governor by request
10/03/2012 ICS+JB+GB
defconfig: remove rarely used governors and set max frequency to preventing booting higher than 998mhz
lower default hispeed_freq to 614Mhz
cpufreq: interactive: always limit initial speed bump to hispeed_freq
09/21/2012 ICS+JB+GB
ALL: New Interactive governor
ALL: Built with GCC 4.6 toolchain from Google
GB: interactive governor tweaked for battery
ICS+JB: interactive governor tweaked for butter
JB: genlock patched for JB support
JB: new wifi driver for compatibility with JB ROMs
08/11/2012 ICS+GB
KSM wasn't enabled as it should have been in the last build - fixed that - also nothing needs to be done to enable it on GB as it's on by default
08/10/2012 ICS ONLY
fixed data usage features for ICS
added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
enabled KSM (Kernel Samepage Merging) - still need to enable in CM settings
08/10/2012 ICS+GB
added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
07/07/2012 ICS ONLY
Merged in multiple driver updates to support HWA (chad0989)
Updated adreno kernel drivers to latest
added xtqta_guid - for ICS' data usage feature, also seems to have resolved stability issues
Added lazy CPU governor
Added back intellidemand
03/21/2012 ICS+GB
Added lazy CPU governor
02/26/2012 ICS+GB
Smartassv2 default governor for sure - doesn't override ramdisk settings though
new governor lagfree - balance between ondemand and interactive
new I/O scheduler SIO
tweaked deadline for better performance
removed CFQ/BFQ schedulers and smartass, conservative, and interactive govenors (still have interactiveX and smartassv2)
01/03/2012 ICS+GB
Tweak intellidemand and interactiveX governors for battery life
Add ZRAM and swap support and add script to toggle ZRAM - see bottom of OP for more info
SmartassV2 default governor again
12/26/2011 ICS+GB
Added faux123's intellidemand governor (thanks faux123!)
Added imoseyon's interactiveX governor (thanks imoseyon!)
Works on GB and ICS currently
interactiveX may not play nicely with ICS so intellidemand is default
Conservative is disabled, let me know if you need it back
12/08/2011 (Chad) ICS+GB
Added ICS support (limited)
11/27/2011 GB
Use ondemand, performance, and conservative governors from the Android Linux 3.0 kernel
Set minimum voltage back to 800 as the voltages will not go below 800 anyway. Anything lower is placebo effect. This is a hardware limitation.
11/14/2011 GB
Update OJ driver
BT fix for newer CM nightlies
WIFI module updates
Update and re-add BFQ scheduler as well as disable deadline
Ondemand is back
Fixes/Tweaks to ondemand and interactive
10/08/2011 GB
Adjusted smartassV2 parameters for 1GHz processor (originally for 500Mhz device)
10/01/2011 GB
Set smartassv2 to default governor
09/30/2011 GB
Added SmartassV2 governor
Current CPU governors as of the latest release:
SmartassV2
Ondemand
Interactive
Lagfree
Lazy
Technical doc on CPU governors (most of the ones in this kernel anyway)
https://raw.github.com/tiny4579/android_kernel_common/android-2.6.38-incredikernel/Documentation/cpu-freq/governors.txt
Update: 11/30/13 - removed link to incredikernel.com as the site has no content - fully on goo.im now
http://goo.im/devs/tiny4579/inc/kernels
Kernel Source
https://github.com/tiny4579/android_kernel_common
Here are a couple notes if you want to build this kernel from source:
Jellybean kernel branch is android-2.6.38-incredikernel-jb.
ICS kernel branch is android-2.6.38-incredikernel-ics.
Gingerbread kernel branch is android-2.6.38-incredikernel.
The config for the kernel is in arch/arm/configs/incrediblec-incredikernel_defconfig. If you want to switch branches I recommend doing a make incrediblec-incredikernel_defconfig after checking out that branch.
I use the GCC 4.4.3 toolchain for this kernel due to GCC 4.6 causing build issues.
Frequently Asked Questions
Some key differences between smartass and smartassv2 so users can decide which they prefer and learn a bit more about the differences:
Smartass
1. Screen off profile built in maxed at 384mhz.
2. Wakeup frequency is 998mhz.
3. Min screen on is 245mhz.
4. Improved by Chad to run better on our devices.
5. Purely load based, no ideal value.
Smartassv2
1. This is the same exact governor in Erasmux's Nexus One kernel (github.com/erasmux/n1-kernel)
2. Ideal wake frequency is 768 (also default that can be changed).
3. Screen on min is actually 128mhz).
4. No screen off profile.
5. Ideal sleep frequency 245mhz.
6. Improved upon from erasmux's version, not Chad's.
Basically the smartassv2 ideal wake frequency allows the phone to favor a certain speed to attempt to save battery life. It can still go above ideal wake and below ideal sleep so there's no caps on max and min while awake or sleep.
Some tips/info on various governors:
Smartass/smartassv2/interactive:
Use 128 min so the governor can scale as it needs to. Max speed I'd recommend at least 768Mhz.
Ondemand:
Try 128 min and if it lags use 245 min. Max speed I'd recommend at least 768Mhz.
Performance:
Only recommended for benchmarks but speed will always run at max.
InteractiveX:
Same as interactive except it has an auto screen off set to the min. Ideal with 245 min in setcpu but try 128 for battery life but it you have wake lag then set to 245.
Intellidemand:
Based on ondemand with a built in screen off. Any speed settings should be fine.
Interactive:
Some new features with this one. Starting with 9/21/12 release I am using the interactive kernel from Google which features a new kernel option called input_boost.
It is off by default but can be enabled by writing a 1 to /sys/devices/system/cpu/cpufreq/interactive/input_boost. Also there is another parameter for interactive called hispeed_freq in the same location. The hispeed_freq is where the governor jumps to first. Hispeed_freq by default in 10/3/12 is 614400 to help save battery. In the older interactive governor there was a maxspeed freq which meant the governor was a bit jumpier to the max speed. This should be a good blend of performance and battery.
Lagfree:
Based on ondemand but with a softer CPU scaling which should help with battery life. It also seems to be very responsive (starting with 2/26)
Lazy:
Based on ondemand as well (Ezekeel is the developer of this governor). I cannot explain this too well but its apparent behavior seems to be to switch between low and high frequencies pretty evenly.
A note from Ezekeel on this governor:
"Thus I took the ondemand governor and implemented an additional parameter 'min_timeinstate' defining a minimum time the CPU will stay in a certain frequency state before it will be allowed to switch frequencies again. This way one can have a fine grained polling by setting the sampling_rate to a low value without running into problems with these fast frequency changes.
I did some extensive testing with a sampling_rate of 10000, min_timeinstate of 40000 and up_threshold of 90 and FLAC, mp3 and video playback all seem to work flawlessly. So it seems the root of the problem was indeed that the CPU does not handle fast frequency changes well.
I tested several apps and games and so far I have not found anything that this governor cannot handle. Thus I dare to say that it seems to be the superior choice over ondemand."
ZRAM, what is it and how to I add it? (starting officially with 12/31/11)
If you are familiar with swap space in linux or virtual memory in Windows it is a similar concept. Except instead of using the hard drive as swap space it compresses swap space in RAM for faster access times than conventional swap. This will also wear out our storage memory less than typical swapping.
Enable ZRAM is simple thanks to a script built by imoseyon which is provided in the kernel zip file. To enable, use adb shell or download a terminal app and run zram enable. This will persist across reboots (if init.d is setup in your ROM) so if you don't want it anymore run zram disable and it will remove the bootscript and deactivate it.
You need to have root privileges to enable/disable zram. Run the su command in terminal emulator to request root.
I was wondering when lazy was gonna make it's way to aosp...
Sent from my ADR6300 using xda premium
OMG_VTEC said:
I was wondering when lazy was gonna make it's way to aosp...
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
The name of the new governor says it all....
You just answered your own question. I took my own sweet time releasing it. It was built like 2 weeks ago. I was being lazy.
tiny4579 said:
Scripts/Mods if I think of something...
Click to expand...
Click to collapse
Tiny, this new thread is great, as is the work you and Chad have done on these kernels. Keep up the great work. Thank you.
jlokos said:
Tiny, this new thread is great, as is the work you and Chad have done on these kernels. Keep up the great work. Thank you.
Click to expand...
Click to collapse
Yeah, the old way was sloppy. Tired of it. I think this thread is cleaner than the sense one and it took me less time to write it.
To help out users (and document the probable future deviation), how about adding a tag to each kernel stating whether it works with froyo (which I believe is none), GB, ICS, or a multiple (which is only the last couple or so, I think).
Great work, by the way.
PonsAsinorem said:
To help out users (and document the probable future deviation), how about adding a tag to each kernel stating whether it works with froyo (which I believe is none), GB, ICS, or a multiple (which is only the last couple or so, I think).
Great work, by the way.
Click to expand...
Click to collapse
Done. 10char
Nice.....great work to you and Chad. Thanks.
Sent from my ADR6300 using Tapatalk
Thanks for the thread tiny, I was wondering what the benefits of the lazy governor were
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
azradiohead said:
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
Click to expand...
Click to collapse
The ROM/kernel/governor have no impact on data signal or speed so what you're seeing is coincidental. Network speed varies on so many factors outside of the control of the ROM or kernel. I'm glad to hear you like the new kernel and the lazy governor. I'm a fan of the dev of the lazy governor's work and run his kernel on my nexus.
My concern is that others will assume it will improve network performance and be disappointed when it doesn't.
Thank you for your compliments!
I just want to make sure I clarified this matter.
chocolate8175 said:
Thanks for the thread tiny, I was wondering what the benefits of the lazy governor were
Click to expand...
Click to collapse
I was looking around for something good that would make sense but I couldn't find anything so far.
Basically I added this governor on a whim. So far it seems to like lower frequencies even more than smartassv2 without too much sacrifice on speed. It might have better battery life. It seems smooth on Nil's Business Sense 3.5 though.
Interesting post here on smartassv2 from the developer of the lazy governor:
User:
and smartassV2 too but let him fix find the cause of the reboots before
Dev:
I will not integrate any new stuff until I have the cause for reboot problems tracked down. I will look into lulzactive, but I definitely will not include smartass since it is an inefficient governor.
Not sure why he said it was inefficient but could see no post about it.
Needless to say, I like lazy and lagfree so far. Give lazy and lagfree a try for a week and see what you think.
azradiohead said:
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
Click to expand...
Click to collapse
may be placibo effect but I have noticed this too and confirmed with speedtest.
Sent from my incredible incredible.
RebelShadow said:
may be placibo effect but I have noticed this too and confirmed with speedtest.
Sent from my incredible incredible.
Click to expand...
Click to collapse
How does it fare with ondemand or lagfree? I still think its placebo. I can't test on my phone as I don't have data on the incredible.
Sent from my Galaxy Nexus using Tapatalk
Running GB and just installed the new Incredikernel, I saw no appreciable difference with data usage on Lazy, Lagfree, SAV2, Ondemand. Depending on your wireless signal, just moving your body by even a few inches could have an impact on data speeds (high frequency shadowing of transmission waves). The ping, might have some more sway by the CPU of the device if the program doesn't get as much processor in when communicating with the server, but not in the order of milliseconds (would be my though).
tiny4579 said:
I was looking around for something good that would make sense but I couldn't find anything so far.
Basically I added this governor on a whim. So far it seems to like lower frequencies even more than smartassv2 without too much sacrifice on speed. It might have better battery life. It seems smooth on Nil's Business Sense 3.5 though.
Interesting post here on smartassv2 from the developer of the lazy governor:
User:
and smartassV2 too but let him fix find the cause of the reboots before
Dev:
I will not integrate any new stuff until I have the cause for reboot problems tracked down. I will look into lulzactive, but I definitely will not include smartass since it is an inefficient governor.
Not sure why he said it was inefficient but could see no post about it.
Needless to say, I like lazy and lagfree so far. Give lazy and lagfree a try for a week and see what you think.
Click to expand...
Click to collapse
I'm using your latest GB kernel with the lazy governor on Warm TwoPointThree 3.5 rom. It is very smooth with very good battery life (undervolted).
jlokos said:
I'm using your latest GB kernel with the lazy governor on Warm TwoPointThree 3.5 rom. It is very smooth with very good battery life (undervolted).
Click to expand...
Click to collapse
Better than SAV2? I can't really comment myself but I like it so far.
Also, try to keep Sense kernel talk in the sense thread and aosp kernel talk in the AOSP thread. It makes tracking easier. But I also brought up the comment in this thread so it makes sense why you posted here.
tiny4579 said:
Better than SAV2? I can't really comment myself but I like it so far.
Also, try to keep Sense kernel talk in the sense thread and aosp kernel talk in the AOSP thread. It makes tracking easier. But I also brought up the comment in this thread so it makes sense why you posted here.
Click to expand...
Click to collapse
I have used both the GB and AOSP versions of the lazy governor. The GB version appears to make the Sense 3.5 rom smoother. As far as battery life, I haven't been able to tell if its better than SA2 since I have a much longer history with SA2. In any event, thanks for adding this governor to both versions (as I switch between the new ICS roms and Sense 3.5); it's another great choice for us to experiment with.
Could you make lulzactive possible tiny?
Sent from my DROIDX using Tapatalk
Note!
Only for stock 4.3
Click to expand...
Click to collapse
Features
Gamma Control - HOW-TO
DoubleTap2Wake - HOW-TO
Sweep2Wake - HOW-TO
Advanced Xperia Recovery - HOW-TO (Only v5 and above)
Based on 10.4.1.B.0.101 kernel sources
Xperia Advanced Recovery Bootloader
CPU overclock upto 1.944 GHz
Undervolting
Built with Linaro 4.8.3 toolchain using -O3 optimisation
Updated Prima WLAN drivers
Additional CPU governors - SmartMAX | SmartMAX_eps | Intellidemand 5.0 | Intelliactive | Preservative
Tweaked SIO and added FIOPS, Zen, VR, BFQ (7.2) and ROW block schedulers
USB force fastcharge
Updated Ondemand and interactive governor
Compressed kernel using XZ
Tweaked voltage regulators
Interactive GPU Governor
Uses CPUQuiet from Nvidia
Click to expand...
Click to collapse
Installation instructions
Flash in CWM/TWRP
Click to expand...
Click to collapse
Un-Installation instructions
Use the AROMA Installer in the zip to uninstall
Click to expand...
Click to collapse
Credits
Sony - I love what they do and only wish they got more recognition. They deserve it.
faux123 - For almost all kernel features
DoomLord - For the RAMDISK
Click to expand...
Click to collapse
Donors
Source
http://bitbucket.org/nikhiljan93/xzkernel
Click to expand...
Click to collapse
XDA:DevDB Information
[Stock-Kernel] XzInnere [Linaro-4.8.3], a Kernel for the Sony Xperia Z
Contributors
alnikki25k
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2014-03-29
Created 2014-01-27
Last Updated 2014-03-28
Reserved
HOTPLUG CONTROL, GOVERNORS, SAMPLE CONFIGS:
Thanks to n3ocort3x
With cpuquiet + load stats governor u get a brilliant battery life while keep it snappy.
I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.
If you want to keep it balanced, and yeah, most users want that:
governor: smartmax
cpuquiet governor: load_stats
If you want ultimate performance:
governor: interactive (up treshold 65) or smartmax (lower tresholds)
cpuquiet governor: load_stats
SMARTMAX GOVERNOR
===============
awake_ideal_freq 594000
boost_freq 1242000
suspend_ideal_freq 384000
touch_poke_freq 1242000
Leave the rest untouched
Click to expand...
Click to collapse
For a more power-saving governor (Recommended)
New! Preservative
Click to expand...
Click to collapse
Thanks to bedalus
This is just for the record, and for those interested. The previous version of Preservative worked like a combination of smartass and conservative. It would scale straight up to the optimum frequency if there was any load (like smartass), then scale up one step at a time (like conservative) if the load was above the required threshold. This worked pretty well, and helped keep the frequency low. But sometimes it was keeping it low for too long, and a few users (myself included) noticed occasional hangs, presumably caused by a pile up of critical code that didn't get executed in time.
To improve responsiveness, but keep the frequency as low as possible was quite a challenge. I took the existing logic and chucked most of it in the bin...
(Remember, it's keeping the frequency low, and not UV that saves power - read this thread, especially post #2 for more background on this issue)
...what came to replace it was a fairly original hybrid, inspired by ondemand. Ondemand works by jumping to the top frequency when there is any load. This is usually overkill. So, you might have been at 100% CPU utilisation at 384MHz, so ondemand will jump straight to 1512MHz. However, when it gets there, the utilisation is now only 30%, so it will scale down to 486MHz.
Preservative now works a little like this. Whatever frequency it is currently at, if the utilisation hits 100%, it will scale up. But scaling up to max like ondemand? In the example above, this was the worst kind of overkill. Scaling up to max just to find scaling up one step would have been sufficient. But do we need to scale up one step, or as many as possible? There's no way to know for sure. You have to scale up before you can measure if the extra CPU cycles were enough or not.
This issue is what Preservative attempts to overcome: if the load is high, it will scale up, but not always to max. Let's label the frequency steps: 384=A 486=B 594=C 702=D 810=E 918=F 1026=G 1134=H 1242=I 1350=J 1458=K 1512=L
Conservative would take 11 calls to the governor to get from A to L, if L was required. Ondemand would go straight there. Ondemand is often overkill, conservative is often underkill. I'd like a compromise. Here's what Preservative would do:
Code:
L <- 4th step selected by preservative
K <- 3rd step selected by preservative
J <- 2nd step selected by preservative
I
H
G <- 1st step selected by preservative
F
E
D
C
B
A <- sat here until there is load
It splits the difference between whichever frequency it is at and the top frequency, and jumps there. If it is still under high load, it will do it again. So if it is idling, then needs to get to the top, it takes three more calls than ondemand, but seven less than conservative. Not only that, but it has also skipped over a large chunk of the slower steps that conservative would crawl through.
Scaling down also works in a similar way. Preservative will work out what step would be sufficient to manage the load, then jump halfway to that step on the first call. This is because, unlike ondemand, there is no down-threshold. Preservative will scale up when the load exceed the up threshold, but as soon as this is no longer the case, it will start attempting to scale back down to save power. It does not wait for load to reduce to drop below a certain point. Loads fluctuate. If went straight back to A, only to come back back to L, it would have to scale through G J and K again. However, dropping to G then D then B before A means if it does have to scale back up towards L, it doesn't have as far to climb, meaning less calls to the governor, and that the best step can be achieved quicker.
There has also been an adjustment to the up threshold. When the device is idle, the up threshold will automatically adjust to be more relaxed about scaling up. This means while the device is idle (e.g. when you are just reading some text) it becomes increasingly sensitive to changes in demand. When you touch the screen it will extremely responsive.
Conversely, when the device is hitting the top frequency, the up threshold will become increasingly strict. So if you are gaming, and putting a lot of load on the CPU, it will aim to be as efficient as possible, and only scale up if it really has to, to ensure that no cycles are wasted at these high power hungry frequencies.
Whenever it goes from hitting L to hitting A, or visa versa, the threshold will reset to default. The sysfs location of this tunable remains at:
Code:
/sys/devices/system/cpu/cpufreq/up_threshold
It will accept values of up to 127, higher being more power-saving. The default is 100, but editing the file changes this value. If you want to use a different value on a permanent basis, add the line
Code:
[B]echo 84 > /sys/devices/system/cpu/cpufreq/up_threshold[/B]
to /etc/init.d/00config
and it will then restore your setting of 84 (or whatever) every time you reboot. Remember it will be overwritten if you flash updates to the kernel, so make a copy of your edited file. However, I believe 100 is a pretty good default.
Click to expand...
Click to collapse
Reserved
Changelog
Next-Release-TO-DO
XzI - v6
Kitkat - 230 Sources
Massive changelog
Large amounts of debugging code removed
Click to expand...
Click to collapse
Current-Release
XzI - v5
Intelliactive CPU governor
New! Advanced Xperia Recovery Bootloader
New! Preservative CPU Governor (Read more)
Kernel mode NEON
MSM CPU Frequency Limiter / a.k.a Snake Charmer(in faux app) support
Kernel Futex tweaks
MSM Memcopy enhancements from Motorola Mobility
Higher Bus Speeds @ Lower cache clocks = Higher performance @ Lower Temperatures + More Power Savings
Generic tweaks
Click to expand...
Click to collapse
Previous releases
XzI - v4
Sony 10.4.1.B.0.101 Sources
Tap2Wake/Sweep2Wake using evgen method
New Power-Aware Workqueue algorithms
AROMA Installer
XzDualRecovery
Lots of debugging removed
BFQ-v7r1
Interactive GPU Governor
Removed Simple GPU Governor
Removed MultiROM
Click to expand...
Click to collapse
XzI - v3
MultiROM Xperia for Xperia Z - http://www.youtube.com/watch?v=9f9gG1sRNog
- Initial implementation. Not functional. Just testing boot.
Revert Power-Supply drivers back to 4.2.2
Intellidemand Governor 5.0
Click to expand...
Click to collapse
XzI - v2
Lower undervolt to 600 mV
Sound Control 2.0
Gamma Control
SLUB updates
Updated Adreno drivers
Use O3 Optimisation
Tune BFQ
System Config Clean-up - Quite experimental
Click to expand...
Click to collapse
XzI - v1
Initial Release
Click to expand...
Click to collapse
Download
Click here
Click to expand...
Click to collapse
MultiROM
Coming Soon
Placeholder
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Kocayine said:
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Click to expand...
Click to collapse
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
alnikki25k said:
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
Click to expand...
Click to collapse
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Kocayine said:
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Click to expand...
Click to collapse
Yup. May not include that. But will have Gamma control.
No sound control right?
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
You sure you cant make a version with doubletap? I dont need very advanced kernel, just some governors and stuff and now I got used to the tapping as well : (
BTW, how about the wakelock fixes and so from XzKernel, are they included here?
beniamin24 said:
No sound control right?
Click to expand...
Click to collapse
This is just the first release. It'll be added next.
my phone reboots after trying to undervolt in trickster mod app
braacic17 said:
my phone reboots after trying to undervolt in trickster mod app
Click to expand...
Click to collapse
It works for me. Clear all settings in TricksterMOD and try again.
alnikki25k said:
It works for me. Clear all settings in TricksterMOD and try again.
Click to expand...
Click to collapse
nope. still not working i tried everything even in faux123 app but it just reboots.
well its not so important for me right now. kernel is awesome and i can see better battery life on my xz 4.3 !!
thanks ! :laugh:
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
What about exFAT? Is it work properly?
-totonio- said:
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
.. and doubletap.. then we got all that is needed
Not for deodexed right?
Inviato dal mio C6603 utilizzando Tapatalk
Exactly what i need, a battery oriented / balanced kernel, while keeping it slim.. Keep up the good work!
Waiting for gamma control.. ??
Edit Note: i've missed the part which state that double tap wont be included here.. Sorry..
Sent from my C6602 using Tapatalk
*** Disclaimer
I am not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Click to expand...
Click to collapse
Features :
-O3, Cortex-A53, NEON, VFPv4 optimizations
Compiled from latest Linaro GCC 4.9.3 2015.02 Toolchain [Christopher83]
Upstreamed to 3.10.71 from kernel.org, from 3.10.28
Asynchronous Fsync ported from HTC Devices
Dynamic Fsync v2.0 [faux123/varunchitre15]
PowerSuspend v1.7 driver support (replaces EarlySuspend) [yank555.lu & faux123]
Android early_suspend/late_resume PM kernel driver framework has been
deprecated by Google. This new powersuspend PM kernel driver is a replacement
for it.
Conserves battery much better.
Triggered by Screen on/off.
Intelli_plug v3.9 driver [faux123]
Intelligent hotplug cpu driver with eco mode.
KCAL - Advanced color control
Disabled MMC CRC check for extra 30% boost in IO
Reduced debugging = More performance
Simple GPU Algorithm [faux123]
FIOPS, BFQ + stock I/O Schedulers
Filesystems support : NTFS, F2FS
Sysfs implementation for changing vibrator intensity [varunchitre15]
Zswap, Frontswap and znswap [faux123]
Support for kernel-mode NEON [faux123]
Increased charging current to 1.2A
Frandom - Fast Kernel Random Number Generator driver added
Added ARM NEON Crypto functions
Click to expand...
Click to collapse
Download :
Velocity v1.1 <- Mirror
Velocity v1.0 <- Mirror
Camera Fix
Changelog :
v1.1
- Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
- Numerous fixes from android kernel_common 3.10 and 3.10.y repos.
- Enabled Conservative governor
v1.0
- Initial release
Installation :
1. Download and save the latest zip to your phone
2. Flash this zip from any custom recovery (eg. TWRP, CWM, Philz)
3. If camera doesn't work, perform steps 1 & 2 for the zip containing camera fix
Recommended Settings :
Min. CPU freq. : 400MHz (Under this might cause SOD)
GPU Governor : simple_ondemand
I/O Scheduler : FIOPS
Read-ahead size : 1536 kB
Intelliplug profiles :
* For general use : Eco Performance/Eco Conservative
* For gaming : Balanced/Disabled
Kernel apps : FauxClock, Kernel Adiutor, Trickster MOD
Credits :
@varun.chitre15
@faux123
@Christopher83
XDA:DevDB Information
Velocity Kernel, Kernel for the YU Yureka
Contributors
neomanu
Source Code: https://github.com/neomanu/android_kernel_yu_msm8916/tree/cm-11.0_exp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.1
Stable Release Date: 2015-03-11
Created 2015-03-07
Last Updated 2015-03-11
Reserved
ooo new kernel...
hello bro first of all thanks for contributions towards Development of yu yureka..
Now downloading...
FEEDBACK AFTER SOME HOURS OF PLAYING....
Hey, can I flash it directly on other custom kernel
screen shots??
ankurvvvv said:
screen shots??
Click to expand...
Click to collapse
Its a kernel not a rom. What do you need screenshots of?
My bad. too excited with my new Yureka that not paying attention to anything
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
question
MIUI custom ROM supported???
sunilnair007 said:
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
Click to expand...
Click to collapse
you are talking about proximity sensor issue , is it right?
Sent from my AO5510 using XDA Free mobile app
Review after using a whole day.
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
How to make best use of it.
Installed this kernel.
However, it seems very complex to make best use of it by a person like me who is not used to Custom Kernels. Before this I have used ThunderZap2, and Xcelerate, without much of tweaking. In Xcelerate for example, I found that different cores where shutting down by default. Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
tons of thanks to you bro... for kcal addition
Bro thanks a lot for adding kcal colour management to YU yureka..
Very nice bro..
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
[KERNEL][3.10.71][KCAL] Velocity v1.1
Seems developer worked hard and results are visible.
No complaints so far testing since morning.
Need 2 days time to give a stable review.
Best wishes and please keep this spirit intact
Regards
Tarry! said:
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
Click to expand...
Click to collapse
Noticed this too. Pressing the volume buttons once/twice, when it is unresponsive, wakes it right back up.
esukhdev said:
Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
Click to expand...
Click to collapse
Firstly, I'll try to simplify the recommended settings.
Secondly, hotplugging is not enabled by default.
Enable it by going to CPU Hotplug in Kernel Adiutor and enabling Intelliplug.
DGEEEK said:
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
Click to expand...
Click to collapse
Set the Intelliplug profile to Eco Conservative/Eco Performance to hotplug upto 7 cores.
I'm looking into the cluster problem as mentioned.
To run cooler, try reducing the max frequency.
Tarry! said:
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
Click to expand...
Click to collapse
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
androidgalaxyman said:
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
The issue is that if you set performance profile to "Power save", gov "ondemand" & min frequency lesser than 500MHz, phone sleeps to death & you have to hard reboot to get back on. Its a known bug and is present in stock kernel too. Check if settings i stated are the reason for you. Doesn't happen with "Interactive" because it never scales lower.
Sent from my AO5510 using XDA Free mobile app
@neomanu , Do I need to wipe cache and dalvik cache while flashing this kernel over any ROM. Also I have flashed a custom kernel previously and now I want to flash this, so Should I simply follow your instructions or need to wipe something.
No Need to wipe anything. To give u extra boost you can wipe dalvik cache which will rebuild cache again and its always good. no need of cache or data wipe
Is this kernel support's volte?
Sent from my AO5510 using XDA-Developers Legacy app