Which magisk module is it?can you maintain this mod for new oos releases? with a new thread in themes and mods section
Which magisk module is it?can you maintain this mod for new oos releases? with a new thread in themes and mods section
You bringing Neuron to OP9P?So on my own kernel I have almost all coresight features disabled and everything works just fine. Never understood why anyone should include it since it's just messing with the scheduler and other things. Also that's the only thing I don't like at oneplus.
I don't have "persis.sys.opperf.enable" in my build.prop and I can't add it. What can I do?for those that also want to disable OPPerf again.
Based on the findings of @xls654 (digging in the oneplus-services.jar) and the idea of @LuK1337 to disable access to the tpd files of the kernel module, I created a new magisk module, after I found a build.prop variable in the code to disable OPPerf.
The module chmods the system writeable files of the tpd kernel module:
Code:chmod 000 /sys/module/tpd/parameters/tpd_cmds chmod 000 /sys/module/tpd/parameters/tpd_dynamic chmod 000 /sys/module/tpd/parameters/tpd_enable chmod 000 /sys/module/tpd/parameters/tpd_id
and sets a build.prop variable to disable OPPerf:
Code:persist.sys.opperf.enable=false
Be informed that this module doesn't modify any system files so its universal and working on upcoming OOS versions. If you disable or uninstall the module and reboot all is reverted.
If you don't want to use a magisk module you can also set and revert the build.prop variable via terminal, but it is only read once on boot, when the OPPerf service starts, so you need to reboot after setting or removing the variable.
disable OPPerf:
Code:su -c "setprop persist.sys.opperf.enable false"
revert:
Code:su -c "resetprop -p --delete persist.sys.opperf.enable"
Same here dude, it breaks the power button after the latest OOS update. You can't lock the screen anymore because it goes straight into the power menuI think I remember seeing the OOS hack on another thread, but no one said what it does?
Well, either it, or a combination of it and something else borks my power button.
YMMV
Only for my private use since I don't like stock kernels. It will never become public due to specific reasons.
I'm more than happy to be a 'private' testerOnly for my private use since I don't like stock kernels. It will never become public due to specific reasons.
no
Which is why 1+ implemented the throttle in OOS for apps that don't need full power.
I want to be a private testerOnly for my private use since I don't like stock kernels. It will never become public due to specific reasons.
I would also like to be a private testerOnly for my private use since I don't like stock kernels. It will never become public due to specific reasons.
How did you manage to achieve such numbers?
I really didn't do anything, no module,no tweaks, nothing, except it is on a custom rom(evolution x)
chmod 000 /sys/module/tpd/parameters/tpd_cmds
chmod 000 /sys/module/tpd/parameters/tpd_dynamic
chmod 000 /sys/module/tpd/parameters/tpd_enable
chmod 000 /sys/module/tpd/parameters/tpd_id
persist.sys.opperf.enable=false
su -c "setprop persist.sys.opperf.enable false"
su -c "resetprop -p --delete persist.sys.opperf.enable"
Not sure why would one bother patching services jar when you can just do "chmod 000 /sys/module/tpd/parameters/tpd_*"...No, it's just what I showed in the post, some things have been disabled, but nothing was added that was not originally there, the module is safe.