Has anyone had any luck on disabling the soft button backlight ? I tried various dimmer and kill led scripts with no luck.
Thanks in advance!
Sent from my YP-G70 using Tapatalk 2
it is a kernel thing
Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
diazlaz said:
Has anyone had any luck on disabling the soft button backlight ? I tried various dimmer and kill led scripts with no luck.
Thanks in advance!
Sent from my YP-G70 using Tapatalk 2
Click to expand...
Click to collapse
What ROM/kernel are you on? If you have init.d support, make a script with the following code:
Code:
chown root:root /sys/devices/virtual/sec/ts/touchkey_led
echo 0 > /sys/devices/virtual/sec/ts/touchkey_led
This will prevent the lights HAL (lib/hw/lights.s5pc110.so) from accessing it to turn it on, and then turn it off. Note that it is a binary value (that file above can only contain a 1 or a 0), so dimming is not possible.
Mevordel said:
What ROM/kernel are you on? If you have init.d support, make a script with the following code:
Code:
chown root:root /sys/devices/virtual/sec/ts/touchkey_led
echo 0 > /sys/devices/virtual/sec/ts/touchkey_led
This will prevent the lights HAL (lib/hw/lights.s5pc110.so) from accessing it to turn it on, and then turn it off. Note that it is a binary value (that file above can only contain a 1 or a 0), so dimming is not possible.
Click to expand...
Click to collapse
thanks mevordel. this worked perfectly!
diazlaz said:
thanks mevordel. this worked perfectly!
Click to expand...
Click to collapse
Dumb question but how to use that script?
Try this or this
Anyway I use root explorer to change permission to this: /sys/class/sec/ts/touchkey_led
Just remove Write permission to Group and turn off once the screen.
help with back lights
hey guys can i turn on my back lights? cause i like them but im running a custom ROM and kernel and they dont want to work ;/
Evoium said:
hey guys can i turn on my back lights? cause i like them but im running a custom ROM and kernel and they dont want to work ;/
Click to expand...
Click to collapse
Which one? They don't work on any released CM9 as far as I know.
Mevordel said:
What ROM/kernel are you on? If you have init.d support, make a script with the following code:
Code:
chown root:root /sys/devices/virtual/sec/ts/touchkey_led
echo 0 > /sys/devices/virtual/sec/ts/touchkey_led
This will prevent the lights HAL (lib/hw/lights.s5pc110.so) from accessing it to turn it on, and then turn it off. Note that it is a binary value (that file above can only contain a 1 or a 0), so dimming is not possible.
Click to expand...
Click to collapse
Should it be like:
Code:
#!/system/bin/sh
chown root:root /sys/devices/virtual/sec/ts/touchkey_led
echo 0 > /sys/devices/virtual/sec/ts/touchkey_led
??
KOala888 said:
Should it be like:
Code:
#!/system/bin/sh
chown root:root /sys/devices/virtual/sec/ts/touchkey_led
echo 0 > /sys/devices/virtual/sec/ts/touchkey_led
??
Click to expand...
Click to collapse
doesn't matter
Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
Related
Hi guyz, i need someone help me.
I need 2 read from logcat a specific line:
Code:
I/ActicityManager< 1782> Config Changed: { scale1.0 imsi=204/16 loc=nl_NL touch=3 [B][COLOR="Red"]keys=2/1/2[/COLOR][/B] nav=2/1orien=1 layout=17 uiMode=17 seq=20}
How can i do to compare the text on red, with some variable into a bash script ?
Thanks in advance
on linux
adb logcat | grep "yourtext"
shows only lines with the text specified
slade87 said:
on linux
adb logcat | grep "yourtext"
shows only lines with the text specified
Click to expand...
Click to collapse
thanks, but i need 2 compare on smartphone, its for keyboard fix, and go something like this:
K1= "keys=2/1/1"
K2="here it takes text from logcat"
if [ "$K1" = "$K2" ];
then
turn on lights
else
turn off lights
fi
Click to expand...
Click to collapse
try to take the event:
maybe this helps:
http://stackoverflow.com/questions/1068000/android-keyboard-event-handler
slade87 said:
try to take the event:
maybe this helps:
http://stackoverflow.com/questions/1068000/android-keyboard-event-handler
Click to expand...
Click to collapse
It's that java languaje ?, **** im confused
PD: Was android programmed in java?, i thought just softwares were programmed in java
Slade it is for keyboard light we need to read the logcat if the key lit is slight out keyboard light goes on
If the lit is out you get keys=2/1/2 so if the script can read that and then echo a 1 to the keylight file
Thats what we need
Sent from my U20i using XDA Premium App
slade see what we got
# keyboard in/out fix
dev=/sys/devices/platform/msm_pmic_misc_led.0
fich=/system/bin
if [ -e cat $fich/whereverlogtakesplace | tail "keys=2/1/1" ];
then
cat /dev/input/event0|read -n 4
echo 1 > $dev/brightness
sleep 1
else
echo 0 > $dev/brightness
sleep 1
fi
you need su priviliges
/system/bin/logcat
slade87 said:
you need su priviliges
/system/bin/logcat
Click to expand...
Click to collapse
You mean script goes something like this
# keyboard in/out fix
dev=/sys/devices/platform/msm_pmic_misc_led.0
fich=/system/bin
if [ -e cat $fich/logcat | tail "keys=2/1/1" ];
then
cat /dev/input/event0|read -n 4
echo 1 > $dev/brightness
sleep 1
else
echo 0 > $dev/brightness
sleep 1
fi
Click to expand...
Click to collapse
EDIT: Dont working, i need to fix, script is bad
EDIT: On /system/bin/logcat dont exist logs, i opened logcat, and no logs
do a cat on /system/bin/logcat in your terminal emulator
works for me
Put the script in /etc/init.d and put this above your script then a blank line and then your script
''#!/system/bin/sh'' without quotes ofc
And make sure permission is 777 or 755 (rwxrwxrwx or rwxr-xr-x)
And name it 00keyboard
And one more thing you are checking the logcat now and then check and read the event0
We found out reading the event0 wont work
So that line will **** up the script
Delete the line ''cat /dev/input/event0|read -n 4''
Sent from my U20i using XDA Premium App
owain94 said:
Put the script in /etc/init.d and put this above your script then a blank line and then your script
''#!/system/bin/sh'' without quotes ofc
And make sure permission is 777 or 755 (rwxrwxrwx or rwxr-xr-x)
And name it 00keyboard
And one more thing you are checking the logcat now and then check and read the event0
We found out reading the event0 wont work
So that line will **** up the script
Delete the line ''cat /dev/input/event0|read -n 4''
Sent from my U20i using XDA Premium App
Click to expand...
Click to collapse
Something like this:
'#!/system/bin/sh
# keyboard in/out fix
su
dev=/sys/devices/platform/msm_pmic_misc_led.0
fich=/system/bin
logcat > $fich/logcat.txt
if [ -e cat $fich/logcat.txt | tail "keys=2/1/1" ];
then
echo 1 > $dev/brightness
sleep 1
else
echo 0 > $dev/brightness
sleep 1
fi
Click to expand...
Click to collapse
sorry just type:
/system/bin/logcat | grep 'keys=2/1/1'
in your console
D4rKn3sSyS said:
#!/system/bin/sh
# keyboard in/out fix
dev=/sys/devices/platform/msm_pmic_misc_led.0/
fich=/system/bin/
if [ -e cat $fich/logcat | grep "keys=2/1/1" ];
then
echo 1 > $dev/brightness
sleep 9
else
if [ -e cat $fich/logcat | grep "keys=2/1/2" ];
then
echo 0 > $dev/brightness
sleep 9
fi
Click to expand...
Click to collapse
I think it need to look something like this?
Long sleep so it dont check it to often
And then loop the script so it keeps checking
Sent from my U20i using XDA Premium App
slade87 said:
sorry just type:
/system/bin/logcat | grep 'keys=2/1/1'
in your console
Click to expand...
Click to collapse
yah that works, but we need to make it working without console, on a batch script
last that i got
#!/system/bin/sh
#
# keyboard in/out fix
dev=/sys/devices/platform/msm_pmic_misc_led.0/
fich=/system/bin/
if [ -e cat $fich/logcat | grep 'keys=2/1/1' ];
then
echo 1 > $dev/brightness
sleep 9
else
if [ -e cat $fich/logcat | grep 'keys=2/1/2' ];
then
echo 0 > $dev/brightness
sleep 9
fi
Click to expand...
Click to collapse
Code:
#!/system/bin/sh
/system/bin/logcat | grep 'keys=2/1/1' > /sdcard/true.log
if [ -s /sdcard/true.log ]; then
echo 1 > /sys/devices/platform/msm_pmic_misc_led.0/brightness
rm /sdcard/true.log
sleep 1
else
echo 0 > /sys/devices/platform/msm_pmic_misc_led.0/brightness
sleep 1
fi
its a dirty hack but give it a try.
it checks wheter created file is greater than 0 bytes which it is if true.log was created.
it removes true.log if successfull.
This script runs once now dark so if u wanna check open the keyboard and do this in terminal
Adb shell
Sh ./system/etc/init.d/00keyboard
You need to add a loop if you wanna to check over and over again
But you need to add longer sleeps then so it would not eat battery the problem then is that it will not put keyboard light on when you slide the lid open but a couple seconds later
Sent from my U20i using XDA Premium App
it would need to run later so name it 91keyboard after sdcard is mounted.
slade87 said:
it would need to run later so name it 91keyboard after sdcard is mounted.
Click to expand...
Click to collapse
Ahh yes ofcourse sorry my bad
Sent from my U20i using XDA Premium App
owain94 said:
Ahh yes ofcourse sorry my bad
Sent from my U20i using XDA Premium App
Click to expand...
Click to collapse
Called it 91keyboard and then this is the actual code:
Code:
#!/system/bin/sh
#
#Keyboard light fix
/system/bin/logcat | grep 'keys=2/1/1' > /sdcard/true.log
if [ -s /sdcard/true.log ]; then
echo 1 > /sys/devices/platform/msm_pmic_misc_led.0/brightness
rm /sdcard/true.log
sleep 1
else
echo 0 > /sys/devices/platform/msm_pmic_misc_led.0/brightness
sleep 1
fi
I'm using Jelly Bean now and I'm trying to make the second core run with little success.
This is what I used to us.
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
I take it that something has changed but I don't what. Any ideas?
oohaylima said:
I'm using Jelly Bean now and I'm trying to make the second core run with little success.
This is what I used to us.
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
I take it that something has changed but I don't what. Any ideas?
Click to expand...
Click to collapse
I would just install Kernel Tuner and select Link Cores and they both will be running.
raptoro07 said:
I would just install Kernel Tuner and select Link Cores and they both will be running.
Click to expand...
Click to collapse
Thanks. I'll download that for safe keeping later on.
The string works, it's just that I was coming across an ID 10-T error.
Here's where it belongs with the string needed.
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
And it goes in :
/system/etc/init.qcom.post_boot.sh
Man, it took me a few hours to figure this out. I'm getting old. I should just find a new hobby.
Hi,
I want to disable the soft-keys (those beside the hardware home button) and their back light in CM10.1 Rom.
Actually I want to use the Navigation bar (interface soft-keys) just like in nexus devices.
But the official CM10.1 Rom doesn't has any setting to enable navigation bar . And there is no advanced settings to disable soft-keys back light or to disable soft-keys.
I managed to enable Navigation bar and disable soft-keys by following this thread . But the soft-keys back light is still present.
Next, I followed this thread to disable soft-keys back light. But it didn't work. Infact there is no such setting as this ( <bool name="config_autoBrightnessButtonKeyboard">true</bool> ) in bools.xml. I tried adding that new line with no result.
So, how can I disable soft-keys backlight ?
nfs1mw said:
Hi,
I want to disable the soft-keys (those beside the hardware home button) and their back light in CM10.1 Rom.
Actually I want to use the Navigation bar (interface soft-keys) just like in nexus devices.
But the official CM10.1 Rom doesn't has any setting to enable navigation bar . And there is no advanced settings to disable soft-keys back light or to disable soft-keys.
I managed to enable Navigation bar and disable soft-keys by following this thread . But the soft-keys back light is still present.
Next, I followed this thread to disable soft-keys back light. But it didn't work. Infact there is no such setting as this ( <bool name="config_autoBrightnessButtonKeyboard">true</bool> ) in bools.xml. I tried adding that new line with no result.
So, how can I disable soft-keys backlight ?
Click to expand...
Click to collapse
Go on dialer and type
3845#*YOUR VARIANT PHONE MODEL#
Click to expand...
Click to collapse
for example mine is p769. I type 3845#*769#. After, go on "H/W device test" and scroll down till you see Touch Led brightness and select off.
Sent from my LG-P769 using Tapatalk 4
run this as su
#!/system/bin/sh
#disable Key Backlight
echo begin set Key Backlight - KB
echo KB - set permissions rw
chmod 0666 /sys/class/leds/button-backlight/brightness
echo KB - set Key Backlight 0
echo "0" > /sys/class/leds/button-backlight/brightness
echo KB - set permissions ro
chmod 0444 /sys/class/leds/button-backlight/brightness
echo KB - done!
note: I did not create this, just sharing
geeshiet said:
Go on dialer and type for example mine is p769. I type 3845#*769#. After, go on "H/W device test" and scroll down till you see Touch Led brightness and select off.
Sent from my LG-P769 using Tapatalk 4
Click to expand...
Click to collapse
I can't find hidden menu in CM10.1 with this trick. The menu appears in stock rom.
kuma82 said:
run this as su
#!/system/bin/sh
#disable Key Backlight
echo begin set Key Backlight - KB
echo KB - set permissions rw
chmod 0666 /sys/class/leds/button-backlight/brightness
echo KB - set Key Backlight 0
echo "0" > /sys/class/leds/button-backlight/brightness
echo KB - set permissions ro
chmod 0444 /sys/class/leds/button-backlight/brightness
echo KB - done!
note: I did not create this, just sharing
Click to expand...
Click to collapse
That worked. Thank you so much. . But the setting is lost on reboot. I have pushed the script file to /etc/init.d/ to start the script everytime on boot.
I'm attaching the recovery flashable zip file below incase anyone needs it. Flashing it from recovery in CM10.1 ROM disables the softkey backlight .
My job was to just show you the way and you take care of the rest.
CM 10.1 P769
I'm using Huawei honor U8860 and this worked for me, thank you so much
not work for cm10.. and brick my phone hehehe sad
kuma82 said:
run this as su
#!/system/bin/sh
#disable Key Backlight
echo begin set Key Backlight - KB
echo KB - set permissions rw
chmod 0666 /sys/class/leds/button-backlight/brightness
echo KB - set Key Backlight 0
echo "0" > /sys/class/leds/button-backlight/brightness
echo KB - set permissions ro
chmod 0444 /sys/class/leds/button-backlight/brightness
echo KB - done!
note: I did not create this, just sharing
Click to expand...
Click to collapse
and how to enable again ??
neodanone said:
and how to enable again ??
Click to expand...
Click to collapse
Reboot phone
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Reboot phone
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ah oke its work, flashable zip right ur script isn't work make a bootloop but if I type its work
Well ive done alot of searching and I am unable to find the info specific to the lg l9. Im currently running kumas rom so I am able to use the command
SU
./etc/overclock
This bumps me up to 1.2 ghz. Is there a method to go higher than 1.2ghz on a locked bootloader? If so can someone explain or post a link. It is also very annoying to have to type the command after each boot. Has anyone got this script to successfully run at boot without running it manually? I have used a few programs that auto runs scripts at boot. I gave it SU and boot permissions and It shows it under notifications that it does run at boot however under no frills cpu program it does not make the 1.2 available until after I manually run the script.THANKS!
lwg45714 said:
Well ive done alot of searching and I am unable to find the info specific to the lg l9. Im currently running kumas rom so I am able to use the command
SU
./etc/overclock.THANKS!
Click to expand...
Click to collapse
Write the script to init.d
Lgeob said:
Write the script to init.d
Click to expand...
Click to collapse
Do you have a link that tells how to do that or maybe explain? THAnks!
lwg45714 said:
Do you have a link that tells how to do that or maybe explain? THAnks!
Click to expand...
Click to collapse
Try to open the file overclock as text.What is written?
lwg45714 said:
Do you have a link that tells how to do that or maybe explain? THAnks!
Click to expand...
Click to collapse
Please take a look at this post
Edit: don't know why I miss a link in last post
http://forum.xda-developers.com/showthread.php?t=2096061
Lgeob said:
Try to open the file overclock as text.What is written?
Click to expand...
Click to collapse
IT says:
#!/system/bin/sh
ECHO 0 300 980> /PROC/CPU_CONTROL/TWEAK_CPu
ECHO 1 600 1200>/proc/cpu_control/tweak_cpu
ECHO 2 900 1260> /proc/ cpu_control/ tweak_ cpu
ECHO 3 1200 1340>/proc/cpu_control/ tweak_ cpu
If you use modules,try this,create a filepaste is:
Code:
#!/system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980> /proc/cpu_control/tweak_cpu
echo 1 600 1200> /proc/cpu_control/tweak_cpu
echo 2 900 1260> /proc/cpu_control/tweak_ cpu
echo 3 1200 1340> /proc/cpu_control/tweak_ cpu
Place it in the folder init.d
lwg45714 said:
IT says:
#!/system/bin/sh
ECHO 0 300 980> /PROC/CPU_CONTROL/TWEAK_CPu
ECHO 1 600 1200>/proc/cpu_control/tweak_cpu
ECHO 2 900 1260> /proc/ cpu_control/ tweak_ cpu
ECHO 3 1200 1340>/proc/cpu_control/ tweak_ cpu
Click to expand...
Click to collapse
I don't have it set at boot because the phone "might" lockup/freeze. In addition, some phones don't allow overclocking.
If you want it set at boot type the following in a terminal
Code:
su
mount -o remount /system
cp /etc/overclock /etc/init.d/
chmod 777 /etc/init.d/overclock
Or just use a root browser app to put it (overclock script) in the init.d folder.
Raising the CPU any higher won't improve performance and the phone will more than likely crash. If you dig through the l9 forums you will find a lot more information on the subject.
Oh and don't be afraid to ask questions in my thread
Lgeob said:
If you use modules,try this,create a filepaste is:
Code:
#!/system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980> /proc/cpu_control/tweak_cpu
echo 1 600 1200> /proc/cpu_control/tweak_cpu
echo 2 900 1260> /proc/cpu_control/tweak_ cpu
echo 3 1200 1340> /proc/cpu_control/tweak_ cpu
Place it in the folder init.d
Click to expand...
Click to collapse
I already have the modules loaded in another script.
Sent from my LGMS769 using XDA Premium 4 mobile app
Hey everyone,
I've been failing miserably to get init.d support on the MIUI 7 developer roms for the Redmi Note 2 and tried every possible thing from this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1933849. I found a couple of posts regarding init.d support on en.miui.com as well, but they are all targeted at MIUI 5/6. Is there anyone who can help me out with this? I would love to get the support to prevent data from leaking at boot (firewall).
Thanks!
Edit 24/01: Flashed Namaless' MIUI Speed MOD which enabled init.d support. Scripts are being executed correctly on boot.
Smiui ?
Have you tried the smiui rom ? http://www.smiui.net/
It works OK on my Redmi Note 2 Prime and claims to have init.d support although I haven't used this feature yet.
Discussed here
http://forum.xda-developers.com/redmi-note-2/development/rom-smiui-rom-kitchen-major-xiaomi-t3225567
I'm using Miui 7 5.11.19
elaurens said:
Hey everyone,
I've been failing miserably to get init.d support on the MIUI 7 developer roms for the Redmi Note 2 and tried every possible thing from this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1933849. I found a couple of posts regarding init.d support on en.miui.com as well, but they are all targeted at MIUI 5/6. Is there anyone who can help me out with this? I would love to get the support to prevent data from leaking at boot (firewall).
Thanks!
Click to expand...
Click to collapse
Pal, this 'switcher' made the magic for me, https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler&hl=it
Redmi Note 2 Prime Dev EU 5.11.1 here
fourlans said:
Have you tried the smiui rom ? http://www.smiui.net/
It works OK on my Redmi Note 2 Prime and claims to have init.d support although I haven't used this feature yet.
Discussed here
http://forum.xda-developers.com/redmi-note-2/development/rom-smiui-rom-kitchen-major-xiaomi-t3225567
I'm using Miui 7 5.11.19
Click to expand...
Click to collapse
Thanks for the tip. Gonna use that as a last resort as I'd rather just run the Chinese developer rom + init.d support (don't really need any of the other features which smiui offers).
oldslowdiver said:
Pal, this 'switcher' made the magic for me, https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler&hl=it
Redmi Note 2 Prime Dev EU 5.11.1 here
Click to expand...
Click to collapse
Installed on 5.11.19 and enabled AfWall+ data leaking fix (script on startup), but it's still not running. Can you tell me which script you managed to get running after enabling init.d through the toggler app?
Thx.
elaurens said:
Installed on 5.11.19 and enabled AfWall+ data leaking fix (script on startup), but it's still not running. Can you tell me which script you managed to get running after enabling init.d through the toggler app?
Thx.
Click to expand...
Click to collapse
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------
oldslowdiver said:
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
Click to expand...
Click to collapse
You know what.. they actually won't work! I was sure they did, I just checked, and they actually don't. Still, Init.d is enabled.. wtf?
oldslowdiver said:
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------
You know what.. they actually won't work! I was sure they did, I just checked, and they actually don't. Still, Init.d is enabled.. wtf?
Click to expand...
Click to collapse
Yeah see.. that's my problem with it I can't find the thread back on en.miui.com's forum, but I read earlier today that MIUI uses another way to launch scripts on startup. No further explanation was given though. Weird, maybe I should try the sMIUI ROM and see what it gives.
Enable Init.d on Redmi Note 2
elaurens said:
Yeah see.. that's my problem with it I can't find the thread back on en.miui.com's forum, but I read earlier today that MIUI uses another way to launch scripts on startup. No further explanation was given though. Weird, maybe I should try the sMIUI ROM and see what it gives.
Click to expand...
Click to collapse
Okay, I found the thread you mentioned on MIUI's website (http://en.miui.com/thread-129336-1-1.html), but you need to correct the path as it follows in Terminal Emulator:
Type :
su
sh /storage/sdcard1/term-init.sh
You have to place the term-init.sh inside the internal SD card in this case, download file here https://www.androidfilehost.com/?w=...5e497fa2bc98ce82437cb8cbfbdb4e56c73c1dd621ead
Anyway, if it works, it should create a Test.log file in /data, but it won't
Try your luck
oldslowdiver said:
Okay, I found the thread you mentioned on MIUI's website (http://en.miui.com/thread-129336-1-1.html), but you need to correct the path as it follows in Terminal Emulator:
Type :
su
sh /storage/sdcard1/term-init.sh
You have to place the term-init.sh inside the internal SD card in this case, download file here https://www.androidfilehost.com/?w=...5e497fa2bc98ce82437cb8cbfbdb4e56c73c1dd621ead
Anyway, if it works, it should create a Test.log file in /data, but it won't
Try your luck
Click to expand...
Click to collapse
Cool of you to follow this up The term-init.sh script actually comes from XDA and this is its original thread: http://forum.xda-developers.com/showthread.php?t=1933849. I copied the script to the internal SD card and executed it (with different versions of busybox), the script ran successfully (/system/etc/init.d and other files are created, permissions set correctly), but that Test.log file isn't being created in /data after a reboot. Of course, when I run the following command manually from a terminal, it does create the Test.log file: /system/xbin/busybox run-parts /system/etc/init.d. So for some reasons, the scripts in /system/etc/init.d/ aren't being executed at boot (and my knowledge is too restricted to troubleshoot this further :/)
elaurens said:
Cool of you to follow this up The term-init.sh script actually comes from XDA and this is its original thread: http://forum.xda-developers.com/showthread.php?t=1933849. I copied the script to the internal SD card and executed it (with different versions of busybox), the script ran successfully (/system/etc/init.d and other files are created, permissions set correctly), but that Test.log file isn't being created in /data after a reboot. Of course, when I run the following command manually from a terminal, it does create the Test.log file: /system/xbin/busybox run-parts /system/etc/init.d. So for some reasons, the scripts in /system/etc/init.d/ aren't being executed at boot (and my knowledge is too restricted to troubleshoot this further :/)
Click to expand...
Click to collapse
Exactly. And I found here http://en.miui.com/thread-99174-1-1.html you may edit Build.prop and add
sys.initd = 1
to enable Init.d scripts at boot, but, again, it won't work. So, if anyone finds a solution, please, share.
oldslowdiver said:
Exactly. And I found here http://en.miui.com/thread-99174-1-1.html you may edit Build.prop and add
sys.initd = 1
to enable Init.d scripts at boot, but, again, it won't work. So, if anyone finds a solution, please, share.
Click to expand...
Click to collapse
Haha. Are you oldmyself on the official MIUI forum who gave me the exact same reply in this thread?
elaurens said:
Haha. Are you oldmyself on the official MIUI forum who gave me the exact same reply in this thread?
Click to expand...
Click to collapse
heheheheh small world, it's me.
oldslowdiver said:
heheheheh small world, it's me.
Click to expand...
Click to collapse
Just so you know, I've got init.d support and scripts being executed on boot thanks to @Namaless' MIUI speed mod. I'm currently running the latest version (v.1.19) and AfWall's firewall rules are being applied on boot. Big thanks to him for that