To disable the capacitive button lights on the Bionic, edit this file to be 0. It's originally at 255.
/sys/devices/platform/leds-cpcap-kpb/leds/button-backlight/brightness
Keep in mind if you use ES Text Editor it messes up the permissions. You'll have to set it back to rw-r--r--. (Evidently this is optional. It works fine without resetting the permissions)
Can anyone make a script that enables and disables this? Or a widget? I'm not a programmer, just an enthusiast. Also, there is a "maxbrightness" file in there that is r--r--r-- so I'd rather be modifying that one, but I am just happy this brightness file works for now, so I'm not going to mess with it.
Looks like it resets to 255 on boot. I guess I will figure out how to make scripts if nobody responds. It's way past my bed time now that I stumbled onto this.
Edit: To get it to stick (except for boot), after changing brightness to 0, I just changed the permissions on the brightness file to r--r--r-- so nothing can write to it. I wonder if I can get used to never having any backlights. It's not like the buttons move around. They're in the same position they've been in the last 3 months.
Edit: Tasker can run Terminal command lines, so I have made some homescreen shortcuts for shutting off and turning on the lights. For terminal commands, you type:
echo "0" > /sys/devices/platform/leds-cpcap-kpb/leds/button-backlight/brightness
and that writes a 0 to the file, shutting off the lights.
I'm finding it gets turned on by more than just rebooting. There are several events that turn the lights back on, so unless you want Tasker to run the script every 30 minutes or something, you can just make a shortcut to the task on your homescreen and just shut them off when they're annoying you.
Related
Hi folks,
Just wondering if one of the experts can tell me, in the Kaiser rom, what is the actual file that gets executed when you tap on the little padlock on the Today screen, which in turn locks the phone? Not sure if it's even an executable or not, but I'm trying to link an icon to the function in a new skin.
Thanks.
No one knows? I guess I'm not surprised being that I browsed pretty much the entire contents of the phone and didn't see anything.
Mike Channon? You are THE MAN with this stuff... any idea?
keylock.exe
Hidden under Windows Dir keylock.exe
The following command line parameters exist for the backend of Automatic Keylock, Keylock.exe:
/off
This command line switch shuts down Automatic Keylock completely without altering the settings. To enable it again, call Keylock.exe without parameters.
/toggle
This parameter toggles Automatic Keylock between on and off state.
/reload
If Keylock.exe is called with this parameter, the settings are reloaded from registry.
Kokkos
Alternate
Devicelock instead of keylock:
http://forum.xda-developers.com/showthread.php?t=305402
Kokkos
Thanks Kokkos!
I have tried searching for the answer to this so please do not ridicule me if i missed it!
Is there a way of stopping the screen from being so dim when i press the power button to wake up device if it is locked.
I always lock the device when i am not using it and will quite often press the power button quickly to turn off the display. When i come to use the phone etc i press the power button to get the screen back then press unlock at the bottom of the screen then the unlock half way up the screen, phone unlocked. BUT when the power button is pressed to turn the screen on and the phone is still locked the screen is so dim i cannot see it in bright daylight. Is there a way of making the screen brighter so i can unlock it?
David
simple answer YES!
The registry key here controls the backlight lock level:
HKCU\ControlPanel\Backlight\LockLevel
There REG_DWORD Key called LockLevel can be set between 0-10 (0=0%, 10=100% locklevel backlight brightness)
The system defaults this setting to 0, hence the dim lock display.
I have found however that the value does not stick after a soft reset/reboot, and goes back to default, so i have set a startup .lnk file that runs a reg script to set this value silently on boot for me.... you can do this yourself using the latest taskmanager 2.9 from here: http://www.dotfred.net/TaskMgr.htm (/silent command line parameter was only added in v2.9 so i can run a reg script without the prompts!)
I like to have a bright pin/unlock screen as i like to use the screen as a torch/light by just pressing the power button!!
Enjoy.
Thanks!!
Thanks for the answer to that. I too have been having the same problem, and it has bugged the hell out of me, especially on those bright summer days .
Thanks heaps for that!!!
Sorry for the delay, but many thanks for the answer! Damned annoying that was.
Regards
David
How do i make this .lnk file? What should it say? Where do i put it? etc etc. Sorry for the question but not done any of this before. The reg edit was easy enough but now i am lost.
Cheers
David
Locklevel startup value
_DrG_ said:
simple answer YES!
The registry key here controls the backlight lock level:
HKCU\ControlPanel\Backlight\LockLevel
There REG_DWORD Key called LockLevel can be set between 0-10 (0=0%, 10=100% locklevel backlight brightness)
The system defaults this setting to 0, hence the dim lock display.
I have found however that the value does not stick after a soft reset/reboot, and goes back to default, so i have set a startup .lnk file that runs a reg script to set this value silently on boot for me.... you can do this yourself using the latest taskmanager 2.9 from here: http://www.dotfred.net/TaskMgr.htm (/silent command line parameter was only added in v2.9 so i can run a reg script without the prompts!)
I like to have a bright pin/unlock screen as i like to use the screen as a torch/light by just pressing the power button!!
Enjoy.
Click to expand...
Click to collapse
I also would like to do this, but havent figured out how to create a command line with TaskMgr that will execute at startup - would you share how it is done?
Also, when I set locklevel to any number other than 1, no dimming occurs when I lock my Tilt. I experimented because I thought I'd like a little dimming but not as much as the default - but it seems like it's all or nothing.
I hate the way the Kaiser and/or WM6 insists on spoonfeeding some settings to us, no matter how much we would like to permanently alter them!
peanutome said:
How do i make this .lnk file? What should it say? Where do i put it? etc etc. Sorry for the question but not done any of this before. The reg edit was easy enough but now i am lost.
Cheers
David[/QUOTe
my thoughts exactly..more instructions for this guy too please
Click to expand...
Click to collapse
BUMP - Anyone know how and what to do to make this .lnk file and then how to use it?
David
strange thing. When I adjust this value it messes with my backlight timeout. I normally have this set to 30secs, i.e. the screen goes dimmer after 30 secs. When I adjust the lockout value as described it goes dim after 5-10 seconds. am I doing this right? I wasn't sure if I had adjusted the value correctly.
M
I have searched all over can someone tell me how to get the \silent to work I have taskmanager v2.9 spent the last 2 hours trying to get this to work please give a bother some help
I think the answer is here...well, not an answer but at least an app that claims to do what you're looking for.
This answer may be too basic, but have you tried changing the registry edit and then NOT doing a soft reset, but instead doing a full power off/on? Some registry entries WON'T stick with a soft-reset, but will with a power cycle. The power cycle gives the OS a heads up that it's being turned off and writes things more permanently...
pkley said:
This answer may be too basic, but have you tried changing the registry edit and then NOT doing a soft reset, but instead doing a full power off/on? Some registry entries WON'T stick with a soft-reset, but will with a power cycle. The power cycle gives the OS a heads up that it's being turned off and writes things more permanently...
Click to expand...
Click to collapse
I always power cycle after a reg change (It forces a registry write and a SR doesn't) but it doesn't matter...this reg change doesn't stick after a power cycle for some reason.
EDIT:
BTW, I loaded BrightLock and it works perfectly.
Excellent seems to do what i needed!!! Cheers
David
Fitipaldi1 said:
I think the answer is here...well, not an answer but at least an app that claims to do what you're looking for.
Click to expand...
Click to collapse
snowgum said:
strange thing. When I adjust this value it messes with my backlight timeout. I normally have this set to 30secs, i.e. the screen goes dimmer after 30 secs. When I adjust the lockout value as described it goes dim after 5-10 seconds. am I doing this right? I wasn't sure if I had adjusted the value correctly.
M
Click to expand...
Click to collapse
I am experiencing a similar issue. My normal backlight on battery power is set to 1 minute, but after installing brightlock, it keeps changing to 10 seconds. I really like what brightlock does for me, but not at the cost of dimming the screen when I am trying to read something. Is there a configuration I am missing?
I think I got rid of this annoying “dim” problem without .lnk file and scripting.
See my next post.
Is there a way of stopping the screen from being so dim when i press the power button
I think I got rid of this annoying “dim” problem without .lnk file and scripting.
What I did is the following:
1. Downloaded and installed Taskmanager 2.9 from: http://www.dotfred.net/TaskMgr.htm
2. Opened Taskmanager and went to Regedit
3. Deleted LockLevel folder from HKCU\ControlPanel\Backlight\LockLevel
4. Saved
5. Rebooted the phone.
After rebooting, system recreates LockLevel folder, however, “dim” problem is gone.
Unit still dims the screen, but pressing any key triggers the bright display.
Suggestion: Export registry and backup your device before playing with Regedit.
can some one please re-post brightlock? mediafire link seems to be done and this is doing me nutter
Any way to do this?
You could probably do this by editing your build.prop file, but make a backup first!
what edit in the build prop would work?
I can't say for sure, but if you feel like reading all of the lines, you probably could.
bump
I would like to see an answer, as well. I don't want to waste battery on illuminating these soft keys. Hopefully someone can figure out what file has the option to disable the lights
Do you have the Root Tools app? I think you can change it in there. I personally like my keyboard and buttons always on because the flickering makes my CDO go crazy and I'd rather always have a backlight when my screen is on than never have it.
redsox985 said:
Do you have the Root Tools app? I think you can change it in there. I personally like my keyboard and buttons always on because the flickering makes my CDO go crazy and I'd rather always have a backlight when my screen is on than never have it.
Click to expand...
Click to collapse
I tried root tools and wasn't able to turn the lights off. I have a privacy screen protector, so when the lights are off, the button area looks completely black, flowing well with the screen. I like the look because it makes the screen look bigger
Anyone have any other solutions, preferably a solution where I can go through root explorer and edit some file?
GoodLooks550 said:
I tried root tools and wasn't able to turn the lights off. I have a privacy screen protector, so when the lights are off, the button area looks completely black, flowing well with the screen. I like the look because it makes the screen look bigger
Anyone have any other solutions, preferably a solution where I can go through root explorer and edit some file?
Click to expand...
Click to collapse
Well, I sat down and read through build.prop line by line and don't think it's in there now. There's a free app in the market place that MAY work. It did for my keyboard backlight. Search something along the lines of "backlight switch", it has a green logo. I'll edit with its exact name when I get my Nand backup done with.
redsox985 said:
Well, I sat down and read through build.prop line by line and don't think it's in there now. There's a free app in the market place that MAY work. It did for my keyboard backlight. Search something along the lines of "backlight switch", it has a green logo. I'll edit with its exact name when I get my Nand backup done with.
Click to expand...
Click to collapse
After testing a couple of applications, I found AdjBrightness successful in turning off the lights. The lights stay off, even when the application is killed in task manager so no wasted ram to ensure the lights stay off
In the options menu, simply check off 'Lock off button light"
GoodLooks550 said:
After testing a couple of applications, I found AdjBrightness successful in turning off the lights. The lights stay off, even when the application is killed in task manager so no wasted ram to ensure the lights stay off
In the options menu, simply check off 'Lock off button light"
Click to expand...
Click to collapse
is there any way to find out what this app does to the phone so we can bypass the need to have it installed?,
Nice find on this app. Thanks!
slvrarrow said:
is there any way to find out what this app does to the phone so we can bypass the need to have it installed?,
Click to expand...
Click to collapse
This was the ultimate solution I wanted, as well. The same developer has an app called SensorsInfo, which tells all the output values of all the sensors (e.g. accelerometer, proximity sensors, and most importantly, light sensor). Maybe someone can find out how to alter the light sensor's function. Just a thought.
(I wish I could figure out myself, but the D3 is my first android phone, and before that, I had a windows mobile 6 phone. Hoping to learn more and more about Android as time goes on )
After a few days, I realized when restarting the phone, the lights turn back on. They turn back off when the program is opened again. This is a pain, so I hope someone can get a better solution
echo 0 > /sys/class/leds/button-backlight/brightness turns it off. But when the screen turns off it reverts the value back to 255 or 0, depending on the sensor. The value can't be changed if AdjBrightness' options are set, but it is not a service. No clue how it does it.
Hello. I have a problem: I installed the newest The FroyoMOD. Now, when my phone is in horizontal position button "volume up" turns volume... down. In vertical position everything works fine.
I thought, that this might be useful - I switched in file qwerty.kl volume down button with search button, but problem has performed before this.
I did 3xWIPE - It didn't help.
If you find any mistakes in my post - I'm really sorry. English is not my native language.
In horizontal mode the vol.up and down switches. This is normal.
Thank you for your reply, but in horizontal mode Volume Up button turns volume down, Volume Down button turns volume down too so in this mode I can't turn volume up or zoom in camera mode.
As FroyoMOD was based on CM6 for Milestone, I guess this behaviour is controlled by the ro.config.volume_keys_rotation property that I introduced in the past.
See http://android.doshaska.net/cm6prop
You can change it if you edit the /system/build.prop file and set the property value to 0.
(In more recent CM7/CM9/CM10 roms, I've changed it to use persistent property instead of read-only property - persist.sys.volbtn_orient_swap. So in newer roms it's determined by what the user has set in /data/property. So in case of CM7/9/10, what is in build.prop file is just the default value, overridden by the user selected value. In the case of CM7, the property value can be set in Settings>CyanogenMod>Input>Swap volume buttons in landscape. In CM9/10, the corresponding GUI for this option has not been implemented yet - setprop on command line can be used there).
It's interesting. Did you tried any other rom? I recommend FuFu's Fast and Light if you'd like to stick to Froyo or any of kabaldan's CM.
If it persists in another rom, the chances are great it is a hardware failure.
Kabaldan has the proper answer.
Thank you guys, especcialy for you @kabaldan, I set "ro.config.volume_keys_rotation=1" to 0, rebooted phone and everything looks fine. Again, thank you so much
I've recently figured out how to use the run shell in Tasker, as well as the input tap command, add variable, and goto a specific line if variable condition is met. I've noticed that doing this simple script results in a once-per-second "tap" input that I'm looking to repeat. I was wondering if there was a way to speed up the inputs (5-10 times per second or something like that).
Thanks!
LifeAsADroid said:
I've recently figured out how to use the run shell in Tasker, as well as the input tap command, add variable, and goto a specific line if variable condition is met. I've noticed that doing this simple script results in a once-per-second "tap" input that I'm looking to repeat. I was wondering if there was a way to speed up the inputs (5-10 times per second or something like that).
Thanks!
Click to expand...
Click to collapse
If the taps fully occur before or after the script, you can just use wait 1000/5 or 1000/6 and then input the tap
If they as during the script, I'm not sure how to achieve it.
alienyd said:
If the taps fully occur before or after the script, you can just use wait 1000/5 or 1000/6 and then input the tap
If they as during the script, I'm not sure how to achieve it.
Click to expand...
Click to collapse
The taps are during the script. A general idea of the script:
- open app
- wait
- tap
- add to variable counter
- go to step 3 if counter below a certain value
Running this generates one tap per second. I'd like to speed it up if possible.