I feel like I need to watch a tutorial to check what the appropriate swipe is. Sometimes I get it a bunch of times in a row. Sometimes I can't get at all for over 10 tries
My first try I had a similar experience so i deleted my fingerprint profile. I then, redid it and i used for instance my thumb and rotated it slightly each time with the swipes, i can now get it open with ine swipe most times now. Its working much better. By rotating i mean keep,it in same perspective just angle it to left swipe down, then straight again, then angle to right, hope that helps.
Related
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:
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
haitower said:
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
Click to expand...
Click to collapse
I have the same problem!!!!
Interesting, I can confirm this too.
I'm currently using OOS, did you tried any custom rom? We could see if it's rom - related.
It's an Android thing.
I don't have that problem with my 5T, on 4.7.6
morback said:
Interesting, I can confirm this too.
I'm currently using OOS, did you tried any custom rom? We could see if it's rom - related.
Click to expand...
Click to collapse
i'm gonna install a custom rom now. i'll report back!
since i guess it's more of a kernel thing, i'm gonna install blu spark or franken kernel as well.
no improvement whatsoever.
i tried:
audax rom -> no change
audax rom & blu spark kernel -> no change
oos oreo beta -> no change
i feel that the effect is worst in chrome. it is not so apparent in youtube scrolling or picture pinch2zoom. however, in chrome the whole experience is just really laggy compared to my 4y old device which is on 4.4.4 kitkat.. :/
that is so sad since i'm 99% sure this is just a software issue that could be easily fixed..
anyone of you guys who also recognize this behaviour have another android device to compare?
You are using oos custom roms. When it's software related you won't solve that problem. I'm using omni and cannot reproduce what you've written.
Trinaaa said:
You are using oos custom roms. When it's software related you won't solve that problem. I'm using omni and cannot reproduce what you've written.
Click to expand...
Click to collapse
you can't know whether it is oos related. it could also be the case that this is just how android 7.0 handles touches these days. my last device was 4.4, so maybe things changed to the worse. also, it is most likely kernel related.
i also think the issue is not recognizeable when you are not used to a 100% buttery smooth device, like my nexus with an AOSP rom was. i bet people coming from a samsung phone would have no clue what i'm talking about even when im doing it right in front of their face
the issue is most apparent when scrolling in chrome. it is negligible when scrolling through other apps, but for chrome it is annoying.
haitower said:
I have a brand new device and to me it seems that it has some sort of protection of unwanted touches in a way that it, when you touch the screen to scroll or pinch to zoom (app independent), it waits a bit until it reacts to the movement of the finger which results in a movement delay.
When I put my finger on the screen and then move it e.g. downwards it does not react instantly. It seems like it's a software setting to prevent micro scrolls when u accidently touch the screen.
I try to explain it: I put my finger on the screen, move it down, the scroll does not start instantly but after a few milliseconds and then jumps (which feels like a single little stutter) after a threshold of minimum movement has been reached. I feel that this effect is more apparent the slower i move my finger.
When i touch the screen and then move my finger REALLY slow i can even move my finger a couple of cm before the scroll is recognized and is started by jumping to the point where it should have been when there hadn't been this micro touch/move protection.
This effect is NOT present when I touch the screen, move my finger around, stop moving and then start moving it again. No matter how slow i move it, the scrolling does not jump/stutter. This effect only happens for the initial touch/scrolling attempt.
All in all this makes the device feel a bit laggy since this does not happen on my 4y older phone. however, it seems to be software related. Anyone knows what I mean?
Edit: i understand that this makes sense when using an app where u get a pop up when touching and keep holding ur finger against the screen (e.g. in chrome when u want to mark text and then get the cut/copy/paste pop up). This movement protection helps to prevent unwanted screen movement which would prevent the popup because for a popup u need to keep touching without moving the finger. However, I feel that this protection and it's resulting delay is too strong and should be reduced because it feels not so smooth how it is now.
Click to expand...
Click to collapse
I noticed this. Does feel like lag. Haven't experienced this on the pixel 2
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 hate to sound like a complete noob but does anyone else have an issue when trying to catch a screenshot using the palm swipe method? I have tested it many times and still find it "hit and miss" as to whether I catch the shot I am aiming for or simply swipe the screen across, sometimes catching a screenshot midway through!
Does anyone either 1) have the same issue or 2) have any tips?
The cover I have for the tab makes using the two button method a touch tricky, especially when trying to be as efficient as possible. I hate looking like I am grappling with my tab during meetings!
You can use the pen to take screen shots
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