Hello has anyone experienced this?
Since last night (1/10/18) I have lost the ability to pull down the top menu using the screen.
I can still bring it up if I use the swiping function of the fingerprint reader though.
If i use the phone in landscape I am however able to pull down the top menu.
I tried rebooting several times, I also tried disabling/enabling the swipe gesture function, nothing helped so far.
Note: I do not use any launcher app.
Any idea as to what could cause that?
Just to update anyone stumbling on this post, the phone actually got worse...
The issue evolved into having the entire area of the touchscreen acting up.
Touch and swipes don't get recognized, and on the top of that the screen is tapping and swiping by itself.
Makes it really hard to use. I tried a factory reset but the issues remain.
The touchscreen digitizer probably failed...
Oh well I started an RMA with Google, should get a new phone with 5 days.
Cheers
Related
This has been an ongoing issue for me since the previous update (not the most recent one from the past couple of days.)
Most of the time, when I go to swipe down to mute or unmute notifications, there is no response until I'm almost half way down the screen.
When I reach the bottom, it just isn't enough to trigger mute/unmute. I have to wildly swipe and after a minute or so I will finally get it to catch.
Normal touch inputs are fine, no matter where I touch the screen. Just this one action seems to be my issue.
Is anyone else having this problem? Any thoughts or ideas?
I've tried factory resetting a few times but that hasn't solved it.
Thank you.
My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.
I've noticed since going to the official Android 10 update and then the October update, if the phone sits idle for a while the the back or home functions stop working (both with gestures and the pill). I can open other apps from the notification pull down and navigate forward. I also cannot pull up the keyboard. I tried to submit a log file to Google but Google requires me to type a description of what happened and I can't do that. The only option is to restart the phone from the power menu. Once that happens it's back to normal functioning. This has happened at least 5 times. Has anybody else experienced this?
Sent from my Pixel 2 XL using Tapatalk
Yes! This has been driving me crazy since updating to 10! I finally got fed up and came here looking for answers.
For me it doesn't seem to have anything to do with the phone being idle. It seems to happen after playing video (or potentially other full-screen things, like a game for example). Not sure if it's related to going full screen or maybe going landscape.
When it happens, it seems to only be the home gesture. Back works fine (and sometimes I can keep doing the back gesture to get out of it)
Restarting is usually the quickest way to fix it, but if I don't want to restart, I've found that if I go to settings and switch to 3-button nav, the home button will work again. With 2-button nav, home still doesn't work but multitasking does. Very odd.
I'm suffering from the same problem. I had to switch back to the pill but I've gotten so used to gestures that the pill is tedious.
demarcmj said:
Yes! This has been driving me crazy since updating to 10! I finally got fed up and came here looking for answers.
For me it doesn't seem to have anything to do with the phone being idle. It seems to happen after playing video (or potentially other full-screen things, like a game for example). Not sure if it's related to going full screen or maybe going landscape.
When it happens, it seems to only be the home gesture. Back works fine (and sometimes I can keep doing the back gesture to get out of it)
Restarting is usually the quickest way to fix it, but if I don't want to restart, I've found that if I go to settings and switch to 3-button nav, the home button will work again. With 2-button nav, home still doesn't work but multitasking does. Very odd.
Click to expand...
Click to collapse
I'm having the exact same problem as you. It seems to always happen when I'm playing something full screen in landscape mode. I've just been restarting my phone each time. Thanks for the info about switching back to the three button. There are times when I'm in the middle of something and restarting is just inconvenient.
I did a factory reset 2 days ago and it hasn't happened since. I did not use any backup except for phone calls and text messages.
Sent from my Pixel 2 XL using Tapatalk
Yeah it's random with me at times the back button becomes useless. Thanks Google for this bug. I can't reset my phone every f time!
Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?
Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?
I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.
Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem
I'm having problems with my Fold 4 not registering taps. I tap a space on the screen and nothing happens. I do it several more times, and finally it responds. I haven't seen a clear pattern yet, because it's somewhat intermittent. Has anyone else seen this problem?
I'm slightly suspicious of the Microsoft launcher here., but I suspect that's because it gets the majority of my taps, it being the launcher. I haven't had that problem in the past.
Just a minute ago I sat down to make a video of what I was seeing in case I thought an exchange might help. It happened on the first try, and I wound up having to press it five times with escalating pressure to finally get it to react. For the record, I have not seen a correspondence between pressure and the problem. I think I just naturally start pushing harder and when it works, it feels like it was more pressure. But when the problem isn't occurring, it takes very little pressure to register a tap.
Not using the Microsoft Launcher, but I am using SwiftKey, and I do have the same issue, especially with the space key. Mostly with the outside screen BTW.
Ah, I should have been more specific. Yes, I've only seen the problem on the outer screen so far. And I'm using gboard for my keyboard.
I've had a similar issue but it seems to have gotten better. Being intermittent makes it hard to pinpoint
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
ggrant3876 said:
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
Click to expand...
Click to collapse
I actually did an FDR last yesterday to try and solve the problem. Naada. It was still there for me.
I'm currently using Samsung's OneHome UI to see if it's something with the MS Launcher. Good god, I hate their launcher!
It feels like the sensitivity on the outer (cover) screen is too low, and combined with much smaller keys on keyboards (I use GBoard) there are plenty of missed hits and no response. Try turning on touch sensitivity and see if it improves ( Setting -> Display -> Touch Sensitivity. Mine went a tad better. I also changed the layout preferences to 'normal' keyboard height and most of my misses are now gone..
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
I've got same issue that a tap on a app gets no action. Happens occasionally. Must be a bug.
After a factory reset mine has come back too. Hopefully we will get some bug fixes with the September security update.
imanony said:
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
Click to expand...
Click to collapse
Same. I never have a problem in application, it's only when I'm interacting with the launcher.
I think the issue is with the refresh rate dropping. I used the galaxy max hz app and increased the base hz on the phone and I'm noticing response being much better now.
I also have this issue on my Fold 4's cover screen. I've always used the debug option to show where I touch, and when my touches don't register I still see the touch indicator, so I can only assume this is a software issue not deciding what to do with the touch. I think One UI might be overly sensitive for gestures, and detects taps as drags/swipes. A mini swipe on an app or folder on the home screen for instance won't do anything (which happens to me frequently).
I've had that problem quite a few times as well, not enough to drive me crazy but enough to be slightly annoying. It only happened when taping on the bottom of the screen. It often registered my taps as a swipe up. I saw the homescreen starting to go up slightly as if it was going to enter the drawer. Then one day I realized it was my way of tapping the screen that was the culprit. The way I hold my phone makes me ever so slightly swipe up as I tap the screen, but only when taping the bottom part, if I tap anywhere else, I don't tend to move my finger up as I tap. Of course, I'm talking minuscule amount of swiping here, probably less than a millimeter. It's just the way I hold the phone and move my thumb, it's personal, and I think everyone is going to have a different experience depending on how they hold their phone and tap the screen. Anyway, I'm not saying "you're using it wrong", because I think it's a problem samsung must fix, as I don't have that problem on any other phone. Probably too sensitive. I just tried to reproduce the problem as I write this message, and succeeded twice in less than 20 tries, so definitely the problem is still there. It's just that now I tap straight on instead of "sideways", and it works just fine. Just a workaround, I know...
Edit: on the cover screen, of course. Inside screen works fine with crooked taps.
Glad im not the only one. On the outer screen i have had times where I have to tap something 3 times for it to register... I never had this issue with my Z Fold 2