Hi, I found a way to turn off the capacitive key backlight. Just download and install ( Soft buttons lite) from the playstore . Open the app and click on (keep the lights off). If anyone has any other solution please post.
Sent from my HTC first using xda premium
It also happens to work on One S. Thanks.
Sent from my HTC One S using xda premium
Thank u for this sollution, i was really looking for it... i hope it saves some battery juice....
Sent from my MK16i using Tapatalk 2
Great app. who really needs the backlights anyway once you get a decent feel for the phone?
thanks for info.
will download and test later.
Sent from my HTC First
If you're rooted and don't want to have an app running for this, you can do the following:
Launch RootExplorer, go to "sys/class/leds/button-backlight" (NOT LCD-BACKLIGHT or any other) and long press "max_brightness." Open in Text Editor, change 255 to 0 and save.
emiquelet said:
If you're rooted and don't want to have an app running for this, you can do the following:
Launch RootExplorer, go to "sys/class/leds/button-backlight" (NOT LCD-BACKLIGHT or any other) and long press "max_brightness." Open in Text Editor, change 255 to 0 and save.
Click to expand...
Click to collapse
It work for me.
Thanks you so much.
Deleted.
Is it possible to disable screen using backlight ?
I've tried using a script doing it all, but seems that the screen on/off is powered by other methods ?
echo 0 > /sys/class/leds/spotlight/brightness
echo 0 > /sys/class/leds/spotlight/max_brightness
echo 0 > /sys/class/leds/red/brightness
echo 0 > /sys/class/leds/red/max_brightness
echo 0 > /sys/class/leds/blue/brightness
echo 0 > /sys/class/leds/blue/max_brightness
echo 0 > /sys/class/leds/green/brightness
echo 0 > /sys/class/leds/green/max_brightness
echo 0 > /sys/class/leds/lcd-backlight/brightness
echo 0 > /sys/class/leds/lcd-backlight/max_brightness
#echo 0 > /sys/class/backlight/lm3530/brightness
#echo 0 > /sys/class/backlight/lm3530/max_brightness
I'm Trying to find some way to disable screen as startup.
Thanks,
Ranchu
I used ES File Explorer for this....Its showing error while saving....what to do??
Related
Can all the keys on the lights to get some regulation to stay constantly on top on (always on) because they are hard to find in the dark?
So how do I get on the keypad lights always on?k
Yeah, I hate this too. The buttons dim out WAY too early during normal web browsing & I'm always searching for them if I'm using the Tab in a dimly lit room.
Im sure this would be easy to hack. I've seen other Android phones be able to apply patches that can regulate the time the soft keys stay lit.
this annoys me too specially when reading ebooks.. everytime i turn the page, the capacitive buttons lit up and its bright!
Did you guys check under display for a how long to keep buttons lit option. On the samsung epic there is an option under display for the menu, back, buttons timeout options maybe that will help. Sorry if I'm wrong
Sent from my SPH-D700 using XDA App
bryanfritz1 said:
Did you guys check under display for a how long to keep buttons lit option. On the samsung epic there is an option under display for the menu, back, buttons timeout options maybe that will help. Sorry if I'm wrong
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
nothing there...
bryanfritz1 said:
Did you guys check under display for a how long to keep buttons lit option. On the samsung epic there is an option under display for the menu, back, buttons timeout options maybe that will help. Sorry if I'm wrong
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yeah, there's only an option for screen timeout & that's it.
Did anyone find a solution to this ?
I have just got a Tab and there are a few niggles to sort out to decide if i am going to keep it or not.
Thanks for any replies.
Anyone ?
And I can thought I was the only one getting annoyed by that
Sent from my GT-P1000 using XDA App
I just drag my finger over the screen and they light up, easy solution
Hi,
Has anyone found a method of disabling those bl***y button lights. I purchased this device mainly for ebook reading at night but the lights popping up like search lights every time I turn a page is very annoying.
ok, you can touch the display to get buttons backlight back on, but that is still pretty annoying. Isn't there any way of controling buttons backlight individually?
One solution would be to recompile the lights library
Code with fix available here:
https://github.com/cmsgs/android_de...mmit/87f51dbe93d153990b14a0e000c0db36f84a0adc
Seems like only the Korean rom have this function of setting the duration of 4 button lights option.
Link- http://forum.xda-developers.com/showthread.php?t=938300
Sent from my GT-P1000 using Tapatalk
No solution to this yet?
Sent from my GT-P1000 using XDA App
same here
Would be nice if some kind of application ortweak wouldmake it possible to keep button light on idd. In the shade or dark its hard to see.
Yeah, I too wanna keep the LEDs (Home, Back, Send and End) on the HTC Fuze constantly on, or at least stay on longer than the few seconds as it does by default. Can't seem to find a solution, only similar requests...
~Des
this is an old issue which is default for gingerbread for samsung galaxy tab.
several solutions I know of
1.replacing the file which controls the lights-here(needs root). this is the one I am using but it is timed and everytime you touch the screen it goes on,I can live with that.
2. using overcome kratos
3. using buttonbacklight widget(from market)-with this one you will be able to set lights off or on.....also needs root.
Bit late but u could use some scripts to turn on/off backlights, root is needed.
Code for off script
chmod 644 /sys/devices/virtual/leds/button-backlight/brightness
echo 0 > /sys/devices/virtual/leds/button-backlight/brightness
chmod 444 /sys/devices/virtual/leds/button-backlight/brightness
Code for on script
chmod 644 /sys/devices/virtual/leds/button-backlight/brightness
echo 1 > /sys/devices/virtual/leds/button-backlight/brightness
chmod 444 /sys/devices/virtual/leds/button-backlight/brightness
Code for restore to stock script
chmod 644 /sys/devices/virtual/leds/button-backlight/brightness
Sent from my GT-P1000 using xda premium
&& Use TASKER to do a LED LIGHTS OUT &&
Biopsin: Thanks for the tip.
However, it is overwritten each wakup, so using TASKER I made it that each display on it executes as root "echo 0 > /sys/devices/virtual/leds/button-backlight/brightness" and it WORKS PERFECTLY! I never really needed the lights on the buttons, I know where they are ... super cool!
I was trying to find a way to completely disable all of the background stuff that runs with the andriod facebook app and couldn't find an elegant way of doing it. Greenify sort of works but the background process somehow always find a way to restart themselves.... With this you can simply launch a facebook tasker link task, tasker will enable or 'unfreeze' the facebook app. Then when your done with facebook, as soon as you close it, a task will run to automatically disable or 'freeze' it. I noticed after this my battery life definitely improved.
As this is actually my first post on xda, I can't post the links to the screenshots I took of the tasker screens If anyone wants I have it in an html page / word doc that shows step by step the tasker profile and 4 tasks. PM me.)
Requirements
-Tasker
-Root
-Secure Settings tasker plugin and Root item > Package State > enable
-If you cannot get secure settings to recognize root (whcih was the case for me) then you need to run the following (which I found on another post)
download a terminal emulator then run the commands below
Play store - Terminal Emulator for Android, Jack Palevich
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
1) Create Profile > Application > Facebook
2)Create a “Facebook start” task
TASK #1: 'Facebook start' > Launch app Facebook
3) Then on the “Facebook” profile click on the ‘facebook start’ and select Add Exit Task
Then choose the a task that you created called ‘Facebook disable’
TASK #2: 'Facebook disable' > Secure Settings plugin > Facebook app > disable
TASK #3: 'Facebook enable' (this is to be used as a generic way to enable facebook and also used in the TASK#4). > Secure Settings plugin > Facebook app > enabled
TASK #4: 'Facebook Launch' (this enables the facebook app then launches facebook).
>perform task 'facebook enable'
>Wait 5 seconds
>Flash 'launching facebook'
>Launch App > Facebook
For the Facebook Icon to show on this task #4, you can choose this by pressing on the bottom right of the task and application Icons
4) Then Create a Tasker Widget Shortcut (don’t use the native Facebook icon as it will disappear from your launcher when you disable the app then you will have to keep re-adding it to the screen…) and point it to Task #4 'facebook launch'
Place your tasker shortcut on your launch screen and you are good to go. Now when you launch it, it will enable facebook, then when you exit , it will disable it.
You can do this for virtually any app, but I found it most useful for Facebook as it drains the battery when its enabled
What about doze? Do I need this tasker profile if my Android use doze?
noorbertt said:
What about doze? Do I need this tasker profile if my Android use doze?
Click to expand...
Click to collapse
I have a Galaxy S5 and am on MarshMallow I find that even if doze is enabled, facebook always finds a way to run. It was constantly draining my battery and until I did this tasker thing my battery would run down quickly. I'd recommend downloading an app from the playstore called "OS Monitor" - it shows what apps are running and how much CPU they are consuming - you can set it to show in real time - similar to windows task manager
Which option do you use in secure settings. I am not able to find any app actions in mine.
iamronin said:
Which option do you use in secure settings. I am not able to find any app actions in mine.
Click to expand...
Click to collapse
Secure Settings tasker plugin and Root item > Package State > enable
-If you cannot get secure settings to recognize root (whcih was the case for me) then you need to run the following (which I found on another post)
download a terminal emulator then run the commands below
Play store - Terminal Emulator for Android, Jack Palevich
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If someone is interested in this feature but doesn't want to mount their system and break SafetyNet here is what I did. Instead of using Secure Settings I use a shell command. I've edited the original post:
drum200910 said:
Requirements
– Tasker
– Root
1) Create Profile > Application > Facebook
2) Create a “Facebook start” task
TASK #1: 'Facebook start' > Launch app Facebook
3) Then on the “Facebook” profile click on the ‘facebook start’ and select Add Exit Task
Then choose the a task that you created called ‘Facebook disable’
TASK #2: 'Facebook disable' > Code > Run Shell > Command "pm disable com.facebook.katana" and select "Use Root"
This only work with permissive SELinux, though. If you have enforcing SELinux you might have to add this command before the main one "setenforce 0" (also with root) and if you want to still pass SafetyNet after the main command run "setenforce 1" (also with root).
TASK #3: 'Facebook enable' (this is to be used as a generic way to enable facebook and also used in the TASK#4). > Code > Run Shell > Command "pm enable com.facebook.katana". Again with the other two.
TASK #4: 'Facebook Launch' (this enables the facebook app then launches facebook).
>perform task 'facebook enable'
>Wait 5 seconds
>Flash 'launching facebook'
>Launch App > Facebook
For the Facebook Icon to show on this task #4, you can choose this by pressing on the bottom right of the task and application Icons
4) Then Create a Tasker Widget Shortcut (don’t use the native Facebook icon as it will disappear from your launcher when you disable the app then you will have to keep re-adding it to the screen…) and point it to Task #4 'facebook launch'
Place your tasker shortcut on your launch screen and you are good to go. Now when you launch it, it will enable facebook, then when you exit , it will disable it.
You can do this for virtually any app, but I found it most useful for Facebook as it drains the battery when its enabled
Click to expand...
Click to collapse
Filip013 said:
If someone is interested in this feature but doesn't want to mount their system and break SafetyNet here is what I did. Instead of using Secure Settings I use a shell command. I've edited the original post:
Click to expand...
Click to collapse
In this part above: TASK #3: 'Facebook enable' (this is to be used as a generic way to enable facebook and also used in the TASK#4). > Code > Run Shell > Command "pm disable com.facebook.katana". Again with the other two.
should the above be "pm enable com.facebook.katana" ? I tried enable and it did work. Just checking...
saxainpdx said:
In this part above: TASK #3: 'Facebook enable' (this is to be used as a generic way to enable facebook and also used in the TASK#4). > Code > Run Shell > Command "pm disable com.facebook.katana". Again with the other two.
should the above be "pm enable com.facebook.katana" ? I tried enable and it did work. Just checking...
Click to expand...
Click to collapse
Thanks. That was a typo.
Let me give you a better and quick way to freezing/de-freezing a app whenever required:
Requisites:
1. Root
2. Titanium Backup
3. Nova Launcher or any other launcher
Steps:
After installing Titanium backup successfully go to Launcher and add widget of Titanium Backup with type as Action (There will be two widgets, Select the first one)
In the screen, tap on the action and select Freeze/Defrost/Launch an app (Scroll up then you will see)
Tap on Filter by and select the target application
Done
You widget will be created and whenever you tap on it a. If the app is frozen then it will get defrosted and get launched b. If its not frozen then it will get frozen
I am using this method since a year already for Facebook and Messenger apps
For those who have installed LineageOS on T5, you know that there is a bug with a text which is bit blurry. There is a fix for this, you go to Developper Option and disable HW overlays. But the small problem is that it doesn't stay after reboot, and each time you need to disable it again. I found in some old forums how this can be permanently fixed using Tasker. I tried, it works, and I want to share with you. You need to be rooted for that to work.
In Tasker, create new profile: Event -> System -Device Boot
Task : Script - Run shell
Shell command : service call SurfaceFlinger 1008 i32 1
Thick "Use Root" box
That's it, the HW overlays is now permanently disabled.
you made my whole month my dude
Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.
does this affect battery life
shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.
Tested now on my RN10-pro... works just fine! Thank you!
Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.
Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.
I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.
Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?
Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).
Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.
You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com
Can somebody help me with a task to turn off aod when face down or in pocket on a samsung s21 FE?
Thanks!
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
eeeemc said:
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
Click to expand...
Click to collapse
Sadly it doesn't work.
But thanks
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Mrawy said:
Sadly it doesn't work.
But thanks
Click to expand...
Click to collapse
eeeemc said:
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Click to expand...
Click to collapse
It doen't work, maybe I need to give tasker some permissions trough adb?
Mrawy said:
It doen't work, maybe I need to give tasker some permissions trough adb?
Click to expand...
Click to collapse
I'm not sure if extra permission is required as not in my case.
May be try below experimental task if it works so that it proofs tasker custom settings is available on your device :
custom settings > system > blue_light_filter > value 1
This turn on Samsung's reading mode and if you manually hit play button from within tasker after you create this blue light test task , then you check from the dropdown tilt to see if the blue light icon is on or not.
if it is on , means custom setting is availble on your device without extra permission.
if this is the case , use custom setting to use the 'FIND' button step-by-step go to AOD on/off menu and set it. ( hope you know custom setting has 'FIND' function to manually choose the require action in your case is to find the AOD )
On Huawei P30 Pro, to disable AOD make task like a photos in attachment.
To use this task You Need use ADB DEBUGGING and Tasker Permissions app or adb command. Read more:
https://tasker.joaoapps.com/userguide/en/help/ah_secure_setting_grant.html
I toggle my AOD on my Samsung device. It's just as the first reply said.
custom setting > system > aod_mode > value 0 to turn it off, and 1 to turn it on.
To test the adb setting on your device, just create a simple task that toggles AOD. EG when you are connected to wifi, set it off, or somethign else you can use to easily test.
If that works (which it should), then it's the sensor part that has the issue.