Code:
* Your warranty is now void...
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone*
* bootloops and alarm does not go off. Please do some research if you have any *
* concerns about features included in my kernel before using it! YOU and only*
* YOU are choosing to make these modifications.
*/
Please don't use these kernels over other devices, absolutely it will brick your unsupported devices.
Its just only for GT-I9192 Galaxy S4 Mini Dual Sim Phone [DUOS]
use at your own risk. I'm not responsible for any damages or bricked phones.
Its Custom Kernel , and will avoid your warranty service
Features
Only For GT-I9192 [DUOS] over Samsung 4.2.2 roms only
Compiled with Linaro Toolchain 4.7.4 and -O3 optimization
Compiled from GT-I9192_JB_Opensource_Update1.zip MK4
AutoRoot
Auto Knox removing apps and notifications
Set selinux to permissive
Changed Samsung LowMemorKiller method to upstream
Fix Battery Drain
Added More FS partition type suuport ; cifs,nfs,ntfs,exfat.
Insecured ADB
Tweaks on CPU frequencies and voltages [battery friendly]
Custom Governorses
badass
smartassH3
smartassV2
Asswax
dancedance
wheatley
smartmax
interactive
userspace
powersave
lionheart
adaptive
ondemand
performance
IO Schedulers
Noop
deadline
row [default]
cfq
bfq
fiops
sio
vr
zen
fifo
Voltage Control
BLN Support
Dynamic FSync
Fastcharge USB
FauxSound V3.1
Increased entropy values
LZO compression method
Version 2.7 13th March 2014
Click to View Details for 2.7
Version 2.5 2nd March 2014
Click to View details @ Post 184
Version 2.4 Changelog 5th January 2014
Filename = Amestris Kernel-2.4_[9192-S4MiniDUOS][MK4]-CWM..zip
New configuration based on fluid script
Code:
# Tweaks and Configuration
/system/bin/setprop pm.sleep_mode 1
/system/bin/setprop ro.ril.disable.power.collapse 1
/system/bin/setprop ro.telephony.call_ring.delay 1000
echo "NO_GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features;
echo "20" > /proc/sys/vm/swappiness; #0
echo "1" > /proc/sys/vm/overcommit_memory;
echo "50" > /proc/sys/vm/overcommit_ratio;
echo "3" > /proc/sys/vm/page-cluster;
echo "10" > /proc/sys/vm/vfs_cache_pressure; #300
echo "2000" > /proc/sys/vm/dirty_writeback_centisecs;
echo "1000" > /proc/sys/vm/dirty_expire_centisecs;
echo "0" > /proc/sys/vm/oom_kill_allocating_task; #1
echo "0" > /proc/sys/vm/panic_on_oom;
echo "4096" > /proc/sys/vm/min_free_kbytes;
echo "10" > /proc/sys/fs/lease-break-time;
echo "64000" > /proc/sys/kernel/msgmni; #1024
echo "64000" > /proc/sys/kernel/msgmax;
echo "0" > /proc/sys/kernel/panic_on_oops; #1
echo "30" > /proc/sys/kernel/panic; #0 #10
echo "0" > /proc/sys/kernel/hung_task_timeout_secs; #45
echo "0" > /proc/sys/kernel/softlockup_panic;
/system/bin/sysctl -w kernel.threads-max=525810
/system/bin/sysctl -w kernel.sched_compat_yield=1
/system/bin/sysctl -w net.ipv6.conf.default.use_tempaddr=2
/system/bin/sysctl -w net.ipv6.conf.all.use_tempaddr=2
/system/bin/sysctl -w net.ipv6.conf.all.temp_prefered_lft=3600
/system/bin/sysctl -w net.ipv6.conf.default.temp_prefered_lft=3600
if [ -e /proc/sys/kernel/sched_min_granularity_ns ]
then
echo 200000 > /proc/sys/kernel/sched_min_granularity_ns;
fi
if [ -e /proc/sys/kernel/sched_latency_ns ]
then
echo 400000 > /proc/sys/kernel/sched_latency_ns;
fi
if [ -e /proc/sys/kernel/sched_wakeup_granularity_ns ]
then
echo 100000 > /proc/sys/kernel/sched_wakeup_granularity_ns;
fi
FauxSound V 3.1 thanks to f4ktion
USB Fastcharging Support thanks to f4ktion
Version 2.3 Changelog
Filename = Amestris Kernel-2.3_[9192-S4MiniDUOS][MK4]-CWM..zip
1-Enabled Voltage Control
2-Disabled BLN Wakelocks
3-Dynamic fsync v1.0 [credit to faux123]
4-changed kernel compression to LZO
5-tweaked ondemand cpu overnor for better battery usage, you may will get lower scores on benchmark apps, you can change the governorse to default if you want more power. [lower parameters than v2.1]
6-increased entropy values [4 x default]
7-increased read-ahead values.
8- revert the new ROW IO schedulers algorithm.
Version 2.2 Changelog is removed!!! unknown WIFI BUG!
Filename = Amestris Kernel_ST_V-2.2_[9192-S4MiniDUOS]-CWM..zip
12/31/2013
Fix for Voltage Control
Standard Edition - [ST]
Version 2.1 Changelog
12/27/2013
1-added BLN Support , you need BLN Control app and Liblights, i will provide them later!
2-Add misc FS support, cifs,nfs,ntfs,exfat.
3-Added IO Schedulers
Noop
deadline
row [default]
cfq
bfq
fiops
sio
vr
zen
fifo
4-Tweaked Ondemand cpu governorse profile
5-Tweaked for some battery consuming
6-CPU Voltage control is enabled
7-ZRAM is enabled
8-Removed useless logs
Version 2.0 Changelog
12/21/2013
1-Compiled kernel from open source samsung new kernel source release [MK4]
2-No changes from source, excepting disabled root prevention security system.
3-AutoRoot Kernel, it will disable Knox Security system and will root your phone if you have not Superuser.apk application in your /system/app folder. [SuperSU V1.86]
4-it will install busybox on /sbin folder and if you don't installed the busybox on /system/xbin or /system/bin folder, it will generate for those addresses to make busybox working for other applications, like Backup titanium.
5- Some Battery Twaeking for lower battery consuming.
6- All Knox Security files will be remove automatically by the kernel, it will check them, if they will be available, it will delete them.
7- Init.D Support
8- Insecured ADB services, adb remount , adb root.
Toolchain Version : arm-unknown-linux-gnueabi-linaro_4.7.4-2013 by christopher83
Version 1.0 Changelog
I just edited stock boot.img file as insecure for running root device.
This package will install :
busybox 1.20.2
Super Su + Su binary
EFS backup to your sd card
Rooted Stock Kernel
Init.D Scripts Support
Persian Language Support Page
Credits:
DSIXDA for kitchen
Christopher83 for LiNARO GCC
Wanam
Stratosk
Ktoonsez
F4k [f4ktion]
googy_anas
AndreiLux
junkyde [BLN]
Faux123
AndiP
ADRENO DRIVERS - GPU DRIVERS
Version : Adreno200-AU_LINUX_ANDROID_JB_VANILLA_04.02.02.060.053
Download the "ADRENO_DRIVERS[JB_VANILLA_04.02.02.060.053].zip" file and install it from recovery.
============================================================================================
============================================================================================
How To Install
** ZIP File Names - CWM Packages
Ensure you have custom recovery mod , CWM 6.x
Download the zipped attached file
copy downloaded file into your Device Storage [Phone]
goto Recovery mod and install the zip file.
enjoy.
----------------------------------------------------------------------------------------
** TAR File Names - ODIN Flashable files
1- Download the tar file .
2- Reboot your phone and goto Download mode
3- Connect your phone to PC and be sure that ODIN is recognized your phone.
4- Run the ODIN 3.09 and put tar file into AP section and uncheck "F.Reset Time" and , Click on the Start button.
** BLN liblights created by junkyde.
Pleasy post to i9190 your
Thank man!
مرسی داداش
THANKS
PLISE MAKE FOR i9190
thanks, what's insicure kernel for?
now i have root access and stock kernel
what init.d scripts are working?
Sent from my GT-I9192 using Tapatalk 4
ahmadblu said:
مرسی داداش
THANKS
PLISE MAKE FOR i9190
Click to expand...
Click to collapse
Trunghuy90 said:
Pleasy post to i9190 your
Thank man!
Click to expand...
Click to collapse
you're welcom, if you want this for your device, please send me original boot.img and recovery.img file from stock firmware that you downloaded.
i will make it as fast as i can.
fburgos said:
thanks, what's insicure kernel for?
now i have root access and stock kernel
what init.d scripts are working?
Sent from my GT-I9192 using Tapatalk 4
Click to expand...
Click to collapse
to access adb commands and also access to su.
yes, init.d is working.
http://db.tt/SHiYWMH4
My file
Thank man helped!
Trunghuy90 said:
http://db.tt/SHiYWMH4
My file
Thank man helped!
Click to expand...
Click to collapse
you send edited recovery and kernel to me..
i told you, just send me stock [unchanged ] version.
this boot.img is insecure.
M_J_Nazari said:
you send edited recovery and kernel to me..
i told you, just send me stock [unchanged ] version.
this boot.img is insecure.
Click to expand...
Click to collapse
I do not know where to get it at all , because I'm not root machine and I do not have personal computers . I just know it 's taken 2 files topic rooting guide .
Sorry my enlish!
Trunghuy90 said:
I do not know where to get it at all , because I'm not root machine and I do not have personal computers . I just know it 's taken 2 files topic rooting guide .
Sorry my enlish!
Click to expand...
Click to collapse
its rooted kernel. no need to change them.
BLN support.....???
M_J_Nazari said:
Hi,
Please don't use these kernels over other devices, absolutely it will brick your unsupported devices.
Its just only for GT-I9192 Galaxy S4 Mini Dual Sim Phone [DUOS]
use at your own risk. I'm not responsible for any damages or bricked phones.
I just edited stock boot.img file as insecure for running root device.
This package will install :
busybox 1.20.2
Super Su + Su binary
EFS backup to your sd card
Rooted Stock Kernel
Init.D Scripts Support
How to Install?
Ensure you have custom recovery mod , CWM 6.x
Download the zipped attached file
copy downloaded file into your Device Storage [Phone]
goto Recovery mod and install the zip file.
enjoy.
Credits:
dsixda for kitchen
Click to expand...
Click to collapse
Hi bro....
I just want to know whether this kernel has BLN support...??
If no, can you pls add it and post the modified kernel here...??
Awaiting your reply.....
Trunghuy90 said:
I do not know where to get it at all , because I'm not root machine and I do not have personal computers . I just know it 's taken 2 files topic rooting guide .
Sorry my enlish!
Click to expand...
Click to collapse
i think you can get the kernel from here:
http://forum.xda-developers.com/showthread.php?t=2375402
M_J_Nazari said:
its rooted kernel. no need to change them.
Click to expand...
Click to collapse
MY FILE KERNEL
http://hotfile.com/dl/236887509/04d283d/KERNEL-XXV-I9190DXUAMG1-1374235283.tar.html
vichunni said:
Hi bro....
I just want to know whether this kernel has BLN support...??
If no, can you pls add it and post the modified kernel here...??
Awaiting your reply.....
Click to expand...
Click to collapse
Hi
the samsung kernel source is published just for MF7 firmware, i trying to learn kernel customization already, but the source has a strange bugs, even when i add some io schedulers.
we have to wait for new kernel sources.
Trunghuy90 said:
MY FILE KERNEL
http://hotfile.com/dl/236887509/04d283d/KERNEL-XXV-I9190DXUAMG1-1374235283.tar.html
Click to expand...
Click to collapse
ok , i will take look at them when i get back to home.
M_J_Nazari said:
Hi
the samsung kernel source is published just for MF7 firmware, i trying to learn kernel customization already, but the source has a strange bugs, even when i add some io schedulers.
we have to wait for new kernel sources.
ok , i will take look at them when i get back to home.
Click to expand...
Click to collapse
Pleasy mod for i9190
Thank man more!
thanx bro I appreciate your hard work . thanks
do you have any plan to make a custom rom for this device with fewer bloatware and smoother . or maybe newer android version ?
Trunghuy90 said:
Pleasy mod for i9190
Thank man more!
Click to expand...
Click to collapse
ok, just be patient , im veru busy these days.
amirsardari said:
thanx bro I appreciate your hard work . thanks
do you have any plan to make a custom rom for this device with fewer bloatware and smoother . or maybe newer android version ?
Click to expand...
Click to collapse
Hi amir
im working on kernel compiling allready, yes i have a plan to make it. just gimme some time.
also you can find articles on persian languages here.
http://www.pda-planet.com/forum/
best reagrds
Thanx bro . now im a member at pda-planet with same user here . thank u
Think you could add oc?
Howdareme said:
Think you could add oc?
Click to expand...
Click to collapse
i will try to do that, allready i added io schedulers and also cpu governors profiles to the kernel, i will share it when i tested .
Related
ICUP Kernel Edition
Features:
**** ->>> Ice Cream Universal Product <<<-->>> ICUP Kernel Edition <<<- ****
~ Updated Kernel Version to 3.1.10-ICUP
~~~ Fixed issues with MIUI & Other Rom's
~~~ GPS 100% Fixed for NS4G Users
~~~ Tweaked Conservative Gov.
~~~ Tweaked lulzactive Gov.
~~~ Added brazilianwax Gov.
~~~ Added intellidemand Gov.
~~~ Added lionheart Gov.
~~~ Added ondemandx Gov.
~~~ Added savagedzen Gov.
~~~ Added Wheatley Gov.
~~ Updated to 3.1.10
~~ USB Tethering Fixed
~~ CFQ I/O By Default now
~~ misc Fixes
~~ Camera Fixed for NS4G Users
~~ VR I/O Added
~~ LCD Voltage Drop
~~ Lagfree Governor
~~ Interactivex Governor
~ OTA ICS Compatible + Newer Custom Rom's
~ OC now Stable up to 1.44GHz ( GPU FB Fixed as well at this speed )
~ Live OC Supported (limited to 115%, anything over that wont take effect)
~ Data Corruption is now Fixed
~ Reboots Fixed
~ 100Mhz Screen on Idle Fixed
~ GPS Tweaks is unknown via NS4G User at this current time.
~ ro.secure=0
~ Voodoo Sound
~ Voodoo Color
~ BLD Supported
~ BLN Supported
~ Touch-wake Supported
~ Deep Idle ( DIDLE ) Not to be confused with Ezekeel Deep_Idle Mod
~ BT Sleep ( Needs Patched Rom to work correctly )
~ Stock Voltage
~ Added Bigmem patch
~ TUN is now built-in
~ CIFS is now built-in
~ Battery 100% fix ( Only Cosmetic, still stops charging at 96% like all android Devices )
~ NSTools Supported
~ added dm-cache
~ kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg
~ BFQ Supported
~ CFQ Supported
~ SIO Supported
~ Noop Supported
~ Deadline Supported
~ readahead edits
~ block: limit default readahead size for small devices
~ ext4 edits
~ init.d Supported
~ *Governors Supported* ~
* lulzactive
* minmax
* lazy
* smartassV2
* smartass
* interactive
* conservative
* ondemand
* userspace
* powersave
* scary ( Fixed Sleep of Death )
* performance
Typical Questions Asked:
~ Switch you Mobile browser to desktop mode to download the link..
~ No I won't be adding Lazy Gov.
~ BLX patch is not needed, the charging is fixed via the battery.c file in the kernel source
~ Deep Idle stats will never show! It's not the same!!!!
~ Yes, Battery life is awesome
~ Yes, Benchmarks will be lower than the last builds.... However what little hit we took we gained in battery.
Installing?
Boot into CWM & Flash.... Reboot & Enjoy!
Kernel Source: https://github.com/eugene373/Nexus_S_ICS
NSTools by arifhn:
NSTools
Download: BLN / BLD / Touch-wake Turned Off Version & Needs NSTools to Activate
3.1.10_ANY-KERNEL-SPEEDY-7.zip
syntax_gosong said:
* For those who ask about the Kernel Governors, I/O Schedulers, etc *
You can refer your questions here :
http://forum.xda-developers.com/showthread.php?t=1369817
http://forum.xda-developers.com/showthread.php?t=1369817
Many thanks to droidphile for the useful explanations.
Click to expand...
Click to collapse
Special Thanks:
To the Voodoo Man Supercurio, For Giving use Voodoo
To the Man Ezekeel!! For all the wonderful work & Patches he provides!!!!!!
Thanks to Neldar! BLN is awesome right!! ( Please buy his app to show Support )
Thanks to Morfic for overclock
Thanks to arifhn for NSTools
Thanks to Koush for Any Kernel
sweet. Do we have to wait for so long for oc to be enabled in stock ics?
Sent from my Nexus S using xda premium
gonna wait for a flashable zip file
Nice thanks.
Sent from my Nexus S using Tapatalk
---------- Post added at 12:39 AM ---------- Previous post was at 12:35 AM ----------
one question u know whats different on this one from 3.0.8?
Kernel works really nice on my AOSP ROM
Ready for another ICS
TrueYears said:
gonna wait for a flashable zip file
Click to expand...
Click to collapse
here is flashable version... : http://www.mediafire.com/?44xggd3apnta5f5
this kernel is working great for me.. i got better result from quadrant too
evilisto said:
here is flashable version... : http://www.mediafire.com/?44xggd3apnta5f5
this kernel is working great for me.. i got better result from quadrant too
Click to expand...
Click to collapse
I think he means flashable rom zip file.
after flash it, why my phone silence
evilisto said:
here is flashable version... : http://www.mediafire.com/?44xggd3apnta5f5
this kernel is working great for me.. i got better result from quadrant too
Click to expand...
Click to collapse
Can confirm that after flashing this specific file in recovery I no longer have any sound either
Better stick with fastboot or repack the CWM version
-peace-
Very thankful to see another kernel from eugene. Been using his kernels since my SGS Vibrant days.
Sent from my Google Nexus S using xda premium
JY02800190 said:
after flash it, why my phone silence
Click to expand...
Click to collapse
I forgot to config the sound driver, doing that now & posting a new boot.img
Sound is now Fixed.... with that bug out of the way, signing off until after X-Mas
eugene373 said:
Sound is now Fixed.... with that bug out of the way, signing off until after X-Mas
Click to expand...
Click to collapse
Thank you kind Sir. may Santa bring you everything on your Xmas list
CWM flashable
Here's a repack of evilisto's flashable zip now with eugene373's fixed(sound) kernel.
All creds to them - Thanks guys
Smooooth kernal. Lookin forward to further development
-peace-
edit ---link removed---
In case you're wondering "What's New?"
With the release of real-time (RT) kernel 3.0.9-rt25, Thomas Gleixner has declared that the Linux 3.0-based RT tree is now ready for use in live systems. He noted that this new version series represents a major leap forward and that development has run pretty smoothly, despite major revisions to many of the core techniques.
Gleixner has now handed over responsibility for maintaining RT patches for Linux 3.0 to Steven Rostedt, who recently released a pre-release version of Linux 3.0.9-rt26 for evaluation. Gleixner has ported the changes aimed at improving real-time properties to pre-release versions of Linux 3.2 (1, 2, 3). The RT patch has shrunk substantially in the process, as some of the changes have now been incorporated into the main development tree.
Kernel version status In view of the maturity of the RT patch for Linux 3.0, Greg Kroah-Hartman is ending support for the 2.6.33 series with the release of Linux 2.6.33.20. As of late it had been being maintained solely for the benefit of real-time developers, with the previous stable real-time patch based on Linux 2.6.33.
Kroah-Hartman has also released stable versions 2.6.32.48, 3.0.9 and 3.1.1. The two 3.x stable versions each include more than 200 minor enhancements and bug fixes. The 3.0.10 and 3.1.2 kernels have just been released too. Most stable and long term kernels are now available from a git repository on Kernel.org.
As predicted in the first Kernel Log in the "Coming in 3.2" series, last week Linus Torvalds released the second pre-release version of Linux 3.2, with the third set to follow shortly. The latter will see the removal of a system for user-friendly disk names, merged during the 3.2 merge window, which has since come in for flak from a number of key kernel hackers. The developer behind the patch now plans to implement a userspace solution to achieve the same objective.
RC3 includes a number of patches produced using information gleaned from Windows drivers which deactivate power saving feature ASPM (Active State Power Management) with specific hardware configurations. The patch to restore the PCIe power-saving technology to being active by default on many systems is not, however, set to make its way into the kernel until Linux 3.3. Fedora and Ubuntu have nonetheless already integrated this change into some of their kernels for testing purposes.
Source: http://www.h-online.com/open/features/Kernel-Log-real-time-kernel-goes-Linux-3-0-1382791.html
As sweet as a nut - many thanks Eugene.
Anyone know if its insecured ?
3.0.13 now Posted...
What's the advantage of this new Kernel compared to the stock 3.0.8 kernel ?
eugene373 said:
3.0.13 now Posted...
Click to expand...
Click to collapse
is that official from google..??
[KERNEL] [P6800 JB 4.1.2] [22 Mar] ROOT | ExTweaks | exFAT | SkyHigh Kernel [5.0.0 FINAL]
** FOR P6800 (GSM/3G) device running JB 4.1.2 DXMD3 ONLY !! **
I am UpInTheAir part time kernel dev (hack) and Chef of SGT 7.7 JB & ICS ROMs, and now bring to you my P6800 Jellybean SkyHigh Kernel.
-- STABLE FINAL RELEASE --
* I don't pretend to know everything, so if you can be constructive and help out this project, please do so. You will find allot of answers by searching gitHub, XDA and SEARCH
FEATURES
* Based on official Samsung source JB DXMD3
* AUTO ROOT (only if you don't already have it)
insecure kernel
su binary 1.91
SuperSU 1.91
busyBox 1.20.2 linusyang installed to system/sbin
* STABLE - under SkyHigh "default" values & conditions
* ExTweaks app support for almost all kernel configurations + more !!
Many descriptions are in the app ! If you require more info, don't be lazy, please SEARCH like I did !
CPU
Boot boost CPU freq
Boost CPU freq (not fully tested)
Cortex wakeup boost (not fully tested)
Max normal freq
CPU freq OC / UC
CFS settings – Arch power
CPU idle mode (sleep & awake)
Scaling max suspend freq
Scaling min suspend freq
Scaling min standby freq
CPU temp throttle
CPU VOLTAGE
Set voltage individually for each 18-step freq
CPU TUNING (Awake & Sleep)
Set default CPU governor
Set governor configuration
Enable/disable hotplug
BUS
Bus voltage group
Thresholds
IO Tuning
Int/ext sdcard read-ahead cache
Dynamic Fsync control
Dynamic dirty page writeback control
IO scheduler (awake & sleep)
MEMORY TUNING
OOM control (screen on/off)
Dirty background ratio
Dirty ratio
Clean RAM cache
zRAM
Swappiness
zRAM stats
KSM control
GPU CONTROL
VPLL/MPLL mode
Freq control
Voltage control
Threshold control
Stay-count control
DISPLAY
FB early suspend delay (CRT TV off animation for SUPPORTED ROM)
Touch screen sensitivity
SOUND
Master volume gain
Headphone
Mic
Speaker
TWEAKS
- CortexBrain-Background-Process control
- Check CortexBrain-Background-Process Service
TCP security
TCP speed
TCP RAM
IPV6 (enabled by default - does not actually switch off)
CPU
Memory
System
Kernel
IO
OTHER
- Cron Task Control
- Test Cron task service
- Cron reset
Clean RAM cache task every hour
Update AD blocker task every week
DB optimizing (sqlite3) task every day
Clean app cache task every day
Zipalign task every day
fstrim lagfix task every day
Cron test task jobs
Zipalign apps now
Zipalign on boot
DB optimization (sqlite3) now
DB optimization (sqlite3) on boot
Battery scaling calibration (fuel-gauge reset) now
Ad blocker update now
Remove Ad blocker
FILE SYSTEM MAINTENANCE / REPAIR
Partitions scan
Data FS repair on boot
extSdCard repair on boot
Fix permissions on boot
Fix permissions now
Trim FS partitions (fstrim lagfix) on boot
Trim FS partitions (fstrim lagfix) now
INIT.D SUPPORT
Enable init.d script run control
USB MASS STORAGE (UMS) MODE
MTP <> Mass storage mode
WIFI & GPS
Clean WIFI lease
TCP congestion control
GPS region
GPS zone check
Update time
ROOT
Install root now
Remove root now
Root check
Auto install root on boot
MODULES
Frandom control
XPAD control
ISO CD-ROM control
UDF CD-ROM/DVD control
PROFILES
Profile check
UpInTheAir & SkyHigh Default (you can configure & save values for each, but not change the actual profile name)
BACKUP & RESTORE
Backup User settings now
Restore User settings now
RE-BOOT
Re-boot into Recovery
BUG-REPORT
Kernel bug-report
App bug-report
Android logger control
Kernel printk control
Module logger control
INFO
* SkyHigh default CPU min/max 200 > 1400 MHz (13-step)
* 18-step CPU 100 > 1800 MHz (Recommend setting 200-1400/1600 MHz)
Default = 13-step 200 > 1400 MHz
Stock = 6-step 200 > 1400 MHz
* No UV for stock frequencies 200-500-800-1000-1200-1400 MHz
* 4-step GPU : Default = 160-200-267-400 MHz
MPLL mode = 4-step GPU (default)
Stock = 2-step GPU (160-267 MHz)
Min freq = 50 MHz
Max MPLL freq = 400 MHz
Max VPLL freq = 520 MHz
Voltage = 800 > 1200 mV (+/- 50 mV increments)
* GPU UV / UC / OC
160 MHz = 950 mV (-50 mV > stock 1000 mV)
200 MHz = 1000 mv
267 MHz = 1050 mV (-50 mV > stock 1100 mV)
400 MHz = 1100 mV
* GPU Control
freq clock
voltage
step thresholds
stay counts
GPU BENCHMARK BEFORE (3DMark app)
{
"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"
}
GPU BENCHMARK AFTER @ 400 MHz (3DMark app)
* GPU VPLL mode optional
For devices that can't handle VPLL – use MPLL mode instead
http://forum.xda-developers.com/showpost.php?p=33720501&postcount=4181&nocache=1&z=1048045007703282
* Busfreq up & down threshold control
Stock / SkyHigh default = 23
* Busfreq (memory) voltage group
default group = 1 (stock)
available group options 1 > 7
L0 = 400 L1 = 267 L2 = 160 MHz
1 > {1150000, 1050000, 1050000} SkyHigh default / stock
2 > {1125000, 1025000, 1025000}
3 > {1100000, 1000000, 1000000}
4 > {1075000, 975000, 975000}
5 > {1050000, 950000, 950000}
6 > {1025000, 950000, 925000}
7 > {1000000, 925000, 900000}
* Set L2 bus (memory) speed from 133 > 160 MHz
- Default MHz now:
L0 = 400
L1 = 267
L2 = 160 MHz / 1000 mV (stock = 133 MHz / 950 mV)
* Adaptive vfs_cache_pressure on suspend / resume
Hard coded values :
- Set @ 10 = save battery on device suspend
- Set @ 60 = better smoothness on device resume
Low vfs_cache pressure values save battery while idle, while a low value also causes stutter with longer up times.
* Governors
pegasusq = SkyHigh default (siyah kernel version & "freq for responsiveness" tweaked to 500 MHz by me)
HYPER
scary
wheatley
abyssplug
lulzactiveq (siyah kernel version & tweaked by me)
lazy
hotplug
ondemand
performance
ZZMoove 0.7d
* IO schedulers
SIO = SkyHigh default
ROW
VR
NOOP
Deadline
CFQ
* SOUND CONTROL via ExTweaks app
* Thunderbolt scheduler IO Tweaks [pikachu01]
* Implemented kernel to report USB trickle charge (previously just reports discharging).
- Those devices without modified SystemUI.apk will now show battery charging animation whilst on USB power source
* Force USB charging source to be detected as AC
- faster USB charge using same circuitry
- limited by:
1. charging source max output
2. kernel - up to max 1500 mA (same is actual AC)
* Auto set init.d scripts to 777 – no need to manually set script permissions, just drop in & reboot
* Reduced GUI lag
- Frandom
- fstrim lagfix - NOT ENABLED BY DEFAULT
- Disabled gentle fair sleepers
- RAM management OOM adj & minfree values from V6SuperCharger
* Improved touch-screen sensitivity (on both battery and charge)
* Mount partitions NOATIME and NODIRATIME by default
* R/W and auto-mounting of exFAT USB-OTG & external sdcard using official Samsung Open Source modules v1.2.5
* modded ROM /system/etc/vold.fstab to permit exFAT mounting
* NTFS R/W OTG file system support (require app to mount)
* UDF/ISO file system support - BluRay (require app to mount) - not tested !
* Network filesystem support
In-built CIFS
In-built NFS (not tested)
* TCP algorithms
- cubic = default
- reno
- westwood+ (some users of other devices have reported faster network throughput speeds)
* In-built zRAM support
* LZ4 compression implemented & enabled for zRAM [psndna88 & Yank555.lu]
* Support paging of anonymous memory (Swap)
* General optimized for size
* Kernel compression = xz
* Support for iPad, iPhone, iPhone_3G/S, iPhone_4/4S, iPhone_5 (not tested as I don't own "rotten fruit" )
* UV motor -100 mV (3.1V → 3.0V)
* UV LED -100 mV (3.2V → 3.1V)
* fbearlysuspend control - allow CRT-off animation in SUPPORTED ROMs)
* Thermal throttle control (default on) – be careful here, do you want to melt your CPU?
* Dynamic read-ahead implemented and set at 1024 KB (variable)
* Int/External sdcard read ahead cache = variable KB
* Internal & external sdcard IO schedulers = SIO
* Dynamic FSync control v1.2 implemented and enabled
* Dynamic management of dirty page writebacks
* Android Logger Control disabled
* Linux printk Control disabled
* KSM support
* Custom bootanimation support
* Custom boot sound support
* Support for XPAD gamepad & rumblepad controller
* Reduce Android logger RAM usage
* Disabled kernel debugging to reduce zImage size
* Disabled some module logging
* Disable mali tracking debug
* Disable zRAM debug
* Triangle Away app support
* vm swappiness = 20 (performance)
* Free pagecache. dentries and inodes will be managed by /proc/sys/vm/vfs_cache_pressure
echo "1" > /proc/sys/vm/drop_caches
* System property accessory tweak values from V6SuperCharger
dalvik.vm.heapgrowthlimit 130m
dalvik.vm.heapsize 130m
persist.sys.purgeable_assets 1
windowsmgr.max_events_per_sec 90 (200 set as SkyHigh default)
* Virtual memory & kernel tweak
# values from V6SuperCharger & Kick Ass Kernelizer [[email protected]]
echo "10" > /proc/sys/fs/lease-break-time
echo "0" > /proc/sys/kernel/panic
echo "0" > /proc/sys/kernel/panic_on_oops
echo "0" > /proc/sys/vm/block_dump
echo "60" > /proc/sys/vm/dirty_background_ratio
echo "95" > /proc/sys/vm/dirty_ratio
echo "0" > /proc/sys/vm/laptop_mode
echo "15360" > /proc/sys/vm/min_free_kbytes
echo "4" > /proc/sys/vm/min_free_order_shift
echo "0" > /proc/sys/vm/oom_dump_tasks
echo "0" > /proc/sys/vm/oom_kill_allocating_task
echo "1" > /proc/sys/vm/overcommit_memory
echo "0" > /proc/sys/vm/panic_on_oom
#echo "20" > /proc/sys/vm/swappiness ########### Already implemented
#echo "10" > /proc/sys/vm/vfs_cache_pressure ########### Implemented adaptive vfs_cache_pressure on suspend (10) / resume (60)
* Misc tweaks for battery life
# values from V6SuperCharger & Kick Ass Kernelizer [[email protected]]
echo "65536" > /proc/sys/kernel/msgmax
echo "2048" > /proc/sys/kernel/msgmni
echo "500 512000 64 2048" > /proc/sys/kernel/sem
echo "2097152" > /proc/sys/kernel/shmall
echo "268435456" > /proc/sys/kernel/shmmax
echo "4096" > /proc/sys/kernel/shmmni
#
echo "524288" > /proc/sys/fs/file-max
echo "32000" > /proc/sys/fs/inotify/max_queued_events
echo "256" > /proc/sys/fs/inotify/max_user_instances
echo "10240" > /proc/sys/fs/inotify/max_user_watches
echo "0" > /proc/sys/kernel/sched_child_runs_first
echo "524288" > /proc/sys/kernel/threads-max
* TCP Speed & Security
# values from V6SuperCharger & Kick Ass Kernelizer [[email protected]]
# 3G TurboCharger Enhancement
#
# Google's public DNS settings
#
/system/bin/setprop net.dns1 8.8.8.8 ########### Not sticking
/system/bin/setprop net.dns2 8.8.4.4
#
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax
/system/bin/setprop net.tcp.buffersize.default 6144,87380,110208,6144,16384,110208
/system/bin/setprop net.tcp.buffersize.wifi 262144,524288,1048576,262144,524288,1048576
/system/bin/setprop net.tcp.buffersize.lte 262144,524288,3145728,262144,524288,3145728
/system/bin/setprop net.tcp.buffersize.hsdpa 6144,262144,1048576,6144,262144,1048576
/system/bin/setprop net.tcp.buffersize.evdo_b 6144,262144,1048576,6144,262144,1048576
/system/bin/setprop net.tcp.buffersize.umts 6144,87380,110208,6144,16384,110208
/system/bin/setprop net.tcp.buffersize.hspa 6144,87380,262144,6144,16384,262144
/system/bin/setprop net.tcp.buffersize.gprs 6144,8760,11680,6144,8760,11680
/system/bin/setprop net.tcp.buffersize.edge 6144,26280,35040,6144,16384,35040
#
# Queue size modifications
echo "20480" > /proc/sys/net/core/optmem_max
#echo "262144" > /proc/sys/net/core/rmem_default
echo "1048576" > /proc/sys/net/core/rmem_max
#echo "262144" > /proc/sys/net/core/wmem_default
echo "1048576" > /proc/sys/net/core/wmem_max
echo "50" > /proc/sys/net/unix/max_dgram_qlen
#
# Be sure that autotuning is in effect
echo "1" > /proc/sys/net/ipv4/tcp_moderate_rcvbuf
#
echo "0" > /proc/sys/net/ipv4/ip_no_pmtu_disc
echo "1" > /proc/sys/net/ipv4/route/flush
echo "0" > /proc/sys/net/ipv4/tcp_ecn
echo "1" > /proc/sys/net/ipv4/tcp_fack
echo "1" > /proc/sys/net/ipv4/tcp_rfc1337
#echo "6144 87380 1048576" > /proc/sys/net/ipv4/tcp_rmem ########### Not sticking
echo "1" > /proc/sys/net/ipv4/tcp_sack
echo "0" > /proc/sys/net/ipv4/tcp_timestamps
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling
#echo "6144 87380 1048576" > /proc/sys/net/ipv4/tcp_wmem ########### Not sticking
echo "6144" > /proc/sys/net/ipv4/udp_rmem_min
echo "6144" > /proc/sys/net/ipv4/udp_wmem_min
#
# Re-use sockets in time-wait state
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse
#
# Hardening the TCP/IP stack to SYN attacks
echo "1024" > /proc/sys/net/ipv4/tcp_max_syn_backlog
echo "2" > /proc/sys/net/ipv4/tcp_syn_retries
echo "2" > /proc/sys/net/ipv4/tcp_synack_retries
#
# Bump up tw_buckets in case we get DoS'd
echo "16384" > /proc/sys/net/ipv4/tcp_max_tw_buckets
#
# Ignore pings
echo "1" > /proc/sys/net/ipv4/icmp_echo_ignore_all
#
# Don't reply to broadcasts (prevents joining a smurf attack)
echo "1" > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
#
# Enable bad error message protection (should be enabled by default)
echo "1" > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
#
# Don't cache connection metrics from previous connection
echo "1" > /proc/sys/net/ipv4/tcp_no_metrics_save
#
echo "15" > /proc/sys/net/ipv4/tcp_fin_timeout
echo "30" > /proc/sys/net/ipv4/tcp_keepalive_intvl
echo "5" > /proc/sys/net/ipv4/tcp_keepalive_probes
echo "1800" > /proc/sys/net/ipv4/tcp_keepalive_time
#
# Don't pass traffic between networks or act as a router
# Disable IP Packet forwarding (should be disabled already)
echo "0" > /proc/sys/net/ipv4/ip_forward
#
echo "0" > /proc/sys/net/ipv4/conf/all/send_redirects
echo "0" > /proc/sys/net/ipv4/conf/default/send_redirects
#
# Enable spoofing protection (turn on reverse packet filtering)
echo "1" > /proc/sys/net/ipv4/conf/all/rp_filter
echo "1" > /proc/sys/net/ipv4/conf/default/rp_filter
#
# Don't accept source routing
echo "0" > /proc/sys/net/ipv4/conf/all/accept_source_route
echo "0" > /proc/sys/net/ipv4/conf/default/accept_source_route
#
# Don't accept redirects
echo "0" > /proc/sys/net/ipv4/conf/all/accept_redirects
echo "0" > /proc/sys/net/ipv4/conf/all/secure_redirects
echo "0" > /proc/sys/net/ipv4/conf/default/accept_redirects
echo "0" > /proc/sys/net/ipv4/conf/default/secure_redirects
* Power saving tweaks
pm.sleep_mode 1
ro.ril.disable.power.collapse 1
wifi.supplicant_scan_interval 180
CREDITS
* My family !!
* Samsung
* XDA
* wanam repo, ezykernel ICS diff, Ryuinferno, CM, boeffla, GM, redpill more to add yet
* Chainfire for root
* GM - siyah kernel
* AndreiLux
* dorimanx
* Christopher83
* zeppelinrox - V6SuperCharger - KAK - 3G TurboCharger values and Fix Emissions script
* idcrisis for permission to implement CrossBreeder entropy into kernel - no success as yet...
* pikachu01 FOR SOME tHUNDERBOLT TWEAKS
* Suxsem for fstrim
* XDA devs that I cherry pick code, values & ideas from. The list is never ending...
* edan1979 for excellent feedback & also nutley for volunteering to test
GPL COMPLIANT - SOURCE: >> GitHub
.
Download & change-log
DOWNLOAD & CHANGE-LOG
** DISCLAIMER : FLASH AT YOUR OWN RISK **
WARNING :
* Under-volting can cause instability
* Over-clocking can cause freeze/reboot, heat & damage to CPU, GPU or other hardware
* Any customizations may void warranty
P6800 GSM/3G JB 4.1.2 DXMD3 ONLY
INSTALLATION
** DO NOT USE ANY 3RD PARTY TWEAKS OR “PERFORMANCE” TYPE APPS & REMOVE ALL ROM /KERNEL SCRIPTS FROM /system/etc/init.d FOLDER **
1. NANDROID (just in case)
2. Have installed any P6800 JB 4.1.2 ROM based from official Samsung sources
3. Remove any previous CPU control settings from starting at boot, remove any 3rd party tweaks etc
4. Flash in custom recovery (CWM or TWRP) to auto wipe previous kernel profile remnants ie. crontab. logs & /data/.siyah folder
5. If requested by Recovery to install SU, DO NOT. Instead - Let the kernel do it on boot
SkyHigh Kernel : Latest release is v5.0.0 FINAL ExTweaks Edition
CWM.zip v5.0.0 FINAL http://d-h.st/n3S
Archive : Working CWM Official Released Legacy Versions (UNSUPPORTED)
v0.7
v1.0.3
v2.0.8
v2.1.0
v2.2.0
v2.7.0
v2.8.0
v3.2.0
v3.3.0
v3.4.2
v3.5.0
v3.6.0
v3.7.0
v3.8.0
v3.9.1
v4.0.0
v4.1.0
v4.2.0 - Stable for some users (4-step GPU control)
v4.3.0
v4.4.0
v4.6.0
v4.6.1
v4.7.0b
v4.8.0b
v4.9.0b
-------------------------------------------------------------------
Stock Kernel :
CWM.zip DXMD3 http://d-h.st/tKE
ODIN.tar DXMD3 http://d-h.st/yxr
++ PLEASE DO NOT REDISTRIBUTE - LINK HERE INSTEAD ++
BUGS
* Check if it is actually a stock firmware bug first using stock kernel -BEFORE- posting in this thread or elsewhere
1. Random screen tint reported on both stock & SkyHigh kernels using CPU control app (Read Post #3)
2. Screen OFF reboot with ONLY SkyHigh DEFAULT kernel settings ( no "performance" type apps, scripts etc) Please read ISSUES section for help or flash v4.2.0 for stabilty
.
.
FAQ & HELP
FAQ & HELP
MY RECOMMENDATIONS
* Governor = pegasusq, lulzactiveq, or ZZMoove
* IMO = Performance → → Battery
1. on-demand
2. pegasusq (snappy, but easier on battery than on-demand)
3. lulzactiveq
4. ZZMoove
* Scheduler = SIO
* CPU freq = 200-1400/1600 MHz
* CPU vdd levels = SkyHigh "defaults"
* Enable zRAM for better mulitasking
* CPU Control app = ExTWeaks
Don't forget to use only one Control app at a time. They will conflict !
ISSUES?
1 Remove any kernel related init.d tweaks, 3rd party performance type apps etc
2 Wipe your CPU control app(s) data (menu > settings > applications > "your control app(s)" > clear data/cache)
3 Use only ONE CPU control app ! USE EXTweaks
4 Open SuperSU app > settings > full unroot (or unroot from with EXTweaks options)
5 Boot into recovery and wipe cache & dalvik cache
6 Re-flash SkyHigh Kernel
7 If requested by recovery - DO NOT install root (let the kernel do it)
9 Reboot
8 If still issue such as bootloop etc, try using MPLL mode for GPU, and or increase GPU voltages +50 mV
9 Try a kernel "legacy" versions
10 Back to stock for you
RANDOM SCREEN TINT AFTER CHANGING GOVERNOR
* Turn screen OFF-ON
* Use only SkyHigh defaults values
* Don't use a CPU control app to change kernel settings - Use init.d script instead
* OR IF IT BOTHERS YOU,...... DON'T USE THE KERNEL
zRAM
Info here : (INFO)What is zram and how does it work???
LOGS
* You can find various ExTweaks logs in the /data folder:
/data/.siyah
/data/extSdCard_fix.log
/data/fsrepair.log
/data/fstrim_lagfix.log
/data/Ran_FixEmissions.log
/data/sqlite.log
/data/zipalign.db
/data/zipalign.log
/data/crontab
PREVENT/REDUCE SCREEN-OFF FLICKER FOR CRT-OFF ANIMATION ENABLED ROMs
* Set fbearlysuspend msleep between 100 and 500 ms
* Set to 0 if you haven't any CRT-off animation mod
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
* [Christopher83]
This feature allows to have two different intervals for dirty page
writebacks and to dynamically manage them when the system has been
resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature,
set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page
writebacks when the system is active (screen on)
- dirty_writeback_suspend_centisecs is the interval for the dirty page
writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's patch:
https://github.com/franciscofranco/mako/commit/34d79548cf16b69c7d0154836018e7f258a22947
Click to expand...
Click to collapse
WHAT IS A CUSTOM KERNEL
* First of all, watch this : Android Basics 101: Understanding Kernels – XDA Developer TV
* Is usually' modified and complied from source.
* My very first successfully compiled kernel just included the "SkyHigh" name. I suppose you could call that a modified "stock" kernel. On the other hand, you could also argue that any firmware modified from either official or built from sources could be called "custom".
HAVE THE STOCK KERNELS ATTACHED BEEN MODIFIED
* If you are referring to the stock MD3 kernels in Post #2, NO
* I just extracted the zImage from official firmware and repackaged for flashing via custom recovery or Odin. There are no changes made to the zImage. I have no plans to modify these.
ENTROPY
* MAX pool sixe 4096
* It's not instant, just use your device and it will grow.
* No need for entropy generator apps that consume battery (use extra CPU cycles)
WHAT ARE GOVERNORS / SCHEDULERS ETC
* Excellent source of info by droidphile :
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
FSTRIM LAGFIX
* fstrim is more of a maintenance binary. Android 4.2.2 and below are more prone to lag over time and prevalent as your internal storage is used up.
* Trims system, preload, data & cache partitions
* fstrim binary set to run by init.d 90lagfix script after boot to reduce impact on boot time
* A manual reboot once a week is suggested. Those users who have ample internal storage and or recently formatted their partitions via ROM flash or Nandroid restore may see little difference for now.
* More info : Google yourself or Nexus Storage Performance Over Time & TRIM 20130829
CUSTOM BOOT ANIMATION SUPPORT
1. copy bootanimation.zip to /system/media/ folder (mount folder r/w to paste)
2. ensure set permissions rw-rw-rw-
3. reboot
NOTE :
* For any further help or instructions for bootanimation, please open your own forum Q&A thread or post in a relevant bootanimation thread. There are many already built and can be found by searching.
* The size we need for our tab is 800x1280 or 1280x800 (depending on portrait or landscape)
CUSTOM BOOT SOUND SUPPORT
* Place custom boot sound PowerOn.ogg in /system/media
* To mute, create an empty file named mute in /system/media
* To unmute, create an empty file named unmute in /system/media
* To restore original boot sound, create an empty file named ori_sound in /system/media
* Reboot device after each process
NOTE :
* when creating a custom boot sound, make sure you use a capital "P" and "O" in PowerOn.ogg
* I will not provide a tutorial for creating boot sounds, you can Google yourself
BENCH-MARKING
Freeze or Re-Boot
1 Try increase CPU 1600 Mhz voltage by +25 mV or +50 mV. I would not recommend any more than that !
2 Lower CPU OC back to stock max 1400 MHz setting
3 To find out which frequency cause the freeze :
a) If you have UV the CPU and the device freeze, obviously you need to increase the voltage to a particular frequency step(s)
b) Do a stress test with SetCPU (or other app) and lock your max frequency for each step (DO NOT SET ON BOOT WHILST TESTING)
4 Try a different governor
5 Use a different benchmark app/tool
AnTuTu Crashes?
* Try another benchmark app !
Low Bench-Marking Scores
* Consectutive tests as well as OC may heat the CPU high enough where thermal limiting occurs. Well here you go........... I observed my CPU regularly drop to 800 MHz after hitting a thermal limit during testing.
Here's the proof !
https://github.com/UpInTheAir/P6800_JB_SkyHigh_Kernel/blob/master/arch/arm/mach-exynos/mach-px.c
Code:
#ifdef CONFIG_EXYNOS4_SETUP_THERMAL
/* below temperature base on the celcius degree */
struct s5p_platform_tmu px_tmu_data __initdata = {
.ts = {
[COLOR="Red"].stop_1st_throttle = 61,
.start_1st_throttle = 64,[/COLOR]
.stop_2nd_throttle = 87,
.start_2nd_throttle = 103,
.start_tripping = 110,
.start_emergency = 120,
.stop_mem_throttle = 80,
.start_mem_throttle = 85,
},
.cpufreq = {
.limit_1st_throttle = [COLOR="Red"]800000[/COLOR], /* 800MHz in KHz order */
.limit_2nd_throttle = 200000, /* 200MHz in KHz order */
* With some undervolt and governor tuning, little OC impact will be felt on battery. Not everyone fixes their CPU to max with performance governor so, providing your hardware can handle it, some OC should be OK for everyday use as the CPU only briefly scales to max freq with the 'right' governor.
* As you can see, this could be easily changed to allow (cheat) in benchmarks. This won't make much difference to everyday use, but IMO shouldn't be touched. My silicon may not handle it
RESET CUSTOM FLASH COUNTER
*There is a Samsung Galaxy Tab 7.7 flash counter introduced for P6800 JB 4.1.2 DXMD3, so any modified ROM, kernel or recovery flashed via PC Odin will increase the counter.
1. Have installed my P6810/P6800 SkyHigh kernel for JB 4.1.2 (patched for triangle away compatibility)
2. Install triangle away app v3.26
3. Reset counter
4. Reboot as requested
5. To check > open app again, or, power off and enter download mode
* Your custom ROM, kernel, recovery & root remain intact
Anything else, IF I find the time
.
UpInTheAir said:
I am UpInTheAir and Chef of SGT 7.7 ICS ROMs, and now bring to you my P6800 Jellybean SkyHigh Kernel.
** FOR P6800 GSM/3G device running JB 4.1.2 DXMD3 ONLY !! **
-- STABLE WORK-IN-PROGRESS --
* I am NOT a recognised developer, and don't actually use the P6800, but thought I would help out this forum by trying to develop a P6800 JB kernel.
* I don't pretend to know everything, so if you can be constructive and help out this project, please do so. You will find allot of answers by searching XDA and Google
FEATURES
* Based on official Samsung source MD3
* Default CPU max 1400 MHz
* OC to max 1600 MHz (support with CPU control app)
* CPU voltage control interface (UV support with a CPU control app)
* Enabled pegasus governor
* NTFS filesystem support
* Support paging of anonymous memory (Swap)
* General optimized for size
* Kernel compression = Gzip
* Default governor = on-demand
* Default IO scheduler = CFQ
* STABLE
TO DO
* Add more governors and IO schedulers
* UV GPU
* OC GPU
* UV screen
* Frandom support
* Other various useful modules
* Auto root
* init.d support
* STweaks support
* Increase AC & USB charge rate
* Custom bootanimation support
* Lots more
CREDITS
* Samsung
* XDA
* wanam repo, ezykernel ICS diff, more to add yet
* edan1979 for excellent feedback & also nutley for volunteering to test
* Development has been slow, but still progressing.......
* Things will speed up (time permitting) once JB source is released for my P6810 model and I can test changes on my own device and subsequent mirror the development
* SOURCE: Still being uploaded to github, and commits will be reflected a soon as I'm home (currently away) and PC stops freezing. Please be patient on this.
DOWNLOAD & CHANGE-LOG in Post #2
FAQ & HELP in Post #3
.
Click to expand...
Click to collapse
Nice!
I was planning to do this for sometime but I'm stuck at other things. I have already prepared the config for 6810 and i815. If you have time, I can send you those files to build the kernel for p6810. Hoping it will help you creating a custom stock rom for p6810 before Samsung!
Thanks again for contribution to our community! :good:
daniel_hk said:
Nice!
I was planning to do it for sometime but I'm stuck at other things. I have already prepared the config for 6810 and i815. If you have time, I can send you those files to build the kernel for p6810. Hoping it will help you creating a custom stock rom for p6810 before Samsung!
Thanks again for contribution to our community! :good:
Click to expand...
Click to collapse
Sounds great. Thanks !
Much easier to build and test with device in hand, so hoping for the official P6810 JB update soon. Although appreciate what you bring to the community with JB, If Samsung haven't released it in the next month, probably sell the tab for the "next big thing", as long as it's 7 or 8 in...... My 9 yo boy wants the tab though, so things could still change
Sent from my GT-I9500 using xda premium
already flashed.
booting : ok
overclock to 1600: work
set pegasusq governor: work
will try to uv and report.
Sent from my GT-P6800 using Tapatalk HD
UpInTheAir said:
Sounds great. Thanks !
Much easier to build and test with device in hand, so hoping for the official P6810 JB update soon. Although appreciate what you bring to the community with JB, If Samsung haven't released it in the next month, probably sell the tab for the "next big thing", as long as it's 7 or 8 in...... My 9 yo boy wants the tab though, so things could still change
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Already sent the link in PM. It should work with the latest JB source for 6800.
Good luck and let's hear more good news!
Edit: attached here View attachment p8-wifi_defconfig.tar.gz
daniel_hk said:
Already sent the link in PM. It should work with the latest JB source for 6800.
Good luck and let's hear more good news!
Edit: attached here View attachment 1979341
Click to expand...
Click to collapse
Got it.
Thanks.
I'll just keep chipping away at the development until I have to go away to work again,.... probably early next month.
Sent from my GT-I9500 using xda premium
My 9 yo boy wants the tab though, so things could still change
Click to expand...
Click to collapse
Seems to me that a Tab 7.7 is about perfect for a little boy.
Keep it in the family:good:
Thanks dev for your kind support for the tab!
anyone try this kernel on the erobot rom yet ?
golfinggino said:
anyone try this kernel on the erobot rom yet ?
Click to expand...
Click to collapse
yes its working fine...
Hi, move to see that our device is not given up by developers
One request: after moving to JB I noticed that the sound is much lower in JB. Is it possible to fix it?
Sent from my GT-P6800 using Tapatalk 2
200mpx said:
Hi, move to see that our device is not given up by developers
One request: after moving to JB I noticed that the sound is much lower in JB. Is it possible to fix it?
Sent from my GT-P6800 using Tapatalk 2
Click to expand...
Click to collapse
Probably a way. In the mean time, take a look at this thread for SGS4 and see if it's applicable to your device....
Maybe with just a few minor adjustments, you can tweak from within your own ROM. Worth a look.
http://forum.xda-developers.com/sho...Modifications for i9500 (i9505 incompatible)!
Sent from my GT-I9500 using xda premium
Hi, how about NTFS filesystem support? I put via OTG usb flash drive 32gb formated as NTFS and tab can't recognize drive.
ROM is eRobot v1.0 and kernel is SkyHigh Kernel v0.7. May be i don't make some settings?
partola1 said:
Hi, how about NTFS filesystem support? I put via OTG usb flash drive 32gb formated as NTFS and tab can't recognize drive.
ROM is eRobot v1.0 and kernel is SkyHigh Kernel v0.7. May be i don't make some settings?
Click to expand...
Click to collapse
Firstly, does it work with your external sdcard formatted as NTFS ?
Secondly, Try USB OTG Helper app from Google Play and see if you have any luck mounting the USB stick.
Third, does it work with the stock kernel? You haven't said as I requested in OP...
Sent from my GT-I9500 using xda premium
Source : GitHub
I am now complying with the GPL and have managed to make the source/changes available for everyone to see.
Took a while, but eventually managed to upload and commit to GitHub.
Link now in OP
Now back to developing............
Edit: having a few git issues......
Edit2: Have gitHub back and correct. Just learning the basics and now lost some dev time because of it............. off to bed, always tomorrow
.
my uv setting
erobot rom
Sent from my GT-P6800 using Tapatalk HD
theerachai said:
my uv setting
erobot rom
Sent from my GT-P6800 using Tapatalk HD
Click to expand...
Click to collapse
Sweet !
Have you stress test each step to ensure stability?
You will need to lock the max frequency to that of each step, make sure it is NOT "set on boot" (during testing), so you can recover easily if device freeze or reboot occurs.
As a previous user didn't bother to give any further feedback on the NTFS, could someone using this kernel please check this:
1. Run Android Terminal Emulator app
2. su
3. Allow Superuser permission
4. lsmod
( the "l" is a lower case "L" )
What do you have? Please post a screenshot.
Also, check system/lib/modules for ntfs.ko
Cheers
Sent from my GT-I9500 using xda premium
|*KERNEL*| *hells-Core* L/KK<test b80>18thJuly<b73 stable>21stApr[Q&A][DISCUSSION]
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"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"
}
Hello fellas ! This is a thread for discussions, questions and answers
DOWNLOADS
mirror BOX
Kernel sources
CM 12.1: https://github.com/hellsgod/hells-Core-N4/commits/cm-12.1
Lollipop 5.1: https://github.com/hellsgod/hells-Core-N4/commits/l-mr1
AOSP: https://github.com/hellsgod/kernel_msm/commits/mr2-rebase
CM: https://github.com/hellsgod/kernel_msm/commits/cm-11-rebase
L: https://github.com/hellsgod/kernel_msm/commits/l-release
please check the 2nd , 3rd and the 4th post for some more info
Starting with version b40 ( JSS, JWR and CM) the multiboot patch by Tasssadar has been applied so it can be successfully used for.
Change logs b65 onwards
(b81)
-temp threshold set to 70°C
-few commits from M
-updated toolchain
(b80)
-updated BFQ-reverted gpu patches to fix chrome issues-some little fs fixes-hellsCode from @Maxr1998
(b79)
-added back Franco`s input listener-added back Franco`s conservative
-added input boost logic to hellsactive
(b78)
-Reverted back to GCC 4.9.3 and reverted conservative changes, switched back to hellsactive.
-should be back to the state of b73 now, except updated faux sound, 5.1.1 commits from google and bfq I/O sched.
(b75)
-faux sound updated-hopefully screen freeze issue fixed
(b74) http://forum.xda-developers.com/showpost.php?p=60370527&postcount=10313(b73)-Merged a patch from stratosk to temporarly disable dt2w with the power key.
-Enable it with "echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_pwr_disable"
- If you use your power key to turn off the screen, dt2w will be disabled, until you turn it on with the power button again.
(b70)-compiled with UBERTC-build flags from shamu/hammerhead(b69)-some fixes from linux upstream (3.4.y)
-new build flag (floop-nest-optimize)
-rtmutex fixes-sched/nohz/irq/genirq improvements from linux mainline
(b66)
-Upstream changes from Linux upstream (refer to git)
-Some fixes for hellsactive/interactive-Removed boost framework from msm_mpdecision
-Added cpu-boost for input boost and thread migrations-Improved cpu-boost-Make scheduler aware of frequency state-writeback fixes-some other little things
(b68)
-misc kgsl updates from caf-disabled some debugging and tracing
-optimizazions for interactive and hellsactive-misc other little fixes for rq_stats and sched
(b65-L)
-Merged latest "L" commits-Merged some upstream stuff from my hh branch
Change logs - old kernels
as from b47 to b64 the kernel it is compatible ONLY with android 4.4.3/4/L
from b65 onwards the kernel works for L only
(b64)-Several ARM patches for suspend/cacheflush/MPU (little longer wakeup time from time to time - but a little less drain during sleep)-New build flags-kgsl: Wakeup only for touch events (to make sure the input event handler is called only for touch inputs)(b63)-kgsl upstream for using with the new drivers-UIO fixes(b60)reverted slimbus changescompiled with new boostedtcmisc fixes(b58)-smp fixes from upstream-mm, vmscan fixes from upstream-random fixes from upstream-smartmax is back!-memcpy optimizations for cortex A15 (i know we don't have a "real" A15, but lets test it)-lib: Use neon-vfpv(b57)-kthread fixes-sched/nohz fixes-tick fixes-cgroup fixes-slimbus controller from hammerhead-some improvement for the slimbus-msm_mpdecision: a tad more conservative, check-enabled sched_mc and cpupower-set fiops as default scheduler-set sched_mc = 2(b56)-merged some upstream fixes-reverted two cpuidle patches(b55)(b54)-New governor: hellsactive*-speedup late resume (faster wakeup)-ext4 patches-pm/bus patches to prevent reported crashes (feedback needed!)-some other little fixes here and there-compiled with boostedtc 4.9.2 by @aznrice2k4*hellsactive:-Based upon intelliactive-removed input boost (we have an input boost in the hotplug driver)-removed sync feature-removed sampling down factorFollowing was added:-Align timer windows for all CPUs*It's more advantageous to evaluate all CPUs at same time so that interactive governor gets a complete picture of the load on each CPU at a specific time. It could also reduce number of speed changes made if there are many CPUs controlled by same policy. In addition, waking up all CPUs at same time would allow the cluster to go into a deeper sleep state when it's idle.-Reset last evaluated jiffy in idle callback*When CPU has been busy for a long time, last evaluated jiffy will be quite behind because the timer would have been canceled. We don't want to schedule a timer to fire in the past as load will always be 100%. Reset last evaluated jiffy so that timer will be scheduled for thenext window.-Round up timer_rate to match jiffy*Timers are scheduled in unit of jiffies. Round up timer_rate so that it matches the actual sampling period.-Use del_timer/add_timer_on to rearm timers*Replace mod_timer_pinned() with del_timer(), add_timer_on(). mod_timer_pinned() always adds timer onto current CPU. Interactive governor expects each CPU's timers to be running on the same CPU. If cpufreq_interactive_timer_resched() is called from another CPU, the timer will be armed on the wrong CPU.Replacing mod_timer_pinned() with del_timer() and add_timer_on() guarantees timers are still run on the right CPU even if another CPU reschedules the timer. This would provide more flexibility for future changes.-Support variable frequency calculations**Use a threshold value up to which we are evaluating the current speed weighted by current load against each new choice of speed. Above switch to the original frequency calculation proportional to load relative to the max possible frequency which allows for more dynamic and fair changes.Default threshold is policy->min which guarantees minimal freqs and energy usage during (offloaded) media playback.Also, choose the highest frequency below or at target, which generally saves us one freq level.-Don't scale beyond min if the load is low***-Thread migration commit***http://forum.xda-developers.com/showpost.php?p=55298804&postcount=7952I've just made some little changes on commits to suit my needs.credits:*CAF**myfluxi***franciscofranco(b53)-fixed cores getting stuck at input_boost if you've min 2 cores online: commit-updated msm_mpdecision with latest nexus 5 commits(b52)Compiled with Linaro 4.9.2-2014.08 by Christopher83New build flags from my hammerhead branch and @baromeCode is identical with b51. Just a newer toolchain and new build optimizations. Let's see if there are new stability issues. I think we've gained some little performance boost(b51)-Added some commits for the camera. We had some reports about reboots while using flash. Maybe there'll be less of them. I don't think I can fix them completely...-Removed some debugging-Some love for conservative governor (thx stratosk)-Added KERNEL_MODE_NEON-Changed some little things in the flags-Some little things here and there. Refer to git if you'd like to know it exactly (b50-test)-No problems occured, just merged some cool stuff -Merged backlight dimmer from stratosk-Added a ton of kgsl/adreno patches (L sources) and Franco`s interactive GPU governor-Added UIO Sharedmem (L sources)(b49-test)NO UNDERVLOTING ANYMORE , stock voltages by default Compiled with Linaro GCC-4.9.1 from Christopher83msm_mpdecision from showpintelliactive governor (default)ZEN scheduler (default)FIOPS schedulerMany many things under the hood (check git)Touch Wake (stratosk)DT2W (stratosk)and so on... ... ...http://forum.xda-developers.com/showpost.php?p=55061297&postcount=7579(b47-pre-release) STABLEMerged 4.4.3Update to Linux 3.4.93Linaro 4.9.1 from Christopher83IMPORTANT NOTE!!!!!IF YOU COME FROM HELLSDOCTOR, PLEASE REFLASH YOUR ROM OR CLEAR YOUR INIT.D FOLDER!!! OTHERWAYS YOU'LL HAVE FC's LIKE HELL!(b46 test 4)-OOM Upstream to 3.14 from faux-S2W Fixes from AK-Linux 3.4.86(b44-45)-Upstream auf 3.4.84-Linaro 4.8.3 03.2014-Cpuidle Commit-futex Upstream updated-jbd2 commits optimized-LoUIS Cache-81mhz(b44 test t3)Lowest frequency 81 MHz Updated to linux 3.4.79Merged CM optimizations(b43)-Rebase auf 4.4.1 Sourcen-Linux 3.4.76-S2W/dt2w Port vom N5-faux sound 3.2-suspend_freq auf max angehoben-Kleine Fixes usw. siehe Git(b40)-Upstream from 3.4.65 auf 3.4.66-ca. 100+ SLAB/SLUB/SL[AU]B/mm... Commits-Module Support (for TouchControl)-Conservative GPU: Thresholds set slightly differently ( probably a little smoother when scrolling)-S2W Fix from fluxi-kexec Support (MultiROM)-3 epoll Commits from Upstream (b39)-Rebase auf CM/JSS/JWR Sources-Compiled with Linaro 4.8.2.09 Toolchain-Upstream from 3.4.65-O3 Support with Custom Build Flags-Conservative GPU Governor-msm_hotplug Hotplug Control (Tanks geht an fluxi)-dynamic fsync off
-=-=-
Thank you @hellsgod !
do you want to show gratitude ? donate to hellsgod HERE
all credits to him , i`m just a twitter
-=-=-
Thank you also to these awesome guys @aznrice2k4for his great toolchain
@faux123
@franciscofranco
@myfluxi
@stratosk
@ak
@flar2
@neobuddy89
@Christopher83
@show-p1984
@mrg666
hells-Core on G+
hells-Core kernel bloghells-Core kernel blog
banners
Q&A Game
Q: My kernel app tells me my min_freq is 918mhz. Why is that?
A: Its because of input boost. Your frequency will be boosted to 918mhz as soon as you touch your screen. It will be boosted for 1 second after touch. So you have smooth animations and no scrolling stutters.
Q: My device rebooted / didn woke up from deep sleep. What can I do to help you to find the cause?
A: Install "Syslog" from the Play Store and get me the "Last Kernel Log" or do it via terminal. You'll find the command one post under this.
Q: Will you add S2W/S2S again?
A: No. We're using dt2w from starosk now. If you want to use S2W with my kernel, clone my sources and add it by yourself.
Q: Why the cpu jumps to 1134mhz so ofter during idle?
A: Thats because we're using an interactive based governor. Interactive based governors jumps to hispeed_freq (1134mhz) if the load reaches 99%. Don't forget, even if you're doing nothing, you always have some background load. The lower you set your min_frequency, the faster it reaches 99% load and will jump to hispeed_freq more often.
Battery Profile:
I've made a battery profile for hot plug settings. Following is changed:
echo "20" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_0 = Threshold for cpu1 to kick in
echo "85" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2 = Threshold for cpu2 to kick in
echo "10" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_3 = Threshold for cpu1 to kick out
echo "99" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4 = Threshold for cpu3 to kick in
echo "45" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_5 = Threshold for cpu2 to kick out
echo "60" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_7 = Threshold for cpu3 to kick out
Most of the time you'll be running on dualcore mode (cpu0 and cpu1). If the load reaches a high level with both cores maxed out, the other cores kicks in and will go off again really quickly. The profile will be active after 90 seconds (counted from bootanimation) so your device boots up with full power first. It'll be stupid to limit it on bootup.
Balanced Profile:
echo "15" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_0
echo "35" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2
echo "8" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_3
echo "55" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4
echo "20" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_5
echo "40" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_7
Its a little less conservative than the battery profile and a little less aggressive than the default values. I've tried to make something in between. Try it and left a comment
I will post here the most common issues , if any and a collection of tricks and tips based on all users experience , then will be easier for everyone to track them
i will keep an eye on every post
-=-=-
Please have a look first at this thread
[Repository] [MakoStuff] [Nexus4 Tools] by @gorilla p
then >>> Troubleshooting Synapse
also >>> Installing Synapse and importing profiles
-=-=-
as from version b49 the kernel has been completely rebased therefore I will add below some new tips and tricks
- first check the change log from b49 onwards and also the discussion starts with that post
- the kernel isn`t undervolted anymore by default so , heating occurs due to stock voltages , I`m sure you know what to do then
- new dt2w by stratosk dropping the s2w/s2s feature
- some inputs here http://forum.xda-developers.com/showpost.php?p=55232079&postcount=7836
terminal command for dt2w
echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled
Click to expand...
Click to collapse
thanks @steviemch for heads up
- try this http://forum.xda-developers.com/showpost.php?p=55214263&postcount=7820 if you`re facing in call delay , thanks @eurochild
- fsync status
-=-=-
For those who wants to use the latest hellscore based on KK 4.4.2 on a ROM based on 4.4.3/4/L , here is a fix for loosing WIFI
http://forum.xda-developers.com/showpost.php?p=53132436&postcount=6487
-=-=-=-
and thanks to @themike10452 we have ...
Hellscore Kernel Manager
original thread here >>> http://forum.xda-developers.com/nexus-4/themes-apps/app-hellscore-kernel-tweaker-t2669442
playstore
Hellscore Kernel Manager
-=-=-=-
SCRIPT CREATOR
thanks @Maxr1998
hells-Core Init.d creator
-=-=-=-
Hells-Core kernel with OTG support for Nexus 4 KK
thanks @justvarshney
-=-=-=-
as some other kernels comes with their own ramdisk which will remain over after flashing hellsCore and an unpredictable negative impact on your phone stability may occur , i would recommend you to flash a STOCK KERNEL from below prior flashing
Nexus 4 Stock 4.4.3 KTU84L >>> http://d-h.st/qxB
Nexus 4 Stock 4.4.2 KOT49H >>> http://d-h.st/W8P
Nexus 4 Stock 4.4 KRT16S >>> http://d-h.st/HwN
Nexus 4 Stock 4.4 >>> http://d-h.st/apv
Nexus 4 Stock 4.3 >>> http://d-h.st/TRC
Nexus 4 AOSP 4.3 >>> http://d-h.st/NuC
-=-=-=-
the recommended applications to control/modify the kernel are
Trickster MOD Kernel Settings
Faux123 Kernel Enhancement
-=-=-=-
to be used only for 4.3/1 kernels
doesn`t affect kk kernels , in case of a broken wifi , just re-dirty-flash your rom and then the kk kernel
dePRIMAtor
-=-=-=-
please provide logs in case of troubles
use the command below in terminal emulator to extract the last_kmsg in case of a sudden reboot
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
-=-=-=-
A nice collection of terminal commands to manually modify the kernel settings as per your desire made by @shengovind
thanks pal ! ... i must write a song for him now ... oh well
To Set CPU Governor:
Su
echo "NAME" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "NAME" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "NAME" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo "NAME" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
NAME can be replaced by intellidemand, interactive, conservative, wheatley, ondemand, performance
Default is intellidemand. Changing NAME to conservative changes CPU governor to conservative
FOR SETTING GOVERNOR PARAMETERS:
First set governor then you will be able to edit these..
I do not know what each and every parameter does so these won’t help normal users’ and those who know what these mean will probably know how to edit these. But I’ve included them just because i had to …
INTELLIDEMAND :
echo "FREQUENCY" > /sys/devices/system/cpu/cpufreq/intellidemand/boostfreq
Change FREQUENCY to required value of frequency. This is the frequency cpu is boosted to when screen is touched.
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/boostpulse
not sure what this does and what the set of values are
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/boosttime
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/down_differential
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/ignore_nice_load
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/io_is_busy
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_load
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_max_freq
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_browser
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_inactive_load
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_inactive_max_freq
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/optimal_freq
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/powersave_bias
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_down_factor
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate_min
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sync_freq
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/two_phase_freq
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_any_cpu_load
echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_multi_core
INTERACTIVE
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/above_high_speed_delay
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boost
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
AFAIK this is the time for which cpu is boosted
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/io_is_busy
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo "??" > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
CONSERVATIVE
echo "FREQ" > /sys/devices/system/cpu/cpufreq/conservative/boostfreq
As told above
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/ignore_nice_load
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "??" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
WHEATLEY
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/allowed_misses
echo "FREQ" > /sys/devices/system/cpu/cpufreq/wheatley/boostfreq
told above
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/ignore_nice_load
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/io_is_busy
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/powersave_bias
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_down_factor
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_factor
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_rate
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/target_residency
echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/up_threshold
ONDEMAND:
echo "FREQ" > /sys/devices/system/cpu/cpufreq/ondemand/boostfreq
told above
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
GO HERE IF YOU WANT TO TRY AND MAKE SENSE OUT OF ALL THIS: http://forum.xda-developers.com/showthread.php?t=1369817
CHANGING GPU GOVERNOR
echo “GOVERNOR” > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/policy
Change GOVERNOR to conservative, performance, simple, or ondemand.
echo "1" > /sys/module/sync/parameters/fsync_enabled
TO ACTIVATE DOUBLE TAP TO WAKE
echo 1 > /sys/android_touch/doubletap2wake
TO DEACTIVATE DOUBLE TAP TO WAKE
echo 0 > /sys/android_touch/doubletap2wake
TO ACTIVATE S2W
echo "1" > /sys/android_touch/sweep2wake
TO DEACTIVATE S2W
echo "0" > /sys/android_touch/sweep2wake
BOOST ON TOUCH
echo "X" > /sys/module/msm_hotplug/cpus_boosted
X can be replaced by 1,2,3 or 4 . This sets number of cores to be boosted on touch,
Default is 2. Changing X to 4 boosts 4 cores on touch.
MINIMUM NUMBER OF CPUS ONLINE
echo "X" > /sys/module/msm_hotplug/min_cpus_online
X can be replaced by 1,2,3 or 4 . This sets number of cores to be online at all time,
Default is 1. Changing X to 2 makes sure 2 cores are online all the time.
MAXIMUM NUMBER OF CORES ONLINE
echo "X" > /sys/module/msm_hotplug/max_cpus_online
X can be replaced by 1,2,3 or 4 . This sets maximum number of cores that can go online,
Default is 4. Changing X to 2 makes sure your phone dual core.
MAXIMUM FREQUENCY WHEN SCREEN IS OFF
echo "X" > /sys/module/msm_hotplug/suspend_freq
X can take values 192000, 384000, 540000, 702000, 1026000, 1242000, 1350000, 1512000
Default is 702000. Changing X to 1026000 makes maximum frequency when screen is off to 1ghz
Someone tell how to set gamma manually... Thank you.
There might be a lot of mistakes, so try and correct them..
-=-=-
Color profiles scripts
by @mohitgalaxy3
0
How to take a kernel LOG after random reboot
an easy way to get the last-kmsg is by using the script below , thanks to @Maxr1998
GetLog
the log will be saved in a folder in your sdcard called Logs
run the script and the log will be there
original post http://forum.xda-developers.com/showpost.php?p=50436922&postcount=3234
-=-=-
Once in a while, a software bug in the kernel will cause a random reboot, so in order to help kernel developers to fix and troubleshoot the reboots, a kernel log need to be submitted to the developer for further analysis and hopefully lead to a bug fix.
Most Android Kernels have "RAM Consoles" to save the necessary kernel logs immediately after reboot in the RAM. *The users can then retrieve this RAM log on a subsequent reboot to submit to kernel developers.
[ Using ADB ]
adb shell
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
open last_kmsg.txt using text editor of your choise
then copy the content
open web browser and go to pastebin.com
paste the content to pastebin.com
then send the developer the link to pastebin.com link
then send the developer the link to pastebin.com link
[ Using android terminal app ]
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
open /sdcard/last_kmsg.txt using text app of your choise
then copy the content
open web browser and go to pastebin.com
paste the content to pastebin.com
then send the developer the link to pastebin.com link
[ Using Root Explorer / ES Explorer with Root ]
go to /proc folder
then copy last_kmsg to /sdcard/
rename last_kmsg to last_kmsg.txt
open last_kmsg.txt
copy the content
open web browser and go to pastebin.com
then copy the content to pastebin.com
then send the developer the link to pastebin.com link
-=-=-
Thank you https://plus.google.com/app/basic/+...g6p&sview=25&cid=5&soc-app=115&soc-platform=1 aka... Faux
WOW!! .... the day I install hellscore .. a Q&A and HELP thread is created ... Thanks @xanthrax for creating the thread...
here's my issue :
I've exprienced 4 reboots since I installed b39 version this afternoon.. I have attached the kmsg log ..
I installed this kernel over semaphore N4 1.7.1 without clearing any cache/dalvik cache ( cudnt find any installation instructions) .. I am on rooted stock ..
The reboots occured when i was charging the phone ..
View attachment last_kmsg.rar
bhanumagotra said:
WOW!! .... the day I install hellscore .. a Q&A and HELP thread is created ... Thanks @xanthrax for creating the thread...
here's my issue :
I've exprienced 4 reboots since I installed b39 version this afternoon.. I have attached the kmsg log ..
I installed this kernel over semaphore N4 1.7.1 without clearing any cache/dalvik cache ( cudnt find any installation instructions) .. I am on rooted stock ..
The reboots occured when i was charging the phone ..
View attachment 2345207
Click to expand...
Click to collapse
Davlik and cache should be wiped when u change kernel. Try reinstall it with proper wipes.
bhanumagotra said:
WOW!! .... the day I install hellscore .. a Q&A and HELP thread is created ... Thanks @xanthrax for creating the thread...
here's my issue :
I've exprienced 4 reboots since I installed b39 version this afternoon.. I have attached the kmsg log ..
I installed this kernel over semaphore N4 1.7.1 without clearing any cache/dalvik cache ( cudnt find any installation instructions) .. I am on rooted stock ..
The reboots occured when i was charging the phone ..
View attachment 2345207
Click to expand...
Click to collapse
tell us please which rom are you using , base and some kernel settings
FalenDemon said:
Davlik and cache should be wiped when u change kernel. Try reinstall it with proper wipes.
Click to expand...
Click to collapse
thanks ,.. I will wait for a few more hours before reflashing to see if any more reboots occur ..
---------- Post added at 07:27 PM ---------- Previous post was at 07:23 PM ----------
xanthrax said:
tell us please which rom are you using , base and some kernel settings
Click to expand...
Click to collapse
ROM : Rooted Stock 4.3 JWR66Y
Kernel : hellscore b39 JWR build
Settings : CPU - 192 Mhz - 1242 Mhz
Governer : Intellidemand
GPU : 320 Mhz max
Undervolting : default settings
bhanumagotra said:
ROM : Rooted Stock 4.3 JWR66Y
Kernel : hellscore b39 JWR build
Settings : CPU - 192 Mhz - 1242 Mhz
Governer : Intellidemand
GPU : 320 Mhz max
Undervolting : default settings
Click to expand...
Click to collapse
ok then , i would suggest you to update to the latest b40 JWR
if you`re using any tweak kernel app , uninstall it first and then flash the new kernel
-=-=-
also , a 1242 MHz freq seems to be a little bit too low if you are using the phone for games , heavy games ... 1350 would be better i guess
and lets see what hellsgod says about your last_kmsg , i`m sure he will pop up in here soon :fingers-crossed:
xanthrax said:
ok then , i would suggest you to update to the latest b40 JWR
if you`re using any tweak kernel app , uninstall it first and then flash the new kernel
Click to expand...
Click to collapse
what about wiping cache/dalvik cache ... and do i have to install stock kernel first??
bhanumagotra said:
what about wiping cache/dalvik cache ... and do i have to install stock kernel first??
Click to expand...
Click to collapse
basically a kernel flash doesn`t require that but , to put your mind at rest , you can do it
xanthrax said:
basically a kernel flash doesn`t require that but , to put your mind at rest , you can do it
Click to expand...
Click to collapse
thanks for the help .. will do that and report back..
FalenDemon said:
Davlik and cache should be wiped when u change kernel. Try reinstall it with proper wipes.
Click to expand...
Click to collapse
cache should be wiped before flashing the kernel or after ?
RohanM said:
cache should be wiped before flashing the kernel or after ?
Click to expand...
Click to collapse
well , after ...
xanthrax said:
well , after ...
Click to expand...
Click to collapse
Thanks , you are so quick man.... appreciated...
I used to wipe before flashing the kernel...
---------- Post added at 07:54 PM ---------- Previous post was at 07:47 PM ----------
Some blogs & post here are saying that we should wipe dalvic before flashing kernel or anything.
please follow the template found here fellow RC: http://forum.xda-developers.com/showthread.php?t=2474979
also, post that you made a Q&A thread of that kernel.
thank you.
RohanM said:
Thanks , you are so quick man.... appreciated...
I used to wipe before flashing the kernel...
---------- Post added at 07:54 PM ---------- Previous post was at 07:47 PM ----------
Some blogs & post here are saying that we should wipe dalvic before flashing kernel or anything.
Click to expand...
Click to collapse
anyway , you can do it both , before and after , won`t harm at all , but , you know what ? i NEVER wipe cache or dalvik when flashing kernels ...
Riro Zizo said:
please follow the template found here fellow RC: http://forum.xda-developers.com/showthread.php?t=2474979
also, post that you made a Q&A thread of that kernel.
thank you.
Click to expand...
Click to collapse
thanks mate ! i`ll request that to a moderator even though a moderator suggested me to post it here ...
Hey
You've got several options here:
1) Open a discussion thread in general section (translated OP if possible), say that it is his work and (if he's fine with it) post the DL links together with the github link. Also include a link to the german thread
2) You create the (dev) thread for him and ask mods to give the thread to him (basically you create his thread), and also include all needed information like sources, ...
3) You open a Q&A thread about the kernel, provide all needed infos in it and wait for him to create the OP
Also, what does he need permissions for? He can open a dev thread at any time
If you need/want further information, just ask
Click to expand...
Click to collapse
... and i chosen the first option ...
bhanumagotra said:
what about wiping cache/dalvik cache ... and do i have to install stock kernel first??
Click to expand...
Click to collapse
bhanumagotra said:
WOW!! .... the day I install hellscore .. a Q&A and HELP thread is created ... Thanks @xanthrax for creating the thread...
here's my issue :
I've exprienced 4 reboots since I installed b39 version this afternoon.. I have attached the kmsg log ..
I installed this kernel over semaphore N4 1.7.1 without clearing any cache/dalvik cache ( cudnt find any installation instructions) .. I am on rooted stock ..
The reboots occured when i was charging the phone ..
View attachment 2345207
Click to expand...
Click to collapse
Ok guys, let me jump in...
Flashing a kernel doesn't need any wipes!
Switching custom kernels that are using anykernel updater (which Semaphore and Hellscore do) usually needs a dirty flash of the current rom...reference:
http://forum.xda-developers.com/showpost.php?p=45374233&postcount=3186
Or, in your case you can also flash the stock kernel which gives you the same result as dirty flash. link to stock flashable kernel (the JWR66Y one):
http://forum.xda-developers.com/showthread.php?t=2381128
Also, as @xanthrax stated disable or better uninstall any kernel tweaking apps before you flash a different kernel. And leave the kernel settings by default to see if you're getting any reboots or not. If not you can tweak it step by step. Though Hells mentioned more than once that his kernel is a flash-and-forget-one...so, usually there's no further tweaking needed. But you can
regards
RohanM said:
Thanks , you are so quick man.... appreciated...
I used to wipe before flashing the kernel...
---------- Post added at 07:54 PM ---------- Previous post was at 07:47 PM ----------
Some blogs & post here are saying that we should wipe dalvic before flashing kernel or anything.
Click to expand...
Click to collapse
is 192MHz default value or have you set it?
I can remember that too low frequency can cause problems!
{
"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"
}
THIS KERNEL IS BORN TO REDUCE RANDOM REBOOT OR REBBOT
AND MORE BATTERY LIFE
My Settings:
(saver)
Governor: Interactive
HotPlug CPU: IntelliPlug
(faster)
Governor: Interactive
HotPlug CPU: (none) off
Everything else without changes ( For tweak kernel use Kernel Adiutor )
Full support int.d for test this goto in '/data' dir and
you see the files Test.log, Z03TDTVacuum.log and Zipalign.log
For disable int.d feature rename folder '/etc/int.d'
Based on asus kernel sources WW-4.21.40.184
Kernel source are here : ZE551ML4_21_40_184.zip
Testing on my ZE551ML 4GB 2,3GHz
Support underclock to 250MHz
Support NTFS and eXfat
Support POWERSUSPEND WAKELOCK EARLYSUSPEND
Support USB OTG
Sensors Fix
DeepSleep Google Play Service Fix
Networking options:
ADVANCED BIC CUBIC WESTWOOD HTCP HSTCP HYBL
VEGAS SCALABLE LP VENO YEAH ILLINOIS
Toolchain Linaro 4.9.2 optimizations standard :
HOSTCFLAGS = -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer -std=gnu89 -fgcse-las -floop-flatten -floop-parallelize-all -ftree-loop-linear -floop-interchange -floop-strip-mine -floop-block -pipe -Wno-unused-parameter -Wno-sign-compare -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-value
HOSTCXXFLAGS = -O2
# L1/L2 cache size parameters by @JustArchi
KBUILD_CFLAGS += --param l1-cache-size=32 --param l1-cache-line-size=32 --param l2-cache-size=2048
Governors CPU optimized :
ALUCARD CONSERVATIVEX INTERACTIVE FRANKENSTEIN HOTPLUG INTEL LAGFREE
PERFORMANCE ADAPTIVE BIOSHOCK BLUACTIVE CONSERVATIVE THESSJACTIVE
CYAN DARKNESS HYBRID IMPULSE INTERACTIVEX LIONHEART YANKACTIVE
NIGHTMARE ONDEMAND PEGASUSQ POWERSAVE SMARTASSH3 ZZMOOVE
SMARTMAX WHEATLEY
new TRIPNDROID INTELLIACTIV INTELLIMM
new INTELLIDEMAND YANKDEMAND HELLSACTIVE
update cpu freq in parameters Governors
IO Schedulers:
NOOP DEADLINE CFQ SIO SIOPLUS ROW FIOPS ZEN FIFO VR TRIPNDROID
Hotplugs driver:
ASMP MSM_HOTPLUG ALUCARD_HOTPLUG INTELLI_PLUG
ZEN_DECISION MAKO_HOTPLUG MSM_SLEEPER
For tweak kernel use Kernel Adiutor... (thanks for this Apps)
Thanks to TheSSJ Project T for your kernel sources on GitHub... Mod diff here fix...
Thanks to Nyks45 OctoDex for your kernel sources on GitHub...
Thanks to ASUS for kernel sources....
For Z008 flash Zenkernel.V1.3.Atom.MM184.Zenfone2_Anykernel.zip in attachments
goto here...
for support init.d add this code in your ramdisk at the end of init.rc:
service sysinit /system/bin/sh /sbin/sysinit.sh
disabled
user root
oneshot
on property:sys.boot_completed=1
start sysinit
exec /system/bin/sysinit.sh
Click to expand...
Click to collapse
For Z00A
Flash Anykernel if have ZenKernel full version in device (for full support init.d flash ZenKernel full)
old UPDATE
UPDATE V1.1
add Asynchronous Transfer Mode (ATM)
ATM is a high-speed networking technology for Local Area Networks
and Wide Area Networks. It uses a fixed packet size and is
connection oriented, allowing for the negotiation of minimum
bandwidth requirements.
add BLX Support for Battery Life eXtender.
add Intel PowerClamp idle injection driver.
This enforce idle time which results in more package C-state residency.
The user interface is exposed via generic thermal framework.
UPDATE V1.2
update POWERSUSPEND (add extern bool power_suspended)
add ASYNC_FSYNC "asynchronous fsync"
update cpu freq in parameters Governors
update governor INTEL
add governor TRIPNDROID
add governor INTELLIACTIVE
add governor INTELLIMM
set default governor TRIPNDROID
add "Number of bits to use for ASLR of mmap base address"
This value can be changed after boot using the
/proc/sys/vm/mmap_rnd_bits tunable
add "Number of bits to use for ASLR of mmap base address for compatible applications"
This value can be changed after boot using the
/proc/sys/vm/mmap_rnd_compat_bits tunable
set CONFIG_OPROFILE_EVENT_MULTIPLEX=y
set CONFIG_JUMP_LABEL=y
remove fs # CONFIG_EXT2_FS is not set
remove fs # CONFIG_EXT3_FS is not set
UPDATE V1.3
update SWEEP2SLEEP driver (fix crash)
fix this error:
E Intel PowerHAL: Error opening /sys/devices/system/cpu/cpufreq/interactive/touchboostpulse: No such file or directory
replace power.mofd_v1.so in '/system/lib/hw' with this set permission 0644 backup original
(only when not set governors CPU INTERACTIVE)
rebuild ramdisk and fix many governors CPU
set default governors CPU INTERACTIVE
UPDATE V1.4 Beta for test
add CPU_BOOST (for tune use Kernel Adiutor)
(add 'migration_notifier_head')
update governor ONDEMAND
add governor INTELLIDEMAND
add governor YANKDEMAND
add governor HELLSACTIVE
add MSM_SLEEPER driver hotplug
update INTELLI_PLUG v5.4 driver hotplug
update INTEL driver hotplug
update ALUCARD_HOTPLUG driver hotplug
update MSM_HOTPLUG driver hotplug
update ASMP driver hotplug
Zenkernel.V1.4-beta.Atom.MM184.Zenfone2_Anykernel.zip
UPDATE V1.5
last commit cm-14.1 :
Enable CONFIG_IP_NF_MATCH_RPFILTER=y
Beta test v1.4 changes add...
UPDATE V1.6
KERNEL in XZ (reduce size)
enable CONFIG_DEBUG_NX_TEST=m
add Kernel-based Virtual Machine (KVM) support:
enable CONFIG_KVM=m
enable CONFIG_KVM_INTEL=m
add in Ramdisk load modules kvm.ko and kvm-intel.ko
You flash full version for new Ramdisk
UPDATE V1.7
add governor INTERACTIVE_PRO thanks @BORETS24
re_tuned governor cpu CYAN
You flash last full version for new Ramdisk
UPDATE V1.9 Super Update
commit cm-14.1 :
update File systems EXT4
update File systems F2FS
commits /* 3.18 backport */
enabled CONFIG_CRYPTO_CRC32=y
new ZRAM, ZSMALLOC, ZPOOL driver
update LZ4 compressor
enabled CONFIG_ZRAM_LZ4_COMPRESS=y
# CONFIG_FRONTSWAP is not set
CONFIG_ZPOOL=y
CONFIG_ZSMALLOC=y
# CONFIG_PGTABLE_MAPPING is not set
# CONFIG_ZSMALLOC_STAT is not set
disable CONFIG_CPUSETS is not set
set CONFIG_PANIC_TIMEOUT=3 (was 0)
set CONFIG_ARCH_MMAP_RND_COMPAT_BITS=16 (was 8)
enabled CONFIG_NF_CONNTRACK_SECMARK=y
enabled CONFIG_NETFILTER_XT_TARGET_SECMARK=y
enabled CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
# Pseudo filesystems:
CONFIG_F2FS_IO_TRACE=y
# CONFIG_F2FS_FAULT_INJECTION is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_UPCALL is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_ACL is not set
CONFIG_CIFS_DEBUG=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_DFS_UPCALL is not set
# CONFIG_CIFS_SMB2 is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
disable CONFIG_UNUSED_SYMBOLS is not set
enabled CONFIG_CRYPTO_MD4=y
disable CONFIG_XZ_DEC_TEST is not set
You flash last full version for new Ramdisk
For install do in this order:
My mod 3Minit Battery & Traffic on Statusbar AsusSystemUI
Tested on Stock Z00A_WW-4.21.40.184 Works SuperSu and Magisk. FIX Not Work Xposed
Tested on [ROM]CleanSTOCK-MM-Z00A_WW-4.21.40.184[28-Nov] with Xposed V87_x86
Thanks to GuilhermeXtreme
Attention: On this Rom is present a Bug: power on HotSpot crash the phone
For fix Hotspot replace dir /framework with /framework dir from 144 and
set permission to 0644 all files (automatic wipe dalvik cache)
1_ Flash in your TWRP Zenkernel_V1.3_.MM184_Zenfone_2.zip in Attachments
2_ Flash magisk v9 zip find on internet Xda Thread
3_ Flash SR4-SuperSU-v2.78-SR4-20161115184928.zip find on internet Chainfire Download or phh's superuser
4_ Reboot devices :good:
Nice man.Your kernel support Z008?
Russiamen said:
Nice man.Your kernel support Z008?
Click to expand...
Click to collapse
Sorry bro not have Z008 phone.
I wait for this news... (test please)
:good:
It's good that you link to the Asus kernel source, but I think linking to your modified kernel source would be better
Doesn't need to be github, you could upload a zip file on Google drive
Renix63 said:
Sorry bro not have Z008 phone.
I wait for this news... (test please)
:good:
Click to expand...
Click to collapse
Boot in twrp(
TheSSJ said:
It's good that you link to the Asus kernel source, but I think linking to your modified kernel source would be better
Doesn't need to be github, you could upload a zip file on Google drive
Click to expand...
Click to collapse
You're right, but I have no way to save 150 mega Web ... maybe I create a patch file. :highfive:
Which xposed i should install?? Please give me the links
Russiamen said:
Boot in twrp(
Click to expand...
Click to collapse
OP needs to compile the Z008 display driver into his kernel, then it will boot - https://github.com/TheSSJ/zf2_mmkernel/blob/master/arch/x86/configs/x86_64_moor_defconfig#L3568
TheSSJ said:
OP needs to compile the Z008 display driver into his kernel, then it will boot - https://github.com/TheSSJ/zf2_mmkernel/blob/master/arch/x86/configs/x86_64_moor_defconfig#L3568
Click to expand...
Click to collapse
And need change dpi in 320
ayush.gl said:
Which xposed i should install?? Please give me the links
Click to expand...
Click to collapse
This xposed-v87-sdk23-x86.zip
TheSSJ said:
It's good that you link to the Asus kernel source, but I think linking to your modified kernel source would be better
Doesn't need to be github, you could upload a zip file on Google drive
Click to expand...
Click to collapse
My modification to your kernel...
Renix63 said:
This xposed-v87-sdk23-x86.zip
Click to expand...
Click to collapse
is it system less xposed??? please give me the links of magisk v9 and supersu working with this and tell me the correct order of flashing magisk, supersu and xposed. thanks
TheSSJ said:
OP needs to compile the Z008 display driver into his kernel, then it will boot - https://github.com/TheSSJ/zf2_mmkernel/blob/master/arch/x86/configs/x86_64_moor_defconfig#L3568
Click to expand...
Click to collapse
Apply my changes and try a build....
ayush.gl said:
is it system less xposed??? please give me the links of magisk v9 and supersu working with this and tell me the correct order of flashing magisk, supersu and xposed. thanks
Click to expand...
Click to collapse
Find magisk v9 in this Rom :good:
Code:
1_ Flash in your TWRP Zenkernel_V10_.MM184_Zenfone_2.zip in Attachments
2_ Flash magisk v9 zip find on internet
3_ Flash SR4-SuperSU-v2.78-SR4-20161115184928.zip find on internet
4_ Flash Xposed v87_x86_23
5_ Reboot devices
ayush.gl said:
is it system less xposed??? please give me the links of magisk v9 and supersu working with this and tell me the correct order of flashing magisk, supersu and xposed. thanks
Click to expand...
Click to collapse
Use my latest builds
http://forum.xda-developers.com/showpost.php?p=69834732&postcount=118
Russiamen said:
Use my latest builds
http://forum.xda-developers.com/showpost.php?p=69834732&postcount=118
Click to expand...
Click to collapse
Thanks :laugh:
Russiamen said:
Use my latest builds
http://forum.xda-developers.com/showpost.php?p=69834732&postcount=118
Click to expand...
Click to collapse
i got bootloops using your builds. is there any correct order i should follow, tell me the order @Russiamen
ayush.gl said:
i got bootloops using your builds. is there any correct order i should follow, tell me the order @Russiamen
Click to expand...
Click to collapse
I don't understand why some get bootloop ,I installed and everything was fine and don't understand how it all goes,what are your steps:crying:
Russiamen said:
I don't understand why some get bootloop ,I installed and everything was fine and don't understand how it all goes,what are your steps:crying:
Click to expand...
Click to collapse
flashed magisk v9 then phh's supersu then xposed v87 then reboot. should i reboot everytime after installing one zip or can i install all the 3 zips same time and reboot??
ayush.gl said:
flashed magisk v9 then phh's supersu then xposed v87 then reboot. should i reboot everytime after installing one zip or can i install all the 3 zips same time and reboot??
Click to expand...
Click to collapse
You have to install all of them in this order(Magisk+Phh's+Xposed)
What kernel are you using?
Code:
/*
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*if you flashed it over marshmallow, i will laugh more than anyone would do !
*/
EMUI 5 ONLY !
Kernel features:
∆this kernel is intended to increase performance, without affecting battery
∆SIO io scheduler added
∆FIOPS io scheduler added
∆ROW io scheduler added
∆TRIPNDROID io scheduler
∆fast fingerprint wake up
∆ fsync on/off support
∆quick wake up added
∆F2FS file system support
∆tweaked stock governors (ondemand/interactive)
∆ NTFS file system support
∆ implemented mbcache2
∆ toggable crc check ( you can en/dis able it) (disabled by default)
∆ drop vfs cache pressure for more ram
∆ faster fingerprint wakeup, decreased duration to 2000ms (3000 was before)
∆ much faster /proc/vmstat for better performance
∆ disabled safetynet check
∆increased number tcp stream (you can do many network requests,more than normal ! )
∆optimized memory utilities
∆cpuidle enabled so as to improve power consumption
∆optimized sfck compression
∆increased threads of dm-crypt
∆set initial tcp window to 64k so as to improve speed.
∆Built with Anykernel package = it can be installed in any version & any model, and without losing root !
∆with this kernel and some small tweaks using kernel adiutor, you can reach 60k point in antutu benchmark ??
Download:
THIS FILES ARE FOR EVERY ROM/FIRMWARE EXCEPT ARSENIK V2 !
SMOKY-KERNEL-V3
SMOKY-KERNEL-V2
SMOKY-KERNEL-V1.1
SMOKY-KERNEL-V1
THIS LINK IS ONLY FOR ARSENIK V2, NOT ARSENIK V1.1 OR V1 ! ARSENIK V2 ONLY !
SMOKY-V2-FOR ARSENIK
Installation:
1/download and install Kernel adiutor
2/enable init.d by emulating it
3/backup boot only
4/Flash the Kernel zip in TWRP Recovery.
5/reboot
CHANGELOG
SMOKY-KERNEL-V2
+ implemented mbcache2
+ toggable crc check ( you can en/dis able it)
+ drop vfs cache pressure for more ram
+ faster fingerprint wakeup, decreased duration to 2000ms (3000 was before)
+ much faster /proc/vmstat for better performance
+ disabled safetynet check
SMOKY-KERNEL-V1.1
+added quick wakeup ( double tap 2 wake became faster)
+added tripndroid io scheduler
+added f2fs file system support
+tweaked stock governors (interactive/ondemand)
SMOKY-KERNEL-V1:
initial release
XDA:DevDB Information
Smoky Kernel for Huawei P9 Lite
Contributors
@simo255 (me)
i wanna really thank @OldDroid , because he helped me so as to build this kernel, after 1000 and 1 errors, if he wasn't here, you would have never seen this kernel !
Thank you @OldDroid !
Source Code: https://github.com/simo255/Smokey-Kernel
Version Information
Status: ~STABLE~
Created 2017-07-14
Last Updated 2017-07-25
can i use on meticulus builds?
hugor671 said:
can i use on meticulus builds?
Click to expand...
Click to collapse
nope, this kernel is only for emui 5 !
Nice to see development for this phone!
Can use otg with this kernel...
Waseem.haidernawa said:
Can use otg with this kernel...
Click to expand...
Click to collapse
im always finding a solution so as to enable otg but atm it isn't working
Ok so where is problem can u tell me ?
simo255 said:
EMUI 5 ONLY !
Kernel features:
∆SIO io scheduler added
∆FIOPS io scheduler added
∆ROW io scheduler added
∆fast fingerprint wake up
∆ fsync on/off support
∆ NTFS file system support
∆Built with Anykernel package = it can be installed in any version & any model, and without losing root !
Download:
SMOKY-KERNEL-V1
Installation:
1/download and install Kernel adiutor
2/enable init.d by emulating it
3/Flash the Kernel zip in TWRP Recovery.
4/reboot
XDA:DevDB Information
Smoky Kernel for Huawei P9 Lite
Contributors
@simo255 (me)
i wanna really thank @OldDroid , because he helped me so as to build this kernel, after 1000 and 1 errors, if he wasn't here, you would have never seen this kernel !
Thank you @OldDroid !
Source Code:https://github.com/simo255/Smokey-Kernel
Version Information
Status: ~STABLE~
Created 2017-07-14
Last Updated 2017-07-14
IF ANYONE WANNA TEST ANOTHER VERSION OF THE KERNEL(ALPHA) WHICH HAS NEW GOVERNORS, PLEASE SEND ME A PM
Click to expand...
Click to collapse
Hello there! I would love to test the alpha kernel
pafchu said:
Hello there! I would love to test the alpha kernel
Click to expand...
Click to collapse
ive sent you a pm
New update )
Can u enable motion future's like rise to ear i mean overall motion guesturs....
Waseem.haidernawa said:
Ok so where is problem can u tell me ?
Click to expand...
Click to collapse
well, i have to change a value inside the source code and build the kernel ,even the ramdisk, I'm trying one by one but none of them worked,
if i find a solution so as to enable it i will release a new version asap
any tricks to go back to stock kernel without flashing whole ROM again?
tw1st3d83 said:
any tricks to go back to stock kernel without flashing whole ROM again?
Click to expand...
Click to collapse
flash stock boot.img
simo255 said:
flash stock boot.img
Click to expand...
Click to collapse
can i extract and flash from ArseniK because i flashed SMOKY over ArseniK?
tw1st3d83 said:
can i extract and flash from ArseniK because i flashed SMOKY over ArseniK?
Click to expand...
Click to collapse
of course
Can you enable high clocks? Would be nice if I can get a bump in speed.
Hi friend. Can you suggest me the best settings in Kernel adiutor to get the best from this phone with your kernel?
If you Need a tester or help i'm ready
UPDATE !
check changelog for more infos
Paolo83 said:
Hi friend. Can you suggest me the best settings in Kernel adiutor to get the best from this phone with your kernel?
If you Need a tester or help i'm ready
Click to expand...
Click to collapse
hello,
for io scheduler , in internal storage use fiops io scheduler with 1024 kb read ahead
do the same for external storage, but with row io sched
disable crc check and fsync, done
you will have this result