Develop Bugs

[KERNEL][CM7/MIUI][03/01/12] Glitch V13.1 - OC/UV - Voodoo - Glitchy Speed

{
"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"
}
These kernels are provided as-is without warranty. I'm not responsible for any problem you can encounter with your phone or if your cat suddenly dies.
Although, don't expect support even if I will eventually help since I love cats.
Note : These kernels are only compatible with CyanogenMod and MIUI roms !​
Do you want to discuss on this kernel, get the fresh news on development, or become a kernel tester ?
Join the IRC channel from your web browser herehttp://webchat.freenode.net/?channels=glitchkernel ! No registration needed
Make sure the channel is "#glitchkernel" and you're set.
For those who already have an IRC client,
here is the server : irc.freenode.net
port : 6667
Channel : #glitchkernel​
Overview :
- Up to 1.7GHz CPU OC with added bus/GPU OC (Thanks to morfic for the great base of work)
- Undervolting (using third party apps)
- Voodoo Sound & Voodoo Color (Thanks Supercurio & renaudallard)
- FPS uncap (Screen running 68Hz instead of 60Hz, from 56 to 66 FPS max) from JPX source
- Various tweaks for more smoothness and reliability
- LED notifications using Neldar's BLN
CHANGELOGS IN #2 POST​The frequency/voltage & informative UV settings table is as follow for V13 kernel :
Note that these UV settings will be unstable on many devices. It's only informative.
1700 MHz - [email protected] 243 MHz - 1.500v / -> Most phones will fail here. -25 to -50mV may help to stabilize. Much stabler as unique frequency for benchmarks.
1600 MHz - [email protected] 229 MHz - 1.500V / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - [email protected] 250 MHz - 1.500V / -25mV
1440 MHz - [email protected] 240 MHz - 1.475V / -50mV
1400 MHz - [email protected] 233 MHz - 1.450V / -50mV
1300 MHz - [email protected] 217 MHz - 1.400V / -50mV
1200 MHz - [email protected] 200 MHz - 1.350V / -50mV
1000 MHz - [email protected] 200 MHz - 1.250V / -50mV - If you have stability issues, try to let this one by default.
800 MHz - [email protected] 200 MHz - 1.200V / -75mV
400 MHz - [email protected] 200 MHz - 1.050V / -100mV
200 MHz - [email protected] 200 MHz - 0.950V / -150mV
100 MHz - [email protected] 100 MHz - 0.950V / -200mV - (can be very different between two devices)
GPU frequency is linked to bus speed
More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.
Considering all phones will respond differently to OC/UV, to tweak the values to suit your device will be required.
By default, no overclock/undervolt is applied. You'll need to use one of the tools below to adjust the frequencies and voltages.
-Pimp My CPU (recommended if you're using MIUI) : http://forum.xda-developers.com/showthread.php?t=1018411
-Voltage Control : http://forum.xda-developers.com/showthread.php?t=829731
-SetCPU : http://forum.xda-developers.com/showthread.php?t=505419​
Downloads
Glitch kernel (CWM flashable only)
Glitch Kernel Updater app now available on the Android market to support us !​i9000 :
- 03/01/2012 - V13.1​Other supported devices : Captivate, Vibrant, Telus Fascinate, Verizon Fascinate​
OLDER RELEASES​LIVE OC GUIDE​FAQ, Changelogshttp://forum.xda-developers.com/showpost.php?p=13021804&postcount=2http://forum.xda-developers.com/showpost.php?p=13021804&postcount=2​​
-------------------------
Source :
- Glitch repo : https://github.com/organizations/Glitchkernel
Who is the Glitch team ?
- Kernel developement : ssewk2x & Tk-Glitch.
- Public relations / web hosting : Sixstringsg.
- App developement : Smasher816.
- Beta testers team, with members coming and leaving
Credits :
Codeworkx, Pawitp, Atinm, GuiPerPT, Unhelpful, Coolya, Morfic, Ezekeel, Zacharias.maladroit, Bilboa1, TheEscapist, Netarchy, Supercurio, lippol94, MAMBO04, Galnet, nitr8, Rahulrulez, Chadouming, renaudallard, existz, times_infinity, bearsfan85
Thanks to the donators and everyone bying the Glitch Kernel Updater app from the market, it's much appreciated and encourages us to continue our work !
Thanks to the beta testers team and to everyone helping me to debug and find new useful things to integrate !
Without all of you, this kernel wouldn't be !​

Changelogs :
V13 - LATEST
03/01/2012 - V13.1
- Cleanup.
- Fixed buttons freezing randomly.
- Fixed media buttons / headset buttons.
- Lots of GPIO fixes which eliminate phantom keypops.
- Added updated sysfs interface for smartass governor.
- Updated screenstate scaling script to use non-deprecated sysfs
interface for smartass2 and other govs.
- Back to CM7 LED Notifications.
- Lots of changes to cypress touchkey driver to guard against phantom
keypops and speed things up.
- Removed CarrierIQ-related virtual serial device. It probably wasn't
used, but now we know for sure.
- Changes to dpram (modem kernel interface) to make the radio a
little more stable.
- slightly more helpful gamma table error message.
- Moved call audio sysfs files from voodoo sound group to their own.
- Integrated 90call_vol into the kernel zip file so people don't
have to mess with it on their own.
- Now possible to choose any governor as sleep governor in the recovery.
- Vandalized bootlogo a bit.
20/11/2011 - V13
- Upstream synced to the latest at release time
- New CFLAGS again
- mfpu switched from neon to vfpv3
- BLN now working correctly, with LED timeout (thanks to Zacharias.maladroit)
- Back to hard float
- Updated toolchain to 4.5-2011.10
- Modified screen colors to look better (ugly gradient fixed, yellowish tint fixed). Don't use Voodoo Color punchy settings with this though (green screen likely to be back)
- Better reactivity under load
- 348MB RAM available
- Better 720p video recording (less buggy)
- Doubled SDCard read cache - Slight speed-up on SDcard read speed
- USB power drain fix
- Better memory management
- Back to 3.0V for the screen - 2.6V said not to give more battery life because of the added amperage
- Bugfixes
- Added Cgroup timer slack to group tasks by timer slack value
- Switched to Tree preempt RCU and added RCU boost
- New rethemed/recolored recovery menu and bootlogo, thanks to Fate-Silver for the blood
- Fixed "GLITCH" menu in recovery not showing for i9000 and Telus Fascinate
- Better handling of the CPU frequency table, + fixes
- Fascinate related fixes and updates from JT1134
- Added Lazy and SmartassV2 governors
- Fixes for SDCard handling
- All leakage settings are now available from a single kernel. Use the GLITCH menu in recovery (recommended way to switch the values)
- Added support of JT's 3-button recovery hack (credit to JT1134)
​V12
13/07/2011 -> 29/09/2011 - V12 BETA #3
- BackLightNotifications (BLN) port, thanks to Zacharias.maladroit must use the BLN app. If it doesn't work, try Blinky. Still not fully working though.
- Some cleaning and added tiny fixes
- Fascinate : Now using Yamaha compass driver from ED01
- *Temporary* fix for green flashes/colors on low brightness (reborn/still not fixed in V11 - not yet proper though)
- Modified color multiplier to avoid yellowish tint by default
- Enhanced cleaning script when flashing
- Screen undervolt (from 3.0V to 2.6V) // it should help battery life
- Lowering kernel debugger buffer
- More work on leakage values
- Adding some old-school (V9D) CFLAGS resulting in substantial performance and stability gains
- 800MHz random lock fixed - not fully fixed it seems
- Popping keyboard bug fixed
- Make use of NEON accelerated mfpu
- Slightly more aggressive ondemand governor default settings // searching the best balance for efficiency
- Added a few speed enhancements
- In-call receive audio is much louder across the board. You can now hear your significant other yelling at you if you're in a noisy area. Sorry, guys
- In-call mic gain should see some improvement as well. Meaning your wife can now hear you apologizing better
-- caveat: I've heard conflicting reports about this while using bluetooth. I'm investigating that, so stay tuned.
- Overhauled the screen state scaling feature.
-- governor setting now stays put
-- users can now enable/disable the feature and configure it via the custom recovery listed below
- New recovery. Screenstate scaling is controllable via recovery, and it's themed now.
-Audio output and input controllable via script linked in OP
-Call volume tweaks re-written to be more clean/effecient.
-Screenstate bug fixed, doesn't cause lag anymore.
-Upstream synced (this means you must be on the latest nightly for your device for this to work)
-New drivers
​V11
13/07/2011 - V11
- Upstream synced as always (updated recovery...)
- More debug stuff disabled & cleanups/fixes on various things
- Printk disabled to reduce overhead
- Updated to linux kernel 2.6.35.13
- OC implementation fixes and modifications (fixing overvolt in Voltage Control Xtreme as well as some other tiny things)
- Added experimental GPU OC implementation from TheExcapist (for future use / not yet functional)
- 1.7GHz step added - working on some pretty good phones
- Modified touchkey/Led notifications settings from Zacharias.maladroit
- Added SLQB
- Added SIO and BFQ schedulers
- Back to LZO compression for faster boot time
- New voltage settings for more stability
- Trying some new speed tweaks
- Better memory management
- 340MB of RAM available for user without breaking 720p recording
- Preemptible Tiny RCU
- Automated per tty task groups patch
- Added InteractiveX governor
- Two new branches for OC settings adapted to high and low leakage chips
- Toolchain sorcery, thanks to Zacharias.maladroit (RIL is compiled using 4.4.3 toolchain, and everything else is compiled using 4.5.2 toolchain -> more speed and stability)
- Enhanced Voodoo Color settings from renaudallard
- Voodoo Sound V10
- Allow CPU-supported unaligned accesses
- Logcat on/off scripts (built as module)
- Bluetooth HID support
- New, cleaner bootlogo
- Now cleaning old scripts, OC values, cache and dalvik cache on kernel installation - thanks to lippol94
- Green tint on low brightness fixed
- Switched to ondemand governor​V10
27/05/2011 - V10A Do not use with CM7 builds older than 23/05 (as well as the 28/05 or newer build) or MIUI -> you'll get no service !
- Now fully compatible with latest CM7 Nightly builds
- Back to 2010.09 toolchain -> slower & less stable but needed to make a working kernel for latest builds
- Upstream sync (bigger radio partition, headset stuff..)
- Int voltage changes to get some stability back on all overclocked frequencies
- A bit faster 1.5 and 1.6GHz steps - Could make these steps unstable for some, please try and report
- Smartass governor tweaked for faster scaling up, and slower scaling down -> better stability and speed
- OC code bugs and inconsistencies introduced in V7B now fixed (it was here to prevent sleep of death issue, now fixed)
- Some fixes and enhancement for compatibility with Xan's Voltage Control app
- Various tweaks for MOAR SPEED
- Black magic
Known issues :
- The reboot recovery command seems broken for some reason on recent builds. Probably rom related.
- Some users still get freeze issue on boot. If you have this issue, please use the "no-optimization" kernel for you device from this post : http://forum.xda-developers.com/showpost.php?p=14180722&postcount=2077
03/06/2011 - V10B To use with newest builds only (equal or newer than 28/05) !
- Upstream sync (FM radio, new Voodoo Sound implementation, etc...)
- Back to 4.4.3 toolchain - needed for new RIL
- Big cleanup - rewrite from scratch
- Many fixes
- New tweaks for speed on 4.4.3 toolchain
- New tweaks for stability on 4.4.3 toolchain
- Black magic
17/06/2011 - V10C (Updated) To use with newest builds, #28+ for i9000 or equivalent
- Upstream sync (cpuidle, updated drivers (wifi etc.), Recovery 4.0.0.x, etc...) (updated as of today 17/06)
- More debug stuff disabled
- Dock audio support (experimental)
- Added DIDLE (Deep Idle) support (removed, buggy)
- New voltage tweaks for added stability on some devices​V9
16/05/2011 - V9A
- Merged with the now dead V8C update because of new added features
- Upstream sync : Calculate battery percentage as percent of max capacity reported when battery full, new wifi driver, etc.
- New PMEM settings for more available RAM (now 331MB)
- 1.54GHz step added with some gentle settings for now.
- New step by step frequency switch when scaling down (part of the Galaxy S II port from Bilboa1) - more stability on highest frequencies
- Corrections and further tweaking on smartass governor + some fixes from Netarchy (Nexus S). 400MHz lock when screen is on removed (not needed anymore -> more power saving)
- Higher cache for faster SDcard read speed
- New sleep settings : Effective lock to 400MHz max when screen is off -> fix long wake up/hiccups when playing music or similar use. Be careful with your UV settings on 200 and 400MHz steps to avoid sleep of death problems ! These were not used on previous versions of my kernel (locked to 100 MHz when screen off and locked to 400MHz when screen on with a buggy gap in smartass governor forcing generally 600+ MHz)
- 600 MHz step removed (it was generating instabilities on some phones when jumping to 800 or down to 400 when using UV)
- Some voltage tweaks for added stability on some devices (as always)
- Cleanups on unused/no more needed stuff
- Little surprise, thanks to Morfic
- Updated to V9A² to fix SOD and some performance issues
21/05/2011 - V9B
- Upstream sync (CWM recovery 3.1.0.1, better screen colors (kills voodoo color for now and looks awful on my 0516 build, but should be good on latest), GPIO fixes, samsung modemctl...) + small changes on my side for official CyanogenMod repository compatibility
- Voodoo Sound updated to V9 / cleaned voodoo color stuff until it works again
- New cleaner bootlogo based on the one in first post, preferred by most users
- Some additional compilation flags from Netarchy and Zacharias.maladroit (better overall performances + NEON)
- Screen refresh frequency bumped to 72Hz (68Hz effective). It'll uncap FPS to 66 again but seems stabler than before on framerate (the divide/2 behavior happens less)
- Added screenstate scaling script from well.heeled.man as a test (with my kernel's smartass default settings). It should give better sleep power consumption as well as better power efficiency on screen off tasks like music playing etc. by switching to conservative governor.
If you want more information, discuss on this or contribute to enhance it, please come here : http://forum.xda-developers.com/showthread.php?t=1087646
- Adding some stuff from Zacharias.madadroit :
- Higher battery charging temperature
- Scheduler tweaks​
Alternative version now available (V9B-VC) using old AMOLED panel color/gamma settings and with Voodoo Color V2 added back.
24/05/2011 - V9C TO USE WITH CM7 Nightly build #12 OR HIGHER ONLY
(Updated to fix "no service" issue, but still sucks.. unstable on #12 build, very stable on others but no service)
- Upstream sync (PMEM disabled (gives 339MB RAM now), new RIL, headset fixes...)
- Divider changes for MUCH better stability on 1.2GHz at the cost of a slight decrease on performances
- New branch with Voodoo Color display driver and "old" color settings named "VC"
- Fix for Vibrant no service problem - hopefully
- Small changes on smartass governor for better scalability (reverts some old settings not needed anymore with the screenstate script)
- Glitch logo now in update script too for nanu_x2 to be amazed when installing my kernel
24/05/2011 - V9D TO USE WITH CM7 Nightly build #11 OR LOWER (for i9000, or cappy/vibrant equivalent) AND MIUI ONLY
First "D" revision.. Sound like duty. It's basically a fix of a fix done to make the V9C features available for "stable builds" (considering the i9000 #12 isn't)
- Obviously all the V9C changelog
- Using old RIL to be compatible with builds before #12 for I9000 (--> WON'T WORK with #12 for i9000 or equivalent !)
- Replaced 1.54GHz step by 1.6GHz (1.54GHz step was somewhat useless, too close to 1.5Ghz, and slower overall because of the lower bus speed)
- I can't build Vibrant ATM, the CM7 build system is broken on this device or I'm doing something wrong but I wasn't able to fix it. Any help is appreciated. I'm sorry for Vibrant users I'm screwed.​V8
07/05/2011 - V8A - To use with 05062011 or newer CM7 build (useable on MIUI RC8 but you'll lose camera - MIUI needs an update)
- Upstream sync (camera fixes etc.)
- More stability fixes
- Cleanups on OC code (found that 1.2 and 1.3GHz were very unstable compared to earlier releases)
- More work on Vibrant/Captivate. The kernels are now available to download but are untested - for now. Feel free to try and report any problem or if all runs well. If I have enough positive reviews, these kernels will be released in their respective device sections.
11/05/2011 - V8B
Upstream sync only :
- USB switch suspend
- TV out stuff
- Fascinate specifics
- Revert "Got back to previous samsung_modemctl" for 05112011 CM7 build​
V7
02/05/2011 - V7A - To use with 05012011 or newer CM7 build and MIUI RC8+ only
- Resurrect Voodoo Color killed by 2.3.4 merge.
- New step for 1.5GHz on top of 1.44GHz (now 9 steps total versus 8 before)
- Forcing 400MHz max when sleeping for added battery life (default = 800). Couldn't detect any side effect.
- New tweaked Smartass governor now default (800MHz min when screen on). Please report your experience
- It seems the smartass governor is not working by default, it will revert to performance >< Please force it to get it to work -> Ok found the problem, I'll update in a min
- Now updated to V7A-2 to fix the governor bug
03/05/2011 - V7B - To use with 05012011 or newer CM7 build and MIUI RC8+ only
- Resurrect Voodoo Color killed by 2.3.4 merge - Again - fully working now
- Fixed sleep of death issue when unplugged
- Switched to LZO compression for better overall speed and reduced boot time
- Tweaked smartass governor more for - hopefully - better battery life and a bit more responsivity
- New voltage and frequency table rewrite as a bonus with now 11 frequencies total
- Stability fixes on 1.5GHz step -> please test and report
- Reverted FPS uncap - at least for now - for two main reasons : more stability on high GPU freqs (1.4GHz and more), and to prevent FPS limit at max/2 (33 when unlocked to 66), limiting overall performances in heavy scenes. I think there's a lack of buffering somewhere.. It will give higher scores on some benchmarks, and lower on others. A better battery life can indeed be expected too.
- Upstream sync
05/05/2011 - V7C - To use with 05032011 or newer CM7 build and MIUI RC8+ only
- Upstream sync (better battery life, reboot recovery, etc.)
- A general stability fix missing from V7 branch added back
- Tiny tweaks on the voltage table
- Big bugfix on the V7 branch (redone from scratch, cleaner)
- Switched to 2011.03 toolchain
- Added some optimization flags, "-mfloat-abi=hard" being one of them (up to 40% performance gains in specific cases)
- Small improvements here and there​V6
WIP
22/04/2011 - V6pre - preview/work in progress of upcoming V6A update *test* :
- Reverted PMEM settings to new CM7 default (317MB - same as V5A)
- Reverted some stability fixes that weren't that stable on some devices, or even prevented some to boot
- New voltage table for a more linear increase, improving stability at default settings
- Switched to Deadline scheduler by default as it appears more stable
- Back to 2010.09 toolchain for speed and efficiency
- Synchronized with last update from SGS CM7 team
Better to use CM7 04212011 update with this kernel and newer.
22/04/2011 - V6pre - update 1 :
- Battery polling bumped to 15 sec (was 1 before), it should help battery to an extent (thanks to Zach for the idea)
- Some internal voltage tweaking to hopefully be more UV friendly
- Bumped USER_HZ for more smoothness
- Another -rare- bootloop fix
22/04/2011 - V6pre - update 2 :
- Added some tweaks from V5A for testing
- Resolved a bug generating fake voltage reading
- Resolved a bug on 400MHz step generating instabilities
- Slight changes to the voltage table
- Fixed a typo
- Trying some toolchain switch - again-
23/04/2011 - V6pre - update 3 :
- Corrected Led Notifications - Now it should work properly again !
- Various bugfixes and typo corrections
- Toolchain change once again
- Added new Interactive governor with aggressive settings for even more speed. You need to change it by app (pimp my cpu/cyanogen settings), it's still on conservative by default.
(thanks Zach for your suggestion)
25/04/2011 - V6pre - update 4
- Cleanups on Led notifications to resolve a bug (buttons stopped working randomly for some users)
- More typo corrections
- Voodoo Sound V8
- Various bugfixes on CPU load and schedulers
- CONFIG_CC_OPTIMIZE_FOR_SIZE disabled for speed
- Lower latency on GPU states switch for stabler performances
- Added a stability fix for voltage change latency when frequency is changing. It should give more stability with high undervolt or big voltage differences between two steps - Please test and report ! (Thanks Zach for pointing that to me)
- Two versions for testing purposes : V6pre-u4 is compiled using GCC 4.5.1 toolchain, and V6pre-u4(alt) is compiled using GCC 4.4.3 one. If you get instabilities on the first one, try the other and vice versa. Please report your findings on that because it was the first stability differences source between my kernel revisions. For information, V6pre-u2 was compiled with 4.4.3, and u3 with 4.5.1.
27/04/2011 - V6pre - update 5 >> 6
- Name changed from "TkGlitch" to "Glitch"
- Cleanups on buttons (Kangsterizer)
- Lower latency on GPU states switch for stabler performances in 3D and/or at high GPU frequency - corrected, thanks to Kangsterizer
- Added a stability fix when frequency changes for cpufreq governors
- Tweaked Interactive and Conservative governors for testing
- New Frequency table : 1.5GHz is now the max selectable frequency, and 800MHz and 400MHz steps are now replaced by a unique 600MHz one.
- Changed initramfs source to remove the annoying "E:no misc partition" error in the recovery
- Now bumped to update 6 to fix an issue with the conservative governor.
27/04/2011 - V6pre - update 7
- New Frequency table : 1.44GHz removed, 800 and 400MHz steps are back.
- Battery polling bumped from 15 to 30 seconds
- GPU power latency bumped from 10 to 60 ms
28/04/2011 - V6A - To use with 04282011 or newer CM7 build only
- New sensors drivers added
- Normalized 1.5GHz bus speed (GPU will now run @ 250MHz versus 247MHz before. It can affect your stability !)
- Int voltage lowered for 1.5GHz step because it did have a bad effect on lower frequencies stability
- GPU power latency back to default - but fixed (100ms)
29/04/2011 - V6B - To use with 04282011 or newer CM7 build only
- New initramfs source to fix compass and update CWM recovery
- 1.5GHz replaced by 1.48GHz for stability
- New voltage table as requested by many users (+25mv on 1200 to 1400MHz steps)
- New interactive governor for better scaling and battery life
- New tweaked smartass governor for testing (pretty bad on CPU benchmarks for some reason, please test how it feels in real world use)
- New ondemand governor from Zacharias.maladroit sources for testing
02/05/2011 - V6C - To use with 05012011 or newer CM7 build only
- Small update to merge with 2.3.4 source, no new feature.
02/05/2011 - V6C² - To use with 05012011 or newer CM7 build only
- Update to repair Voodoo Sound conflicts from 2.3.4 merge.
- Back to 1.44GHz max to prepare 1.5GHz return​
V5
19/04/2011 - V5A - Initial release
21/04/2011 - V5B :
- GPU overclock on 1.3 GHz added (217MHz / +8.5% from default)
- New PMEM settings for more available RAM compared to V5A (now 328MB)
- Stability fixes for all frequencies, needing globally less volts. Results may vary depending on the device
- Switched to Conservative governor by default (still switchable by app). It can feel less responsive coming from idle but more battery saving, and plays better with high frequencies.
- New voltage table. Default settings should be stabler for most devices.
- Switched to 4.4.3 toolchain for added stability on some sensitive devices
Captivate and Vibrant support will come later. It will need more time than expected.
21/04/2011 - V5C : Small update to fix a bootloop issue on some devices.​

Tk-Glitch said:
Changelogs :
19/04/2011 - V5A - Initial release​
Click to expand...
Click to collapse
will try and report, thanks

Tried it out, feels amazing, thanks so much! Yet to try 1.4 though
Sent from my GT-I9000 using XDA App

Thanks a lot, goign to try it soon.
I have a question: what is a stock frequency of GPU and is it possible to control it?
If no, can you release 2 versions: with and without GPU OC?

andrewin said:
Thanks a lot, goign to try it soon.
I have a question: what is a stock frequency of GPU and is it possible to control it?
If no, can you release 2 versions: with and without GPU OC?
Click to expand...
Click to collapse
The stock frequency for the GPU is 200MHz. It's not possible to control it directly because it's linked to the bus. The bus clock being a fixed value by frequency step.
Up to 1300 MHz, the GPU runs at 200MHz. At 1400MHz it runs @ 233 MHz, and at 1440MHz it runs @ 240MHz.
The bus frequency increase will lead to higher memory bandwidth and a better productivity from the CPU.
A version without GPU OC would mean with lower global performances too on the highest frequency steps, but better stability for some sensitive devices.
I'll wait a bit for more opinions if you're okay, and if some of you wants a stock GPU version i'll do it, no problem

Hm.. after flashing i got boot loop..
I'm on MIUI
Sent from my GT-I9000

What kernel did you use before ?

great
man, you are so cool... bilboas kernel died in development, and platypus is soo lagy, and still autorotation problems... thank you for this, everything looking working great, so far...

looking great on first install. I like it! Thanks.

Tk-Glitch said:
Up to 1300 MHz, the GPU runs at 200MHz. At 1400MHz it runs @ 233 MHz, and at 1440MHz it runs @ 240MHz.
The bus frequency increase will lead to higher memory bandwidth and a better productivity from the CPU.
I'll wait a bit for more opinions if you're okay, and if some of you wants a stock GPU version i'll do it, no problem
Click to expand...
Click to collapse
That's OK because I am not going to OC that high and will keep at 1200 as maximum.
Thank you once again for your efforts.

I have zacharias last kernel can install this one over?
Sent from my GT-I9000 using Tapatalk

@ mosd Sure you can. His init.d scripts could interfere with stability and/or speed though I don't know. You'll have to tell me, I didn't test that at all ^^

Tk-Glitch said:
@ mosd Sure you can. His init.d scripts could interfere with stability and/or speed though I don't know. You'll have to tell me, I didn't test that at all ^^
Click to expand...
Click to collapse
OK should i install other kernel then yours?
Sent from my GT-I9000 using Tapatalk

mosd said:
OK should i install other kernel then yours?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
To delete the scripts ? Not needed, you can do that with zach's kernel.
For something else.. hmm.. not needed, you can flash mine directly^^

If I'm on Miui and install your kernel do I still have to install the gpu drivers u put up?
Sent from my GT-I9000 using Tapatalk

@mosd
If it's the latest MIUI, I don't think so. This driver should already be included.

Thanks for answers man
Sent from my GT-I9000 using Tapatalk

No problem

Since the gpu oc is linked to cpu oc I suppose it's impossible to make gpu clock higher from 1300mhz..right?cause not all phones clock up to 1400

Paranoid Android w/Franco.kernel, first impressions

Hi all,
with this post I want to suggest a configuration for those who want to give a boost to their GN and also want to have good battery life and a better look.
I've tried out Paranoid Android 3.15 (JB 4.2.2) rom on my GN with the latest GApps, flashing the kernel with the one provided by Francisco Franco (franco.kernel). This kernel gave a new life to my battery (-1% per hour with screen off).
Thanks to a previous post in this forum, I also modified some settings in the Francisco Franco update app:
Max Frequency: 1305 MHz
Min Frequency: 192 MHz
Governor: interactive
Governor Tunables: 15000 / 95 / 729 MHz / 45000 / 15000 / 85
IO Scheduler: row
IO Scheduler Tunables: 100 / 75 / 5 / 4 / 4 / 3 / 2 / 15 / 25
Read Ahead Buffer: 512; NR Requests: 512
TCP Congestion Avoidance Algorithm: westwood
Color Multipliers: 190 195 215
RGB Gamma: -4 0 5
Trinity Contrast: -5; OMAP4 Gamma: Disabled; CAB: Disabled
Click to expand...
Click to collapse
With his stock kernel, the PA rom is good and responsive; Franco.kernel gave a boost to my GN wich is now way faster and with smooth transitions. Before changing the kernel, the AnTuTu score was of approx 5300 points. With Franco's one the score was of 8000 points (see attached screen).
I've also installed Holo Glass (beta) Theme (which I suggest, it's beautiful and lightweight), using it with the Phablet option provided by PA (just ignore and apply when prompted to leave or continue anyway applying the theme, in use there are no particular issues).
I'm a newbie of the forum so I cannot insert links to post screenshots, so I upload a zip with the screens.

Now try doing some bluetooth streaming to your car stereo at that lower frequency - you'll hear a faint noise coming your phone as it squeals with pain and anguish.

Those are my settings taken directly from my settings post. Quote me properly or give me credit next time please.

just read your post. yesterday i installed PA 3.15 with Franco 376 and it my battery got drained. maybe i want to apply your setting to trickstermod. thanks...

[KERNEL] AlterNdromadus 3.0.x JB (CM10+, AOSP 4.x, SlimBean) R11 [3.0.101][25/03/14]

I will try to keep this up to date. I'm not a developer, I like mucking about with stuff.
Please give feedback, in the very least just vote on the poll, and I am entirely open to suggestions! I would love to hear from you.
Please try to keep this thread tidy, and if you're reporting issues then logs and a last_kmsg would be greatly appreciated.
Lastly, I hope you enjoy this kernel, attached below, and info about compiling in post #2.
-{ AlterNdromadus }-
This is ultimately tweaked for performance. Therefore if a governor, for example, has (tweaked) next to it, it is likely to be more so towards the performance side.
None of these features should really have a negative impact on battery life, however, in fact some should improve it.
Any orange text shows where updates have occured
-{ For Android JB 4.1.x - 4.2.x | CM10 - CM10.1 | SlimBean | MIUI V5 }-
3.0.101
Latest Andromadus source: 24/08/13
...also cherry-picked new stuff from the andromadus_4.4 branch
Built with @Christopher83 's latest Custom toolchain and -O2 optimizations
Governors: Interactive, Ondemand, Conservative, Performance, Powersave, Userspace, Dynamic Interactive
I/O Schedulers: Noop, CFQ, BFQ, Deadline (tweaked), ROW, Zen (default)
More frequencies (see frequency table below)
Undervolted frequencies below 1.4GHz (See frequency table below)
Frequency table:
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 0, 24576, LPXO, 0, 0, 30720000, 800, VDD_RAW(800) },
{ 0, 61440, PLL_3, 5, 11, 61440000, 800, VDD_RAW(800) },
{ 0, 122880, PLL_3, 5, 5, 61440000, 800, VDD_RAW(800) },
{ 0, 184320, PLL_3, 5, 4, 61440000, 800, VDD_RAW(800) },
{ 0, MAX_AXI_KHZ, AXI, 1, 0, 61440000, 800, VDD_RAW(800) },
{ 1, 245760, PLL_3, 5, 2, 61440000, 800, VDD_RAW(800) },
{ 1, 368640, PLL_3, 5, 1, 122800000, 800, VDD_RAW(800) },
{ 1, 544000, PLL_2, 3, 0, 122800000, 900, VDD_RAW(900), &pll2_tbl[0] },
{ 1, 600000, PLL_2, 3, 0, 122800000, 925, VDD_RAW(925), &pll2_tbl[1] },
/* AXI has MSMC1 implications. See above. */
{ 1, 768000, PLL_1, 2, 0, 153600000, 950, VDD_RAW(950) },
{ 1, 806400, PLL_2, 3, 0, 192000000, 1025, VDD_RAW(1025), &pll2_tbl[2]},
/* AXI has MSMC1. End */
{ 1, 1024000, PLL_2, 3, 0, 192000000, 1100, VDD_RAW(1100), &pll2_tbl[3]},
{ 1, 1200000, PLL_2, 3, 0, 192000000, 1100, VDD_RAW(1100), &pll2_tbl[4]},
{ 1, 1305600, PLL_2, 3, 0, 192000000, 1200, VDD_RAW(1200), &pll2_tbl[5]},
{ 1, 1401600, PLL_2, 3, 0, 192000000, 1250, VDD_RAW(1250), &pll2_tbl[6]},
{ 1, 1516800, PLL_2, 3, 0, 192000000, 1300, VDD_RAW(1300), &pll2_tbl[7]},
{ 1, 1612800, PLL_2, 3, 0, 192000000, 1400, VDD_RAW(1400), &pll2_tbl[8]},
{ 1, 1708800, PLL_2, 3, 0, 192000000, 1400, VDD_RAW(1400), &pll2_tbl[9]},
{ 1, 1804800, PLL_2, 3, 0, 192000000, 1450, VDD_RAW(1450), &pll2_tbl[10]},
{ 1, 1920000, PLL_2, 3, 0, 192000000, 1500, VDD_RAW(1500), &pll2_tbl[11]},
{ 1, 2016000, PLL_2, 3, 0, 192000000, 1550, VDD_RAW(1550), &pll2_tbl[12]},
{ 0 }
};
CPU Idle PM
2 Phase Ondemand
Preemptible UP-only small-memory-footprint RCU
RCU Priority boosting
Disabled disable heap randomization
Disabled various unneeded debugging stuff
Tons more stuff, see GitHub
-{ CHANGELOG }-
14/03/25 R11 - 3.0.101
I said I wouldn't update this... WELL I lied, deal with it.
Updated with lots of cherry-picks from the latest andromadus_4.4 branch
No more Lionheart (anyone mind?)
Zen scheduler
GPU OC
Simple GPU governor
new toolchain
more optimizations cherry-picked
GO HERE FOR ALL THE CHANGED THINGIES
(R10 still attached here for Justin Case)
13/10/04: R10 - 3.0.93
Updated to latest Andromadus source
Removed governors: asswax, lulzactive,
Added governor: Lionheart
Removed GPU OC
Removed some stuff which either sucked or didn't work
Sorry for the wait
13/07/04: R9 - 3.0.85
Fixed GPU 2D OC
Removed lowmemorykiller 3.9
Disabled an absolute ton of useless tracers and debugging stuff
Disbale cleancache (Somehow got reenabled at some point)
More stable, should have fixed reboots and performance issues
-{ CREDITS }-
The Andromadus team for their amazing source
@kylon for putting up with my incompetence and helping me far too much ( sorry!) and for lots of tweaks
@franciscofranco for his kernel source, I copied some tweaks
@Christopher83 for the toolchain
@bbedward for the Zen scheduler
@Shaky156 for the GPU stuff
The XDA community
Any one else I've forgotten, thank you so much​

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
-{ AlterNdromadus SOURCE }-
(Click on the GitHub Logo ^ for AlterNdromadus source)
Of course this is just forked from the mighty Andromadus htc7x30-3.0 kernel source so check that out as well.
-{ PREREQUISITES TO COMPILATION }-
Firstly, you need to know how to use Github. Read @eagleeyetom 's guide. Also read here so you know how to update to the latest Andromadus/my source.
Secondly, to update to the latest kernel version go to CodeAurora, then the boring bit: go through each update individually, click on patch, copy the contents into a file and apply the patch. (see how to do this in the guides below).
Thirdly, don't use the Android NDK, it won't work and Linaro is better anyway. Download the latest Linaro toolchain HERE and specify your path like so:
Code:
export CROSS_COMPILE=/home/PUT_YOUR_USERNAME_HERE/WHATEVER_SUBDIRS_YOU_PLACED_IT_IN/android-toolchain-eabi/bin/arm-eabi-
Last of all, if you're using my source, the AlterNdromadus config is vision_altern_defconfig . This has all the options enabled featured in the OP.
-{ COMPILATION }-
So, you're all set up and now you want to compile your own kernel from mine or the original Andromadus source? Here are some good guides I've found to help:
@TheWizardOfROMs 's [GUIDE] Build Your Own Android Kernel{Easiest and Fastest Way] [Using The NDK]
@thewadegeek 's [Tutorial] Building Your First Kernel
XDA University: Building a kernel from source
-{ ADDING FEATURES }-
Well, that was a bit of anticlimax... it's just like the original, but you compiled it... so you want to add some unique features?
XDA University: Adding features to your kernel
errrmm... there doesn't appear to much stuff on the web about modding kernels, so my advice is to search Github, look at other interesting source (here, here, and here), and just learn.
Have fun! ​

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
reserved

HTCDreamOn said:
reserved
Click to expand...
Click to collapse
Is this only for AOSP or CM roms? Can I use it in Sense rom?

Yeah right! You are becoming more and more of a developer with each passing day! Just keep up the good work and you'll be a recognized developer in no time!
I'll be adding this to the aroma package for cm10.1 soon, for now keep up the good work!
And yes this is for cyanogen ROMs and should work in aosp and possibly miui but I doubt sense, feel free to try but do a nandroid first of course!
Sent from my Nexus 7 using xda premium

HTCDreamOn said:
NTFS File system support (Read-only); testers would be appreciated
Click to expand...
Click to collapse
Didn't RW support fit in the kernel?
Other than that, looks pretty cool. Good job

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
NeverGone\RU said:
Didn't RW support fit in the kernel?
Other than that, looks pretty cool. Good job
Click to expand...
Click to collapse
I can enable writing to NTFS, I just didn't want to mess anything up, as I wasn't sure how well NTFS support would work. I'll enable it in the next release unless anyone has any problems with it.
By the way as a general note to everyone, if I'm not clicking your thanks button for giving me feedback it's 'cause I've reached my limit of 8 already.

Good job implementing the UKSM, let's hope it works well on our G2 just like it is on a desktop.

seems to be better battery life, and even faster
thanks

after flashing this kernel, my mobile turned damn slow and i cant even draw the security pattern at boot up.it seems cant even get my home page.. so lagging..
what can i do?

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
sharptv said:
Good job implementing the UKSM, let's hope it works well on our G2 just like it is on a desktop.
Click to expand...
Click to collapse
The developers of UKSM have a test that can be run, I'll try it and see what results it gives. It should be better than normal KSM though.
patek said:
seems to be better battery life, and even faster
thanks
Click to expand...
Click to collapse
Glad you think it's working well so not the same performance problems with AndromadusMod, then? (which I haven't abandoned, just having some trouble with it)
ramprabhu19 said:
after flashing this kernel, my mobile turned damn slow and i cant even draw the security pattern at boot up.it seems cant even get my home page.. so lagging..
what can i do?
Click to expand...
Click to collapse
Sounds odd, most people are experiencing better performance. What are your settings? Governor, CPU speed, I/O scheduler, anything you've enabled/disabled under performance settings and Developer settings? If nothing seems out of place then I'll release a version without the iosettings init.d script, admittedly I haven't tested this much.

i use ondemand, with noop or deadline...and cpu speed set @ 240-1800, ROM - cm 10.1 v 22.

FORCED Hard Reboots
i tried this kernel to attempt to get rid of the daily reboot that andromadus build 21 had for me.
unfortunately when using this kernel i got forced reboots about once every 4 hours with no warning, no lag, just boom HTC logo and BZZZZ
I have linked the cause here > http://pastebin.com/YtEkpt26
the kernel seems to be reporting incorrectly as 2.6, and the kernel itself crashed and obviously took the system down for a reboot
Also would like to note that this kernel had significantly worse battery usage and lagged doing basic tasks

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
ramprabhu19 said:
i use ondemand, with noop or deadline...and cpu speed set @ 240-1800, ROM - cm 10.1 v 22.
Click to expand...
Click to collapse
Have you got any mods installed, e.g. V6 Supercharger, Kick Ass Kerneliser, Cross Breeder, Seeder, anything else? I've just done a fresh install of B22 with this kernel and it seems fine to me, and I haven't installed anything extra apart from a keyboard remap and an apps to SD-ext script. Also, run Antutu or another benchmark app: I usually don't believe in benchmarks but if your getting obviously abysmal results then something must be wrong.
General notice: frandom isn't working by default, I'll need to edit the init.d script to autoload it. Hopefully you should see some more stuff in the next release as well :fingers-crossed: any suggestions?

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][22/05/13]
MissyVixen said:
i tried this kernel to attempt to get rid of the daily reboot that andromadus build 21 had for me.
unfortunately when using this kernel i got forced reboots about once every 4 hours with no warning, no lag, just boom HTC logo and BZZZZ
I have linked the cause here > http://pastebin.com/YtEkpt26
the kernel seems to be reporting incorrectly as 2.6, and the kernel itself crashed and obviously took the system down for a reboot
Also would like to note that this kernel had significantly worse battery usage and lagged doing basic tasks
Click to expand...
Click to collapse
If you already had forced reboots then I doubt that the kernel is the problem, but there's evidently something not right. I don't suppose you're using SmartassH3? I had problems with it before, but I thought I'd fixed it. Also I ran cat /proc/last_kmsg and it reports the kernel as 3.0.79 (as it should) and no errors. It sounds ridiculous, but it's as if you're not even using this kernel. It should report version 3.0.79 and gcc version 4.8, and your report says the build date was Mon 30th April 2013, it should say Wed 22nd May 2013. Try a completely fresh install of B22 with this kernel.

HTCDreamOn said:
If you already had forced reboots then I doubt that the kernel is the problem, but there's evidently something not right. I don't suppose you're using SmartassH3? I had problems with it before, but I thought I'd fixed it. Also I ran cat /proc/last_kmsg and it reports the kernel as 3.0.79 (as it should) and no errors. It sounds ridiculous, but it's as if you're not even using this kernel. It should report version 3.0.79 and gcc version 4.8, and your report says the build date was Mon 30th April 2013, it should say Wed 22nd May 2013. Try a completely fresh install of B22 with this kernel.
Click to expand...
Click to collapse
i have since wiped out /system and installed build 22. I have downloaded a kernel zip and discarded the old one, will update this post with results
--------------------------------------------------------------------------------------------------------------------
after a full wipe and install now reporting as 3.0.79, and with proper dates. maybe i had some sort of flag in my build.prop to kill error reporting ( but i dont recall that) essentially stalling it at the last rom that crash ?
this is now reporting properly, but still slow as molasses, and i am not sure why.
Scheduler is ondemand (its all i use, laptop or phone), speeds are set to stock 245/806. it just seems so much less responsive in comparison to the default for me

no didnt flashed any extra tweaks or anything... jus trie in a fresh, even it doesnt support me

RE: [KERNEL] AlterNdromadus 3.0.x CM10.1 R1 [3.0.79][25/05/13]
ramprabhu19 said:
no didnt flashed any extra tweaks or anything... jus trie in a fresh, even it doesnt support me
Click to expand...
Click to collapse
MissyVixen said:
i have since wiped out /system and installed build 22. I have downloaded a kernel zip and discarded the old one, will update this post with results
--------------------------------------------------------------------------------------------------------------------
after a full wipe and install now reporting as 3.0.79, and with proper dates. maybe i had some sort of flag in my build.prop to kill error reporting ( but i dont recall that) essentially stalling it at the last rom that crash ?
this is now reporting properly, but still slow as molasses, and i am not sure why.
Scheduler is ondemand (its all i use, laptop or phone), speeds are set to stock 245/806. it just seems so much less responsive in comparison to the default for me
Click to expand...
Click to collapse
OK I've just put a new build out, frandom and the init.d scripts should be working now, so hopefully this might give the performance boost you were missing. If it's still giving you worse performance, try over clocking a bit above stock, I find 1GHz a good middle ground for performance/ battery. Enable show CPU usage in developer settings to see if anything is acting suspiciously. Also I assume you have Max 2/3 background processes enabled in dev settings, it pretty much a requirement for the ROM.

link? not in op for now.

HTCDreamOn said:
OK I've just put a new build out, frandom and the init.d scripts should be working now, so hopefully this might give the performance boost you were missing. If it's still giving you worse performance, try over clocking a bit above stock, I find 1GHz a good middle ground for performance/ battery. Enable show CPU usage in developer settings to see if anything is acting suspiciously. Also I assume you have Max 2/3 background processes enabled in dev settings, it pretty much a requirement for the ROM.
Click to expand...
Click to collapse
i dont run the background process limit, i instead run a combined 600MB of swap space between cache and data. Had issues where it would kill off skype or andchat :S
But i am downloading this to flash and try again ^^, thank you for reading my post and changing things up for me. Im still not to the stage of making my own phone kernel yet
*******updates to follow*******
whatever all the changes did im not sure, but now it is smooth and responsive for me with the ondemand scheduler and 245/806. and battery life seems really good, with IMO/Skype/andIRC up for 8 hours i was at 50% *there was considerable screen off, but the wifi was being constantly used of course)

[KERNEL] [25/9] [LP][ KK] Carbon Kernel R5

CARBON KERNEL
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
R1
Bricked_hotplug
custom governors (conservative , ondemandplus , intelliactive, smartass, optimax, wheatley, n more )
new power management mode PowerSuspend for deep sleep fixes
frandom add
kernel mode NEON
LCD KCAL Color Calibration
Double Tap 2 Wake
Sweep 2 Wake+Sweep 2 Sleep
Multi Core Power Saving
Faux Sound 3.8
RAM management n optimization
Underclock upto 96 Mhz
dynamic fsync
simple algorithm for GPU from faux123
latest Linaro 5.1.1 (UBER) used for the build with full -o3 optimizations
R2
msm_hotplug and brick_hotplug (msm_hotplug enabled by default)
added state notifier
added USB fast charging
GPU overclock upload 650 Mhz
GPU underclocked to 100 Mhz
Franco Thermals added back with fixes
added governors
abyssplugv2
adaptive
badass
dancedance
darkness
hyper
intelliactive
intellimm
lazy
lionheart
nightmare
ondemandplus
optimax
pegasusq
slim
smartmax
smartmax_eps
uberdemand
wheatly
I/O schedulers added
BFQ
SIO
ZEN
FIOPS
VR
TRIPNDROID
Multicore powersaving enabled to aggressive by default
Added 10 new TCP cong
Used SaberMod 6.0 with -O3 optimizations
and much more check my github for more details
https://github.com/tarunkapadia93/android_kernel_xiaomi_armani/tree/cm-12.1
R3 :
compatible with CM R7 n Nameless R3 n the other lastest builds (that means no SystemUI FC any more )
based of caf kernels by @rebelos
few fixes
led notification light fixed
R4 BETA FINAL:
back to bricked hotplug with proper tuning this time
rebased of armani-dev kernel
video recording issue solved
dt2w & s2s+s2w added
new governor
same list of i/o
gpu max clock too 533Mhz (i dont see a real good scaling at 650 Mhz i m working on this part so pls wait)
R5:
Compiled with Linaro 4.9.4 Cortex A7 (Thanx to Christopher83)
O3 Optimizations
MultiROM support aka Kexec Patched
Works with Both KK n LP Roms
Hotplugs
Intelli_plug
Bricked_Hotplug aka MSM_MPDecision
MSM_Hotplug
Alucard_Hotplug
Governors
Intellidemand
Intellimm
Alucard
Hyper
Impulse
Pegasusq
Nightmare
Intelliactive
Yankactive
Smartmax
Zzmove
I/O Sched
BFQ
FIOPS
SIO
Zen
Vr
TripNdroid
CPU Overclock to 1.7Ghz
GPU Overclock to 590 Mhz
Double Tap 2 Wake
Simple Thermal Driver by @SultaXDA
Dynamic Fsync
Kcal Updates
Faux Sound
Much more
KNOWN BUGS :
LED NOT BLINKING SOMETIMES N STAYS SOLID
How to Install :
Boot into recovery
Wipe cache
Wipe dalvik cache
Flash kernel
Reboot and enjoy!
*use Kernel auditor(best) or Aero Kernel Control (full native sysfs best if you know what you are doing) to activate or tweak with kernel settings
## NOTE ##
After Flashing any Kernel Or Rom let you Phone Cool down to normal temp before you start using it. Pls dont complain the phone is heating n lagging. Flashing n things have heavy CPU usage so if will Heat.
Disable "Enable per-app Profile" if you are running benchmarks like Antutu
Downloads
Carbon kernel downloads
CARBON_KERNEL_LP_KK_25092015_1734.zip - 8.29 MB
its can be flashed on all aosp and cm based roms​
Thanx to everyone with helped me all the dev who i cherry-picked from thanx alot :angel:
XDA:DevDB Information
[KERNEL] [25/9] [LP][ KK] Carbon Kernel R5, Kernel for the Xiaomi Redmi 1S
Contributors
Tarun93, fellow kernel dev (kD a.k.a thewisenerd, zeroblade1984, LuffyXDA, armani-dev )
Source Code: https://github.com/tarunkapadia93/android_kernel_xiaomi_armani
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R5
Stable Release Date: 2015-09-25
Current Beta Version: R4 BETA Final
Beta Release Date: 2015-06-19
Created 2015-01-23
Last Updated 2015-09-25

Setting n tweaks
daily use settings
governor = alucard
i/o scheduler = BFQ
cpu = 300 min 1689 max
Alucard Hotplug
gpu mac clk = 450
DT2W will drain battery so think before you tweak around with the kernel n end up telling me your kernel is giving me **** Battery packup
Faux Sound
dont complaint if sound distorts at loud profile
loud profile is mean for full size cans (headphones) n similar things where you need a little more power
dont switch it on if you are using IEM (in-ear earphones) or normal earphones
i normally keep a setting of
digital output gain = 3
analog output gain=5
Hope that this clears some questions n helps you guys :fingers-crossed:

msm_mpdecision
show-p1984 said:
What is msm_thermal?
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic
delay = time between checks
pause = if something else plugs in the cpu, fall asleep for 10000ms
max_cpus_online_susp = if the screen is off, how many core should be active when the screen is off
enabled = enable(1) or disable(0) mpdecision. This does not affect max_cpus_online_susp
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (300000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
Some values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula.
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/msm_mpdecision/conf # ls | grep boost
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz.
Example: To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/msm_mpdecision/conf/boost_freqs
960000
960000
729600
576000
Why do I have no WLAN?
Due to this kernels very high optimization settings it is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort.
​
Click to expand...
Click to collapse
enabling n disabling a hotplug is simple
1 = enabled
0=disabled
to disabling a hotplug here is a example via terminal
Code:
echo "0" /sys/kernel/msm_mpdecision/conf/enabled
you can use third party apps too to make it a macro
i like aero kernel control available in the playstore
goto misc settings
tap "+" sign
navigate to the path you want n set the parameter as a macro
msm_hotplug
enabling n disabling msm_hotplug
/sys/module/msm_hotplug/enabled
other parameters
/sys/module/msm_hotplug/
msm_mpdecision
enabling n disabling the msm_mpdecision
/sys/kernel/msm_mpdecision/conf/enabled
other parameters
/sys/kernel/msm_mpdecision/conf/
intelli_plug
enabling n disabling the intelli_plug
/sys/module/intelli_plug/parameters/intell_plug_active
other parameters
/sys/module/intelli_plug/parameters/
MAKE SURE YOU DISABLE THE OTHER HOTPLUGS BEFORE YOU ENABLE ONE
if you enable intelli_plug make sure bricked_hotplug and msm_hotplug are disabled
if you enable msm_hotplug make sure bricked_hotplug n intelli_plug are disabled
bricked_hotplug is enabled by default as i feel its the best daily driver for max sot n battery life without compromising on performance
The zip adds module insertion to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14701 0 - Live 0x00000000
cifs 275399 0 - Live 0x00000000
bcmdhd 2964650 0 - Live 0x00000000 (C)
Then something went horribly wrong.
Chances are that I broke it and this should never happen.
One post in the issue tracker will probably fix it with the next release
You can restore wlan for your current bootup by executing:
Code:
adb shell
su
insmod /system/lib/modules/bcmdhd.ko

Thanks. Downloading. Gonna try asap. Will leave feedback.

bhu1 said:
Thanks. Downloading. Gonna try asap. Will leave feedback.
Click to expand...
Click to collapse
which rom are you trying it out on ??? pls mention the ROM if you can guys

Tarun93 said:
which rom are you trying it out on ??? pls mention the ROM if you can guys
Click to expand...
Click to collapse
Flashed it on cm11 RC16 for now, everything seems swift and smooth for now. Gonna leave more feedback soon on CM11 RC16.
Tomorrow I'll move to carbon RC6, will provide more feedback then.
Now, I'm gonna go and play around with the settings. Heh.
---------- Post added 24th January 2015 at 12:07 AM ---------- Previous post was 23rd January 2015 at 11:35 PM ----------
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
I did a standard test I do with all kernels that I try (I have tried all the latest versions of all kernels that are currently available), I close every app that is running in background using greenify, CPU is set to 1.6ghz - 300 MHz, intelliplug (eco mode disabled in urs, no other has eco mode, I use mp-decision on those which doesn't have intelliplug), on demand governer, GPU set at Max (550 on urs and beast kernel and 450 on others) and I play a 720p hevc video, on ur kernel i was getting the smoothest playback among all (It was lagging for the least amount of time, same lag times as beast kernel, so might be just cause of OCd GPU). But in any case, currently this kernel is the best performing and feature rich kernel available. Period.
I'll try other settings (especially eco mode), and will leave further feedback soon.
Thanks, I await further updates. Loving the increasing amount of kernels on our forums.

bhu1 said:
Flashed it on cm11 RC16 for now, everything seems swift and smooth for now. Gonna leave more feedback soon on CM11 RC16.
Tomorrow I'll move to carbon RC6, will provide more feedback then.
Now, I'm gonna go and play around with the settings. Heh.
---------- Post added 24th January 2015 at 12:07 AM ---------- Previous post was 23rd January 2015 at 11:35 PM ----------
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
I did a standard test I do with all kernels that I try (I have tried all the latest versions of all kernels that are currently available), I close every app that is running in background using greenify, CPU is set to 1.6ghz - 300 MHz, intelliplug (eco mode disabled in urs, no other has eco mode, I use mp-decision on those which doesn't have intelliplug), on demand governer, GPU set at Max (550 on urs and beast kernel and 450 on others) and I play a 720p hevc video, on ur kernel i was getting the smoothest playback among all (It was lagging for the least amount of time, same lag times as beast kernel, so might be just cause of OCd GPU). But in any case, currently this kernel is the best performing and feature rich kernel available. Period.
I'll try other settings (especially eco mode), and will leave further feedback soon.
Thanks, I await further updates. Loving the increasing amount of kernels on our forums.
Click to expand...
Click to collapse
Hey plz comment on the battery life, SOT also.... Thnx

bhu1 said:
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
Click to expand...
Click to collapse
This is what happens when you don't read the phuxking documentation.

thewisenerd said:
This is what happens when you don't read the phuxking documentation.
Click to expand...
Click to collapse
What do u mean by 'Documentation' ? If u inferring that I didn't read the OP, then I'll inform that I properly read it before flashing the kernel, it says nothing about this. I did notice that the feature list says 'Sleep 2 Sleep' instead of 'Sweep 2 Sleep' but nothing else. What am I missing here, buddy ?

bhu1 said:
What do u mean by 'Documentation' ? If u inferring that I didn't read the OP, then I'll inform that I properly read it before flashing the kernel, it says nothing about this. I did notice that the feature list says 'Sleep 2 Sleep' instead of 'Sweep 2 Sleep' but nothing else. What am I missing here, buddy ?
Click to expand...
Click to collapse
S2w work from bottom left to right,while s2s work from bottom right to left
press thanks if i helped you

Hsmetric181 said:
S2w work from bottom left to right,while s2s work from bottom right to left
press thanks if i helped you
Click to expand...
Click to collapse
I know that, S2W isn't working in any case.

Great Work.
Using this kernel currently with CM R16, everything is working fine.
Battery life is excellent for me. After nearly 15h - there is still 72% battery left. Usage: Screen on: 30 min, Wifi, Bluetooth always enabled.
Only thing so far is that Netflix is not working, but this might be totally Rom related, as it was also not working with the orginal kernel.

bhu1 said:
I know that, S2W isn't working in any case.
Click to expand...
Click to collapse
only s2w wouldnt work s2s n s2w both with be enable together

Thanks for this kernel tarun...really a great one...every thing works awesome...just by using trickstar mod...and this kernel is working for me on PAC latest nitly...just have to flash kernel comparability patch updated!!! Lol

little warm
is this only for me or not, but i feel little warm when using this kernel on carbon. and thats make battery reduce faster.

justian said:
is this only for me or not, but i feel little warm when using this kernel on carbon. and thats make battery reduce faster.
Click to expand...
Click to collapse
fir the first start yes it is let it cool down for a while n you are good to go it wont heat there after

is this working on Mokee 4.4.4 Nightly?

I cant turn the zram off. If i turn it off and save it emidiately gets turned on again. Am i doing something wrong?

everything is working for me guys.
bhu1 said:
I know that, S2W isn't working in any case.
Click to expand...
Click to collapse
S2W is also working properly for me. I am on CM11 RC16.

Tarun93 please mention the settings for best battery and best performance separately please coz I play games a lot and I want to get max battery when I'm not gaming .

[Kernel][FEATURED] Venom kernel v5 - DP9 [MM][N][O][Releases]

{
"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"
}
Venom Kernel for A7000 (aio_row)
Venom is designed for maximum performance and battery backup. It is made for people who depend on their phone every day.
It is feature Enriched kernel which makes your device even better than before.
Compiled with UBERTC 6.x​
Features : (Note : Might vary as per versions)
RGB color control
Working RED and GREEN notification LED.
Smartwake for config-panel
Vibration control using thunderquake engine module by varun.chitre15
Performance and battery optimizations
USB fast Charging enabled by default
TCP Congestion Algorithm (TCPCA) set to Westwood by default
All other TCPCA added
Double tap to wake enabled + Customisable Haptic feedback
So much customisable dt2w, like screen area, time for tap, relative distance between taps... Much more
Wifi Power Management (taken from GSandeep96)
Fixes for blueborne bluetooth vulnerability at kernel level
Entropy tweaks -- Increased entropy values in random.c to max pool
Network tcp window tweak -- Lock window size to full for maximum speed
Pocket Mode to prevent dt2w from waking up screen when proximity sensor is covered
Enabled Forced fast charge -- Customisable
Standalone kernel-level livedisplay support. You can use livedisplay on any ROM, not only LineageOS-based.
CPU governors :
(In alphabetical order)
Darkness
InteractivePlus
Ondemand
Pegasusq
Performance
Poison --- Default custom governor made by me (based on ThunderX)
Powersaver
Renice
ThunderX
Userspace
Wheatley
Features of my Poison governor :
Dynamic CPU frequency transition mode engine. More info in Poison governor thread.
Battery Optimising tweaks.
Best governor for this device because it is made for A7000
Custom tunables :
Can be found here, in my poison governor thread.
https://forum.xda-developers.com/lenovo-a7000/development/explanation-poison-cpu-governor-t3691304
(Most information about the modes and tuneables in Poison governor thread)
Note : Not all tunables in latest versions are documented in Poison thread. Some are documented within the release changelogs. I'll update things when I get time.
Installation :
For custom roms:
Reboot to recovery
Flash the Kernel Zip
Reboot to system and Enjoy
Download links and Changelog :
See second post
Supports all Custom roms (MM and N (based on MM libs) only)
Stock + Vibe Roms also Supported [MM only]
Jiayu-based ROMS (LP libs based) NOT supported.
Still more features might come. Who knows what time may bring.
Note:
* Take a Nandroid backup before installing
Appreciate me by thanking me... Or... You could donate to me if you're an Indian!!!
Donation :
How to donate ??
---> Simple. Send me a PM or mail me ( [email protected] ) and say that you're willing to donate. Further instructions will be sent by me.
I also want to build venom for myself!
Sure! You can find the link for the venom kernel source below in xda DevDB info.
The branch currently in use is "Snapshot" but you can also use "master" build which is a simpler less-featured source.
Both the sources should be compiling with ease. If they don't compile, let me know ASAP.
(Sources are a mess due to bulk releases right now, but the source will be updated with proper commit history once I'm free from school after April-may)
XDA:DevDB Information
Venom kernel aio_row, Kernel for the Lenovo A7000
Contributors
tanish2k09, rohan taneja, GSandeep, daniel_hk, Team M.A.D, aryankedare, HDHR, flar2, varun.chitre15, franciscofranco
Source Code: [url]https://github.com/tanish2k09/Venom_A7k/[/URL]
Kernel Special Features: Custom CPU governor, custom code, dynamic tuneables
Version Information
Status: Stable
Current Stable Version: 3.1
Stable Release Date: 2017-10-18
Created 2017-10-18
Last Updated 2018-06-27

Latest build link :
Old builds :
First OREO build : 01 January 2018 (New Year CARNAGE OREO edition) :
No gestures. Maximum battery :
https://www.androidfilehost.com/?fid=673791459329070547
Only dt2w. Slightly less battery :
https://www.androidfilehost.com/?fid=962157660013069052
Only dt2w + swipe2wake. Same battery as only-dt2w :
https://www.androidfilehost.com/?fid=673791459329070548
Dt2w + s2w + trace2sleep. Same battery as only-dt2w :
https://www.androidfilehost.com/?fid=889964283620775590
01 January 2018 (New Year MM/N CARNAGE edition) :
1) Dt2w + swipe2wake + trace2sleep build :
https://www.androidfilehost.com/?fid=817906626617955916
2) Dt2w + swipe2wake build :
https://www.androidfilehost.com/?fid=889964283620775584
3) Only dt2w build :
https://www.androidfilehost.com/?fid=673791459329070540
4) No gestures build (pure battery) :
https://www.androidfilehost.com/?fid=962157660013069048
Note : First three builds use the same amount of battery. But the last one (pure battery) will give much more BB because the screen input is turned off completely unlike first three
12 November 2017 (108 Upstream edition) :
Smartwake kernel :
http://goo.gl/cfzpYZ
Only dt2w, no smartwake gestures (more battery) :
http://goo.gl/BK3wU9
27 October 2017 (Smartwake edition) :
https://goo.gl/WNPvAq
20 October 2017 (Fixed diwali edition) :
https://goo.gl/dWqkxH
19 October 2017 (Diwali build) :
https://goo.gl/fB9F6V
18 October 2017 :
https://goo.gl/2hhkKz
Changelogs :
Build 26 Feb 2018 (Hyperlapse Superhybrid edition with Wireguard integration) (MM/N/O)
Changelog is too big to add. Check out the release post itself
https://forum.xda-developers.com/showpost.php?p=75700463&postcount=40
First OREO build : 01 Jan 2018 (New Year CARNAGE OREO edition) +
Build 01 Jan 2018 (New Year CARNAGE)
Code:
1) Tweaked poison for more performance. Now you will feel that kernel is much more smooth than ever.
2) Added vibrator engine with real-time linking with poison. You'll feel it when you try yourself and see what this means.
3) Upgraded to dt2w 2.0 with haptic feedback (customisable vibration level) and more efficient structure and checks. My code is 1/3 of original code. Now dt2w is much faster and smoother.
4) Added pocket mode override mechanism. Now you can tap 3 times within 0.8 seconds to override proximity sensor. Number of taps and timeout is customisable with poison.
5) New tunables details :
a) vibrator_on_lock : Disables vibrator on screen off completely. Capacitive buttons won't vibrate on screen off, notifications won't vibrate phone on screen off, but calls will turn screen on and then vibrator will activate. This is a good feature for those who want no notification disturbances but also don't want to enable silent mode.
b) pocket_mode_dt2w_override_taps_number : This is the value of the number of taps that you will have to tap within timeout to wake up the screen even in proximity mode.
c) pocket_mode_dt2w_override_taps_timeout : This is the value of the time in milliseconds within which you will have to tap to override pocket mode.
d) dt2w_tap_distance : Merged dt2w_tap_distance_x and _y into a single variable and changed the distance calculation from rectangular linear to circular radial. This us the radius of the circular region with the center as the first tap coordinates, within which you will have to tap second time within timeout to activate dt2w. Easy.
e) enable_trace2sleep : enables or disables trace2sleep gesture. See how it works in below video.
f) min_swipe_radius : Builds with s2w have this tunable. It controls the minimum required swipe length to wake up screen.
6) Merged x and y distance tunables into a single radius.
7) Enabled 7 cores while booting. (Thax to gsandeep)
8) Added my own trace2sleep gesture.
9) Added swipe2wake gesture. This is very different from sweep2wake because :
a) It can wake up the screen by swiping in any direction. Sweep2wake only wakes on full horizontal swipe.
b) Removed unnecessary sweep2sleep. Sweep2wake can't be used without Sweep2sleep enabled.
c) Removed unnecessary code checks. my code is about 10 times smaller than original sweep2wake so it is much more battery efficient and fast.
d) The swipe distance is customisable from poison.
e) Proximity support.
10) Changed host from "python" to carnage.
11) Added wakelock blockers.
12) If you have enabled the "double press power button to open camera from anywhere" feature (if present in your rom) then swiping on the screen twice really quicky will also open the camera. It's all about the speed.
13) Swipe2wake checks for proximity also. It will not wake up if in pocket.
14) Swipe2wake and Trace2sleep DO NOT consume extra battery. This is because dt2w already keeps the screen active so that's why other gestures take nil battery
Build 12 Nov 2017 (Upstreamed to 108)
Code:
1) Upstreamed to Linux version 3.10.108
2) Three new tuneables for customising dt2w
3) Poison more tuned towards smoothness and speed and also battery backup. You can literally feel that change.
Build 04 Nov 2017 (Smartwake v2.0)
Code:
1) Perfected the gestures for aex4.5,4.6 and viper 3.1.1
Now all the gestures get detected smoothly and with very high precision. In previous venom build and latest devil build, the gestures are sometimes inaccurate. Sometimes up was detected as down and left was detected as right. FIXED!!!
2) Enabled fast charge by default and set limit to 2000.
3) New tunable in poison "gesture_sensitivity". It can go from 1 to 10... 1 means more sensitive and easier detection. 10 means less sensitive and harder to detect.
4) Enabled UID_CPUTIME to prevent logcat buffer bloating.
Build 27 Oct 2017 (Smartwake edition)
Code:
1) Enabled gestures.
2) Highly tweaked gestures. I like to call these "mega-gestures" (lol)
3) Added 4 more tunables in poison governor.
New tuneables :
1) Ac_charge_level : Sets maximum charging limit with charger
2) USB_charge_level : sets max charging limit from usb (laptop and others)
3) Gesture_min_x : Minimum length of screen pixels to swipe before activating gestures in horizontal direction.
4) Gesture_min_y : Minimum length of screen pixels to swipe before activating gestures in vertical direction.
Build 20 Oct 2017 (Fixed diwali build)
Code:
-->Fixed revert_dt2w_area_bounded_by_xy tuneable
Build 19 Oct 2017 (Diwali build)
Code:
--->Added Dt2w trigger area co-ordinates tuneables in poison.
They are "X_left", "X_right", "Y_up", "Y_down". To learn what they do and how to use, go to the poison explanation thread. Link in last of this post.
--->Added negative tuneable of above tuneable. Go to poison thread for more info. Called "revert_dt2w_area_bounded_by_xy"
--->Added tuneable to enable/disable pocket_mode to remove conflicts with vibe roms.
--->Optimised power interrupt delay. Now screen should wake up faster than before.
--->Renamed "dt2w_regions" tuneable to "dt2w_on_buttons"
--->Brought up whole new thread for poison governor. Check end of this post. :D
Build 18 Oct 2017
Code:
1) Added tunable in poison "dt2w_regions" to control dt2w activation from capacitive buttons.
2) Added WiFi power management. To control you can use thunderzap app from play store, or
3) Added WiFi power management tuneable in poison "WificustPowerMode". Works like (2) but without that app.
4) Added ZEN iosched.
5) Removed smartwake gestures used in aex4.5 and aex4.6
All previous builds can be found in this thread :
https://forum.xda-developers.com/lenovo-a7000/development/kernel-venom-kernel-lenovo-a7000-t3656348

Please don't bloat this thread now. It has already been cleaned by mods and I don't want to keep disturbing them. If you have any queries, please go ask it in the other support thread. Link is given below.
Also, for best experience, open this thread from desktop browser
Misc Links :
1 ) How to use trace2sleep and swipe2wake video explanation :
https://goo.gl/JWhw9k
2) Venom kernel support thread :
https://forum.xda-developers.com/lenovo-a7000/development/kernel-venom-kernel-lenovo-a7000-t3656348

Reserved.

Awesome work bro

AEWSOME

VibeUI-X [MM] 20171810 [LATEST]
Link : https://drive.google.com/file/d/0B0T-sUhsKXBGUWlxTGp6QXRxblU/view?usp=drivesdk
By : Me

So guys a new venom build is up!!!
Venom build 19 Oct 2017, Diwali edition!!!
Link and changelog in post #2.
If you have any confusion or queries regarding any tuneables or their functioning, please go to my new thread specifically for poison :
https://forum.xda-developers.com/lenovo-a7000/development/explanation-poison-cpu-governor-t3691304
Please don't bloat this thread about questions regarding poison. Post there. Also, make sure you thank that post

How you're kernel is very good but Kernel.ota.prop missing please fix

Eren2k17 said:
How you're kernel is very good but Kernel.ota.prop missing please fix
Click to expand...
Click to collapse
I don't provide OTA updates.

Fixed venom build of 19th October.
Releasing venom build 20th oct 2017 :
Link :
https://goo.gl/dWqkxH
Changelog :
Fixed revert_dt2w tuneable

Those who were using previous build of venom should flash the above build ASAP.

Sir make jaiyu based.

Presenting VENOM MAXIMUM V2 kernel.
Venom maximum V2 smartwake edition
Changelog from last V1 :
1) Enabled gestures.
2) Highly tweaked gestures. I like to call these "mega-gestures" (lol)
3) Added 4 more tunables in poison governor.
4) Kept fast charge disabled by default to prevent harm. Enable manually.
New tuneables :
1) Ac_charge_level : Sets maximum charging limit with charger
2) USB_charge_level : sets max charging limit from usb (laptop and others)
3) Gesture_min_x : Minimum length of screen pixels to swipe before activating gestures in horizontal direction.
4) Gesture_min_y : Minimum length of screen pixels to swipe before activating gestures in vertical direction.
Link :
https://goo.gl/WNPvAq

The gestures like O for flash, up for dialer, down for music are now much more optimised and faster and also smarter as I've tweaked the code to detect the gestures.
I've actually added more code of my own to make it sharper and precise.
You can easily feel the difference between the accuracy of my kernel gestures and the rough approximate gestures of devil kernel.
I recommend you to switch to my enhanced smartwake gestures build.
How to use gestures properly :
Press finger on screen and hold like that for 0.5 seconds. Then make the gesture you want (preferably in a clockwise direction, though it is only because that's how to program calculates the gesture. If you know c++ then you can also see the marvelous, genius code of smartwake file. I appreciate the original Dev for thinking it up. The algorithm is amazing, and requires brain.)
Simple.
I've also cleaned up some code from smartwake and will clean further in later build.
I'm planning to make the next build free of bloat code and to enabled fast charge with safe values by default.

Venom kernel maximum build 4th Nov Smartwake v2.0 :
Changelog :
1) Perfected the gestures for aex4.5,4.6 and viper 3.1.1
Now all the gestures get detected smoothly and with very high precision. In previous venom build and latest devil build, the gestures are sometimes inaccurate. Sometimes up was detected as down and left was detected as right. FIXED!!!
2) Enabled fast charge by default and set limit to 2000.
3) New tunable in poison "gesture_sensitivity". It can go from 1 to 10... 1 means more sensitive and easier detection. 10 means less sensitive and harder to detect.
4) Enabled UID_CPUTIME to prevent logcat buffer bloating.
Thx to Aryan Kedare and gsandeep96
Link :
https://goo.gl/j3sPNE
PS : I have been unable to update the poison thread since last build and so far 5 tuneables of Poison governor have not been explained in that thread. I'll update it ever I get time in future. Please don't expect major updates from any dev for some time now, because a transition is happening. On behalf of all devs, I ask you to not disturb anyone for at least a month, except for reporting bugs (with logs) and providing fixes (if found).

Soft keys vibrates and pressing the back button wakes up the screen even after disabling each and every options under 'wake' section in kernel auditor.It is really annoying

@tanish2k09 The Best Kernel For My Phone Lenovo A7000-a , I'm Using Your Own CPU Governor "Poison" It's Having The Best Battery Backup & Best DAMNED Performance But I Having A Problem When I Charge My Phone With Computer The Indicator When Is In 40% It's Down To 39% , How To Fix It ???!!!?
I'm Using Resurrection Remix ROM Official Release By @Rohan Taneja Latest Build 2- 10-2017 .

ahmedsaadimam said:
@tanish2k09 The Best Kernel For My Phone Lenovo A7000-a , I'm Using Your Own CPU Governor "Poison" It's Having The Best Battery Backup & Best DAMNED Performance But I Having A Problem When I Charge My Phone With Computer The Indicator When Is In 40% It's Down To 39% , How To Fix It ???!!!?
I'm Using Resurrection Remix ROM Official Release By @Rohan Taneja Latest Build 2- 10-2017 .
Click to expand...
Click to collapse
Turning off the screen while usb charging will increase the charge speed very much. Charging is very slow when screen is on

ahmedsaadimam said:
@tanish2k09 The Best Kernel For My Phone Lenovo A7000-a , I'm Using Your Own CPU Governor "Poison" It's Having The Best Battery Backup & Best DAMNED Performance But I Having A Problem When I Charge My Phone With Computer The Indicator When Is In 40% It's Down To 39% , How To Fix It ???!!!?
I'm Using Resurrection Remix ROM Official Release By @Rohan Taneja Latest Build 2- 10-2017 .
Click to expand...
Click to collapse
Turning off the screen while usb charging will increase the charge speed very much. Charging is very slow when screen is on.
Otherwise change the usb_charge_level tunable value to something higher. I WON'T TAKE RESPONSIBILITY FOR ANYTHING BAD THAT MIGHT HAPPEN TO YOUR DEVICE IN DOING SO.
There. I've warned and told you. Now it's your choice.:highfive:
Edit : New update will be released on Sunday.