Home soft buttons/gestures not working anymore - Google Pixel Questions & Answers

I'm having a weird issue with my Pixel 1, all of a sudden my swipe from bottom home gesture stopped working. I enabled the soft buttons bar again but even tapping the home button there does nothing neither does the app drawer button, however the back gesture and button works fine.
There's also a few more oddities like my registered fingerprints got deleted so I had to register them again, some settings were changed like the order of the quick action icons, swiping the fingerprint reader down doesn't open notifications, and so on.
I've had issues with my battery for a while so I thought it could be related but I still have issues after replacing it. Is this a know issue or some sort of malware maybe? I'm thinking about doing a factory reset but I'm wondering if there's a less nuclear option.
Thanks!
Device Model: G-2PW4200
Android Version: 10

Related

[Q] Keyboard blocks lockscreen, bug?

I'm having this weird issue since a couple of days, and it's starting to annoy me.
I have stock 4.3 on my Moto G (Still no 4.4 here in Chile) and when I'm writing a message, post, or anything involving the keyboard, and then press the power button to lock the phone, when I wake up the phone again the keyboard is still there on top of the lock screen, blocking the pattern area/slide button/unlocking method widget, and the only way to get rid of it is by dragging the notification area to bring any notification or settings menu up, trying to bring the camera/Twitter widget/any lockscreen widget, or activating Google Now.
So far, it looks like this bug happens with any app capable of bringing the keyboard up. I haven't tried to factory reset my phone yet and I still have to do a full backup in that case, but I hope that's the last resort. Any ideas?
Thanks in advance.

Lockscreen not showing on power button press*?

Hello,
After a few days of using the phone, I installed Lightning Launcher and set it as default. I got some bugs with the lockscreen (i'll explain later) so I reverted back to the Xperia original launcher.
Now, after not using LL, I still have that same issue. I'm pretty sure it hasn't anything to do with LL or anything, but I prefer mentionning it just in case.
(tl;dr)
Whenever I press power button, it is supposed to immediately scan the fingerprint. It doesn't anymore and instead of the normal lockscreen I have a completely blank screen, only with Back and Home button.
Finger is not scanned, I can't swipe in any direction BUT, if I press the Home button, lockscreen shows up (it slides from the left side), as if I already swiped to the right.
That's pretty annoying when the purpose of fingerprint scan is to immediately unlock
Got any idea ? Somebody has the same problem maybe ?
EDIT:
Okay my bad. I uninstalled LL completely and the problem didn't show up anymore. I reinstalled because I remembered it can also be used as a lockscreen, and i disabled that in its settings. I'll check if problem continues but if not, I'll come back to inform about it.

Hard Buttons Acting as they were held for sometime!?

I have a stock Galaxy S6 with stock ROM and no mods at all.
Problem:
The problem started couple months ago where when I tap the back capactive key it acts like it was on hold for a time so it triggers the options context menu of the current app. That would trigger on some apps most of the time, another apps will sometimes pass, sometimes have the problem.
Here is exactly what happens when I tap the back key:
Tap *Vibration to let me know the hardware received my gesture*
No action
Tap again *no vibration this time - phone trying to complete (on its own) the time needed for the key to be held to trigger the HOLD action and open the options menu on the currently active app*
After some time, option menu (eg. settings menu on the top right corner of Whatsapp for example opens up)
This exact process happens so fast, and was inconsistent so I acted as if it was never there, and after sometime, it was gone for a short period of time, until Today, the problem reoccured again but now with the home button and the recent button.. Back button is fully working now.
Home button: Triggers Google Assistant
Recent button: Triggers Split View
I restarted my phone and now it's gone, but I know it is coming back.
I think it is not a hardware issue, how do I fix that annoying issue?
Current Version Info:
SM-G920F
Baseband: G920FXXU6ERCA
Android 7.0
Security Patch Level: March 1, 2018

Multitouch issue/disable with the status/notification bar?

Hello. So i made the switch to the S10e and i've been running into this issue where if i accidentally hold my phone with my finger just touching the selfie camera (or any part of the status/notification bar at the top of the screen), any and all other touch inputs just get disabled.
Any solutions to this? I assume Android thinks i'm going to pull it down and disables every other touch or something, but is there an option not to do that but still keep the draggable status bar? This also happens in all apps and the home screen/apps etc. no matter the screen.
Activating Show Taps in developer shows that the OS DOES see both my taps, the status bar and anything else, just that the software-side blocks other inputs once that initial status bar touch is seen and still active. It does NOT happen with the back/home/apps bar or generally anywhere else. I have tried making sure Nova launcher isn't doing anything. Tried Accidental touch protection On and Off and a host of other settings. Confirmed this is a status bar issue with hiding it in Samsung Internet and repeating the test.
Tried EdgeTouch with NiceLock but it only really helps for the sides which aren't really my issue.
Rarely this sometimes happens with stuff on screen too in the OS itself and in apps. Usually it's with triggering a function like holding the phone with touching the left hand of the screen and accidentally 'dragging' a menu' into view a few pixels, and then that disables all other input until it's gone. But that's fine since it's very rare. It's more more often than the status/notification bar is my main issue.
Cosmitz said:
... i accidentally hold my phone with my finger just touching ...
Click to expand...
Click to collapse
Do you use a case? That's what help'd me with accidental screen touches. An "ultra slim" case was all it took for me. Hope you find what works for you.
I am really against cases, as i really want a compact fone, and there are extremely few which get launched with AMOLED nowdays. I'd rather solve this via software.
Up?
Up?
Up?
up?
Up.
Up.

Question Touch delay after exiting apps

Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
Your browser is not able to display this video.
I use Xposed edge pro for system gesture and it's fast AF
abdullaHD said:
Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
View attachment 5589763
Click to expand...
Click to collapse
I'm not seeing much of any delays in your video but maybe its because it's too small on my screen. If you want to speed things up navigating between apps go into developer options and there are 3 parameters you can play with (top 3 in screen shot)
I'm having different issues after updating. I'm on a Verizon S22 Ultra, using Nova Launcher with gestures and power savings mode enabled.
I'm having an issue where, after I use the pull down gesture (swiping downward) on the home screen (for example, if I'm just trying to switch from wifi to mobile data, or trying to turn off Bluetooth, or trying to turn on location) a lot of the time I'll have a delayed and or almost immediate ghost touch input, without touching anything.
Sometimes, even if I don't touch anything and I just swipe down to bring down the pull down ui, it'll act like I used the swipe up gesture and clear the pull down ui and return me to the home screen. Other times it'll act like I pressed the home button icon (there will be a soft white glow that shows up around the home screen icon), even though I never touched the home button icon.
Other times, on the home screen, I'll use the slide down gesture. The pull down comes down, and almost immediately it'll act like I have pressed the recents button and my recent apps pops up. It's like someone else is controlling my phone, but only on the homescreen, very annoying.
This only seems to happen when I'm on my home screen and trying to use the pulldown gesture when power savings mode is enabled. Although, it did happened a couple of times in Samsung Internet Browser Beta when power savings was enabled and prior to the recovery cache clearing. Randomly, the settings ui popped up on me while trying to type in an internet address, but I never touched the hamburger menu icon in the lower right.
This doesn't seem to happen in the Samsung Internet Browser Beta anymore after performing the recovery cache clearing. When it was happening in the browser, I'd try turning off the power saver and the ghost touches seemed to stop.
On the homescreen, once the pulldown comes down, even when pulling down for a second time to fully expand the ui (sometimes almost immediately and or even after a few seconds of not touching anything), it'll either take me right back to the home screen (like I pressed the home button icon or it'll pull up the recent apps ui and I never touched anything). It is wonky.
I've tried clearing cache through the recovery method and it's still acting up when power saving mode is enabled. The only thing that seems to have caused it to stop, is turning off power saver mode.
Anyone else experiencing this issue of ghost touches with power savings enabled along with Nova Launcher's gestures (or on any other 3rd party launcher and or even the stock launcher perhaps?) on the home screen? I haven't had time to record this yet, I'll have to get some video of it, just wanted to see if anyone else is experiencing this or knows of a better workaround perhaps?
Justinphxaz said:
I'm having different issues after updating. I'm on a Verizon S22 Ultra, using Nova Launcher with gestures and power savings mode enabled.
I'm having an issue where, after I use the pull down gesture (swiping downward) on the home screen (for example, if I'm just trying to switch from wifi to mobile data, or trying to turn off Bluetooth, or trying to turn on location) a lot of the time I'll have a delayed and or almost immediate ghost touch input, without touching anything.
Sometimes, even if I don't touch anything and I just swipe down to bring down the pull down ui, it'll act like I used the swipe up gesture and clear the pull down ui and return me to the home screen. Other times it'll act like I pressed the home button icon (there will be a soft white glow that shows up around the home screen icon), even though I never touched the home button icon.
Other times, on the home screen, I'll use the slide down gesture. The pull down comes down, and almost immediately it'll act like I have pressed the recents button and my recent apps pops up. It's like someone else is controlling my phone, but only on the homescreen, very annoying.
This only seems to happen when I'm on my home screen and trying to use the pulldown gesture when power savings mode is enabled. Although, it did happened a couple of times in Samsung Internet Browser Beta when power savings was enabled and prior to the recovery cache clearing. Randomly, the settings ui popped up on me while trying to type in an internet address, but I never touched the hamburger menu icon in the lower right.
This doesn't seem to happen in the Samsung Internet Browser Beta anymore after performing the recovery cache clearing. When it was happening in the browser, I'd try turning off the power saver and the ghost touches seemed to stop.
On the homescreen, once the pulldown comes down, even when pulling down for a second time to fully expand the ui (sometimes almost immediately and or even after a few seconds of not touching anything), it'll either take me right back to the home screen (like I pressed the home button icon or it'll pull up the recent apps ui and I never touched anything). It is wonky.
I've tried clearing cache through the recovery method and it's still acting up when power saving mode is enabled. The only thing that seems to have caused it to stop, is turning off power saver mode.
Anyone else experiencing this issue of ghost touches with power savings enabled along with Nova Launcher's gestures (or on any other 3rd party launcher and or even the stock launcher perhaps?) on the home screen? I haven't had time to record this yet, I'll have to get some video of it, just wanted to see if anyone else is experiencing this or knows of a better workaround perhaps?
Click to expand...
Click to collapse
I use Nova with power saving mode enabled and have no issues with ghost touches. Are you using the latest version of Nova 7? How did you migrate from your old phone (backup and restore Nova settings)?
I used to have this problem with Dr. Ketan's rom but not on samsung's.
March update
abdullaHD said:
Hi, as a really fast user that needs quick actions im suffering a bit from these weird touch delay after closing apps or overlays... I tried different launchers and different apps, tried safemode and tried disabling animations nothing worked, video attached for example
View attachment 5589763
Click to expand...
Click to collapse
That's known issue with Gestures and launchers on almost all android phones. I have that issue on Pixel too if I use Nova or other launcher
Rubby1025 said:
I use Nova with power saving mode enabled and have no issues with ghost touches. Are you using the latest version of Nova 7? How did you migrate from your old phone (backup and restore Nova settings)?
Click to expand...
Click to collapse
Okay, cool. I appreciate your input. I'm using Nova 7.0.57. Yeah, I loaded Nova on the phone from my old Note 20 to the S22 Ultra. Things have been fine, no ghost touches. I noticed it happening right after I downloaded and installed the April security patch.
At first I thought it was me going too fast through everything like usual and maybe I was hitting the back button or home button or just off the screen by accident and closing out of the expanded notifications ui. But, it has continued, just not in the Samsung Internet Browser Beta anymore.
Now it's only when I'm on the home screen and I try swiping down to expand notifications, then it acts all wonky and either closes by itself and or takes me to the recents ui.
I don't use nova, but have picked up phantom touches in certain apps....this is after the April update. I would open ambivision app...in the settings menu it would exit out of settings or sub menus in the app...thought it's an app bug, but sometime when swiping down the notification bar I also get phantom swipes closing the pulldown as if I swiped up....few other appa also random swipes/gestures
termdj said:
I don't use nova, but have picked up phantom touches in certain apps....this is after the April update. I would open ambivision app...in the settings menu it would exit out of settings or sub menus in the app...thought it's an app bug, but sometime when swiping down the notification bar I also get phantom swipes closing the pulldown as if I swiped up....few other appa also random swipes/gestures
Click to expand...
Click to collapse
Yup, I thought it was just some apps that had bugs but it's happening on the pull down notifications bar and expanding the notifications too. This all happened after the April security patch update. I didn't have any of this at all prior.
I noticed it immediately after the update, I opened the Samsung internet beta browser, started browsing and had the settings ui popping up and the recents ui pop up. I thought I was just moving through things too fast and hitting buttons. Then on the notification pull downs, they started rolling back up right after I'd pull it down.
It still happens quite a bit and the only thing I've found that seems to stop the phantom touches is turning off power saving mode. Dark mode also seems to slow it down, but it doesn't always stop it. It must have something to do with being in 60hz mode instead of 120hz as power savings reduces the refresh rate to 60hz.
I also picked it up after the update. .also with the pull down of notifications etc
I also started seeing phantom touches after the Apr update - especially with Google News app. I turned off extra dim feature and now I don't get any phantom touches!

Categories

Resources