[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
************

This mod' has been updated to support AOSP only if you are running freeza's latest BEAST MODE KERNEL which contains a folder named "gnfre3" in the /system/etc directory. The methods of installation are the same. The file you are replacing for AOSP (after flashing his kernel) is /system/etc/gnfre3/war_mods.sh

So, see below for instructions. And any commands applicable to file paths for the /system/etc/init.qcom.post_boot.sh file, just change to the AOSP-specific ones above.

Make sure you download the correct variant... for both AOSP and stock ROMs, you'll have a 4 GB and 6 GB option

***************

Well, this device is a breath of fresh air? Wouldn't you guys say? 128 GB ROM, 6 GB RAM and a monster of a processor!

That being said, custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.

Here is what is required of you before you begin:

1. Must be rooted

2. Must have the ZTE Axon 7 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.

3. Must have write protection disabled.

Using adb shell:

adb reboot disemmcwp

Using Linux terminal (from your phone, for example):

reboot disemmcwp

The above command can also be executed in recovery terminal.

IT IS IMPORTANT THAT YOU USE THE CORRECT VERSION (RAM), AS THIS COULD HAVE UNDESIRABLE PERFORMANCE IMPACTS OTHERWISE... however, nothing will be permanently damaged, this won't turn your device into a paperweight.

Let's begin.

Getting right to it, here's what I've done:

- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)

- reconfigured input_boost parameters - disabled

- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio and dirty_background_ratios, set swappiness value to 100, and other parameters of the virtual machine have also been adjusted, such as vfs_cache_pressure.)

- (Above) you will have as much available RAM as possible for your apps. This will reduce redraws if you are a heavy user. If you'd like to test this, reboot, and check your available RAM in the settings :eek:

- Enabled zRAM for all variants

- remapped minfree parameters for LMK (low memory killer) for 6 GB variants only

- Set scheduler to CFQ

- Tuned CFQ scheduler for flash storage devices

- Turned off core_ctl for BEAST MODE kernel.. you can enable this if you'd like, just know what you are doing. There are commented out lines of code near the bottom of my scripts to enable or disable it.

- Added an option to change GPU governor to simple_ondemand (again there is a commented out line at the bottom of each script, just remove the "#" symbol and blank spot right before the line. simple_ondemand is more power-friendly GPU governor, with a very small hit on performance

In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.

How to install????

There are two main folders found in the unzipped package. One for the 4 GB variant, one for the 6 GB variant. Only use files from the appropriate folders for your device. Each of those two folders has 3 sub-folders: ondemand, conservative, interactive… this is where you will find the various init.qcom.post_boot.sh files

Note: magisk users, see this post https://xdaforums.com/showpost.php?p=72144888&postcount=286

Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.

All you have to do is download the zip file to your device, open up a file explorer (must have root capability) unzip the package, grab the file you want to use, navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.

After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!

Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:

Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).

su

cd /

mount -o remount,rw /system

cd /system/etc

rm init.qcom.post_boot.sh

cd /sdcard

mv init.qcom.post_boot.sh /system/etc

chmod 0644 /system/etc/init.qcom.post_boot.sh

I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:

That's pretty much it, guys. Enjoy!

Links below

STOCK

6 GB

4 GB

AOSP (Using Latest Beast Mode Kernel with the /System/etc/gnfre3 folder present)

6 GB

4 GB