Related
[KERNEL][23/07] █░ SGSII | 2.6.35.7-MirageS2 [v5]- STOP BATT DRAIN | OC 1600mhz ░█
Firstly, I'm not responsable if you brick your phone doing overclock or a bad use of this kernel. So, be careful.
This kernel is built from a custom modified source by me (I've added and modified some things to an updated SGS2 source), I've tried to modify it to get the lowest battery drain, so this kernel should stay in a step between performance and battery, if you like some more performance you can download SetCPU, or other custom app to modify freqs and default governor.
What's included:
-For XXKG1/G2/G3 (should work with olders too)
-Modified Freq range 11 steps (200-400-500-600-800-900-1000-1200-1400-1504-1600 Mhz)
-CPU UV sysinterface (thanks to ninphetamine)
-Modified cpufreq.c to force processor to go step-by-step in freqs.
-Default Freq: 500-1200 Mhz ondemand (the best to get low batt drain, should drain lower in sleep)
-Lowest maximum freq blocked to 400mhz (so if you put 200-200, it will run 200-400, locked due to better performance)
-Available governors: interactive-smartass-conservative-userspace-powersave-ondemand-performance (custom modded smartass, ondemand and interactive governors)
-CFS Scheduler.
-SLQB Allocator.
-CFQ Block IO Scheduler (Available: no-op, deadline, cfq)
-Modified Initramfs from saturn_de (thanks to him and Chainfire) - I've added some values to this init.rc to get lower battery drain and some performance. (some different from saturn)
-CWM 4.0.0.2 Recovery
-Disabled Profiling support and debugs, added ThumbEE, Improved Control Group Support.
-Added some CFQ IO tweaks
-Changed dalvikvm heapsize to 60m (this should improve performance on tasking)
-Touchscreen fix added (thanks to vicenzo91)
*[email protected]
*[email protected]
*int:fast is not included due to performance problems.
*not compatible with tegrak OC (tested with SetCPU)
test with performance 1504mhz, vfs_cache_pressure=100 and dalvik 64m (default vfs=70, you can modify it downloading Sysctl Config from Market)
v5:
*set samsung-update1 as base (fix reboots)
*added slqb patch
*removed bfq
Download:
SERVERS:
[USA]SGSII-2.6.35.7-MirageS2-v5
[DEUTSCHLAND]SGSII-2.6.35.7-MirageS2-v5
[Mirror]http://sgsii.z4mb0.net/Kernels/SGSII-2.6.35.7-MirageS2-v5.tar Mirror by El TeKi thanks
reserved.....
Wow nice to see you here. Will try it out immediately
Sent from my GT-I9100 using XDA Premium App
looks really really really promising... trying it now
how come i only get scores around 3200 with every rom and kernel? and everyone else has so high
going to try this one soon
yeaaa baby !!
Good to see you here Neo. Been a Aurax/Reflex fan on the Desire...
This is good news!
Regards
Awesome, will try this when i get home
Sent from my GT-I9100 using XDA Premium App
Just flashed. Oc to 1.5ghz. First quadrant 4566
will give feedback on batt consumption soon
Hope to see soon a rom made by you..... On my old desire i had your auraxtsense!!! U are great
Very nice neo. I'm a fan of your desire rom.. now u make a kernel for sgs2. No doubt, i will try it in the future. I hope u release your own version rom for sgs2.
+1
Sent from my GT-I9100 using XDA App
+2
Sent from my GT-I9100 using XDA App
trunks986 said:
Hope to see soon a rom made by you..... On my old desire i had your auraxtsense!!! U are great
Click to expand...
Click to collapse
Soon mate, soon. Thanks
Holy shiznit,who would've thought we'd be seeing you here Neo?I gotta thank you for the first rom that made me actually love my Desire.Not the only one,but it was the first whatsoever.
I'd like to tell you a thing or two(or three ) though.
1)You should add support for SetCPU's voltage control.I know there are other apps that do the same thing,but the number of people using SetCPU is massive.And on the Galaxy S 2,undervolting is very important,especially to avoid issues with overheating.
2)Could you pleaaaase lower the max clock by only 4MHz?My phone is unstable at 1504MHz with 1350mV,while it's rock stable at 1500Mhz with 1325mV.And I'm serious,4MHz only and it makes a huge difference,while performance-wise it's the same.
3)You could also overclock the GPU.200MHz with 750mV min and 400MHz with 1100mV max seems stable for everyone.You can gain quite a lot of performance,while it doesn't heat or consume more.You can also test if what I say is true yourself.
Else that those three...Well,welcome to our world pal!The world of power!
I don't know what you did to get 5000 in productivity on smartbench11 cos I can't hit more than 4300 even with the vfs setting changed...and yes I am overclocked to 1.5ghz and locked there.
Hi can make a kernel with default clock with 1,5ghz please ?
Yanardag said:
Hi can make a kernel with default clock with 1,5ghz please ?
Click to expand...
Click to collapse
Just download SetCPU and set the min and max to full.
Mirror http://www.megaupload.com/?d=4LLP5HPF
Another mirror http://www.multiupload.com/L215724GBY
Just flashed your kernel. Thanks
Is auto brightness broken ? The brightness goes to 100% on autobrightness eventhough it is night and there is no light
Tried wiping dalvik cache but did not help
EDIT: Covering the light sensors with a black blanket did not change anything. So there seems to be a problem with auto brightness. I am on stock KG1 leaked rom
Hey guys,
This is the Lollipop version of the Matr1x kernel and it works on 5.0/5.0.1.
Features:
Code:
- Based on Linux kernel version 3.4.0
- Built with GCC 4.8 from Google
- Voltage Control Interface (by faux123)
- Gamma Control Interface (by faux123) with PA tweaked colors and bundi22 iPhone 5 color preset
- FauxSound (by faux123)
- Speaker amp control (by faux123)
- Simple GPU governor (by faux123)
- Dynamic fsync Control (by faux123)
- Accuracy Filter Control (by stratosk)
- GPU OC to 487.5 Mhz
- UV by 75mV for all frequencies and cores
- SIO, ROW, and FIOPS I/O Schedulers
- Wheatley governor (by Ezekeel)
- Thermald and mpdecision removed
- 192 Mhz frequency for better battery when idle
- Fast Charge (thanks to franciscofranco)
- BLX (Originally by Ezekeel and ported to Nexus 4 by me)
- Double tap to wake and touch wake support (by stratosk)
- ARM hotplug driver (by _thalamus) with min_online_cpus value (by me) and max_online_cpus value (thanks to _motley)
- MultiROM support (by Tasssadar)
- USB OTG "usb-host" mode support (by ziddey)
- MSM Sleeper Mod (Max screen off frequency) (by flar2)
- Various performance tweaks
Changelog:
v1.0 Initial release: stock 3.4.0 kernel with added deadline I/O scheduler tweak.
v1.5 Added overclocking capabilities to 1.728 Ghz.
v2.0 Removed OC capabilities, added GPU OC to 450 Mhz, 100mV UV across the board, ARM CPU Topology (which improves the efficiency of multi core devices), and various performance tweaks.
v2.5 Added SIO I/O Scheduler, touch screen improvement tweaks (see http://forum.xda-developers.com/showthread.php?t=2027476 and extra tweak by faux123), UV'ed all cores and frequencies by an extra 50mV for a -150mV overall, and switched to the AnyKernel template. (thanks _motley!)
v3.0 Reverted the extra 50mV of UV that caused instability and added faux123's voltage control interface for manual voltage adjustments.
v3.5 Added the reduced msm_hsic_host wakelock tweak, ROW I/O Scheduler, removed thermald to allow kernel to manage the heat using its own drivers, some ondemand governor tweaks, tweaked ARM CPU topology, and lowered the minimum voltage for voltage control interface (test your phone's limits).
v4.0 Reduced the minimum voltage for voltage control interface even more (test your phone's limits), added the CPU Voltage table for "faster" binned chips (still -100mV UV), added Fast Charge, added a 288 Mhz CPU step for better battery when idle, and added the BLX mod (see here: http://forum.xda-developers.com/showthread.php?t=1257497).
v4.5 Added the proper reduced msm_hsic_host wakelock tweak, fixed the "faster" CPU table (users who have "faster" chips should have no trouble now), added showp1984's Sweep2Wake, and partially reverted a display tweak from Google (this should provide a bit better display color than stock).
v5.0 Added Sweep2Wake gestures by faux123 with the touch events patch (no more frozen touch screens), switched to the GCC 4.7 compiler from Google, removed mpdecision and added _thalamus hotplug driver, and added the min_online_cpus module capability for the hotplug driver.
v5.5 Removed the 450 Mhz GPU OC and bumped it up to 487.5 Mhz, added thermal tweaks (to manage phone temperature) by franciscofranco, updated the interactive governor and ROW I/O scheduler to the latest version, and tweaked the auto hotplug driver for better battery life.
v6.0 Fixed the msm_hsic_host wakelock once and for all (You may still see it but it shouldn't be running that much), added PGM support (thanks to bponury), and added faux123's gamma control interface.
v6.5 Tweaked auto_hotplug to try to further improve battery life, removed Sweep2Wake (attempt to solve any touchscreen freezing issues), updated ROW I/O Scheduler, removed some CPU frequency steps (only kept the useful steps), added the FIOPS I/O Scheduler, and added the PA tweaked display colors.
v7.0 Merged the Android 4.2.2 kernel code, added the final PA colors from molesarecoming, added _motley's generic color control interface to allow easier scripting, and _motley's tweak to allow color changes to be "refreshed" automatically.
v7.5 Fixed the PGM touch control issue, added faux123's speaker amp control mod, added franciscofranco's accuracy filter control mod, updated the ROW I/O scheduler to the latest version, and added several ondemand governor update patches.
v8.0 Added fix for sporadic WiFi drops, added faux123's FauxSound mod, removed sweep2wake completely (attempt to fix power button issue), and added data drop fix (by faux123).
v8.5 Added the max_online_cpus mod by _motley (You can make your device single core, dual core, etc.), added a 192 Mhz CPU step (This should help with battery), and added the Wheatley governor by Ezekeel (#23 on http://www.alliance-rom.com/community/wiki/governors-explained/).
v9.0 Added USB OTG by ziddey, updated the FauxSound to v2.1, added the idle drain patches, updated the ROW I/O Scheduler to the latest version, added Touch Wake by stratosk, and got rid of the touch_boost errors in the logcat.
v9.5 Removed Touch Wake by stratosk and brought back Touch Control by bponury, removed USB OTG, and added MIUI support.
v10.0 Fixed the screen on lag, added some performance patches, added faux123's Simple GPU governor, and fixed the bluetooth issues some users were having.
v10.5 Added support for Android 4.3 (JSS15J).
v11.0 Switched to the Anykernel zip template, updated Fauxsound to the latest driver, added faux123's dynamic sync control mod, and added support for bponury's touch control.
v11.5 Added support for Android 4.4.
v12.0 Merged mako 4.4.1 kernel source, added s2w fixes from showp1984, and added the FIOPS I/O scheduler.
v12.5 Added Tasssadar's kexec patch (for multirom), added ziddey's USB OTG (http://m.androidcentral.com/android-advanced-usb-otg-nexus-4), put in bundi22's iPhone 5 color preset by default, and updated Fauxsound to the latest driver.
v13.0 Fixed the bundi22 iPhone 5 colors to match the real preset, added flar2's MSM sleeper mod (max screen off frequency), updated the Interactive governor to the latest version, and updated the ROW I/O scheduler to the latest version.
v13.5 Reverted the Interactive governor updates due to issues (back to v12.5 Interactive governor), added mrg666's Linux 3.6.11 workqueue backport patches in order to improve hotplug efficiency, and added CyanogenMod based ROM support (CAF).
v14.0 Added support for Android 4.4.3, raised voltages across the board by 25mV (this will help those with slower CPU bins), and added stratosk's double tap to wake and touch wake mods.
v14.5 Added support for Android Lollipop and updated the FauxSound driver.
Link to Lollipop version:
http://matr1xkernels.com/
Link to source: https://github.com/mathkid95/linux_lg_lollipop
What's up guys... this is the first release of the Matr1x kernel for N4. I am starting off real simple (I set deadline as the default I/O scheduler and tweaked some values)
There is much more to come!
Also, I will start posting the kernels at www.matr1xkernels.com soon... for now please use the mediafire link. You can flash this in recovery.
Spammer.
Where's the punchline good jerb math kid
brainmaster said:
Spammer.
Click to expand...
Click to collapse
Just so everyone else doesn't have to view op's profile, this is not a spammer and he's pretty well established on xda. Wasted a few seconds of my life trying to verify that...
Wow great to see you here man!
Sent from my Nexus 4 using Tapatalk 2
mathkid95 said:
Hey guys,
This is the JB version of the Matr1x kernel and it works on 4.2.
Features:
Code:
- Based on Linux kernel version 3.4.0
Changelog:
v1.0 Initial release
Links to JB version:
http://goo.gl/zVlm4
Link to source: https://github.com/mathkid95/linux_lg_jb.git
Click to expand...
Click to collapse
Wow look whoz here.. I'm waiting for my N4 and to have your work on it..
Loved the Matrix kernel on my nexus s.. Now it's the turn for N4
Always appreciate your work Math kid
Hung0702 said:
Just so everyone else doesn't have to view op's profile, this is not a slammer and he's pretty well established on xda. Wasted a few seconds of my life trying to verify that...
Click to expand...
Click to collapse
I confirm he's done a wonderful job since Nexus S, and i'm pleased to see him there now
Btw, flashed this and it is very nice so far : snappy and smooth. We'll see about battery life...
Ok kid. I'm awake. I'm awake, I'll flash it now. Hit me up later today so we can discuss the future of this kernel lol. Happy Thanksgiving everyone
Sent from my Nexus 4 using xda premium
Happy Thanksgiving everyone !!!
Got it flashed. Very smooth. According to system tuner only 2 cores are being used though.
I'm running a super top secret test rom and I was getting flickering unlocking the screen. It's gone after flashing this.
Sent from my Nexus 4 using xda premium
Great to see you here MK! Looking forward to entering the Matr1x with my N4.
Sent from my Nexus 4 using xda premium
Just flashed. Smooth so far. Will report back if any issues. Thanks!
Hey Mikey mind sharing super top secret test ROM
Happy Thanksgiving To All!!!!
Sent from my Nexus 4 using xda app-developers app
mikeyinid said:
Got it flashed. Very smooth. According to system tuner only 2 cores are being used though.
Click to expand...
Click to collapse
Wooooooooahhhh! What? Two cores only?
The ONDEMAND governor either shuts down two of them, or it has Hotplug enabled, or there's just some kind of a mistake. I don't know, might be a bit of a noobish comment.
Can anyone solve this for us?
DonJuan89 said:
Wooooooooahhhh! What? Two cores only?
The ONDEMAND governor either shuts down two of them, or it has Hotplug enabled, or there's just some kind of a mistake. I don't know, might be a bit of a noobish comment.
Can anyone solve this for us?
Click to expand...
Click to collapse
I wouldn't worry about it. I'm sure it's running as intended.
Sent from my Nexus 4 using xda premium
---------- Post added at 05:49 AM ---------- Previous post was at 05:48 AM ----------
buddahlou said:
Hey Mikey mind sharing super top secret test ROM
Happy Thanksgiving To All!!!!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Haha. Sorry I can't. It'll be available to all very soon. It's worth the wait, trust me.
Sent from my Nexus 4 using xda premium
Yea seems like it been checking the tweets
Sent from my Nexus 4 using xda app-developers app
You can check if all 4 cpu's are used properly by starting Geekbench and than have a look. While geekbench is running, all 4 cpu's should be used.
Here we go! Love me some Matr1x. Accidentally fell asleep last night...sorry kid. Happy Thanksgiving!
Sent from my Nexus 4 using XDA Premium HD app
Hey mathkid, nice to see you here. Will have a look at this and report back
Gesendet von meinem Nexus 10 mit Tapatalk 2
NOTICE: This is COMPATIBLE with ALL Google Rooted Stock and Custom ROMs based on JellyBean 4.2!
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you ![/b][/center]
Hi XDA members and fellow Nexus users:
This is my twenty-third kernel hack. I want to thank T0dbld, Turl and rest of my teammates, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
THIS KERNEL is BASED ON Google Source Code. So it is COMPATIBLE WITH ALL AOSP JB 4.2 Builds.
DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibility (Forced Close).
Kernel Features:
So what type of kernel is this? Well, this kernel is based on Linux 3.4.y (says so from the version string)
Features in Magenta are identical as the latest Linux 3.4+
Memory Management subsystem:
Init:
Core Kernel:
*** RCU:
*** Scheduler:
Power Management:
File System:
Block I/O:
Kernel Features:
Device Drivers:
Library Support:
Installation Instructions:
Change Log => Change Log
Beta 4.4 Kernel => Beta kernel
Mainline 4.4 Kernel => mako kernel <== (Stock CPU frequencies, Stock GPU frequencies 400MHz)
Ultimate 4.4 Kernel => mako kernel <== (CPU frequencies up to 1.8 GHz, GPU frequencies up to 450 MHz)
Deprecated JELLYBEAN kernels:
Stock Plus Change Log => Change Log
JWR Stock Plus Kernel => http://faux.romhost.me/mako/sp/mako-SP-JB43-JWR_r2.zip
JSS Stock Plus Kernel => http://faux.romhost.me/mako/sp/mako-SP-JB43-JSS_r2.zip
Mirrors http://androidhosting.org/Devs/Faux/
Here's a step by step instruction to install this kernel:
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
[ Advanced Users: ]
[ Optional: ]
If you encountered any funny / weird / strange issues coming from other than 100% pure stock ROMs or my kernels, the following "Reset Kernel" will restore the kernel to its Original Stock Settings.
After applying the reset kernel, then load my latest kernel again.
*** JellyBean -- RESET KERNEL (FOR STOCK BASED ROM ONLY. FORC CM SIMPLY REFLASH THE LATEST NIGHTLY, then FLASH my KERNEL AFTERWARDS) ***
JellyBean 4.2.x Reset kernel for STOCK ROMs ONLY (Cyanogenmod, simply reflash nightly again to reset)
*** 4.2.2 ***
http://faux.romhost.me/mako/mako_422_reset_kernel.zip
*** 4.2.1 ***
http://faux.romhost.me/mako/mako_421_reset_kernel.zip
Tmobile LTE Hybrid Modem hack:
http://forum.xda-developers.com/showpost.php?p=43926154&postcount=12988
[ For Kernel Devlopers ONLY: ]
NEWS BULLETIN:
Version 029 is OUT!
(lurking, no more open betas )!
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 0.x.x -- more to come...
History:
See Post below...
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 1.512 GHz for performance, 1.242 GHz for battery
Min clock - MHz 384 MHz for both
CPU Governor - Intellidemand for performance AND battery
mpdecision - Off
Snake Charmer - OFF for performance, On for Battery
Eco Mode - Off for performance, On for battery
Set On Boot - On
SOC Control
Set On Boot - On
C0 - On
C1 - On
C3 - On (Note: N4 AP modem is very sensitive to some of the deeper sleep states, if you experienced Green/Yellow AP Modem Watchdog Bark screens, I recommend disabling C2/C3 states).
Voltage Control
Set On Boot -
Global CPU Voltage - mV
intellidemand gov control
Up Threshold - 95 for both
Up Threshold Any CPU Load - 85 for both
Up Threshold Multi Core - 75 for both
Boost Frequency - 1026000 for both
Two Phase Freq - 1134000 for both
Optimal Freq - 1242000 for both
Synchro Freq - 756000 for both
Set On Boot - On
GPU Control
GPU Governor - Simple for both
GPU Clock - 400 MHz for performance and 320 MHz for battery
GPU Vsync Toggle - On for both
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - FIOPS for both
Readhead Size (eMMC) - 2048 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Vibration Control
Set On Boot - On for both
Vibration Control - 70 for both
Screen Color
Set On Boot - On for both
Factory Presets - LG Presets
Color Adjustments - R, G, B 255, 250, 245
Gamma Amp Adjust 0 - R, G, B 13, 20, 22
Gamma Amp Adjust 1 - R, G, B 0, 2, 3
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
Above is what I use personally. MAY NOT be optimal for all :fingers-crossed:
Updated on September 6, 2013
DUE TO MY EXTREMELY BUSY SCHEDULE BOTH @ WORK AND @ HOME, I WILL ONLY MAKE MAJOR ANNOUNCEMENTS ONCE PER WEEK
Open Beta may not be stable and may cause issues with your phone!
By loading open beta you have agreed to:
1. To report all random reboots with associated /proc/last_kmsg
2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps
3. Participate in Forum discussions for the beta software with others without FLAMING each other or post useless information such as:
a) Phone doesn't boot (without providing any additional information, ROM versions etc)
B) phone is too hot (without providing any additional information, ie OC freq, UV etc)
The Open Beta system is designed to have the community help each other and the developers. This way, all potential bugs are flushed out so the final released version will be stable and error free. The more actively you participate in Beta Testing the better the final product will be (you are really helping yourself to create a better community software).
If you do NOT agree with the statements above, DO NOT load my Open Beta software.
Kernel 00x Open Beta 0x is now CLOSED!
FAQ:
1. Why don't my settings "stick" when using FauxClock App?
#1 issue with settings NOT sticking is superuser Switch to SuperSU should solve 95% of issues
https://play.google.com/store/apps/...51bGwsMSwxLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
UPDATE: Koush's new Superuser is also compatible with my apps!
2. Why doesn't my Max frequency settings NOT "stick" when using intellidemand governor with FauxClock App?
Intellidemand will AUTOMATICALLY UNDERCLOCK when there's a CONSTANT load for greater than 3 minutes. (Load spikes will NOT trigger the auto underclock, only CONSTANT loads). After the load is gone, it will restore back to original Max Clock. Constant load will drain the battery quite quickly, intellidemand governor will detect this behavior and automatically underclock to save more battery without ANY user intervention at all!
3. Why does the CPU freq slider move when I touch the screen?
Qualcomm's closed source mpdecision is the culprit. mpdecision raise the minimum CPU frequency to 1.026 GHz to "cheat" or increase UI smoothness. While this is a good idea, it is too aggressive and overkill causing unnecessary battery drains. And because it is closed sourced, it is NOT POSSIBLE to tweak its behaviors. I highly recommend turning off mpdecision when using my kernels in combination with intellidemand/intelli_plug
4. What is Intelli_plug? How do I use it?
Intelli_plug is my open source solution to Qualcomm's closed source mpdecision. Intelli_plug is enabled automatically upon boot, so NO need to turn on or off. However, it conflicts with mpdecsion, so I HIGHLY recommend turning off mpdecision when using my kernels! To turn off mpdecision, either use fauxclock app under CPU page or use terminal / init.d script and write "stop mpdecsion"
5. What is Eco Mode in FauxClock App?
Eco Mode is a special power savings mode part of the intelli_plug where the kernel automatically reconfigures its decisions in real time and optimizes to use only 2 out of 4 cores. Cores 3 and 4 are turned off completely.
6. My Gamma/Color settings do NOT stick when I removed FauxClock App from memory!
FauxClock app MUST be running to retain the colors. This is a limitation of the stock kernel and FauxClock app was designed to overcome this issue, so therefore it has to be running and be in memory (Avoid all Task Killers!!!)
7. If FauxClock has to be running all the time, does it CAUSE MORE DRAIN?
NO, FauxClock is a normal behaving app which does NOT HOLD or request ANY wakelocks from Android system. Therefore it does NOT cause any drain at all while running (matter of fact, it's suspended most of the time until it's needed)
8. What is "SnakeCharmer" ?
SnakeCharmer is an extension that I created to tame the Qualcomm Krait CPUs. Due to asynchronous SMP cpu design, each CPU can have its own independent min/max frequencies. SnakeCharmer allows you to set a specific max cpu frequency to all cores at the same time, so if you want to UNDERCLOCK your CPUs to a specific frequency, you should enable it under FauxClock.
9. I enabled "SnakeCharmer" but I occasionally see it still goes to max 1.512 GHz, why?
SnakeCharmer works flawlessly. FauxClock app is a Java app which runs on top of Linux. Sometimes it gets out of sync with the kernel, so it will display a frequency that's higher than the maximum "SnakeCharmer" frequency. This is a PURE DISPLAY issue with FauxClock App. SnakeCharmer works advertised! (Confirmed using CPUSpy by multiple users).
10. I have BOTH FauxClock and FauxDisplay apps but I seemed to lost the Screen Adjustment Tab under FauxClock? (Nexus 4 Only)
FauxDisplay (aka Advanced Gamma Control has full 27 controls unlocked, it supersedes the basic controls provided by FauxClock
11. What is Turbo Boost and how do I enable it? (Nexus 4 ONLY)
Turbo Boost is similar to Intel's Turbo Boost for the x86 CPUs. It increase the clock frequencies when 2 or less cores are active. (TB-U allows up to 1.9.44 GHz, TB-M allows up to 1.836 GHz). To enable turbo boost, simply slide the CPU max frequency slider all the way to the right!
12. Why can't I Undervolt below 600mv?
Ever since I created the UV interface for Qualcomm phones on 2010, 600mv minimum voltage has been chosen for a reason. There are typically 2~4 different "binnnings" for the same CPU chip (each binning has their own voltage tables) and therefore NOT ALL CHIPS are created equal. The 600mv limit was put through many different tests and was found to be stable ACROSS many many different chips/binnings combinations (No crash or sleep-of-death aka SOD) and it has been proven time and time again to be a good value for minimum voltage value.
SOC Sleep States demystified! (Corrected for incorrect information thanks for G+ comments!)
Often times users using many apps like CPU Spy will say post how much time their phone spent in "deep sleep" and thinking that "deep sleep" is only 1 state, unfortunately, it is WRONG. For many modern CPUs there are several C-States (sleep states), and the term "deep sleep" does NOT correctly describe them all.
Just like in real life, there are several stages of "sleep", the shallowest sleep is C0 State. As in real life, C0 state is very easy to wake up from with almost NO latency at all (real life will be like grogginess, so C0 is just like when you first doze off but any little distraction will instantly wake you up). The deeper the sleep, the harder it is to wake up from. It takes longer for CPU to re-initialize itself to a waking state (just like real life where once you enter REM sleep, it's very hard to wake up from it).
For most processors, C3 is the Deepest sleep state. C3 state is ALMOST like turning it off using the absolutely minimum power.
C0 - Shallowest sleep (dozing off) with instant wake up
C1 - slightly deeper sleep with slight latency when waking up
C2 - deeper sleep with longer latency when waking up
C3 - really deep sleep (like REM sleep in real life) with longest latency when waking up
My pyramid (Sensation 4G) kernel has Intellidemand Governor 2.0 (Grand daddy of the Mako's Intellidemand governor) where I disabled ALL hotplugging when screen is on (ie, both cores stays ON the WHOLE TIME) but I enabled C2 state for both processors, so even though at first you think it may draw more battery than hotplugging (turning off the core when not using), many of my users have experienced better battery life than with hotplugging (Hotplugging is VERY expensive, the act of turning cores on/off drains battery as well).
On Nexus 4 (Mako), for some reason, Qualcomm has decided to only allow for C0 state (the shallowest sleep) and so the "deep sleep" isn't really that deep. With my FauxClock app + my kernel, I give you all the "deeper" sleep states so when idling, you phone can experience deeper sleep. There's a hardware bug for Krait processors where the secondary cores, 1~3, cannot achieve deeper sleep state independently, so hotplugging is still necessary to save power for cores 1~3 but for core 0 (and core 0 is the master CPU and it's NEVER hotplugged) being able to go into deeper sleep state will help to conserve more power.
FauxClock is designed with forward compatibility. With the newer Qualcomm Krait 600/800 series, they have fixed a few of the hardware bugs from the Krait processors, and so for those newer SOCs, you can go into deeper sleep with all cores like the like older 8x60 SOCs.
Yea! Glad to see you came with me from the Amaze forums! Can't wait to flash soon!
I remember you from the hercules forums. Nice to see you here! Looking forward to using your kernels.
Well well well... Look who's here. Nice to see you working on This beast man. I'm excited to see what you have in store for us.
Oh and where are my manners... Happy Thanksgiving man.
Sent from the Nexus 4 Drinking Club...
"It's not drinking alone if you are with people on an internet forum"
Oh **** faux is here, now it's a party
Sent from my Nexus 4 using xda app-developers app
STFU! Faux!? Oh, it's ON now baby!!!
Sent from my Nexus 4 using xda premium
Holy crap! I'm gonna cry! First kernel I ever flashed was a Faux123. My phone needs to get here....
Source?
doesnt boot
edit:
well, boots, but not into your kernel.
using fastboot flash causes no boot.
edit the edit:
wtf. works now. right on man.
randomblame said:
Source?
Click to expand...
Click to collapse
You can find it on his profile, as per usual
https://github.com/faux123/mako
EDIT: actually, it doesn't seem to be updated. But anyway, I'm sure faux will update it when he finishes recovering from post-turkey stress
r2DoesInc said:
doesnt boot
edit:
well, boots, but not into your kernel.
using fastboot flash causes no boot.
Click to expand...
Click to collapse
exaclty what i was going to say...tried boot, but no go, simply boots without changing kernel ; and flash doesn't work.
Also, doesnt run @ 1.8. Itll reboot and then hang till you reflash the kernel.
Pesonally I'd suggest staying away from this until it was a bit more tested.
Oh man.
Now the situation has gotten real. Nice one faux.
r2DoesInc said:
Also, doesnt run @ 1.8. Itll reboot and then hang till you reflash the kernel.
Pesonally I'd suggest staying away from this until it was a bit more tested.
Click to expand...
Click to collapse
you do realize that not every CPU is going to be able to oc that high? Some won't oc at all. Some will go higher. Just saying......
Damn faux anyway way we can get a flash able after u get some time? Not near a comp right and want to try this bad boy! Thanks
wont boot...
got a lockup at 1.7 and reboot loop after till i flashed the kernel again
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
tweaked said:
you do realize that not every CPU is going to be able to oc that high? Some won't oc at all. Some will go higher. Just saying......
Click to expand...
Click to collapse
...yes
derp
Page 1: Information
Page 2: Changelog and Downloads
Page 3: Additional info and FAQ
Instructions:
Make sure you are on the latest bootloader version before flashing this or any other custom kernel. Search for a flashable zip or use fastboot and the google factory images.
Download Kernel to internal SD card. Flash in recovery. Reboot. Congratulate yourself for wisely installing the best nexus 7 kernel.
A complete list of changes is available at my Github.
Source: https://github.com/Metallice/android_kernel_grouper
Recommended Settings:
The only app supported for changing any kernel parameters and settings is TricksterMod - https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
CPU governor - TouchDemand with default parameters (default)
I/O Scheduler -
- ROW for pure read speed. Fast reads which are often the most important on mobile. Similar concerns like deadline.
- BFQ for more consistent performance. Slower than Deadline and ROW, but prevents stutters while downloading in background
Max Frequency - 1.2Ghz (Stock max for 2+ cores) (for lollipop it might be a good idea to use 1.3Ghz)
- Note: Tegra sets the max frequency to 1.5Ghz at boot, make sure to change it manually or have an app set it at boot to avoid battery loss. If you have a program such as
TricksterMod set it at boot make sure to include at least a 60 second "delay" in applying boot settings.
- Note 2: DO NOT USE THE APP "SYSTEM TUNER" TO SET FREQUENCIES. CONFLICTS WITH AUDIO PERFLOCK IN KERNEL. Do NOT use system tuner to set frequencies as it conflicts with audio performance lock in this kernel. Will prevent you from lowering your maximum frequency. Use Trickstermod.
GPU Max Freq - 446Mhz (maintains good battery life while smoothing out some games. Anything greater than 446Mhz is so heavily bottlenecked by RAM that it's essentially worthless. 600Mhz might give you 1 or 2 extra FPS for significantly worse heat, battery life, and stability)
- Possible frequencies - To be completed later
Fsync - On
Dynamic Fsync - On (be aware of data loss concerns, even if they actually are minimal.)
SmartDimmer/PRISM - On (off for a63 and lower)
zRAM - off/none (default) (For lollipop it may help with multitasking at the price of speed, although you really shouldn't be trying to heavily multitasking with a 2012 N7 anyway) (Not very useful on android 4.x with >=1GB RAM, for lollipop it's not really helpful >=3Gb)
Data remounting scripts - already included in ramdisk. Additional scripts not needed.
I DO NOT RECOMMEND, nor will I support, any kind of optimization/superdupercharge/placebo script. All settings are already optimized in kernel and ramdisk. Using these scripts or tweaks will only lead to problems and performance degradation.
__________________________________________
If you'd like to buy me some caffeine so I can continue to fit studying and kernel-ing in my busy schedule, feel free to donate below. Thanks so much for all of your support! Clicking the thanks button is always appreciated too
Alpha Changelog (stable feature list above):
a77 - remove CM12.1 specific stuff from ramdisk
a76 - Fix for 5.1
a75 - 5.1 Lollipop update and patches
Click to show complete changelog
a74 -
Fix for TricksterMod. Sync with cm12 ramdisk. Fake update dmcrypt to allow TRIM on encrypted devices (untested). Set ROW as default scheduler.a73 -
Lollipop! Updated toolchain. Removed touch2wake due to the wakeup issues it created for some. Other stuff.a69 -
Quick fix to allow overclocking on stock roms.
a68 -
Update to latest 4.4.3 kernel source
Sync with latest CM 4.4.3 ramdisk
Update to 4.8 toolchain
F2FS support
Zip installation supports all permutations of ext4/f2fs layouts
Based on work by frantisek.nesveda, but modified to support all layouts and be more flexible
Make sure to go to his thread -HERE- and click the thanks button!
Upgrade to BFQ v7r4
Adjust touchboost values
Enable Kernel Samepage Merging - I've gone back and forth on this. For now, enabled.
Probably some other changes I'm forgetting.
a67 - Update + sync ramdisk from cm11 to enable native USB OTG. Add thermal charging shut off. Some kconfig tweaks.
a66 - Only hold wakelock is touch/slide to wake is enabled. Tweak default BFQ values a bit.
a65 - Update BFQ from 5.1 to 6r2. Set BFQ as default for testing. Tweak Deadline and CFQ (Franco's CFQ values). If CFQ is still causing reboots for some, I will revert it to stock in next build. Cgroups timer slack controller. Enable RCU priority boosting for testing.
a64 - merge 4.4 kernel changes. Update ramdisk for 4.4
a63.1 - CM hotfix
a63 - Add Tegra 4 SmartDimmer (ported from TripNRaVeR's port for the One X). It either works much better or is completely broken. Either way, it's an improvement from the old SmartDimmer. Add necessary ramdisk change for PAC rom. Add dm9620 usb ethernet support. Switch back to linaro 4.7 toolchain from google 4.6 (used in mr2 for stability reasons).
a62 - Add double tap to wake thanks to flar2 and sgt. meow. Add configurable timer to keep double tap to wake active after screen shut off. Remove Fsync toggle. Pointless and confusing with Dynamic Fsync available now. Update Dynamic Fsync from faux123. Set backlight levels back to defaults and disable otf_scaling. Some random stuffs.
New sysfs:
/sys/android_touch/wake_timeout
Value is in seconds. Defaults to 60. Set to 0 to keep double tap to wake permanently active at the price of battery.
a61 - Enable compass driver. Add Dynamic Fsync by Faux123. Disable Fsync off at boot. Enable Dynamic Fsync at boot. Remove wifi pm fast/max toggle as it is now pointless and won't work since 4.3 kernel update. Add an older, but simpler, version of usb host mode by mehrvarz. Fixed and enabled many 4.3 config options relating to things like selinux.
a60 - More ramdisk fixes
a59 - Update cm10.2 ramdisk to fix storage issues. Fix 00su init.d.
a58 - Incorporate cm10.2 ramdisk.
a57 - Update to 4.3 kernel base. 4.3 stock only. Ramdisk base courtesy of Francisco Franco. Fsync off at boot since the internal storage is just so appallingly slow.
a56 - Add back some missing config options removed in a55 to support various features. No CIFS support. Couldn't get it to boot for some reason.
a55 - Add v2 of Tegra AHB patch set. Remove and revert USBHOST patches. Revert to almost stock kernel config for testing (will probably revert back later). Revert to stock PA ramdisk for testing. Tweak default TouchDemand parameters for bettter performance. Hard-code deadline and cfq tuneables thanks to the work by those in Franco's thread - details in commitlog on github. Set deadline as default I/O scheduler. Add core hotplugging lock during touch boost/input to interactive governor based on implementation in stock interactive governor (not fully tested). Other minor, inconsequential changes.
a54 - Remove AHB bus drivers and patches.
a53 - USBHOST support and patches. WiFi adhoc IBSS support.
a52 - revert voltage table changes
a51 - fix flickering at brightness level 13 when smartdimmer was enabled by setting SD min to 10. Re-enable a 3g modem reset assignment fix. It was disabled in a49/a50; let's see if re-enabling it causes 3g drops to return (Otherwise TCP proportional rate reduction was the cause). Re-enable wifi p2p patch that was disabled in a49 under the impression it wasn't included in the stock kernel when it actually is (whoops). Increase the some DVFS voltages so that that they are at least as high pre-a50 (according to DVFS debug showing actual running voltage) and not more than 25mV greater than pre-a50. Hard-code default pm_qos_max_cpus as 4 instead of ULONG_MAX. Fixes aesthetic bug where the default tegra hotplug max_cores was 2147483647 (For the curious - it is 2^31 − 1, the maximum value for a 32-bit signed integer in computing).
Oh, and change thread title to accord with new XDA requirements.
a50 - re-enable dynamic edp. Rework some edp limits. Rework DVFS voltage tables to better match frequencies, YMMV. Removed 1.7GHz max frequency option as it was pretty split whether your device could run it or not. If people were more responsible and wouldn't complain about issues when running 1.7 or higher I would leave it in, but unfortunately that's just not the case. So it saves me headaches in the future. Sorry. It's a minor increase from 1.6GHz and most can do 1.6 just fine.
a49 - add some rwsem patches. Revert TCP proportional patch. Revert a wifi p2p patch. Fully stock /net and drivers/net in source now. Add custom min/max backlight interface. I'll add more info when I'm not so busy. Removed zRam support.
Change your max backlight (min - 255) - /sys/module/board_grouper_panel/parameters/max_backlight
Change your min backlight (1 - max) - /sys/module/board_grouper_panel/parameters/min_backlight
Enable/Disable on-the-fly backlight level redistribution through available brightness slots based on new min/max using math below (0/1) - /sys/module/board_grouper_panel/parameters/otf_scaling
- brightness = min_backlight + DIV_ROUND_CLOSEST(((max_backlight - min_backlight) * max((brightness - 10),0)),245);
a48 - actually upload a kernel that is mr1 + row patches + flash fix
a47 - mr1 + row patches + flash fix accidentally uploaded old kernel version...
a46 - disable have_efficient_unaligned_access. Add USB Host mode charging patches.
a45 - Fix adobe flash corruption. Add ARM unaligned access and enable have efficient unaligned access. Make sure slider min brightness and auto-brightness min have the same backlight value.
a44 - Start over at mr1. Add ROW patches. Add LZ4 compression.
a43 - revert all network and wireless patches since mr1.
a42 - revert some config options. Fix fixed_mode on boot for multiboot. Sched_mc_power_savings set to 0 instead of 2 to see how it affects wakeup.
a41 - ARM cpu topology and relevant patches. Enable multi-core scheduling. Enable maximum multi-core scheduling power savings for testing. Switch back to LZ4 ramdisk compression as Multiboot supports it now. Increase touchdemand sampling down factor since sampling rate was decreased previously.
a40 - Revert SLQB. Add latest usb host mode charging from mehrvarz's repo. Force detect/report usb as ac, no apparent benefit. Enabled a config SVIPC or something... I forget. Enabled rndis support from CM.
a39 - SLQB allocator. Switch back to Gzip ramdisk compression for multirom.
a38 - Fix adobe flash playback. Super fast Lz4 compressed for ramdisk and kernel. Arm unaligned efficient memory access. Some misc. wifi and network patches. Many other changes. No guarantees.
__________________________________________________
Downloads:
Alphas 5.1 -
a77 - https://www.androidfilehost.com/?fid=23991606952601904
a76 (CM12.1) - https://www.androidfilehost.com/?fid=23991606952601166
Click to show downloads for older versions of Android
Alphas 5.1 -
a75 - https://www.androidfilehost.com/?fid=95916177934553111
Alphas 5.0 -
a74 - https://www.androidfilehost.com/?fid=95916177934528566
a73 - https://www.androidfilehost.com/?fid=95784891001616369
Alphas 4.4 -
a69 - http://d-h.st/kI7
a68 - http://d-h.st/gPV
a67 - http://goo.im/devs/Metallice/Nexus7/4.4.x/M-Kernel_a67.zip
a66 - http://goo.im/devs/Metallice/Nexus7/4.4.x/M-Kernel_a66.zip
a65 - http://goo.im/devs/Metallice/Nexus7/4.4.x/M-Kernel_a65.zip
a64 - http://goo.im/devs/Metallice/Nexus7/4.4.x/M-Kernel_a64.zip
Milestone 4.3.x Releases -
mr2 (4.3.x)
http://goo.im/devs/Metallice/Nexus7/Milestones/M-Kernel_mr2.zip
Alphas 4.3 (post mr2) -
a63.1 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a63.1.zip
a63 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a63.zip
a62 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a62.zip
Alphas 4.3 (pre mr2) -
a61 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a61.zip
a60 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a60.zip
a59 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a59.zip
a58 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a58.zip
a57 - http://goo.im/devs/Metallice/Nexus7/4.3.x/M-Kernel_a57.zip
Milestone 4.2.x Releases -
mr1 (4.2.x)
http://goo.im/devs/Metallice/Nexus7/Milestones/M-Kernel_mr1.zip
Alphas 4.2.x -
a56 - http://goo.im/devs/Metallice/Nexus7/4.2.x/M-Kernel_a56.zip
a55 - http://goo.im/devs/Metallice/Nexus7/4.2.x/M-Kernel_a55.zip
a54 - http://goo.im/devs/Metallice/Nexus7/4.2.x/M-Kernel_a54.zip
a53 - http://goo.im/devs/Metallice/Nexus7/4.2.x/M-Kernel_a53.zip
a52 - http://goo.im/devs/Metallice/Nexus7/4.2.x/M-Kernel_a52.zip
__________________________________________________
Legacy downloads available at http://goo.im/devs/Metallice/Nexus7
THIS POST/GLOSSARY NO LONGER UPDATED DUE TO TIME CONSTRAINTS
Glossary of terms:
(that one may not be as familiar with as things like CPU and GPU)
Hotplugging - the process of turning CPU cores on and off.
G core(s) - One of four ARM A9 CPU cores found in the Tegra 3 SoC
LP (core) - The ARM A9 "Low-Power" CPU core found in the Tegra 3 SoC in addition to the 4 G cores. The LP core, contrary to what many seem to believe, does not run in tandem with the 4 G cores.
Runnable Threads (hot plugging) - Limits turning on more cpu cores based on the average number of running threads
Touchdemand - A modified ondemand-based governor that I designed and configured to better suit the Tegra 3 and android based on my observations
Variant -
Scheduler -
Other things
FAQ:
What's the difference between the mr(#) version/download and the a(#) version/download? Which should i download? What do these acronyms mean/stand for?
The mr# (ex. mr1) stands for milestone release number #. The milestone builds are the stable, bug-free, and thoroughly, extensively, and expansively tested builds of m-kernel.
The a# (ex. a38) stands for alpha build number #. The alpha builds listed under downloads are all of the alpha builds after the latest milestone build listed in reverse chronological and "morphological" (? FIX) order. It is the continuation of the "alpha branch" of m-kernel, and is basically the latest milestone with a ton of patches, fixes, and changes that are completely UNTESTED by anyone but me. The number and substantiality of changes since the latest milestone obviously vary and also depends on the number of alpha builds since the latest milestone release. An alpha build isn't guaranteed to be stable, working, and bug-free. They are testing builds leading up to the next milestone
Do you recommend setting the maximum number of cores to 2?
I don't necessarily recommend everyone do this, for it really comes down to personal preference. However, limiting the maximum cores to two is a very simple change to make that will slightly improve battery, with little to no impact on performance. Android 4.x is highly optimized for dual-core processing. There is no part of the Android 4.x OS that needs more than 2 cores for a smooth experience, and likewise there are few to no android applications that need 2 cores.
For the most part, the 3rd and 4th g cores are only activated during time sensitive actions such as opening an app for the first time (i.e. not previously opened and cached in RAM) and during screen rotation. These are short lived operations meaning those 3rd and 4th g cores are quickly turned off afterwards. In essence a small hit to battery life for even smaller benefits.
Why won't my minimum frequency go below 340MHz?!?
As long as you don't use system tuner, the minimum frequency does go below 340MHz. The minimum frequency is temporarily raised to 340MHz during an audio event to prevent audio playback problems when using ondemand and similar governors. The minimum frequency returns to the previous value afterwards. Some apps may show the minimum frequency as 340MHz because clicking the app to open it created a sound causing the minimum to temporarily rise. The app does not change when the minimum frequency goes back to its previous value.
Why can't over clock the GPU as high as I can on other kernels!?!
You can. You have to raise the voltage for the top GPU slot. Other kernels do this automatically and to fixed values. The amount necessary depends on the GPU frequency you are trying to run and your device. No devices are alike and the voltage necessary at whatever frequency will vary considerably from device to devices. Be aware that having to overvolt to run a certain frequency may mean suggest that you shouldn't run that frequency anyway. Raising the GPU frequency and voltage has risks to consider
What is this tegra 3 "variant" or whatever? How do I find it? What does it meeeeaaaannnn??!!?
You can find this info in /sys/kernel/debug/t3_variant
In the stock kernel/source, each device sku is recognized and assigned four ID values. For the CPU there is a primary "cpu speedo id" and a secondary "cpu process id". For the SOC, or core (think LP core, RAM, GPU, etc), there is a primary "soc speedo id" and a secondary "soc process id."
Each "pair" of ids is used to choose the respective voltage tables for the components they represent. I'm going to ignore the soc/core ids as they aren't relevant to my point and are the same for all our devices.
The CPU voltage tables are represented by ( cpu_speedo_id # , cpu_process_id #). The voltage tables that share the same first number, the cpu_speedo_id, all end with the same MHz value. To make things simple, Tegra uses the maximum frequency in the voltage table to determine the maximum frequency. All of our Nexus 7 Tegra 3s share the same cpu_speed_id, corresponding to a maximum frequency of 1.3GHz.
The second number, the cpu_process_id, differs between all of our N7 T3's. Faux123 and everyone refers to value as our "variant." This value, cpu_process_id determines the voltages for each frequency in the table. For each increase in cpu_process_id, the RANGE of voltages for the voltage table is compressed by 25mV (i.e. the voltage for the top frequency is decreased by 25mV while the bottom stays at 800mV and the middle frequency voltages are adjusted accordingly).
Therefore, in a direct sense, the cpu_process_id, or "variant", HAS NOTHING TO DO WITH CPU FREQUENCY. I'll repeat this. YOUR CPU_PROCESS_ID OR VARIANT HAS NO DIRECT CONNECTION TO THE MAXIMUM FREQUENCY CAPABILITIES OF YOUR CHIP. Variant/cpu_process_id refers to the voltage tolerance of your cpu. While there may be correlation or secondary connection to the maximum frequency capabilities of your chip, there is not direct connection. Additionally, cpu_process_id HAS NOTHING TO DO WITH YOUR SOC/CORE AT ALL, WHICH INCLUDES YOUR GPU/LP/RAM. A high cpu_process_id tells you nothing about your core and how high you can clock your GPU.
TL;DR - Variant, or more accurately cpu_process_id, refers to voltage tolerance, and has no direct connection to the max frequency abilities of your chip, and definitely has absolutely no relationship to your core/GPU.
To do:
Core voltages quirks.
Max freq delay necessity.
Why doesn't the kernel come with recommended settings?
One more
Re: [Kernel[3G+Wifi] M-Kernel - mr1
Sweet will flash this and give you some results later
Sent from my VS920 4G using Tapatalk 2
Re: [Kernel[3G+Wifi] M-Kernel - mr1
azoller1 said:
Sweet will flash this and give you some results later
Sent from my VS920 4G using Tapatalk 2
Click to expand...
Click to collapse
+1 I got a good feeling about this one
Sent from my SGH-T999 using xda app-developers app
tdizzle404 said:
+1 I got a good feeling about this one
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I really hope you're making a joke... I've had a thread in android development for a while now... 37 versions...
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
So really there is no need for gpu over clock unless for a benchmark?
Sent from my VS920 4G using Tapatalk 2
azoller1 said:
So really there is no need for gpu over clock unless for a benchmark?
Sent from my VS920 4G using Tapatalk 2
Click to expand...
Click to collapse
Says who? Me? Where?
No of course that's not true. GPU overclock can have benefits. Minimal due to RAM bottlenecking, but it will still marginally imrprove FPS in some cases.
I love your work metallica, we really appreciate it
I remember you made 5(+) different versions just because for 2 people having wifi issues...
You really spend a lot of time at this and this is a great kernel.
Thanks!
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
Metallice said:
I really hope you're making a joke... I've had a thread in android development for a while now... 37 versions...
Click to expand...
Click to collapse
No joke here ive had decent results with your kernel I'm just commenting on the update
Sent from my SGH-T999 using xda app-developers app
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
Oc GPU to 520 and when I left trickster It blacked out and rebooted
Sent from my Nexus 7 using Tapatalk 2
Nothing to say at the moment but gotta post in it so I get subscribed. Keep up the good work!
I had just posted in the original M-kernel thread and couldnt edit my last post (probably cuz its being moved) . I was unable to set cpu max core to 4 w/o system freezing up. I just upgraded to mr1 and it shows 4 cores active and no freeze ups so far. I will leave everything to stock for now.
Cool you finally moved to "original" forum, makes it alot easier for me to navigate since I am usually in this forum anyways..
thxs
d
azoller1 said:
Oc GPU to 520 and when I left trickster It blacked out and rebooted
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi, you just need to increase the GPU voltage a little bit before you overclock it to 520mhz, hope that helps
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
azoller1 said:
Oc GPU to 520 and when I left trickster It blacked out and rebooted
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Maybe you should try reading the FAQ :/
Sent from my Nexus 7 using Tapatalk HD
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
Congrats my friend. What a journey!
How,s it feel to be in the big leagues
Edit: mr1 flashed. Keeping it default for now. Seems very smooth. Another excellent kernel. Thank you for everything.
Cheers, FReaKRaNT
Re: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
thanks for the hard work the kernel works great and the FAQ was very helpful.
Sent from my Nexus 7 using Tapatalk 2
Απ: [Kernel[3G+Wifi][4.2.2] M-Kernel - mr1
Guys does flash working for u without any problems?
Edit:I'm on Francos kernel now. I just flash this kernel without wipe cache and dalvkin?
Sent from my Nexus 7 using Tapatalk HD
Cool you're in Original Dev now. Congrats Metallice.
Downloading mr1 now. :good:
CAF is for CM and its derivative ROMs (Make sure you KNOW what you are flashing... ie, STOCK ROM flash normal zip... CM ROM flash CAF versions)
Change log:
http://faux.romhost.me/flo/kk44/changelog.txt
Beta - http://faux.romhost.me/flo/beta
Enhanced Stock - http://faux.romhost.me/flo/kk44/
Mainline - http://faux.romhost.me/flo/kk44/
Ultra CCCCCCOMBO - http://faux.romhost.me/flo/kk44/ultra/
github: https://github.com/faux123/flo_nexus7
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 1.944 GHz (or 1.836 GHz) for performance, 1.512 GHz for battery
Min clock - MHz 384 MHz for both
CPU Governor - Interactive for performance, Intellidemand for battery
mpdecision - Off
Snake Charmer - OFF for performance, On for Battery
Eco Mode - Off for performance, On for battery
Set On Boot - On
SOC Control
Set On Boot - On
C0 - On
C1 - On
C3 - On (Note: N4 AP modem is very sensitive to some of the deeper sleep states, if you experienced Green/Yellow AP Modem Watchdog Bark screens, I recommend disabling C2/C3 states).
Voltage Control
Set On Boot -
Global CPU Voltage - mV
intellidemand gov control
Up Threshold - 75 for both
Boost Frequency - 0 for both
Two Phase Freq - 1134000 for both
[*]LMF Max Freq - 1512000 for performance, 1350000 for battery (deprecated)
Sampling Rate - 50000 for both
Optimal Freq - 1296000 for both
Synchro Freq - 756000 for both
Set On Boot - On
interactive gov control
Hispeed Load - 99
Hispeed Freq - 1512000
Timer Rate - 20000
Min Sampling Time - 80000
Set On Boot - On
GPU Control
GPU Governor - ondemand for both
GPU Clock - 487Mhz for performance and 400 Mhz for battery
GPU Vsync Toggle - On for both
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - FIOPS for both
Readhead Size (eMMC) - 2048 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Vibration Control
Set On Boot - On for both
Vibration Control - 70 for both
Screen Color
Set On Boot - On for both
Factory Presets - LG Presets
Color Adjustments - R, G, B 255, 250, 245
Gamma Amp Adjust 0 - R, G, B 13, 20, 22
Gamma Amp Adjust 1 - R, G, B 0, 2, 3
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
Above is what I use personally. MAY NOT be optimal for all :fingers-crossed:
reserved 2
reserved 3
faux123 said:
reserved 2
Click to expand...
Click to collapse
Nice to see you here man. Gonna check this out.
+1
Thanks
Sent from a Candy Painted N7 (2013)
IT"S HERE!!!!!!!! Love the name for the top level one. Flashing time! Can't wait to see your recommended settings.
Shazam!!! Finally the kernel I want appears
Sent from my SGH-I317 using xda premium
I've heard good things about your work. I'll be interested in flashing this shortly. Thanks for the work.
yessss the kernel i have been waiting for arrives! thank you faux!
About time . Thanks!
Sent from my Nexus 7 using Tapatalk 4 Beta
so glad to see this kernel, worked amazing on my Nexus 4. its too bad I can't use the Ultra.
keep up the great work.
I'm guessing your reset kernel - grouper-faux123-reset-kernel-4.2.2.zip - won't work with 4.3? Will there be a 4.3 reset kernel forthcoming?
thecdn said:
I'm guessing your reset kernel - grouper-faux123-reset-kernel-4.2.2.zip - won't work with 4.3? Will there be a 4.3 reset kernel forthcoming?
Click to expand...
Click to collapse
Yup, wouldn't work, totally different hardware. But I am curios of the same thing.
Sent from my Nexus 7 using XDA Premium HD app
using mainline when i set to 2106 and benchmark it gets set back 1512 or 1944
Can't speak on battery yet, but it sure seems snappier!
Sent from my Nexus 7
Aaaaand I should've read the change log before I asked. Deleted question
@faux123: what would the beta kernels normally be? Es, mainline, or ultra?
Sent from my Nexus 4
Awesome.. Picked up your app to go with it and its smooth thanks for the hard work
Sent from my Nexus 7 "Flo" using Tapatalk HD
0.0 said:
Aaaaand I should've read the change log before I asked. Deleted question
@faux123: what would the beta kernels normally be? Es, mainline, or ultra?
Sent from my Nexus 4
Click to expand...
Click to collapse
Mainline
Sent from my Nexus 7 using Tapatalk 2
This doesn't have cifs integrated yet does it? Please say yes...