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
Related
how to disable ambient light sensor in xperia mini ,is there any method to do that,can anybody help on that issue ?
i use this on my x8, i don't know is this working on Xperia mini, my ray don't have it so i can't try.
1.ROOTED
2.open system/etc/hw_config.sh
3.edit
Code:
echo i2c_pwm_als > $dev/mode # BL control modes [i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als]
delete "_als" in "echo i2c_pwm_als"
4.save and out, reboot
this should work....you can use root explorer to do this.
sorry for my English, still learning and have bad marks at GRAMMAR and VOCABULARY.
ok thanks will try it
Moved to proper forum.
nitinex said:
ok thanks will try it
Click to expand...
Click to collapse
is it working?
[HOWTO] disable ambient light sensor for LCD in xperia mini
I think I've suceeded in turning off auto-brightness in my SK17i (Xperia mini pro), Android 2.3.3, build 4.0.A.2.368.
It doesn't dim backlight after couple of second inactivity.
It still dim backlight about 3 seconds before timeout set in Settings/Display/Screen timeout.
You will need root. Files you have to modify has mode "-rw-r--r--" (writable only for root).
You can try it without permanent changes (settings will be lost after reboot):
Connect phone to PC over USB cable, enable Settings/Applications/Development/USB debugging.
Run command:
Code:
adb shell
You should get root shell (line begins with #).
In that shell run:
Code:
echo 0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
Disconnect USB cable.
If it works for you, you can make it permanent. Basically you will edit file which sets this on device boot:
Open Root explorer
Go to /etc diretory
Find hw_config.sh, long touch and in popup select Open in Text Editor
Find line
Code:
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
and edit it to
Code:
echo 0 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
Press Back button and save file.
scroolik said:
I think I've suceeded in turning off auto-brightness in my SK17i (Xperia mini pro), Android 2.3.3, build 4.0.A.2.368.
It doesn't dim backlight after couple of second inactivity.
It still dim backlight about 3 seconds before timeout set in Settings/Display/Screen timeout.
You will need root. Files you have to modify has mode "-rw-r--r--" (writable only for root).
You can try it without permanent changes (settings will be lost after reboot):
Connect phone to PC over USB cable, enable Settings/Applications/Development/USB debugging.
Run command:
Code:
adb shell
You should get root shell (line begins with #).
In that shell run:
Code:
echo 0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
Disconnect USB cable.
If it works for you, you can make it permanent. Basically you will edit file which sets this on device boot:
Open Root explorer
Go to /etc diretory
Find hw_config.sh, long touch and in popup select Open in Text Editor
Find line
Code:
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
and edit it to
Code:
echo 0 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
Press Back button and save file.
Click to expand...
Click to collapse
It works, but... After the phone starts, the maximum brightness is set up and ambient senzor doesn't work. But if you turn off display and then you wake it up, brightness is lower than before it's like you have been in dark room, but aren't.
Is it also working with xperia active?
Is there a possibility to disable the soft key backlight at this way?
duke85 said:
Is it also working with xperia active?
Is there a possibility to disable the soft key backlight at this way?
Click to expand...
Click to collapse
Use "superDim"
Sent from my MT15i using Tapatalk
superDim can also disable soft key backlights?
I can't find that kind of option
Yes. Try other lights option.
To disable softkeys light I use Screen Filter with 100% settings to not dim the screen and it has an option to disable softkeys light. I enable and disable with app shortcut. The widget will not work with full 100% screen, but use regular icon.
I rooted my xperia active.
Superdim don't disable the ambient light sensor.
The Button Backlight once is disabled, once it isn't... doesn't work steady When I'm closing superdim, backlights are back on.
Is there another possibility?
Will this work for you?
market.android.com/details?id=com.hatcyl.android.Disable_Auto_Brightness
http://forum.xda-developers.com/showthread.php?t=1259445
Meanwhile I edited my /etc/hw_config.sh:
# LMU AS3676 Configuration
dev=/sys/devices/i2c-0/0-0040/leds
#Sensor on/off. 1 = on, reg 90h
echo 1 > $dev/lcd-backlight/als/enable
#[gain],[filter_up],[filter_down],[offset]
echo 3,2,2,0 > $dev/lcd-backlight/als/params
# touch-button-backlight
echo 8000 > $dev/button-backlight/max_current
echo 6450 > $dev/red/max_current
echo 7950 > $dev/green/max_current
echo 4500 > $dev/blue/max_current
# ALS curve display BL [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 1,30,255,54,52,1,65 > $dev/lcd-backlight/als/curve
# ALS curve key LED 2 [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 2,48,0,128,128,4,10 > $dev/button-backlight/als/curve
# ALS curve RGB(red) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/red/als/curve
# ALS curve RGB(green) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/green/als/curve
# ALS curve RGB(blue) [grp],[Y0],[Y3],[K1],[K2],[X1],[X2]
echo 3,71,255,64,32,5,37 > $dev/blue/als/curve
In line echo 1 > $dev/lcd-backlight/als/enable I replace the "1" with a "0".
The other bold lines I simple deleted, except echo 8000 > $dev/button-backlight/max_current
Until now the ALS is disabled in any Situation.
For button backlight I replaced "8000" with "0001" in line echo 8000 > $dev/button-backlight/max_current
Until now the button backlight is disabled in any Situation...
scroolik said:
I think I've suceeded in turning off auto-brightness in my SK17i (Xperia mini pro), Android 2.3.3, build 4.0.A.2.368.
It doesn't dim backlight after couple of second inactivity.
It still dim backlight about 3 seconds before timeout set in Settings/Display/Screen timeout.
You will need root. Files you have to modify has mode "-rw-r--r--" (writable only for root).
You can try it without permanent changes (settings will be lost after reboot):
Connect phone to PC over USB cable, enable Settings/Applications/Development/USB debugging.
Run command:
Code:
adb shell
You should get root shell (line begins with #).
In that shell run:
Code:
echo 0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
Disconnect USB cable.
If it works for you, you can make it permanent. Basically you will edit file which sets this on device boot:
Open Root explorer
Go to /etc diretory
Find hw_config.sh, long touch and in popup select Open in Text Editor
Find line
Code:
echo 1 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
and edit it to
Code:
echo 0 > $dev/lcd-backlight/als/enable #Sensor on/off. 1 = on, reg 90h
Press Back button and save file.
Click to expand...
Click to collapse
It also works on my st15i. Thanks!
You think or you did ?
This works even on ICS
https://play.google.com/store/apps/...uYW5kcm9pZC5EaXNhYmxlX0F1dG9fQnJpZ2h0bmVzcyJd
duke85 said:
superDim can also disable soft key backlights?
I can't find that kind of option
Click to expand...
Click to collapse
you can do it yourself.
type in terminal emulator:
su
echo 1 > /sys/class/leds/button-backlight/max_current
after reboot backllights will be on again.
you can create a script using scripter app from play store or you can create a permanent init.d script yourself (or i can provide a flashable zip)
Hi how to change led color in kernel to initiate recovery??
Jawor245 said:
Hi how to change led color in kernel to initiate recovery??
Click to expand...
Click to collapse
Are you familiar with editing the boot.img?
I'd like to know which file and command is responsible for this after i unpack boot.img.
Jawor245 said:
I'd like to know which file and command is responsible for this after i unpack boot.img.
Click to expand...
Click to collapse
I think it's in the ramdisk -> sbin. There is a bootrec or booterc-device file where you can find these lines or similar ones:
Code:
# trigger amber LED
echo '255' > /sys/class/leds/blue/brightness
echo '255' > /sys/class/leds/red/brightness
echo '0' > /sys/class/leds/green/brightness
# trigger button-backlight
echo '255' > /sys/class/leds/button-backlight/brightness
cat /dev/input/event2 > /dev/keycheck&
sleep 3
# trigger amber LED
echo '0' > /sys/class/leds/blue/brightness
echo '0' > /sys/class/leds/red/brightness
echo '0' > /sys/class/leds/green/brightness
# trigger button-backlight
echo '0' > /sys/class/leds/button-backlight/brightness
Now you should be able to change these leds to another color. But I haven't tried that yet
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
I found out how to switch between 4 screen modi.
It works on rooted devices and the commands can also be used with tasker.
Code:
echo "0" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "1" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "3" > /sys/devices/virtual/mdnie/mdnie/accessibility
0 : Normal Screen
1 : Inverted Colors
2 : Ultra Power Save Mode
3 : Screen off but not locked and touchscreen is still working
Mode 3 is particulary interesting if you want to record long videos while screen is off or if you want to listen to youtube music videos.
Here some commands to change colors (RED,GREEN, BLUE)
Code:
echo "255 0 0" > /sys/devices/platform/kcal_ctrl.0/kcal;echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
echo "0 255 0" > /sys/devices/platform/kcal_ctrl.0/kcal;echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
echo "0 0 255" > /sys/devices/platform/kcal_ctrl.0/kcal;echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
An other way to turn off the Display is to set all colors to 0
Code:
echo "0 0 0" > /sys/devices/platform/kcal_ctrl.0/kcal;echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
to return to normal screen type
Code:
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal;echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
Maybe some of these commands can also used on other devices.
Have fun
I have attached a Tasker Profile and a toggle widget, so you can try it out.
The widget activates/deactivates the profile, and with the proximity sensor you can switch the screen mode.
Interesting...on Galaxy S4 with UPSM code all color became white and black
Nice find!
Albe95 said:
Interesting...on Galaxy S4 with UPSM code all color became white and black
Click to expand...
Click to collapse
This works for me too! Been looking for this for a while now...
I'm on SGS4 GE and the echo "2" code turns my screen black and white. Now I can finally complete my Tasker %Battlow profile the way I want :victory:
Great find!
Great find
Thanks alot for this, I have a wierd bug where power saving mode will never deactivate grayscale (I think I introduced it at some point while screwing around with root).
Made a tasker task to enable power save mode (without gray scale) then "manually" run "echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility" to turn on gray scale. Works like a charm.
Thanks! Invert screen toggle tasker action
Nice!
I just mapped the "Assistance Request" event on my Samsung tablet to a Tasker task that toggles screen inversion. The task gets triggered by holding the home button. This is great for reading in a quick-and-dirty "night mode" with white text on black in most e-readers. Psuedocode below:
1: Run Shell Command: echo "0" > /sys/devices/virtual/mdnie/mdnie/accessibility
Use Root = On
If %ColorsInverted eq 1
2: Run Shell Command: echo "1" > /sys/devices/virtual/mdnie/mdnie/accessibility
Use Root = On
If %ColorsInverted neq 1
3: Variable Set %ColorsInverted = 1 - %ColorsInverted
Do Maths = On
Thanks for sharing. I used this method to create a toggle for grayscale. Since I'm new to Tasker, I didn't figure it out after following step 1 to 3 until I added:
4: add a new variable %ColorsInverted in VARS and give it a value of 0.
After the task is created, I added the shortcut with widget from Tasker.
gsearle5 said:
Nice!
I just mapped the "Assistance Request" event on my Samsung tablet to a Tasker task that toggles screen inversion. The task gets triggered by holding the home button. This is great for reading in a quick-and-dirty "night mode" with white text on black in most e-readers. Psuedocode below:
1: Run Shell Command: echo "0" > /sys/devices/virtual/mdnie/mdnie/accessibility
Use Root = On
If %ColorsInverted eq 1
2: Run Shell Command: echo "1" > /sys/devices/virtual/mdnie/mdnie/accessibility
Use Root = On
If %ColorsInverted neq 1
3: Variable Set %ColorsInverted = 1 - %ColorsInverted
Do Maths = On
Click to expand...
Click to collapse
It is possible to use 128 128 128? grayscale
Good day all, I've been testing these commands on tasker for my Note4 running 6.0.1 and i've found one additional setting which i believe might help some of you.
echo "0" > /sys/devices/virtual/mdnie/mdnie/accessibility [normal mode]
echo "1" > /sys/devices/virtual/mdnie/mdnie/accessibility [inverted colors]
echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility [ultra power saver - almost pitch black tones]
echo "3" > /sys/devices/virtual/mdnie/mdnie/accessibility [screen off with touch on]
echo "4" > /sys/devices/virtual/mdnie/mdnie/accessibility [power saver mode with normal gray scale colors]
I greatly appreciate the thread and i hope my added line helps others like me that lost the gray scale when updating to marshmallow. Have a great day guys and keep-on tweaking! ^_^
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