[ROM] [6.0.1] [Build 4] [03/04] Unofficial CyanogenMod 13.0

[ROM] [6.0.1] [Build 4] [03/04] Unofficial CyanogenMod 13.0 - Moto G 4G Android Development

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.

Related

[ROM][CM-10.1]arter97's Linaro-built CyanogenMod 10.1.3 based ROM V4 for Galaxy S3

{
"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's Linaro-built CyanogenMod 10.1.3 based ROM V4 for Galaxy S3 [Android 4.2.2]
* Tux is a penguin character and the official mascot of the Linux kernel.
* Above character is a redesigned Tux by @irendah07
● "What is this?"
'this' is a custom ROM built for Galaxy S3 based on CyanogenMod 10.1.3 code.
The main differences are 'Optimizations' and 'Features'.
I'm a huge fan of stock AOSP and I developed this without screwing up stock CyanogenMod's feeling.
You won't find any major UI differences.
I know that this article is very long. Please take your time on reading this.
You should at least know what this ROM offers you. Right?
● Features
Performance improvements & optimizations
- Built with latest Linaro stable toolchain with lots of optimizations flags
- Built with latest Java Development Kit(JDK) - (7u45)
- All *.jar, *.apk files within the ROM are uncompressed, zipaligned for maximum read speeds
- Optimized all images within the ROM by image_optim
- fstrim, remount all partitions with discard option on boot
- FSTRIM is performed while installing
- Optimize all /system, /cache, /data partitions with journal_data_writeback while installing
- Use Exynos optimized memcpy, memset
- Light build.prop optimizations
New features
- ListView animation by team ThinkingBridge (ignore others credit. This was originally designed and coded by ThinkingBridge)
- Camera Shutter Sound control
- Status-bar Quick Peek with Timeout control
- Status-bar transparency control with seperate Lock-screen transparency from Carbon
- 0% transparency on notification icons (icons on the status-bar are basically clearer)
- HALO from ParanoidAndroid (not 2.0)
- Screenshot Quick Trash
- Improved download/upload animation (just go to market and download anything)
- Vertical Electron-beam animation
- Animation scale in Development settings now has additional 0.6x ~ 0.9x (for those who thinks 0.5x is too fast and 1.0x is too slow)
- f2fs supported installation (for those who uses f2fs file-system on /system like me)
- Multitasking UI is now fullscreen
- LED notification behavior is same as CyanogenMod 10.1.0 (turn off the screen, the LED will go off)
- bootanimation is from http://forum.xda-developers.com/showthread.php?t=2429613
- Removed CMstats, CMupdater
- Full, proper exFAT, NTFS support
- No kernel is included in this build since kernels doesn't support gcc 4.8 out-of-the-box.
- Gesture based lockscreen security
- Pinch to enable expanded desktop added to Trebuchet (go to Settings->Launcher->General)
- AOKP custom system animations (go to Settings->System->AOKP Custom System Animations)
- added ADB over network QuickSettings Tile
- back-to-kill timeout control by neighbors28 from DokDo ROM
- DMB functionality for SHV-E210S, SHV-E210K (needs kernel-side support)
● What you need to know
- Even with all of those changes above, you still won't find any major UI differences.
- Linaro toolchain offers many optimizations than the stock Google's toolchain.
Also, the latest gcc 4.8 is used. Basically, this ROM has gcc 4.8 + Linaro optimizations.
Optimization flags includes : -w -s -pipe -O3 -marm -munaligned-access -mcpu=cortex-a9 -mtune=cortex-a9 -march=armv7-a -mfloat-abi=softfp -mfpu=neon -fno-unsafe-math-optimizations -mvectorize-with-neon-quad -fgcse-lm -fgcse-sm -fsched-spec-load -fforce-addr -fno-tree-vectorize -fno-tree-slp-vectorize -fno-defer-pop -fmerge-constants -fmerge-all-constants -fgcse-after-reload -fno-unsafe-loop-optimizations -fomit-frame-pointer -finline-functions -funswitch-loops -fpredictive-commoning -fivopts
-ffast-math has been explicitly disabled due to causing major and minor problems here and there across the entire ROM.
- Java Development Kit(JDK) 7 offers more stable, secure and optimized result than previous versions.
The latest 7u45 has been used.
- image_optim(https://github.com/toy/image_optim) is an image optimizer.
It can reduce image's size up to 95%. It will make the image load faster.
image_optim has, literally, took 26 hours to optimize the entire ROM.
- Uncompressed *.jar, *.apk will result in faster read speeds and reduce CPU loads by skipping decompression unlike any other ROMs out there.
It, of course, will use more space than stock CyanogenMod ROMs.
This ROM + optimized gapps will use about 680 MB in size.
- FSTRIM is a trim-like functionality on SSDs.
http://www.xda-developers.com/android/yet-another-reason-to-update-to-android-4-3-trim-support
- No kernel is included in this build since kernels doesn't support gcc 4.8 out-of-the-box.
Please use other 3rd-party kernel or stock CyanogenMod 10.1's boot.img.
- journal_data_writeback is an option to EXT4 partitions.
It will write datas to RAM first and flush it later. It will increase write speed dramatically.
- ListView is originally designed and coded by the team ThinkingBridge and can be controlled from Settings -> System.
Other ROM devs mostly has their credit written wrong. Please give proper credit to the original author!
- Camera Shutter Sound can be controlled from Settings -> Sound.
Please note that disabling the Camera Shutter Sound can be illegal in some areas.
- Status-bar transparency is cherry-picked from Carbon ROM and can be controlled from Settings -> Status Bar.
Lock-screen transparency has its separate control.
- HALO is cherry-picked from neighbors28's Github who ported HALO to DokDo ROM from ParanoidAndroid.
Credit goes to neighbors28 and other DokDo ROM developers and ParanoidAndroid ROM developers.
(Unfortunately, HALO included in this ROM is not 2.0 yet. Maybe not forever.)
- Light build.prop optimizations only has :
browser.tioptimization=true
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=false
debug.performance.tuning=1
persist.sys.purgeable_assets=1
ril.category.delay=0
ro.config.nocheckin=1
ro.gpu.driver=1
ro.HOME_APP_ADJ=1
ro.HorizontalBUA=true
ro.HorizontalVVM=true
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.media.enc.jpeg.quality=100
ro.product.gpu.driver=1
ro.ril.spender.bending=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=90
● FAQ (Frequently Asked Questions)
Q : What is Linaro and why should I care about them?
A : Linaro is a not-for-profit engineering organization consolidating and optimizing open source Linux software and tools for the ARM architecture. It's widely known to provide the best optimized toolchain sets for arm-eabi and Android. Not only can it bring more faster binary, it can also bring stable, more bug-fixed binary as well. I care compiler optimizations more than the Android source code itself. Since compiler optimizations can speed up the same source code up to 5x, I hunted a lot for the best optimization flags available for Android. As a result, this ROM is speedier, more reliable than other ROMs that uses stock Google's toolchain.
Q : What about Linaro 4.9?
A : Linaro toolchain is built on the official GNU's code. Since GNU hasn't even finished on gcc 4.9 yet, Linaro 4.9 can be considered unstable. I'll work on it when GNU officially releases gcc 4.9.
Q : Can you teach me how to build ROM using Linaro toolchain?
A : There are tutorials of how to build ROM using Linaro toolchain on XDA already. Google is your friend.
Q : Is this ROM open source?
A : For selective parts, yes. Framework and Settings are available on http://bitbucket.org/arter97 . Don't repo init towards my repository. It doesn't have all repositories for full ROM build.
Q : No plans for CyanogenMod 10.2?
A : Yes, I do have plans on rebasing on CyanogenMod 10.2. I'm waiting for CyanogenMod 10.2's source code becoming bit more stabilized.
Q : Can I install your ROM on top of CyanogenMod 10.2 without factory reset?
A : No. Upper versions of Android's data are not compatible with older versions. You have to do a full data wipe in order to install my ROM on top of CyanogenMod 10.2.
Q : I got stuck on Galaxy SIII logo HELP!!!
A : Let me say it again, this ROM DOES NOT includes any kernel. Since kernel built with gcc 4.8 doesn't boot at all, I decided to remove kernel out of this ROM. Please use other kernel.
Q : What is F2FS?
A : F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. I use a custom-kernel that has F2FS support and I use my /system, /cache, /data with F2FS. F2FS support on this ROM is mainly for me Please don't ask me how to use F2FS.
Q : Some app crashes!
A : I won't get any sort of bug reports on app crashing on my ROM. My ROM uses Linaro and it can break some compatibility between userspace applications. Popular example, Handcent SMS. And it will not be fixed.
● Supported devices
- GT-I9300
- SHW-M440S (Korean 3G variant)
- SHV-E210S (Korean SK-LTE variant) (Fully applies telephony patches)
- SHV-E210K (Korean KT-LTE variant) (Fully applies telephony patches)
● Installation
- Download ROM from http://d-h.st/users/arter97/?fld_id=25066
or Downloads tab on the top
(Supported device All-In-One zip installation file)
- Download gapps from http://d-h.st/VtQ
(Checkout http://forum.xda-developers.com/showthread.php?p=45406214 for more information on my gapps. It's also uncompressed and optimized. I highly recommend to use my gapps with my ROM.)
- Download kernel
- Use Clockworkmod or TWRP
- Flash ROM, gapps, kernel in order.
- Enjoy!
● To do
- Korean translation
- Increase volume steps
● Disclaimer
Code:
/*
* 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 ROM
* 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.
*/
- No mirrors are allowed. Please ask me if you need any mirrors.
- Do not use files within my ROM and redistribute or edit.
- Redistribution or modifications are not allowed.
● Thanks to
- @irendah07 for the stylish drawing
- CyanogenMod (https://github.com/CyanogenMod)
- ParanoidAndroid (https://github.com/ParanoidAndroid)
- DokDo(neighbors28) (https://github.com/DokDo-Project)
- lion0738 (https://github.com/lion0738)
- Linaro (http://www.linaro.org)
- ThinkingBridge (https://github.com/ThinkingBridge)
- Carbon (https://github.com/CarbonDev)
- Der-Schubi (https://github.com/Der-Schubi)
- gal3 (갤3)
Comments are always welcomed!
Please hit "Thanks"!
XDA:DevDB Information
arter97's Linaro-built CyanogenMod, a ROM for the Samsung Galaxy S III I9300
Contributors
arter97
ROM OS Version: 4.2.x Jelly Bean
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: V4
Stable Release Date: 2013-11-07
Created 2013-09-19
Last Updated 2013-11-07

Changelog
● Changelog
- V4 : compiler option -funroll-loops has been removed; it was causing weird issues such as suddenly-fast-playing bootanimation.
built using Linaro toolchain 2013.10
built using JDK 7u45
host has been upgraded from Ubuntu 12.04 to Ubuntu 13.10 with gcc 4.8.2
dalvikvm, libdvm has been compiled with -ffast-math option for faster java runtime
--- This will be most likely the end of CyanogenMod 10.1 release. Since CyanogenMod 10.2 has a stabler M source tree, arter97 ROM will be getting rebased for Android 4.3 ---
- V3 : compiler option -fno-fast-math added to completely disable -ffast-math, -fmodulo-sched option removed; this will drastically improve system stability. (+ fixes video recording, WebKit parsing errors)
added -funroll-loops -fivopts compiler options to gain performance
built using JDK 7u40
used blobs from TheMuppets
added AOKP custom system animations (go to Settings->System->AOKP Custom System Animations)
fixed SHV-E210 variant's Airplane mode switch issues
Gallery2: reduce the latency between cam&camcorder switch
partial KO translations by lion0738
fade recents thumbnail to transparent earlier
show Expanded desktop toggle at the lock screen as well
play lock screen sound sooner
added ADB over network QuickSettings Tile
added back-to-kill timeout control by neighbors28 from DokDo ROM
- V2 : rebased on CyanogenMod 10.1.3 stable (adds CMAccount)
Revert Vold changes from Android 4.3; it may cause external SDcard mounting errors resulting in com.android.media force closes.
Added 01fstrim to init.d to replace Vold functionality of fstrim (remounts partitions with discard option, fstrim /system, /data, /cache; checkout adb logcat | grep arter97)
Focal has been removed; please download it from Google Play
Superuser deamon has been removed to provide more free resource to the system
added "Gesture based lockscreen security"
apns-conf.xml updated for SHV-E210
disabled additional MMS patch for SHV-E210 since it was causing SMS sending errors
back-to-kill timeout adjusted to 0.75s
misc Trebuchet changes to improve responsiveness
Pinch to enable expanded desktop added to Trebuchet (go to Settings->Launcher->General)
- V1 : initial release

Known issues
● Known issues
- As of V2, CMAccount has been added and it can cause FC loop on initial setup for some users.
After clicking like crazy, OK button on the FC message, you will be able to bypass the FC.
Sorrt for the inconvenience! But it looks like a source-code issues up from CyanogenMod

reserved
reserved #3

1 question : is navbar included with removal of 3-dot menu overflow button ?
if not, then please add it, and fix bug that 3-dot menu overflow button doesn't go off when nav bar is enabled.
this bug in all cm10.1 roms.

RohanAJoshi said:
1 question : is navbar included with removal of 3-dot menu overflow button ?
if not, then please add it, and fix bug that 3-dot menu overflow button doesn't go off when nav bar is enabled.
this bug in all cm10.1 roms.
Click to expand...
Click to collapse
Navbar is not included at all. (And I don't have it planned)
If you want to enable it, you have to do a build.prop trick.
Can you give me a open-source ROM address that has that 3-dot fixed?

Thank you for this ROM! Can you tell me if the ROM has a good camera (like no FC etc bugs etc) and also if there are any graphic glitches etc like some other CM roms?
Thanks again for your work!

zadusimple said:
Thank you for this ROM! Can you tell me if the ROM has a good camera (like no FC etc bugs etc) and also if there are any graphic glitches etc like some other CM roms?
Thanks again for your work!
Click to expand...
Click to collapse
What you've asked is identical to official CyanogenMod 10.1.3.
As of a personal experience, I haven't had any issues with the stock Camera app.
Graphic glitches are barely noticeable.
(Not like early CM-10.2 stage)
Sent from my SHV-E210S using xda app-developers app

A dumb question. Why based on 10.1? CM ditched 10.1 alltogether? Why not move to 10.2, it's stable now, and the glitches are gone? I'd love to try your rom, the feature list is amazing (I really want to try F2FS) as soon as you move to 10.2 CM base.

granets said:
A dumb question. Why based on 10.1? CM ditched 10.1 alltogether? Why not move to 10.2, it's stable now, and the glitches are gone? I'd love to try your rom, the feature list is amazing (I really want to try F2FS) as soon as you move to 10.2 CM base.
Click to expand...
Click to collapse
Because I want "stability".
If CyanogenMod 10.2 is stable, they would already put a "M", "RC", or "stable" tag.
They didn't.
I consider it unstable at the moment.
It's a quite big pain in the a** to build a ROM that's based on nightly since I'm not good on maintaining Git.
But, I do understand you.
If I have more free time, I'll try to
About F2FS, it's a serious journey both to you and the device.
Of course you need a FULL device wipe and you need an appropriate kernel, ROM and recovery.
What this means is you are stuck using one kernel, one ROM, one recovery.
(version may vary)
I make all three of them so I am free to use F2FS on my device.
But you, sometimes, may want to try other? Then you are in big trouble.
If you want your life to be more easier to live, I recommend not to try so

com.andriod.media force close

adilrenzu said:
com.andriod.media force close
Click to expand...
Click to collapse
Which ROM were you using before?
Sent from my SHV-E210S using xda app-developers app

arter97 said:
which rom were you using before?
Sent from my shv-e210s using xda app-developers app
Click to expand...
Click to collapse
cm 10.1.3 rc2

adilrenzu said:
cm 10.1.3 rc2
Click to expand...
Click to collapse
Can you tell me
Kernel/gapps/other mods you've flashed
Sent from my SHV-E210S using xda app-developers app

arter97 said:
Navbar is not included at all. (And I don't have it planned)
If you want to enable it, you have to do a build.prop trick.
Can you give me a open-source ROM address that has that 3-dot fixed?
Click to expand...
Click to collapse
latest rootbox (10.1) builds have 3 dots fix, and temasek's builds based on 10.2.
.
plz plan for nav bar.

arter97 said:
can you tell me
kernel/gapps/other mods you've flashed
sent from my shv-e210s using xda app-developers app
Click to expand...
Click to collapse
no mods or gapps but i flashed googy max kernel, may b that's the problem, cant you make it compatible with this kernel please

adilrenzu said:
no mods or gapps but i flashed googy max kernel, may b that's the problem, cant you make it compatible with this kernel please
Click to expand...
Click to collapse
i just flashed temasek kernel and not start just w8 on the bootanimation :S

FINEEEEE said:
i just flashed temasek kernel and not start just w8 on the bootanimation :S
Click to expand...
Click to collapse
I think this rom is compatible with only the kernel which support F2FS.
Sent from my GT-I9300 using XDA Premium 4 mobile app

adilrenzu said:
I think this rom is compatible with only the kernel which support F2FS.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
uhmm thx then what kernel are compatible with F2FS?..

FINEEEEE said:
uhmm thx then what kernel are compatible with F2FS?..
Click to expand...
Click to collapse
I dnt know. I hv seen this word first time.
Sent from my GT-I9300 using XDA Premium 4 mobile app

[KERNEL] [4.3] [29 Nov.] ★ SimpleGX v3.5.1 ★

★ 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

arter97 kernel for Galaxy S6 edge Plus

{
"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?

[Kernel] AX7 Hybrid Kernel - R21 - AOSP and STOCK (B25) - 2017U ONLY

Reserved
Wifi Fix if not available with AX7-Hybrid in LOS based ROMS
The problem is that for some reason the ROM does not load the wlan.ko module at boot, so if you run into a "no wifi" situation with a LOS Based ROM all you have to do is navigate to the sbin folder and run the shell script named insmod.sh with your favorite ROOT Explorer APP. Right after you execute the file Wifi will be available. I'm looking into a permanent solution for this, stay tuned.
How to Bypass SafetyNet bootloader and/or root checks
* If comming from a clean flash of ROM or GAPS only do the following:
Magisk Approach
Flash the UnSu file from HERE
Flash my latest Kernel
Flash the latest Magisk from this thread:
Donwload Magisk Manager from the Playstore
Enable Magisk Hide in Magisk Manager
Profit, SafetyNet Checks will pass, all green!
SuperSU Approach
Flash the UnSu file from HERE
Flash my latest Kernel
Flash the latest SuperSU from this thread:
Donwload RootSwitch APP from HERE
Unpack the zip and install the apk inside it
Open Root Switch and disable root
Profit! SafetyNet checks will all be green!
Battery Life Extender (BLX) feature
In order to configure the cap you'll have to navigate to:
Code:
/sys/class/misc/batterylifeextender/charging_cap_level
edit the file and put the cap you want the battery to charge to, i won't recommend setting a cap lower than 90% cause then the phone could abruptely stop a fast charging cycle and damage your battery. If you want to have your phone charging to 100% just put 100 in the file and close it. No need to reboot, just plug and unplug your charger.
On a side note, this value will be set at 97% after every boot. So you'll need to manually change it back to 100.

AX7Kernel Changelogs:
AX7-Hybrid R22- 06/02/2017
Removed the WiFi module and instead it is now compiled within the Kernel to fix the problem with the Hotspot
AX7-Hybrid R21- 05/23/2017
Split both kernels, now there is a STOCK and LOS version again due to the camera incompatibility between Stock B25 and LOS.
Updated Camera driver from B25 2017U. Do not attempt to use on any other variant because it will break your camera. You've been warned!
Adreno Idler added
Updated LOS Kernel Sources
AX7-Hybrid R20- 05/02/2017
Temp camera fix for B25 2017U users. Do not attempt to use on any other variant because it will break your camera. You've been warned!
Added other options that i can't remember now (You can check my github ). I will release a new update once B25 source is released and from there update the changelog properly.
AX7-Hybrid R14 - 04/17/2017
Fix issues with Big Cluster, it was not being properly handled. Keep an eye on Core_CTL it might affect the way the big.LITLE arch works.
Updated F2FS to latest 3.18.y branch from HERE
Updated F2FS encrypt system to a per File encrypt system
Updated the way the scripts determine user setup to properly patch for Wifi Fix on AOSP based ROMS.
Added the option to patch the fstab.qcom file with F2FS support on System partition, Data and Cache was already there. THIS IS ONLY FOR LOS based ROMS, i didn't add the patch for fstab.qcom for STOCK. I'll look into this within this week.
Enabled NTFS FS
Updated Wifi Driver
AX7-Hybrid R13 - 04/09/2017
Fix Core_CTL. It was not working properly in R12
AX7-Hybrid R12 - 04/09/2017
Fixed WiFi for AOSP ROMS. It will execute a script based on the setup of the user. Depending on Stock or AOSP
Enabled Core_CTL Helpers and hotplug wrappers.
AX7-Hybrid R11 - 04/09/2017
Fixed several Memory Leak sources
Increased screen off sampling for Interactive Governor, should fix some Bluetooth hiccups when playing music either locally or streamed.
UPSTREAM ANDROID - SDCARDFS
Added more wake-locks to be disabled and make the disable process more strict, it's user responsibility any issues due to disabled wake-locks.
Read through the commits in github
AX7-Hybrid Basic R1 - 03/25/2017
AX7-Hybrid Basic is up... Only added Kcal, SafetyNet Patch, Quickwake, CPU and GPU OC
AX7-Hybrid R10 - 03/24/2017
AX7-Hybrid R10 is up... AKA the one Kernel to rule them all!. Please Red Post 2 with info regarding Wifi on LOS based ROMS...
AX7Kernel R7 - 03/16/2017
For both STOCK and LOS Based versions. Upstream Linux Kernel to 3.18.45 thanks to jcadduono patches.
AX7Kernel R6 - 03/03/2017
Cap for battery charging set back to 100% by deffault. BLX Settings, you want to change them, refer to this POST and to this POST. If you want to extend your battery's life think about adding the cap to a 95 or 97%
Fixed the issue where the phone won't go into deep sleep at all.
WQ_POWER_EFFICIENT MODE is enabled by default now.
AX7Kernel R5 - 03/01/2017
Cap for battery charging set to 97% by deffault. BLX Settings, you want to change them, refer to this POST and to this POST. Your battery won't charge beyond 97%.
Added options to manipulate thermal settings, now you can choose when the phone will throtle the CPU or when to start shutting down cores to prevent damage. My recommendation don't push it too high or your phone might get damaged due to the high temps. It's not set to 60 Celcius so i recommend lowering that to avoid damage.
Added WQ_POWER_EFFICIENT MODE ( you'll need EX Kernel manager to get this, it's paid app but it's totally worth it guys)
Enabled the option to 'disable' some wakelocks. Disable them on your own risk. Wakelocks that can be disabled are: Bluedroid, wlan_rx, wlan_ctrl, wlan, IPA_WS, wlan_extscan_wl_ws, qcom_rx_wakelock_ws - You'll also need EX Kernel manager to get this options.
AX7Kernel R4 - 02/24/2017
Renamed both the Folder and Kernel zip file to appoint to the version. Now we'll have 2 versions, LOS and Stock AX7Kernel, make sure to check the zip name correctly to avoid issues when cross flashing kernels. All LOS/RR/AOKP and other LOS Based kernels will have the word LOS in it.
Fixed BLX feature. It should now properly stop the charging process when the battery has reached the cap_level set by users. Charge will resume once the charge drops from the cap assigned.
AX7Kernel R3 - 02/21/2017
Added one more step of OC (pushed just a little bit further)
Added my own and really simple implementation of BLX (battery life extender) based on the work made by bedalus for the OP3 and OP3T
AX7Kernel R2.3 - 02/17/2017
Updated to latest LOS Stock Kernel
Disabled some debugging
fixes to ZEN ioScheduler - highly recommended now.
Disabled color inversion in Kcal - can't be used anyways.
Fixed USB Fast Charge - Should worl properly now.
GPU OverClock - 684MHZ max frequency now.
Adreno Boost added and enabled (should boost GPU a bit)
Updates to interactive governor (should work better when operation are in the background and screen is off - music streaming is an example.
Changes to the Sync
Changes to Random function for IO ops.
Updates to Zram.
AX7Kernel R1 - 02/13/2017:
Updated to latest LOS Stock Kernel
Added a few governors like: lionfish / despair / darkness / blu_active / wheatley / ironactive and bioshock
added a few IO Schedulers: Tripndroid / Zen / SioPlus / VR
Kcal Color Control driver
USB Fast Charge
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock
Motorola Quickwake
Extended battery charge time from 30s to 100s

Nice! Flashing now and testing and will report back.
Edit : Trying to flash the kernel on the latest 14.1 Official nightly, but I get an error 1 in TWRP. Any suggestions? Thank you.

jimbo77 said:
... {snip} ......my first custom kernel for the ZTE Axon 7 ......{snip} .... [/QUOTE]
Really great to see further & ongoing development fot this great hardware. Your wide range of options leads inevitably to the question: Based upon your testing and build, what selection have you found the best for SOT & performance? (knowing ones's mileage will always vary based upon specific, etc)
Thanks!
Click to expand...
Click to collapse

TheLastSidekick said:
Nice! Flashing now and testing and will report back.
Edit : Trying to flash the kernel on the latest 14.1 Official nightly, but I get an error 1 in TWRP. Any suggestions? Thank you.
Click to expand...
Click to collapse
Don't know what the issue is. Are you running the latest TWRP?
I justo downloaded the file and it flashed well into my device

kcal, more governors and overclock?
kickass

amphi66 said:
Really great to see further & ongoing development fot this great hardware. Your wide range of options leads inevitably to the question: Based upon your testing and build, what selection have you found the best for SOT & performance? (knowing ones's mileage will always vary based upon specific, etc)
Thanks!
Click to expand...
Click to collapse
As you said it will depend on each user and the usage of the phone. I personally use ironactive / tripndroid / overclock / cpu touch boost / enabled dynamic file sync.
Test it and let me know

jimbo77 said:
Don't know what the issue is. Are you running the latest TWRP?
I justo downloaded the file and it flashed well into my device
Click to expand...
Click to collapse
Thanks, sorry. Not sure either. Flashed latest by jdac 3.0.3.4 I believe?? Now it says N after you said that I checked recovery once more. Reporting back soon.

jimbo77 said:
As you said it will depend on each user and the usage of the phone. I personally use ironactive / tripndroid / overclock / cpu touch boost / enabled dynamic file sync.
Test it and let me know
Click to expand...
Click to collapse
Just adjusted color a bit and oc'ed. So far it's pretty sweet. Going to try out your settings right now.
---------- Post added at 11:30 PM ---------- Previous post was at 11:21 PM ----------
Got everything but touch boost... Is that input boost? If so what freq did you use.

Is the video recording bug gone with this kernel? Would love to try but need video recording for work.

EasyTiger6x13 said:
Is the video recording bug gone with this kernel? Would love to try but need video recording for work.
Click to expand...
Click to collapse
I've been able to record a couple of videos and have no issues at all

What tuning app are you using? Kernel aduitor?

RUNNERX said:
What tuning app are you using? Kernel aduitor?
Click to expand...
Click to collapse
Yes.
Side note, my recovery problem was fixed. Make sure you're all on the latest recovery, mine got replaced somehow.

Anyone got any tips or settings for screen calibration they care to share?

Do I need to have root to install?

SafetyNet Patch isn't working for me on A2017g LOS 14.1 official. CTS Profile Match : false

jimbo77 said:
Don't know what the issue is. Are you running the latest TWRP?
I justo downloaded the file and it flashed well into my device
Click to expand...
Click to collapse
Same problem here error1.
Is this compatible with A2017G?
Running the 3.0.n1-1 Twrp.
Official LOS 14.1 13/2 nightly.

zguy30 said:
Do I need to have root to install?
Click to expand...
Click to collapse
No you don't need to have root.
tron1 said:
SafetyNet Patch isn't working for me on A2017g LOS 14.1 official. CTS Profile Match : false
Click to expand...
Click to collapse
This is an issue with a su add on found in those roms. Flash this file:
https://drive.google.com/file/d/0BzZ9GYzoA6tMd1NVTXROSGZ3RTg/view?usp=drivesdk
Then flash the kernel again. Then SafetyNet will pass, if you want to have root then flash supersu 2.79 and use root switch to disable root whenever you need to use anything that checks SafetyNet.
This are my results with above steps...

machetie said:
Same problem here error1.
Is this compatible with A2017G?
Running the 3.0.n1-1 Twrp.
Official LOS 14.1 13/2 nightly.
Click to expand...
Click to collapse
Make sure you have the latest recovery

Development [Kernel][11.06.2023][Android 13] Kirisakura 3.0.2_T for Asus Zenfone 8 aka "Sake"

Kirisakura-Kernel for the Asus Zenfone 8
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 8 aka Sake. The Zenfone line-up internal codenames are traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila".
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!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
If that got your curious, I welcome you to continue reading if you´re still interested!
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.
A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. In this years generation ( 5.4 linux kernel base/ SD 888 ) CFI and SCS are enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
I put the explanations and links in hide tags here.
Spoiler: Documentation Control-Flow-Integrity (CFI) / Shadow Call Stacj (SCS)
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.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.
Another security feature is Shadow Call Stack (SCS).
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above 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.
Read more about the Release-Model following this link.
This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
Starting with the Initial Message , the following reply and a good summarizing statement.
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 888 that´s built into the different SKUs of the Zenfone 8.
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 the other features 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.
A 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 Asus for Android 13 and intended to be used on the latest Asus Stock-Firmware
- compiled with Clang 14.0.7 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 5.4.231
- upstreamed CAF base for the Snapdragon 888 (qcoms internal codename "lahaina")
- include important fixes/improvements from kernel/common
- tune scheduler for improved jitter and less jank frames
- reduce power consumption during deep sleep
- remove logging while device is suspended
- remove sleep debugging from Asus for release build
- disable various debugging mechanisms for drivers which are not needed on a perf build (for example touchscreen, fingerprint reader, display, binder)
- disable various debugging configs, that are not needed in a perf kernel build according to google.
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- display tweaks to reduce power consumption on statically rendered images
- disable unnecessary CPU errata for our specific SoC
- disable per cgroup pressure tracking to reduce overhead
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- free up RAM by removing reserved mem regions used only for debugging
- implement LRNG (thanks @arter97, see arter kernel OP for more info )
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
- EAS implementation patched up to latest CAF state
- updates from kernel/common
- scheduler updates from sd888/ 5.4 kernel
- scheduler update from sony xperia 1 III kernel aiming to improve WALT
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
- improvements to cpufreq/times/stats
- vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.4 default, keep for documentation)
- remove event debug logging
- disable broken irq detection, disable debugmon
- improve suspend/resume from audio driver (caf-upstream for audio-kernel)
- cpuidle: wake only cpus for which qos has changed (this allows cores to keep idle states better)
- disable debugging during sleep states as per qcom recommendation
- remove RTB logging to reduce overhead
- disable trace_printk as it shouldn´t be used on production/perf kernel builds
- enable suspend_skip_sync to save power during suspend/resume
- disable edac and coresight (following google on the pixel kernels)
- disable jtagv8 debugging as recommended by qcom for perf builds to avoid potential power, performance and memory penalty
- disable s2idle in favor of deep idle state -> improves deep sleep drain (google initially used 2idle for improved suspend/resume latency on pixel 3 and pixel 4, but disabled it on pixel 5. qcom followed suit for sd 888, but apparently didn´t see google reverting it on pixel 5. Other OEMs such as Xiaomi or OnePlus already disabled s2idle on their SD888 devices in favor of deep- read more about s2idle vs deep here)
GPU related features:
- GPU driver updated to latest CAF-State
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
- add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU
File System related features:
- upstream BFQ-MQ to latest state in linux-mainline and default to 128KB readahead
- improve memory allocations in kernfs
- ufs improvements from pixel 4/ pixel 5 kernel
- improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 8 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- includes new bbr
- improved networking drivers from caf-upstream (especially wifi)
- remove unnecessary wakelock from WLAN driver to reduce thousands of very short wakeups during a 7 hour deep sleep period
- improved bluetooth performance (¹, ²)
- Enable support for TTL spoofing
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- patches from kernel/common
- improve memory allocations in various subsystems, video encode/decode, kernfs, cgroup
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
- Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
- free more RAM by removing unused reserved memory regions
- mm: Micro-optimize PID map reads for arm64 (improves game performance, especially unity based games such as genshin impact)
- MGLRU added (info here and here
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
- Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
- enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)
Misc Features:
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:
- clean up asus drivers and fix a few warnings in kernel log
- 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
- enlarge dmesg size to ease debugging
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img, vendor_boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware)
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 8 receives an OTA update it takes Asus 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.
Always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=326387
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 11
1.0.0 Initial Release
1.0.3 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85230887
1.1.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85369421
1.3.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85471991
1.4.7 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85580815
1.5.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85708459
1.7.5 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
1.7.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
1.7.9 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86004361
Android 12
1.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86200913
1.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86219239
1.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86221081
1.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86546997
2.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86856077
2.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87005047
2.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87053951
2.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87244107
2.0.10 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87432111
2.0.12 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87641841
2.0.15 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87944971
Android 13
3.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88195025
3.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88326835
3.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88632657
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Asus for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@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 and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_SAKE_Zenfone_8

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, vendor_boot.img as well as dtbo.img from matching firmware you are on and flash them via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , 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 .zip of /asdf.
Easiest way is immediately after booting up, with a root explorer navigate to /asdf. 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!

and this is mine too

justincase

last one I promise

Woah another kernel for sake ! Might give it a try later !

Update to 1.0.3
Hey guys and girls,
I hope everyone is having a good day or starting into one. Here´s the next update.
The kernel is updated for the latest firmware:
30.11.51.67. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.
The link to the firmware can be found here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.4-30.11.51.67 source code
- Linux-Stable Upstream to 5.4.128
- bump clang to latest prebuilt clang by google (12.0.7)
Download:
https://www.androidfilehost.com/?fid=14943124697586354960
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07

Freak07 said:
Update to 1.0.3
Hey guys and girls,
I hope everyone is having a good day or starting into one. Here´s the next update.
The kernel is updated for the latest firmware:
30.11.51.67. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.
The link to the firmware can be found here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.4-30.11.51.67 source code
- Linux-Stable Upstream to 5.4.128
- bump clang to latest prebuilt clang by google (12.0.7)
Download:
https://www.androidfilehost.com/?fid=14943124697586354960
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Click to expand...
Click to collapse
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?

a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Soory, wrong post

a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.

Freak07 said:
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.
Click to expand...
Click to collapse
Thank you. Today I will also try to flash the vendor_boot.img

no updates?

I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!

elchmartin said:
I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!
Click to expand...
Click to collapse
unfortunately no. 8 flip uses a separate kernel.

Hi @Freak07 ,
Thanks a lot for your effort and time that you invested into developing this kernel.
However, as is the case with other custom kernels, I would like to know what kind of battery life benefits I can expect from using this kernel on my device?
Unlocking the bootloader on Asus phones right now means a bit more hassle with the updates, also rooting the phone means a bit more hassle with using some apps (safety net etc),so I would really like to know what are the benefits in terms of battery life.

Update to 1.1.8
Hey guys and girls,
I hope everyone is having a good day or starting into one. Here´s the next update.
The kernel is updated for the latest firmware:
30.11.51.83. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.
The link to the firmware can be found here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07

Freak07 said:
Update to 1.1.8
Hey guys and girls,
I hope everyone is having a good day or starting into one. Here´s the next update.
The kernel is updated for the latest firmware:
30.11.51.83. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.
The link to the firmware can be found here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Click to expand...
Click to collapse
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?

a7lanov said:
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?
Click to expand...
Click to collapse
That´s expected behaviour on the few last gens of QCOM SoCs. and you´re also fooled by the ui of the app.
if there are no tasks/work the clusters go into idle c-states, but kernel managers/monitors will show you the frequency that you described.
depeding which battery mode you chose in settings, minfreqs for the clusters will be higher or lower.
dynamic should be at 300mhz for little cluster, 710mhz for big cores and and 844mhz for the prime core.

Freak07
Thanks for clarifying

Freak07 said:
Update to 1.1.8
Click to expand...
Click to collapse
Thanks man!
Could you please let us know if defconfig is stable or it's better to configure something (like cpu/gpu freq's) on the device ?
Does it support both 8GB and 16GB RAM devices?

Database Develop

welcome