yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Updated******

Adjusted swappiness again (set to 1 now for both variants)

Adjusted dirty and dirty background ratios

Adjusted the dirty writeback and expire parameters

Made fiops the default IO scheduler

I would recommend using a kernel that supports fiops. If you don't, the default settings of cfq will be implemented, and make sure you guys are making system backups.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Thanks, downloading now, although I'm on stock kernel for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Update:

So far so good, speed is nice, smoothness is nice, even benchmarks are nice.

Good job man.

I have one question out of curiosity though.

Why is the original file that we replace larger in file size than the mod?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Taken from the 4GB variant file:

Not cool.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheLastSidekick:
I thought we were keeping this a running joke between all the people who actually took the time to read. Why you do this? We all know it's a joke man.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Not a funny one.

Cancer is funny?

ok
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheLastSidekick:
I've had 4 uncles die from it. I'm not gonna sit around and cry about it, I'd rather laugh about it now. Of course it's not funny in the limelight, but we are human we say and do things and handle things the best we can. Who are you to judge exactly?

The guy puts some good work out there, and that's what we are looking at. Not a comment in some code in some file. If it bothers you this much, don't use the dude's work lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I actually did read that, I was like what the f***..?

But I laughed it off and used the file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Don't be so touchy guys, lol. I've known people that have died from cancer. I have firsthand rights to joke about it.

Carry on
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jedi.Tester:
Could you make a small writeup on how to implement this on LOS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MiMtnBiker:
[MENTION=7372544]warBeard_actual[/MENTION]

I am curious to know what the reason was as to why you specifically chose fiops as the scheduler? When I use a custom kernel with the ability to chose a different scheduler, will it supersede fiops, or vice versa? The reason I ask is because I like to 'mess' around with the different options to see what works best. Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
I pretty much flashed the kernel, ran the root remover from the OP, then flashed magisk.

After that I put the file in the init.d folder, took the .sh out of the name, and changed the permissions to 755.

The kernel I use didn't support init.d so I use kernel adiutor to emulate it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ephexxis:
i thought it was hilarious.

comedy is about confronting the darkness in our lives and associating it with something other than suffering. those who choose to let it bother them are free to do so but like, why
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ro_bro:
Does this mod fix the crazy Whatsapp and LinkedIn app lags in stock 7.1.1? If so, I might consider going back to stock from LOS. I can't stand the sound and the camera on LOS right now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ThePublisher:
Trying to use this on Ressurection Remix with AX7Kernel. I run into an issue when I try to paste this tweak file into system/etc/init.d/. I am unable to change properties to allow writing to the folder so the operation fails. I'm using rom toolbox root browser. Thank you in advance for any help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
You might have to disable write protection. I think the command is "reboot disemmcwp" in a terminal
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Performance data between fiops and cfq indicated fiops performs better.

However, I've been considering going back to cfq because the tests performed were done with an unmodified cfq (stock settings) scheduler. I haven't had time to look into it again but we might be reverting back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
Just responding to your post in the 7.1.1 OTA thread and claiming my spot in line as a willing guinea pig for whatever kind of vodoo magic you're cookin' up!

...Though I might need to get the update first. Sort of stuck on B15 (update says there's no update)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
I'd recommend being updated, but it won't destroy your device. lol.

I'm updating the OP right now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Updated - new version for 7.1.1 is up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
So far so good on stock B19. Thanks again for sharing this. I can't imagine running stock without it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Hello been using your mod few several weeks on stock B29 and loving it. I finally went to B19 using DrakenFX method. Using terminal emulator I did the su reboot disemmcwp on my phone but am still unable to remove and replace the files. I did not have any issues before. In fact I didn't even have to do the disemmcwp part. Any ideas? Thanks in advance.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] otaconremo:
I also got this problem when updating to 7.1.1 and I believe it's the systemless mode of SU that's causing this. But I managed to solve it by copying the file in twrp file manager. I saved the modded file from OP to my sdcard. Then mount the system partition in twrp, made a backup of my original init.qcom.post_boot.sh by copying it to a folder in my sdcard then copy the modded file to system/etc folder. last, browse again to system/etc and tap on the file and chmod to 0644. then reboot.

everything's working for me nicely.

Thank you OP for this wonderful update.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
I was able to get the file in the folder but am still unable to change it to 0644 :(. Hopefully my phone will be ok.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Hmmm .. .. .. absolutely no issue here. Renamed from the long download .txt filename, renamed original file with an -orig suffix, copied/pasted new file with Root Explorer, changed permissions and rebooted. Using Freeza's Enforcing kernel.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Looks like I have a new file manager to learn. My old standby let me down. Thanks for the help everyone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Sorry for all the posts. Just to be sure we're supposed to get a 1 in terminal now?

I'm 6gb axon 7, B19 7.1.1, Freeza BM vR29 Enforcing Kernal just installed.

I'm getting a zero.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
You should be returning a 1 for swappiness.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Reading the OP, are you recommending using [MENTION=309990]freeza[/MENTION] 's BeastMode Kernel as downloaded with this mod, or do you tweak it via KernelAdiutor or other also?

Thx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
I would recommend his kernel, yes. Not sure if he's got R30 up yet, but it is the build with the updated B19 source. I've been using it since he sent it to me earlier today. Everything working as it should (of course).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Yes, R30 is up and running well. The question was: do you recommend using his Kernel as is and allowing your mod to make ALL of the tweaks, or using Kernel Adiutor to OC and/or make other changes first andTHEN apply your mod? Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
I would just use his kernel, maybe kernel auditor to play with the screen a bit, and that's it. My shell file is pretty solid for everyday use. Not sure what else you would need to do.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ro_bro:
I'm running beastmode kernel R31, with this mod. It's buttery smooth! On stock 7.1.1 btw. Thanks [MENTION=7372544]warBeard_actual[/MENTION]!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Would anybody here be interested in running another test version of this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Certainly!

Device: A2017U 4GB 7.1.1 (although baseband is 090, rooted Stock (but with a bunch of stuff frozen), Freeza's Kernel, your 3/16 script, APEX Launcher
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
I'm down!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
For sure! Loving Battery Life.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Ok, I'll upload the files for you guys tomorrow
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Hey guys, sorry for the small delay, [MENTION=309990]freeza[/MENTION] and myself have been trying to test out our **** as much as possible. I'm currently running his version 34 kernel with the following files and getting amazing results, better than before. I've created my own benchmarking tests to validate results. As promised, here are the current "preliminary" shell files.

4 GB VARIANT

6 GB VARIANT

I'm very pleased with the results of this version. Most likely will be final. [MENTION=309990]freeza[/MENTION] thanks for the awesome work on your end as well. We make a good team brother!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Nik2424:
Would this work just as well on R31? Any chance you could you share the R34 for testing? :)

Thanks for these your time tuning this mess of variables my man.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
Yes, it'll work on R31 or even stock kernel.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Your 4GB trial has been working great on BeastMode r31 (enforcing). Any word on the improved r34?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Preliminary update****

Hey everyone, so [MENTION=309990]freeza[/MENTION] has a new version of his kernel available to a few of us who are working on this device together. I went ahead and updated my script to compliment the new feature he tossed in called core_ctl, which is a task loading module.

It is extremely efficient and, even better, highly tunable. I've added some lines in my post_boot file to tune that module up.

The efficiency seen in managing power usage of the two cpu clusters has been unreal :eek: expect massive improvements in battery life.

Here they are, you can download them now, but install them after you get your hands on his version 38. Links below:

4GB VERSION

6GB VERSION
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] VeNuMuS:
Dudebro straight teasing. Nice work
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] QAM:
Hola

Hey [MENTION=7372544]warBeard_actual[/MENTION] or anyone knowledgeable enough. If I want to you use your tweaks, should I use the version you mention in the OP or use the latest release. I ask because you mention that for the latest release, you recommend / suggest using freeza's kernel. I am currently on RR 7.1.1. For now I prefer to not use a non-stock kernel.

Thanks for your valued contribution.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Well, as preliminary updates go, they are just preliminary. I've since changed a few things to achieve a little bit better responsiveness.

Probably going to release the official version sometime this week and at the time [MENTION=309990]freeza[/MENTION] releases his kernel.

You can use either. If you experience lag on the preliminary version, find the one in the OP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KennyKusanagi:
I'm trying to disable write protection in terminal but its saying "permission denied". Anyway I could grant the permission?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Did you type su before the command?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
I was able to follow all the instructions to get this kernel tweak running on latest RR with AX7Hybrid kernel. In my root explorer I had to place file in init.d folder in system/etc and remove sh extension and set permissions @ 0644. In KA, I ran the script and set init.d @ boot and I was finally able to get back 1 for swappiness. From here, how long do I let settle or can anything else be tweaked? The phone does seem snappier right away. Thanks for the hard work OP!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KennyKusanagi:
Nope, I did not. let me try that

---------- Post added at 03:36 PM ---------- Previous post was at 03:27 PM ----------

Says "it's not found". So I guess it's not enabled
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
You don't have root do you?

su enables the terminal to do root stuff. so if you haven't got SuperSU or whatever on your phone you won't be able to run su

---------- Post added at 10:22 PM ---------- Previous post was at 10:07 PM ----------

I got this far lol. tried to mount the damn system and it won't even let me, resource is busy error. I even tried to use busybox mount and it seemed to do something, but when i tried to remove the original file it told me that the system was read-only. I'll try removing write protection though I'm not sure if it ever worked

edit: no, disabling write protection didn't do the trick
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KennyKusanagi:
I do have root & my BL unlocked. It's not letting me change permissions or anything. I need help :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Yeah, try su, if you're not rooted you'll need to root your device mate.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Okay it's probably because you denied it root access when you typed su in. just delete the terminal app's data or uninstall it and install a more common one

---------- Post added at 10:28 PM ---------- Previous post was at 10:27 PM ----------

Why did you quote me though?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Missclick, hehe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Those of you having issues installing this... Just manually remove the file in recovery and copy the new one to the directory, set permissions 0755

Edit* also, [MENTION=309990]freeza[/MENTION] and I are updating today
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
did you ever remove system write protection? type reboot disemmcwp from terminal emulator
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KennyKusanagi:
I got it installed. Noticed the difference right away. Thanks everyone
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Sorry what file explorer do you reccomend for changing perm? I've tried 3 already including ES and none of them let me change thenpermissions, though they did let me delete and put the file
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
@warBeard_actual

Is this still working with the stock kernel too?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
I have it in the init.d folder with the .sh extension removed, permissions set to 0644 and I still get swappiness return of 1 in KA and Terminal. Did I do the setup correctly?

---------- Post added at 09:55 PM ---------- Previous post was at 09:51 PM ----------

Forgot to mention, I'm on 4/10 RR with AX7Kernel
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
flashable zip, anyone?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Once upon a time ago I had flashable zips for this modification, I'll look into this as an option again. I usually prefer doing things manually, however. But I understand that isn't everyone's cup of tea.

Seems you had successful results, yes. :good:

Yes, you can still use this with the stock kernel with no issues.

I prefer root explorer myself.

Just a heads up, updated on its way up right now. This will likely be the final release (for reals this time) and will compliment [MENTION=309990]freeza[/MENTION] latest kernel nicely. I also found a pretty critical typo in my last preliminary update that i fixed in this coming version.

Quick change log for 4/11:

- modified frequency stepping (above_hispeed_delay) quite a bit. This was needed to get the performance and battery duo out of the kernel and script combined.

- modified dirty cache ratios and "expired" dirty page writes.

- Turned on zRAM for the 4 GB variant.

- Modified the parameters of the core_ctl module. Also, it is enabled now if you are using freeza's kernel.

- Adjusted the touch_input_boost parameters to something a little more battery friendly.

- Turned on io_is_busy for interactive governor

Other things, but those are the major ones.

Update coming, check OP in a minute here.

*EDIT*** updated!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bluestudy:
Tried earlier instructions for RR and return 0 for swappiness. Not sure what I'm doing wrong. Set permissions to 644 instead of 755.

---------- Post added at 06:45 AM ---------- Previous post was at 06:31 AM ----------

Tried earlier instructions for RR and return 0 for swappiness. Not sure what I'm doing wrong. Set permissions to 644 instead of 755.

Edit: Got it. But I can't seem to figure out how to set it to apply at boot in Kernel Aduitor. Have to run the script again on every reboot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
Turn on init d emulator
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
I can usually figure these things out, and admittedly I have not tried yet, but if someone could make a nice set of instructions for custom rom use that would be great.

I have read everything in this thread multiple times and am still a bit confused on what to do. If nobody chimes in I will figure it out an post up a list.

currently on candy rom with ax7 kernel.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
Ok, I replaced yesterday's file with the most current and I took a look at the parameters. Should Z-Ram be set to 0mb and should Dynamic Fsync be on or off? I'm getting a swappiness return of 1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Will this work on stock MM 6.0.1?

7.1.1 messed my phone up big time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Small test coming here. I wanted to have a few of you try this out and let me know if you are experiencing any lag in your UI. Make sure you are on Freeza's latest kernel.

Links below:

4 GB

6 GB

Please give both of these a test run, for about 2 days and let me know if you experience any unusually negative performance side-effects. For me, this would turn up after the phone was idled for an extended period of time... unlock the phone, stuttering UI... it was very noticeable and obnoxious. Only way to get rid of it would be a reboot.

Feedback appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
If you have the 6 GB variant, zRAM is disabled. If you're on the 4 GB variant, I left zRAM enabled.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Borias:
I've got a first impression on this.

After half a day of testing on A2017G running B19 with freeza's vr40 permissive on ext4 the mentioned side effects are present, also there is some annoying keyboard lag with Gboard now.

Will keep running it and report back again after 2 full days of testing.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
See this post here... try these ones. This is what I am currently using.

https://xdaforums.com/showpost.php?p=71836261&postcount=423

Let me know what you observe
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
[MENTION=5903312]Borias[/MENTION] ... another update below, please install this and report back since you confirmed the issue.

6 GB Test

4 GB Test
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Borias:
Alright, will try that one. I'm on 4 GB of RAM I forgot to mention.

Are there any logs/numbers/scores I could grab that would help you? Or is reporting on my subjective experience all it takes to make you happy? :D

EDIT: Just saw your new post, will switch to that version then. Maybe naming them by version numbers would help keeping an overview though xD

(Like Experimental v1/ Test 1 or something)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
well, naming them by version won't do much to help since I can't name the file. We'll just keep this unofficial for now.

Give me your feedback, I'll make adjustments. I'm pretty sure we figured out what was going on.

Basically, the core_ctl module has some parameters such as setting down and up thresholds, and also values to set a minimum number of cores on for each cluster, and then a parameter to identify which one is the "large" cluster.

I believe what was happening is the values I was setting were being overridden by the kernel. [MENTION=309990]freeza[/MENTION] wasn't experiencing this lag in his UI (he had tuned this slightly himself) because he was only setting values for the smaller cores for busy_up and busy_down thresholds... so, basically, his larger cores weren't flipping on and off - only his smaller ones.

Since the larger cores do most of the heavy lifting, this is is where the difference was coming from.

This version I posted above, turns core_ctl on, but doesn't set any values for any of the core_ctl parameters other than designating cores 2 and 3 as the "big" cores.

Performance should improve drastically, and you should get more "accurately" placed tasking.

This should zero in on the issue quite dramatically. As I told [MENTION=309990]freeza[/MENTION] I didn't start seeing any problems until he introduced core_ctl and I started messing with it through sysfs. It is rather finicky, probably due to many other conflicting variables.

I'll get this sorted out, don't worry. Just need feedback, trial and error, as timer governors require this type of "real implemenation" testing. I had to completely take a different approach to the script today, as adding the core_ctl changes the way the cpu functions entirely.

Be patient, I'll figure this out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
Likely will have something for you guys tomorrow. Just checking in.

I apologize for the seeming chaos. The new settings implemented by freeza are indeed legitimate and a step in the right direction as far as power savings go, the script just really wasn't designed for some of the extreme changes he made. Without getting too technical, the short answer is that everything combined was just "too conservative".

I had him build me a version (by request, thanks bro) to address some of the conflicting operational parameters of core_ctl with my script and I redesigned my script to be tailored around his kernel.

Hopefully tomorrow I'll have some answers but I think we've got it. I'll know more in the morning.

Tomorrow, guys! I'll check in here and let you know where we're headed.

Thanks again for the feedback. Users are absolutely crucial to fix issues sometimes. Thanks again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
First, device is running great. Second, I think we might have a winner here.

(Images attached)

[MENTION=237822]FreeZe[/MENTION]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] VeNuMuS:
Confirmed. Script running like a champ with freeza's test kernel. I'd say coupled together, we got a hell of a ccccccombo breaker.. Good work bro