{
"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"
}
Z5/SUMIRE/E6653 AOSP SABERMOD BUILDS
MARSHMALLOW 6.0.1_r74
Current Build: 20161114
DOWNLOAD
CURRENT ISSUES:
- you tell me!
ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.X (20160726)
BUILDS ALREADY HAVE GAPPS INCLUDED.
KERNEL SOURCE: https://github.com/SonyAosp/kernel/tree/mm-6.0
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- NO MODS OF ANY SORT
CHANGELOG:
(check the download folder for the build corresponding changelog)
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 4x western digital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced with open-source code from SonyAosp repos.
Many thanks to @davidteri91 for letting me use his sources. all credits goes to him.
XDA:DevDB Information
AOSP FOR Z5/SUMIRE/E6653, ROM for the Sony Xperia Z5
Contributors
infected_
Source Code: https://github.com/SonyAosp
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Created 2016-06-05
Last Updated 2016-11-14
Coming from stock sony:
- download build, and extract boot.img from the zip
- download twrp from here
- fastboot flash recovery recovery_20161026.img
- fastboot flash boot boot.img
- enter recovery (vol up @ LED violet), wipe and flash build.
- reboot and you are done!
Coming from an aosp based rom:
- enter recovery, wipe and flash build.
- you are done!
ROOT:
TWRP / FlashFire installable ZIP:
Stable: http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
BUILDS ALREADY HAVE GAPPS. PLEASE DONT BREAK IT BY FLASHING THEM.
How-To
F.A.Q (Frequently Asked Questions)
These are AOSP builds for the Xperia Z5 (E6653)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 4.9.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
Click to expand...
Click to collapse
Source: http://elinux.org
What is SaberMod?
The term "SaberMod" is coming from:
the SaberMod project. Initially the project was used on SaberMod ROM for the Nexus 7 WiFi model (2013). This continued onto the Nexus 4 and Nexus 5 through help of user donations. The toolchains are based on GNU GCC 4.8, 4.9, and 5.0 with AOSP patches forward ported into GNU GCC. SaberMod also provides extra optimization features unlike Google’s toolchain, which gives options for a few amendments in the ROM itself to add more performance gains, such as graphite loop transformation optimizations. SaberMod tracks other utilities from GNU in the toolchain source components that are generally more up to date than AOSP or Linaro toolchains, and almost always tracks the development branches of GNU GCC for the latest patches and bug fixes. The toolchain ecosystem of SaberMod is very different from AOSP, using complex scripts to provide quick, up to date toolchains. Other toolchain sources like the AOSP based toolchain build repository have been heavily modified to work in favor of the way SaberMod toolchains are produced. I have approached some toolchain developers to ask a few questions.
Click to expand...
Click to collapse
Source: http://www.xda-developers.com/interview-with-developers-of-sabermod-hyper-toolchains/
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
Optimization Flags in GCC
What are flags?
For compilers such as GCC, flags are essentially options. A flag can enable or disable an option or feature that is used when compiling (building) code.
What are optimizations?
Optimizations, in the context of compiler flags, are flags that improve some aspect of the code, whether it be size, speed, memory use, and debugging, among other possibilities.
General Optimizations
These optimizations are basic flags in GCC, typically implemented into projects to improve an aspect of the final compiled code.
-O1: Optimization level 1, very basic optimizations, rarely used.
-O2: Optimization level 2, basic optimizations, most commonly used.
-O3: Optimization level 3, basic + experimental optimizations. Large performance boost, but can produce bugs.
-Os: Optimize for size. Most of the optimizations from levels 1 and 2, with extras added to decrease the size of code.
-Ofast: All Optimizations from levels 1, 2, and 3, with extra fast math optimizations.
Typically produces the most bugs, with a large performance gain.
-Og: No performance boost, optimizes the debugging experience, making errors and
warnings more informative to help developers.
-g0: Disables all extra debugging, usually makes code faster.
-fomit-frame-pointer: Removes frame pointers when they aren’t needed, streamlining the code.
-fipa-sra: Removes unused parameters/variables and replaces parameters with the called value, streamlining the code.
-fkeep-inline-functions: Emits static inline functions, even after they’ve been called.
-fmodulo-sched: Reorders instructions in loops in the most optimal way.
-fmodulo-sched-allow-regmoves: a more aggressive -fmodulo-sched, optimizing loops further by allowing register moves
-fgcse-sm: Moves stores out of loops to decrease the workload of loops.
-fgcse-las: Removes redundant loads after a store to reduce the workload.
-fgcse-after-reload: Removes redundant loads after a reload.
-funsafe-loop-optimizations: Optimize more by making assumptions, can create bugs from loops overflowing.
-fira-hoist-pressure: Decreases size of the code by evaluating register pressure for hoist expressions.
-fira-loop-pressure: Makes code smaller and faster by evaluating the register pressure of loops.
-DNDEBUG: Passes the variable for no debugging.
-flto: Enables link time optimizations (LTO) for improved library and executable performance.
Graphite Optimizations
Graphite is a project within gcc that uses the integer set library (ISL) and the chunky loop generator (CLooG) to improve memory use and optimize loops.
-fgraphite: Performs basic graphite loop and memory optimizations.
-floop-interchange: Switches two nested loops.
-floop-strip-mine: Splits a complex loop into a set nested loops.
-floop-block: Splits a loop into nested loops so that the memory fits into caches.
-fgraphite-identity: Creates a visual polyhedral representation of certain graphite optimizations. with some optimizations from ISL such as dead code removal.
-floop-nest-optimize: Optimizes the order of nested loops for data-locality and parallelism. This flag is experimental
-floop-unroll-and-jam: Enable unroll and jam for the ISL loop optimizer.
-floop-parallelize-all: Use graphite data to find and parallelize loops that can be.
Multithreading optimizations
Make code run in multiple jobs (threads) to use a multicore cpu to its fullest potential.
-ftree-parallelize-loops=n: Run parallelized loops is n number of threads.
-pthread: Use the posix thread system for multi-threading.
-fopenmp: Use the OpenMP thread system for multithreading. Tends to use less ram than posix.
Sanitizer Flags
These flags use libsanitizer for memory optimizations.
-fsanitize=leak: Sanitize memory leaks to reduce memory use
-fsanitize=address: Sanitize memory addresses to reduce memory use
-fsanitize=thread: Sanitize excess threads to reduce memory/cpu use. Only for 64bit.
Hardware Optimizations
These optimizations optimize code for the targets cpu, gpu, or ram.
-marm: Uses the ARM instruction set for executable code, improving performance.
-mthumb: Uses the Thumb2 instruction set, improving compatibility.
-mthumb-interwork: Improves compatibility between Thumb and ARM code.
-march=X: Optimizes code for your CPU’s arch, such as armv6, armv7-a, etc
-mcpu=X: Optimizes code for your specific CPU such as cortex-a15, cortex-a53, etc.
-mtune=X: Refer to -mcpu
-mfpu=X: Optimizes code for your CPU’s FPU such as vfpv3. vfpv4, neon, etc.
-mabi=X: Optimizes code ABI for your CPU, such as 32 or 64
Click to expand...
Click to collapse
Thanks for this! Can you tell me what you mean by usable camera?
Mr_Bartek said:
Thanks for this! Can you tell me what you mean by usable camera?
Click to expand...
Click to collapse
camera still takes a bit to focus, and preview has colors switched, but the end photo will be ok.
regards.
wow thanks for this. so happy
edit: oops sorry for quoting
Deleted
albertobom said:
Can't get root in this build also.
?
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:05 PM ---------- Previous post was at 02:51 PM ----------
@iNFECTED
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
@infected_
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------
albertobom said:
Can't get root in this build also.
?
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:05 PM ---------- Previous post was at 02:51 PM ----------
@iNFECTED
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
@infected_
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
albertobom said:
Can't get root in this build also.
?
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:05 PM ---------- Previous post was at 02:51 PM ----------
@iNFECTED
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
@infected_
Sent from my E6653 using XDA-Developers mobile app
@albertobom builds already have superuser included, you dont need to flash any other su...
regards.
albertobom said:
@infected_
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------
@infected_
Sent from my E6653 using XDA-Developers mobile app
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
@infected_
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
You don't need quote some times .... also you will see root options when you enter to settings .... you don't need flash other SU service because it is included
Inviato dal mio E6853 utilizzando Tapatalk
davidteri91 said:
You don't need quote some times .... also you will see root options when you enter to settings .... you don't need flash other SU service because it is included
Inviato dal mio E6853 utilizzando Tapatalk
Click to expand...
Click to collapse
I try to apply layers and nothing happen also try adaway and nothing. I'll try again...
infected_ said:
@albertobom builds already have superuser included, you dont need to flash any other su...
regards.
Click to expand...
Click to collapse
Sent from my E6653 using XDA-Developers mobile app
albertobom said:
I try to apply layers and nothing happen also try adaway and nothing. I'll try again...
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
use the latest build ive uploaded. should be the only one there.
i was using twrp trees from omni, but omni has issues with root/sepolicy ATM.
infected_ said:
use the latest build ive uploaded. should be the only one there.
i was using twrp trees from omni, but omni has issues with root/sepolicy ATM.
Click to expand...
Click to collapse
Works perfect the last build. Thanks my friend. Amazing work. [emoji6]
Sent from my E6653 using XDA-Developers mobile app
Does the fingerprint works with this build?
superalin98 said:
Does the fingerprint works with this build?
Click to expand...
Click to collapse
Works but I don't recommend it because works very buggy. Take loads of time to react.
Sent from my E6653 using XDA-Developers mobile app
After some time playing with the rom, I can easily say this is amazing and it's gonna be my daily driver, but it have some issues also. I get very often interruptions/lags and the display and the audio all stops for some moments. And also some small performance issues here and there and the battery doesn't actually charge when it's powered on but I can live with those. There are mostly display issues but they're not that often. But the nexus imprint is amazing, I have the fingerprint while screen is off, this is amazing and works very well.
superalin98 said:
After some time playing with the rom, I can easily say this is amazing and it's gonna be my daily driver, but it have some issues also. I get very often interruptions/lags and the display and the audio all stops for some moments. And also some small performance issues here and there and the battery doesn't actually charge when it's powered on but I can live with those. There are mostly display issues but they're not that often. But the nexus imprint is amazing, I have the fingerprint while screen is off, this is amazing and works very well.
Click to expand...
Click to collapse
battery charges, but theres no battery icon animation. just look at the device led, when you plug in the charger.
and can you please elaborate "interruptions/lags, the display and the audio all stop, also some small performance issues" ?
regards.
The first boots have been laggy for me, meaning the device was a lot less responsive than the stock one, and not because of the aosp animation speed. Now after 24h I kind of fixed the performance problems setting the governor on performance (not really a long term fix).
The only problems remaining are the display issues which are quite often, once my device shut down itself without me doing anything, and sometimes the fingerprint can be less responsive than ideal ( in the first hours it was way better than expected, maybe even better than the stock one), and also the camera but I don't use it that often so I'm ok with that ( also check out other apps with this rom, there are other behaviors like on the HTC Camera app the UI views are doubled but the colors are normal).
Also about the "interruptions" the device sometimes could just block for some moments or seconds and it also blocks the audio output of the device. I don't know how to explain this better than that.
Also I forgot to tell you, for some reason my device is named sumire_dsds (my phone is not dual sim) in ro.product.device and I needed to modify the updater script myself, I don't know if it was just me or someone else also got issues here.
superalin98 said:
The first boots have been laggy for me, meaning the device was a lot less responsive than the stock one, and not because of the aosp animation speed. Now after 24h I kind of fixed the performance problems setting the governor on performance (not really a long term fix).
The only problems remaining are the display issues which are quite often, once my device shut down itself without me doing anything, and sometimes the fingerprint can be less responsive than ideal ( in the first hours it was way better than expected, maybe even better than the stock one), and also the camera but I don't use it that often so I'm ok with that ( also check out other apps with this rom, there are other behaviors like on the HTC Camera app the UI views are doubled but the colors are normal).
Also about the "interruptions" the device sometimes could just block for some moments or seconds and it also blocks the audio output of the device. I don't know how to explain this better than that.
Also I forgot to tell you, for some reason my device is named sumire_dsds (my phone is not dual sim) in ro.product.device and I needed to modify the updater script myself, I don't know if it was just me or someone else also got issues here
Click to expand...
Click to collapse
i cant replicate what you are describing, except the slowness after boot, which returns to normal if you press power to the device sleep, and then press power again to awake.
and no, this rom doesnt have the product_id has a dual sim.
regards.
new build is up!
- android updated to release 6.0.1_r46.
- decided to use GCC 4.9 on the toolchains (not that 5.3 wasnt stable, but lets play safe), both are updated to release 20160520.
- you can now use twrp, since builds have sony init.
- added "How-to" to third post of OP.
and always check the build changelog for what's been merged.
regards.
Related
[STOCK KERNEL][NOV20] guestekrnL v2.2.1 | stable, smooth [VIBRO- &RAMHACK] [AROMA]
guestekrnL kernel v2.2.1 + GuesteOC v2.3 (TrymHansen) -- with Aroma
- If you like my work, you could press thx, vote positively for this thread or buy me a beer.
If you want to test you device's stability: Try TrymHansen's Myrt Torture Tester! - this tool is awesome : http://forum.xda-developers.com/showthread.php?t=1645938 -- read the instructions first!
Donators from XDA:
Daniele S.
flat__line
Thank you !! :good:
Basic kernel description:
this is a Gingerbread LG O2X Stock kernel! not for use with Cyanogenmod
focus on stability, smoothness and great power consumption
Linux 2.6.32.9
allows Ramhack from 0-96 MByte (this means 0-96 MB additional real RAM, lowering GPU Ram), can be set easily with GuesteOC app, reboots aren't affected by ramhack.
comes with TrymHansen's famous GuesteOC app - following kernel-features can currently be controlled with it:
stepless or stepful over- and underclocking from 216 MHz - 1450 MHz
complete deactivation of second cpu core (and reactivation of course)
setting of maximum screen-off frequency
second cpu core activation speeds/times and auto-calculation of those
change of IO schedulers and read-ahead buffer
swappiness
2-way virtual RAM enhancement: you can choose between Swap & ZRam and enable/disable them on the fly
disable fsync (can be used for higher benchmarks) - attention, disabling is bad for your data in case of sudden power loss and also it can both decrease or increase power consumption
touch-light brightness (101 intensity steps choosable)
special feature: changing auto-backlight intensity (8 intensity steps choosable)
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying
app for Undervolting included (MyrtUV by TrymHansen)
Default CPU speed is 1000 MHz - but you can OC using the included app of course
OnTheFly-changing of kernel logging policy:
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC app.
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
merged/included FORCE_FAST_CHARGE - credits to chad0989
...
For this kernel + the GuesteOC app to work properly you need init.d scripts to be working on your ROM. You should be able to enable them using the latest AROMA installer of guestekrnL >= v2.1, if they are not working on your ROM.The toolchain affects: stability, smoothness, performance & power consumption.If you can't enable ZRam, upgrade to Rebuild 2 release of guestekrnL v2.0 or to a newer releaseIf something else doesn't work: Recommended is Busybox 1.19.4 -- install it with JRummy installer, not a different installer!@ROM-CHEFs (important!):
If you want to directly include guestekrnL v2.x in your Stock ROMs, you will have to set the command line parameters of your ROMs boot.img (via Android kitchen -> modify boot image -> modify command line params) to the following (otherwise Ramhack can't be enabled by the users):
Code:
[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3000001a323ed07 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800
(This will enable the default 32 MB RamHack right after the installation of your ROM with latest guestekrnL included.)
Also in v2.0 the setup script and many setup files of guestekrnL have changed - make sure to merge all the important parts into your ROM setup. Also do not include boot-up scripts which modify LED brightness or virtual RAM and similar stuff or disable kernel logging because that's the job of GuesteOC app.
Changelog latest version:
v2.2.1
smoothness-related changes for higher smoothness
tun.ko now built-in in kernel again
spica toolchain edition now is default preselected on in AROMA installer
v2.2
smoothness-related changes for higher smoothness
better RAM management
tun.ko now as kernel module instead of built-in in kernel
dropped symbi0sis-toolchain edition, instead added spica1234 toolchain edition (like the name says this toolchain has been built by spica1234, credits for this chain go to him)
new unique feature: introducing dual-vibrator support:
in GuesteOC you can set the kernel's vibration intensity (like you already know)
new: intensity 1500 - 2700 uses "weak" vibrator output device for vibration (the one used in original stock kernel)
intensity levels >2700 - 3700 use the "strong" vibrator output device
some prefer the weak device because it seems to be more "accurate", others prefer the stronger one
now it's completely up to you which one to use, without having to change the kernel version! Enjoy
Changelog version 2.1:
v2.1
also read the v2.0 Changelogs!
smoothness-related changes for higher smoothness
added FlixEdition-Power by and for flix123 with the following differences to official version: https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards/compare/master...FlixEdition - the differences are minimal because I merged some good changes into the official version of the kernel. Nevertheless thanks to flix123 for his endless efforts to make this kernel smoother :good::victory: Currently the FlixEdition-Power is only different from guestekrnL-Flix123-Chain in it's default GuesteOC settings (heavy use of second core, different scheduler, stock led brightness,...) and in the default ramhack size. Still flix123 has earned his own edition named after him, as he is the creator of the very smooth flix-toolchain I use for 2 of my builds as well and the one responsible for some more smoothness improvements in the kernel in general.
Still I recommend to use the normal/official build as of the default heavy use of second core of FlixEdition-Power (higher battery drain during use) and because fsync is disabled by default - not everyone likes that.
AROMA Installer is now able to enable init.d, apply smoothness tweaks and convert filesystem to ext4 if a user selects this option - however this option can only be experimental as it replaces the boot image, which should but might not work fine on every stock ROM. Backup first!
Changelog version 2.0 part 3/3:
v2.0 Rebuild 2
this kernel version is still the same as v2.0, so also read the other v2.0 Changelogs!
fixed ZRam not working for everyone - see the changes here: https://github.com/StefanGuendhoer/...mmit/55eac20be15cffe001c5d2ce9452f3887e7fff74
This rebuild has been made for all those who had problems enabling ZRam
Who already got ZRam working and already has latest GuesteOC v2.3, does NOT need to upgrade to this release!
Changelog version 2.0 part 2/3:
v2.0 Rebuild 1
this kernel version is basically the same as v2.0 so please read the changelog of v2.0 additionally!
introducing 2 new editions (built with a toolchain by flix123) for provision of maximum smoothness + an extra AROMA version with ALL kernel editions inside:
{
"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"
}
all other editions are the same as before, only GuesteOC has been updated and they have been recompiled (couldn't avoid)!
AROMA installer package has been built automatically by my new enhanced kernel building script
AROMA installer package allows you to choose between 6 different kernel editions, and allows you to set max. CPU frequency, RamHack size, desired IO Scheduler and ZRam enabled/disabled right during the installation of the guestekrnL kernel
new GuesteOC v2.3 directly included with undervolting AND overvolting (new) - TrymHansen is the creator of guesteOC, thank you very much for this awesome new version, Trym! :good:
complete sources of guestekrnL v2.0 will be published soon - this means the Ramhack for stock, vibration strength for Stock, tweakable kernel logging and other features introduced by me for guestekrnL will be available for other developers too - please don't forget who introduced them first.
Advice:
Please try the new edition(s) compiled with flix123 toolchain (by flix123, thanks to flix for provision!) - you can test & install them along with your preferred settings with the cool new AROMA installer package!
Changelog version 2.0 part 1/3:
v2.0
introducing ramhack + changeable ramhack size (!) (details some lines below) - never seen on any LG O2X stock kernel before
introducing completely adjustable vibration intensity (!) (details some lines below) - never seen on any LG O2X stock kernel before
additional UHOC (ulta high OC) version is available too with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
only use UHOC version if you really need overclocking > 1,45 GHz! otherwise use default version (HOC) with OC up to 1,45 GHz
new symbi0sis toolchain v2 with full arm hard-float ABI support instead of softfp, updated components and tweaks
4 kernel versions:
Which version of the kernel should I take?
only take a version with "-UHOC" at the end of the filename if you really need highest overclocking
symbi0sis toolchain is always changing and work in progress. its purpose is to beat guestekrnL toolchain in kernel smoothness, performance and battery.
rktdi said:
hmm which version to choose? guestekrnL tool chain or symbiosis tool chain? what is the difference?
Click to expand...
Click to collapse
As mentioned the compilation toolchains are used for compiling the kernel under linux (= making binary kernel image out of kernel source files) and affect battery, stability, smoothness (scrolling) and performance of the kernel.
guestekrnL chain is from May 31 2012 (initially created for guestekrnL) while symbi0sis v2 is from October 10 2012. guestekrnL chain is the "good old stable&smooth one" and symbi0sis is the one aiming to beat (be better than) gueste --- war of the chains :laugh:
Some differences:
- symbi0sis chain v2 uses gcc compiler v4.5.4 (2012) while guestekrnL uses gcc v4.5.3 (2011)
- symbi0sis chain v2 uses some newer libs and components than guestekrnL chain
- symbi0sis chain v2 is a full hard-float chain while guestekrnL chain is softfp (probably performance improvement)
- some differences in build flags
- minor other differences
Feedback on the performance of both chains by different users:
- symbi0sis chain v2 seems to provide a bit better power consumption than guestekrnL chain
- symbi0sis chain v2 seems to provide the best overall performance
- guestekrnL chain seems to provide the smoothest slow-scrolling (so the fewest lags when scrolling very slowly)
- guestekrnL chain seems to be a bit more stable than symbi0sis chain (so if you use symbi0sis and have freezes or something you might want to try guestekrnL chain edition)
So just try whatever edition you like, they are both not bad at all.
enhanced kernel building script which automatically builds all 4 versions of the kernel (2 toolchains + UHOC/nonUHOC) - advantage for me basically because it saves time :laugh:
switched back to ZRam without snappy compression due to some lagginess reasons
drastically improved smoothness
various changes in kernel configuration, inspired by 1.1.2 of my CM7 symbi0sis kernel
added full arm hard-float ABI support for performance
there have been some changes in the kernel & GuesteOC default values, so the currently recommended settings will be set in GuesteOC automatically after kernel flash. Try them.
changed auto-brightness steps: the lowest step now is 99% identical to CM7 kernel original default auto-brightness
new build flags for kernel modules
updated GuesteOC app by TrymHansen (thank you!!!) for controlling new kernel feature, supporting new kernel modules structure & mounting and fixing some bugs
tweakable kernel logging (logging disabled by default)
screen-state-based kernel behavior: giving for example the possibility of kernel logging only when screen is on
kernel modules can now be loaded with "modprobe <module-name>" and don't need to be loaded with "insmod <full_module_path/module-name.ko>" - advantage: modprobe doesn't need full module path and also loads dependent modules if there are dependencies
stability improvements
removed Compcache (ZRam is better)
I introduced a completely new kernel OnTheFly feature: (never seen on any LG O2X stock kernel before)
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC (see screenshot).
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
Amazing new features by TrymHansen for GuesteOC:
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying - THX again to TrymHansen, you are the best!
optimized AES and SHA1 routines
current size of Ramhack is OTF readable in /proc/gueste/ramhack_size -> default: 32 MB Ramhack [changebale in GuesteOC]
OTF changeable vibrator (haptic feedback) intensity in /proc/gueste/vibe_intensity (values 1500-3700) [changebale in GuesteOC as well]
enabling optimized crypto routines in defconfig
added 3 small binaries to kernel setup zip for providing GuesteOC app the possibility to change ramhack size
many changes in kernel configuration
battery-related changes
some other, minor things
some tweaks
credits during changes of this release to TrymHansen, morphic, wkpark, vadonka, faux123 and benee - If I forgot someone he/she is most likely mentioned in the git commits or source code merges or the changelogs and commits of my symbi0sis kernel
Ramhack:
Ramhack size in MB (set it in GuesteOC):
MisjudgedTwat said:
0 -- Everything is working
32 -- Everything is working [in rare cases problems with video rec]
48 -- Everything is working [in some cases problems with video rec]
64 -- 1080p video recording/playback doesn't work
80 -- 1080p video recording/playback and some very heavy 3D games doesn't work (Chainfire3D texture resolution adjust help)
96 -- 1080/720p video recording/playback, and many 3D games doesn't work (Chainfire3D texture resolution adjust help)
Click to expand...
Click to collapse
Questions:
What does virtual memory/RAM mean? Virtual memory means that the real available RAM (the more the bigger Ramhack is) can either be compressed to simulate additional RAM (= ZRAM) or it can be enhanced using a Swap file which will be stored on the SD card. Swap is slower than compressed RAM, and compressed RAM is faster but needs more battery!
I OC'd / UV'd too high and get bootloops - what now? If you OC'd too high and get bootloops, re-flash only the kernel, it will remove OC / UV ! No need to re-flash whole ROM.
Download all versions: http://www.mediafire.com/?9lvnkfthj9dbo
Installation: Just flash. Preferably use a clean system without many left-overs from other kernel so you don't get a wrong impression of symbi0sis kernel.
Stefan Gündhör said:
Hi! Nice to hear that you are willing to try guestekrnL :good:
Well since some version guestekrnL deletes some init scripts and some additional stuff flashed along with other kernels like HorsePower, but there might be some files (left-overs) not being deleted by guestekrnL setup script.
Easiest way would be if guestekrnL cleaned the whole init.d folder, but I always criticized this about kernel DEVs doing this because in this cause all custom init.d scripts added by creators of custom ROMs would be lost too.
However there are some things guestekrnL can't/doesn't clean: Tweaks by other kernels in /system/build.prop file per example. These entries will be left over even if you change your kernel.
You could of course replace this file with the original file of the ROM you use.
Additionally in past some kernels also replaced some system files with tweaked or different ones. You can't really undo that.
But basically this is no problem, the tweaks will work with guestekrnL as well. I just mentioned it because user experience / power consumption / stability of "clean ROM + guestekrnL" versus "ROM with different kernel previously + guestekrnL" might be different.
But just go ahead, try guestekrnL and if you think you need a full wipe you can still do that later on
Click to expand...
Click to collapse
Complete sources in the main download folder: http://www.mediafire.com/?9lvnkfthj9dbo
Screenshots: will follow soon
Changelogs & description guestekrnL v1.x:
guestekrnL v1 - for Stock & Stock-based ROMs
Download all Versions: http://www.mediafire.com/?9lvnkfthj9dbo
Latest version (v1.8.1-HighOC): http://www.mediafire.com/?pfby2anqqdifz
Latest FlixEditions by Flix123 (based on guestekrnL 1.8.1 if > v1.3): http://www.mediafire.com/?kguh32agjhmgp
You find the latest GuesteOC tool (for overclocking and tweaking) by TrymHansen always here: LINK
Click to expand...
Click to collapse
You need init.d to be already working on your ROM in order to use GuesteOC! - If u don't have init.d yet, u can enable using a spica PerformancePack
Click to expand...
Click to collapse
Easily build your own (modified) version of guestekrnL: http://forum.xda-developers.com/showthread.php?t=1678049
Click to expand...
Click to collapse
Changelog:
June 09, 2012 -- added best battery edition of guestekrnL v1.8.1: LINK
Changelog:
June 03, 2012 -- guestekrnL v1.8.1-HighOC: LINK
Changelog:
May 30, 2012 -- first community build of guestekrnL is out -- guestekrnL-FlixEdition-v1.1: LINK
Changelog:
May 28, 2012 -- rebuild of guestekrnL SR99R100.1PI.1337 using a different VM -- rebuilt version is smoother than the build from yesterday (May27)!
Changelog:
May 27, 2012 -- guestekrnL SR99R100.1PI.1337: LINK
Changelog:
May 13, 2012 -- guestekrnL v1.7_SE-Final: LINK
Changelog:
May 01, 2012 -- guestekrnL v1.7.0: LINK
Changelog:
April 26, 2012 -- guestekrnL v1.6.2: LINK
Changelog:
April 17, 2012 -- guestekrnL v1.6.1: LINK
Changelog:
April 13, 2012 -- Bugfix01 for guestekrnL v1.6:
Small Bugfix: Trym has discovered a very small bug, causing one of the saved OTF frequencies not to be remembered correctly after reboot. You can solve it by flashing the Bugfix01 or the kernel with Bugfix01 included.
(This is no kernel bug! Just a bug in an /etc/init.d/ script responsible for "remembering" the OTF values)
Click to expand...
Click to collapse
Changelog:
April 12, 2012 -- guestekrnL v1.6 + Bugfix01 (April 13): LINK
Changelog:
March 26, 2012 -- guestekrnL v1.5: LINK
Changelog:
March 20, 2012 -- guestekrnL v1.4.1: LINK
Changelog:
March 07, 2012 -- guestekrnL v1.3.1:
extremely small kernel and modules sizes (even without -Os compilation flag)
both ZRam (+369 MB Ram) and Swap (+383 MB Ram) enabler/disabler available for download - freedom of choice (ZRam enabler will disable Swap and vice-versa) ; Zram should be more performant than Swap, but eventually also drain the battery faster ; both ZRam and Swap are disabled by default
BFQ scheduler updated
many entries added to global kernel configuration file "include/linux/guestekrnl.h" (only important for users interested in compiling guestekrnL from source)
bug fixes, performance tweaks
compilation flags changed (-O2 instead of -Ofast)
some kernel logging removed
xz-compressed kernel image, xz-(de)compression (boot-time) support added
reverted some changes in lowmemorykiller
many voltage and clock/speed adjustments
new version of ZRam enabler, the old one won't work!
stable, not too highly undervolted kernel -- you can UV yourself using UV tools though (only overclockable edition)
Changelog:
March 03, 2012 -- guestekrnL v1.2.1:
Overclocking bug fixed - once CPU is OC'd it will stay OC'd now
changes in cpu speed steps: new steps are 216, 324, 503, 800, 1015, 1100, 1216, 1408 (same steps as etana kernel currently uses)
kernel default cpu speed now 1.0 GHz like stock kernel
screen off max cpu speed now 503 MHz
changes again in second core handling
stability fixes
strong vibration editions (thx to spica1234) -- please note that strong vibration might cause problems if haptic feedback is enabled in LG stock keyboard:
markop90 said:
I guess the vibrator is too strong and LG "tap" sensors are activated moving the cursor randomly
Click to expand...
Click to collapse
Changelog:
March 02, 2012 -- Additional version without OC/UV possibility @1.0 GHz Stock-max.Speed -- for stock kernel lovers
Changelog:
March 01, 2012 -- guestekrnL v1.2 FINAL:
never-seen smoothnes @ 912 MHz (= underclocked)
non-working ramzswap kernel module removed
ZRAM integrated as kernel module (use is optional; use of ZRAM "increases" RAM amount (= +369MB), but might drain battery faster)
activation/deactivation pack for ZRAM
old swap file will be deleted on kernel or zram pack install
lower swappiness if no ZRAM is used
ipv6 enabled again
revert second core activation & treshold back to stock kernel settings for better battery
there will be an additional version with stronger vibration soon (thanks and credits to spica!)
currently two downloadable & flashable kernel ZIPs:
guestekrnL_v1.2_FINAL_withAndrevOC_normalVibration.zip -> Andrev OC Adjuster and Myrt Undervolt GUI will be installed directly with the kernel
guestekrnL_v1.2_FINAL_Bulk_normalVibration.zip -> Only the kernel will be installed
-- pending: version with stronger vibration
Changelog:
February 18, 2012 -- FINAL version of v1.1:
new cpu speed steps & voltages
again more smoooothness (scrolling, responsiveness)
max. ScreenOff CPU frequency lowered to 316 MHz and some other changes (hopefully saving some juice)
3 versions of kernel with different cpu speed steps:
Low overclock version with cpu speed steps 216-316-503-655-816-912-1015-1100 (MHz) -- recommended version!!
Medium overclock version with cpu speed steps 216-316-503-655-816-912-1015-1216 (MHz)
High overclock version with cpu speed steps 216-316-503-655-816-912-1015-1312 (MHz)
the first 7 cpu speed steps are the same in all 3 versions, because I decided these steps are the best choice -- there is only one OC step because there can only be 8 CPU steps (handled by OC tools)
try 1,1Ghz max version, it is smooth enough for nearly everyone I hope, even at 1,0 GHz!!
default max cpu clock (screen on) is 1015 MHz
Features/Description
WIPE DALVIK CACHE BEFORE INSTALL
- EXT2/3/4 built in
- based on official LG v20Q kernel sources
- OC/UV support, overclocking up to 1408MHz
- Andrev OC compatibility
- not highly undervolted by default, you can do this yourself using tools
- however, still some voltage tweaks
- CPU clock locked at max. 503 Mhz while screen is off (taken from swiftextreme kernel if I remeber correctly) - no need to set this in oc tools
- default CPU clock at 1.0 GHz, you can higher/lower it yourself using OC tools
- very smooooooth
- Voodoo Sound
- SLQB
- CIFS, TUN
- SWAP & ZRAM support
- many Tweaks either by me or "inspired" and taken from the source codes of ironkrnL and SwiftExtreme kernel
- compiled with Linaro GCC & Toolchain
- more things which you can find in the latest changelogs
Credits:
- setiron
- fajarep
- cpasjuste
- pastime1971
- spica1234
- supercurio
- dr4go
- LG for v20Q sources
Big THX to spica1234 for supporting me via PM during development!!!!
Latest sources @ Github (1.0 sources @mediafire): https://github.com/StefanGuendhoer/LG-P990-O2X----guestekrnL-for-stock for kernels < 1.6.2 and https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards for kernels > 1.6.2 OR at http://androtransfer.com/?developer=gueste&folder=sources
Source for kernel 1.7-SE is within the download folder of the kernel and @androtransfer and @mediafire!
I'll not use this moment, because I use CM7 + vadonka's kernel. But I followed the topic and kernel development, for future testing based on a stock rom. Thanks Stefan.
totally agree with your initial paragraph, personally I envy the knowledge that shows every day spica, but for the ignorant like me, is much more useful to mention kernel set, and while this is a personal opinion, maybe instead so many parameters to configure, it would be more useful, use presets as a function of the tastes of each user, power, response, saving battery etc etc, well, maybe not the right place here, well, in principle, its kernel is installed normally, it may seem silly but I assure you it is not, say my phone is very special in terms of internal modificaiones already the slightest forces blocked at the moment I tried connecting wifi perfect, seamless gPS, fM radio without problems and later proves the bt. As for the rom, I'm wearing the carburano and is perfectly smooth, no lags etc., for the moment .... we know that android is the opposite of wines worsen over time. Best regards, and I hope this is not really your last job for our phone, I say sincerely.
Stefan,
Thank you very much for this kernel, installed without thinking and testing it now. Couple of observation I made, and opinion I have about the testing stuff.
1. I have no experience in android and stand in minus on technical aspects. You opinion about letting users do the testing of kernels is kind of valid BUT since IMHO, what spica doing is the right thing here. Since this is a development section. So technically developers release their work here so that others developers can test it and contribute 'technically' to improve their work. Honestly speaking dumbass users like me have absolutely no place here .
Everyone who uses the work of a developer have to , should and must understand that what he is doing is testing a possible experimental work and it can lead to unpredictable results. Then analyze what happens, look for possible workaround or solution and give it back to the developer and others, to improve his work.
Dumb users like me have no place here because I don't understand what happens if I use a particular switch or parameter. So there is absolutely no point doing something that I have no clue and then come whining and spoil the developers thread with statements like "helppppppp or my phone is deadddd " or similar things, without even bothering to give details like - for example - what kernel they use, what BB / ROM combination they have, What other application they installed that possibly can create this problem.
Having said that, there are a lot of good developers who patiently help people like this because of the goodness of their heart - you are on of such person. Yet, this being a developer's section should not be treated by noobs as a personal helpdesk to get instant technical support for FREE. If that happens, it affect the development very badly because it wastes everyone's time - especially of the developers.
Phew..! Since my rant is over, I will get back to you 'if' I understand what happens after installing your kernel and eagerly waiting for your latest gift to us .
Congrets for new kernel, nice to see you back
No offence, I don't like even to write this, first time in my life I'm writing this.
OP:
It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers, and so I don't really like this "outsourcing" of sensitive kernel settings to users. There are various good CM7 kernels and they don't need this stuff either. Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation. So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself. The sources of ironkrnL and Swiftextreme kernel (both CM7 kernels) have been very inspiring and helpful.
==>" it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
What I do is something you can't, that's why want to keep it simple What I do is something *new* which needs more skills, knowledge of HW and programming Yes users are user not Devs, That's why I've set simple 'Powersave" and 'Nitros' profile for them who have no more knowledge. And we've an APP now to control these values
==>" and so I don't really like this "outsourcing" of sensitive kernel settings to users"
SENSITIVE? None of my max values are above your or any other Kernel's max values. I've given an opportunity to lower the values not increase the value. And my default values are lower than your or anyother kernel So in terms of SENSITIVE, atleast RC12 values are not sensitive, And I've written kernel modules to not accept any SENSITIVE values,You don't like thiis "outsourcing" values. What you like applying various pre-available *patches* which berely are made for android? Or you dislike someone's coding knowledge?
==> " There are various good CM7 kernels and they don't need this stuff either"
Nobody needs nothing as per your psychology. And as per your psychology CM Devs should have abandoned development after they had released first stable version. As per your psychology they should have stopped adding new features and releasing nighties and RCs? What can we say in other words? "End Of Development?" Nothing is needed until it's valued. Do you know what SR and RC means? PPL who wants stability can stick with SR series. CM7 kernel don't need this stuff cause they've more important other things to concentrate on
==>"Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation"
Where you learn this? Yes nobody uses O3 but Ofast which is 2 steps more optimized flags. Swiftextreme uses Ofast and many devs use Ofast. So as per your theory does these kernels are resulted broken kernels with bugs and issues?
Then I think you should e-mail GCC to remove this O3 flag
==>"So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself"
Your kernel obviously should be stable cause You've done nothing creative. What do you think is resposible for stability? You used LG base source, merged Oc and Voodoo codes and other codes available. So definately it should be stable. But is that stability is credit of yours or LG and other Devs? There is a way much difference in compiling kernel and developing kernel. Anybody can merge changes with basic linux knowledge and issue few commands and kernel is ready. Developer in real mean is someone who creates something out of nothing, who has knowledge of stuff and how stuff work, someone with knowledge of programming to write codes, read and to be understood codes and knowledge to rectify wrong code and correcting them. There is a way much difference in Kernel Compiler and Kernel Developer.
This is no personal, I dont want to hurt anyone but to clear somethings Dont mind
There are some users who prefer simple and stability rather than something with many new features but not so stable.
ryaneu said:
There are some users who prefer simple and stability rather than something with many new features but not so stable.
Click to expand...
Click to collapse
Yes you're absolutely right but whats the theory and logic of writing that paragraph in OP thread?
Does it make sense?
Sent from my LG-P990 using Tapatalk
the difference between the v20l and the v20q kernel is almost nothing.
better off pick any v20l based OC kernels what is tested by the users already
some people believe that the new v20q kernel is have a new features and better stability. i was compared the v20l and the v20q kernel, an other thread im posting the difference and a patch file too. i can say the lg developers did not force themselves.
Moderator Message
Can we stay on topic?? Thanks
Yes that would be bad to close this thread...... for some words that should never have been written....
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
coldfear00 said:
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
Click to expand...
Click to collapse
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Lo_RaT_PeNaT said:
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Click to expand...
Click to collapse
if u wanna talk about kernels and not personal views about who likes what, then stefan should not have said this line " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
Yes that's what I'm pointing, on the first page(OP) of this thread, he should write describtion about his kernel like what other dev does, not about what I or anyone is doing
Never mind
Sent from my LG-P990 using Tapatalk
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
fajarep said:
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
Click to expand...
Click to collapse
fajarep should again return to cheer you too .... not it
getting back to the topic did some1 actually tested this kernel?
Lo_RaT_PeNaT said:
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
Click to expand...
Click to collapse
y r u so hooked up on proving stefan innocent, how do u know he didnt mean to critize spica, and y dosent stefan clear the foul air himself on this thread.
im +1 for spica because if my english aint so bad this line he said looks like criticism to me " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
for my issue resolved, but absolutely sure that the intention of stefan is not apparently be interpreted, also without a doubt, and now please, to the point, the kernel, and I must say that I tried the BT's car and has not been disconnected at any time, not blackscreen not freezes at least for now the battery issue, I can not say for now. Greetings to all.
{
"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"
}
WARNING :
This kernel is only for Galaxy S3 International (GT-I9300) version,
and running Android 4.3 (Samsung ROM's) !
Click below to read the full story..
Many of you knows already knows me from my older LiteGX kernel series (for Android 4.1.2 & 4.3).
This time for SimpleGX, I would like to be closer of stock than LiteGX by removing a lot of unneeded things which finally were not gaining any battery stat at all. I had to review everything from zero (once again !).
SimpleGX is only looking for simplicity and stability, trying to aim for best battery life, smoothness and performance experience, than a pure stock kernel.
SimpleGX will now abandon all scripts that I created for LiteGX (even if some of them are still compatible but not recommended).
I really would like to create back a kernel which was my main idea, a kernel “flash-and-play”, nothing to configure, no need to be a nerd, every newbies can have directly best battery life and smoothness once flashed. Of course that’s every kernel cookers wants, but I would not qualify mine as a real “custom kernel”, since it’s not offering any app to configure it and having much more opportunities, at the cost of many random instabilities (freezes, lags, reboots, etc).
There is many differences between LiteGX and SimpleGX, you will have to compare threads if you want to know them.
I really would like once again to give a huge thanks to my friendly devs (post #3) who helped me a lot during all kernel building phase, learning me, and making adventure possible. I can tell also that Google is really a good friend, I confirm that ^^
I still don’t qualify myself as of a real developer, but just a basic person with some android/linux knowledge already.
As always, I’am enjoying sharing my contribution here on XDA for free, which taking me a lot of time to release, so if you can offer me a little beer (as I’am still jobless yet), I will really appreciate that and you will be added into post #4 ! LiteGX had more than 10000 total downloads, I let you imagine if everybody gave me at least a single dollar ! ^_^
This kernel must be only flashed over an official Samsung ROM and not AOSP/AOKP !
Feel free to include my kernel to your ROMs / Threads but please don't forget to inform/ask first via PM and credit me in your original thread.
★ WHAT TO EXPECT ★ :
(over a pure stock kernel) :
Best battery life experience.
Much better overall performance.
Efficient (only proven to be good ones and not affecting battery life) tweaks.
Stay as close as possible from stock source.
★ FEATURES (up-to-date) ★ :
Base :
Directly based on "GT-I9300_JB_Opensource_Update14" (XXUGND5) JellyBean Android 4.3 source from Samsung (for clean work and stability).
Compiled with Linaro Cross Compiler (4.7.4 / 2014.06) toolchain (optimized for Cortex-A9) with optimization flags.
Ramdisk from XXUGNJ2.
Main :
ZZMoove (v1.0 beta4) governor added (and currently as default). Built-in profiles available HERE.
ZEN as only I/O scheduler.
Wolfson Boeffla Sound (v1.6.6 drivers) compatibility.
hardcore mDNIe tweaks (for better colors + sharpness fix for better readability).
Touch-to-Wake (v1.1a) (enabled by default with 5 secs).
USB charging increased to 900mA.
Allow manual brightness to 300 candela.
init.d support.
Native frandom support.
Native ExFAT (v1.2.9) support.
Native xbox controller support.
CRT-off effect friendly (early_suspend set to 100ms).
Westwood TCP congestion control module activated (and currently as default).
TriangleAway support.
Various tweaks :
All logging and debugging disabled.
Tweaked LMK (LowMemoryKiller).
speedup late resume tweak (faster wakeup of the device).
"GENTLE_FAIR_SLEEPERS" disabled.
"ARCH_POWER" enabled.
"CONFIG_SCHED_AUTOGROUP" enabled.
CRC disabled.
USB OTG enabled.
Doubled min-max ReadAhead.
random: increase entropy levels (both read and write).
writeback: fix occasional slow sync.
slub.c: little tweak for performance improvements.
Misc :
Fully compressed libs ".ko" modules.
Automatic dalvik-cache wiping in kernel flashing procedure.
Automatic verification of android version during flashing procedure.
Features that will NEVER be included in this kernel :
Overclock / Underclock / Undervolt.
ZRAM/SWAP support.
auto-root.
LED control.
Charge control.
Master sequence (screen calibrated).
ABB (Adaptive Body Bias).
Any upgrade of Linux kernel 3.0.XX.
STweaks compatibility.
Dual-Boot Sammy/AOSP.
CyanogenMod compatibility.
MIUI compatibility.
etc.
★ PREREQUISITE ★ :
Any odexed or deodexed international I9300 Samsung 4.3 Jelly Bean ROM.
A custom recovery (CWM recommanded) to flash the kernel.
Be sure to remove any of your init.d scripts which can meet conflicts with the kernel.
★ SOURCE (up-to-date) ★ :
Github >> SimpleGX.
~> DOWNLOAD LINK <~
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!
Changelog
★ All ZZMoove profiles can be found HERE ★
★ CHANGELOG ★ :
29.11.2014 : v3.5.1 released.
Updated ZZMoove governor to 1.0 beta4.
Upgrade full ramdisk from XXUGNJ2.
23.11.2014 : v3.5.0 released.
Stock ZRAM activated back with stock values (excepted 80% swappiness, instead of 60 by default), (no more launcher force close within my whole day experience).
I decided to bring back some interesting performance tweaks from my old LiteGX kernel (which are safe, absolutely close to stock and finally sufficient proved):
- writeback: fix occasional slow sync.
- slub.c: little tweak for performance improvements.
- random: increase entropy levels (both read and write).
Overall kernel experience is now more smooth and reactive.
I also changed all download links from the thread to point to my new personnal ftp (so you will now have to click "download link" from post #1). Downloads will now be faster than ever (no more need of dropbox, etc).
09.11.2014 : v3.4.3 released.
Updated ZZMoove governor to 1.0 beta2
31.10.2014 : v3.4.2 released.
LMK (LowMemoryKiller) tweaks (add +10MB everywhere on 'minfree' file). This should fix stock samsung low memory related problems.
19.10.2014 : v3.4.1 released.
Update ExFAT to version 1.2.9.
Upgrade full ramdisk from XXUGNH4.
15.10.2014 : v3.4.0 released.
Updated ZZMoove governor to 1.0 beta1 (credits @ZaneZam).
Added some patches which was necessary for new ZZMoove 1.0 version:
- simplegx_defconfig: Enable support for CPU temperature reading.
- nohz: Fix update_ts_time_stat idle accounting.
- mach-exynos: Support for current CPU temperature reading from Exynos4 TMU driver.
08.10.2014 : v3.3.2 released.
Finally achieved frandom support fully working and operational (thanks again to @Lord Boeffla for his help).
ramdisk: busybox replaced by the one from Boeffla kernel.
ramdisk: removed useless custom "busyboxlitegx" (+ will save some kernel size).
06.10.2014 : v3.3.1 released.
frandom module now fully and correctly loaded this time (it wasn't the case until now). Thanks to @Lord Boeffla for his precious help.
Some internal ramdisk init changes (modules are now loaded directly from my custom ramdisk script and no more from init.rc).
04.10.2014 : v3.3.0 released.
Updated cross compiler toolchain to 2014.06.
09.09.2014 : v3.2.2 released.
Introduce ZEN I/O scheduler and set as default (and only) scheduler (from my first tests, seems to overall perform slightly better than ROW).
ROW I/O scheduler completely removed.
07.09.2014 : v3.2.1 released.
"CONFIG_SCHED_AUTOGROUP" enabled (will bring multitasking possibilities).
04.09.2014 : v3.2.0 released.
Upgrade full ramdisk from XXUGNG3.
Click below to see older changelog ..
31.08.2014 : v3.1.2 released.
All debug disabled (again) from defconfig side (at the exception of USB).
Due to this above, slightly lowered overall kernel size (again also).
30.08.2014 : v3.1.1 released.
Fixed GPS (which was broken since v3.0.0).
speedup late resume tweak (faster wakeup of the device), added again.
Set back pure stock Update14 defconfig with kernel needs only.
17.08.2014 : v3.1.0 released.
Update ZZMoove governor to 0.9 (beta4).
Fixed ExFAT support.
Update ExFAT to version 1.2.7 (Samsung OSRC from KK sources).
15.08.2014 : v3.0.0 released.
Now directly based from new latest official Samsung source "GT-I9300_JB_Opensource_Update14" (XXUGND5).
speedup late resume tweak removed (from my first tests, it looks useless since new source).
Bunch of debugging part from new defconfig source disabled.
Overall kernel size has been slightly lowered.
15.07.2014 : v2.0.1 released.
Update ZZMoove governor to 0.9 (beta3).
24.06.2014 : v2.0.0 released.
Finally fixed high "Android OS" usage at top of battery stats.
speedup late resume (faster wakeup of the device) (credits Yank555 & AndiP).
Many new (and new way) toolchain optimizations (credits JustArchi).
Compiled with highest possible optimization level (-Ofast).
ALL logging and debugging disabled (credits Yank555, AndiP & JustArchi) :
- android logger.
- kernel logger.
- code side.
- defconfig side.
- init side.
All ".ko" modules now compressed with Linaro Cross Compiler 4.7.4 toolchain from Christopher83 (instead of stock google arm-eabi 4.4.3).
Now extracting/repacking kernel using ArchiKitchen (with latest mkbootimg tool) instead of obsolete dsixda kitchen.
Fixed a little mistake from my simplegx init script within ramdisk which was simply not working until now !
Both smoothest and best battery friendly release ever !
20.06.2014 : v1.9.2 released.
Update ExFAT to version 1.2.7.
16.06.2014 : v1.9.1 released.
Update ZZMoove governor to 0.9 (beta2).
Compilation toolchain optimization.
08.06.2014 : v1.9.0 released.
Update ZZMoove governor (and profiles) to 0.9 (beta1).
Removes Wheatley governor (useless at it was coded initially for dual cores anyway).
29.05.2014 : v1.8.0 released.
Upgrade full ramdisk from XXUGND5.
Some init ramdisk renaming (LiteGX > SimpleGX) that I forgot to do since.
09.05.2014 : v1.7.0 released.
Upgrade full ramdisk from XXUGND2.
30.04.2014 : v1.6.0 released.
Some compilation toolchain optimizations (smoothest release ever).
25.04.2014 : v1.5.0 released.
Upgrade full ramdisk from XXUGND1.
Add 'Wheatley' CPU governor.
(I tested it for few hours now and it looks I'am getting the best battery life experience with it over ZZMoove. Let me know what do you think of it).
20.04.2014 : v1.4.1 released.
Removed pegasusqplus and smartassv2 governors (useless and anyway I prefer to let only ZZMoove).
Removed some kernel code cleanup about pegasusqplus which was needed to get compiled.
19.04.2014 : v1.4.0 released.
Updated cross compiler toolchain to 2014.04.
frandom support is now fully working (kernel should be smooth as butter now).
31.03.2014 : v1.3.1 released.
Update ZZMoove built-in profiles to match latest corrections from Yank.
All ZZMoove built-in profiles (of 0.8) are available HERE.
21.03.2014 : v1.3.0 released.
ramdisk upgraded to XXUGNB6.
Boeffla Sound Engine updated to v1.6.6 (Allow full range volumes for speaker and headphone amplifiers).
ZZMoove 0.8 governor: add latest bug fixes from ZaneZam.
21.03.2014 : v1.2.0 released.
Update ZZMoove governor to 0.8
Change default governor from pegasusqplus to ZZMoove.
17.03.2014 : v1.1.0 released.
New more "stylish" UI when flashing the kernel.
Revert: "unstable power charging ignored" (charging was really faster but battery was draining much faster also, so back to stock).
Add native xbox controller support.
09.03.2014 : v1.0.0-noIUPC released.
Same version as initial, but with ignore unstable power charging removed, so USB tethering should work again (at the cost of a slow battery charging back).
FYI : the "no_IUPC" version means : no Ignore Unstable Power Charging.
08.03.2014 : v1.0.0 released.
Initial release (check actual features on post #1).
Thanks & greetings
★ THANKS & GREETINGS ★ :
XDA board and community
Google
Samsung
CyanogenMod Team
gokhanmoral
Andreilux
wanam
spica1234
ZaneZam
Yank555
DerTeufel1980
googy_anas
hardcore
Lord Boeffla (AndiP)
Christopher83
dsixda
JustArchi
Donations
★ DONATIONS ★ :
Many thanks to @fuxmen ! :good:
Many thanks to @colingpt ! :good:
Many thanks to @letmarebrmbarove ! :good:
Many thanks to @batahulu ! :good:
Many thanks to @sqlpro ! :good:
Thank you to support my work !
Another one from the master. can't wait to test. CHEERS Bro, all the best with your New Kernel.
Nice one - I'll be giving this a go :good:
tnx a lot
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Sent from my Nexus 7 using Tapatalk
sqlpro said:
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Should be OK - it's fine on NA7 Neat.
Nandroid first just in case
Sent from my GT-I9300...
Spannaa said:
Should be OK - it's fine on NA7 Neat.
Nandroid first just in case
Sent from my GT-I9300...
Click to expand...
Click to collapse
I know it will be fine on na7 but I am using na5 base so was not sure. Thank for the reply.
Sent from my GT-I9300 using Tapatalk
i will try this one out
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
reywal said:
i will try this one out
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
Click to expand...
Click to collapse
It's a plug and play, but if you want, you can try trickster for setting stuff like zram on or off, but nothing much to do though.
Your Kernel really rocks. I have been always using your Kernel for close to stock. I am still using LiteGX.
I have tried several one but was looking for one which is hassle free. Your is the one.
This one I will not use now due to USB tethering broken, will wait for next version with that fix.
sqlpro said:
@AndroidGX , is it OK installing this kernel na5 neat rom? Thanks for the advise
Click to expand...
Click to collapse
As long as you flash it on android 4.3 and that the automatical script during procedure won't stop you before checking, then you are good to go
When samsung release his (for example 4.3) source, you can be sure that it will be compatible with every 4.3 future coming firmwares :good:
Sometimes a ramdisk upgrade can also help in some case, so if needed I will do it, no worries
reywal said:
by the way, is there any app by which i can configure the settings? like Stweaks or Boeffla Config?
Click to expand...
Click to collapse
As stated in the story part of post #1, and as Mosh Edd said, this is a flash and play kernel :good: but you can still configure governor settings or some options directly via TricksterMod/SetCPU, etc (don't forget to keep settings after rebooting).
Mosh Edd said:
like zram on or off
Click to expand...
Click to collapse
I intentionally disabled stock ZRAM which was on by default via defconfig so no way to activate it manually :angel:
I decided to always disabled it now on SImpleGX, since zram is eating battery a bit and after some ours of use you will face some random lags.
KSKHH said:
This one I will not use now due to USB tethering broken, will wait for next version with that fix.
Click to expand...
Click to collapse
I informed Lord Boeffla about this bug which affects every kernels, he will take a look as soon as he can :good:
By waiting, I will maybe release a "no_IUPC" (no Ignore Unstable Power Charging) version in parallel for each releases, so each one will choose directly if they prefer fast charging or slow charging but with USB tethering working. I intentionally used IUPC as default because wifi it still working to share (for the few I'am using it..) and that I prefer to not wait hours to charge only 10% of my device
AndroidGX said:
As long as you flash it on android 4.3 and that the automatical script during procedure won't stop you before checking, then you are good to go
When samsung release his (for example 4.3) source, you can be sure that it will be compatible with every 4.3 future coming firmwares :good:
Sometimes a ramdisk upgrade can also help in some case, so if needed I will do it, no worries
Click to expand...
Click to collapse
Thanks for the reply mate. I just installed and all seem to be fine so far. will test couple of more days and update here.
BTW do we need to clean init.d folder ? i know boeffla andi frequently recommends cleaning up init.d folder. is this necessary with your kernel. Note, i dont have any issues so far (only used few mins though).
Thanks for the advise.
sqlpro said:
BTW do we need to clean init.d folder ? i know boeffla andi frequently recommends cleaning up init.d folder. is this necessary with your kernel. Note, i dont have any issues so far (only used few mins though).
Thanks for the advise.
Click to expand...
Click to collapse
He is right because some init.d scripts can affects stock settings from governors for example or try to enable/disable things that is not from my kernel, etc :good:
For exemple, I'am using NeatROM 6.5 and I can see that there is a lot of scripts in init.d already by default bur they don't affect any of kernel part so it's ok
There's no other solution that checking manually each of them, sadly.
Hi,
Thanks for the new kernel!
I come from the latest LiteGX kernel, so I run the cleaner script before flashing this one. My phone hangs when I reboot. I restarted my phone to get it to boot, but then I now have SwiftKey not loading. What could be the problem?
I reverted back you LiteGX for now.
Sent from my GT-I9300 using Tapatalk
I flashed kernel last night and waited until phone settled. Checked if all works fine, and it does, and then put the phone in flight mode.
This morning I checked battery stats and it looks like battery was charging a bit while in flight mode (phone was not connected to any power source).
Funny
All is super smooth. Thank you :thumbup:
Sent from my GT-I9300 using xda app-developers app
rodlane said:
I come from the latest LiteGX kernel, so I run the cleaner script before flashing this one. My phone hangs when I reboot. I restarted my phone to get it to boot, but then I now have SwiftKey not loading. What could be the problem?
Click to expand...
Click to collapse
Strange, as I'am using SwiftKey also and no problem here. If phone hangs at boot this it not normal, did you tried to re-download the kernel from first post ? (maybe a bad download).
If problem still here, maybe try to Try to wipe cache + dalvik from your recovery :good:
pexon said:
This morning I checked battery stats and it looks like battery was charging a bit while in flight mode (phone was not connected to any power source).
Funny
Click to expand...
Click to collapse
I confirm this is funny :laugh:
By waiting, I advice you also to try a wipe cache and dalvik before reaching another 100% and disconnect again to verify :good:
I will try this night aswell to confirm or not if I have the same bug
3.0.31? Why no update to 3.0.101?
Enviado desde mi GT-I9300 mediante Tapatalk
Introduction
This ROM is inspired by JustArchi's build optimizations that provide up to 6x performance boost .
I am not a developer by any means, I did my homework and I figured out how to compile and cherry-pick cool things. I am open to advice and guides that can help me make this ROM even better, you can also always ask for features and I'll do my best to bring them in.
As this is my rom for daily use, it contains many, many tweaks and endless hours of work of the best devs of XDA. In these features you can find Faux's Intelliplug, Yank555 powersuspend driver and many other stuff. At this point if you use any other kernel with my ROM you will lose about 80% of the features and the experience I want to provide will be lost. If you like other custom kernels such as Pink please kindly use official Nightlys.
If you are still here and haven't ran away you must know that you can always ask me for new features you see in other fine roms (Such as Temasek, CrDroid, etc) and if everybody like that feature (Including me) I will gladly bring it into the ROM. Don't forget that if you want a full featured ROM there's plenty of fine choices. The main idea with this is the same as with my old CM11 builds; "To stay as close to Stable CM as possible while adding on a little somethin' somethin' to make things better."
DISCLAIMER: I am not responsible for any damages to your device, always have a nandroid on hand if anything happens
Main Features
Based on CyanogenMod 13 latest updates
ROM compiled with UberTC 5.2
Build optimized with Graphite and O3 flags
Build optimized Cortex A7 architecture
Custom cosmetical changes
Screen Record
Custom msm8226-common device branch (Different PowerHAL)
Custom Kernel with several features out of the box such as:
-Upstream GPU patches
-GPU Overclock
-HTC dynamic fsync
-USB fast charging
-Some Interactive picks
-Power efficient workqueues
-Simple GPU Algorithm
And much more, for a deep insight you can visit my github
{
"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"
}
Installation Instructions:
Upgrading from a previous build:
1.- Flash the ROM
2.- Flash any add-ons you want
3.- Wipe dalvik and cache
4.- Reboot into ROM
Upgrading from any other ROM even CM11:
1.- Full wipe
2.- Flash the ROM
3.- Flash GApps
4.- Flash any add-ons you want
5.- Wipe dalvik and cache
6.- Reboot into ROM
Downloads:
ROM
Build 4
Build 3
Build 2.1
Build 2
Build 1
Kernel
[MM]Beto's_Kernel_V6.0.zip
5.1.1 releases,
Beto's_Kernel_V5.0.zip
Beto's_Kernel_V4.1.zip
My preferred GApps:
Open Gapps
--Recommended Settings--
Nope.
Source and credits:
*CyanogenMod for the awesome ROM and great support for our device
*Somcom3X our beautiful CM maintainer.
*JustArchi for the countless hours of testing build flags and Toolchains.
*Chainfire for the great Superuser.
*bedalus (picked lot of things from your kernel)
*GalacticStrider for his amazing build work on SaberSunset.
*CL3Kener
*Faux
*Synergy510 For his amazing work with Saberize optimizations which made possible this ROM. (I also took his thread as base to make this one )
This ROM wouldn't be possible without them, so please donate and show your support to them.
ROM OS Version: 6.0.1 Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Source: My kernel sauce
Version Information
Status: Stable
Created 01/30/2015
Changelog
Build 4
-Updated to latest cm-13.0
-Changed some out of the box kernel settings
Click to expand...
Click to collapse
Build 3
Synced with latest cm-13.0 sources
MSM8226-Common
- Revert "msm8226-common: Add falcon and peregrine sensors HAL" …
- Revert "msm8226-common: Enable proximity check on wake" …
- Revert "msm8226-common: Enable Ambient Display" …
- msm8226-common: Kill Doze and sensor usage …
vendor/motorola
- Revert "falcon peregrine: Remove proprietary sensors HAL" …
cm/vendor
- Added Kcal control by savoca
- Added latest AdAway
- Added Nova Launcher
Click to expand...
Click to collapse
Build 2.1
Fixed derps with BT and optimzation flags
Click to expand...
Click to collapse
Build 2
ROM:
-Updated to latest cm-13.0 release
Kernel:
-Added Kcal support
-Added Faux Sound Control
Click to expand...
Click to collapse
Build 1
MSM8226-COMMON
-Default scheduler is ROW
[+] Which is vastly superior than default on real life usage
-Killed custom cm PowerHAL in favour of Qualcomm implementation.
[+] This improves battery consumption both on iddle and screen on.
-Disabled hispeed_freq when screen is off
[+] Intended to improve energy usage on iddle
-Replaced some libs to match qcom vendor
[+] This one fix some very annoying logs on the PowerHAL as it looked for libs that didn't exist. Such as “QCOM*PowerHAL:*Failed to acquire lock”
-Added MSM8226 board optimizations
[+] Given more data to the compiler such as number of cores and cache L1/L2 to allow it to optimize the code even further
Frameworks/Base:
-Ability to hide root icon
-Switchable kill-app timer
Build
-Compiled with Arter97 optimization flags
-Build compiled with UberTC 5.3 optimized
Vendor/cm
-Some cosmetical changes
Kernel: (Featuring my old kernel which is a stock kernel with a couple of extra features)
-Upstream GPU patches
-GPU Overclock
-Intelli-Plug and Mako hotplug
-HTC dynamic fsync
-USB fast charging
-Some Interactive picks
-Power efficient workqueues
-Simple GPU Algorithm
-Intelliactive governor
-More TCP congestion
-CPU-Boost on which is needed by qcom PowerHAL
-“A lot” of misc stuff which you can check on my github
Click to expand...
Click to collapse
Final
-Updated to latest cm-12.1 sources
-Reverted some custom PowerHal upstream commits since we are using qcom implementation
-Deleted profile settings that used to turn on MP-Decision on several tasks (We may now use Intelli-Plug without it messing around)
Click to expand...
Click to collapse
Build 26
-Updated to latest CM-12.1 sources
-Added wakelock blocker.
-Default scheduler is ROW again.
-Reverted custom PowerHal implementation
-Reverted readahead back to normal values
Click to expand...
Click to collapse
Build 25
ROM:
Updated to latest cm-12.1 sources.
Removed Nova Launcher
Custom PowerHAL implementation
[+] This one changes the battery profiles, specially for power saving, making the phone actually usable on saving mode (More info here)
Added MSM8226 board optimizations
[+] Given more data to the compiler such as number of cores and cache L1/L2 to allow it to optimize the code even further for our phone.
Bionic changes
[+] Added optimized memcpy implementation for Cortex A7
ART Optimizations
Patch to allow Viper4Android on enforcing mode
Misc UI changes
Kernel:
Pushed readahead to 512Kb
Intelli-Plug updates
Default scheduler is now BFQ
SELinux is now enforced.
soc: qcom: bam_dmux: Add fast-shutdown flag
[+] This one should greatly reduce bam_dmux_wakelock on our 4G device
Click to expand...
Click to collapse
Build 24
-Updated to latest CM-12.1 sources
-Reverted some unnecesary framework/base commits
-Restored MotoDoze
-ROM compiled now with Uber 4.9, which is fairly similar to SaberMod. Just for testing purposes.
-Cleaned my build environment squashing commits
Click to expand...
Click to collapse
Build 23
-Updated to latest CM-12.1 sources
-ROM is now compiled with GCC 4.9, the toolchain that'll be shiped on M.
-Fixed wrong auto-vectorization of ID3 iterator causing various media crashes with badly-tagged MP3s
-Kernel compiled with Linaro 4.9.4
-Added built in SuperSu menu (Require SuperSu)
-Updated to ArchiDroid Optimizations 4.1.
Click to expand...
Click to collapse
Build 22
-Updated to latest CM-12.1 sources
-Refactored kernel after *some guy* decided to fix Interactive governor when there it was nothing wrong with it.
-Updated kernel toolchain to Linaro 4.9.4
-Updated SaberMod 4.8 to latest release
Click to expand...
Click to collapse
Build 19
Updated to latest CM12 sources
Fixed hide supersu icon option
Disabled Faux123 Simple_Ondemand
Enabled Arter97 AdrenoIdler 1.1
Misc kernel cherry-picks I had before my phone died
Click to expand...
Click to collapse
Build 18
-Updated to latest CM12 sources
-Lot of things have been fixed, specially fixed parameters for lowminfree memory and possibly bluetooth hiccups
-Updated SaberMod toolchain.
Click to expand...
Click to collapse
Build 16
Updated to latest CM12 sources
Kernel and ROM are now separated, if you want my kernel it must be downloaded and flashed after the ROM.
Merged pull request of @Frazew
Fixed screen record which I had broke on Build 15
Build lited with Opti-Charger
Misc updates to Kernel
Click to expand...
Click to collapse
Build 15.1
-Finished bringing features of old kernel to the new one
-Implemented misc build.prop tweaks (Commit)
-Introduced Opti-Charger (To improve RAM use, more info in the spoiler)
Custom ROMs in the beginning had limited space to work with which is why Cyanogen introduced opticharging to the custom release tool in order to shrink apks to fit more apps on system partitions of the original android devices. The opticharger script pulls apart apks near the end of the build and optimizes all pngs drawables found in them. Originally this script used optipng which is great and there is absolutely no quality loss involved in the png compressions but more recently I’ve begun using pngquant because it compresses pngs even smaller 30-70% with usually an average of about 50%. Pngquant does result in a slight loss of quality but nobody has noticed yet (See more on pngquant here: http://pngquant.org/) (If you are worried about quality you can always use optipng which compresses without any quality loss themers usually use this option instead)
Currently, CyanogenMod has abandoned the use of the opticharger but many ROMs still use it such as SLIM, AOKP, LiquidSmooth, Dirty Unicorns, Carbon, Validus, and many others. Themers and app developers alike use these techniques as well to make their apps/themes run more smoothly. Making pngs 70% smaller actually makes the loading time 3 times faster for these pngs and also saves you RAM. I understand apks aren't all pngs but you'd be surprised how many junk pngs google has left behind since froyo that serve no purpose but are loaded into your ram with SystemUI anyways. Thankfully opticharging shrinks all of those undesirables by usually 50-70% and saves you several MB worth of space and speeds up your SystemUI. Since you can't unload the system UI this is well worth the effort! My motto always is every little bit counts
Many still argue that high end device don’t need opticharging anymore because they are fast enough to handle these full-sized pngs. While this is true it still doesn’t change the fact that opticharing IS still slightly faster and opticharged apks do use less ram
.
Click to expand...
Click to collapse
Build 15
-Updated latest CM-12.1 sources
-Switched kernel to latest CM sources, meaning you can use Optimus and Spirit kernel now. Make sure to update your bootloader if you don't want "screen-tearing" lines.
-Merged Arter97's fix to Play Store FC's
Click to expand...
Click to collapse
Build 14.1
First attempt to fix suddenly battery drops
Added more TCP congestion options
Click to expand...
Click to collapse
Build 14
Synced latest CM-12.1 sources
Featuring latest 5.1.1 R1 release.
Fixed crazy radio wakeups on deep sleep
Removed p-thread to get more battery life (MOAR!)
Added quick lockscreen gestures (To turn screen on when notification led is blinking and pocket mode)
Switched to latest JusArchi 5.1 gcc optimized for Cortex A7.
Added screen-recorder, which can be enabled on "Buttons" -> "Poweroff Menu"
Probably more stuff I don't remember right now
Click to expand...
Click to collapse
Build 11
Updated to latest CM-12.1 sources 8/05
We are back to my "stock" kernel which doesn't have DT2W
Released 2 variants of my kernel, one with DT2W and the other without it.
Click to expand...
Click to collapse
Build 10.1
Enabled DT2W implementation
Enabled power efficient workqueues
Activated fast charge via USB
Some misc picks to enhance kernel
Click to expand...
Click to collapse
Build 8.1
Fixed kernel Toolchain (Crucial for a perfect synergy with optimizations)
Click to expand...
Click to collapse
Build 8
Featuring Android 5.1.1
Synced latest CM12.1 sources 21/04/15
Updated kernel Toolchain to SaberMod 5.0
Complete rebase to kernel.
Updated graphite flags.
Beast benchmark scores (over 20k)
All old optimizations that are posted on OP are up and running too.
Click to expand...
Click to collapse
Build 6
Updated with latest CM12 sources
Intelli-Plug 4.0 with eco-mode is back.
Added some special changes to hotplug
Added option to hide the annoying icon of root at status bar. (@Pupet_Master bet you are going to love this one)
Switched to Linaro Toolchain 4.9.2 optimized for A7 Cortex architecture. (Rom is still compiled with SaberMod)
Misc tweaks to kernel.
Click to expand...
Click to collapse
Build 5
Reworked Project, added all optimization flags.
Click to expand...
Click to collapse
Build 4
*Synced latest CM12 sources
*No screen-tearing issues
*Re-Enabled MP-Decision
*Added new implementation of Intelliplug directly from Faux's Github
*Removed IntelliMinMax governor (For now)
*Updated powersuspend driver to v1.5
*Updated SaberMod Toolchains
*Ditched my old build environment and bringed up @JustArchi optimizations which takes Android to a whole new level
Important changes:
- Optimized for speed yet more all instructions - ARM and THUMB (-O3)
- Optimized for speed also parts which are compiled with Clang (-O3)
- Turned off all debugging code (lack of -g)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Sorted the common symbols by alignment in descending order. This is to prevent gaps between symbols due to alignment constraints (-Wl,--sort-common)
Click to expand...
Click to collapse
Build 3
Updated CM12 commits.
Initial Modular O3 Implementation … (Yay!)
armv7-a-neon: Apply Correct mfpu and mfloat tunings per arch …
Updated Graphite flags
Speed up Recents Menu, StatusBar and Windows Orientation.
Added a setting to disable expanded notifications.
Disabled MP-Decision (Conflicting with Intelli-Plug when performance per app is ON)
Enabled Intelli-Plug by default.
Misc cherry-picks to polish new optimizations
Click to expand...
Click to collapse
Build 2
Added Graphite optimizations
Added Strict-Aliasing optimizations
Updated latest CM12 sources.
Click to expand...
Click to collapse
FAQ
Thanks a lot @Travisholt92 for writing this guide, please give him a big thanks here!
Question 1: I am coming from (Stock or CM11), how can i install this?
Answer 1:
1. Back up all of your files, text messages, and everything else that you dont want to lose (try Easy Backup in the Google Play Store). You will lose everything stored on your phones internal storage and applications , your SD card will be safe.
2. Download the latest build posted in OP and Download GAPPS and move the .zip files onto your SD card (Remember where you put these files).
3. Shut down your phone.
4. Reboot into recovery mode by holding down the volume down button and the power button, then releasing the power button. This will come up with the Fastboot interface. Press volume down to highlight Recovery and then press volume up to boot into recovery mode.
(through TWRP)
5. Press Wipe
6. Press Advanced Wipe
7. Select Dalvik Cache, Data, Internal Storage, Cache, and System.
(Do not select microSD card or USB OTG)
8. Swipe to wipe.
9. Press Install. At the top of the screen make sure it says "Storage: microSD card". Navigate to the ROM .zip file and press it.
10. Press Add More Zips and select the GAPPS .zip file.
11. Swipe to confirm flash, reboot system, enjoy SaberMod!
(If none of these answers fix your issue read the comments for others having similar issues to see if anybody has found a fix for the issue. If the issue hasn't been meantioned previously please report the issue, leave a comment. Make sure to state what build you are running and what kernel you are using if you installed a custom kernel. If its something that happens when you perform a certain action such as after sending a text your phone reboots, try and be as detailed as possible when reporting the bug)
Question 2: I just installed (insert build name here and issue below). How do i fix this?
A. and my device is stuck at boot animation, device boots but spams with system application errors (meaning installed by your ROM not from GAPPS) , or anything else that prevents you from using your phone.
Answer: Backup your device and follow the directions for answer 1. (install the last ROM you were running if you are coming from an AOSP build if needed to back up your data)
B. and my device boots but spams with my downloaded application errors.
Answer: Uninstall the application and redownload it from the Google Play Store.
Gonna test
Que buena ver un chileno por estos lares, y más aun desarrollando roms, bastante bueno; voy a probar la ROM y ver como anda
English; Gonna test the rom and will say how it works
Any severe bugs up to know?
primewell said:
Any severe bugs up to know?
Click to expand...
Click to collapse
Only CM11 bugs, wich at this stage of develeopment are almost zero. That's the idea of applying only minimal stuff, the result is a enhanced CM11 experience with the same stability.
Next build will inlude GPU and RAM OC.
.
I also prefer CM 11 for now. Better stability and performance. And your ROM is great! No bugs so far. Thanks!
BUG
I Got Alll cores running on 1190hz all time and i can't change the frequencies
SplaszIG said:
I Got Alll cores running on 1190hz all time and i can't change the frequencies
Click to expand...
Click to collapse
It is not a bug, MPdecision shows all cores at full freq, but if you check them at real time (I.E using CoolTool) you'll see they work normally.
Anyway, I DK if add more features on the next build (Halo maybe?) or keep things simple with Linaro and Archi's optimizations. What do you guys think?
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
WiCiO_MeDi said:
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
Click to expand...
Click to collapse
+1
WiCiO_MeDi said:
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
Click to expand...
Click to collapse
Will do.
Thanks for your input!
I Think that modular add ons wolud be great , btw i would like more perfomance improvements too:good:
Wonderful job, hermano trasandino'. One thing I'm missing is the Tap2Wake feature. How can I add it to this ROM ?
Thanks
I'm guessing there's still this mystical memory leak problem as in CM11?
Sent from my XT1039 using XDA Free mobile app
New build is up. Currently I'm adding general tweaks before fetching more advanced stuff. (I'm having a lot of fun on Blechdose's AeroKernel and Faux github )
Changelog:
Updated with latest CM sources
Added GPU OC 550mhz
Added Min CPU Freq 192mhz
GPU optimizations
Added instructions for Cortex A7 architecture
ARM: use -mcpu=cortex-a7 when targeting MSM8226 CPU
Added frequency to corner mappings for msm8226v2
Reverted RAM OC due overheating
Interactive governor misc tweaks.
Click to expand...
Click to collapse
Link: Build 2
Can I flash this doing a clean install from CM12? There will be no problem right?
rodsayd said:
Can I flash this doing a clean install from CM12? There will be no problem right?
Click to expand...
Click to collapse
Yes. That's the way I've done it. Just simply erase everything EXCEPT sdcard and usbotg. Then, as usual, flash this ROM and then Gapps
I've been using it since yesterday and the perfomance is amazing! I will keep this as a daily driver, just one problem: sometimes the camera doesn't take the photo, it freezes just after I push the botton (I had the same problem on CM12).
rodsayd said:
I've been using it since yesterday and the perfomance is amazing! I will keep this as a daily driver, just one problem: sometimes the camera doesn't take the photo, it freezes just after I push the botton (I had the same problem on CM12).
Click to expand...
Click to collapse
Glad to see there's actually someone using and enjoying it. I'm having pretty good battery life and performance too, I guess Linaro and JustArchi's optimizations are just magical.
Regarding the camera, I don't use stock CM11 app but "A Better Camera" from the PlayStore. GIve it a shot and tell me if the issue persists.
Regards!
Great, I will try it. By the way, there isn't block screen notifications on the rom? That would be a nice feature if you can add it and keep up the good work, I'm staying with 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"
}
arter97 kernel for Galaxy S6 / S6 edge / Note 5 / S6 edge Plus
/* Details */
Upgraded to the latest Linux 3.10
Latest Linaro LSK kernel fully merged
Based on the latest Galaxy S6 / Note 5 kernel sources
Fading LED by AndreiLux and other Note 4 developers
Proper, full support for f2fs & backported from latest stable Linux
CPU undervolt support with Synapse
--- Performance & responsiveness improvements ---
UI lags fixed with binder patch
Full unaligned access enabled
Processor scheduler improvements from AndreiLux
Uses LZ4 with zswap
Dynamic fsync from faux123
Networking speed improvements
Random driver backported from mainline Linux
Westwood as default TCP network congestion control
Built with latest Linaro GCC toolchain with latest GNU linker
Entropy hook on storage removed
Default file-system mount option with noatime
ROW I/O scheduler added and set to default
Scheduler, workqueue, network drivers, file-system drivers, commits properly ported from mainline Linux and CodeAurora(Qualcomm)
Interactive CPU governor replaced with CodeAurora(Qualcomm)'s one
Reduced screen-on delay with boosted CPU cores on resume
--- Memory efficiency & management improvements ---
LowMemoryKiller source-code revamped
Various memory tweaks applied
Memory-management commits properly ported from mainline Linux and CodeAurora(Qualcomm)
--- Battery life improvements ---
Intelligently moves apps to LITTLE cores
Power-efficient workqueues from Linaro enabled
Interactive CPU governor patched for better battery life
NVIDIA's power-efficiency improvement commits applied
Power-managements commits properly ported from mainline Linux and CodeAurora(Qualcomm)
And many others... please read the changelog
/* Switch to f2fs */
As mentioned above, this kernel fully supports f2fs.
However, you are completely free to choose not to use f2fs.
You can selectively convert partitions to f2fs using TWRP provided in the downloads.
You should use the provided TWRP at all times after you switched to f2fs.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Supported devices */
--- Galaxy S6---
SM-G920F
SM-G920I
SM-G920S
SM-G920K
SM-G920L
SM-G920T
SM-G920W8
--- Galaxy S6 edge---
SM-G925F
SM-G925I
SM-G925S
SM-G925K
SM-G925L
SM-G925T
SM-G925W8
--- Galaxy Note 5 ---
SM-N920C
SM-N920I
SM-N920G
SM-N920S
SM-N920K
SM-N920L
SM-N920T
SM-N920W8
--- Galaxy S6 edge Plus ---
SM-G928F
SM-G928C
SM-G928I
SM-G928G
SM-G928S
SM-G928K
SM-G928L
SM-G928T
SM-G928W8
/* Warning */
Redistribution, modifying files used within this project's file or integrating with other projects are prohibited with no exceptions other than my projects.
Making mirrors, re-uploading to another servers are also prohibited with no exceptions.
/* Downloads and links */
I cannot test this kernel with TWRP.
Switching to the provided PhilZ Touch recovery is highly recommended for all users.
arter97.com
/* Thanks to */
AndreiLux
faux123
Linaro
MinL(xens0117)
hsk from Matcl
CodeAurora
/* Contact */
Email : [email protected]
Twitter : @arter97_dev
/* Known issues */
None
/* Installation */
1. Put the downloaded kernel on your internal storage
2. Enter ClockworkMod(or PhilZ) recovery
3. Flash kernel
XDA:DevDB Information
arter97 kernel for Galaxy S6 edge Plus, Kernel for the Samsung Galaxy S6 Edge+
Contributors
arter97, AndreiLux
Source Code: https://bitbucket.org/arter97/android_kernel_samsung_exynos7420
Kernel Special Features:
Version Information
Status: Stable
Created 2015-08-30
Last Updated 2016-06-19
/* Changelog */
22.0 - EOL
Support for future firmwares are not guaranteed!
Fixed support for systemless SuperSU
Latest G920FXXU4DPGW sources merged
Linux 4.8 random drivers merged(12 times faster)
- Please remove Seeder if installed as it's completely unnecessary
TWRP rebuilt with latest f2fs-tools v1.7.0
I/O scheduler optimization for UFS(nr_requests)
Added support for Note 7(Grace UI) ROMs
- Please download the right kernel; it's in another directory
- Incomplete support. Few features might be broken as Samsung have not released the sources.
21.1 - EOL
Support for future firmwares are not guaranteed!
Added support for systemless SuperSU
ADB daemon replaced to stock ones
ADB switched to secure mode
TWRP rebuilt with stock adbd for better compatibility
Galaxy S6 flat - LDU correction disabled
21.0
Memory managements sources related to compression merged with Galaxy S7
Swappiness set to 190 for Galaxy S6
Reverted HMP scheduler commits that causes random kernel panic
Enabled HW accelerated SHA2, GHASH, AES_CCM, AES_NEON_BLK
Reverted cpuidle commits to improve performance
Recovery rebuilt to fix adb sideload, f2fs conversion
Fixed Synapse error for Galaxy Note 5, S6 edge Plus
Support added for Xbox game controller
20.0
Major memory leak fixed
Implemented new feature that moves background applications to LITTLE cores automatically to save power
- Default is set to move unimportant apps to 1 LITTLE core(cpu0)
- You can use Synapse to make it more aggressive - move all background apps(including apps like music player) to LITTLE cores(cpu0~3)
Applied upstream f2fs bug fixes
Revamped CPU governor to fix misc issues due to improper merges
ren_max_freq renamed to scaling_max_freq to fix apps like Kernel Aduitor
DVFS auto resetter implemented to workaround ROM's DVFS race-condition resulting in 1200 MHz clock stuck
Removed dynamic fsync for better reliability and memory efficiency
Re-applied previous Mali GPU commits (by AndreiLux)
- Fixes voltage control
- Adjusts throttling threshold
Merged latest memory management behaviors from Nexus 6P Android N and Galaxy S6 stock ROM
Latest Samsung kernel sources merged
Re-introduced sound-control by AndreiLux as a separate release for Galaxy S6
- You may encounter in-call audio issues with this
- Install the regular version if you don't need this
SysV IPC removed
LOAD_FREQ adjustment hack removed
Kernel tick clock changed from 100 Hz to 300 Hz for better performance
Memory management commits from Nexus 6P Android N merged
Few commits and hacks attempted to reduce resume time
Stand-by ARP and multicast packet filters enabled on Wi-Fi drivers (by AndreiLux)
Built with Linaro GCC 6.1
Binder replaced with CodeAurora sources used with Snapdragon 810
ADB updated
Support added for SM-G920T/W8
Support added for SM-G925T/W8
Support added for SM-N920C/I/G/S/K/L/T/W8
Support added for SM-G928F/C/I/G/S/K/L/T/W8
13.1
Updated to Linux 3.10.101
f2fs updated to Linux 4.7 merge window
Music studderings while screen-off fixed
DriveDroid support added
Synapse fixed
Few memory optimizations
TWRP recovery updated to 3.0.2-0
13.0
Updated to Linux 3.10.100
f2fs updated to Linux 4.6 merge window
Removed improper OOM operations resulting in lags
Merged some optimizations from Liquorix kernel
vnswap updated to Galaxy S7 kernel
Few arm64 optimizations added from upstream Linux kernel
Re-merged HMP scheduler updates from Linaro LSK kernel
Fixed OTG and MTP on TWRP recovery
12.0
Updated to Linux 3.10.98
Support for Android 6.0 added
Support for Android 5.1 dropped
- You will encounter boot issues if you're not properly on Marshmallow firmware
Switched to TWRP recovery
- Make sure to use SuperSU v2.68+ if you want to root your device
Switched to Linaro toolchain 5.3 with GNU linker 2.26
f2fs updated to Linux 4.5 merge window
Adaptive LMK disabled by default
SLUB memory allocator performance improved
Insecure ADB from Android N merged
- Make sure to disable USB debugging if you don't use that feature
zswap, zsmalloc(used with vnswap) merged from latest upstream Linux
Memory managements tweaked
interactive CPU governor tweaked for better responsiveness
Note 5 - used GPU configurations from the S6
11.0
Updated to Linux 3.10.94
Latest Note 5, S6 kernel sources merged
Latest ramdisk, dtb.img merged
Slow Wi-Fi turn-on issue fixed with memory tweaks
X (10.0)
https://en.wikipedia.org/wiki/Roman_numerals
Few possible binder errors fixed
Minor compiler optimizations done to binder
New linker used with compilation (hg-binutils 2.25.51.0.4)
10.0-beta2
Samsung framework's automatic application killer(SPCM) re-enabled
Adaptive LMK re-enabled
scaling_max_freq renamed to ren_max_freq
- Please use Synapse to change CPU max frequency
Core limit on screen-off removed
- Careful observation shows there's not much of a difference
Responsiveness and power consumption tweaks made to hotplugging driver
10.0-beta1
Stand-by ARP and multicast packet filters enabled on Wi-Fi drivers
- This may potentially help battery drain on Wi-Fi connected
CPU max frequency override blocked
Samsung framework's automatic application killer(SPCM) disabled
All A53 cores are now allowed to be turned on during screen-off
Few commits reverted to fix screen-on delay
Adaptive LMK disabled to improve multitasking and potentially increase battery life
Fixed an issue with bottom keys unusable when external output is connected
9.4
Updated to Linux 3.10.93
10.0-alpha discontinued after confirming zram's performance is worse than zswap+vnswap
10.0's display color switcher implemented
- Original code from gokhanmoral's Siyah kernel for i9300
- Toggle by quadruply tapping the multitasking button
- This may not work on edge variants
Added option to allow A57 cores to be turned on during screen-off
(Check the OP's reserved post for details)
Possible race-condition during boot fixed
Memory reclaiming function completely removed to fix performance degradation as time goes on
10.0-alpha3
9.3 changes merged
A new display's color switcher implemented
- Original code from gokhanmoral's Siyah kernel for i9300
- Toggle by quadruply tapping the multitasking button
- This may not work on Note 5 or S6 edge Plus
9.3
Switched back to Samsung's CPU governor to fix performance weirdness
CPU governor patched to be more responsiveness
Boot time decreased
10.0-alpha2
9.2 changes merged
CPU frequency boosts on hotplugging to improve responsiveness
9.2
CPU governor downgraded to LA.BR.1.3.2 to improve performance
Kernel panics related to process reclaim fixed
10.0-alpha1
f2fs updated to Linux 4.4 merge window
Process reclaiming code from LG G4 added to LowMemoryKiller
Adaptive LMK disabled for better multitasking
zram and its dependencies updated to the mainline Linux
Replaced zswap+vnswap with zram
Swap size reduced from 1280MB to 1024MB
zram can be potentially faster than zswap with parallelized compression - max_comp_streams
If testing doesn't show improved memory managements, zram will be removed
This kernel is unstable and regular end-user should avoid it.
Try this only if you're brave and back-up before you proceed.
9.1
Kies, Smart-Switch issue fixed
Added proploader for customizing kernel parameters
9.0
Major performance degradation issue fixed
9.0-beta7
FAST mode on vnswap disabled to fix random reboots(kernel panic)
CPU governor updated to LA.BF64.1.2.2_rb4.6
9.0-beta5
IRQ, CPU hotplug commits reverted to reduce screen-on delay
Hotplugging reconfigured to drastically reduce screen-on delay
Cortex-A53 errata 843419 fix re-enabled to fix invalid instructions
Possible no-deep-sleep issue fixed
9.0-beta4
"CPU cores boosted on screen-on request" reverted to fix screen-on delay
Exynos 7420 IPA and PMU changes applied to CodeAurora's CPU governor
9.0-beta3
Hotplugging properly disabled during screen-on for saving few CPU cycles
Only 2 A53 cores are allowed to be turned on during screen-off
- This significantly helps saving battery life during screen-off
more than just lowering CPU frequency
CPU cores boosted on screen-on request earlier than stock kernel by hundreds of milliseconds
for reduced screen-on delay
Interactive CPU governor replaced with CodeAurora(Qualcomm)'s one
- This version has many advancements compared to stock version
(Benchmark)
8.1
RCU, IRQ, topology merged with CodeAurora(Qualcomm)
ION: system heap allocation time reduced
8.0
Updated to Linux 3.10.92
8.0-alpha2
Hundreds of file-system drivers, memory-management commits ported from CodeAurora(Qualcomm)
This kernel is unstable and regular end-user should avoid it.
Try this only if you're brave and back-up before you proceed.
8.0-alpha1
Scheduler, workqueue, network drivers, power-managements commits backported from mainline Linux and CodeAurora(Qualcomm)
for better performance, responsiveness and power consumption
(Thanks to XileForce)
This kernel is unstable and regular end-user should avoid it.
Try this only if you're brave and back-up before you proceed.
7.1
Recovery device detection fixed for Note 5, S6 edge Plus variants
7.0
Updated to Linux 3.10.91
Graphics drivers updated
PhilZ Touch recovery updated
- Fixes USB storage unusable after first eject
- Fixes kernel, recovery, EFS backups
7.0-beta2
SELinux completely disabled
- This should greatly increase available memory, however might decrease stability as Touchwiz Android 5.1 is full of hardcoded SELinux stuffs
Dual-Sim model support dropped due to development inconsistencies
7.0-beta1
LowMemoryKiller minfree, vmpressure adjusted for better multitasking
Latest Note 5, S6 kernel sources merged
Latest ramdisk, dtb.img merged
Input booster issue fixed for S6, S6 edge variants
CONFIG_EXYNOS5_DYNAMIC_CPU_HOTPLUG_SLEEP_PREPARE set to 1 for better stand-by battery life
Support for G9208, G9200, G920FD, N9208, N9200, N920CD added (untested)
- Please read the 'Supported devices' section
- These variants are untested, please report if it's not working as intended
7.0-alpha2
LowMemoryKiller durp fixed
Kernel panic log shortened to prevent truncation
This kernel is unstable and regular end-user should avoid it.
Try this only if you're brave and back-up before you proceed.
7.0-alpha1
LowMemoryKiller replaced with CodeAurora(Qualcomm)'s version
LowMemoryKiller optimizations(via RBTREE) by Motorola merged
Adaptive LMK enabled
LMK values updated from Nexus 6
f2fs and other drivers updated to use new shrinker API
Automatic process-based memory reclaim method added and enabled
"Drop file-system caches on screen-off to reduce screen-on delay" reverted
This kernel is unstable and regular end-user should avoid it.
Try this only if you're brave and back-up before you proceed.
6.0
f2fs updated to Linux 4.3-rc4
ROW I/O Scheduler by Qualcomm added and set as the default
5.1
Updated to Linux 3.10.90
TCP Congestion Control set to westwood
N920G and G928G support added
5.0
Updated to Linux 3.10.88
Major memory managements changes for better responsiveness
- Reverted vfs_cache_pressure back to 100
- Dirty writeback adjusted(reduced)
- dirty_expire_centisecs and user_reserve_kbytes tweaked
- Drop file-system caches on screen-off to reduce screen-on delay
- S6 & S6 edge - LowMemoryKiller values tweaked
- Note 5 & S6 edge Plus - LowMemoryKiller values reverted back to stock
- Replaced FHA with DHA
- swap-on-disk disabled by default(/system/swapfile)
4.3
Power efficient workqueues enabled by default
Few optimizations to storage performance
Added option to revert back to stock memory managements
- This will give you even better responsiveness at the cost of vastly reduced multitasking performance and increased chance of background services malfunctioning
- Install use_stock_memory_managements.zip from the recovery to enable
- Remove /system/bin/lmktweak to disable
- This will only work on 4.3+ versions
- This is not enabled by default
4.2
Sound-control temporarily removed for fixing in-call volume
4.1
Potential performance degradation issue fixed
VPNCLIENT_SECURITY enabled
(Fixes Wi-Fi calling on T-Mobile)
4.0
G928F,T,W8 support added
Sound-control by AndreiLux added
Synapse loading fixed
Serious malfunction related to LowMemoryKiller issue fixed
Attempt made to fix T-Mobile Wi-Fi calling (Note 5/S6 edge Plus only, untested)
3.6
N920C,I,S,K,L,T,W8 and G928C,I,S,K,L support added
/* To kang or not to kang */
I prefer "open" to all stuffs, explicitly except for my personal kernels.
I've once used to use private Git repository for my kernels and just release the source-codes as a tarball,
which means that other developers who are interested in my kernel's changes would not get the specific changes they want while not violating XDA forum rules or GPL.
That was almost 3 years ago which by then, I was a newbie developer on XDA.
I was afraid other big developers merging all of my changes and I'll get buried down.
However, I've changed my mind and opened up my Git access to everyone after thinking my previous actions did not belongs to XDA's spirit.
That was a big move for myself of re-thinking what should be open.
Later down on the road as I gained more development skills, I've contributed into CyanogenMod and other's custom kernel and ROMs for fixing stuffs, introducing new concepts or improving performance.
During such process, there were quite a lot of occurrences where I was actually the first one to do those things.
For those who're familiar with "temasek ROM", you may know that after I became a contributor, temasek rose even more into the center of other AOSP ROMs' attention, as I was the first to introduce new exciting stuffs such as compiler changes or f2fs. And I quickly gained dozens of followers on my GitHub account.
And eventually, people *kang*ed my changes. Sometimes invalidating my authorship.
It surely is not a right thing to do, but I let it slide as it didn't matter that much. I believed that if my changes are good enough, it'd be better to end up with a larger user base rather than being a **** trying to hunt down every ROM developers who're doing it wrong.
Same story goes to my ROMs.
My real first popular ROM was back-to-n00t, which is a ported ROM from Galaxy S3 LTE to provide stable Touchwiz KitKat experience to the Galaxy S3 3G users.
I opened up everything to GitHub. And I even encouraged that other ROM developers to use my ROM as a base to work on their own ROM as I knew there are a lot of Touchwiz ROM cookers who're way better than me on modifying SystemUI or frameworks(via smali) BUT aren't too good on porting ROMs. I hoped that my ports can be a great base for others to work on their own modifications.
Now those spirits repeated on the Galaxy S6, I opened up everything about back-to-n0t3.
However, I do not do or believe those same things with the kernels.
There are far less kernel developers on XDA compared to ROM developers. ROMs are much more appealing for an "Android newbie" to go tweak. You can modify UI, enable some hidden settings and even port features from another devices.
So when ROMs gets copied off, users can easily distinguish if that was stolen or not.
Let’s say a well-known developer A ported S6 designs and features to the S4. Next day, less-known developer B uploads a ROM on XDA that claims to do the same thing. First thing that comes to the users’ mind would be ‘Is that guy a thief?’.
However, same thing cannot be said on the kernels as they work on a much lower level. You can’t distinguish individual custom kernels just by staring at your phone.
If a ROM developer choose to go use other’s custom kernel and integrate it into their ROM, it’s most likely that users won’t appreciate that custom kernel developer whose work powers that ROM. Let’s face it, not all users care about “Thanks to”, “Credits” sections, and let me tell you, those are the majority. Now some custom kernel developers might be OK with that. However, I’m not. Unlike most developers on XDA, I got fascinated to Android because it runs on Linux kernel. Modifying Linux kernel was the first thing I’ve done on my Android device, not modifying ROM. And I spent years and years on gaining information on Linux/Android kernels and tweaking, coding myself. While I don’t necessarily care users choosing to NOT use my kernel, I cannot stand that my kernel would be installed on one’s device which its owner don’t even know which kernel, which developer who made that kernel is. That is why I’m against with the idea of integrating custom kernels into custom ROMs. If you want your users to have a custom kernel, let them learn themselves what that kernel really is, what does it offers, and who developed it. “For the ease of flashing/installation” is not an excuse for me. Take yourself a few more minutes to download a kernel from the web, and a few more seconds to flash a secondary ZIP file from the recovery. Is that hard? Time-consuming? Absolutely not.
I hope everyone gets the idea why I'm sticking with the idea of "don't integrate my kernel into others".
Cheers.
/* Customizing kernel */
You can install Synapse from the Play store to control voltage and other frequencies.
To control some core kernel parameters, create /sdcard/arter97 as a directory and do the followings
--- Enable Adaptive LMK ---
Enabling Adaptive LMK will increase responsiveness at the cost of reduced multitasking capabilities and battery life.
Create a text file with 1 letter "0" under /sdcard/arter97 named "adaptive_lmk" and reboot
--- Disable LED fade ---
If you have issues with other 3rd-party LED controlling apps, try disabling it.
Create a text file with 1 letter "0" under /sdcard/arter97 named "fade_led" and reboot
reserved 4
reserved 5
reserved 6
It seems like you guys cannot even root this device.
There's fully functional PhilZ Touch recovery in the downloads, feel free to use it to flash SuperSU and spread the words.
But please don't make mirror!
Also, please note once you modify /system partition (by installing custom recovery or SuperSU), you need custom kernel to be installed.
yessss
my friend i see that asked you to help and you did thats great man dont forget top keep support our community
i loved your great stuff with s6 + s6 edge and now here love you man continue with your great work :good::good::good::good:
---------- Post added at 02:14 PM ---------- Previous post was at 02:05 PM ----------
my friend i have deepsleep problem ...is the kernel fix it???
---------- Post added at 02:36 PM ---------- Previous post was at 02:14 PM ----------
ok i can confirm working like acharm recovery+root+kernel
\exellent job thx
\now only rom !!!!!!!! lolllll
OK. So I'm gonna go ahead and the the edge plus tomorrow.
Would love to have a sprint version sometime.
Sent from my SM-G928P using Tapatalk
My LIFE is safed !!!
Great news for Edge+ users !
I got sm-g928t.
Which one I need to take "g928ci" "g928skl"?
Regards
eminem5055 said:
Great news for Edge+ users !
I got sm-g928t.
Which one I need to take "g928ci" "g928skl"?
Regards
Click to expand...
Click to collapse
No support for tmobile :crying:
avetny said:
No support for tmobile :crying:
Click to expand...
Click to collapse
Says coming soon. So. Fingers crossed.
Please tmobile
370 viewes and not thx come on people he gaves us best stufff :good::good::good:
thanks
Deleted
---------- Post added at 08:07 AM ---------- Previous post was at 07:44 AM ----------
Not able to flash recovery error : custom binary blocked by frp lock
arter97 said:
It seems like you guys cannot even root this device.
There's fully functional PhilZ Touch recovery in the downloads, feel free to use it to flash SuperSU and spread the words.
But please don't make mirror!
Also, please note once you modify /system partition (by installing custom recovery or SuperSU), you need custom kernel to be installed.
Click to expand...
Click to collapse
hi, I have a Singaporean S6 Edge+ SM-G928I
just to confirm your instructions, the correct recovery to flash is: http://arter97.com/browse/exynos742...ecovery-g928ci-3.6-philz_touch_6.59.0.tar.md5 ?
your "g928ci" folder is for my SM-G928I too?
also do you have a link for superSU to flash in recovery?
Kirisakura-Kernel for the OnePlus 8 Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the OnePlus 8 Pro aka InstantNoodle.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 865 that´s built into the OP8 Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
I´d like to mention @tbalden ´s excellent CleanSlate features at this place. They improve usability by a big margin for me personally. The highly customizable sweep to sleep implementation (adjustable to different navigation settings), long tap to bring down status bar (very useful on a big device), backlight dimmer and notification reminder are very useful features that I use personally every day, which can be enabled rootless if one desires to run without root.
Another big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from OnePlus for Android 10 and intended for use on OOS-Stable releases
- compiled with Clang 11.0.3 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.146
- CAF base for the Snapdragon 865 (SD865) updated to CAF-Tag LA.UM.8.12.r1-12500-sm8250.0
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Cleanslate Features included! See @tbaldens´s CleanSlate Thread for more information
- Flashable via EXKM and FKM on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken, @joshuous and @tbalden for the rootless implementation )
- updates from kernel/common
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
GPU related features:
- GPU driver updated to latest CAF-State
- remove POPP functionality from GPU driver to avoid constant fight about downscaling with msm-adreno-tz
- don´t wake the gpu on touch input, instead wake when receiving an ioctl
- don´t copy fence names by default to save a bit of cpu-time (explanation)
- msm: kgsl: Stop slab shrinker when no more pages can be reclaimed
File System related features:
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture
- Backlight Dimmer - possibility to use lower panel brightness (switch DC dimming off in Lab settings!)
- KCAL Color Control (credit to @savoca)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF default)
- various fixes for PSI-Monitor, which is used by the userspace lowmemorykiller-daemon
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- various other changes from mainline
- included zstd as an option for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- improve memory allocations in various subsystems
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- fix several coding issues detected by newer Clang-Toolchains
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching OnePlus firmware. When OOS receives an update it takes OnePlus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk-stable, if you choose to use Magisk.
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=313864
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10
1.0.0 Initial Release
1.2.0 https://forum.xda-developers.com/showpost.php?p=83260487&postcount=67
1.2.2 https://forum.xda-developers.com/showpost.php?p=83521551&postcount=119
1.2.4 https://forum.xda-developers.com/showpost.php?p=83539543&postcount=125
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid and @mwilky for their awesome roms and work!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the OnePlus 8 Pro
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OP8PRO_InstantNoodle
Kernel Special Features:
Version Information
Status: Stable
Created 2020-06-19
Last Updated 2020-09-20
FAQ
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from matching firmware you are on and flash the extracted boot.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
Please also take a log at the FAQ one post above. It covers some procedural steps as well and serves as a guideline too!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
Hello everyone
I want to lose a few words about this kernel.
Before anybody asks, it´s made for the OP8 Pro only!
As you may or may not have noticed by reading the OP this kernel is very far from the stock base.
Adding linux-stable upstream and CAF-Upstream causes the commit-count to increase from 805000 to about 840000.
A "higher" commit count does not automatically translater to a better kernel. However upstreaming linux-stable and the CAF-Base to the latest code is an important aspect, that´s often cast aside. (after all the android kernel is based on the linux-kernel and the CAF-Base is the kernel base OnePlus bases the kernel for the OP8 Pro on) . Many developers work constantly on improving the linux-stable branches with commits that are tested, same goes for the qualcomm developers over at the CAF-Forums.
The main goals of this kernel are summarized in the OP. I encourage everyone to at least read once through it.
Here´s a short summary of what I think are the most characteristic and important aspects (also an excerpt from the first post of this thread ):
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be (and probably is) the first 4.19 kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If some of that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 865 that´s built into the OP8 Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
I invite everybody to try the kernel
If you face any bugs, I´d appreciate if bug reports are done in the proper way, like it is asked for and explained in the 2nd and 3rd post.
If you read the OP you probably noticed I´m not talking about any improvments (some call it even magic) to performance or battery life. This is not one of the direct goals of this kernel.
If the modifications present in the kernel make you feel a noticable difference in either of these I´m very happy for you. I know that artifical benchmarks are improved and some other things I tested.
If this kernel is not for you you can very easy return to the stock kernel, like it´s described in the FAQ as well!
There might not be updates of this kernel for every single linux-stable upstream revision that is released at kernel.org or every single new commit added to the tree, but rather less updates but bigger ones.
I guess that gives everybody a rough idea of where this project might be going.
I wish everybody a nice day
Loved this for the 7 pro. Welcome ?
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Excellent, welcome!
Hey buddy! Nice to see you here! ?
possible to add option to disable touchboost?
tbalden said:
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Thank you! Glad to have you as a wingman for a very long time across different devices now!
Keep on rocking with all the CleanSlate goodies!
Reuben_skelz92 said:
Loved this for the 7 pro. Welcome
Click to expand...
Click to collapse
kristofpetho said:
Excellent, welcome!
Click to expand...
Click to collapse
TheKnux said:
Hey buddy! Nice to see you here!
Click to expand...
Click to collapse
Thank you
Nekromantik said:
possible to add option to disable touchboost?
Click to expand...
Click to collapse
Yes, since all Cleanslate features are included it´s accessible via CleanSlate config app.
https://forum.xda-developers.com/showpost.php?p=82598221&postcount=192
Gestures and Extras Section - Stock touchboost.
nice to see ya here
Doing a sexy dance right this minute! :victory: Dam glad your covering this device now also buddy Always a great solid kernel that runs smooth and fluid without issue! :good:
Omg the kernel was amazing on the OP7P, can't wait to use this one again on my 8!
Running smooth as butter for me ?
Thank you sir, donation sent.
Nice to see this Kernel here for the 8pro
Gesendet von meinem IN2023 mit Tapatalk
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
Try to disable zram/swap
cultofluna said:
Try to disable zram/swap
Click to expand...
Click to collapse
still around 65%
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
Freak07 said:
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Click to expand...
Click to collapse
good hardware, suck software