I wanted to share with you these two simples kernels based on the D85520P, I changed it just to implement the init.d support, for using it with stock rom. Of course, I also have Bumped them.
There are differents ways to proceed, and two points of possible inputs to activate init.d. This can indeed be done directly in the kernel, in ramdisk, or in the system.
For my part, to do this, I modified in two differents ways, the kernel D85520P (ramdisk), that I provide for those who are interested.
The first one uses run-parts, applet typically provided with busybox, and it therefore requires busybox installed on your system. Prioritize it, if you use a busybox that manages run-parts.
The second does not require any third party and will work without special prerequisites.
Both created, at the boot, if it does not exist, the init.d directory with the correct permissions (system/etc/init.d chmod 755).
Theses very simples kernel modificiations, are part of a project on which we work at our own pace, and for the fun, me and @jac10000 .
This unpretentious project will try to make a series of more or less customized , optimized, stock-based rom.
We called this series, our Stock EXperience (for) You (SEXY) ROM
That is why these two simples modified kernels have this name too
These kernels are only for using with pure stock rom:
They are in img format, and can be flashed with TWRP after selecting this format
Kernel D85520P bumped and with ramdisk implementing init.d using run-parts (busybox with run-parts is required):
https://www.androidfilehost.com/?fid=23991606952611236
or
Kernel D85520P bumped and with ramdisk implementing init.d without prerequisites:
https://www.androidfilehost.com/?fid=23991606952611243
in addition, our first version of the SEXY 20P rom can be found here (It doesn't contain init.d implementation nor other customisation, it's just the pure stock prerooted 20P with busybox):
Stock EXperience (for) You -- SEXY rom V1
and original 20P kernel just bumped, without any change:
https://www.androidfilehost.com/?fid=23991606952604603
UPDATE 05/30/15:
To satisfy a solicitation made to me (http://forum.xda-developers.com/showpost.php?p=61059947&postcount=4), I made two other versions which include setting permissive SELinux.
Two versions:
One including init.d with run-parts (requires busybox)
The other with no particular prerequisites.
Setting permissive SELinux is made in the ramdisk before init.d.
init-d with run-parts (for busybox users) and set permissive SELlinux:
https://www.androidfilehost.com/?fid=23991606952612236
md5: 2b068d36a0191df5af63eb90461f4297
init.d without particular prerequites and set permissive SELlinux:
https://www.androidfilehost.com/?fid=23991606952612230
md5: 091621d8fc0d1c494f3fd71321c20693
Thank's and credits:
@Chainfire for supersu
@Cloudyfa for his script sh supersu and busybox install and permission to use it.
@thecubed, @autoprime and codefire team pour bump!
@Skin1980 for his live bump @thecubed for his [Tool][python] LG Compressed KDZ Extractor
@cybojenix for his (system merger)
@bullghost for his windows GUI version KDZ and TOT Extractor
@osm0sis for his Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux]
Nice work my friend :good:
Nice! Good luck with development. Gonna try the rom when it's ready.
Plz feedback for life battery..tnx
jojobans said:
Plz feedback for life battery..tnx
Click to expand...
Click to collapse
m8, kernel is just released.
No one can give feedback with few hours of use.
you have to fully charge 1 or 2 times for conclusion
jojobans said:
Plz feedback for life battery..tnx
Click to expand...
Click to collapse
Also if you read his posts he said its a stock kernel with init.d support how battery could be different than stock kernel?
About SELinux permissive request:
http://forum.xda-developers.com/showpost.php?p=61058876&postcount=3
OP UPDATED:
To satisfy a solicitation made to me (http://forum.xda-developers.com/showpost.php?p=61059947&postcount=4), I made two other versions which include setting permissive SELinux.
Two versions:
One including init.d with run-parts (requires busybox)
The other with no particular prerequisites.
Setting permissive SELinux is made in the ramdisk before init.d.
init-d with run-parts (for busybox users) and set permissive SELlinux:
https://www.androidfilehost.com/?fid=23991606952612236
md5: 2b068d36a0191df5af63eb90461f4297
init.d without particular prerequites and set permissive SELlinux:
https://www.androidfilehost.com/?fid=23991606952612230
md5: 091621d8fc0d1c494f3fd71321c20693
Thank you... i searched for a Stock Kernel with only init.d support ... keep it up...
Stock kernel with permissive and init.d without any other tweaks..
Thank you, maybe this is what I need
How to install it? Need to flash via ADB?
dantezinn said:
How to install it? Need to flash via ADB?
Click to expand...
Click to collapse
What about reading the op?
Related
Here's the modified stock kernel from software ver 2.17.651.5, flashable through recovery, of course.
As of 1/13/12, CIQ back and front ends have been removed by HTC.
Includes init.d support.
Changelog:
8/21/11
On boot the following happens:
-Removes files from /data/system/dropbox
-Removes files from /data/system/appusagestats
-Removes files from /data/system/usagestats
-Removes files from /data/tombstones
-Modifies permissions on /data/system/dropbox to read-only
-Modifies permissions on /data/system/appusagestats to read-only
-Modifies permissions on /data/system/usagestats to read-only
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db-shm
-Removes permissions on /data/system/userbehavior.db-wal
-Removes permissions on /data/system/userbehavior.xml
8/30/11
Thank you to mike1986 of the awesome Sensation forum and the Android Revolution HD ROM for the initial idea, and smokin1337 for bringing it in mod form to the EVO 3D forums.
-DualCore support (my own twist). It sets the second core to run at half the speed of the first core as well as drops the minimum frequency to 192MHz on both cores.
-Compatible with scripts/apps that don't bother the second core.
-PowerSave script is not compatible or needed with this kernel.
-For Quadrant braggers, your scores will take a slight dip since Quadrant isn't optimized for dual cores. However, performance does increase.
8/31/11
-Minor ramdisk tweaks.
-Removed /system/etc/init.post_boot.sh from zip. No longer needed.
-A2SD support.
-594MHz second core now runs with a threshold of 40. (should be slightly better performing)
-Update4: 1.2GHz second core runs in sync with first core at 75 up-threshold.
9/1/11
-Fixed stuck-at-splash-screen.
-Removed A2SD for now.
9/6/11
Removed HTC IPC Server from ramdisk.
10/26/11
Updated kernels with HTC's ramdisk edits.
Added TrevE's ro.lb=unknown and ro.bootloader=unknown values to default.prop. TAKE THAT GOOGLE! Thanks TrevE!
Removed references to htc_ebdlogd
Set ANR (app not responding) history to 0
Set dirty_expire_centisecs to 100
Set capacitive lights to dim (2)
10/27/11
Added ScreenOff script
Added Uninstall ScreenOff script
1/13/12
Updated kernel
Added mpdecision (Thanks TrevE)
Removed insmod /system/lib/modules/qce.ko
3/12/12
Removed mpdecision and references to it in the kernel ramdisk
Updated unmodified and stock dual core kernels to include stock mpdecision so that users of the modified kernels can get mpdecision back when flashing unmodified kernels.
3/14/12
Changed loglevel to 0. Afterall, this is a stock kernel. The less logging the better.
Removed wimaxDumpKmsg
Removed wimaxDumpLastKmsg
Removed wimaxDumpLogcat
Removed bugreport
Removed loading and references to those files from the Kernel ramdisk. Don't worry, WiMax still works. If anything it will work just a bit better now that it doesn't need to worry about dumping any information to logcat and kmsg.
Updated unmodified kernel package to include missing files for those who want to go back to pure stock after flashing one of these.
Here are the changes from 2.08.651.3 ramdisk to 2.17.651.5:
Code:
init.rc
Removed:
mount debugfs /sys/kernel/debug /sys/kernel/debug
Added:
#set projector permissions
chown system system /sys/devices/platform/projector/interface/enable
Added:
on property:crypto.driver.load=1
insmod /system/lib/modules/qce.ko
Not exactly sure why insmod /system/lib/modules/qce.ko is in there. This file is not in the OTA or full ROM package. But it looks like it only gets called if crypto.driver.load=1, but even so, the file isn't there. Strange. Gonna go ahead and remove that.
HTC has made the following ramdisk edits with 2.08.651.3 but actual kernel version hasn't changed.
Here are the edits:
Code:
init.shooter.rc:
Added:
# to enable low charge current in voice call
chown radio radio /sys/class/power_supply/battery/charger_control
chmod 0660 /sys/class/power_supply/battery/charger_control
Removed:
# for vnc
service androidvncserver /system/bin/androidvncserver -a
disabled
oneshot
service usbnet /system/bin/usbnet on
disabled
oneshot
Removed (in bold):
on property:init.svc.bootanim=stopped
[b] start thermald[/b]
start mpdecision
Changed:
[b]FROM[/b]
service mpdecision /system/bin/mpdecision --Nw 5.4 --Ts 480 --no_sleep --avg_comp --single_core_while_panel_off
[b]TO[/b]
service mpdecision /system/bin/mpdecision --Nw 5.4 --Ts 350 --no_sleep --avg_comp --single_core_while_panel_off
Kernel information:
freEVO 3D-StockKernel 2.17.651.5.zip: Dual Cores active. 2nd core max frequency 1.2GHz, Up-threshold at 90 (Stock setting). Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5b.zip: Dual Cores active. 2nd core max frequency 1.2GHz, Up-threshold at 75. Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5c.zip: Dual Cores active. 2nd core max frequency 594MHz, Up-threshold at 90 (Stock setting). Minimum freq at 192MHz.
freEVO 3D-StockKernel 2.17.651.5d.zip: Dual Cores active. 2nd core max frequency 594MHz, Up-threshold at 75. Minimum freq at 192MHz.
Unmodified:
freEVO 3D-StockKernel 2.17.651.5ORIG.zip
Modified (dual cores left at stock settings):
freEVO 3D-StockKernel 2.17.651.5e.zip
Dual Core ScreenOff script:
freEVO-3D-DualCoreScreenOffscript.zip (1.2GHz version):
freEVO-3D-DualCoreScreenOffscript594.zip (594MHz version):
This will install the 70cputweak file in /system/etc/init.d/. To check whether or not it's working (and if your kernel supports init.d), with your phone connected to ADB, simply type or copy: "cat /sys/devices/system/cpu/cpu1/online" If it returns a 0 while the screen is off, that means it is working. You can also do "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" while the screen is off, and if it returns a 384000 then it is working. Keep in mind that you may also edit this file with root explorer or notepad++ to your liking, but you will need to reboot for it to take effect.
Uninstall ScreenOff script
freEVO-3D-UninstallScreenOffScript.zip: This will simply delete the 70cputweak file in /system/etc/init.d. You can accomplish the same thing from adb or root explorer.
NOTE: Please make sure that you don't have any other CPU controlling app such as SetCPU, virtuous OC/OC daemon, CPU Tuner/CPU Master, 98dualcore (from ziggy kernel/synergy) installed if you decide to use this, as they will most definitely interfere with this script and I haven't coded a failsafe to disable it in their presence. You can essentially accomplish what this script does if you use any of the above mentioned apps, but this is mainly for those who want to 'set it and forget it.' Also, SetCPU is most definitely not compatible with this method of dual cores, script or no script. It will return cpu1's online state to default and will render this script as well as the kernel useless.
NOTE 2: If you are going to install another kernel and would like to uninstall dual cores active always, you will need to flash either the unmodified or modified without dual cores kernel first with a reboot afterward, as the ramdisk method employed here will survive many kernel replacements that use Koush's anykernel updater. I've thought about using init.d scripts rather than ramdisk method but eventually decided on this way. Sorry for any inconvenience!
ENOUGH CHOICES?
HBOOT 1.5 users? or just want an easier way to flash things? Joeykrim has created a fantastic app that will allow you to flash kernels, among other things, directly from Android. Check it out here: http://forum.xda-developers.com/showthread.php?p=16129916
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Download: here
Click to expand...
Click to collapse
You are the man!
hTc Evo [3D]
Dang..
Awesome
Sent from my PG86100 using XDA App
Thank-you! I didn't even wait, downloaded it on my phone.
Sent from my s-off Shooter!
Can this kernel get the OC scripts?
I'm sure most of you know this, but since I made the mistake, ill share it. Don't flash the kernel unless your on a 2.3.4 rom. It will break the camera and wifi, among other things. If you did flash, just reflash the old one.
Thanx again and again
Sent from my PG86100 using XDA Premium App
will the silverneedle kernal flash over this succesfully
mjohnson4580 said:
will the silverneedle kernal flash over this succesfully
Click to expand...
Click to collapse
You can flash any kernel over another one......
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Pardon my ignorance but, A, what is cIQ and, B, will this work with Overclocking apps?
Thanks!
gksmithlcw said:
Pardon my ignorance but, A, what is cIQ and, B, will this work with Overclocking apps?
Thanks!
Click to expand...
Click to collapse
A: think of it as carrier spyware
B: No
[email protected] said:
You can flash any kernel over another one......
Click to expand...
Click to collapse
I don't think any other kernel will work on 2.3.4
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Good stuff man! Thanks!
freeza said:
Here's the modified stock kernel from software ver 2.08.651.2, flashable through recovery, of course.
It's been modified to remove cIQ (Carrier IQ) backend/frontend/misc from the kernel as well as init.d support.
Click to expand...
Click to collapse
Thanks. Nice and fast without ciq running in the background.
lafester said:
I don't think any other kernel will work on 2.3.4
Click to expand...
Click to collapse
I believe you're right. I tried to flash the RCMix kernel and got bootloops until I reflashed the 2.3.4 rom again. I guess we'll have to wait until they release the kernel source for this rom before we see newer ones.
sonic41592 said:
I believe you're right. I tried to flash the RCMix kernel and got bootloops until I reflashed the 2.3.4 rom again. I guess we'll have to wait until they release the kernel source for this rom before we see newer ones.
Click to expand...
Click to collapse
that sux.. definitely gonna wait myself, on flashing any custom 2.3.4 ROMs right now.. will wait for AOSP/CM7/MIUI 2.3.5 gotta have my OC and Custom ROM..
Nice work on pulling the iQ BS out of it..
Freeza, what ROMs is this tested with? I tried it on my own build and on xhausx build and it wouldn't boot all the way. Screen goes blank and then nothing. Still responds to power because I see the buttons toggle on and off.
Do I need to have the other firmware updates (radio, etc) too?
Any thoughts?
I did the firmware updates and this modified kernel ran fine on Haus's stock.
Sent from my PG86100 using XDA App
Mexiking10 said:
I did the firmware updates and this modified kernel ran fine on Haus's stock.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Sweet! Thats what I wanted to know.
Thanks brother!!!!
scrosler said:
Freeza, what ROMs is this tested with? I tried it on my own build and on xhausx build and it wouldn't boot all the way. Screen goes blank and then nothing. Still responds to power because I see the buttons toggle on and off.
Do I need to have the other firmware updates (radio, etc) too?
Any thoughts?
Click to expand...
Click to collapse
i got the same thing going on on my end. i baked it in as well. just reboots.
Dear friends i found new scripts mod by @Exit_Only ...
http://forum.xda-developers.com/showthread.php?t=2411161
I'm Using this mod for many weeks and still no problem exists..
Wifi tether and direct also works under this mod..
Default Scripts | 10/03/2013 | Team Kernelizers | Operation Killjoy™ | RC7 | Insanity
OPERATION KILLJOY™
TEAM KERNELIZERS PRESENTS...
Operation Killjoy™ This tweak package takes your android device to a whole new level of awesomeness. Big thanks to all the developers involved.
THIS TWEAK PACKAGE IS 100% UNIVERSAL ON ALL DEVICES RUNNING ANDROID 4.0 OR HIGHER!!!
CREDITS:
Thanks to all my testers
First and foremost I want to thank team kernelizers for taking me inas a member of there team
@malybru (for the awesome banner)
@Ryuinferno(For the entro binary)
@LENAROX(For all your recommendations)
@Koush(For being an awesome coder)
@CyanogenMod(Do I need to say why)
@mw86(Being an amazing tester and debugger)
@idcrisis(For haveged binary for entropy)
@thomas.raines(Just a general thanks)
@jrummy16(Being an awesome coder)
@kejar31
@kobridge(Awesome scripter)
@zeppelinrox(Awesome scripter, most scripts on xda is because of your genius)
@Chainfire(Touchscreen script)
@ImbaWind(ICS ram flush boost script)
@GideonX(Awesome kernel dev
@RErick(Team k)
@decialman(Team k)
@castle_bravo(Team k)
@dsexton(Remount and readahead original dev)
@Juwe11(Original Minfree script)
@noobnl(GS3 maintainer for CM)
Any one else? If I forgot you please pm me and it will be fixed ASAP!!!
ATTENTION DEVELOPERS: I REALLY DO NOT WANT ANY DEVELOPER USING MY TWEAKS FOR ANYTHING. DUE TO UNFORTUNATE INCIDENTS ON XDA I RESPECTFULLY ASK NO DEVELOPER USE KILLJOY IN THERE PROJECT, TWEAK, MOD, KERNEL, ROM OR ANY OTHER TYPE PROJECT. PLEASE ADD A LINK TO YOUR OP BUT DO NOT INCLUDE IT IN YOUR ZIP FILE.
My Donations: https://www.paypal.com/cgi-bin/websc...=V6B74D49LB3SW
CURRENT DONATIONS RECEIVED:
Melanie (Unknown XDA Screen name) - $10.00 @azuma37 (XDA) - $5.00
Unknown name / Unknown XDA Username - $5.00 @iamsmallpang - $5.00 @RErick - $75.00 @jakereeves - $20.00 @Samurai - $5.00
Updated on 8/19/2013 @ 6:55am P.D.T
General Q & A Section:
Q.)How can I tell if this is actually working or not?
A.)Open Terminal Emulator and type this command...
Code:
su
killjoy
Q.)Help!!! Why is my phone bootlooping?
A.)I need more detailed information like what device you have, what version of android are you on, what recovery are you using? Better yet please get me a adb boot logcat as well.
Q.)Build.prop tweaks did not inject!!! Why?
A.)You don't have init.d support!!!
Q.)But my kernel supports init.d so why is my buildprop not getting injected?
A.)Well obviously you don't have init.d support cause if you did the build.prop would have been injected.
Q.)How can I test to see if I have init.d support?
A.)Flash this - http://www.mediafire.com/?97q4sh1wwcesois
Once you flash it then go into /data folder and look to see if you have a file called "okj_test.log", no log means no init.d support. END OF STORY!!!
Standard Disclaimer: Flash at your own risk. Myself nor XDA is responsible for any damage this thing may cause you. If your phone blows up after flashing this and you point the finger at me or team kernelizers I will laugh at you!!!
GENERAL WARNING: Do NOT I repeat DO NOT use ANY other tweaks with this package. If you choose to do so after reading this you do so AT YOUR OWN RISK. If you ask bout other tweaks in my thread YOU WILL BE IGNORED.
WHAT IS NEEDED:
1.) Root access (su binary required)
2.) Need to be on 4.0 ICS or higher
3.) Terminal Emulator app
4.) Enough space in your /system partition (10 mb available minimum)
If you do not meet these requirements then DO NOT USE IT!!!
5.) A kernel that has init.d support built into it or another init.d support method.
If you don't meet all these requirement DO NOT use this package!!!
1.) Make sure you meet the requirements above
2.) Download the latest version of Operation Killjoy™
3.) Boot into recovery (CWM recovery)
4.) Make a nandroid backup
5.) Flash inside CWM recovery
6.) Reboot...
7.) Profit...????
ABOUT THE TWEAKS:
1.) 2 init.d script
2.) Entropy Generator
Turn on entropy...
Code:
su
entro_on
Turn off entropy...
Code:
su
entro_off
Check available entropy levels type (YOU MUST HAVE ACTIVATED ENTROPY RESTORE BEFORE ATTEMPTING THIS)
Code:
su
entro
3.) Ext4 Tweaks
4.) Zero UI Lag
5.) Maxed out speed & Performance
6.) Disables most logging activities
7.) Lots of kernel tweaks (Disabled most kernel sleeps and Adjusted Linux values)
8.) Multiple VM & Net tweaks
9.) RAM booster binary (Recover lost ram on the go without rebooting)
Choose between moderate and aggressive ram boost...
Code:
su
boost
10.) Killjoy™ Binary (Exit_Only Exclusive)
Code:
su
killjoy
11.) Very light weight and fast
12.) CpuControl script that is 100% user tweaked via root explorer
If you are running ANY overclock apps then cputuner IS NOT for you!!! Cputuner will check to see if your running an OC app and will kick you out of cputuner if it detects said app!!!
I'll add more as I remember it :thumbup::beer:
08-18-13: First Release
08-19-13: Fixed All Derps
08-26-13: Completely Revamped CPU Tuner
Read ahead adjusted from 3072 to 2048 kb
Added new cat logging feature from tkmod (MERGED)
Added GPU Rendering from tkmod (MERGED)
Added buildprop script modified from tkmod (MERGED)
Redid entire init.d script from ground up and added samsung touchscreen mod (NOT APPICIBLE ON ALL SAMSUNG MODELS)
Numerous adjustments to code overall
08-29-13_test: Removed GPU render script
Removed build prop injector
Adjusted some values for better stability
09-02-13_official: Removed all test scripts
Fixed licensing errors
Fixed all errors
Removed cputuner to kill developer conflicts
Stable release
09-03-12_official: Fixed multiple bugs
No new features added
09-05-13_official: Made buildprop script busybox dependent
Fixed random rebooting
Fixed laginess
Fixed buildprop tweaks not installing on TWRP
Much better battery life and stability
09-08-13_RC2: Fixed bootloops happening because of read ahead scripts
Added testinitd script that will tell you whether you have init.d support, look in /data/killjoy/*
Adjusted a lot of stuff for better stability and battery life
Fixed logging issue from RC1
Official Release Canidiate v2
09-10-13_RC3: No more support for gingerbread devices
Must be running android 4.0 or higher or script will abort
Fixed lag issues
Killed logcating again
Adjusted build.prop script
Removed all test scripts
10-02-13_RC7: Added intellidemand governor to cputuner
Removed unstable commented out code
Updated to newest busybox
Fixed killjoy binary
Updated version number
OFFICIAL RELEASES
09-05-2013_official: http://www.mediafire.com/?41gw8d3tude71q3
OFFICIAL RELEASE CANIDIATES
10-02-2013_RC7: http://www.mediafire.com/?861h11n1767gu15
TEST RELEASES
No test releases yet!!!
WARNING: THESE ARE EXPERIMENTAL BUILDS ONLY. FLASH AT YOUR OWN RISK!!! Some of these builds will be super stable and others may not be stable at all. Keep in mind I do test every release so it will be at least semi stable.
KNOWN ISSUES & BUGS:
1.) Bootloops have happened on a few devices using TWRP Recoveries, Current workaround is use CWM Recovery.
2.) Build.prop injection tool not working on TWRP v2.6.0.0+ on multiple devices. Current workaround is use CWM Recovery.
XDA Script & Code Developer
Check out my github: http://github.com/ExitOnly
In support of Android Open Source Project (AOSP)
Current Device:
Samsung Galaxy S III (d2spr)
Current Setup:
CM10.1.1 Nightly w/ RNGD Entropy generator
Direct Injection Turbo Custom Tweaks
0-60 in less then 2 seconds
How to uninstall killjoy!!!
1.) Open terminal emulator
2.) Type these commands
Code:
su
uninstall
3.) Reboot your device
4.) Killjoy is gone
hello. would like to know how to make this script run on every boot?
zamurai x said:
hello. would like to know how to make this script run on every boot?
Click to expand...
Click to collapse
this script run over every boot automatically..
{
"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"
}
ArchiKitchen - Brand new Android Kitchen
Commits/Changes -> https://github.com/JustArchi/ArchiKitchen/commits/master
Source -> https://github.com/JustArchi/ArchiKitchen
TODO list -> https://github.com/JustArchi/ArchiKitchen/issues?state=open
Download. Of course you can also clone my repository to stay up to date.
[SIZE="+1"]Features:[/SIZE]
Compatible with every Linux, which provides bash shell (every available distro nowadays)
Full ARM/X86 support for all included android binaries (Root, Busybox)
Dynamic permissions - A generic list of all available permissions, with proper filter for your local build and device
Dynamic symlinks - A generic list of all available symlinks, with proper filter for your local build and device. Additionaly if you're building from stock image, support for including symlinks from image itself, which results in best 1:1 copy
FS-friendly method of flashing - ROMs created with ArchiKitchen are fully compatible with every available partition, which means that they don't reformat /system partition during flashing. This is extremely important for dual-FS support for example for EXT4 and F2FS on SGS3.
Kernel repacking - Powered by mkbootimg, repacking a kernel never was easier. With one click you're extracting the kernel along with ramdisk to the proper folder, and with the second you repack it back
Deodexing - With one click you can easily deodex your whole ROM. With multi-threaded process and automatic API detection, this never was easier as well.
ArchiDroid Init.d - Forget about relying on kernel's ramdisk. Implement init.d in your ROM, not the kernel!
Latest [Bak]smali
Latest SuperSU
Latest Busybox
Latest Zipalign
And many more in the unique shell ktichen
[SIZE="+1"]Credits:[/SIZE]
@osm0sis - For mkbootimg
@Chainfire - For SuperSU
@Stericson - For BusyBox
@JesusFreke - For [Bak]smali
@bgcngm - For MTK-Tools
AOSP - For Zipalign
ArchiKitchen Tutorial
Part 1 - Setting up Linux & ArchiKitchen on Windows
https://www.youtube.com/watch?v=ktedmhWHz2M
By watching above step-by-step video, you'll learn:
1. How to install Debian on your VirtualBox machine
2. How to connect Windows with Linux through a shared VBox folder
3. How to install ArchiKitchen
4. How to create your first custom ROM, with built-in Root and Busybox
Extra information:
- You can use any virtualization method you want. I suggest using VirtualBox, as it's very easy, flexible and free virtualization solution.
- You can use nearly any Linux distro. I suggest either Debian or Ubuntu, as both of them have excellent support and are very easy to install and use, compared to some other ones. However if you feel fine in Linux environment, you can install nearly any distro you like.
Mini.iso link
Weekly Debian Testing.iso link
Installing virtualbox additions: apt-get install virtualbox-guest-dkms
Installing required tools: apt-get install zip unzip openjdk-7-jdk
Mounting a shared VBox folder: mount -t vboxsf yourName /path/to/yourFolder
Tutorials made by other developers: @bigrammy
Part 1. Prepare for linux Installation https://www.youtube.com/watch?v=aDsQTcDvSMY
Part 2. Install Linux (Ubuntu/Zorin) https://www.youtube.com/watch?v=KwnIjCXXM5Y
Part 2.5. Edit Winows bootloader to boot Linux: https://www.youtube.com/watch?v=gNpQucQxcFQ
Part 3. Work as Root Mod & Install ArchiKitchen https://www.youtube.com/watch?v=T_ad7uML8QM
Part 4. How to add your device locally to the Kitchen: http://youtu.be/YXNDcmf6GhI
ArchiKitchen Questions & Answers
Q: What is this "ArchiKitchen"?
A: A Linux-based kitchen, with a main objective of converting stock ROM drops in .img, .tar.md5 or similar formats to CWM-flashable .zip.
Q: So I can create my own custom ROM based on stock ROM with it?
A: Exactly.
Q: Is it for Linux only? Why windows is not supported?
A: Let's face it, Android is based on Linux kernel and we could call it a mobile UNIX fork. It's hard to work with Linux-based things on Windows, in fact, Windows doesn't even offer Bash (Bourne-again shell), which is absolutely core for ArchiKitchen. Working with windows is painful, for example - .img mounting. I can very easily mount any filesystem image on Linux with just one command, while doing so on Windows usually requires a massive convertion of whole image to .zip file, then extracting a single files. Also, Windows doesn't support symbolic links, and this makes it impossible to create 1:1 copy of the image "translated" to zip file. Therefore, making a Windows port would require lots of more work and solving issues, and even with that it would still cause some core features to be unavailable. However, launching Linux on Windows is very easy thanks to VirtualBox and other virtualization software, so you don't need to reformat your PC or stick purely with Linux. In fact, this is the proposed way of using ArchiKitchen - Installing a native Linux distro (suggested: Debian or Ubuntu) and then installing ArchiKitchen on it. Take a look at tutorial to see how easily you can install and run ArchiKitchen in Linux VBox.
Q: Is Cygwin supported?
A: No. Cygwin IS NOT supported and it's not planned to add such support. Reason is nearly the same as above one. However, ArchiKitchen is open-source project and I'm open for all pull requests, so perhaps somebody will add support for Cygwin in the future. Until then, ArchiKitchen is compatible ONLY with Linux, and if you use it on Cygwin you're on your own with the issues that may happen.
Q: Which phones are supported?
A: ArchiKitchen contains a local "database" of devices, which includes a kernel/modem blocks to be used. However, as long as you know the partition layour of your device (kernel block), ArchiKitchen works with every phone and every Android variant. I'm trying to make it as universal as possible, so even if your device does not exist in our local database, it should work.
Q: How can I add my own phone to the local database?
A: If it doesn't exist yet, take a look at "product" folder. Inside you can notice various devices with name based on their models. ArchiKitchen will detect your ROM's model and check inside if it exists, if it does, then some properties for this model will be loaded, if it doesn't exist, then ArchiKitchen will ask user for them. Probably the best idea is to copy one of the already available models (for example "m0" - Samsung Galaxy S3), then rename new copied folder to your model name and finally edit files inside.
Q: What is "NULL" text found for example in some MODEM files in the database?
A: Some phones have a possibility to flash modem directly from CWM, others don't. "NULL" text indicates that this model does not support flashing modem.bin, so even if ArchiKitchen finds and recognizes it, it will pop up an error telling you that it unfortunately can't be used.
Q: Where is SYSTEM block?
A: System block is not being used at all, as it's a valid partition and should be located in "fstab" file in recovery already. ArchiKitchen mounts system automatically through "mount" binary, with automatic filesystem and /system path. I consider providing a system block as something obsolete, because it's only required when you're formatting a partition, and even during flashing, a wipe - delete_recursive() function is enough. Therefore, ArchiKitchen does NOT require providing a /system block.
ArchiKitchen Troubleshooting
Q: It looks like something is wrong with zipalign command. I can notice errors like "./zipalign: No such file or directory"
A: This is because zipalign is x86 binary (32-bit), while you have amd64 (64-bit) Linux. Therefore, we must install some missing core packages to properly support x86 binaries. This will do the trick:
Code:
apt-get install lib32stdc++6 lib32z1
[SIZE="+1"]ArchiDroid Init.d[/SIZE]
ArchiDroid Init.d is an innovative method for including init.d support in the ROM itself, and not in the kernel. ArchiKitchen supports adding ArchiDroid Init.d to any Android ROM.
ArchiDroid Init.d is based on two files. A core - debuggerd hook, and a check part - simple init.d script.
Init.d script is named 00ARCHIDROID_INITD, and it only creates a special file to notify the core that init.d has been already executed, therefore it can't conflict with anything and it's completely safe.
The core is a hook for special /system/bin/debuggerd binary, which is normally called once during initial boot. Therefore, when it's called, ArchiDroid Init.d firstly waits a specified amount of time (default: 5 seconds), in case if user has already a kernel with init.d support. This is required because otherwise all init.d scripts would be executed twice - by kernel and our init.d. After specified time, if init.d is still not executed, our hook executes all scripts in alfabetical order. Lastly, when we're done, hook is executing original debuggerd binary (default: debuggerd.real) and shares the environment, arguments and everything. This is a perfect method for implementing init.d in the ROM itself, because we don't need to trust the kernel that it supports and executes init.d properly. We give it a 5 seconds to execute it, and eventually we do the job if kernel is not interested in that. This way we can support both custom kernels with native init.d support (we wait initial delay, if kernel executes init.d, all is fine and we don't have to do so), and also pure stock kernels without init.d support (we wait initial delay, kernel doesn't care about init.d, so we're executing it).
I think that such hook works far better than relying on the kernel and modyfing stock ramdisks. Also we're sure that even if user changes kernel to any custom one, we still have reliable init.d support, regardless if custom kernel supports init.d or not.
Reserved.
JustArchi said:
It's a bit quiet in here, I was expecting more noise
Click to expand...
Click to collapse
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Harris_xx said:
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
Looking forward.
i really appreciate your work, like every time
In general whole kitchen needs a magic touch more or less but firstly I'll want to make it fully usable (and modern!) then eventually rework it.
As for now it's more or less up-to-date. Also added Note3 variant.
Thanks for your work and projekt!
I will download and test it with the new Galaxy Note 10.1 2014 :good: (Android 4.3)
Feel free to test it, but keep in mind that it's still work in progress .
Today I've added new experimental method for *better* handling setting up rom directory. As for now it supports only system.img in sgs format, however it automatically extracts it (if needed) from any tar/zip package, also with properly detecting cache.img. This is the main feature I was missing in original kitchen.
https://github.com/JustArchi/Android-Kitchen/commit/cf025ebf6573d23e5d2b7cfde258d9b7c36abd29
Just please don't track "wip" branch, as it's rebased often and merged into master when ready .
This is great, as I love the kitchen it is awesome that you've updated it. I'll be trying it out tonight. Thanks for your work.
Sent from my XT1032 using XDA Premium 4 mobile app
Great work :good:
Tested New device LG G2
Looks very good, thanks for updating the kitchen.
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Perka said:
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Click to expand...
Click to collapse
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
JustArchi said:
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
Click to expand...
Click to collapse
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Perka said:
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Click to expand...
Click to collapse
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
JustArchi said:
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
Click to expand...
Click to collapse
Sounds good
---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------
Donation made
4T106212CC7164407
i worked with planty firmwareswith the latest kitchen for my devices but anytime the SuperSu after installation was saying something like "there is a SuperSu, but not Supersu binary installed". that thing was gone after i flash the SuperSu update binary. Does your kitchen gonna give me SuperSu from the start (instalation)?
Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
ludogaut14 said:
Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
Click to expand...
Click to collapse
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
freaksamael said:
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
Click to expand...
Click to collapse
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
ludogaut14 said:
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
Click to expand...
Click to collapse
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
freaksamael said:
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
Click to expand...
Click to collapse
Hi, I did your advice but do not work. 00test init.d ok, 01disable_selinux not work, "getenforce" always "enforcing". I wait a good person makes a kernel with SELinux permissive and KNOX desactived. Thank you very much for your advice and excuse me for my english.
Introduction:
This modification / custom kernel configuration for Pixel and Pixel XL is optimized and made with the focus on bringing several, carefully tuned behind-the-scenes enhancements & adjustments that improves overall critically needed performance, system responsivness and battery life to the highest possible level. The seed to this project can by the way be found here, for anyone that is interested of its origins.
Note: This script is not recommended to be modified or customized by the user.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
[
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give the script the following permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for both the first generation as well as the second generation of Pixels!
Credits:
@nathanchance for his contributions with his Flash Kernel
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory from the beginning
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2018-10-08
Last updated: 2019-01-04
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Edit: sorry for stealing the first post btw hehe
EDIT: My changelog dedicated post have exceeded 30000 characters, so I have decided that the changelog will only be included in the respective update posts from now on!
So you all know how the situation is.
shagbag913 said:
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Click to expand...
Click to collapse
I'll do whatever I can on the first generation Pixels for giving you guys & girls the same awesome experience.
And thanks btw.
:highfive:
Update!
v1.1 (Minor release)
- Made a few more (hopefully) battery conserving adjustments to the Sched governor.
Enjoy!
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Core control screenshot
Phalanx7621 said:
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Click to expand...
Click to collapse
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
xFirefly93 said:
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Click to expand...
Click to collapse
I can confirm that the same happens to me.
Thanks for the work!
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
Old Man Dave said:
I can confirm that the same happens to me.
Thanks for the work!
Click to expand...
Click to collapse
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
xFirefly93 said:
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
Click to expand...
Click to collapse
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Phalanx7621 said:
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Click to expand...
Click to collapse
I will compare how my Marlin / Pixel XL performs with it disabled respectively enabled and see which "solution" that is giving best battery life with less performance tradeoffs, and then I will include the best overall compromise in v1.2 of my kernel configuration / script.
For anyone else interested in this, this is how I went about it:
1) Downloaded Flash Kernel from his thread over here https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300
2) Downloaded the latest version of this mod
3) Downloaded the Magisk module required, which you can find by searching Magisk for "busybox" and choosing the "Busybox for android NDK" version
4) Flash that Magisk module, reboot into recovery, flash the Flash kernel (no need to reflash magisk, it's automatic), reboot back into system.
5) Check to make sure Magisk is functioning properly, for me I had to reboot due to an error in the application but that may have been on my end.
6) So now you have Flash kernel and the Magisk module required to be able to properly run this script. Extract the script from the .zip file you downloaded to a folder.
7) Ok so these next steps if you aren't familiar with this stuff could be tricky, but it's actually simple it just sounds tricky. I use Mixplorer for this, I highly suggest using it, it's free and it's on XDA Labs here. https://labs.xda-developers.com/store/app/com.mixplorer But any file explorer w/ root access will do. Inside the folder you extracted the script into there are two versions, choose the Public Release version and copy that file. Navigate to root ( / ) and go to /data/media/0 and paste the file there. The reason for this is you have to change the permissions to allow it to be an executable script and this folder allows that. (there are other ways to do this, FYI but this works just fine for me) You want the permissions to be 755, so it would look like this: (see attachment) To change permissions in Mixplorer, just long press the file and hit the little i (for information) in the upper right. Then click on the permissions you want to change.
8) Now all you have to do is copy that file you just changed the permissions to and paste it into: /sbin/.core/img/.core/service.d | | Now you won't be able to SEE .core unless you have hidden files on, in Magisk it's in the upper right hand corner 3 dot menu. Click Show Hidden. After you paste the file there, reboot and congratulations, you have achieved greatness.
Phalanx7621 said:
.. FYI..
Click to expand...
Click to collapse
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
xFirefly93 said:
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
Click to expand...
Click to collapse
Oh ok cool, just wanted anybody else to be able to use this awesome mod too, it works wonderfully!
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
It's there.... I'm on the same rom. You need to start at root and not device storage, as well as show hidden folders
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
Use X-plore file manager adn give Root permissions and in settings Show hidden files or folders something.
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
xFirefly93 said:
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
Click to expand...
Click to collapse
Hi, which release from Public and Maintenance we have to use. Thank you for your hard work.