Hi Guys,
I think this has been already asked before but i did not a get a perfect solution for this, i brought a the Note 2 and i tried using the s Pen and found that when even not touching the screen in the apps/home screen if i scroll left and right it scrolled the page just like that, i did not even touch the screen for it and it worked to scroll the pages just like that with 2 cms away from the screen and the next day when i try to hover it, its not working like that, it asks me to touch the screen in order to scroll the pages or hover it to the corner of the screen to show the arrow mark where it scrolls (even here i don't have to touch it), i saw lots of videos , and everyone are trying to touch the screen and move it, and as everyone said , we need change that potentiometer and things, even i tried that and its not working. please clarify me, will i be able to swipe screens left and right without touching it, like before, or its a setting i have changed or i have a issue with S pen, i am totally confused, help me out guys.Thanks in Advance.:crying:
This is my first post here. I searched but didn't find anything like this. I posted on another site and nobody could help.
Ok so I just got my M8 yesterday and so far love it. However I have found a small issue that really bothers me. For some reason when on the lock screen gestures, if I swype left to go to home screen it always takes me to the screen just to the right of blinkfeed. I have changed my home screen and reset it so that my home screen is in the middle of two panels. (Blinkfeed is two to the rignt). However regardless each time I swype left on lock screen it takes me to the (what was the default) panel where the home screen used to be.
Anybody else experience this or know how to fix?
bump
Sometimes when you scroll down to the end of a list and swipe one more time, it bounces back up with the same speed. This drives me mad. It happens systemwide and in third party apps. I know that the original Nexus 5 had a similar bug some months ago, but it was fixed with Android 6.0 I think. I hope this gets fixed in a future update. Will Google fix this problems? /I have a problem with the behavior of the touch screen when scrolling top or bottom. When I scroll bottom a few times a touch screen is beginning to think that I Scroll top. It happens rarely, but terribly annoying. For example, when i'm scrolling top the settings menu, it begins to scroll down suddenly. Sorry for my english
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