[09.01][Script]schedtune.boost - making Pixel XL (and eas) even more smoother - Google Pixel XL ROMs, Kernels, Recoveries, & Other

hello guys and girls,
I am quite sure everyone knows and feels that our pixels are already super smooth. However few of us are never completely satisfied and are looking for ways to make the device even more smoother.
Some of you might be aware, that the sched governor, which is bound to eas, isn´t as customizable as the old interactive governor. This is the main reason we don´t have any scripts or tweaks touching the governor.
So I did some digging and finally found a tunable that allows the cpu to be even more aggressive. This will result (at least for me) in a tremendous effect on overall smoothness. Battery life will take only a slight or a grave hit, depending on the boost you choose. @Alcolawl you are free to do benchmarks
The schedtune.boost (s) reside in the directories /dev/stune, dev/stunde/foreground and dev/stune/background
You can apply values from 0 to 100.
When setting it to 100 your device will run constantly with all cores maxed out.
I found values from 2 to 10 to have the most efficient effect.
I am currently using a boost value of 8. Battery life is still awesome. But oh my god how smooth the device runs now.
Remember: you can also set the values higher yourself
For your convenience I made scripts that you can either put in system/etc/init.d or system/su.d. I am planning to refine and maybe add more tweaks to our pixels. So stay tuned and lets all work together. The script does not look like much, but try it before you judge.
Download links will be in the second post.
Instructions:
1. Download the desired file. sched2 means a boost value of 2 will be applied. sched6 means a boost value of 6 will be applied. I think you get the concept.
2. Extract the script from the download
3. Copy the script to either system/etc/init.d or system/su.d
4. set permissions to 0755 (rwxr-xr-x) via terminal or your preferred root explorer.
5. reboot and wait a minute (there is a sleep timer)
6. profit
7. to check if the script got applied correctly do in terminal on your phone
su
cat dev/stune/schedtune.boost
Attention:
su.d only works when you have working root via supersu from chainfire.
Credits:
google for integrating eas to our pixels
@Alcolawl for letting me use his scripts on the HTC 10 and inspiring me greatly in the process. If he did not exist I probably wouldn´t have looked into finding this

Downloads:
init.d and su.d:
https://www.androidfilehost.com/?w=files&flid=140794
01.07.2017
I added an all in one package. The all-in-one package has all scripts with boost values including 2,4,6,8 and 10. So you do not have to start multiple downloads.
09.01.2017
v1:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 15
- schedtune.boost for all other activities (that are not getting categorized) is set to 10
v2:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 12
- schedtune.boost for all other activities (that are not getting categorized) is set to 8

Freak07 said:
Downloads:
init.d:
https://www.androidfilehost.com/?w=files&flid=140135
su.d:
https://www.androidfilehost.com/?w=files&flid=140130
Click to expand...
Click to collapse
Trying to execute it through root browser and get this: http://i.imgur.com/WbUsV6g.png
Put it in su.d directory. Not sure if it is applying on boot.

XtraArrow said:
Trying to execute it through root browser and get this: http://i.imgur.com/WbUsV6g.png
Put it in su.d directory. Not sure if it is applying on boot.
Click to expand...
Click to collapse
What kernel are you on?
Did You run it from sdcard or su.d?
did you set the right permissions?

Freak07 said:
What kernel are you on?
Did You run it from sdcard or su.d?
did you set the right permissions?
Click to expand...
Click to collapse
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.

i like this.
just great!

XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse

XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.
Click to expand...
Click to collapse
kirschdog1 said:
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
Could you please try this file?
Edit: see new link in second post!
Put it in system/etc/init.d
Permissions to rw-r--r-- (644)
Reboot
Navigate to dev/stune/schedtune.boost and see if the value gets changed to the one your script should set.
It seems like the the scripts did not like the laptop at my Patents home
Click to expand...
Click to collapse

kirschdog1 said:
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
make sure there are two lines
for some reason there must be a space below the text. this worked for me.
Click to expand...
Click to collapse

kirschdog1 said:
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
Try it with one of these and copy them to system/etc/init.d please. Permission 644 for the script and reboot.
https://drive.google.com/folderview?id=0BxbxiBXaZVu-d3NOQlFqd3QzMVU

Hello all
I updated the second post. The scripts should work now please report back! Also regarding smoothness.
sorry for any inconvenience.
Have a nice day.

Freak07 said:
kirschdog1 said:
Could you please try this file?
Edit: see new link in second post!
Put it in system/etc/init.d
Permissions to rw-r--r-- (644)
Reboot
Navigate to dev/stune/schedtune.boost and see if the value gets changed to the one your script should set.
It seems like the the scripts did not like the laptop at my Patents home
Click to expand...
Click to collapse
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse

Freak07 said:
Hello all
I updated the second post. The scripts should work now please report back! Also regarding smoothness.
sorry for any inconvenience.
Have a nice day.
Click to expand...
Click to collapse
Same issue unable to change permissions

airmaxx23 said:
Freak07 said:
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse
I have the same structure i found su.d in root but not the other.
Also how would i go about determining if it has taken effect?
Click to expand...
Click to collapse

Jerreth said:
I have the same structure i found su.d in root but not the other.
Also how would i go about determining if it has taken effect?
Click to expand...
Click to collapse
The value in dev/stune/schedtune.boost and /dev/stune/foreground/schedtune.boost should be changed to the value of the script you picked. You can probably change them manually without the script.

airmaxx23 said:
Freak07 said:
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse
Did you Flash Elemental X kernel Prior or after rooting your device. I am not entirely sure but elex should have init.d Support.
can you install the app universal init.d from playstore, open it, scroll down and do the test to determine if init.d is supported or not?
airmaxx23 said:
The value in dev/stune/schedtune.boost and /dev/stune/foreground/schedtune.boost should be changed to the value of the script you picked. You can probably change them manually without the script.
Click to expand...
Click to collapse
yes that is correct. you can Change the values manually but they will not survive a reboot. that is why i made the scripts.
Click to expand...
Click to collapse

kirschdog1 said:
Same issue unable to change permissions
Click to expand...
Click to collapse
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.

Freak07 said:
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.
Click to expand...
Click to collapse
I can change them manually but upon rebooting they reset to 0.

Freak07 said:
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.
Click to expand...
Click to collapse
How do I check?

XtraArrow said:
I can change them manually but upon rebooting they reset to 0.
Click to expand...
Click to collapse
Okay. I was in a hurry. I told you all to set the permissions to 644. You have to set them to 755 (rwxr-xr-x).
kirschdog1 said:
How do I check?
Click to expand...
Click to collapse
check with a root Explorer. it is the easiest way.
or via terminal
cat /dev/stune/schedtune.boost
But first set the permissions of the script to to 755 (rwxr-xr-x). I was in a hurry and did not think correctly
then reboot and wait a Minute.
I edited the instructions in the op and all should be working now. It will not matter if you put it in system/etc/init.d or in system/su.d.
I somehow mixed the permissions with somethings else up. yeah, 755 and all will be well. stupid me.
have a nice evening.

Related

Request: any way to get init.d on Stock rom without using CF Root

Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
frz said:
Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
Click to expand...
Click to collapse
found it
http://forum.xda-developers.com/showthread.php?t=1017291
frz said:
Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
Click to expand...
Click to collapse
thanks for it
frz said:
found it
http://forum.xda-developers.com/showthread.php?t=1017291
Click to expand...
Click to collapse
This won't work for Galaxy Ace, because the scripts in that thread refer to some Motorola scripts that are not present in Ace (/system/bin/mot_boot_mode).
Does someone know of a script that gets executed at boot in a Galaxy Ace stock rom? If so, maybe it could be used in the same way as mot_boot_mode for Motorola Droid, and get an executable /etc/init.d in our stock Galaxy Aces...
Just have a look at the "!Autostarts - Enable init.d on Stock ROMS.sh" script. It is very straightforward.
Juanma.
I would really be interested in this. Anyone? Care to shed some light on this little issue?
Basically you have to add this into the init.rc file (after creating manually the init.d folder of course):
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
Click to expand...
Click to collapse
=> an example of usage; or just google "busybox run-parts"
It is the same method which CF-Root also uses. So you still have the option to study the CF-Root way and will learn some more tricks on the way. ...
^^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android kitchen has that feature
Herpderp Adreno + Tegra.
I found this post here had a possible workaround: http://forum.xda-developers.com/showpost.php?p=20134361&postcount=3
Bakuron said:
I found this post here had a possible workaround: http://forum.xda-developers.com/showpost.php?p=20134361&postcount=3
Click to expand...
Click to collapse
andy572 said:
3. answer is some wrong:
you doesnt need to cook a custom rom, you only need the adb (android debug bridge) to "speak" with your phone:
...
Click to expand...
Click to collapse
That's what she said. ...
^^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tossan said:
Basically you have to add this into the init.rc file (after creating manually the init.d folder of course)
Click to expand...
Click to collapse
So I take it it is not as simple as browsing with Root Explorer, finding the file and adding it. If not, could you tell me how. Can I do it using the terminal emulator app rather than connecting phone to PC and using cygwin? Thanks
tossan said:
That's what she said. ...
Click to expand...
Click to collapse
Sorry, I didn't read your post before I posted. You explained it even simpler so thanks
Gizmotech said:
So I take it it is not as simple as browsing with Root Explorer, finding the file and adding it. If not, could you tell me how. Can I do it using the terminal emulator app rather than connecting phone to PC and using cygwin? Thanks
Click to expand...
Click to collapse
I'm really not sure it's possible. But regarding 'in-phone script writing' Pyronia's just started a thread here on it that you could possibly raise the issue in: http://forum.xda-developers.com/showthread.php?t=1476400
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Gizmotech said:
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Click to expand...
Click to collapse
Rest of that thread has a suggestion on testing if its working forum.xda-developers.com/showthread.php?p=20134361#post20134361
I think permission of init.d is rwxr-xr-x. Check this thread here forum.xda-developers.com/showthread.php?t=1390093
Gizmotech said:
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Click to expand...
Click to collapse
Which script? Post the link here...or u open the script then type the command on terminal to check if the script working..
regards,
•ƒγяύs ργяσ™•
pyronia said:
Which script? Post the link here...or u open the script then type the command on terminal to check if the script working..
Click to expand...
Click to collapse
Basically, I mean how would I know if init.d is activated and any scripts I put in is actually working. After all I created init.d folder manually. What command do I type in adb shell to see if scripts are working?
Can someone help me troubleshoot this please. I have put scripts in the init.d folder but see no difference. I followed the method on this thread to enable init.d. I don't notice any difference after putting any scripts such as lagfree, turboboost or even the keylight one.
Gizmotech said:
Basically, I mean how would I know if init.d is activated and any scripts I put in is actually working. After all I created init.d folder manually. What command do I type in adb shell to see if scripts are working?
Click to expand...
Click to collapse
Sent me the script then i show u how to check
regards,
•ƒγяύs ργяσ™•
Gizmotech said:
Can someone help me troubleshoot this please. I have put scripts in the init.d folder but see no difference. I followed the method on this thread to enable init.d. I don't notice any difference after putting any scripts such as lagfree, turboboost or even the keylight one.
Click to expand...
Click to collapse
Which thread actually?
regards,
•ƒγяύs ργяσ™•
Init.d support ? Not without CF-ROOT
Herpderp Adreno + Tegra.
Well I thought this thread was about init.d on stock rom without CF-Root.

[HOW_TO] get 'init.d' Support on Tablet S

Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.
For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.
How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.
But now "Step-by-Step":
Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.
Step-by-Step Instructions:
1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'
Now finished .... it should work !
After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.
Have fun with the new 'init.d' support and apologize for my weak English !!
Special thanks to DooMLord for the idea and first implementation.
Source: http://forum.xda-developers.com/show....php?t=1431134
am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.
Thanx for a nice "how-to"
Seems simple and straightforward enough
Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)
Now you should find the zip on the end of first post.
Sorry - how do you gve the 777 file permissions?
SWFlyerUK said:
Sorry - how do you gve the 777 file permissions?
Click to expand...
Click to collapse
Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.
Whoops, my device is in a bootloop lol
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?
obicom said:
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
Click to expand...
Click to collapse
Doh! Thanks
SWFlyerUK said:
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
Click to expand...
Click to collapse
Not permissions fault. Mine didn't bootloop
obicom said:
Special thanks to DooMLord for the idea and first implementation.
Click to expand...
Click to collapse
yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
obicom said:
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
Click to expand...
Click to collapse
hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.
I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"
If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.
Click to expand...
Click to collapse
SWFlyerUK said:
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Click to expand...
Click to collapse
I wrote in many threads about 'rescue-backdoor', why havent you made it?
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!
-- Edit --
Rolled the build.prop increment value back
Click to expand...
Click to collapse
Does it mean now you have the original value or the lower value?
If first case , that was a fault.
SWFlyerUK said:
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
Click to expand...
Click to collapse
The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!

[MOD][KERNEL MODULE] wp_mod: disable system write protection

wp_mod: Module to disable system write protection
This is a kernel module that disables write protection on the system partition while running the stock kernel.
HTC changed the MMC_MUST_PREVENT_WP_VIOLATION code to make it much harder to crack. I had to redo the module completely, so this is experimental. In the past, it was a simple matter of changing a variable, now we have to replace a function in the kernel so it returns something different, causing the kernel to skip over the write protection code.
I would caution against loading the module after attempting to make changes to the system partition. It could end up corrupting the filesystem. If the module is loaded at boot, there should be no worries.
This module will probably need to be updated to load with future kernels when they are released.
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Download:
wp_mod for GPE Marshmallow 6.0 can be found here:
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Sense 4.4.4 (thanks @migascalp):
http://www.mediafire.com/download/4vyqslnc4crsnto/wp_mod_3.28.401.6.zip
Sense 4.4.3 (2.22 base):
wp_mod.ko
Sense 4.4.2:
wp_mod.ko
GPE 4.4.4 (thanks to @italyforever):
wp_mod.ko
GPE 4.4.2:
wp_mod.ko
Installation:
Wait for it to be implemented in your favourite ROM
* or *
Copy the module to your device, and type
Code:
su
insmod /location-where-you-copied-it/wp_mod.ko
Changes:
April 2, 2014 - wp_mod 4.1
-only return non-existing partition number if called by generic_make_request_checks
-remove exit from module (we don't want to be able to unload it)
-clean up code
March 31, 2014 - wp_mod 4.0
-new method for HTC One m8
Source:
https://github.com/flar2/wp_mod
Module was compiled against m8 Google Play Edition source. Some symbol CRC checks had to be hexedited in the compiled module to match the stock kernel. Thanks to Michael Coppola for example of function hooking on arm: http://poppopret.org/2013/01/07/suterusu-rootkit-inline-kernel-function-hooking-on-x86-and-arm/#arm
Nice Job!!!! this is awesome
AWESOME! Thank you! Will test and see
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Confirmed working here. I was able to delete stuff with titanium backup and it stuck after reboot. Thanks so much!
Sent from my M8 via XDA Premium app
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
You guys are awesome.
Awesome work....Can now scratch my theming itch
Sent from my unknown using Tapatalk
gjlowe said:
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Click to expand...
Click to collapse
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
graffixnyc said:
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
Click to expand...
Click to collapse
Can you share your zip please
Sent from my HTC One_M8 using Tapatalk
gjlowe said:
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
Click to expand...
Click to collapse
You need to run it each time you boot, until it is correctly working as init.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Electronic Punk said:
You need to run it each time you boot, until it is correctly working as init.
Click to expand...
Click to collapse
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
gjlowe said:
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
Click to expand...
Click to collapse
Yup, I have already added it to my copy of ARHD 3.x and it is working great, so look for a release as soon as Mikes connection allows!
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
-4ndr01d- said:
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
Click to expand...
Click to collapse
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
flar2 said:
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
Click to expand...
Click to collapse
jcase has got us root access ...its only writable to /system/xbin and has to run on every boot. the app used is called WeakSauce
but i was thinking. once my phone boots up, i wait til i have root access, then download the file, place it in the correct directory, download terminal emulator and run the commands. then /system becomes writable until next reboot?
@flar2 nice job as always man!! :good:
awesome awesome awesome
looking forward to elementalx on the m8!
For users who have init.d support in their ROM. Flash this and your good to go
https://mega.co.nz/#!XINyDIrB!QcdP3sZJjgKAivkEa7iN8Jusx0e78T1rpA5PT7VGAxQ
Sent from my Note 3

KPPD - Configure post-processing settings of your display! [2015/08/09]

Hello all! If you're familiar with KCAL and suffer from symptoms such as a locked bootloader or non-loadable kernel modules then you may be interested in KCAL Post-Processing Daemon, or KPPD - the all-in-one display tuning tool that you can use to customize your color calibration on the fly!
This does NOT require an unlocked bootloader, custom kernel, or even a kernel that supports module loading, just run the daemon and you're good to go!
To install on a device with a locked bootloader, you'll need to download the kppd release below, and unpack it to prep for some adb fun... (If you have TWRP, you can also flash this in recovery)
Code:
adb push /path/to/kppd /data/local/tmp/
adb push /path/to/postproc.conf /data/local/tmp/
adb shell
su
mount -o rw,remount /system
cp /data/local/tmp/kppd /system/bin/
cp /data/local/tmp/postproc.conf /system/etc/
chmod 0755 /system/bin/kppd
chmod 0644 /system/etc/postproc.conf
reboot
Now at this point, you can use any scripting app to start the daemon on boot, I use ROM Toolbox... http://i.imgur.com/0juzfug.png
And you're done! To edit your display settings, just edit the postproc.conf file... http://i.imgur.com/pjOPbIr.png
Download KPPD
Thanks, works great. Now we need some custom configs
any chance you can update your KCAL Color Control app to support KPPD? Easy way to set the values
Thanks Savoca! I have followed all of your work fairly closely and am very glad we have you around the forums!
This is amazing. Would it work for other LG tablets such as the LG X8.3 with the snapdragon 610?
My G4 is pretty decent but my tablet is super red. Once you get it setup, you constantly have to have Rom Toolbox installed to make this work or do you only need the app for the initial setup?
I think I can answer the second part of this. The rom toolbox thing is just one of many ways to run this script on boot. But you will need SOMEthing to start it no matter what. This could be init script (I think that's what its called, which some roms have built in) Or any custom rom could include it by default.
So no, Rom toolbox isn't really necessary, its just the way he recommended to get it running on boot if you don't know another way.
I am more curious to seen if it will work on my LG tablet. I'll just have to test it out. I guess worst case scenerio is you dont have it auto start on boot. If you mess it up you just reboot.
player911 said:
I am more curious to seen if it will work on my LG tablet. I'll just have to test it out. I guess worst case scenerio is you dont have it auto start on boot. If you mess it up you just reboot.
Click to expand...
Click to collapse
Yes it should work, however it depends on each device's version of the MDSS (Qualcomm display driver). If it doesn't work, let me know so I can add support for it.
I'm wondering if this would work on my G Flex 2 ? Is there any chance that it can break anything if it doesn't work?
---------- Post added at 03:37 PM ---------- Previous post was at 03:05 PM ----------
I've just installed it on my G Flex 2 and it works great. Thanks a lot!
how control this mod with KCAL apk???
armsar1978 said:
how control this mod with KCAL apk???
Click to expand...
Click to collapse
You can't (yet?). Only via the config.
New version uploaded significantly reduces CPU load and removes any delay between modifying the postproc.conf and applying the display settings.
I've read a little and I remember making rgb adjustments regularly with my old gnex years ago...
Wondering if there are suggested settings/values one can recommend for use with the G4 please.
I second this g4 question, any recommended values?
dontbeweakvato said:
I second this g4 question, any recommended values?
Click to expand...
Click to collapse
I'm using these right now: http://imgur.com/UKkOt7x
If you're editing the file at runtime, I recommend you use either FX File explorer or ES File Explorer to edit the config, root explorer and ROM toolbox editors delete the original file and rewrite a new one for some reason (maybe they can fix this in their apps) and kppd looses the original from the kernel.
Does this have an option for sharpness?
"su" doesnt work -> not found
Z900 said:
"su" doesnt work -> not found
Click to expand...
Click to collapse
You need to root your device.
savoca said:
I'm using these right now: http://imgur.com/UKkOt7x
If you're editing the file at runtime, I recommend you use either FX File explorer or ES File Explorer to edit the config, root explorer and ROM toolbox editors delete the original file and rewrite a new one for some reason (maybe they can fix this in their apps) and kppd looses the original from the kernel.
Click to expand...
Click to collapse
"Error occurred while trying to save file. File will not be saved." - using es file explorer. I seem to not have issues with rom toolbox. What's the deal with it not saving after editing?
dontbeweakvato said:
"Error occurred while trying to save file. File will not be saved." - using es file explorer. I seem to not have issues with rom toolbox. What's the deal with it not saving after editing?
Click to expand...
Click to collapse
Sounds like an issue with the app. You could always move the config file to somewhere on /data where you would have write access. Just point kppd to the config location in the init script.

G8x bootanimation

I need a way to get rid of the annoying carrier bootanimation thats in /product/OP/poweron and use the LG animation in /system/media
#Rooty_Mikes# said:
I need a way to get rid of the annoying carrier bootanimation thats in /product/OP/poweron and use the LG animation in /system/media
Click to expand...
Click to collapse
Nevermind! Figured it out! Searched for the G8X Twrp installer, flashed the ramdisk, flashed Disable DM-Verity&Force Encryption, then just used the twrp file manager to handle what i needed in the directories.
I was under the impression that their was no twrp for g8x.
#Rooty_Mikes# said:
Nevermind! Figured it out! Searched for the G8X Twrp installer, flashed the ramdisk, flashed Disable DM-Verity&Force Encryption, then just used the twrp file manager to handle what i needed in the directories.
I was under the impression that their was no twrp for g8x.
Click to expand...
Click to collapse
We can change root files from twrp? I tried with file managers but it got replaced again by ui. I have root
thekalpkuleria_24 said:
We can change root files from twrp? I tried with file managers but it got replaced again by ui. I have root
Click to expand...
Click to collapse
Yes, operating in twrp you are basically running abd root in terminal and you are system-as-root in the file manager so be careful, back-up prior to any changes. Any apk managers has a hard time with system-as-root permissions in production builds unless your the root master topjohnwu lol
#Rooty_Mikes# said:
Yes, operating in twrp you are basically running abd root in terminal and you are system-as-root in the file manager so be careful, back-up prior to any changes. Any apk managers has a hard time with system-as-root permissions in production builds unless your the root master topjohnwu lol
Click to expand...
Click to collapse
But making change from manager not works coz the ui changes my change again
It should work in twrp; unless you have a recovery.from.boot file in your system. I would go to terminal and run # getprop and see what's going on, you may have a ro.prop that's not allowing what you want to change
Yes it is ro.prop so what should i do?
thekalpkuleria_24 said:
So will running #getprop in terminal help me or twrp will help
Click to expand...
Click to collapse
It will help you find to see if you have a RO "read-only" property and value on your desired item example; I want to set my adb port to 5555 i would run # getprop and look through the property's to find my item and if it says:
$ service.adb.tcp.port=5038
I would change it with:
$ su -c resetprop service.adb.tcp.port=5555
Its all depending on the property and the location in the partition the files are in really in how its modified. What exactly are you trying to do?
#Rooty_Mikes# said:
It will help you find to see if you have a RO "read-only" property and value on your desired item example; I want to set my adb port to 5555 i would run # getprop and look through the property's to find my item and if it says:
$ service.adb.tcp.port=5038
I would change it with:
$ su -c resetprop service.adb.tcp.port=5555
Its all depending on the property and the location in the partition the files are in really in how its modified. What exactly are you trying to do?
Click to expand...
Click to collapse
Im trying to change sounds from product/OP plz tell a proper command what you wrote here it confused me a bit
thekalpkuleria_24 said:
Yes it is ro.prop so what should i do?
Click to expand...
Click to collapse
Run $ su -c resetprop [property]=value
And what to write in property and value ? I have no idea
thekalpkuleria_24 said:
Im trying to change sounds from product/OP plz tell a proper command what you wrote here it confused me a bit
Click to expand...
Click to collapse
thekalpkuleria_24 said:
/product/OP is mounted to a RO only partition, I would modify in the manager built in twrp. The modifications will remain when you reboot the system that way.
Click to expand...
Click to collapse
thekalpkuleria_24 said:
And what to write in property and value ? I have no idea
Click to expand...
Click to collapse
The property doesnt change only value "usually" a number 1 for yes, 0 for no
Okay thanks going for it
#Rooty_Mikes# said:
The property doesnt change only value "usually" a number 1 for yes, 0 for no
Click to expand...
Click to collapse
Do you have twrp?
#Rooty_Mikes# said:
Do you have twrp?
Click to expand...
Click to collapse
No im doing it in termux
thekalpkuleria_24 said:
No im doing it in termux
Click to expand...
Click to collapse
Not going to work
#Rooty_Mikes# said:
Not going to work
Click to expand...
Click to collapse
Ohh why it a terminal too
#Rooty_Mikes# said:
Not going to work....you need twrp or a recovery manager flash like AromiaFM.zip
Click to expand...
Click to collapse
Okay then will do in twrp

Categories

Resources