The light coming from the 4 soft keys and the two physical home and end buttons is bugging the hell out of me. They hurt my eyes, especially when it's dark.
Is there some kind of script I can run to permanently turn them off? Preferably a zip file I can just flash in the recovery or something.
Interesting that you want them turned off.
I want to know how to turn ON the soft key lights, because sometimes I press the wrong key (as I came from a Droid-X).
Easy, if your rooted download gscript and run one of these scripts one for of is lightsout.sh one for one is lightson.sh
push them to your sdcard/gscript folder then load them in gscript and run from gscript
there is allso trackballon and trackballoff if you want to turn your trackball on or off for some reason. I will have the green and orange led up later
NOTE: if there is an error like the lights turn off after a bit then edit the gscript lightson.sh and remove the line that says sleep1.
NOTE#2: this may cause soft reboots were your phone will run the boot animation and restart the xserver of android shell blah blah. nothing to worry about doesnt hurt your phone
androidifyme said:
Easy, if your rooted download gscript and run one of these scripts one for of is lightsout.sh one for one is lightson.sh
push them to your sdcard/gscript folder then load them in gscript and run from gscript
there is allso trackballon and trackballoff if you want to turn your trackball on or off for some reason. I will have the green and orange led up later
NOTE: if there is an error like the lights turn off after a bit then edit the gscript lightson.sh and remove the line that says sleep1.
NOTE#2: this may cause soft reboots were your phone will run the boot animation and restart the xserver of android shell blah blah. nothing to worry about doesnt hurt your phone
Click to expand...
Click to collapse
First of all, thank you.
But I ran into some issues/have questions:
1) The lightsoff script works after I run it in gscript, but when I turn the screen off and back on again, the soft key lights turn right back on.
2) By the green and orange LEDs, do you mean the notification LED? Because if so, it's not necessary; I actually need those ones.
3) The green phone and red end/power lights still stay on.
4) I don't see a line that say "sleep1" in the lightson script.
If you are running a CyanogenMod ROM, there is a control for the automatic backlight that also lets you set the light levels fot when the softkey backlights go on (which you can set to 0 to never come on.) I don't have a CM ROM installed at the moment, but it's in settings->CyanogenMod ROM settings somewhere. if you cannot find it, I can dig around.
[edit] I think it's in user interface->automatic backlight. That's where it was in CM6 (Froyo).
doogald said:
If you are running a CyanogenMod ROM, there is a control for the automatic backlight that also lets you set the light levels fot when the softkey backlights go on (which you can set to 0 to never come on.) I don't have a CM ROM installed at the moment, but it's in settings->CyanogenMod ROM settings somewhere. if you cannot find it, I can dig around.
[edit] I think it's in user interface->automatic backlight. That's where it was in CM6 (Froyo).
Click to expand...
Click to collapse
Thank you! I found it after digging around the settings a bit.
on Arc S
while button-backlights are off value of
/sys/class/leds/button-backlight/brightness is 0
while its 0 change permissions to read only
they are disabled
I can also limit current to 150 in max_current which limits current and lights are dimmed if you want it running but not at max brightness...
added
echo 0 > /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
chmod 444 /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
Click to expand...
Click to collapse
to /system/etc/hw_config.sh
now they are set off on boot
another more hardcore approach is to unplug the leds. remove the back cover, sdcard, and battery. then use a t5 or t6 torx screwdriver to remove the four screws. remove the back casing, starting at the top, near the headphones. peel off the copper plate held on by 4 pieces of tape, but dont bend the copper. then in the middle of the circut board there will we a yellow film. peel it back to reveal a hole in the board where a long and skinny brown wire plugs in. unplug it, it just lifts straight off. follow these steps in reverse, and the softlights will be disabled.
WARNING: this WILL irrevocably void your warranty, although seeing how old the model is, i doubt it has one
Hey guys, can I use any of your solutions with my samsung galaxy s plus ?
Diablob555 said:
Hey guys, can I use any of your solutions with my samsung galaxy s plus ?
Click to expand...
Click to collapse
I hardly know anything about this aspect of the Eris (my phone), so I really can't say, but I would doubt it being such different hardware and of course different manufacturer.
Related
Hello,
Anyone have an idea of how to simply turn off LED button back lights?
It seems it could be done as there is already at least one app that uses them for notification.
Here is what I am trying to do:
I've downloaded a desktop alarm clock app that turns the screen back light WAY down so it is not disruptive in a completely dark room while sleeping. But, the buttons remain illuminated.
Basically 8 want to use tasker to launch those clock and turn off the button back lights if the phone is charging and the time is after a certain hour.
I am thinking I could fire off a script with tasked to do thwarting back lights portion of this as well, but I don't even know where to begin.
Any ideas? Thanks!
Sent from my Dell Streak using XDA App
I'm rooted, and use an app called AdjBrightness. Works wonders, and also via menu, you can totally turn off the LED lights.
Hope that helps.
Cool, I will check it out. Ideally I would like to do it automatically, without having to open another app, but this tells me it ostensibly at least doable.
Thanks!
Sent from my Dell Streak using XDA App
If you want the code, just do this from adb or from your phone's terminal.
echo "0" > /sys/class/leds/button-backlight/brightness
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Spleisher said:
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You could always leave your computer on overnight and make a macro that executes the adb command to dim the leds and then executes another that makes them bright again at a certain time.
There must be something similar you can do on the phone though.
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Spleisher said:
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Click to expand...
Click to collapse
Good job, sounds pretty cool
I'm sure many people will find this useful!
Does the louder volume app work with the streak?
SeanH said:
Does the louder volume app work with the streak?
Click to expand...
Click to collapse
No i'm afraid it doesn't. Also, send me a pm next time rather than ask in someone else's thread
I did turne off button's back-light by adjusting the context of "/sys/class/leds/button-backlight/brightness" file from 255 to 0, it works great, but it gets back to normal after phone restart, I even went to properties of the file and removed all the "write" rights, but it won't give in.
Hi all,
Im rooted and running viper rom, with netarchy.
the bottom lights (home, menu, back, search) never turn off, even when i press the power button and put the phone to sleep. The lights dim but never turn off. I have tried led hack, and screen filter with no luck. I tried going back to my nandroid backup of stock and it still the same. Is this a hardware problem? obviously a battery pull leads to the lights going out but as soon as i reboot its the same problem. Anyone have any ideas?
thanks again
heatbball said:
Hi all,
Im rooted and running viper rom, with netarchy.
the bottom lights (home, menu, back, search) never turn off, even when i press the power button and put the phone to sleep. The lights dim but never turn off. I have tried led hack, and screen filter with no luck. I tried going back to my nandroid backup of stock and it still the same. Is this a hardware problem? obviously a battery pull leads to the lights going out but as soon as i reboot its the same problem. Anyone have any ideas?
thanks again
Click to expand...
Click to collapse
haven't heard of anybody having this issue and i'm also on netarchy's kernel with stock rom and haven't experienced it.
i think you're on the right path, load up the stock rom and stock kernel, if you still experience the issue, it would appear to be more hardware related and i'd take it back to sprint.
if you don't experience the issue then you know it was probably triggered somewhere along the lines of customization. i'd customize again step by step checking along the way.
if you're technically inclined and feel adventurous, i'm pretty sure the backlight leds can be controlled thru the sysfs space and adb shell.
/sys/class/leds/button-backlight
all the control files are in there and you can experiment echo'n values to see if it turns them on/off and/or controls the brightness ...
best of luck!
Look in the market for an app called covedesign. It will allow you to turn off the bottom lights. Hope this helps.
Locked & Loaded
"" Shooter on Deck""
Everytime i try to edit the button backligjt file the file is empty with nothing in it
R.I.P. HD2 hello EVO 3D!!
laie1472 said:
Look in the market for an app called covedesign. It will allow you to turn off the bottom lights. Hope this helps.
Locked & Loaded
"" Shooter on Deck""
Click to expand...
Click to collapse
Thank you! Been looking for something to turn off the button lights off!
joeykrim said:
if you're technically inclined and feel adventurous, i'm pretty sure the backlight leds can be controlled thru the sysfs space and adb shell.
/sys/class/leds/button-backlight
all the control files are in there and you can experiment echo'n values to see if it turns them on/off and/or controls the brightness ...
!
Click to expand...
Click to collapse
jyazzie110 said:
Everytime i try to edit the button backligjt file the file is empty with nothing in it
R.I.P. HD2 hello EVO 3D!!
Click to expand...
Click to collapse
you don't "edit" the files in a text editor ... you echo values to them.
example: echo 50 > brightness
dumasauce said:
Thank you! Been looking for something to turn off the button lights off!
Click to expand...
Click to collapse
No prob hopefully it helps you out
Locked & Loaded
"" Shooter on Deck""
anyway you can provide me some step by step to turn them off via that method? (i am a relative noob)
thanks again
Is there any mod that can disable notification LED and sensitive buttons LEDs forever? I know there is a few apps that can do that. But I don't wanna use apps, I noticed some custom ROMs ship with that option. I'm using stock ROM. Sorry for creating a new thread for that. But I can't find a solution for EVO 3D that would work for me. Thanks
I'm sure there will be something released like that. Nothing to my knowledge as of yet. Just something to dim the capacitive buttons.
And this goes in the Q&A section. I hope you have thick skin. Pm a mod to have it moved
Sent from the CM powered 3d
It wouldn't be too hard to do. You can see what needs changed in the kernel in my thread here. I have a version that has no capacitive LEDs and the notification LED will shut off after 5 mins or so.
plotnick said:
Is there any mod that can disable notification LED and sensitive buttons LEDs forever? I know there is a few apps that can do that. But I don't wanna use apps, I noticed some custom ROMs ship with that option. I'm using stock ROM. Sorry for creating a new thread for that. But I can't find a solution for EVO 3D that would work for me. Thanks
Click to expand...
Click to collapse
well... not sure about the blinking LED's... but let me ask you this: how will you know when your phone is charged?
and as for the soft keys, if you have root explorer, navigate to...
/sys/devices/platform/leds-pm8058/leds/button backlight/currents
when you select the button backlight directory, the "currents" is a file. long press on this file until a little menu pops up, select "open in text editor" the value there should be default 20. change it to zero, then hit your menu soft key and select "save and exit"
your leds are now off.
EDIT** and before you do all of that, you will need to select the little grey box at the top of root explorer to mount the system files as "RW", otherwise you wont be able to edit the currents file (as it will be read only)
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
it worked but only until the next restart. It restores default value everytime... Why?
plotnick said:
it worked but only until the next restart. It restores default value everytime... Why?
Click to expand...
Click to collapse
because the LED is controlled by the kernel... so, although you can manually fix it for a moment to the value you want, every time the phone boots, the phone resets the value.
the only way to make it permanent is to have a kernel with disabled LEDs
plotnick said:
it worked but only until the next restart. It restores default value everytime... Why?
Click to expand...
Click to collapse
If you just don't want the bottom buttons to light up, use the kernel I linked in my earlier post (assuming you are using a 2.3.4 ROM). If you're still using a 2.3.3 ROM, you can find a kernel call nolights made by joe85 (which is where I found the changes to make in the kernel for 2.3.4).
Yay! Now i will finally be able to sleep at night!
FXP045 released, http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
Current Issues (FXP045) and unofficial fixes
Hardware keyboard layout scrambled - Old keyboard file is no longer in this ROM but appearently just pasting the old stock file (attached) to /system/usr/keychars/ fixes the layout. The included keyboard changer app force closes.
LEDs under soft keys Return and Menu - Replace /system/etc/hw_config.sh with the attached file.
Screen flicker upon turning on - New issue in fxp045.
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
xutienan9520 said:
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
Click to expand...
Click to collapse
I believe these fixes will work on Ray but you should find the stock values from Ray ROM because there probably are some differences.
Basically, only one issue you're having can potentially be fixed using SK17i fixes and that is max brightness by applying the fix for screen flicker. If you can't get a hold of Ray's stock values, try SK17's stock ones, but do a backup in recovery just in case.
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
xutienan9520 said:
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
Click to expand...
Click to collapse
i'm editting these files on the phone. copy the file to sdcard to edit it, with any kind of text editor. i use edit function of Total Commander. then i copy over the original file in system with Root Explorer. backup original file to sdcard just in case.
dont know about Mac much, sorry.
root explorer is a paid app but i think ES file explorer has the required functionality
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
xutienan9520 said:
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
Click to expand...
Click to collapse
oh, i messed up the links. will be fixed in a moment =)
Per someones suggestion I've added modified files and instructions on how to replace the original CM ones.
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Thank you good Sir! Testing it later!
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Amazing job! I'm gonna test it out now in a super dark place to see if i can check whether it stays on when closed. =)
I'll be updating original post with results and updated files in a bit.
Edit: Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Nice to see process.
Now i need to find the button light for RAY
sulkie said:
Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Click to expand...
Click to collapse
I thought that
Okay, there is a binary called slidercounter that or something similar sets a system var. If you take your dev Tools app and look unter Configuration there it is mentioned:
hardKeyboardHidden=2 <- if closed
hardKeyboardHidden=1 <- if opened
We now just have to find out where it occurs and if not we make a background script that ech0 x (100) or 0 into the node depending on the state.
But there must be a system process watching this we could use.
Don't hide, I'll find you anyway
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
xutienan9520 said:
Nice to see process.
Now i need to find the button light for RAY
Click to expand...
Click to collapse
did you look, if in ray the nodes under /sys are similar to the pro mini?
you can test using adb shell or terminal app cat'ing the node to see what's in it and echo'ing a number to see what happens.
You meant progress, didn't you
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
PoedelPCS said:
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
Click to expand...
Click to collapse
not the most elegant solution but it'll do until the fix is in =)
good job though
If I had more time I would have searched where the system keeps the var keyboardHiddenState or how it was called and build a condition of if it's open and not bright enough to switch in on/off
But how I understood fxp the fact about the light seems to be enough to get this working ..I hope so
new issue:
km launcher disturbes camera module.
I use the KM Launcher to determine which keyboard to use in which state.
Portrait: swype
Landscape: thumb keyboard
Keyboard open: hardware keyboard
This is a very cool application that worked perfectly on my rooted stock. If it is active the cam works in the cam app, but not in many other apps that use the cam, e.g. barcoo barcode scanner. I have to disable KM Launcher before using these apps. Hope it'll be fixed automatically in the next release.
I just cannot guess why that happens.
Hey guys I still have the problem with the over sensitive lcd backlight, whenever I'm in a brightly lit room the backlight starts going crazy and sometimes goes so dark I can't see the screen, it then goes super bright.
It repeats this several times a day
I've tries the fix in this thread but it doesn't work
Could someone attach the fix to this thread? As I've tried the the fix using terminal emulator
Thanks
EDIT: it started doing this while I was writing this
Sulkie did append the script to the first post of the thread. Did you test it?
send from a fruit called mango using xda app.
I did it before but it didn't work, I found the reason it didn't work was because I didnr change the permissions.
Sorry I got confused
---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------
Its still going crazy, I followed the instructions properly though,
When I get home ill upload a video of it happening
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Having the same problem. Waiting to see others replies.
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages. Because if you put the phone in your pocket with the screen towards you body then it could be unlocking it when you get a text and the skin being close is keeping it awake. Specially if you have the glove feature turned on.
Sent from my SCH-I545 using Tapatalk 4 Beta
nativi said:
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages.
Click to expand...
Click to collapse
Good idea, but (heh) maybe I don't have enough friends but I don't get that many text messages. This happens frequently enough that I've spent a lot of time trying to figure out if some notification did something to wake up the screen, and most of the time I can find no reason for it to light up, which is why I suspect a button mash. (I also do not have the "extra sensitivity for gloved hands" option enabled.)
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Sent from my SAMSUNG-SGH-I337 using xda premium
ktetreault14 said:
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Click to expand...
Click to collapse
A reasonable suggestion. Might be the excuse I need to finally learn how to use Tasker. Wonder if I could get in a situation where I can't get my phone to wake up in a dark room, though....
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
oilfighter said:
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
Click to expand...
Click to collapse
I think this is the answer. I just got an Otterbox Defender and there's no way the buttons will get mashed in my pocket now. If the screen comes on again, I'll know there's something else causing it.
MysticCobra said:
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Click to expand...
Click to collapse
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
MysticCobra said:
Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen...
Click to expand...
Click to collapse
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
jbel25nyy said:
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
Click to expand...
Click to collapse
Great idea. That's why I posted about my Otterbox Defender in the reply right above yours.
Capp5050 said:
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
Click to expand...
Click to collapse
Good thoughts, but not exactly what I was looking for. These features might cause the screen to stay on once it awoke, but I was actually trying to prevent the screen from waking up in the first place.
I had the same thing happening to me until I put a case on the phone. I just have a hard silicone case, but the lip on the front it just enough to keep the home button from being pressed in my pocket.
I had a similar thing happening several times each day,except I would take my phone out to see that the camera was open. I figured out that it was because I had set a voice command to open the camera from the lock screen. I got rid of the command and it hasn't again
My problem is due to the intermittent wifi connection. My phone screen wakes up every time I get reconnected to the wifi network. It is so annoying.
Chris000001 said:
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
Click to expand...
Click to collapse
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Capp5050 said:
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Click to expand...
Click to collapse
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Capp5050 said:
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Click to expand...
Click to collapse
Im on a Verizon Note 3. I did as you described but it did not work. Im thinking it didnt because Root Explorer made a backup file with the non altered txt. Should I delete it to get it to work?