[FAQ] AK Kernel 101 - Samsung Galaxy Nexus

AK Kernel FAQs
{
"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"
}
Q1) What are custom kernels? What are the benefits of using custom kernels?
A kernel is basically the bridge between the software and hardware. Whenever you command your phone to do something (launching an app), the software sends that request to the hardware which in turn, makes the launching of the app possible. Custom kernels for Android are unofficial creations of independent developers. Unlike the kernels that OEMs make, custom kernels offer more modifications that allow you to tweak your phone in every possible way.
Benefits Of Installing Custom Kernels
You can benefit from having better control of your device. These options are most helpful for users who want to maximize the full potential of their phone or perhaps want to extend their device's battery life. Below are some of the benefits of installing custom kernels.
-Adjust CPU frequencies and set profiles like OnDemand, Battery Saving, etc.
-Underclock and overclock CPU speeds
-Underclock and overclock GPU speeds
-Adjust voltage
-Adjust touch screen sensitivity
-Equip your phone with BLN (backlight notifications)
-Custom recovery that allows backups and restorations of entire ROMs as well as installation of .zip files
-Minimum screen brightness pushed past the limitations of stock kernel
-Conserve battery (with the right settings
Q2) Where can I get the AK kernel and which one should I flash?
The latest kernel is always linked in the OP. The kernel is broken down between the Purity version and Pirate version. The Purity kernel is meant to be as close to stock as possible. The Pirate kernel on the other hand is more of a experimental kernel with more options than Purity.
Q3) I have a XXXXX version of the Galaxy Nexus, will it work?
Yes, the AK kernel works on all versions of the Galaxy Nexus. This includes the CDMA and GSM versions. Download the kernel from the AK thread.
Q4) How do I make changes to my kernel settings? (ex: voltages, fastcharge, etc.)
Download the Trickster Mod from the Google Play store.
Q5) Can I use AK on xxxxx rom?
AK is known to work on any rom based on AOSP, AOKP, CM10, and even MIUI.
Q6) How do I install it coming from another kernel?
TWRP is the prefered recovery, although CWM recovery may also work.
The ideal way to install AK, especially if you are coming from another kernel, is to do the following.
Wipe cache and dalvik cache
Wipe /system
Re-flash your ROM
Flash AK
Fix permissions in recovery (this may take up to a minute or two)
Reboot
Q7) Do I need to wipe cache/dalvik/battery stats/etc if I'm just installing the kernel onto a previous AK version?
No, download and flash away. Only wipe battery stats if your battery percentages are off. Do not believe the myth that doing so will increase your battery life.
Q8) Do I need to run any other apps like SetCPU or equivalent?
No, if you plan to install and run Trickster Mod, please uninstall any other apps that may interfere with your CPU settings. If you are still running into problems (ex: reboots, FCs, etc.) please check your /etc/init.d directory for any left over scripts from other rom or kernels. These may interfere with how AK operates.
Q9) What is Smart Reflex? What is FSync? What is Thermal Throttling?
Smart Reflex is used to scale your voltages. Voltage will be increased or decreased when required. If you are overclocking, disable SR to have access to higher clock speeds.
FSync is a system call that can be toggled on to write buffers to disk (slow) or toggled off (fast) for performance. FSync defaults to on in the linux kernels, the option to disable it exists but it is advised to use this with caution. COMPLETE data corruption could occur if the phone crashes with fsync disabled.
Thermal throttling protects your CPU from overheating. If you are benchmarking, turn this option off to prevent throttling of the CPU that can cause lower scores. Just remember to re-enable it afterwards. Bear in mind that at 110C, the CPU will shut down no matter what. It is not advised to disable thermal throttling, however the option exists for those enthusiasts who are aware of the risk of permanent hardware damage. Please take the necessary precautions!
Q10) Does PGM (slide2wake) for the Nexus work with AK?
Yes PGM is supported on. But be sure to use the latest(March-25) version.
Note- The latest free or pro version of the pgm app is required.[/B]
Q11) What is the sleep of death (SoD)?
You turn the screen off, when you want to pick it up, you can not wake it up.
There is no blinking notification and when you call it, there is no ringing or vibration. When you press and hold power, it does not turn on, otherwise it was OFF.
If you play a game and it reboots, or freezes. That is NOT a SoD.
Q12) Can xxxxx option be implemented in AK?
Stefano wants to keep Purity as close to stock as possible but feel free to request features for Pirate within this thread or the dev thread. Whether or not it gets implemented is up to Stefano.
Q13) I want to keep my Rom's bootanimation, why does AK kernel keep trolling me?
The boot animation by Ciprian is hardcoded so it cant be changed.
Q14) How is battery life?
No one can predict your usage. However, most folks are getting great screen on time and performance.
Q15) I just experienced a reboot, how can I help to pinpoint the problem?
Open up terminal emulator and issue the command:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Take this last_kmsg.txt file and show it to Stefano in this thread. It's suggested to copy the contents and use something like pastebin instead of spamming the thread with your log.
Q16) Whats with all the name changes?
Stefano aka AK changes the name whenever he makes major change to kernels, meaning they are different kernels thats why they have different names.. thats why the kernels went from berserk>dummy>pirate>cylon>AK/diamond>.. AK/Diamond are the same he just changed the name from AK to diamond thats why the changelog for diamond leads to changelog of AK.. as for purity that kernel is as close to stock as possible so its name has been purity since i started using this kernel, Stefnao stopped making the purity kernel and now BigBrother1984 makes Rubik in its place
Any other things that should stand in the FAQ? Did I make some horrible language mistakes? Write me a PM or post in this thread.
=============================
Credits-
Stefano - for this great kernel :good:
GideonX - for letting me use this format and some of the question from his post :good:

If you have any problems, you need to collect the following data before reporting it:
- Report Only with default Freqs + default Uv
- kernel version
- rom version
- governor
- scheduler
- freq cpu
- freq gpu
- logcat
- dmsg
- last_kmsg
- short description of the problem

First!
Great job on this.

jstn_hillis said:
First!
Great job on this.
Click to expand...
Click to collapse
thanks.. btw guys i think this thread should be in the Q&A section instead so i am requestiong that a MOD move it there :good:

Khizar said:
Q4) Can I use AK on xxxxx rom?
Trinity is known to work on any rom based on AOSP, AOKP, CM10, and even MIUI.
Click to expand...
Click to collapse
What? :silly:

Kakashi Hatake said:
What? :silly:
Click to expand...
Click to collapse
i used GideonX post that is linked in the OP to make this and looks like i forgot to edit that, thanks for the catch :good:
PS- if anyone finds something else or has any siggestions please let me know :good:

Honestly I'd like to see peoples custom and under volt settings.
Sent from my Galaxy Nexus using Tapatalk 2

thx dude

PGM(free and better version) can't work with my Gnex with PA 20/2/13 on both Purity kernel and Pirate kernel.

fishhelmet said:
Honestly I'd like to see peoples custom and under volt settings.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
users are more than welcome to post their settings here :good:
pponto said:
thx dude
Click to expand...
Click to collapse
your welcome
baiyy0906 said:
PGM(free and better version) can't work with my Gnex with PA 20/2/13 on both Purity kernel and Pirate kernel.
Click to expand...
Click to collapse
the issue isnt with AK, its with pgm, the free version is outdated

Khizar said:
users are more than welcome to post their settings here :good:
your welcome
the issue isnt with AK, its with pgm, the free version is outdated
Click to expand...
Click to collapse
you are right,I find the latest version,that's work , thank you

Khizar said:
Q12) I want to keep my Rom's bootanimation, why does AK kernel keep trolling me?
The boot animation by Ciprian is hardcoded so it cant be changed.
Click to expand...
Click to collapse
I have no problem with branding, but I believe just a splash of the logo would suffice. I am running the Pirate version and not a huge fan of the pirate splash and would really like to remove it or at least have the option to change it to the AK logo. Any chance of this ever happening?

ThePhantom97 said:
I have no problem with branding, but I believe just a splash of the logo would suffice. I am running the Pirate version and not a huge fan of the pirate splash and would really like to remove it or at least have the option to change it to the AK logo. Any chance of this ever happening?
Click to expand...
Click to collapse
You can download source, compile with:
CONFIG_LOGO is not set

Why do I get major lag after receiving a notification with this kernel?
Sent from my Galaxy Nexus using xda app-developers app

soccer568 said:
Why do I get major lag after receiving a notification with this kernel?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i persoanly dont have any lag with this kernel(i use stock settings) but post the following info and we might figure out why you are getting lag-
- are you using custom Freqs + Uv?
- kernel version?
- rom version?
- governor?
- scheduler?
- freq cpu?
- freq gpu?

So I'm new to custom kernels, but I'd like to see super basic stuff for newbies in the faq. like "What is the benefit of installing a kernel and what does it do?" in the faq. or like "Is there a rom that works better with this kernel?"

uncola said:
So I'm new to custom kernels, but I'd like to see super basic stuff for newbies in the faq. like "What is the benefit of installing a kernel and what does it do?" in the faq. or like "Is there a rom that works better with this kernel?"
Click to expand...
Click to collapse
i like the first question so will add it in the OP, as for second question nobody can answer it but you, every device is different so the rom/kenrel that works best for me wont necessarily work best for you thats why i recommened that you try different rom/kernel combos

This might help with the question "is there a rom that works better with this kernel", or any kernel for that matter.
http://forum.xda-developers.com/showthread.php?t=2160723
Sent from my Galaxy Nexus using xda app-developers app

My personal opinion about this kernel
I really like the thing to keep it update to mainline linux, only 2 kernel keep this ( leankernel & franco kernel )
I noticed some strange things
the first is disabling MPU Smartreflex and set lower voltage than SR , device is hot and drain more battery WHY? it's unsense ( test with #704 ) anyone can confirm?
The second one too much battery ( using SR ), in the past i love check my phone every seconds and close all apps to keep some juice inside battery, now with AK kernel battery life is something incredible and it's annoying : / , i arrive to 21:00 ( from 7:00 ) with 30-40% and 4-5 hours screen on and ever single thing turn on ( i'm using google now only for meteo lol ), with others kernel same thing, i arrive with much lower %, like 5-10%
This is my settings:
AK kernel 704
AOKP Self Compiled updated with 22feb git
Interactive ( 350 - 1060 Mhz ) - ( Screen off max : 535 Mhz ) - ( hispeed_freq : 810000 ) ( brightness: 50% ) ( 135 apps installed ) ( Full disk encryption [ said only cuz disk operation use more CPU = more Battery ] )

I feel you should include the Wep not working on 704+ pirates.
SOS sent from my gnexus captured by the pirates.

Related

[KERNEL][GPL] ezterry A100 kernel (ezT20) 2.6.39.4-ezT20-v1.0.1~ [Aug 12th, 2012]

~~~~~ Latest release
A100 - V1.0.0 (first stable release)[Size=+1]
ezT20-v1.0.1-a100_S.zip
MD5: d4febaf119f618afda9c749da4615445
[/SIZE]​
**Please remove all undervolting and overclocking before installing, as different kernels will use the CPU differently, This may require you thus to change the OC/UV levels to be stable with this kernel.
While plenty of work has gone into ensuring this kernel was fit for use: I take no responsibility for any problem the use of this kernel may cause, and/or loss of data if you fail to backup your data before installing it. Proceed at your own risk
A100 Installation:: simply flash the zip from recovery, this will extract and replace the zImage (linux kernel) from your current rom; and leave your existing ramdisk unchanged.
A101 Installation: : Experimental support only (this may or may not work): Your ICS rom requires to load the new simdetect_switch.ko module on boot, if your rom dose not have support for this, but has support for init.d scripts please first install the patchkit ezT20_a501_patchkit_S.zip MD5: 617f558555c13d215103cd3669d3c009, (This kit only includes the init.d script to load the simdetect_switch module if it exists, and doesn’t include the actual kernel or modules; Note its labeled for the A501, however ought to work as is on the A101)
After the patch kit is installed (or if it has been previously installed/is part of your rom) you can flash the a100 zip above to install the kernel + related modules.
Let me know if this works out
CM (9 and 10) installation Install per your device above, then install the audio patch init.d scripif you have audio problems: ezT20cmaudio_patch_S.zip MD5: 26251900115b0ca433f26f4d95e7f269
Are you an A500 user? you are in the wrong place see here
~~~~~ Kernel Features
- BFQ IO scheduler (details here)
(BFQ is now the default scheduler, previously was noop)
- Lulzactive CPU governor (by tegrak with a500 modifications by myself)
(Interactive will be the default governor for most roms, as defined on the ramdisk)
- Max OC speed: 1504MHz (default 1000MHz)
- Min OC speed: 216MHz (default 216MHz)
- Fixed voltage tables to allow OC on devices previously unable to on A500-OCTestV3 and A100-OCTestV1
- initial 3g support thanks to patches from Vash (v1.0.0 - a501) .. switched to acer's code in v1.0.1 (a501/a101)
- ability to disable acer audio settings (v1.0.1)
~~~~~ Kernel Notes/Warnings
** A specialized lulzactive configuration program can be found at: https://play.google.com/store/apps/...1bGwsMSwxLDMsImNvbS50ZWdyYWsubHVsemFjdGl2ZSJd
(note setCPU will also let you change the values, I only mention tegrak's app as it may make it easier to understand what is being changed)
** The kernel ought to work in place of the stock ICS kernel, roms requiring special kernels may not function with this kernel
** de-odexed roms may have graphical artifacts that are made more serious by this kernel, civato and I have been working on a build.prop tweak to re-generate odex like dex files on de-odexed roms to solve this
** Voltage display may not be accurate (a rework of the UV logic is planned) note UV offsets are accurate.
(for a quadrant sample on the a500 see the related post
~~~~~ Kernel History
This kernel is the continuation of the Overclocked Test kernel, originally posted for the A500 here and subsequently for the A100 here
~~~~~ Credits
Thanks to:
* richardtrip - original OC and MIN/MAX code
* tegrak - for lulzactive
* civato - for being a willing advanced tester
* Bobg1231, Metallkasten, pio_masaki, Moscow Desire - additional testers
* Vash - A501 3g modem patch set
* Acer/NVidia for providing the source to our devices
* The countless number of people that have created the linux kernel in the form it is today
~~~~~ Built list w/ source links
v1.0.1 ezT20-v1.0.1-a100_S.zip
MD5: d4febaf119f618afda9c749da4615445
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v1.0.1
Tarball: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v1.0.1
v1.0.0 ezT20-v1.0.0-a100_S.zip
MD5: 3b3d3ee93528393384884066c25f2db7
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v1.0.0
Tarball: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v1.0.0
v0.9.9 ezT20-v0.9.9-a100_S.zip
MD5: 1a7f6f296e5ec0d43836cbe318928d1b
Github: https://github.com/ezterry/AcerTabKernel
Tag: ezT20_kernel_v0.9.9
Tarbal: https://github.com/ezterry/AcerTabKernel/tarball/ezT20_kernel_v0.9.9
~~~~~ Change Log
v1.0.1
*) Import of acer's 3g code [A101 and A501]
*) audio updates to better work with CM roms when cm audio patch is applied ezT20cmaudio_patch_S.zip MD5: 26251900115b0ca433f26f4d95e7f269
*) Allow lower min-voltage
v1.0.0
*) cleanup graphics logic with more patches from the nvidia tegra test kernel (and other patches to prevent the graphic under-runs causing screen flashes on some roms) [applies to all devices]
*) modify lulzactive (yet again) to attempt to stem a rare deadlock .. frequently resulting in a SoD overnight on my tab (probably not most peoples constant SoD problem) [applies to all devices]
*) Add Acer A501 patches for 3g modem [applies to A501]
*) fix some touch events on the A50X caused by the a100 patch set rolling back the a500 touch driver, the touch drivers are separate so this ought not impact the a100 [a50x only]
v0.9.9
Initial release, providing some bugfixes and new features to the previous OCTestV3
~~~~~ Developers Corner
The building instructions for this kernel are identical to the ones for the A500, except that instead of using picasso_defconfig you use vangogh_defconfig (from the same codebase and same commits)
Therefor rather than copying the instructions here, and attempting to keep them in sync I recommend you review the original "Developer Corner" post in the A500 thread.
http://forum.xda-developers.com/showpost.php?p=27241693&postcount=2
Great work ! ! !
Anychance you could look at getting touch to wake with your kernel ?
Sent from my HTC EVO 3D X515m using XDA
maek_it_happen said:
Great work ! ! !
Anychance you could look at getting touch to wake with your kernel ?
Sent from my HTC EVO 3D X515m using XDA
Click to expand...
Click to collapse
I saw some patches (noted you mention it before) looks interesting but requires some work for our device.
May be trivial but requires a hook added to our touchscreens not just the ones from whatever device I grab the source from .. hopefully I will figure it out in the future.. there are still one or two things such as the UV logic I wish to cleanup first.
Wow! Are you sure is BFQ governor is stable? maybe SIO?
pomka78 said:
Wow! Are you sure is BFQ governor is stable? maybe SIO?
Click to expand...
Click to collapse
Given many have been using it on android now for a long time (kernels started using it as the default on the htc dream in cupcake days) not to mention its following of other linux usrers and the patch sets are well maintained..
Yes its stable.. more than deadline on our kernel anyway (also in the codebase but not in the build, got tired fast of the random reboots).
But if you rather noop its still included. Its horrible however when multiple apps access flash.
SIO is described as being bad timings on flash and a combo of noop and deadline.
pomka78 said:
Wow! Are you sure is BFQ governor is stable? maybe SIO?
Click to expand...
Click to collapse
When I was testing bfq seemed stable and benchmarks just as fast as noop. Keep in mind it was a test kernel so it was an earlier version so I would imagine it would do fine. I ran into no IO related issues during testing. Tested on my A100.
Oh here, lulzactive, BFQ 1.5ghz -145 UV all the way. Not my best, not my worst.
{
"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"
}
Tapatalked from my Galaxy S II.
Thanks for answers! I flash kernel on CyanogenMod9 Alpha 3 and all works fine...
ezterry said:
I saw some patches (noted you mention it before) looks interesting but requires some work for our device.
May be trivial but requires a hook added to our touchscreens not just the ones from whatever device I grab the source from .. hopefully I will figure it out in the future.. there are still one or two things such as the UV logic I wish to cleanup first.
Click to expand...
Click to collapse
Thanks for looking into it ?
Sent from my HTC EVO 3D X515m using XDA
Thanks for your work!
Keep up the good work. I will try it out soon. Is this built purely for high benchmarks or is it reliable as a daily driver?
mattyray1 said:
Keep up the good work. I will try it out soon. Is this built purely for high benchmarks or is it reliable as a daily driver?
Click to expand...
Click to collapse
I'm running the oc kernel with flexreaper, set to 1.4ghz on demand and its been daily use stable.
I'm running v0.9.9 with CM9 at 1504 mhz. No issues in over a week of use.
Sent from my Acer A100 running CM9 using XDA Premium.
Mordak said:
I'm running v0.9.9 with CM9 at 1504 mhz. No issues in over a week of use.
Sent from my Acer A100 running CM9 using XDA Premium.
Click to expand...
Click to collapse
I've (on the a500 build) have found some SoD on the lulzactive governor and we have found issues with some roms but the new test version seems much more stable.. so hopefully Monday will see v1.0!
Sent from my Galaxy Nexus using Tapatalk 2
ezterry said:
I've (on the a500 build) have found some SoD on the lulzactive governor and we have found issues with some roms but the new test version seems much more stable.. so hopefully Monday will see v1.0!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah I can report no SoD dispite trying. I left wifi on and keep awake off and left it charging for 16 hours. Fired up like normal. For those wondering....for me I find leaving wifi on always and leaving it charging can cause it on other devices.
My wife ran it her way as well, no issues. You kinda have 2 testers at this house lol.
No freeze, reboot, crashes or force close in normal usage and heavy usage. A100 at least shows its probably ready for release into the wild.
Tapatalked from my Galaxy S II.
How many of you play stressful games while being over clocked? I just picked up this tab yesterday updated to ics rooted n noticed n64oid was a little laggy. After installing this kernel bumping up to 1400 eliminated all lag. I just wanna know if I should worry being I play lots of games on here.
Sent from my A100 using XDA
h3r3tic said:
How many of you play stressful games while being over clocked? I just picked up this tab yesterday updated to ics rooted n noticed n64oid was a little laggy. After installing this kernel bumping up to 1400 eliminated all lag. I just wanna know if I should worry being I play lots of games on here.
Sent from my A100 using XDA
Click to expand...
Click to collapse
Rolls fine at 1.5 for me. Heats up a little under stress and battery will be gone in a couple hours, otherwise seems fine.
Tapatalked from my Galaxy S II.
v1.0.0
Version 1.0.0 is out See OP for the download and source links
This version improves stability on the A100/500 systems, plus adds experimental support for the A501 devices. (the a501 information is in the a500 version of the kernel/thread, a100 users ought not be impacted by these changes)
Already had a few times where when my screen times out by itself it takes me almost 3-4 mins to get it to come back on. Is this the governor issue? I was using lulz. At 1.5. I didn't noticed if this happened on v.99. I switched to interactive to see if it persists.
Sent from my A100 using XDA
h3r3tic said:
Already had a few times where when my screen times out by itself it takes me almost 3-4 mins to get it to come back on. Is this the governor issue? I was using lulz. At 1.5. I didn't noticed if this happened on v.99. I switched to interactive to see if it persists.
Sent from my A100 using XDA
Click to expand...
Click to collapse
I've never seen that on v1.0, nor heard reports of it till now: on previous versions 0.9.9 and the testing versions I have seen such things when the system became busy, and became stuck at min frequency.
Avoid screen off profiles, lulzactive automatically reduces speed to the 816MHz when the screen is off (assuming that is less than max) lower than that background tasks may take additional unexpected time and delay the device from full sleep where the cpu turns off.
Otherwise what rom are you using, any large apps running, logcat? dmesg? (logcat will tell us if its something installed, dmesg will show what the kernel did.
Well I'm on stock ota ics 4.0.3. Just your kernel when this happened I was just downloading SD data for n.o.v.a 3. Happened every time the screen timed out. It also happened on a multiple file transfer from internal to SD when I did the dirty swap for more space. Would maybe switching the governor for screen off fix this? To like on demand or interactive. To get a logcat I would need to replicate the problem using adb correct? Never actually did one before. I don't have anything special installed only large files are games. That's pretty much what I use it for along with internet.
Sent from my A100 using XDA

[APP] RENOVATE Gaming Boost JellyBean v1

First off i would like to say a massive thanks to henk2484 who made the original app then sent me the source code to modify/improve to my liking.
I would also like to say a massive thanks to hamdir for for finding all the optimal values.
Right here we go
RENOVATE GAMING BOOST
{
"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"
}
What is it?
Renovate gaming boost is a simple app which optimized the kernel to be used while gaming. It will give you easily the best gaming experience you have ever had on a mobile phone.
How do i use it?
It's really simple to use, before you want to start gaming just open the app, grant root permissions then click on enable. After you've finished gaming, simply open the app again and click to disable the boost.
Which kernels/ROM support this app?
Theoretically, it will work on all kernels and roms, but if your ROM dev uses custom ondemand values the app won't work. Ask your dev to look at the source code I uploaded and get him to tweak the app to match his ROM values.
Any bugs/side effects?
Obviously, gaming on a device like the One X will cause big battery drain, so don't be complaining to me if your battery only lasts an hour while playing a multi core game like ShadowGun.
How to install?
Flash the zip in recovery.
Changelog:
JellyBean v1- 27/11/2012:
Compatible with JellyBean ROMs
Changelog:
v2.1- 15/10/2012:
Fixed Minfrees
Fixed CPU Clocks
v2- 15/10/2012:
Two versions for stock and custom kernels,
Removed 1.4ghz lock on custom kernels,
Re-added GPU scaling tweaks
Overclocks GPU on supported kernels.
v1-19/07/2012:
Initial Release
Download Link:
Renovate Gaming Boost JellyBean Stock Kernel
Renovate Gaming Boost v2.1 (Stock Kernel)
Renovate Gaming Boost v2.1 (Custom Kernel)
Devs if you wanna include this in your rom feel free, just send me a pm telling me so i can see how any people are finding it useful.​​
Reserved
HTC One X - Tegra 3
RENOVATE Gaming Boost JellyBean v1.0
This version is suitable for most HTC phones including the HTC One X+
Sets supercharger's max memory minfree values (8, 16, 200, 220, 240, 275), when turned off it returns to stock ICS/JB values (32, 40, 28, 56, 64, 80)
Optimizes HTC's ondemand governor to greatly reduce random CPU stalls, turning boost ON will always switch you to ondemand governor with the tweaked values, turning boost OFF will also switch you back to ondemand governor with it's original stock values (this will also help you apply the performance tip below)
Unlinks the GPU from the CPU in 3D mode, that is when gaming if the CPU chooses to drop down, the GPU will keep using the upper clock (3d scaling off)
It will Attempt to set GPU520 for kernels using Franco's GPU interface
Does not attempt to change the scheduler, every kernel has it's own choice of schedulers, you can still set your favorite scheduler outside this app (using scripts or SetCPU)
It will not touch the CPU clocks, on stock JB ROM you can choose between 1300mhz and 1500mhz using the stock powersaver mode, on custom kernels you can still OC (using scripts or SetCPU)
For those who can't get it to work try to use the stock values fix zip from here
This version was optimized for HTC's stock JB OTA and Kernel, checkout the Stock HTC JB Kernel 3.14.x.24 review
PowerSaver mode
With HTC powersaver's CPU mode turned off, the device will use up to 1500mhz single and 1400mhz quad core, sadly for some rare quad enabled games like shadowgun this might cause random performance drops when the game calls the single core 1500 step
Enabling HTC powersaver's CPU mode will lock the device to 1300mhz quad core, effectively its a quad lock but slightly slower with less heat and battery consumption
Experiment with your game to find which mode works best along with game boost
Locking the quad
Simply set the CPU clock to 1400 on boot and it will stick, the powersaver mode will switch between 1300 and 1400, both quad modes without the buggy single core 1500 step
Place the attached 99CPU1400.txt script in etc/init.d folder, remove .txt extension and set all permissions, reboot
If this doesn't work or you are using a kernel without init.d support, simply use SetCPU, change the clock to 1400 and set on boot
Aggressive Performance tip
You can go further if you want to force max possible performance, unlike ICS, JB kernel allows the performance governor to use full quad, so you can enable boost ON and then switch to performance governor using your favorite SetCPU app, with powersaver off the device will use up to 1400mhz quad cores and idle around two cores 1200mhz, with powersaver on it will use up to 1300mhz quad cores and idle around two cores 1200mhz, naturally this tip will cause extra heat and battery drain, once you are done disable game boost and you will switch back to stock ondemand governor
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
RENOVATE Gaming Boost ICS v2.1: NCX gaming kernel v4 is the recommended custom kernel (based on pure stock kernel)
Unlinks the GPU from the CPU in 3D mode, that is when gaming if the CPU chooses to drop down, the GPU will keep using the upper clock (3d scaling off)
Set GPU520 for Franco's R20 GPU method
No longer tries to change the scheduler, since every kernel has it's own choice of schedulers, you can still set your fav scheduler outside this app (using scripts or set CPU)
The custom version will not touch the CPU clocks, this way you can OC or UC on supported kernels (using scripts or set CPU) and still use gaming boost, the custom version is best for Franco R20 and Faux 11
The stock version is for both ICS and JB stock kernels, for the ICS kernel like always you need to make sure not to switch off the screen after boost, on JB the values no longer reset on screen off
For those who can't get it to work try to use the stock values fix zip from here
If you still have trouble getting this app to work since it doesn't request SU or do anything, check this post
you will know that the app is working, if it requests SU the first time and takes a second switch to the boost mode
Warning! due to HTC code, on many kernels including both stock and older Faux, turning off the screen will reset two vital parameters set by the app so you have to make sure not to turn off the screen between boost and playing a game
This issue was fixed in most custom kernels like Gaming Kernel, Faux and Franco, if you are not using such custom kernels always remember to renable boost mode after screen unlock
If you still have trouble getting this app to work since it doesn't request SU or do anything, check this post
If you like to set the boost mode permanently:
How to set the gaming boost mode permanently using SetCPU 3.x for any Kernel
For AOSP 4.0.x ROMs, you will also need this:
RenovateGamingBoost_SenseFramework.zip (for AOSP 4.0.x ROMs, it will add the needed Sense framework system files, flash first followed by the app)
For AOSP 4.1.x ROMs this app is currently not working
Thanks to rayford85 and h00py for the installation solutions
Special thanks to timlambo for helping us test and refine the parameters
---------------------------------------------------------------------------------------------------------
For information the One X should last 2.5 hours of non stop gaming on full boost with screen brightness at 20%, it reaches a max of 52c in ambiance of 33c, do not try this while on the charger
---------------------------------------------------------------------------------------------------------
here is a link the original gaming boost thread for those who like to understand what this app really does:
[GUIDE+TOOLS] How To Easily Maximize One X Tegra 3 Game performance - root
Superb. Thanks guys.
Something that would really be useful if possible is a Tasker plug in to automatically enable and disable when a game is launched.
Sent from my HTC One X using xda premium
Can I suggest you keep the MD5 Sum in your OP?
MD5: b78c274cfd484c787d0cca7ed61435fa
Great work man
Awesome! I just can't seem to install it though, says failed to install.
Pointlol said:
Awesome! I just can't seem to install it though, says failed to install.
Click to expand...
Click to collapse
Either push to system/app with adb or put on sd card and move to /system/app with a root explorer.
wilkyyyy said:
Either push to system/app with adb or put on sd card and move to /system/app with a root explorer.
Click to expand...
Click to collapse
Alright will do, thanks
wilkyyyy said:
Either push to system/app with adb or put on sd card and move to /system/app with a root explorer.
Click to expand...
Click to collapse
why? i can't install it either? we should make it into a zip file
also root explorer will require permissions no?
hamdir said:
why? i can't install it either? we should make it into a zip file
also root explorer will require permissions no?
Click to expand...
Click to collapse
Will make a zip now
Tested it out with Sonic thd and Dead trigger, it's working very nicely. Battery reaching up to 55C was fine right? Hit 52 degrees playing sonic, which btw is playing better than ever with the gpu overclocked and this app
Things like this make me really happy to have gotten a one x, by that I mean the things people such as you and Hamdir do, no way I would find that on another device
Nice work mate ... Will test it . ..
Well done Willkyy. Will test this soon, and see which values you use. Do you use the same ones, as which hamdir used in his latest scripts?
timlambo said:
Well done Willkyy. Will test this soon, and see which values you use. Do you use the same ones, as which hamdir used in his latest scripts?
Click to expand...
Click to collapse
I do indeed!
timlambo said:
Well done Willkyy. Will test this soon, and see which values you use. Do you use the same ones, as which hamdir used in his latest scripts?
Click to expand...
Click to collapse
My values for faux 004b6 for now
Soon wilkyyy will make versions for specific kernels, but this will do for now he is going on his well deserved holiday
wilkyyyy let me know if i can assist in that process
wilkyyyy said:
Either push to system/app with adb or put on sd card and move to /system/app with a root explorer.
Click to expand...
Click to collapse
You need to sign the app bro, then it can be installed how ever. Also maybe get your self a private sign key so you can upload it to google play for updates
Sent from my HTC One X using xda premium
rayford85 said:
You need to sign the app bro, then it can be installed how ever. Also maybe get your self a private sign key so you can upload it to google play for updates
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im sure i signed it will try it now and test
playstore upload would be awesome
Thx wilkyyyy,
no problems with installing.
Just pushed the file as told nice one!
Obviously the HOX heats up a bit more but is to be expected.
Thx to hamdir and henk2484 here too!
Sent from my HTC One X using latest faux kernel and viperX Rom
The app should also explain that it's for the Tegra 3 One X

Leankernel: ( JB4.2 - 7.1, JB4.3 - 8.3 - , KK 9.0 beta 11/25)

Ok guys i have got permission to bring over lean kernel and offer support for it on xda. I will keep this post up todate with all the most recent kernel updates and news. All credit goes to imoseyon as the original op and rootzwiki for original posting. I am posting this with full permission and support from imoseyon
Mod Type:: Kernel
Difficulty:: Very Easy
Mod Status:: Stable
Apply In:: CWM Recovery
Requires Root:: Yes
Exp builds are also up and includes a bunch of Android/OMAP updates not in stable.
SOURCE:
ICS
JB
This is a minimalistic Galaxy Nexus kernel. My philosophy is to keep the kernel as lean and stable as possible, at the same time to keep the kernel as modern and close to latest mainstream linux as possible. You will see that my kernels will lack some of the bells and whistles from other kernels.
sorry host4droid is still down. Mirrors:
kk4.4 LK 9.0 beta (use at ur own risk)
JB4.3 [ stable builds | exp builds ] [ change log | exp changes ]
JB4.2:Stable
Stock JRN84D kernel
Terminal Emulator not finding scripts? Read this post.
CHANGE LOG JB 4.2
FEATURES
Patched to latest in Linux 3.0.x branch.
All unnecessary kernel components removed to make kernel lean and fast!
OC to 1.65ghz. Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
User voltage control
InteractiveX V2 (screen-off hotplug of cpu1) added. Select it using setcpu if you want to use it.
Ramdisk tweaks (sysctl, vm, filesystem speed, etc.)
SWAP & zram (next generation compcache) support. Run "zram enable" in terminal.
init.d support in ramdisk.
lk.conf for basic kernel configuration.
HotplugX governor (Hotplug optimized and modified for screen-off suspend).
wakelock tweaks for wlan and lte modem
lkflash - script to flash latest versions of leanKernel from Terminal (type "su" without quotes, hit enter, then type "lkflash" without quotes and then hit enter)
checkv - voltage checking script (for custom undervolting) - detailed at bottom of this post.
checkt - script that displays 1) your current temp, 2) # of times you were throttled due to temp "recently", 3) CPU trim type, and 4) CPU silicon type, etc.
Fast USB charge (by chad0982) and "ffc" toggle script by me. (Open terminal, and type "ffc" without quotes then enter)
ColorControl from both CM9 and Ezekeel (compatible with all ROMs). Helpful posts: 1and 2.
TempControl - sysfs interface to control the CPU temp threshold. Read these two posts: 1 and 2.
Variable GPU OC - sysfs interface to select GPU max speed between 307MHz (stock), 384MHz and 512Mhz. The changes take effect immediately. Check FAQ for more info and how to use it.
Custom SR Tuning - override kernel default minimum voltage for SR calibration.
SoundControl
Gamma Control
ROW scheduler v4
DIRECTIONS
Uh.... flash the zip in clockworkmod.
Thanks to forum member maddler for providing file hosting
FAQ
How do i change voltage? - Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.
Do i need to wipe dalvik/cache? - in general there's no need, but it doesn't hurt so if you have time go ahead. Posted Image I don't wipe.
​Can we OC higher or add more frequency slots? - You can find the extra slots in my experimental versions.
​Will this work on GSM gnexus as well? - It should. I don't have a GSM phone to test so let me know if it stops working.
What is interactiveX V2? Read this post and thttp://rootzwiki.com/topic/13092-kernel-leankernel-minimalistic-kernel-120-123111/page__view__findpost__p__342571
Are you getting Screen-Off/Sleep-Of Death (SOD), general instability, or unusual battery drain?
Before you post here (especially if you're running the experimental version), try the following steps in order:
0) dude, disable screen-off profiles if you're running interactiveX.
1) If you're running the experimental version, do you have 180mhz/230mhz and/or 1.42ghz slots enabled? If so disable them both!
2) If the above doesn't help, do you have custom undervolting enabled? If so disable it! (keep in mind that the kernel is already undervolted by default).
3) If the above doesn't help, are you using interactiveX or hotplug governors? If so change to interactive.
4) If the above doesn't help then you should not be running the experimental version. Install the stable version and try both interactiveX and interactive without custom undervolting.
If you're still getting SOD with stable/interactive, report it here.
What about call-recording? - First the app needs to support Galaxy Nexus. Find out if it does and then find out from the author of the app what kernel changes are required and let me know.
Should i set up screen-off profile? - ICS kernels have built-in screen-off profile for all governors at 700mhz. So you don't need it unless you want to set it lower than 700mhz. In general there isn't a whole lot to gain by setting it lower.
Hotplug vs interactiveX? - Read this post. HotplugX vs interactiveX
What is zram and why do i need it?
zram basically takes a portion of your RAM (10% using my script) and turns it into a compressed swap device. So in layman's terms you're extending the size of your memory (potentially from ~700mb to close to 1000mb depending on the compression ratio).
To answer the 2nd question, no you don't really need it but if used properly (using custom LK zram script) it could help you in two different ways:
1) Android OS is based on Linux OS and the OS will try to use a growing portion of your RAM for file and inode caches and if you keep your phone up without rebooting after a while you may notice things getting a little sluggish. That's because the OS is not doing a good job in dropping the caches and freeing up memory for the apps.
2) more RAM and tweaked minfree (also handled by custom LK script) could potentially allow your apps to stay in memory longer (this may or may not be desirable based on your preference of course).
In conclusion, I'd say if you're curious it doesn't hurt to try. To revert, just type "zram disable".
What's the low-down on the GPU OC?
My kernel's GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. My kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.
Why are the IO benchmark test scores lower than another kernel?
Some of the kernels out there have fsync disabled to increase benchmark scores. I believe that is unsafe and could cause data corruption. I do have hooks in my kernel to disable it but I don't use it.
In real world there will not be any user perceivable difference whether you have fsync enabled or disabled.
Is there a way to tune hotplug via sysfs?
yes. Advanced users only!
My phone doesn't seem to be deep-sleeping, what gives?
(assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.
I'm having unusual battery drain - help!
First of all, our gnex has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.
I'm having unusual battery drain while screen is off, or phone is sleeping - help!
First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.
I'm having unusual battery drain while phone is in deep-sleep - help!
First make sure you are absolutely positive that deep sleep is working (read the previous question).
While on my kernel *and* connected to Wifi, you shouldn't drain more than 1% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 1-3% per hour, depending on signal strength.
tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
tip 3: http://checkthis.com/d87t
If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.
What is tempcontrol and how do I use it?
First, read these two posts: 1 and 2.
Although tempcontrol was designed to be used with the experimental notrim builds because the cpu gets hotter in notrim frequencies, you can actually use tempcontrol to throttle lower frequencies. I haven't tried myself, but theoretically you can set your top speed at say 1.2Ghz and use tempcontrol to throttle at say 60C (instead of the stock value of 63C) resulting in slightly cooler phone. Theoretically.
What is SmartReflex?
SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
My stable and experimental builds will have SR Class 1.5 enabled by default.
You can disable SR via sysfs
How do I use Variable GPU OC?
You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
307Mhz (stock) is set default by the kernel.
Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
for 384MHz: oc gpu 1
for 512Mhz: oc gpu 2
What are the available sysfs options?
Check this post (thx byrong)
Which governor should I use on JB?
As usual I'd recommend trying all the governors and see which one works best for you. Stock JB, however, is optimized for interactive. The OS will automatically modify various interactive governor parameters on the fly while you're using the phone as part of "project butter". Namely, the following parameters are constantly adjusted by the OS: boostpulse, timer_rate, min_sample_time, hispeed_freq, go_hispeed_load, and above_hispeed_delay.
I hope this helps people if there is any other information you might want added just ask and i will do my best to come up with a comprehensive guide.
Donate to your favorite charity, or donate to imoseyon.
Did you ask Imoseyon before you posted this?
Thanks for bringing the thread over to XDA. Hopefully you got the necessary permissions, for the sake a peaceful thread. Its good to have most developments of the GNEX here and I finger tip away.
Sent from my Galaxy Nexus using xda premium
I've heard a lot about this kernel!
yes this is with his permisson
ajf64 said:
No i didn't ask him but i did put all due credits in it and it is in every other gnex forum but the sprint one all brought over by other people so if he has a problem with this he can feel free to pm me and i will get it removed i just figured it give us some easier access to his great kernel. In no way am i claiming this to be my work all support should be directed at the original thread op. I was just trying to make access to his kernel a bit easier for all xda users
Click to expand...
Click to collapse
That's all hunky dory but just doing things without asking the developer is just not right. Regardless if he has an issue or not. Its like you make something you work diligently on and then somebody just posts it somewhere else.
I dunno maybe its just me but its just common courtesy.
Sent From My Toro+ via SkyBlue Tapatalk
Thanks op.
#inb4close
#ReOpened
Sent from my Galaxy Nexus using Tapatalk 2
all fixed
ajf64 said:
well then sorry for posting it will a mod please delete this thread before it becomes a flame pit
Click to expand...
Click to collapse
Doesnt need to be deleted.. if just ask him if its alright.. thats fine enough
ÜBER™ said:
Doesnt need to be deleted.. if just ask him if its alright.. thats fine enough
Click to expand...
Click to collapse
Why do you always ruin the flaming? With your...good nature...and your rap music.
Thanks for linking. You can still ask dev for permission but I get what you're trying to do. I prefer xda since this is where I have gotten help with every phone since my nexus 1.
Sent from my Galaxy Nexus using XDA Premium HD app
Well i have gotten permission to post this from imoseyon and to keep this thread updated on xda sprint forums for him so it looks like we are all set he got back to me alot faster then i thought he would so every thing should be all good guys
and yes jayare313 i am so used to finding every thing i need on xda some times it s a pain having to check 3 or 4 sites to see if any of your mods for your rom are updated
Sorry. 3 issues here:
1) I need to verify permission from the developer and he needs to verify that he is going to support it here. If someone downloads it, flashes it, and somethings wrong.......who is going to give answers and support it? We have an active community who can help, sure, but the developer has to actively support it here. If he were ready to give support here, he would have posted it here already. And even then it would have to go in general unless he started the thread.
2) There is no source provided in the OP. Kernels must be GPL compliant and listed in the OP.
3) If you did not create it, do not post it in the development section.
Alrighty. Everything should be good now. I'll be keeping an eye out.
OP will be updated soon, with source and I've spoken to the developer.
Thank you guys.
---Jay--- From the GNex
Well, I will say I like having this thread here. So thanks to the op.
Sent from my Galaxy Nexus using Tapatalk 2
I will be updating the thread when i get home today and be offering any support you guys may need for this kernel
MichaelMcEntire said:
Well, I will say I like having this thread here. So thanks to the op.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I totally agree. Thanks to OP for the thread and imoseyon for the kernel
Sent from my Galaxy Nexus using xda premium
Np guys any time and if there is any thing i can help with just ask i plan to provide full support for this kernel. Also if there are things you wish to have added feel free to post them as well i have permission to compile my own versions of lean kernel with cherry picked features from his repository and to add features to it. I look forward to your feedback.
is 4.2 jb cm10 compatible
twoeleven99 said:
is 4.2 jb cm10 compatible
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda app-developers app

KT-SGS6E [Kernel] Builds [Discussion] [G92X] [TW 5.0] ★KTWEAKER SHOP★

ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR HIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.​
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS6E kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and find which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S6 & S6 EDGE users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED {G92X} users
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for TEST PROFILES
If at any given time you aren't already on the kernel and Ktoonsez hasn't updated his links, there'll be no need to flash previous builds when you want to receive OTA's as ALL posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***​
If you encounter any suspicious issues when updating the kernel, follow my recommended procedure for the best possible results:
1) Backup current Ktweaker settings
2) Open any root browser (make sure it's mounted as r/w) then navigate to /system/app/ and delete the Ktweaker and KTmoniter apk's
3) Navigate to your sdcard and delete the Ktweaker folder OR rename it by adding a ".bak" extension without the quotes.
4) {Optional} Clear all Superuser logs
5) Reboot Recovery
6) Flash kernel
7) Reboot
8) Copy any saved profiles back into /sdcard/Ktweaker/Profiles/
9) Restore Ktweaker settings
10) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
**********G92X**********​
KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G920W8 and G925F and G925I and G925S and G925T and G925W8
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/Yo6i7SqAQS8zsAmg
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758
{
"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"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and Ktoonsez. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S6 and S6 EDGE users with their personal needs in mind as it's pretty clear not everyone favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future profiles will be added here for sharing and discussion. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their role and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles per project. Make your selections based on your usage needs and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel.
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and "About" file. The "Adjustments" file is just a simplified view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to "/sdcard/KTweaker/Profiles" using a file Manager of your choice.
3. Open the Ktweaker app and click on the "Profiles" setting at the top of the slider drawer OR scroll to the bottom and select "Profiles & Scripts" then click "Restore Profile from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply and confirm.
5. Make sure the "Set options on boot" setting at the top of the slider drawer shows a little green boot icon below it, indicating the settings will be applied upon reboot.
6. Profit!
IMPORTANT: Be sure to ALWAYS load your stock voltage table on BOTH CPU clusters IMMEDIATELY after applying a profile as most of these are based on an ASV10 CPU and may result in reboots!!!
1) Apply the profile
2) Quickly go to the CPU voltage for cluster 0 and click "more" and load default voltages, then click apply.
3) NOW go to the CPU voltage for cluster 1 and click "more" and load default voltages, then click apply.
4) Done!
​
Conservative​
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
Coming soon....
Bless The Child
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
coming soon...
Dead By April
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further with it's heavy underclocking as well as it's higher thresholds and online blocks to prevent other cores from coming online too soon. Although It focuses very little on performance it manages to maintain a fairly smooth interface for your average daily use.
https://copy.com/oFLHg4ZG2MyvRzrq
Balanced​
Balanced Bull v1
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and is a profile designed for my own personal usage pattern. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/SKdHYHskn1NgLitp
ECLIPSE
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
coming soon
Ktoonsified v1
These settings are my settings, This is a performance oriented option in which also offers a great deal of battery life. YOU WILL NEED TO LOAD YOUR STOCK VOLTAGE TABLE THOUGH since there are 16 different bins of CPUs!!!
Click to expand...
Click to collapse
https://copy.com/COP9WtEfLzTudZ2F
Ktoonsified {MOD}
This mod is intended to work as an alternative to the original Ktoonsified profile. It's specifically for the users experiencing issues such as screen wake and incoming call delays and media stutters on Ktoonsified v1 . Use this profile to repair most if not all of these issues.
NOTE: The adjustments text file will show you the few changes I've made from the original Ktoonsified profile.
https://copy.com/2bcvnievx8suWohD
SmoothManic v1
This profile was put together by none other than the BOSS himself, @ktoonsez!
The idea with this is to get the CPU really high on 2 cores when screen is touched and then bring them both back down really quick so UI is super smooth but don't kill the battery by hanging out at that high Mhz step.
Click to expand...
Click to collapse
https://copy.com/mgoNzpgrYn7TkLZO
Undisputed
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
coming soon
Performance​
Feed The Machine
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
coming soon
From Ashes To New
This is a straight performance profile. It's similar to Feed The Machine and Rebirthing in the sense that it syncs the cores to the boosted frequency on touch and almost instantaneously jumps right back down to 300MHz. The difference between the profiles is that this one makes better use of all the cores. However, due to the rapid scale down I think most people will find battery life to be surprisingly good for this type of profile
coming soon
KTGaming v1
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/VwSaksMPwJGCfCux
SmoothGaming v1
This profile is based on SmoothManiac v1 but with performance enhancenents to provide a much smoother gaming experience while hotplugging is active. Some of these enhancements include a much higher sampling interval as well as offline blocks to allow frequencies to scale and hotplug at a more reasonable pace.
NOTE: The adjustments file will show you the changes I've made to SmoothManiac v1.
https://copy.com/zI4c1TovjavAQBtI
Projects​
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing" Like "Comatose" it uses a fairly high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu as "Comatose" but ALL profiles run at stock 2457Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage, consuming even less when a specific task has completed and immediately dropping the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
coming soon
If you'd like to contribute to the Ktweaker Shop all you need to do is post the profile you'd like to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev so he can add the profile to the Shop in Ktweaker!
Useful Links​
Information about profiles can be found HERE
Interested in learning how to fine tune this kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
Ktoonservativeq governor adjustments explained HERE
Reserved
Reserved..
just in case
Are the Same
LuigiBull23 said:
**********T-MOBILE**********​
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/NGddRACV6Nm1xulA
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758
Click to expand...
Click to collapse
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.
fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
+1. Let us know if it works especially the sim unlock. Thanks
what worst?
LuigiBull23 said:
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.
Click to expand...
Click to collapse
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?
fabioplata said:
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?
Click to expand...
Click to collapse
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.
dont work
LuigiBull23 said:
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.
Click to expand...
Click to collapse
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
Attempt to boot into recovery and wipe your data.
fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
just press power+volume down and it will restart
thanks
batillojr said:
just press power+volume down and it will restart
Click to expand...
Click to collapse
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:
fabioplata said:
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:
Click to expand...
Click to collapse
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist
I can't
batillojr said:
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist
Click to expand...
Click to collapse
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.
fabioplata said:
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.
Click to expand...
Click to collapse
Ya se, estamos en una situacion muy dificil , ojala que exista una solucion pronto.. por mientras seguire usando mi nexus6
Very awesome
Good thread dude, loaded some of these on to my phone

[Oct 31] [Machinex][MarkOneHundred][KERNEL][TW][5.0.1][I9505]

Machinex
MarkOneHundred
Sheer will .
This is machinex.
This is machinex. I have been working on this kernel for over a year now, and am finally comfortable with its release to the public. This kernel builds on the great work of those who have made this device the powerhouse that it is. There are elements here that you have experienced on every GS4 kernel to date, as well as other devices.
The goal I had for this project was upstreaming/updating/experimentally upgrading as much as I possibly could. I have done so, and will continue to do so.
This kernel is ONLY for TW-based, 5.0.1 roms for the I9505!!! NO I WILL NOT DEVELOP FOR DEVICES I DO NOT OWN, SAVE YOUR BREATH!
OBLIGATORY DISCLAIMER:
THIS KERNEL COULD VERY WELL DESTROY YOUR PHONE, YOUR LIFE, YOUR MARRIAGE, Etc. YOU INSTALL AT YOUR OWN RISK!! XDA AND I ACCEPT NO LIABILITY FOR YOUR DECISION TO USE THIS KERNEL!!For noobs: assume that installing this kernel will cause your phone to grow arms and punch you in the face.
PLEASE READ AND UNDERSTAND THIS OP BEFORE LEAVING USELESS "IT DOESN'T WORK" COMMENTS!
Issues that aren't answered here will be dealt with on a case-by-case basis.
SEE POST #2 FOR UPDATES, CHANGELOGS, and FIXES
SEE POST #3 FOR BATTERY/PERFORMANCE INFO
SEE POST #4 FOR A SHORT SYNAPSE BRIEFING
LOGS OR IT DIDN'T HAPPEN! Context helps too. What were your Synapse Settings?
KNOWN ISSUES Wifi issue is fixed! After a fresh rom install, all you need to do is reboot and the appropriate files are created in /data enjoy! HOTSPOT IS FIXED!!!! Finally! I AM AWARE OF AND WORKING ON LOCKSCREEN PIN BUGS!!
FEATURES:
- Linux 3.4.113 + a LOT of upstreamed subsystem code.
- Automatic Busybox Installation, Version 1.25.1.
- Cpufreq core backported ENTIRELY from mainline 4.13. All Cores operate independantly. Their governors and tunables can all be different.
- Govorners: Due to a highly upstreamed cpufreq core api, not many custom governors for now except for Interactive, Intelliactive, and the *NEW* Schedutil governor, described in the documentation like so:
The "schedutil" governor aims at better integration with the Linux
kernel scheduler. Load estimation is achieved through the scheduler's
Per-Entity Load Tracking (PELT) mechanism, which also provides
information about the recent load [1]. This governor currently does
load based DVFS only for tasks managed by CFS. RT and DL scheduler tasks
are always run at the highest frequency. Unlike all the other
governors, the code is located under the kernel/sched/ directory.
Sysfs files:
* rate_limit_us:
This contains a value in microseconds. The governor waits for
rate_limit_us time before reevaluating the load again, after it has
evaluated the load once.
For a great, comprehensive blog regarding the specifics of each governor, as well as the settings found below, please check out the link I've referenced in post #3.
- HARDLIMIT and THERMAL: Incorporated Yank555's CPU Limiting solution, Hardlimit. ALL hardlimits, cpu boost limits, and thermal limits are now PER CORE. I have included it directly in the core cpufreq code, and it is the primary controller for THERMAL, INPUT BOOST and user controlled hardlimits. Thermal overrides both user-selected and input-boost limits, and you can monitor the limiting in real time. Also, the thermal driver now accounts for each core's temperature, and saves time/lock-contention by skipping core control if the temps are below the frequency limiting value.
-CPU HARDPLUG: A driver I built that hooks into the main cpu hotplug API and allows you to disable any core you want, configurable for screen on/off.
- Hotplugs: MX Hotplug, personally built from scratch and uses a real-time kthread for its calculation work. Intelliplug 15.8 (Personally Updated), Alucard Hotplug, MSM_sleeper, Lazyplug, Blu Plug, and Bricked hotplug.
Hotplug Notes: I changed the names of certain functions in the Alucard and MSM Sleeper hotplugs, so that their tunables could be streamlined in Synapse. Synapse is cleaner and simpler than ever, but if you use a third party app, Alucard and MSM Sleeper's max cores and max cores during suspend settings will not be tunable. So anyone who uses a third party app with this kernel let me know and I'll devise a workaround. Mpdecision removed entirely. The "mpdecision" in our sysfs is actually bricked hotplug.
-GPU:Machinactive, Interactive, Conservative, Ondemand, Performance and Powersave GPU Governors, GPU touchboost (fixed suspend issue), ability to lock the min/max freqs, and more!
-Updated version of fauxsound (5.4) (flar2, alesaiko, me). I limited the options in the code to the 4 controls that actually work for our device, and you'll notice a significant stability improvement. Slimbus:Golden-ratio-based operation is pristine. Sound quality is hardware-perfected. The version number is largely arbitrary and I increment when I make any significant improvements. NO MORE USERSPACE CALCULATIONS NEEDED!!!
-A gamot of colour, brightness, and panel options that I frankly didn't think would be feasible for our device, but it's working! MDNIE HIJACK selection, KCAL, and Cyanogen's generic PCC colour control are implemented in Synapse. Note that MDNIE/KCAL stuff is a battery thief, and I've not tested PCC colour control enough for power consumption to give you a definitive statement on it. Note: PCC values are from 1000 (safety limit) to 32768 (or a number close to that), meaning your tuning control is as FINELY GRAINED as possible for this device. I can't believe Synapse actually supports its ridiculous number of steps (and well, I might add). Faux's generic "colour control presets' are in there and they actually work! The stock colours much more vivid, and lower brightness settings benefit from them as I have modified top brightness to my liking.
-HBM:Qualcomm High Brightness Mode: unlocked! This can be controlled via a checkbox in Synapse, but you can also use flar2's HBM widget from the play store. I tried it before and HBM would flicker, but i pulled off a VERY hacky way of making it userspace controllable. Be careful! Though it doesn't seem to drain the battery or overheat the device, it's purely experimental and could cause Chuck Norris to come to your house and personally smash your phone. Now SEPARATE from autobrightness! "SCREEN FLICKER FIX" on PAGE 2
- Completely upstreamed and overhauled cpu, power, scheduling...you name it. Updated Powersuspend to the point where I had to rename it, because it is now closely integrated with the core suspend/power api. Introducing: Prometheus. The driver now calls suspend directly when you turn the screen off, unless a) music is playing, b) the phone is plugged in or c) you choose to disable the feature.
-All the TCPIP tweaks etc, updates to random/frandom, android-specific autogrouping, limited but significant LMK/OOM updates.
-BACKPORTED "codel" fair-queueing net-scheduler, for a faster/more consistent networking experience.
-persistent ram, kexec-support, fast-charge, etc. Drop Caches button in Synapse is useful.
-Utilizing Qualcomm's built-in QRNGD (qualcomm random number generator daemon) with randomness optimized in the kernel = entropy for days.
-BOOTLOADER: Officially only 5.0.1 Bootloaders are supported. Unofficially, someone tried it with a KK bootloader and it worked fine for him so what do I know?
-COMPLETE Synapse support. Download, update, AND install Busybox On Rails from the PlayStore before you install the kernel for best compatibility and support. UPDATE: FULL Busybox installation is now included in machinex installer script. If you have any issues, still feel free to install Busybox on Rails. Upon kernel installation, you'll find Synapse installed in your system apps. If you want to get rid of it, just remove it from /system/priv-app with your file manager.
-CPU and GPU VOLTAGE Control: Both in Synapse. I DO NOT SUPPORT ISSUES IF YOU CHANGE VOLTAGE. YOU ARE ON YOUR OWN.
MENTIONS:
To those listed here, I cannot express how grateful I am for your assistence, patience, and kindness towards me as I badgered you throughout my journey. Though saying "thank you" doesn't feel like enough, thank you all. If I missed someone here, please tell me.
Thankyou:
friedrich420
Slim80
Tkkg1994
flar2
osm0sis
alesaiko
HybridMax
Kushan
Alucard24
Ausdim
Ktoonsez
neobuddy89
javelinanddart
Andreilux
theHacker911
UpInTheAir
Pafcholini
Placiano
Dorimanx
faux123 (seriously like the godfather of s4 kernel hax)
jcadduono
FransiscoFranco
Cyanogen
Meticulus
Eliminator74
Matthew-333 (moonshine kernel)
klabit87
apbaxel
yank555
ion-storm
yseras
PDesireAudio
lsswizard
arter97
Grarek
mrg666
showp1984
gsstudios
Lord Boeffla (andip)
Chainfire
TeamTrickster
tommygreenus
Andycar (For being the best bloody coding buddy I could ask for)
The Machinex Testing Team! - AMAZING folks, just amazing.
My Awesome Testers from this thread.
Again, I'm sure there's tons more.
On to the fun part then
INSTALLATION INSTRUCTIONS:More importantly, the uninstallation instructions. The install pretty much takes care of itself.
There are two links below that you must download in order to safely have an install/uninstall solution for this kernel. The one labelled "machinex-MarkOneHundred.zip" is the kernel. UPDATE: Busybox On Rails isn't required anymore. The second zip is crucial for uninstalling, aptly named "machinex-uninstaller-Jan12.zip." When this kernel is installed (and everytime it boots), it will rename mpdecision, thermald, thermal-engine, and power.default.so with an appended "-bak" suffix, because they all interfere with the updated power/cpu code in the kernel. If you switch to a different kernel, I INSIST that you flash the uninstaller (or take a look at the scripts yourself and do the stuff manually). ATTENTION: SLIM80'S KERNEL CLEANING SCRIPT IS NO LONGER NECESSARY WHEN FLASHING THIS KERNEL!!!!!! I HAVE INTEGRATED MY OWN CLEANUP PROCESS IN THE INSTALLER!!!!!!!!!!
TLDR: NO NEED FOR BUSYBOX ON RAILS, flash zip. use uninstaller zip to uninstall.
DOWNLOADS:
!!!JANUARY 12, 2017:UPDATE!! NEW UNINSTALLER for EVERY VERSION!!!!
DO NOT MIRROR THESE ELSEWHERE. DO NOT INCLUDE THEM IN YOUR ROM WITHOUT ASKING MY PERMISSION FIRST. I AM HAPPY TO COLLABORATE, NOT TO BE ON THE RECEIVING END OF BUG REPORTS CAUSED BY THIRD PARTY DOWNLOADERS.
UNINSTALLER-JAN12: https://www.androidfilehost.com/?fid=385035244224412313
md5: 295ac70bbb17ad2e5dc59e4ca1288e79
MarkOneHundred
INSTALLER: https://www.androidfilehost.com/?fid=745849072291685412
md5: 03af9cfc399d3eda3141254291668563
SOURCE: https://www.github.com/robcore/machinex
(be gentle on my ridiculous commit history, my git skills are shoddy at best).
So keep in mind this a development thread, blah blah blah, but if we all have good discussions (let's TRY to keep it on topic), I'm more than happy to have some fellow nerd friends to talk about my passion with. Heck, I want to use this thread as a chance to meet some other developers who wanna work on stuff together, exchange ideas, learn, and teach me how to get better at git.
Enjoy!
XDA:DevDB Information
Machinex, Kernel for the Samsung Galaxy S4
Contributors
robcore
Source Code: https://www.github.com/robcore/machinex
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: MarkOneHundred
Stable Release Date: 2017-10-31
Created 2016-09-05
Last Updated 2017-10-31
Reserved
UPDATES NOTICE:
Reset your fuelguage (in Synapse) after every install! WIping your cache and dalvik-cache can be helpful for stubborn apps, as well as wiping the cache of any specific app giving you trouble!
-------------------------------------------------------------------------
UPDATES - MarkOneHundred - October 31, 2017
CHANGELOG:
- Updated memory management to roughly linux 4.4.
- Modified Cpufreq in various ways. Per-Cpu frequency touchboost, per-cpu thermal core tracking and limiting, and governors can now be changed if a cpu core is offline. The governor selected will be applied to the core once it comes back online.
- Implemented Omniboost, a generic touchboost interface that can be used for any driver, so long as driver has an external function that the booster can use.
- Built a new hotplug driver from scratch, mx_hotplug. The driver chooses to on/offline cores based on a combination of system load and current number of scheduler requests (and touch of course). What separates this hotplug driver from others is that it uses a real-time kthread in order to give it an "interactive" type calculation.
- Speaking of which, found and fixed the issues with google's most recent interactive governor, and have added it back. Due to it working perfectly now, I forward-ported Intelliactive as well.
- Updated Hardplug to be more efficient.
- Built a little userspace hotplug driver from scratch for those who just need manual core adjustments.
- Tons of other little fixes and updates, to the kernel itself and to Synapse. Please explore around Synapse for some of the updated features.
- Found and fixed any of the user reported bugs i could.
- Continued with the various core updates to 4.14.
- Updated to my own toolchain, 7.1.1 hardfloat, cortex-A15 optimized (it is similiar enough to krait to give us an edge).
- I will update this if i think of anything else.
Sticky: Kernel base is now pretty much somewhere between 3.16-3.18, however I will keep the versioning at 3.4 for certain functions that depend on kernel_version conditionals. Wifi hotspot disconnect issue still persists, but i'd like to think that one day it will be solved...
Can be found in MachineX Rom by the awesome @Andycar found here: https://forum.xda-developers.com/ga...m-machinex-debloated-nogapps-s6-apps-t3573009
See my poorly formatted wiki for older updates:
https://github.com/robcore/machinex/wiki
-----------------------------------------------------------------------
LOGS
In Synapse, under 'LOGS AND PROFILES,' you will find a button that says ALL LOGS. Please press this button IMMEDIATELY after a bug appears that you would like to report, or after a boot if you get a kernel panic (RR).
From now on, without these logs present, I am no longer able to respond to the issues brought up by users.
FIXES
The following fixes involve sqlite and the "Setting Storage" application, also known as Settings Provider, or "com.android.providers.settings package" You will be working with a file named settings.db, and the 'system' table within.
Synapse Cancelled Fix: Get rid of the init.d scripts that are conflicting with UCI service startup. Also check the SuperSU section below...
Sound Fix: Either don't use an audio mod, or don't use Faux Sound Engine. That's all she wrote.
ScreenFlickerFix: Using an SQLITE DB Editor of your choice (from playstore), navigate to the "system" table and change values for "dim_screen" and "intelligent_screen_mode" to 0. *UPDATE* NOW AVAILABLE IN SYNAPSE UNDER THE "EXTRAS TAB"
ChargingTweak: Same as above but change "adaptive_fast_charging" to 0. This is only IF you are having issues which kernel driver-level fast charge. *UPDATE* NOW AVAILABLE IN SYNAPSE UNDER THE "EXTRAS TAB"
MASSIVE THANKYOU to @Andycar for making the above two fixes possible via Synapse!
SuperSU: I'm seeing a lot of permisison errors. Make sure, when using custom roms and kernels, that SuperSU is set to be as permissive as possible so you don't get knox blocked. Here are the crucial settings:
- ENABLE SU during boot
- DISABLE (untick) Mount namespaces separation
- Install SuperSU into /system
- ENABLE Trust System User
- Though I know many have security issues with the idea of allowing apps by default, doing so will make your experience way faster and provide you with less interuptions. At the very least I would set allow by default for Synapse.
These SU settings are kinda par for the course when it comes to android modding.
build.prop: Here is a list of property removals/changes recommended for our device:
REMOVE(lines containing):
ANYTHING with "fps/FPS" in it.
persist.sys.NV_FPSLIMIT
persist.sys.NV_POWERMODE
persist.sys.NV_PROFVER
persist.sys.NV_STEREOCTR
persist.sys.NV_STEREOSEPCHG
persist.sys.NV_STEREOSEP
persist.af.resampler.quality
af.resample
persist.af.resample
ro.telephony.default_network
telephony.lteOnCdmaDevice
dalvik.vm.dexopt-flags
ro.media.enc.jpeg.quality
ro.media.enc.hprof.vid.fps
ro.ril.power_collapse
ro.ril.sensor.sleep.control
pm.sleep_mode
power.saving.mode
persist.cust.tel.eons
persist.sys.dalvik.hyperthreading
boot.fps
shutdown.fps
debug.egl.profiler
hw2d.force
hw3d.force
video.accelerate.hw
debug.mdpcomp.maxlayer
debug.egl.buffercount
debug.enabletr
ro.hwui.renderer.disable_opaque
persist.sys.media.use-awesome (this is default anyway, and is controlled via the nuplayer checkbox in developer settings, so it's unneccesary)
CHANGE:
persist.sys.storage_preload=0 to persist.sys.storage_preload=1
tunnel.decode=false to tunnel.decode=true
af.resampler.quality=4 (or anything else) to af.resampler.quality=255
ro.config.dha_ils_enable=false to ro.config.dha_ils_enable=true
#ro.config.dha_cached_max=4 (remove the #)
#ro.config.dha_empty_max=36 (remove the #)
#ro.config.dha_lmk_scale=0.594 (remove the #)
sys.config.samp_spcm_enable=false to sys.config.samp_spcm_enable=true
sys.config.spcm_preload_enable=false to sys.config.spcm_preload_enable=true
ro.security.mdpp.ux=Disabled to ro.security.mdpp.ux=Enabled
For those having gaming issues, try removing them if you have them or adding them if you don't:
debug.performance.tuning=1
persist.sys.ui.hw=1
This might solve some issues for some folks.
---------------------------------------------------------------------------
INSTALLATION NOTE: Your first boot will probably take longer than usual, because this kernel makes significant (but safe, and auto-backed-up) changes to your core operating system.
This kernel includes drivers that TW has been compatible with since JB (I checked),
but didn't update the kernel drivers for (the best example of this is Autosleep). That said, there are userspace controllers like thermald and mpdecision (a binary linked to kernel code)
that interfere with custom governors, hotplug drivers, etc, so I've made the decision to back them up in the kernel script, and have them disabled while using this kernel.
The UNINSTALLER restores everything to the state it was in before flashing machinex, which is why I so strongly emphasize its use.
PERFORMANCE AND POWER-SAVING
Regarding the age-old performance/battery-life settings questions floating around, I'm gonna go ahead and suggest the following website created by a very dedicated fella who started out with the exact line of questioning, and built a genius guide for users of custom kernels. Heck, it's useful for developers too.
His username here is @gsstudios and he is a recognized developer here on XDA. Deserves it too
http://androidmodguide.blogspot.ca/
and on XDA:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
I encourage you to rate that thread 5 stars, as it is the most comprehensive guide to kernel tunables you ever did see.
Note that I *probably* don't incorporate feature requests, as I have enough on my plate with bringing up the subsystems to a point where I can call this a stable release thread. Don't like it? YOU try backporting linux 3.9 scheduling code to a Samsung 3.4 base
On that note, if anyone here is savvy regarding kernel, C and (not "or") git development, I welcome coding partners because working with a team means better quality, better time management, and a better chance of incorporating fancy tweaks.
Cheers.
SYNAPSE:
Synapse has a default "warning" that comes up the first time you open it.
{
"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"
}
The initial warning is just a bug in the app because it's just been installed.
It's a design flaw in the app itself.
Synapse bases its stability check on whether the device is rebooted within 2 mins of being turned on.
Synapse does this on first boot for every single kernel that uses it,
because it has no previous internal boot settings to base its decision on,
and also because the app expects saved defaults when none have been established yet.
It is nothing to worry about.
Untick the option in settings called "stability check" going forward.
Breathe.
Does it work?
I'm on imperium kernel on Thor s7 rom, I was wondering if your kernel works with m919, tmo gs4, I was looking forward to trying out your rom.
Thank you
-jeff
Hey Jeff,
The answer is...maybe/probably. I know that's probably not what you want to hear, but let me explain.
My device is actually an i337m (which is why i included it in the thread title), but I've been using the international kernels and roms without *major* issues ever since I've owned it. This is built from international sources, and it is running well on Albe's awesome 9.0 rom, so I imagine it will perform well for the ported/upgraded roms for our phones.
So if you've been using the international roms/kernels without problems, I see no reason why this wouldn't work for you other than the bugs/current issues listed in the op.
Sent from my GT-I9505 using XDA Forums
Can you create kernel for cm 13?
Wysłane z mojego GT-I9505 przy użyciu Tapatalka
Welcome to s4 community Bro.
Congratulations . Downloading. ......
Sounds nice bro, good Job! Try this Kernel later as soon as possible on my GT-I9505 with THOR S7 v1.5!
Sent from my SM-G935F using XDA-Developers mobile app
r2089 said:
Can you create kernel for cm 13?
Wysłane z mojego GT-I9505 przy użyciu Tapatalka
Click to expand...
Click to collapse
Sorry man, but CM is not on my list of priorities.
NAROUTO said:
Welcome to s4 community Bro.
Congratulations . Downloading. ......
Click to expand...
Click to collapse
Thanks! Though I've been around here for a while
xell75 said:
Sounds nice bro, good Job! Try this Kernel later as soon as possible on my GT-I9505 with THOR S7 v1.5!
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks! I hope you enjoy!
Everyone who uses this, feel free to provide feedback to help me assess what's needed for MarkTwo!
@robcore.
Im gonna try this to imperium rom v15.
So what is the best settings for more battery life ?
Playing clash of clans a few times a day browsing tapatalk and using youtube all day.
I want my device to run cool. Lol
Update:
Got a random reboot from the first initial setup.
==========
Will let it run for a couple of days with the preset default settings.
I will use my old 2600mah for now and later on swap my 7500mah once i get some good battery stats.
droidblitz said:
@robcore.
Im gonna try this to imperium rom v15.
So what is the best settings for more battery life ?
Playing clash of clans a few times a day browsing tapatalk and using youtube all day.
I want my device to run cool. Lol
Update:
Got a random reboot from the first initial setup.
Click to expand...
Click to collapse
Msm sleeper is a pretty sold hotplug for battery. I've noticed power efficient workqueues tend to slow things down/eat battery. Honestly I would try out msm sleeper for battery savings. Just note that games+youtube by design will eat into battery life. I will add some more power conscious governors soon. Also the usual stuff, the power your screen brightness the better, and turning off vibration/haptic will help.
robcore said:
Everyone who uses this, feel free to provide feedback to help me assess what's needed for MarkTwo!
Click to expand...
Click to collapse
I'm using this Kernel now on my GT-I9505 with THOR S7 v1.5 and so far a stable Kernel for me, many settings and alot settings I had never seen before as I like, very good! Just one thing til yet, Trying to set "Hellsactive" as CPU governor causes a freeze and a full reboot. Otherwise Kernel seems stable, using "Stockdemand" CPU Governor now. Keep going your work!
Sent from my SM-G935F using XDA-Developers mobile app
xell75 said:
I'm using this Kernel now on my GT-I9505 with THOR S7 v1.5 and so far a stable Kernel for me, many settings and alot settings I had never seen before as I like, very good! Just one thing til yet, Trying to set "Hellsactive" as CPU governor causes a freeze and a full reboot. Otherwise Kernel seems stable, using "Stockdemand" CPU Governor now. Keep going your work!
Click to expand...
Click to collapse
You know what, the interactive-based governors gave me trouble for the longest time. But I have found the issues in a great patchset, and am working on a fix that should be ready in a couple of hours. Until then EVERYONE STICK TO ONDEMAND-BASED GOVS!!!!
droidblitz said:
@robcore.
Im gonna try this to imperium rom v15.
So what is the best settings for more battery life ?
Playing clash of clans a few times a day browsing tapatalk and using youtube all day.
I want my device to run cool. Lol
Update:
Got a random reboot from the first initial setup.
==========
Will let it run for a couple of days with the preset default settings.
I will use my old 2600mah for now and later on swap my 7500mah once i get some good battery stats.
Click to expand...
Click to collapse
I'm guessing interactive based gov? If so, see my post above, MarkTwo is coming tonight.
robcore said:
You know what, the interactive-based governors gave me trouble for the longest time. But I have found the issues in a great patchset, and am working on a fix that should be ready in a couple of hours. Until then EVERYONE STICK TO ONDEMAND-BASED GOVS!!!!
Click to expand...
Click to collapse
Nice mate that's ok, thanks for the information! I'm looking forward for your new version!
Sent from my SM-G935F using XDA-Developers mobile app
xell75 said:
Nice mate that's ok, thanks for the information! I'm looking forward for your new version!
Click to expand...
Click to collapse
Dude thank YOU. I can't tell you how much I appreciate you and the others for testing this out and helping me iron out the remaining bugs, and being so understanding that "interactive based govs are broken" which is super embarrassing. Lol.
droidblitz said:
@robcore.
Im gonna try this to imperium rom v15.
So what is the best settings for more battery life ?
Playing clash of clans a few times a day browsing tapatalk and using youtube all day.
I want my device to run cool. Lol
Update:
Got a random reboot from the first initial setup.
==========
Will let it run for a couple of days with the preset default settings.
I will use my old 2600mah for now and later on swap my 7500mah once i get some good battery stats.
Click to expand...
Click to collapse
Update: simple gpu gov is snappy at stock settings and sooooo much better for battery consumption.
Also if memory serves me correctly, aren't you a cm kinda guy ; )
robcore said:
I'm guessing interactive based gov? If so, see my post above, MarkTwo is coming tonight.
Click to expand...
Click to collapse
Nope havent touched anything
There was a failed message when i booted the synapse app.
Something link kernel image failed but not sure should have taken a screencapture and the log.
Either way its working now.
robcore said:
Update: simple gpu gov is snappy at stock settings and sooooo much better for battery consumption.
Also if memory serves me correctly, aren't you a cm kinda guy ; )
Click to expand...
Click to collapse
More into like AOSP rom but had to use Tw for camera/video
I just noticed something.
My display colors somewhat changed? I think in a good way. Lol
simple gpu gov in marktwo?
droidblitz said:
Nope havent touched anything
There was a failed message when i booted the synapse app.
Something link kernel image failed but not sure should have taken a screencapture and the log.
Either way its working now.
More into like AOSP rom but had to use Tw for camera/video
I just noticed something.
My display colors somewhat changed? I think in a good way. Lol
simple gpu gov in marktwo?
Click to expand...
Click to collapse
Well it's great to see you here man! Lol with screen colour I made some fixes and changes to sammy's mdnie code. Upon checking the code against their roms, it turns out they've never bothered to fix discrepancies between the values in settings and the driver itself! "Standard" and "dynamic" have been switched this whole time. Also "auto" has been a placebo all along, they have had the backend in place all along but never initialized it in the list of available screen modes. On that note, for even cooler stuff check out the "video_mode" scenario in synapse. It's AWFUL for battery life, but sharpens everything to a crisp. I'm pretty sure kcal helped with color too(?).
As for simple gpu gov, works just fine on MarkOne! Franco's simplification to it made it a freakin' powerhouse while being better for battery somehow.
Building MarkTwo as we speak, then I'll test it and it's out! I'm working on the gov settings in synapse while building too. The tunable settings are ticking me off.

Categories

Resources