Some system tweaks specifically conceived for our SoC Snapdragon 810 can enhance the battery life of our Xperia Z5.
Features:
- Power Tweaks for S810 (no performance loss)
- Various common performance / battery friendly system tweaks (no performance loss)
- Tuned Interactive Governor Profiles for S810 (performance depends on the chosen profile)
Requirements:
- Z5 and Z3+/Z4 series
- Root
- Busybox app installed and activated
- SManager app installed
Installation:
- If you were using a previous version of this mod, delete all the scripts
- Download the attached Z5_Endurance_Tweaks_v5.zip (this is not a flashable zip)
- Copy the folder Z5_Endurance_Tweaks from the zip and paste it to "/system/etc/"
- Open SManager and navigate up to /system/etc/Z5_Endurance_Tweaks
- Select the file "Power_tweaks.sh" and set it as su and boot, save the configuration, and run it
- Select the file "Setprop_tweaks.sh" and set it as su and boot, save the configuration, and run it
- Select the file "Gov_prof_Deadpool.sh" and set it as su and if you want to use it as your default profile governor, set it as boot, save the configuration,
- Select the file "Gov_prof_DragonFly.sh" and set it as su and if you want to use it as your default profile governor, set it as boot, save the configuration,
- Select the file "Gov_prof_Excalibur.sh" and set it as su and if you want to use it as your default profile governor, set it as boot, save the configuration,
- Run your chosen default profile governor
In the SManager dashboard, you should have something like this:
{
"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"
}
Governor profiles indications:
Performance: Stock > DragonFly > Excalibur > Deadpool
Battery life: Deadpool > Excalibur > DragonFly > Stock
Update (27/11): new profile attached - Xenon v2 especially made for Z5 by @koekoek91 and @_LLJY
Potentially as battery friendly as Deadpool (?) but with great performance (as good as Dragonfly ? stock ? better ?), good for common users and for gamers... Pls give feedback!
- Enjoy
Notes:
- Alternately, you can put your chosen scripts in your init.d folder if you have init.d support, but I strongly encourage to use SManager, it's much more reliable and versatile
- Wait a little before to draw any opinions on this tweaks mod.
- Feedbacks and suggestions for futures versions are strongly encouraged.
Credits:
@Naman Bhalla and @henryzhang317 for their Power Tweaks for SnapDragon 810 Devices
@xperator for his tuned interactive governor profiles
@zacharias.maladroit
@_LLJY and @androidexpert35 for some tweaks
Changelog:
v5 (08/10)
- Darkspice and Heimdall interactive governor profiles removed (outdated)
- DeadPool, Excalibur and DragonFly interactive governor profiles added
v4 (05/09):
- Some tweaks added, some other removed
v3 (05/03):
- HEIMDALLv3 interactive governor profile slightly modified by me
- DarkSpiceR7.5 interactive governor profile added, slightly modified by me
- New tweaks added in Setprop_tweaks.sh
v2 (27/02): All the scripts rewritten and various common performance / battery friendly system tweaks added (Setprop_tweaks.sh)
v1 (24/02): Initial release
Hey nreuge,
First of all, thanks for the scripts. Hope they work really nice
About the modifications/tweaks, could you please specify what changes have been made, and what to expect from them?
---- Edit
Just made some tests over here...
It actually made my phone a bit laggy.
ChristianLetti said:
Hey nreuge,
First of all, thanks for the scripts. Hope they works really nice
About the modifications/tweaks, could you please specify what changes have been made, and what to expect from them?
Click to expand...
Click to collapse
Hi !
The Power Teaks controls the qualcomm power drivers in a more efficient way than stock.
The Tuned Interactive Governor Profile is made to be very battery friendly with great responsiveness/snappyness.
If you want more information, follow the links given in credits section. Note that only some tweaks have been selected by me. If you still want more information, just look at the script ^^
Nice !
Merci beaucoup !
Lol - I knew that there was still something lurking at the Oneplus forums
http://forum.xda-developers.com/oneplus-2/general/power-tweaks-snapdragon-810-devices-t3261790
Seeing all these permissions makes me feel dizzy - but it guarantees that the job gets done
@nreuge how much of an SOT improvement did you observe ? (already several days of usage with those scripts ?)
Or did you spot these tweaks today ?
ChristianLetti said:
Just made some tests over here...
It actually made my phone a bit laggy.
Click to expand...
Click to collapse
For me, hard to say...
zacharias.maladroit said:
Seeing all these permissions makes me feel dizzy - but it guarantees that the job gets done
Click to expand...
Click to collapse
zacharias.maladroit said:
@nreuge how much of an SOT improvement did you observe ? (already several days of usage with those scripts ?)
Or did you spot these tweaks today ?
Click to expand...
Click to collapse
I've tested these tweaks the last 2 days.
I've not etablished any reliable testing methodology to measure any improvements on battery life. It's why I'm eagerly waiting for feedbacks.
I've the feeling they are efficient in conditions of moderate usage, maybe less for intensive tasks...
Leaving this here:
https://github.com/zachariasmaladro...ntation/devicetree/bindings/power/qpnp-fg.txt
QTI's QPNP PMIC Fuel Gauge Device
Click to expand...
Click to collapse
https://github.com/zachariasmaladro...devicetree/bindings/power/qpnp-smbcharger.txt
QPNP SMB Battery Charger
Click to expand...
Click to collapse
https://github.com/zachariasmaladro..._Sun-Kernel_v6-stable/drivers/power/qpnp-fg.c
So you're dealing with one of the most essential parts of your phone (charger and [assumedly] how much the battery offers the system)
Any no one can give more details on this ... tough stuff
drivers/power/qpnp-smbcharger.c:static int vf_adjust_low_threshold = 5;
drivers/power/qpnp-smbcharger.c:module_param(vf_adjust_low_threshold, int, 0644);
drivers/power/qpnp-smbcharger.c:static int vf_adjust_high_threshold = 7;
drivers/power/qpnp-smbcharger.c:module_param(vf_adjust_high_threshold, int, 0644);
drivers/power/qpnp-smbcharger.c:static int vf_adjust_n_samples = 3;
drivers/power/qpnp-smbcharger.c:static int vf_adjust_n_samples = 10;
drivers/power/qpnp-smbcharger.c:module_param(vf_adjust_n_samples, int, 0644);
drivers/power/qpnp-smbcharger.c:static int vf_adjust_max_delta_mv = 200;
drivers/power/qpnp-smbcharger.c:static int vf_adjust_max_delta_mv = 40;
drivers/power/qpnp-smbcharger.c:module_param(vf_adjust_max_delta_mv, int, 0644);
drivers/power/qpnp-smbcharger.c:static int vf_adjust_trim_steps_per_adjust = 3;
drivers/power/qpnp-smbcharger.c:static int vf_adjust_trim_steps_per_adjust = 1;
drivers/power/qpnp-smbcharger.c:module_param(vf_adjust_trim_steps_per_adjust, int, 0644);
drivers/power/qpnp-smbcharger.c: && i <= vf_adjust_trim_steps_per_adjust; i++) {
drivers/power/qpnp-smbcharger.c: if ((vbat_mv - chip->vfloat_mv) < -1 * vf_adjust_max_delta_mv) {
drivers/power/qpnp-smbcharger.c: if (chip->n_vbat_samples < vf_adjust_n_samples) {
drivers/power/qpnp-smbcharger.c: if (delta_vfloat_mv > vf_adjust_high_threshold
drivers/power/qpnp-smbcharger.c: || delta_vfloat_mv < -1 * vf_adjust_low_threshold) {
Click to expand...
Click to collapse
that's quite a difference to the suggest values of 55 for low (vs. 5) and 99 for high (vs. 7)
https://en.wikipedia.org/wiki/Float_voltage
I feel rather uneasy after having gone through all these files to adjust these settings,
perhaps anyone with some in-depth knowledge can say whether it's relatively safe or a red flag to change the values:
Code:
pr_smb(PR_STATUS, "sample number = %d vbat_mv = %d ibat_ua = %d\n",
chip->n_vbat_samples,
vbat_mv,
ibat_ua);
chip->max_vbat_sample = max(chip->max_vbat_sample, vbat_mv);
chip->n_vbat_samples += 1;
if (chip->n_vbat_samples < vf_adjust_n_samples) {
pr_smb(PR_STATUS, "Skip %d samples; max = %d\n",
chip->n_vbat_samples, chip->max_vbat_sample);
goto reschedule;
}
/* if max vbat > target vfloat, delta_vfloat_mv could be negative */
delta_vfloat_mv = chip->vfloat_mv - chip->max_vbat_sample;
pr_smb(PR_STATUS, "delta_vfloat_mv = %d, samples = %d, mvbat = %d\n",
delta_vfloat_mv, chip->n_vbat_samples, chip->max_vbat_sample);
/*
* enough valid samples has been collected, adjust trim codes
* based on maximum of collected vbat samples if necessary
*/
if (delta_vfloat_mv > vf_adjust_high_threshold
|| delta_vfloat_mv < -1 * vf_adjust_low_threshold) {
rc = smbchg_adjust_vfloat_mv_trim(chip, delta_vfloat_mv);
if (rc) {
pr_smb(PR_STATUS,
"Stopping vfloat adj after trim adj rc = %d\n",
rc);
goto stop;
}
chip->max_vbat_sample = 0;
chip->n_vbat_samples = 0;
goto reschedule;
#ifdef CONFIG_QPNP_SMBCHARGER_EXTENSION
} else {
pr_smb(PR_STATUS, "reschedule vfloat adj\n");
chip->max_vbat_sample = 0;
chip->n_vbat_samples = 0;
goto reschedule;
#endif
Hello @nreuge!
goodjob on the thread. may i ask if these tweaks will work on oneplus2 as well
henryzhang317 said:
Hello @nreuge!
goodjob on the thread. may i ask if these tweaks will work on oneplus2 as well
Click to expand...
Click to collapse
It should work !
When you run the scripts in SManager, you can see if there are errors messages or not.
nreuge said:
It should work !
When you run the scripts in SManager, you can see if there are errors messages or not.
Click to expand...
Click to collapse
Thanks for the quick reply! ill test it and report in in 2 weeks time been busy with my exams. keep up the good work!
SD810-fg-scripts.sh
Code:
#!/system/bin/sh
# kudos to Nama Bhalla, henryzhang317, nreuge on XDA
echo "setting 'debug_mask' to 1"
echo "1" > /sys/module/qpnp_fg/parameters/debug_mask
echo " "
cat /sys/module/qpnp_fg/parameters/debug_mask
echo " "
echo "1 means 'debug_mask' enabled"
echo " "
echo "..."
echo " "
echo "setting 'sense_type' to 0"
echo "0" > /sys/module/qpnp_fg/parameters/sense_type
echo " "
cat /sys/module/qpnp_fg/parameters/sense_type
echo " "
echo "0 means alternative 'sense resistor' successfully set"
echo " "
echo "..."
echo " "
echo "enabling setting 'first_est_dump', to 1"
echo "1" > /sys/module/qpnp_fg/parameters/first_est_dump
echo " "
cat /sys/module/qpnp_fg/parameters/first_est_dump
echo " "
echo "1 means 'first_est_dump' set"
echo " "
echo "..."
echo " "
echo "done ..."
Launch SManager (Script Manager) with root rights,
then tap on the SU icon (yes, you need root twice - that equals doing su - in terminal )
after that it should launch
Unless you know what you are doing with the modifications of the charger - I'd keep to this and see whether that makes difference at all.
No permission changes needed
zacharias.maladroit said:
So you're dealing with one of the most essential parts of your phone (charger and [assumedly] how much the battery offers the system)
that's quite a difference to the suggest values of 55 for low (vs. 5) and 99 for high (vs. 7)
perhaps anyone with some in-depth knowledge can say whether it's relatively safe or a red flag to change the values:
Click to expand...
Click to collapse
Perhaps can you ask to @Naman Bhalla by mp if you are worried, these tweaks are from him...
Thanks for the script, it's well written, I'll update mine but keeping the smbcharger tweaks.
Good evening !
ChristianLetti said:
what to expect from them?
Click to expand...
Click to collapse
zacharias.maladroit said:
how much of an SOT improvement did you observe ?
Click to expand...
Click to collapse
I'm now convinced of the efficiency of these tweaks. I would say that the battery life is increased by at least 10-15% for a daily usage, maybe more. I have the impresion of having my old Z2 in my hands (in term of battery life).
It would be interesting to test all of these tweaks independently to quantify the gain for each of them. But I don't feel the courage to do it...
nreuge said:
Perhaps can you ask to @Naman Bhalla by mp if you are worried, these tweaks are from him...
Thanks for the script, it's well written, I'll update mine but keeping the smbcharger tweaks.
Good evening !
Click to expand...
Click to collapse
Thanks,
maybe adding some kind of feedback (output) ?
otherwise you don't know if it was applied successfully or not
Update (27/02): v2
Z5 Endurance Tweaks v2 (27/02) : all the scripts rewritten and various common performance / battery friendly system tweaks added (Setprop_tweaks.sh)
ChristianLetti said:
Just made some tests over here...
It actually made my phone a bit laggy.
Click to expand...
Click to collapse
It's due to the tuned interactive governor profile. You can retest the mod with Governor_Tweaks.sh disabled.
nreuge said:
It's due to the tuned interactive governor profile. You can retest the mod with Governor_Tweaks.sh disabled.
Click to expand...
Click to collapse
Thanks, just gave a try, now it seems fine
nreuge said:
Z5 Endurance Tweaks v2 (27/02) : all the scripts rewritten and various common performance / battery friendly system tweaks added (Setprop_tweaks.sh)
Click to expand...
Click to collapse
@agentsandy007
@Fekajo
@pikeylfc
Guys, thanks for your thanks, but it would be nice to give thanks for the first post too !
And don't forget to read the new instructions...
I'm using this on my z3+. Works great phone seems more snappier
pikeylfc said:
I'm using this on my z3+. Works great phone seems more snappier
Click to expand...
Click to collapse
Thanks, good to know
Hi, do we have to set specific permissions regarding both the script files and the folder ? Also, I am currently using kernel adiutor, will it mess with your tweaks when applying settings after boot is done ?
Thx for your work !
Related
Announcement Box:
The Kernel Is Fully Re-based At .431 Source Enjoy The Liquid Fast And Jet Fast Speed Of Trinity Kernel!
Click to expand...
Click to collapse
{
"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"
}
Why Trinity Kernel ?
Because many people Believe its A Chain of Kernel + ROM Where The Device Boot Without kernel Out Device Will Not Boot! Nor
Why Many People say's Battery Drain on Different Kinds of Kernels / People Opinions?
Guys. 1st Reason is The 3G/4G/Edge/HSDPA Active at Background Obviously make A WiFi Tether and Leave it there at 12+ Minutes Plus.. Right Battery Drain Fast because of the Very Active Process in Background the "MOST" Common thing people sue is the ROM no Its not its Depend how you use it.. Playing Games Etc. May Cause to battery drain. 1st Step to recover Battery Drain WiPe Battery Stat.
2nd Use Other Apps Can Disable WiFi when your Asleep or Not Using It ...
Is My Kernel Stable?
Absolutely Yes! Compiled Using arm-eabi 4.4.3
Trinity Kernel V2.0 Download :
Trinity Kernel 1.6 - Main Kernel
{ Will Show 2.6.32.9-Trinity_1.6 Sorry FORGOT To Change But it i Still 2.0 Please see The Compiler I Used Download on Google Play }
= Click Here =
WiFi Modules
-------------------------------------------
Trinity Kernel 2.0 - WiFi Modules
= Click Here =
You Want To Support Me!!
User This !
OR
SpecialThanks To ! : Andridu - Jimbo - DooMLord - Sony - XDA - Mike 1986 - PayPal { For Service }
Changelog Version 1.0 { Sunday Jun 17, 2012 }
Based @ Jimbo Source
Pre-Rooted
Enable CONFIG_CRYPTO_SHA256 to support Android data encryption
1.7Ghz Nor 2.0Ghz OverClock
Compiled With eabi-arm-4.4.3 ~ For Better BenchMark Using Other ToolChain For More Best Benchmark.
Added I/O Scheduler
Added Governor
Support for ext2,ext3,ext4 and NTFS FileSystems.
0% Battery Friendly
Increase RAM ~ FXP
Init.d Support
Two Way Recording
Cifs.ko.
Tun.ko.
Changelog V1.6 { June 21, 2012 }
Rebased At .431 Source On Sony Open-ware Source
Added RAMDISK Default.Prop For Trinity App Support : COMING SOON :
Enable CONFIG_CRYPTO_SHA256 to support Android data encryption - Set 1 to Y Value
Fix Battery Drain And Improve Battery Charged { Over Ride }
Changelog V2.0 { [?] }
Increasing Battery Charge ... { Stable And More Juice }
=MINIMUM=
struct device_data device_data = {
.limit_tbl = &limit_tbl,
.battery_capacity_mah = 1650,
.maximum_charging_current_ma = 1120,
=MAXIMUM=
struct device_data device_data = {
.limit_tbl = &limit_tbl,
.battery_capacity_mah = 1780,
.maximum_charging_current_ma = 1180,
Click to expand...
Click to collapse
Increase Semc_Anzu_LED
{
.name = "lcd-backlight",
.sinks = BIT(AS3676_SINK_01),
.flags = AS3676_FLAG_ALS | AS3676_FLAG_WAIT_RESUME,
.max_current = 25000,
.default_brightness = LED_FULL,
},
{
.name = "button-backlight",
.sinks = BIT(AS3676_SINK_RGB1) | BIT(AS3676_SINK_RGB2),
.max_current = 25000,
},
{
.name = "red",
.sinks = BIT(AS3676_SINK_41),
.flags = AS3676_FLAG_RGB | AS3676_FLAG_BLINK,
.max_current = 25000,
},
{
.name = "green",
.sinks = BIT(AS3676_SINK_42),
.flags = AS3676_FLAG_RGB | AS3676_FLAG_BLINK,
.max_current = 25000,
},
{
.name = "blue",
.sinks = BIT(AS3676_SINK_43),
.flags = AS3676_FLAG_RGB | AS3676_FLAG_BLINK,
.max_current = 25000,
},
};
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Features : < OLD >
configurable number of frequency steps (default 6-steps, 200MHz to 1400MHz) you can have 3 to 18 steps. available steps are (in MHz) 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800, 700, 600, 500, 400, 300, 200, 100, 50, 25. { Not For V1 }
Auto-root. You can also remove root via ExTweaks app and install it without rebooting your phone again. Auto-root can be disabled as well.
CPU Overclock/Undervolt support (we have two interfaces for that. both of them are defacto standard)
Cpu governor optimizations
CPU voltage, clock and stepcount interfaces (CPU Overclock/Undervolt)
Available CPU Governors: Ondemand, Lulzactive, SmartassV2, Interactive and Conservative, Performance, Userspace, Powersave
CIFS as module
Available I/O schedulers: CFQ noop, Deadline, SIO, V(R)
Lots of I/O tweaks and filesystem optimizations via some parts of thunderbolt scripts.
Voodoo louder support (already default in all kernels but people ask it if it is supported)
USB Mass Storage mode is working in CWM Touch Recovery ( Soon Touch ) and you can mount both internal as a disk drive
USB mouse and keyboard support
Almost everything is configurable such as scheduler features, thresholds, GPU frequencies, voltages,
--
Click to expand...
Click to collapse
< NEW >
- Based On Jimbo
- Governors: Ondemand, Lulzactive, Performance, Conservative
- Schedulers: Noop, SIO, VR (default) , Many More!
- Using JRCU (++smoothness, ++responsiveness)
- XZ Compression only for KERNEL (+speed, --size)
- Fully compatible with: Voltage Control, SetCPU,NO-Frills CPU
INITRAMFS AND MISC:
- Init.d Support
- CIFS,Support (modules)
- Logger already enabled into the kernel
CPU/GPU:
- NO OC!!!! (100-1700Mhz)
- CPU Undervolt support
- Complete control of freqs/voltages with Voltage Control/SetCPU
- GPU OverclockExperimental @ V2.0
MEMORY & PERFORMACES:
- Some Are From Other Device Via Commit
- ARM CPU Topology + sched_mc (can be enabled via CWM, disabled by default)
- SLQB Allocator (better memory management)
- Improved memory management functions
- Allow CPU Unaligned access (++performaces)
- Disabled all the big debugging (++speed, --size)
OPTIMISATIONS:
- Using Linaro GCC
- GPU UI Rendering
- Compiled with Linaro GCC 4.5-2012.03-dev + A lot of optimisation flags
- Optimised EXT4 filesystem
- Generally optimised code (removed useless functions and variables, fixed warnings)
and many others...
Click to expand...
Click to collapse
--
Nightly Build Kernel
-----------------------------------------------------------------------
|Nightly Build Kernel !|
-----------------------------------------------------------------------
======================================================
Note : This is A Experimental Kernel Please Use Stable Kernel At The TOP You Can Download It
Click to expand...
Click to collapse
Nightly Build Kernel :
Nightly Build Kernel V2.0 Advance Build ~
Cooming Soon!
Click to expand...
Click to collapse
Ok i will try it!
P.S. Both links are for WiFi modules!
hahah THX a lot for this kernel ! this is one of the bestes i´ve ever tested
only 1 question : can i use this kernel on stock ics like arconium 4?
Ooops Fixing Link.
Done .. Link Updated 1 And 2 ']
Sent from my LT26i using XDA
AlfalfaX said:
hahah THX a lot for this kernel ! this is one of the bestes i´ve ever tested
only 1 question : can i use this kernel on stock ics like arconium 4?
Click to expand...
Click to collapse
Yeah.. Its Support all rom on xperia arc.
Sent from my LT26i using XDA
yuhuuuu i will trying and give a review later...
ChaosFirZen said:
Ooops Fixing Link.
Done .. Link Updated 1 And 2 ']
Sent from my LT26i using XDA
Click to expand...
Click to collapse
Click clack the thanks button nigg;D
Great, i must try this kernel but, i would like to see a custom kernel for cm9
Sent From Xperia Arc Using Xda Premium!
Chaos,
not being very good at English, I do not understand everything.
Could you tell me what the governor and what I / O you advise me?
Thx in advance
built-in profile support with default, battery and performance presets (you can change them in CWM Recovery). Even using everything default will save you a lot of battery juice.
Click to expand...
Click to collapse
ummm, where are they in CWM? looking and looking but can't see
other then that all seems to be smooth and fast will test longer for sure
stef67000 said:
Chaos,
not being very good at English, I do not understand everything.
Could you tell me what the governor and what I / O you advise me?
Thx in advance
Click to expand...
Click to collapse
Thats is A Cool Banner ..
Sent from my LT26i using XDA
iambroken said:
ummm, where are they in CWM? looking and looking but can't see
other then that all seems to be smooth and fast will test longer for sure
Click to expand...
Click to collapse
Its On My ROM ... But the Kernel is Smooth and Fast
ChaosFirZen said:
Its On My ROM ... But the Kernel is Smooth and Fast
Click to expand...
Click to collapse
oh I see thanks
it sure seems fast, you're right
hope the battery will be good too on JJ's hybrid
tried all custom ROMS and kernels. all of them too laggy. unable to view youtube without lag.
do i have to convert to ext-4 filesystem?
how to convert, ChaosFirZen?
Actually Yaffs2 is way beeter than ext4 for file system for User space
Sent from my LT18i using Tapatalk
is Yaffs2 in working by default?
previously, i had a galaxy s. and ext-4 would eliminate the lag.
so, how do i convert if the kernels support all the filesystems?
My phone and me Thanks you !!!! You Did A Great Job Thanks for the Effort!!!!!
Try the Kernel is real good!
[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
AOKP (Android Open Kang Project) Milestone1 - Jellybean 4.2.2
{
"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"
}
Updates:: Here is AOKP milestone1 (Android 4.2.2) built from source using my CM repos and kernel. Should run about just as well as the CM version with all of the same bugs or lack there of
Screenshots
Installation Instructions
Requirements
* Rooted (obviously)
* A brain
Installation
1: If you are coming from another ROM do a full wipe
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
1b: if your device is S-ON you must flash your boot.img either with fastboot or some type of GUI program EVERY FLASH (google is your friend)
2: Flash gapps (download below)
3: Reboot
4: Enjoy AOKP
Please read the whole post for changelog, Download links, and other important info
. As always: remember it takes a FULL charge from AC, and a full discharge then re charge batteryt to be accurate. Also leave it plugged in for up to an hour at 100%, Another thing i find helps battery life is to make custom auto-adjustment values if you use auto-brightness. Check below for full changelog Feedback always welcome Please read the Kernel section for more info and full config options for the kernel.
Albinoman887
Working
SMS/MMS
Wi-FI
Data
GPS
Audio
Radio
Camera
Google Now
Internal/External SD card
Bluetooth
H/W Accelerated Video Playback
Native Wi-Fi Tethering
1080p Video Recording
Not Working
????????????
Changelog
July-20
* Synced with upstream - maybe gallery issue will be fixed?
July-18
* initial build
Kernel
ChronicKernel
* Compiled with linaro
* Set flash to disable if battery is below 10% to prevent the random shut-off when taking a pic
* Removed/Disabled KSM
* Removed ZRAM
* User-configurable GPU OC (Not OC'd by default)
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* Reverted CRT hack to smooth animation in Android 4.2.2
* Increased PMEM_MDP as it is needed in Android 4.2.2 to fix soft-reboots
* PM_FAST enabled by default (high power wi-fi when screen is off)
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. If you want more features of the Sultan kernel feel free to flash it, but support will not be provided in this thread.
Other Features of the kernel include:
* OC to 1866Mhtz (default 1566Mhtz)
* Undervolted
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = SIO)
* User-configurable badass gonvernor (default = balanced)
* Sweep2Wake
You can edit many of the settings in /system/etc/init.d/99kernel, here is a snippet of the script with all the config options
Kernel init script: Click Show Content to expand
Code:
#Script originally made by Axetilen. Modified by Sultan (android1234567)
#Updated for albinoman887's ChronicKernel (98% of the credit goes to android1234567. Thanks so much man :)
# Configure your options here #
# Config default CPU Gonvernor (Disabled by default: When disabled uses internal Kernel setting)
# For better battery life switch to badass
# Kernel Default: ondemand
# Possible values
# badass
# ondemand
# interactive
#= lagfee
# performance
GOV=ondemand;
# Config I/O scheduler
# deadline
# cfq
# noop
# vr
# sio (default)
IO=sio;
# Config CPU max frequency
# Default: 1566000 (1566Mhtz)
# Overclockable to - 1836000 (1836Mhtz)
# for badass set to 1566mhtz (best performance/battery life)
MAXFREQ=1566000;
# Config CPU min frequency
# Default: 384000 (384Mhtz)
# Range 384000 - 1944000 (384Mhtz - 1944Mhtz)
MINFREQ=384000;
# Config 3D GPU clock
# 228571000 = 228mhz
# 266667000 = 267mhz (default)
# 300000000 = 300mhz (Recomended For balance of Performance and Battery life)
# 320000000 = 320mhz
GPU=266667000;
# Config 2D GPU clock
# 145455000 = 145mhz
# 160000000 = 160mhz
# 200000000 = 200mhz (default)
# 228571000 = 228mhz (Recomended For balance of Performance and Battery life)
# 266667000 = 267mhz
DD=200000000;
# Badass
# possible values
# 1 = performance
# 2 = balanced
# 3 = battery saving
BADASS=2
# Enable Sweep2Wake
# 0 = disabled (default)
# 1 = enabled
# 2 = enabled (with no button backlight during sweep)
SWEEP=0
# Enable Fastcharge
# 0 = disabled
# 1 = substitute AC to USB charging always
# 2 = substitute AC to USB charging only if there is no USB peripheral detected
FASTCHARGE=0;
# Fsync Control
# Disabled by default (recomended)
# 2 = Fsync disabled
# 1 = Fsync enabled
FSYNC=2;
# TUN
# Disabled by default
# 0 = Disabled
# 1 = Enabled
TUN=0
# End of configurable options #
Please note this is not the full script just a small portion, Check /system/etc/init.d/99kernel for the full script
Bugs
* MHL doesn't work
* Sweep2wake sometimes causes issues with the proximity sensor during calls
Notes
* As of AOSP 4.2.2 ADB now has a whitelist feature. On first connect with adb it will say device offline You need to update your ADB then with the phone connected. Disable and Re-Enable Android Debugging in the Developer Options menu. It will ask if you want to accept and show the PC's RSA key. Select Yes and it will now work as expected
* As of AOSP 4.2.1 Developer Options and Performance setting menu options are hidden until you go into about phone and tap build number repeatedly (aprox. 6 times) this only needs to be done once
* If you are having a lot of soft reboots when waking the device set you min CPU freq. to 384htz in Performance settings. (What? no Performance settings? ummm look up hehe)
* If you are coming from another ROM i highly recommend you perform and Wipe Date/Factory Reset in recovery menu when applying this ROM.
* The gapps linked to does not have photosphere. As far as i know it's not supposed to. If you want photophere search for the flashable zip
* If you can't get MMS to work. Send yourself a MMS. or just wait a day. eventually they will work again
* For the best battery life I suggest the stock settings with the exception of the ONDEMAND governor. Switching to BADASS will yield best battery results
DOWNLOAD
ROM : aokp_holiday_Albinoman887_2013-07-20.zip
Gapps : gapps-jb-20130301-signed.zip
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *
Source Code
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/AOKP
Credits
* android1234567 for getting this porting project going, it was a joint effort between us to get this going
* billibox for his relentless testing
* of course cyanogen, the CyanogenMod project and all who contribute.
* The AOKP project and all who contribute
* And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
* dastin1015 for answering all my n00bish questions, and providing helpful hints and solutions
* android1234567 for all the help with the kernel, without you we wouldn't have new kernel
* tarfu for fixing camera p2z
* NLJ for fixing the Sweep2Wake proximity sensor issue
* A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
Donations
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
For more information, like kernel info (and possibly newer kernel builds) from our kernel chef android1234567 read the 2nd post
Happy Flashing
Albinoman887
Reserved
Too much ROMs omg good work albino and bili
Sent from my Vivid 4G using xda premium
lol
Since these ROMs all seem to be the same, this one have a center clock? Only thing I don't like about CM
Sent from my Vivid 4G using xda premium
joe3681 said:
Since these ROMs all seem to be the same, this one have a center clock? Only thing I don't like about CM
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
What do you mean? And these Roms are very different.
camo_flage said:
Too much ROMs omg good work albino and bili
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
If you think this is too much you're in a whirl of trouble my friend....
Can't even turn on WiFi
Sent from my Vivid 4G using xda premium
joe3681 said:
Can't even turn on WiFi
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
Did you flash boot img??
No. I'll try that. Works without flashing on other roms
Sent from my Vivid 4G using xda premium
NIiice
OT:
I was trying myself to sync the AOKP repos a few weeks ago (when you had first got CM10.1 up) but it ened up freezing half way through some 20 million lines of w.e it was doing and after like 70gb of w.e. was downloaded. I gave up after hours of nothing happening lol.
So am I glad that a dev came through on this thank you! I really dont know how you even keep all that source stuff straight..I am no noob with computers by any means but jeez lol thats some confusing-ness.
ROM REPORT:
So, first build aannnd....its AWESOME! So far everything works as expected. So far no reboots (knock on wood), sound, data, wifi, calls, etc. work great. Seems smooth and very stable (in the few hours I have been testing).
THANKS:
Thank you thank you for helping the few of us left. And they said we couldn't have CM10 because of mic...if we just had these devs when phone came out, I think it would have got way more spotlight. Which is quite sad because I think this phone is one of the nicer on the market (for a 2011 phone).
Thanks, and no problem
Sent from my SGH-M919 using Tapatalk 2
another good rom, much faster then pac, and a little faster than cm10.1, and what i like - it just works)
albinoman887, thank you very much for your work)
I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?
ulsigem said:
I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?
Click to expand...
Click to collapse
My DU rom does the same thing I believe. Albino and I are talking about it
EDITED!: Don't listen to whatever i posted before this was edited
I'm a crazy tired guy xD We will see whats up
ulsigem said:
I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?
Click to expand...
Click to collapse
I am thinking so.
I had a weird one happen too. I think maybe I took a few pictures, had dropbox installed and setup to transfer instantly to my account. After a few shots, dropbox just started FCing along with a system.media FC. I could not even log in to dropbox after that, it kicked me out and FC any time I hit log in, along with the media FC.
I tried clearing data of the app, no go. Tried wiping dalvik in recovery. No go. Then noticed all my photos were missing in gallery before my few pictures I took with this build (I only saw those few pics). I thought weird, I hope they didnt get deleted during install of ROM. But nope, I flashed the sense 4.1 backup I had (its the most stable I got) and everything went back to normal, all pics were there, dropbox works fine, no FC.
I think something is indeed weird with the gallery. 'IS' anyone else having any issues too?
i know it sounds dumb but anyone try redoing permissions? either with "fix permisions" or just running chown -R 1000:1000 /sdcard/ and then chmod -R 644 /sdcard/
if not... try taking the gallery2.apk from cm and see what happens
bilibox said:
My DU rom does the same thing I believe. Albino and I are talking about it
EDITED!: Don't listen to whatever i posted before this was edited
I'm a crazy tired guy xD We will see whats up
Click to expand...
Click to collapse
sorry for offtopic, but.. can you build aosp? (just 4.2.2 without any options.. like vanilla android on nexus devices?) (+root)
kkruglov said:
sorry for offtopic, but.. can you build aosp? (just 4.2.2 without any options.. like vanilla android on nexus devices?) (+root)
Click to expand...
Click to collapse
Ill look into it in the morning
i'll be updating this rom sometime today....just got a lot to compile
|*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!
This is an EXPERIMENTAL Kernel that continues the work of @pengus77, but with some additions i make. That means a huge thank to pengus77! Please check his thread http://forum.xda-developers.com/showthread.php?t=2097788
This kernel is completely based on his latest release.
This kernel only supports newbl and will only work on roms with 3.1 support (these are atm only 4.4 (aka KitKat) Roms and tonyps TheRom that is compatible with the 3.1 kernel
Features:
Features from the kowalski kernel:
3.1.10 Kernel Version
bcmdhd wifi driver
Dynamic FSync
Overclock to 1.5 GHz (Not all phones work well with 1.5 Ghz!)
Undervolting
MultiCore Sched PM
Auto Hotplug
Fast charge
Wifi PM
and many more ...
Features added by me:
PKSM as enhanced KSM module
Built in ZRAM Modul (that makes it possible to use the android default zram solution)
Possibility to use deferred_timer for (P)KSM
0, 16 or 32 MB Ramhack
Support for extra free kbytes tunable (more a ROM dev feature)
Custom vibration force/strength through sysfs
120MHz and 168 MHz frequencies for more battery savings during wakelock
Known bugs:
Camera Bug
Gyro does not work properly
If you want to report a new kernel bug, you must describe your problem in detail, post your kmsg and last_kmsg (if available) (you can found them under /proc/kmsg and /proc/last_kmsg) otherwise the rule is: no log = no issue
Downloads:
This is more a personal kernel build. I have built these kernels for weeks for myself and used them in private. Now i just want to share them with you guys!
You can download the kernels here: https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/ They are labeled like this: firtecy_kernel_X-N.zip where X is either exp for an experimental kernel release and stable for a stable kernel and where N is the build number (this number is always incremental!)
Sourcecode:
You can find the sourcecode at github: https://github.com/Firtecy/kowalski/ the branch is exp. The config file is: "kowalski_defconfig"
The intention of this thread is to continue the 3.1 kernel development pengus started. Development related questions or discussions are appreciated
Have fun!
And to quote pengus77:
On a side note... i'm not really responsible if you decide to test it and your phone melts... right?
Thanks to:
@hjunii for bringing up 3.1 Kernel
@pengus77 for the kowalski kernel
XDA:DevDB Information
Firtecy Kernel - a modified Kowalski Kernel, Kernel for the LG Optimus 2x
Contributors
Firtecy, pengus77, hjunii, djnoxd
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.1#5
Beta Release Date: 2014-08-25
Created 2014-10-31
Last Updated 2014-10-31
Changelog:
firtecy_kernel_exp-5 - 25.8.2014
Added intellactive governor (thanks to @faux123) and powersave
Some bug fixes
Added sync framework and exfat support (but not active for the moment)
Added a "kowalski touch driver" and dt2w files (since they are not stable enough for now, they are disabled)
The reason why I disabled those things is that I didn't had the time to test them. If you want to test them you have to build your own version. Especially for other developers that can be interesting.
Click to expand...
Click to collapse
firtecy_kernel_exp-4 - 25.6.2014
minor updates/fixes from other kernels
Added the min screen on freq back
Added a sysfs attribute to change the min screen on freq
when disabling pksm, it will be disabled completely
Screen on min freq
If your screen is on, this frequency is the lowest that will be used. If your screen goes off for whatever reason the cpu will go to the normal min frequency.
Note: It seems like 120MHz and 168MHz are stable even for screen on, but since there was the question if i can add it, here you go:
How to change the value:
Code:
echo [value] > /sys/module/cpu_tegra/parameters/cpu_screen_on_min_cap
You have to use a value that is in the frequency table, but you have to echo the frequency in KHz, so 120MHz -> 120000KHz:
Code:
echo 120000 > /sys/module/cpu_tegra/parameters/cpu_screen_on_min_cap
This option does not stick after a reboot
According to @BS86 this release should be more stable than exp3 and thanks for testing!
Click to expand...
Click to collapse
firtecy_kernel_exp-3 - 13.6.2014
tons of updates to zram/zcache (picked from faux123 tegra kernels)
crypto: added optimized AES and SHA1 routines
added permission checker for binder IPC
tegra video driver updates
Fixed the voltage table -> all values below 770 MHz are not supported by the regulator chip (thanks to all who helped researching! )
Click to expand...
Click to collapse
firtecy_kernel_exp-2 - 8.6.2014
Added the possibility to change the vibration force (or vibration strength)
Added 120MHz and 168MHz as cpu frequencies
Enabled 600 mV as lowest undervolting value (undervolting is very dangerous if you go too low! Better stay at defaults)
Fixed a nvidia or lg cpu derp.
For security reasons it is not possible that the cpu will go underneath 216MHz when screen is on!
Option to use: No ramhack, 16Mb Ramhack or 32 Mb Ramhack!
Vibration force:
to change the vibration force echo a number between 0 and 127 to /sys/module/tspdrv/parameters/vibration_force. Where 127 is the highest and the default. 20 seems to be the last noticeable value.
Code:
echo [force] > /sys/module/tspdrv/parameters/vibration_force
This option does not stick after a reboot. Rom support will be available (hopefully) soon. I'm preparing a patch for tonyps Rom, so that it is possible to change it in the Rom settings.
120 and 168Mhz:
These values are useful for the case where the phone helds a wake lock. This means because of the wake lock it won't enter deepsleep. The phone would run at 216MHz even if it isn't needed. Running at 168Mhz or even 120MHz should result in a better battery life.
If you experience any problems, try to raise the voltage at this frequencies to a higher value and test again. If it is still unstable report it (with a description of the problem) and change the minimum frequency to 216Mhz.
Click to expand...
Click to collapse
firtecy_kernel_exp-1 - 1.6.2014
Initial release
Base source: kowalski kernel
Added built in ZRam (no need to use zram.ko for longer)
Added PKSM as replacement for ksm (http://code.google.com/p/pksm/)
Enabled deferred timers for pksm and ksm
Notice: Since there is no ksm available, but pksm you will not find the options for ksm in any app. All configurations are no longer under: /sys/kernel/mm/ksm/ , but under: /sys/kernel/mm/pksm/
To deativate pksm run this command as root:
Code:
echo 0 > /sys/kernel/mm/pksm/run
This option does not stick after a reboot
Click to expand...
Click to collapse
How to build your own kernel:
You need a Linux PC with either 32 or 64Bit. I'm using Linux Mint Debian Edition 64Bit. And you will need the following packages:
build-essential kernel-package libncurses5-dev bzip2
For example to install them run:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Hint: If you run into troubles with installing packages, check this post
1. Create a new directory for your kernel building (for example: ~/kernel_p990)
Code:
mkdir ~/kernel_p990
2. cd to your kernel dir
Code:
cd ~/kernel_p990
3. Run this command to download the source code for compiling:
Code:
git clone https://github.com/Firtecy/kowalski
4. Now we need to download the toolchain for compiling: Download it from here: http://www.linaro.org/downloads/ under the Bare-Metal section. It is labeled GCC ARM Embedded. Version: 4.7-2013.q3 ; Release: 13.11
5. Now extract the toolchain to a new dir, for example: ~/kernel_p990/toolchain
6. Now we have to define some values for the build enviroment:
Set the CROSS_COMPILE var to your path where you have downloaded your toolchain. For example:
Code:
export CROSS_COMPILE=~/kernel_p990/toolchain/gcc-arm-none-eabi-4_7-2013q3/bin/arm-none-eabi-
Notice at the end you find this prefix: arm-none-eabi- this is not a dir, but the prefix for all files inside the bin directory(for example: arm-none-eabi-gcc)
7. Set the architecture (processor architecture) for which the kernel should be build. So in our case arm:
Code:
export ARCH=arm
and
Code:
export SUBARCH=arm
8. The next step defines the configurations for the kernel (in this case the configuration is named kowalski_defconig)
Code:
make kowalski_defconfig
Notice: this takes the configuration from the file located under arch/arm/configs and will write it to .config
9. Now we can finally build the kernel :victory: Run:
Code:
make
You will find the kernel under: arch/arm/boot/zImage. You just have to copy the zImage and replace the one found in the flashable zip (e.g. my downloads) under kernel/zImage with your own.
Troubleshooting:
Before you can build or run any from step 8 or 9 you have to make sure that all three vars are set correctly (so ARCH, CROSS_COMPILE and SUBARCH). You can check it by running:
Code:
echo $ARCH
for ARCH (for CROSS_COMPILE and SUBARCH it is the seem, but you have to change the name)
If they are not set correctly repeat step 6 and 7.
If you get a compile error first try to run:
Code:
make clean
and try to build the kernel again.
How to diff 2 files or directories in linux
If you are running linux and have two files on your computer and you want to find the differences you can run the diff command in the terminal.
Let's say you have a file "hjunii/traps.c" and "kowalski/traps.c", this is how you compare them:
Code:
diff -u hjunii/traps.c kowalski/traps.c
The command will compare both and will print an output to the terminal that will be similar to this:
Code:
@@ -27,6 +27,7 @@
#include <linux/delay.h>
#include <linux/init.h>
#include <linux/sched.h>
+#include <linux/slab.h>
#include <linux/atomic.h>
#include <asm/cacheflush.h>
@@ -483,25 +484,38 @@
static inline void
do_cache_op(unsigned long start, unsigned long end, int flags)
{
- struct mm_struct *mm = current->active_mm;
- struct vm_area_struct *vma;
-
if (end < start || flags)
return;
+ return flush_cache_user_range(start, end);
+}
+
+static inline int
+do_cache_op_iov(const struct iovec __user *uiov, unsigned long cnt, int flags)
+{
+ int i, ret = 0;
+ unsigned long len = cnt * sizeof(struct iovec);
+ struct iovec *iov = kmalloc(len, GFP_KERNEL);
- down_read(&mm->mmap_sem);
- vma = find_vma(mm, start);
- if (vma && vma->vm_start < end) {
- if (start < vma->vm_start)
- start = vma->vm_start;
- if (end > vma->vm_end)
- end = vma->vm_end;
+ if (iov == NULL) {
+ ret = -ENOMEM;
+ goto out;
+ }
- up_read(&mm->mmap_sem);
- flush_cache_user_range(start, end);
- return;
+ if (copy_from_user(iov, uiov, len)) {
+ ret = -EFAULT;
+ goto out_free;
}
- up_read(&mm->mmap_sem);
+
+ for (i = 0; i < cnt; ++i) {
+ unsigned long start = (unsigned long __force)iov[i].iov_base;
+ unsigned long end = start + iov[i].iov_len;
+ do_cache_op(start, end, flags);
+ }
+
+out_free:
+ kfree(iov);
+out:
+ return ret;
}
/*
@@ -550,6 +564,10 @@
do_cache_op(regs->ARM_r0, regs->ARM_r1, regs->ARM_r2);
return 0;
+ case NR(cacheflush_iov):
+ do_cache_op_iov((const struct iovec __user *)regs->ARM_r0,
+ regs->ARM_r1, regs->ARM_r2);
+
case NR(usr26):
if (!(elf_hwcap & HWCAP_26BIT))
break;
Each line starting with a "+" are lines that were added, for example:
Code:
+#include <linux/slab.h>
On the other side lines starting with a "-" are lines that were deleted, for example:
Code:
- struct mm_struct *mm = current->active_mm;
A line like the following should just show you were you find the changes:
Code:
@@ -550,6 +564,10 @@
with the following syntax:
Code:
@@ -[line number in 1. file],[number of lines that were printed from 1.file] + [line number in 2. file], [number of lines that were printed from 2.file] @@
But the basic syntax is the following:
Code:
diff -u [base file] [file containing the changes you want to display]
You can also compare whole directories!
ProTip: Install the program "colordiff". It will color the console output, that means the output is more readable!
Syntax:
Code:
diff -u [base file] [file containing the changes you want to display] | colordiff
Example:
Code:
[COLOR="Plum"]@@ -1,8 +1,8 @@[/COLOR]
[COLOR="Red"]-VERSION = 2
-PATCHLEVEL = 6
-SUBLEVEL = 39
-EXTRAVERSION = .4
-NAME = Flesh-Eating Bats with Fangs[/COLOR]
[COLOR="RoyalBlue"]+VERSION = 3
+PATCHLEVEL = 1
+SUBLEVEL = 10
+EXTRAVERSION =
+NAME = "Divemaster Edition"[/COLOR]
Nice New kernel!
will try that one as soon as possible.
thanks for the work.we dont let the 2x die!
Will this work on Mokee rom?
If you don't understand the subconscious you will always bump into it calling it fate...
themistoklisv said:
Will this work on Mokee rom?
If you don't understand the subconscious you will always bump into it calling it fate...
Click to expand...
Click to collapse
Which kernel is included by default in the Rom or can you paste a link?
Gesendet von meinem LG-P990 mit Tapatalk
[email protected]#126
If you don't understand the subconscious you will always bump into it calling it fate...
themistoklisv said:
[email protected]#126
If you don't understand the subconscious you will always bump into it calling it fate...
Click to expand...
Click to collapse
Then I am sorry, but it is not compatible.
The 3.1 kernel differs too much to be compatible with ROMs that are build for an 2.6 kernel
Gesendet von meinem LG-P990 mit Tapatalk
Oh my God, amazing! Finally some serious development! Great work Firtecy. Time to bust CM11 back on my device and try this ramhacked wonder
Oh...i see...this why no ksm settings
Btw...i would suggest a higher ramhack like 32mb like m1 ramhack...but this kernel works great so far...just classic low ram problem exist (well...obviously) need to set an aggresive value (i'm using swap without zram)
Do i need to post a logcat?
Sent from my LG-P990
Will this work with cm 10.1?
Wysłane z mojego LG-P990 przy użyciu Tapatalka
No, it has a different wifi driver, sorry for my english
Sent from my ME173X using XDA Free mobile app
Okey
Wysłane z mojego LG-P990 przy użyciu Tapatalka
The first change:
Okay since there was the wish that there should be a 32 MB ramhack version and the poll showed the same i built one. You can find it at my basketbuild https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/.
So the 32 MB Ramhack version is labeled: firtecy_kernel_exp-1_32MB-RH.zip and the previous one is labeled: firtecy_kernel_exp-1_16MB-RH.zip
I have flashed it and in the settings app, I had 372MB available (Settings > About)
The second change:
Since i have been asked to explain how to build my kernel from source code i wrote a small how to in the third post of the thread. Check it and maybe try to build it for your own.
If you wish i can also write how to change the kernel by your own. (So add new stuff or something similiar)
Great job firtecy...downloading asap
--------------------++-
Very fluid ui with 32rh and with performance control app i can set lmk on boot (dunno..the one come with rom 0527 always reset after reboot)
So far...no bugs for me (except known bugs)
Btw i'm using swap only..no zram but zram works too (i turned it off)
Sent from my LG-P990
Would like to know if random reboot and phone always waking is a kernel related or rom?
Sent from my LG-P990 using Tapatalk 2
mkchan said:
Would like to know if random reboot and phone always waking is a kernel related or rom?
Sent from my LG-P990 using Tapatalk 2
Click to expand...
Click to collapse
I haven't got random reboots or always waking phone in fact on 3.1 kernel there's a bug for waking phone (need press power button twice or thrice)
Maybe your memory full ocupied and still lot queued job to do...that's sometimes happen to me...that's why i need to set lmk a bit aggresive...
Well as dev always said...log or it's not happen
Sent from my LG-P990
Firtecy said:
How to build your own kernel:
You need a Linux PC with either 32 or 64Bit. I'm using Linux Mint Debian Edition 64Bit. And you will need the following packages:
build-essential kernel-package libncurses5-dev bzip2
For example to install them run:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Click to expand...
Click to collapse
I have even had to install libc6-dev-i386 in my 64bit vbox image, then the make seems to have started working :good:
If you wish i can also write how to change the kernel by your own. (So add new stuff or something similiar)
Click to expand...
Click to collapse
+1 (if you don't mind and have time for it )
Thanks!
Thx for your dev. but can you build this kernel for su660?
나의 LG-P990 의 Tapatalk에서 보냄