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.
Related
I noticed after upgrading to Lollipop that it was difficult to navigate menus near the top of the screen in some apps. I turned on the "pointer location" option and sure enough I found very strange results.
i.imgur com/tPdVowo.png (you'll have to add a period after the domain name, new user status prevents me from posting links)
This first screenshot is me running two fingers all the way to the top of the screen, and once i reached the top i ran them towards the edge of the screen. As you can see there is an area where the pointer location bugs out.
i.imgur com/bh5hWeV.png
This image is just a single finger running horizontally across the top of the screen. The top line is where my finger actually was, but the phone also registered extra touches as you can see from the line below. There's even a section where the top line didn't register at all.
This is a Verizon phone, never been rooted, and hasn't been dropped or wet. I noticed while making this post that the area i am having issues with aligns almost perfectly with the top part of Sense's notification menu.
Is this normal or do I need to exchange my phone?
I am having the same issue with my phone. When I turn on show touches in developer options or install a multitouch test app, it'll show an extra touch just below where I'm touching but only when I'm touching at the top of the screen. Stock lollipop, never rooted, no water damage.
Bump
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
bumbarush said:
same problem. do you have s-off? downgrade firmware and rom - maybe this fix problem?
Click to expand...
Click to collapse
I don't. I didn't want to do that yet. Was hoping to see if anyone else had the issue and if they were able to resolve it.
Just want to see if anyone was able to resolve this issue.
fixed!
we need the old piezo lighter's element. The phone must be turned off. A few strokes on the screen near the problem area, and voila, the screen works again. Do not be afraid, the phone will not be damaged
i
on russian:
http://4pda.ru/forum/index.php?showtopic=496511
I'm facing a weird issue with the Z5P touchscreen (tapping) action on the top left side of the screen panel, the usual location for the (back arrow <-) or the (Menu Icon).
1- after reboot everything works fine
2- after an hour or so, sliding (for example the facebook chat head) is detected over this area, but leaving it then tap to open is not detected, same happens with any application back arrow or menu icon, even the (back) of the settings for example.
3- in landscape mode the same area (the top left side) is not detected when tapping over, although the touchscreen panel location is changed now its at the top right, as i rotated the device clock wise
4- after reboot every thing works fine for an hour or so, then the issue is back.
tried the services test, the sliding touch is detected allover the screen, but at the (tap test) tap is not detected at box no# 1. this is weird for me as if there was a problem in the touch sensor, the problem should exist at the same location, even if i rotate the device, but it stays at the (back) arrow when the device rotates.
tried PCC software repair with no luck so far.
The Fix:
Facebook Messenger was the cause for this issue, by removing it the issue is gone immediately without even a reboot
Did you try disabling chat heads to see if it was only a chat heads problem? Because I have messenger installed and I don't have this problem.
thanks man, works like a charm
Hossam.Abdelsalam said:
thanks man, works like a charm
Click to expand...
Click to collapse
unfortunately, the issue occurred again even the chat heads was disabled
Just delete the facebook messenger app. Must be a bug. That's the only way I got my problem to go away.
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
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
marshle said:
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
Click to expand...
Click to collapse
I tried to replicate what your talking about. However, I couldn't do it. Maybe because I'm using Nova launcher, which may be a viable option for you. A factory reset might be helpful, however, we all know how much fun that ISN'T! Definitely an interesting issue your having. Then again, I think these devices have a mind of their own at times ?
Thanks for your reply. Forgot to mention, I have tried safe mode and done a factory reset and it did not remove the issue. It seems after a factory reset you are still on Oreo 8.1, so I'm not able to confirm it the issue exists in 8.0. I also have tried Nova Launcher.
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