I use the left swipe for menus a lot and was really hating the back gesture messing that up. Found https://android.gadgethacks.com/how-to/disable-androids-back-gesture-left-side-make-hamburger-menus-easier-open-0338679/ and worked perfectly. The below ADB code is what I used and assumes you have the Android SDK and ADB set up.
Code:
adb shell settings put secure back_gesture_inset_scale_left 0
You can adjust the sensitivity for each side in settings. This just turns it completely off?
letrain02 said:
You can adjust the sensitivity for each side in settings. This just turns it completely off?
Click to expand...
Click to collapse
Yes and it works perfectly on Pixel 5 too.
Setting lower sensitivity won't disable back gesture.
letrain02 said:
You can adjust the sensitivity for each side in settings. This just turns it completely off?
Click to expand...
Click to collapse
I don't think it turns out all the way, I've had it trigger in apps with no left menu. It's much less sensitive though and the menu will pop out first. I'm thinking of doing it in the right too because it's way too sensitive for the browser I use, which has a ton of gesture controls.
The sensitivity in settings did nothing for me so found this.
brandontowey said:
I use the left swipe for menus a lot and was really hating the back gesture messing that up. Found https://android.gadgethacks.com/how...ide-make-hamburger-menus-easier-open-0338679/ and worked perfectly. The below ADB code is what I used and assumes you have the Android SDK and ADB set up.
Code:
adb shell settings put secure back_gesture_inset_scale_left 0
Click to expand...
Click to collapse
you should mention that others should try -1 or -2 if 0 does not work, 0 did not work for me but -2 seems to have disabled it
bramble with proton rom and kernel
I put -20 on both sides (to make sure it doesn't trigger in the cutout area in landscape mode) and use FNG instead. Works like a charm.
old thread, but this worked for disabling the right-back-gesture on Android 13/Pixel 6
adb shell settings put secure back_gesture_inset_scale_right 0
I use this command to use gesture from 3rd party application, but the original back gesture still working on my vivo x60 pro. Any thoughts please?
Related
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
+1
Sent from my Nexus 5X using Tapatalk
hmmm, you can try to use command 'input keyevent 26' , for tasker task...
this will required root though.
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
minnemike said:
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
Click to expand...
Click to collapse
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
jpen said:
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
Click to expand...
Click to collapse
Any solutions yet?
scottfreeze said:
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for this! Added it as a Tasker shortcut for double-tap gesture in Nova and it works like a charm.
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Pumpino said:
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Click to expand...
Click to collapse
There's a known list of Android commands that software can use to simulate some hardware presses, etc.: http://thecodeartist.blogspot.com/2011/03/simulating-keyevents-on-android-device.html
Tasker or using the keyevent 26 will not interfere with the system in any way. By sending the keyevent 26 you are doing exactly what pressing the Power button does - only with software. It does nothing to change any system settings. Not sure about the Soft Lock Screen app, but I suspect that like other software, if you use that, you will prob need to re-enter your password/pattern/pin and the fingerprint won't work. By sending the keyevent 26, you can still unlock it using the fingerprint sensor.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
minnemike said:
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
Click to expand...
Click to collapse
It does require root to be able to let Tasker run a shell command. You would not need Nova launcher as you can easily put a widget to launch the Task within Google Now Launcher or any other launcher. Nova launcher is nice because it enables gestures and double tap to do certain actions. I have Nova to launch my phone app when I tap the Home button on the main home screen. Double tap runs my Task to turn off the phone. Pinch in, pinch out, two finger swipe down/up, etc.
Could you have something trigger Tasker to temporarily change the screen timeout to 1 second (and then change it back after the screen is off)?
solara1973 said:
It does require root to be able to let Tasker run a shell command
Click to expand...
Click to collapse
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Pumpino said:
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Click to expand...
Click to collapse
Nova launcher does not have a function to send keyevents or turn off the screen etc.
You can always try some of the Screen Off apps on the playstore and see if anyone of those allow you to unlock the phone again using Imprint. Swipe-Lock, Screen Off and Lock, Screen Lock, etc.
this one works (experimental) https://play.google.com/store/apps/details?id=com.iglint.android.screenlockpro&hl=en
it is paid one
Am I just so used to Moto phones that I didn't realize that screens down light up when picked up? Laying in bed reaching over to turn my phone to me I have to push the power button? Am I missing a setting? I'm so used to it lighting up to show me time and notifications just tilting it.
sadly, this phone doesnt have this feature
check settings > moves > lift to check phone
uicnren said:
check settings > moves > lift to check phone
Click to expand...
Click to collapse
Nope it's not one of the three options there. I found a app called Gravity Screen and once you select the right options it works pretty great. Took me a second to figure out how to get it not to block unlocking with my finger. Not great I need a secondary app but at least it feels right again.
Jacobk85 said:
Nope it's not one of the three options there. I found a app called Gravity Screen and once you select the right options it works pretty great. Took me a second to figure out how to get it not to block unlocking with my finger. Not great I need a secondary app but at least it feels right again.
Click to expand...
Click to collapse
See also:
Turn on ambient display: A feature of Android Wear and Motorola devices, it's now on Android Nougat by default. Head into Settings > Display and you'll be able to glance at monochrome notifications.
Seems they have also changed how this works, so your current solution may be better.
Apparently it (ambient display) now only illuminates the screen when a notification comes in, not again when you lift.
Can't believe this phone does not come with such a simple yet very convenient feature
Sent from my Pixel XL using Tapatalk
I miss it as well, but I guess the Pixels should be getting a tap to wake update soon, that will help some.
Whoa, if so that's amazing. How sure are we? What's the source?
So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.
EyeBeeNY said:
So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.
Click to expand...
Click to collapse
Have you been messing with Immersive Mode where you hide the nav/status bars?
mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.
Did you install Greenify? I experienced a similar issue with Greenify installed.
byproxy said:
mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.
Click to expand...
Click to collapse
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar
Thanks for the tips, all. I am not running any third party apps to alter anything stock on the phone. I'm not exactly sure what immersive mode is or how to activate it, but I haven't changed any settings in the phone other than your typical changes like font size, wallpapers and notification tones.
I do have an app called Calls Blacklist to block unknown and private calls, which Ive been getting a lot of lately. Perhaps that app's not playing nice with the AOD?
henderjr said:
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar
Click to expand...
Click to collapse
do i need to undo the adb command i used originally?
byproxy said:
do i need to undo the adb command i used originally?
Click to expand...
Click to collapse
No should just be able to run the command I posted above
I narrowed it down to the Call Blocker app. Just applied the November security patch and now it happens everytime the app blocks an incoming call. I haven't uninstalled the app yet, but when I do I will update the thread to confirm my theory.
Thanks to everyone for their input.
When I picked up my P6P the screen turns on which I don't want. I've changed these and it still comes on when I pick it up. What I would like is tap to check and the old standby press the power.
This doesn't seem possible right now? Or it's either so obvious or hidden that I can't see how to achieve this.
I have Lift to check phone turned off.
Tap to check phone turned off.
Don't turn screen on for new notifications
Don't show notifications on lockscreen.
Now Playing turned off.
All face tracking to keep screen on turned off.
But pick the phone up and the screen turns on with the time, battery percentage and the fingerprint symbol even with all the above turned off.
Ultimoose said:
When I picked up my P6P the screen turns on which I don't want. I've changed these and it still comes on when I pick it up. What I would like is tap to check and the old standby press the power.
This doesn't seem possible right now? Or it's either so obvious or hidden that I can't see how to achieve this.
I have Lift to check phone turned off.
Tap to check phone turned off.
Don't turn screen on for new notifications
Don't show notifications on lockscreen.
Now Playing turned off.
All face tracking to keep screen on turned off.
But pick the phone up and the screen turns on with the time, battery percentage and the fingerprint symbol even with all the above turned off.
Click to expand...
Click to collapse
It's related to having fingerprint unlock set up. 2 ways around it that I know of:
1. Delete fingerprints and use another unlock method, or
2. Connect your phone to your computer and in adb shell run this command:
shell settings put secure doze_quick_pickup_gesture 0
Lughnasadh said:
It's related to having fingerprint unlock set up. 2 ways around it that I know of:
1. Delete fingerprints and use another unlock method, or
2. Connect your phone to your computer and in adb shell run this command:
shell settings put secure doze_quick_pickup_gesture 0
Click to expand...
Click to collapse
Thank you for the ADB command - that is absolutely driving me nuts that it just randomly wants to turn the screen on if I bump it or move it.
SchmilK said:
Thank you for the ADB command - that is absolutely driving me nuts that it just randomly wants to turn the screen on like that!
Click to expand...
Click to collapse
No problem
Lughnasadh said:
It's related to having fingerprint unlock set up. 2 ways around it that I know of:
1. Delete fingerprints and use another unlock method, or
2. Connect your phone to your computer and in adb shell run this command:
shell settings put secure doze_quick_pickup_gesture 0
Click to expand...
Click to collapse
20 kinds of thanks @Lughnasadh Not to get ranty, because it's funny as of now but this thing seriously wakes up and pops the display on if I even think about touching it. Because I have smart unlock on with my watch I invariably end up opening up some random menu or hitting manual lock and then have to pin it open.
Hi all,
I got my Pixel this week and it's great so far. I got an issue with the deactivation of the gesture "activate display on lift up" (could be different in english because it's in German for me). If I deactivate this setting, the gesture just gets deactivated for a few screen-off screen-on cycles. In the settings it's still deactivated but in real life the pixel activates again if I lift it up. Does anybody knows a fix?
adb shell settings put secure doze_quick_pickup_gesture 0
mcboums said:
adb shell settings put secure doze_quick_pickup_gesture 0
Click to expand...
Click to collapse
Thx, this works! Do you know why it isn't possible via GUI? Is it a known bug?
daniel.1983 said:
Thx, this works! Do you know why it isn't possible via GUI? Is it a known bug?
Click to expand...
Click to collapse
It's related to fingerprint unlocking. If you didn't use fingerprint unlocking then it would act "normal" and the screen wouldn't turn on when phone is touched or lifted (assuming you have lift to wake disabled). It "appears" to be a feature that Google implemented to make if faster or easier to unlock your phone. Most users see it as a bug
Lughnasadh said:
It's related to fingerprint unlocking. If you didn't use fingerprint unlocking then it would act "normal" and the screen wouldn't turn on when phone is touched or lifted (assuming you have lift to wake disabled). It "appears" to be a feature that Google implemented to make if faster or easier to unlock your phone. Most users see it as a bug
Click to expand...
Click to collapse
It is a bug from what I can tell.
The lift to wake toggle in gestures doesn't do anything being on/off, it's always on when it shouldn't.
Tap to check toggle works as intended.
Fingerprint being on or off shouldn't make the toggle work or not, my other FoD devices the lift to wake toggle work as intended.
Probably another half-done crap Google left behind.
edit: also after using the adb command, the toggle seems to work as intended from then on. Funky
eng.stk said:
It is a bug from what I can tell.
The lift to wake toggle in gestures doesn't do anything being on/off, it's always on when it shouldn't.
Tap to check toggle works as intended.
Fingerprint being on or off shouldn't make the toggle work or not, my other FoD devices the lift to wake toggle work as intended.
Probably another half-done crap Google left behind.
edit: also after using the adb command, the toggle seems to work as intended from then on. Funky
Click to expand...
Click to collapse
Apparently someone on Reddit had a Google chat with Google about this and they told them that this was intended as part of the fingerprint unlocking system. That's why I said Google probably views it as a feature, but most users view it as a bug.
I personally use the adb command to make it work as "we" think it should, not how Google thinks it should.
Lughnasadh said:
Apparently someone on Reddit had a Google chat with Google about this and they told them that this was intended as part of the fingerprint unlocking system. That's why I said Google probably views it as a feature, but most users view it as a bug.
I personally use the adb command to make it work as "we" think it should, not how Google thinks it should.
Click to expand...
Click to collapse
If that really happened, is just nonsense. Toggle is there to be used.
It works in my other several devices, FoD or not. It works after the adb command issued on my oriole (toggle state works as intended I mean).
The amount of broken stuff on raviole devices is just ridiculous by now.
Also the radio stack on the device is the worst I ever seen.
eng.stk said:
If that really happened, is just nonsense. Toggle is there to be used.
It works in my other several devices, FoD or not. It works after the adb command issued on my oriole (toggle state works as intended I mean).
The amount of broken stuff on raviole devices is just ridiculous by now.
Also the radio stack on the device is the worst I ever seen.
Click to expand...
Click to collapse
You're preaching to the choir