There is a way to "soft restart" phones. If I change a system setting, my phone's homescreen will go blank, and "redraw" all the icons... etc. I was wondering if any developers know the shell command used. I am working on an application, and I need that command.
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
Hello Everyone,
I don't know if I am missing something, but since the button on the Blu Pure XL do not light up... I wanted to add the bottom navigation bar with the back home and switch button but I can't!
I have installed Google Now Launcher... Nothing.
I have Nova Premium... Nothing.
Any suggestions?
Thank You
My buttons never light up even if I use another launcher .. if I hold the phone a certain way in the light - i can see them. But I have a general idea where they are so I just press the general area. Most times I hit it .. sometimes it takes a couple of taps.
jaybirdhawaii said:
My buttons never light up even if I use another launcher .. if I hold the phone a certain way in the light - i can see them. But I have a general idea where they are so I just press the general area. Most times I hit it .. sometimes it takes a couple of taps.
Click to expand...
Click to collapse
I am aware that the buttons do not light up... i am trying to add the navigation bar at the bottom of the screen (on screen, software), so I would not have to worry about the hardware buttons.
dkokkos said:
I am aware that the buttons do not light up... i am trying to add the navigation bar at the bottom of the screen (on screen, software), so I would not have to worry about the hardware buttons.
Click to expand...
Click to collapse
I have just done this so it is confirmed working. First off you need to be rooted and have busybox installed. And if you are rooted you have twrp installed so I would recommend doing a backup. Anyway download a app called soft buttons from the play store. Open the app, open menu go down to capacitive keys menu open that and click on disable capacitive keys. Once all the permissions stuff stops popping up on the screen open menu and click on virtual keys menu then click on enable virtual keys. Wait till all the permissions stop popping up on the screen then reboot your phone. Once your rebooted you will have virtual menu buttons and your regular capacitive keys will be disabled so you don't hit them on accident.
There are also options to reverse the process a far as re enabling capacitive keys and disabling virtual keys as I have decided to do because I'd rather have the 1/4 inch or whatever of screen that it takes up.
So there is this app that if you use ADB, it can give you Android O's navigation bar...without root: Here
However, when I checked something off in one of the settings, something crashed my phone and sent me back to my lockscreen, now when I try to go to put in my passcode, it crashes before I have a chance to use it. The command I put in is this to get the app to let me use it: "pm grant xyz.paphonb.systemuituner android.permission.WRITE_SECURE_SETTINGS" but thats not what broke it, I think it was a setting where I tried to add a extra button. I dont think my navagation bar works anymore...
Is there a way to reverse this without resetting my phone back to default? Let me know if I need to give out anymore info.
Running Unlocked HTC One A9 on 7.0, stock/unrooted/unmodified.
Try to reboot in safe mode and uninstall that app?
With the phone powered off, press the power button. As soon as you see the HTC logo, release the power button and press and hold the volume down button until you're in the OS. It should now be in safe mode and hopefully that app shouldn't boot.
i had the same problem, after the compatibility test of that app (customized nav bar by paphonb),.. status/notification bar, navigation bar disappeared. and when I try to open an app, the phone freezes. Please help!
[GUIDE] fix for the blank space under keyboard & status bar going down on its own bug
guys i found the fix for 2 major problems
the first being on FTS screens.. flashing another kernel will fix touch freeze. but will break status bar. it will go down on its own.. and the second in android q when using gesture navigation you will notice a blank area that appears best under your keyboard..
the solution to both problems is by connecting your device to a pc
have usb debugging turned on
and then type this command
adb shell wm overscan {left},{top},{right},{bottom}
so to remove the blank space beneath the keyboard we simply type
adb shell wm overscan 0,0,0-100
and to solve for the status bar issue we alter the top value for a bit
i have a screen protector so it eats some of my screen so i typed
adb shell wm overscan 0,7,0,-100
and voila everything now works
if you want to reset just type 0,0,0,0
notes
if you flash a kernel above that it will reset your values
you can restart and flash mostly anything except kernel and it will be still the same
bugs
on some like gallery it will require you to use gesture navigation twice to actually do what you want.. just like in full screen mode. one swipe to show the navbar. the other is to return
and you will notice white lines in the borders of your screen if you altered the values too much
I have made many test with that, and finally went back to Pie because withhout the bar it makes conflict with gestures when using KB or long pressing keys at the corners activating the gestures... At android Q it stinks, that is why i came back to Latest Miui stable :'(
205GTX said:
I have made many test with that, and finally went back to Pie because withhout the bar it makes conflict with gestures when using KB or long pressing keys at the corners activating the gestures... At android Q it stinks, that is why i came back to Latest Miui stable :'(
Click to expand...
Click to collapse
yeah man. FTS are the worst. but we have to sacrifice a few to save the majority