Is there a kernel that allows the capacitive key backlights to be turned on at all times that the screen is on? I'm using ElementalX and I can't see anything in the settings.
I know there's an app on Play that does this but it needs to be re-enabled after every reboot.
appro77 said:
Is there a kernel that allows the capacitive key backlights to be turned on at all times that the screen is on? I'm using ElementalX and I can't see anything in the settings.
I know there's an app on Play that does this but it needs to be re-enabled after every reboot.
Click to expand...
Click to collapse
There's a setting under "Buttons" in the settings. Disable the toggle titled "Backlight". I've never had mine turn back on after I've toggled that off.
reffu said:
There's a setting under "Buttons" in the settings. Disable the toggle titled "Backlight". I've never had mine turn back on after I've toggled that off.
Click to expand...
Click to collapse
The thing is that I want them on all the time..... not off all the time.
appro77 said:
The thing is that I want them on all the time..... not off all the time.
Click to expand...
Click to collapse
Whoops, misread that, my bad. I'm not sure how to enable them all the time, maybe see if you can create a tasker profile for the app that needs to be enabled on boot.
reffu said:
Whoops, misread that, my bad. I'm not sure how to enable them all the time, maybe see if you can create a tasker profile for the app that needs to be enabled on boot.
Click to expand...
Click to collapse
Yes, that might work.
You can try Xposed + Gravitybox, but if you're willing to go that route I'd suggest running a custom ROM, because all of them have that option
appro77 said:
Is there a kernel that allows the capacitive key backlights to be turned on at all times that the screen is on? I'm using ElementalX and I can't see anything in the settings.
I know there's an app on Play that does this but it needs to be re-enabled after every reboot.
Click to expand...
Click to collapse
You may try with EX Kernel manager, setting brightness on sys/class/leds/button-backlight
I tried quickly, setting to 255 light them up and short time after screen goes off they are lightning off too, when screen goes on they are lightning up again.
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Sinaptik said:
You may try with EX Kernel manager, setting brightness on sys/class/leds/button-backlight
I tried quickly, setting to 255 light them up and short time after screen goes off they are lightning off too, when screen goes on they are lightning up again.
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Click to expand...
Click to collapse
I don't think that I'm doing this correctly. Do you mean in Tools/User Settings, then add a new setting so that I end up with " sys/class/leds/button-backlight/255" on the top line? The bottom line shows "NA".
Edit: doh.... I finally worked it out. Thanks heaps. This was exactly what I was looking for.
Mackay - how can You fix this problem?
appro77 said:
I don't think that I'm doing this correctly. Do you mean in Tools/User Settings, then add a new setting so that I end up with " sys/class/leds/button-backlight/255" on the top line? The bottom line shows "NA".
Edit: doh.... I finally worked it out. Thanks heaps. This was exactly what I was looking for.
Click to expand...
Click to collapse
How did you get this to work? I can create a sys/class/leds/button-backlight by typing it directly into the user settings but then I can't change its value (stays na). Or I can follow the path to sys/class/leds/button-backlight but then I cannot select it.
Related
Flashing this will enable navigation bar, and disable capacitive touch buttons on Nexus S.
Make sure to set the Backlight Dimmer delay to 0 using the NSTools, so the capacitive touch buttons don't light up.
If you are using the navigation bar, I recommend setting the LCD density to 200 or 190. Edit it with Rom toolbox, or
navigate to /system/build.prop/ro.sf.lcd_density=200 edit it with text editor and reboot.
Always do a backup before flashing. It should work for any JB rom.
To disable navigation bar, reflash the rom, restore the backup or flash disable nav bars.
You are doing this at your own risk.
Its based on Brainmaster's tweaks for android, all thanks goes to him.
Added files, they set dpi to 190 or 200 or disable Nav bars.
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
You get these three buttons on bottom of your screen.
http://cdn3.digitaltrends.com/wp-co.../samsung-galaxy-nexus-review-home-buttons.jpg
Or you can just add
qemu.hw.mainkeys=0
To your build.prop and reboot. It works with every ROM I think. To disable, just set it back to =1.
Sent from my Nexus S using xda premium
But that won't disable the capacitive buttons
Sent from my Nexus S using xda app-developers app
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
tehkraft said:
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
Click to expand...
Click to collapse
First time I went from 240 to 200, I wiped googleplay, everything else worked okay, as far as I remember.
If you get FC's wipe that app.
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
apatal said:
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
Click to expand...
Click to collapse
They are disabled...
Serris said:
They are disabled...
Click to expand...
Click to collapse
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
great! this is working just great. really thanks! but i don't see any problem by leaving screen density to 240 though. been opened all apps installed on my ns
quick edit: i am using CM 10 nightly
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
Yes you can see the three dots in the navigation bar, and in aplications
Serris said:
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
Click to expand...
Click to collapse
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
BenHeng said:
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
So all you have to do, is disable BLN, and put below code(script) in init.d?
Code:
echo 1 > /sys/devices/virtual/misc/backlightdimmer/enabled
echo 0 > /sys/devices/virtual/misc/backlightdimmer/delay
Works for me at least
Sent from my Nexus S using xda premium
Tried the mod last night and it works! Unfortunately, my fingers are already too big for the default PDI, and reducing it to 200 won't really help me very much. Thanks for sharing this anyway. I'm sure some users have been looking for this.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
in order to turn off capacitive buttons follow these:
1. using root browser lit go to system.
2.then "usr" then " keylayout"
3. open sec_touchscree.kl > open as > text file > rb text editor
4. insert "#" in front of lines u want to make them stop working.
like
#key 158 BACK virtual
will make back button stop working.
Hello,
My S4s (i9500) screen keeps coming on when it reaches full charge, with a notification to unplug my charger. This wakes me up in the middle of the night, I'd like the phone to remain face up during the night...is there any way to stop this from happening?
turn your phone face down?
Sent from my GT-I9505 using Tapatalk 2
Thanks, need an answer to my actual question though, about how to disable the screen turning on when this notification happens.
ekko84 said:
Thanks, need an answer to my actual question though, about how to disable the screen turning on when this notification happens.
Click to expand...
Click to collapse
You'll have to wait for a mod. There is no stock way to do that.
settings<more<developer options<stay awake. un-check it
its_dale said:
settings<more<developer options<stay awake. un-check it
Click to expand...
Click to collapse
I don't have the developer options menu option in my settings...how do I get it?
ekko84 said:
I don't have the developer options menu option in my settings...how do I get it?
Click to expand...
Click to collapse
1.Head into the Settings menu. Samsung's done things a little differently and changed the way the settings menu looks, so you'll need to hit the "More" tab, and then get into the Software information.
2.Look for "About device" at the bottom. Tap it.
3.Hop on down to the build number, and tap it seven times. One. Two. Three. Four. Five. Six. You'll get a little prompt saying you're about to unlock the developer settings. Hit that button one final time -- seven! -- and they're unlocked.
Now you've got developer settings on the Galaxy S4.
its_dale said:
settings<more<developer options<stay awake. un-check it
Click to expand...
Click to collapse
Hmm this is a pretty good workaround, the screen still comes on but turns off on it's own and pretty quick. Thank you.
Guess I'll have to wait for a mod for the screen not to come on at all or to disable the beyond useless notification altogether.
If you have root, grab es file manager or root explorer or something and go to system/media/ui/ and delete whatever sounds you want deleted. Make sure to back them up if you want them back.
Sent from my SGH-I337M using xda app-developers app
I don't use it very often but I do like one handed operation. Today I realized that it wasn't working so I started undoing all the mods/setup I've been working on. Turns out it was lightflow. I can disable it in accessibility options and one hand operation immediately starts working.
Are there any other decent led control apps to try?
Thought I'd post here to hopefully save anyone else the trouble if they run into the same problem.
Sent from my Nexus 7 using Tapatalk 2
It seems like having anything enabled under Accessibility kills one-handed mode.
But Light Flow is working for me without the Accessibility setting. There's a new setting called Notification Access in the Security section.
Try enabling Light Flow there and see if it works. As I said, mine is working that way, but I'm also rooted, so maybe that has something to do with it...
Yeah it was enabled there too. Maybe there's just something wrong with mine because my wife just informed me that hers is working find and all she did was install it and forget about it. I had to enable options I've never used before like the one to make the led flash even when the screen is on, in order to get or to do anything at all.
I'm rooted too.
Sent from my SM-N900V using Tapatalk
dclutter1 said:
Yeah it was enabled there too. Maybe there's just something wrong with mine because my wife just informed me that hers is working find and all she did was install it and forget about it. I had to enable options I've never used before like the one to make the led flash even when the screen is on, in order to get or to do anything at all.
I'm rooted too.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Make sure that you have the LED settings under 'Settings' > 'Display' to have "Charging" and "Notifications" checked along with the checkbox in 'Security' > 'Notification Access'.
bd177 said:
Make sure that you have the LED settings under 'Settings' > 'Display' to have "Charging" and "Notifications" checked along with the checkbox in 'Security' > 'Notification Access'.
Click to expand...
Click to collapse
Lol, looks like that was my problem. For some reason I thought they all needed to be turned off so I did that initially and didn't even think to revisit it.
Thanks.
So we don't need to enable it in accessibility? Cuz that ruins most features. Makes you disable them.
Sent from my SM-N900V using Tapatalk 2
imablackhat said:
So we don't need to enable it in accessibility? Cuz that ruins most features. Makes you disable them.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
Mine is currently disabled in Accessibility and enabled in Security -> Notification Access. In Display -> LED indicator, I have Charging, and Notifications checked.
Working like a charm.
Works good this way with or without root. Just installed.opened.enabled the notification access. And use. Doesn't need enabled in accessibility.
Sent from my SM-N900V using Tapatalk 2
dclutter1 said:
Lol, looks like that was my problem. For some reason I thought they all needed to be turned off so I did that initially and didn't even think to revisit it.
Thanks.
Click to expand...
Click to collapse
In my S3 they had to be disabled in stock settings to work. In this they need to be enabled in stock settings for it to work. I know lightflow told me to disable it in stock settings on the S3.
Sent from my GlaDos Baked Potato
FWIW, I FOUGHT WITH THIS FOR A WEEK AND GOT NO WHERE. THE TASKER PROFILE LISTED IN THE REDDIT THREAD BELOW WORKS GREAT ON MY ROOTED PHONE. ALSO, LIGHTFLOW WORKED ON MY ROOTED PHONE. SO I AM JUST GOING TO ASSUME THIS REQUIRES ROOT
So, i have been searching and reading and asking around and I STILL cannot get the power button LED to light up with notifications.
I have lightflow installed
I have the notification and accessability settings turned on for the app
I have back button led 1 and 2 turned on
I have them turned to "always" on for notifications (I dont expect it to pulse)
I have the brightness set at 255 (But i have tried all other numbers in between)
I am NOT rooted
I am on stock 4.4.2
all other LED notifications seem to be working just fine and are the colors/speeds I set them to.
anyone able to get it working? not sure what else I can try to get it working.
if you have it working on stock rooted 4.4.2 let me know what options you have checked and unchecked in the "settings" page.
guess I'm the only one with this problem eh? lol
I didn't think it did light up. Only time mine does is when unlocking the screen.
Sent from my LG-D802
turdbogls said:
guess I'm the only one with this problem eh? lol
Click to expand...
Click to collapse
Haha, on AOSP ROMs I used tasker to run a script that changed the values in the file that controlled the 2 back LEDs to 255 when I got a notification. Then it cleared the file, and so on until I turned the screen on.
I don't remember it exactly, and I'm pretty sure it would need root.
treebill said:
I didn't think it did light up. Only time mine does is when unlocking the screen.
Sent from my LG-D802
Click to expand...
Click to collapse
by default it only works for a couple apps. others have had success with the latest lightflow app, but I haven't
bleached45 said:
Haha, on AOSP ROMs I used tasker to run a script that changed the values in the file that controlled the 2 back LEDs to 255 when I got a notification. Then it cleared the file, and so on until I turned the screen on.
I don't remember it exactly, and I'm pretty sure it would need root.
Click to expand...
Click to collapse
interesting, I poked around for a bit in tasker and didn't see anything in there for the back buttons. if you happen to come across this, or remember it, please let me know.
edit: i found the profile on Reddit to do this. going to give it a try in a little bit
Oh, please link me the reddit profile. It is probably better than mine. Haha.
Edit: Found my profile. I set it to trigger at a notification event. Works for me. (Remove the .txt at the end if you want to load it into tasker and look at it).
bleached45 said:
Oh, please link me the reddit profile. It is probably better than mine. Haha.
Edit: Found my profile. I set it to trigger at a notification event. Works for me. (Remove the .txt at the end if you want to load it into tasker and look at it).
Click to expand...
Click to collapse
here is the reddit thread. looks like it requires Root so I didn't even try it.
http://www.reddit.com/r/lgg2/comments/20769k/how_to_use_tasker_to_control_the_back_button_led/
but thanks for your profile. I loaded it, and it isn't giving me any errors, but I'm still not getting it to work. I have it set to trigger when a notification event happens...I set Hangouts to the "owner application" and still not getting it working.....I have almost given up on this working without root.
thanks for you help though. if you think of anything, I would greatly appreciate any help, but dont bend over backwards for me...haha
It about stops me from doing uploading pictures, downloading. It's driving me crazy anyone else having this problem?
Yea lots of people are. Anything that changes the status of the screen like some kind of screen filter like twilight, night owl, any of those things, can mess with this. It's been pretty annoying. I have Twilight set to a timer to eliminate blue light on the screen before sleeping and I have to freeze and defrost it several times a day. Apparently it's an issue with ZTE. There is a thread over there about it.
presley07 said:
It about stops me from doing uploading pictures, downloading. It's driving me crazy anyone else having this problem?
Click to expand...
Click to collapse
I guess that it should actually be a security feature to prevent an overlay app from abusing any open apps below it... but it is really annoying that the ZTE integrated feature Mi-POP will also make this warnings display... you can simply deactivate it through its notification bar shortcut but it's still annoying...
Gachmuret said:
I guess that it should actually be a security feature to prevent an overlay app from abusing any open apps below it... but it is really annoying that the ZTE integrated feature Mi-POP will also make this warnings display... you can simply deactivate it through its notification bar shortcut but it's still annoying...
Click to expand...
Click to collapse
Well for now I am backup and running, I shot down the phone and restated posting ok
presley07 said:
Well for now I am backup and running, I shot down the phone and restated posting ok
Click to expand...
Click to collapse
I'm going to guess you have MiPop enabled? is so turn it off and your screen overlay issue might go away.
Gatorguy2 said:
I'm going to guess you have MiPop enabled? is so turn it off and your screen overlay issue might go away.
Click to expand...
Click to collapse
I an checked everything and it did no good, mipop and all else. Restarted phone and all was OK, hope this helps others with the same issue
presley07 said:
I an checked everything and it did no good, mipop and all else. Restarted phone and all was OK, hope this helps others with the same issue
Click to expand...
Click to collapse
Screen overlay is new in 6.0 to prevent apps from creating an overlay and giving permissions to themselves. It's not an issue with ZTE.
Yes screen overlay is new. Came from a N6 and never had this problem on stock 6.0 from Google. Facebook messenger will not do anything other than message can't call, or send pictures. Yes it is a problem with ZTE
Sent from my ZTE A2017U using Tapatalk
Go to the "Apps" setting, and then click on the "gear-shaped" setting button to go to the "Draw over other apps" menu and turn off all apps that are enabled. Go back to the "Apps" setting and click on the app that needs permissions modified. When all the permissions are updated, go back and enable the "Draw over other apps" for those apps you disabled.
Use this app it will get rid of that annoying overlay issue.
https://play.google.com/store/apps/details?id=jp.sfapps.installbuttonunlocker