I'm not sure if there's a better place to post this, i there is let me know and sorry.
My main problem: If I use the terminal to turn the Flash on / off (# echo 0 > /sys/class/leds/led:flash_torch/brightness), my Torch control apps (i.e Torch, TeslaLED), somehow lose the ability to turn the Flash on and off. The only thing that can still control the Flash is the camera app for taking pictures or by using the terminal to turn in back on. Does anyone have any ideas about why this happens, how I can fix it, or where I should go for more help? Or is there a way I can use the terminal to tell my app (Torch -- net.cactii.flash2) to turn off the Flash (instead of forcing it off through the echo 0 to the brightness file?
Background as to why I need to even do this: My phone (Oneplus One, 4.4.4, CM11), has gesture controls that allows me to control the flash while the screen is off and locked. The phone uses the Torch app to do this (net.cactii.flash2). Sometimes it turns on accidentally and I don't notice. So I made a tasker profile that essentially turns the Torch off it's been on for more than 30 seconds. It runs the command (# echo 0 > /sys/class/leds/led:flash_torch/brightness). This works to turn the Flash off, but then I can no longer use Torch or TeslaLED to control the torch. The only way it turns back on is by running a (# echo 1 > ...) (The camera app can also use the Flash for pictures). I've tried to just kill the torch app, but that doesn't turn the flash off.
Oh also, It's not that the Torch apps still work but the "Brightness" is 0 (AFAIK). If that were the case, I feel that the Camera Flash wouldn't work. And When I do Echo 1 > ... to turn it back on, the Apps can't turn it off either.
Also, restarting my phone fixes the issue. But I can't just restart every time.
Thanks!
The capacitive button lights....turn on...all the time. Every time I touch the screen, they flash on....then after half a second, back off. I touch the screen again, they flash at me. I was ready to move on from on screen buttons on my nexus 5...but the lights are so annoying. And even if you turn them off by going to power saver (which you shouldn't have to), then they don't vibrate! And there's nothing printed on the phone at all...so you're just pressing a blank corner of the phone.
Even if they do give the option to turn the lights off in the future, there won't be anything labeling the button to press. Ugh.
I guess you have to pick your poison. You don't want the lights on but at the same time you don't want to touch a blank corner of the bottom of the phone
twoeleven99 said:
I guess you have to pick your poison. You don't want the lights on but at the same time you don't want to touch a blank corner of the bottom of the phone
Click to expand...
Click to collapse
They could have printed something on the phone...but for the sake of making the phone prettier and more iphone like, they didn't. Not to mention the power save mode throttles cpu too...so that's hardly a long term solution. Not keeping a $700 phone in hopes that they'll add an option to turn the lights off.
That sounds really annoying. I have a galaxy s4 on stock touchwiz lollipop and the capacitive button lights don't turn on unless they are pressed. It's always been like that on the s4 and it's the same on my tab 10.1. The only time I've seen the lights turn on whenever I touch the screen is on some aosp roms. Maybe this is a bug on the s6.
I can turn the key lights off on my AT&T S6. Settings, Display, Touch key light duration, always off.
yeah only the ATT s6's have the setting for turning off the lights.
Every other version has had the setting removed. And now the bloody lights turn on anytime you interact with the phone...even if you're not touching the buttons!
But none of the versions have any label printed there right?so even if they add the option to turn off the lights, you won't even have labels to pish will you?
But you know where the buttons are and what they do why do you need them to be labeled?
twoeleven99 said:
But you know where the buttons are and what they do why do you need them to be labeled?
Click to expand...
Click to collapse
OCD mainly. I shouldn't have to push a general area of the phone and have it do something. Heck, half the promo shots of the phone make it look like there is a light printing of the buttons, but in reality it's blank.
If the ATT version has the option to disable or set a timer, it's definitely software bound. Probably will be added to future updates, hoping so.
I'm sure it could be tweaked with software. Hell, they wouldn't really bother me that much if they just faded in and out.
adb fix for capacitive buttons
0dBu said:
I'm sure it could be tweaked with software. Hell, they wouldn't really bother me that much if they just faded in and out.
Click to expand...
Click to collapse
Hi, using my Note 3 and adb I figured out the fix for this. On the Note 3 these settings were under Settings/Display/Touch Key Light. Assuming you have ADB installed and the phone put into developer mode (root is not required, this is 'standard' stuff) + usb debugging to on, take the following steps (tested on an S6 Edge):
* on the PC running adb, connect it to the device and use the command 'adb usb'. Perform the requested action to allow the PC access to the S6 (Edge)
* next, use the following commands to change the light-out period:
"adb shell settings put system button_key_light 0" -> always disable the capacitive button lights
"adb shell settings put system button_key_light -1" -> always enable the capacitive button lights
"adb shell settings put system button_key_light 1500" -> always disable the capacitive button lights after 1.5 seconds
"adb shell settings put system button_key_light 6000" -> always disable the capacitive button lights after 6.0 seconds
"adb shell settings get system button_key_light" -> get the current setting (standard: 1500, ie. 1.5 seconds)
Good luck,
Sander761 (I posted this same instruction on Tweakers.net in Dutch btw)
Interesting, thank you.
So it's either disable the capacitive backlights or enable them? I'm not sure about the S5, but I know the S3 and S4 will only turn on the backlights for the buttons if you actually press them, and they will stay off when you are touching the screen. It's much better that way.
mupet0000 said:
So it's either disable the capacitive backlights or enable them? I'm not sure about the S5, but I know the S3 and S4 will only turn on the backlights for the buttons if you actually press them, and they will stay off when you are touching the screen. It's much better that way.
Click to expand...
Click to collapse
I get the exact same behaviour on my S6 as I get on my Note 3: if I touch them they will light up, if I touch the screen they will stay off. So I don't think that has changed.
I can assure you that at least on a T-Mobile GS6 when you touch the screen the capacitive buttons light up.
0dBu said:
I can assure you that at least on a T-Mobile GS6 when you touch the screen the capacitive buttons light up.
Click to expand...
Click to collapse
Confirming as true.
sander761 said:
Hi, using my Note 3 and adb I figured out the fix for this. On the Note 3 these settings were under Settings/Display/Touch Key Light. Assuming you have ADB installed and the phone put into developer mode (root is not required, this is 'standard' stuff) + usb debugging to on, take the following steps (tested on an S6 Edge):
* on the PC running adb, connect it to the device and use the command 'adb usb'. Perform the requested action to allow the PC access to the S6 (Edge)
* next, use the following commands to change the light-out period:
"adb shell settings put system button_key_light 0" -> always disable the capacitive button lights
"adb shell settings put system button_key_light -1" -> always enable the capacitive button lights
"adb shell settings put system button_key_light 1500" -> always disable the capacitive button lights after 1.5 seconds
"adb shell settings put system button_key_light 6000" -> always disable the capacitive button lights after 6.0 seconds
"adb shell settings get system button_key_light" -> get the current setting (standard: 1500, ie. 1.5 seconds)
Good luck,
Sander761 (I posted this same instruction on Tweakers.net in Dutch btw)
Click to expand...
Click to collapse
Thanks for the fix, disabled them. Sad there isn't a way to have them only go on when you press them.
I'm sure it can be customized to only light up if pressed on a custom rom. If there are enough requests maybe a dev making roms for us can implement it
sander761 said:
I get the exact same behaviour on my S6 as I get on my Note 3: if I touch them they will light up, if I touch the screen they will stay off. So I don't think that has changed.
Click to expand...
Click to collapse
This is the behaviour we all want I think. Which variant do you have?
mupet0000 said:
This is the behaviour we all want I think. Which variant do you have?
Click to expand...
Click to collapse
I have the European variant S6 Edge SM-925F, build LRX22G.G925FXXU1AOCV. But just to confirm: my behaviour is that *once the display is on*, using the touchscreen (except cap. button area) does not light the buttons. When unlocking the device, the buttons always light up briefly (unless you turned them off, of course). If that is the wanted behaviour, I guess this is the build you want
I bought the Phab2 Pro and one of the first things I noticed is that the light of the navigation bar (back, home, recent buttons), is always on, and the settings option to disable it, it's gone.
I tried to manage it with some apps and they don't work.
Also tried trampling with the adb usb debugging "adb shell settings put system button_key_light 0" and it doesn't work, but change it for screen_brighteness for example and it works perfectly.
I just want to turn it off because it's really annoying when I'm watching videos or just playing landscape. Anyone knows a way?
I saw an article that described how to use ADB to enable the Two button navigation feature that doesn't show in the Betas.
I've also seen the posts about ADB way.
I was wondering if one has root. Is there a config file that the feature can be turned on from instead?
Here is the ADB command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Just didn't know if someone could tell from this what config file it might be.
paulsg63 said:
I saw an article that described how to use ADB to enable the Two button navigation feature that doesn't show in the Betas.
I've also seen the posts about ADB way.
I was wondering if one has root. Is there a config file that the feature can be turned on from instead?
Here is the ADB command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Just didn't know if someone could tell from this what config file it might be.
Click to expand...
Click to collapse
I just updated my op7pro to Android 10 and would like this option back too and this is all I can find about it
Sent from my OnePlus7Pro using XDA Labs
I love this - thank you. Do not like the Android 10 gestures at all. 2 button is my favourite !
Have you tried just omitting the adb shell part and bunging this into Termux?
cmd overlay enable com.android.internal.systemui.navbar.twobutton
Anybody finding that the back button puts the screen off if double tapped when on the launcher screen? I tried disabling double tap to sleep on the home button, but it still happens. Just curious to see if it happens everyone or if it's just mine. Thanks
hallo dare said:
Anybody finding that the back button puts the screen off if double tapped when on the launcher screen? I tried disabling double tap to sleep on the home button, but it still happens. Just curious to see if it happens everyone or if it's just mine. Thanks
Click to expand...
Click to collapse
Just tried and it doesn't happen for me.
The back button doesn't show if I'm on the home screen and if I tap the back button when the app drawer is open it tends to just open the app that's 'underneath' the button
skymera said:
Just tried and it doesn't happen for me.
The back button doesn't show if I'm on the home screen and if I tap the back button when the app drawer is open it tends to just open the app that's 'underneath' the button
Click to expand...
Click to collapse
Yep same as that, no back button displayed on home screen, but it's turning off the screen if i tap on it twice. Something my side so. O well. Thanks for confirming
All of my recent devices have had the back button on the right of the navbar, or the option to move it. I'm so used to having mine in that configuration that I kept hitting the wrong button so decided to change it, using ADB we can achieve this.
Connect to ADB then use the following commands:
adb shell
settings put secure sysui_nav_bar "space,space,space,space,recent;home;back,space,space,space,space"
If you want the buttons spread out a little more, remove a space from either side