Related
Hey all,
Focus owner here. I've noticed this really annoying issue with my WP7 and was wondering if anyone else is seeing it. Every now and then, when I am scrolling the browser, or specially in Adobe PDF reader, the device would detect a single scroll touch as a pinch zoom :/ Suddenly, as I am scrolling, the page would zoom instead.
Anyone else get this? I am trying to figure out if it's an OS issue in general or if I have a bad device that I need to get replaced.
Thanks!
HTC 7 Trophy here, haven't experienced that. sounds like a dodgy?
make sure that the hand holding the phone does not have a finger accidentally touching the screen
nazeeh said:
Hey all,
Focus owner here. I've noticed this really annoying issue with my WP7 and was wondering if anyone else is seeing it. Every now and then, when I am scrolling the browser, or specially in Adobe PDF reader, the device would detect a single scroll touch as a pinch zoom :/ Suddenly, as I am scrolling, the page would zoom instead.
Anyone else get this? I am trying to figure out if it's an OS issue in general or if I have a bad device that I need to get replaced.
Thanks!
Click to expand...
Click to collapse
Maybe you have a cut on your finger or a dimple that the screen detects as two fingers.
Nah, no cuts or anything on my finger now that I see that no one has it, I will pay more attention to what repros it. I was chalking it off as a glitch in the OS. It can be really annoying sometimes.
Thanks guys
No touch issues
nazeeh said:
Nah, no cuts or anything on my finger now that I see that no one has it, I will pay more attention to what repros it. I was chalking it off as a glitch in the OS. It can be really annoying sometimes.
Thanks guys
Click to expand...
Click to collapse
Can't duplicate that on my Focus...
Good luck.
I've seen it on both my EVO and my HD7, only to find the corner of my hand was touching the screen. Otherwise no issues here with multi-touch.
It's happened a couple of times on my Focus, not enough to be a problem. I can't really reproduce it on purpose but sometimes my finger will slide VERY slightly when I go to tap something (a link in explorer for example) then I get a zoom instead. It rarely happens so it doesn't bother me at all.
Never had that on my HD7
I'm experiencing the same issue on Omnia 7. It's a software bug rather than hardware flaw IMHO.
Never happened on my Focus.
Try avoiding double tapping. From experience a double tap is a zoom shortcut, unless an app specifies an action for it.
[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.
i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.
It happens to me too just like you see in the youtube video.
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.
atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.
Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.
Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.
I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app
I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?
Here's the thing. It's not a big deal but it's annoying. When I put my finger on the screen to hold something or slowly scrolling the screen, or more accuratly the item I'm holding, starts shaking sometimes very faintly.
Could there be a driver issue, too sensitive? I enabled pointer tracking in the dev options and the numbers jump around sometimes when holding something. So i guess that could be the problem.
Btw only happens with my fingers not with the spen. Maybe my fingers are too thick? Can you guys reproduce this? Its easy to reproduce with a solitaire klondike game where you have to move cards around.
[e] Just FYI: My device does not have the multitouch issues described in this thread: http://forum.xda-developers.com/showthread.php?t=2491690
Yeah I just recreated it on my device too - tbh I haven't noticed it until now so it doesn't bother me at all. But yeah probably is just too sensitive at slow scroll but no real idea tbh.
Yeah that's what I was thinking. The driver is just very sensitive and that's probably needed for S-Pen I guess.
In normal use I don't even notice it anyway but I was playing this card game and while holding a card for a while thinking where to put it I noticed the faint shaking Thx for the quick answer.
Could some more people test this? I'm wondering if all devices have this or if it's only some. I've read it might be related to temperature, as in if the touchscreen gets too cold it starts acting funny. Oo.
I have it also... I found it yesterday when I used stock browser. I wanted to mark some text and holded finger on, it started to shake a little.. But for me it is not annoying.. and I think that is kind of characteristic for this "S-pen-able" screens..
Thx You know I have the tablet for almost a month now and I'm trying to find out if there are any issues because I can't live without root any longer. So far no issues at all and it seems this shaking thing is just a common driver/spen issue nothing that might be a possible warranty case (other devices have it too, google told me so)
Think I'm gonna root this baby!
heh.. I understand you very well.. I rooted mine two days after bought.. I can not imagine using it without root. Of course I tripped knox
Happens with me to when playing solitaire but like you say, not with the s-pen.
Same problem
When you hold the icons for example to move them they start shaking rather erratically, for me it was very annoying as this does'nt happen on Note 3. I check several devices. I don't know if it is a fault with the device or the driver. I tend to read alot as well at it makes scrolling text up and down quite annoying as well.
So the interesting question now is if there are people having absolutely zero shaking
But i suspect it's the driver that has issues with big touch points because it's tuned to the small tip of the s pen. Maybe the high resolution makes it different from the notes? But I'm just speculating, don't know enough about how these wacom digitizer work...
If you enable pointer position tracking in dev options you can see how the pointer position is jumping around more the bigger the touch point is. If you put your whole finger on the screen things tend to get more jumpy. I think this should be fixable with a driver update.
Btw I did a soft reset (holding power button for 10secs) and since then it seems that it has gotten better. Weirdly enough but that might be placebo... so..
OK I think i have isolated the issue. I've been to a store today and compared with a note 3 that was on display.
I used the "show pointer location" debug in the developer options for analysis.
On my note 10.1 2014 even though the spen is docked it still registers pressure somehow. Shown as "prs" in the top bar that appears when you enable pointer location. The pressure using just my finger as input fluctuates between 0.00 and about 0.15 even without spen! Where it should be at a steady 1.00 without spen.
That is exactly how it works on the note 3 (and all other android devices without pressure support like my sgs3). If you use your finger it sticks to 1.00 and when you use the pen it scales between 0.00 and 1.00.
Now on our notes normal touch input with finger only registers as very low pressure (~0.15) and I'm pretty sure that causes the shaking.
And what I conclude from that is that it should be a simple software fix in the driver to correct that. Finger = 1.00 prs. Any way to let samsung know about this? Or maybe even a dev could try to fix that in a custom rom?
clouds5 said:
OK I think i have isolated the issue. I've been to a store today and compared with a note 3 that was on display.
I used the "show pointer location" debug in the developer options for analysis.
On my note 10.1 2014 even though the spen is docked it still registers pressure somehow. Shown as "prs" in the top bar that appears when you enable pointer location. The pressure using just my finger as input fluctuates between 0.00 and about 0.15 even without spen! Where it should be at a steady 1.00 without spen.
That is exactly how it works on the note 3 (and all other android devices without pressure support like my sgs3). If you use your finger it sticks to 1.00 and when you use the pen it scales between 0.00 and 1.00.
Now on our notes normal touch input with finger only registers as very low pressure (~0.15) and I'm pretty sure that causes the shaking.
And what I conclude from that is that it should be a simple software fix in the driver to correct that. Finger = 1.00 prs. Any way to let samsung know about this? Or maybe even a dev could try to fix that in a custom rom?
Click to expand...
Click to collapse
Verified on my P605. Probably the same cause of the problems I see when playing Angry Birds...
I've noticed that when I hold things down or. Put my finger on a Web page
Sent from my SM-P600 using XDA Premium 4 mobile app
Good thinking. I'm in the process of sending my tablet in to Samsung for this reason. I have no clue how to fix this, but I'm glad someone is looking into this. Thanks! I think this issue is the same as the one we're having here: http://forum.xda-developers.com/showthread.php?t=2491690
I have this problem on mine SM-P605, notice on 1 days use and so far only with Chrome I notice this "shaking". Sometime after opened Chrome browser and top adress bar is shaking all the time. Even I dont hold the tab, the shaking stop if shut down Chrome and reopen it again. Thought it was Chrome browser issue and havent bother about it.
clouds5 said:
OK I think i have isolated the issue. I've been to a store today and compared with a note 3 that was on display.
I used the "show pointer location" debug in the developer options for analysis.
On my note 10.1 2014 even though the spen is docked it still registers pressure somehow. Shown as "prs" in the top bar that appears when you enable pointer location. The pressure using just my finger as input fluctuates between 0.00 and about 0.15 even without spen! Where it should be at a steady 1.00 without spen.
That is exactly how it works on the note 3 (and all other android devices without pressure support like my sgs3). If you use your finger it sticks to 1.00 and when you use the pen it scales between 0.00 and 1.00.
Now on our notes normal touch input with finger only registers as very low pressure (~0.15) and I'm pretty sure that causes the shaking.
And what I conclude from that is that it should be a simple software fix in the driver to correct that. Finger = 1.00 prs. Any way to let samsung know about this? Or maybe even a dev could try to fix that in a custom rom?
Click to expand...
Click to collapse
Not sure if that is the issue........
I have a GT-N8013 and a SM-P600, both units return the same numbers that your 2014 edition does but only my 2014 has the shake bug.
.
Yeah well at this point it's just a wild theory :angel: could also be something else that is causing the problem and not the prs thing. But I'm pretty sure it's the driver being too sensitive or not accurate enough with finger input.
But we'll have to wait and hope for samsung to fix it with an update i guess. I just hope they are aware of the problem...
clouds5 said:
Yeah well at this point it's just a wild theory :angel: could also be something else that is causing the problem and not the prs thing. But I'm pretty sure it's the driver being too sensitive or not accurate enough with finger input.
But we'll have to wait and hope for samsung to fix it with an update i guess. I just hope they are aware of the problem...
Click to expand...
Click to collapse
I also think it is software and not a hardware issue.
.
hardware problem
I think it's a hardware problem because I replaced it to another unit and it doesn't have the shaking problem now. Although there is a dead pixel now.
hmukarram said:
I think it's a hardware problem because I replaced it to another unit and it doesn't have the shaking problem now. Although there is a dead pixel now.
Click to expand...
Click to collapse
Same Firmware and everything? I know that the nexus 7 had similar issues and it was fixed via software update so I really hope Samsung will release a new firmware soon.
From all the information I've gathered so far I can't see how it could be a hardware issue. It's just too sensitive when you use your finger and the driver is buggy in other ways too(see multi-touch issue thread).
If not it should be covered by warranty anyway. But seeing how many people have the issue just here on xda (small sample size), that would be extremely bad quality assurance for such a flagship device.
Is anyone else having issues with what appears to be dead areas when scrolling, swipe texting or otherwise using your phone? In typing this message the phone just lost my finger on 4 occasions. When scrolling webpages it often just stops and clicks an area where my finger was. I'll get occasional double clicking on things when I do try to click. I have trouble purposely replicating my problems but in regular us it is driving me nuts. Because I can't constantly replicate I'm not sure trying to take the phone back will be successful. Anyone else having issues? Could there be something I'm missing somewhere?
Sounds kind of mean but I hope your issue is isolated. I saw the ifixit teardown and the ease with how the digitizer came off of the glass has me worried about the longevity of the digitizer.
Happening to me insanely often on my regular Pixel.
This happens to me occasionally. Sometimes, when typing it spams v and b. If I find anything I will fill you in.
Yes, I'm having this problem with my Pixel. It happens across all apps, even in Settings. Generally it happens if I start scrolling after not touching the screen for a little while.. for example when reading a news article. The scrolling freezes, and I can move my finger around on the screen and it doesn't react, but then it might pick up my finger again and the screen jumps around or clicks on something even though I've not lifted my finger from the screen. I tested it in safe mode and it happens there also. I even got my original device exchanged, and the same thing happened immediately on the new phone. I've been in touch with Google Help this morning and they've confirmed it's a software issue. They've asked me to submit a bug report. It'll help them if more people report the bug though and they have more data to fix it, so if you're experiencing the same issue, please report it! You can chat directly to Google support through settings on your Pixel.
Haven't had any issues but I know the google keyboard can be a bit glitchy at times. I used to have a nexus 6P and I would get weird issues with that keyboard as well on that phone. Getting them less on my Pixel though.
Having issues with typing on my 6P, it's so odd as sometimes I can not type when in desktop mode and sometimes not when in mobile. Switching the webpage screen mode and also doing a soft shut off on the phone and coming back both fix it temporarily. Thought at first using a different keyboard app might help but what app it runs does not solve the problem.
Same problem here. Google pixel
Happening to me as well. Did a factory image flash and it seems to have helped but still happens once in a while. I notice it the most when I'm using reddit sync. Seems to just happen too frequently.
Just an update on this... After doing a few steps suggested by google tech support like, test on safe mode, factory reset using bootloader method, etc... They just replaced my unit. I'm using a new one today and problem is not existent now. I would assume the problem would be hardware.
To be honest, I'm quite happy with their tech support...24/7 support and the staff are really competent. This in my opinion, is worth the high price of the pixel. Good job google!
I have the standard Pixel, and I too had issues with typing (occasionally wrong letters or spaces would register), and dead areas in the top corners of my screen when trying to open apps. I was going to return it one day after confirming that the dead areas at the top of the screen were persistent, but for some reason I decided to grab an App from the bottom of the screen and move it by sliding to the top area. Instantly this cured the dead area issue, even after I moved the app back to the bottom of the screen. It's as if it recalibrated the touch sensitivity vertically as it stopped erroneous spaces when typing too.
Pixel 2 one handed thumb scrolling issue
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.
Newpixel2 said:
I have the pixel 2 and I have intermittent scrolling issues when I hold it one handed and try to scroll with my thumb. I realized it's because the base of my thumb is brushing the opposite side of the screen and preventing it from scrolling freely.
Click to expand...
Click to collapse
You should probably post about that in the Pixel 2 forums.
I've had this phone for about 5 months now and one thing thats been bothering me for most of the time is the phones touch sensitivity. Lately also it appears to be getting worse.
Phone is completely stock
I am on Pie and I have the newest update.
I am not rooted
I am not using a screen protector
I do not have huge hands or particularly fat fingers
first I don't use a lock on my phone, so I swipe up to unlock it. Most of the time it take multiple swipes to unlock, most of the time its 2 or 3 but sometimes up to 5 if not more. Is this livable sure but let me tell you it's getting really really annoying after just 5 months.
Scrolling on the phone has always been odd, it feels choppy at times, especially when scrolling in apps like facebook or the browser, scrolling outside of apps seems ok. Its like it's missing some of my inputs or applying some sort of acceleration or deceleration based on how fast you swipe and its just doing it poorly. Now again this is just an inconvenience but still...coming from a Note 8 the scrolling was always smooth..never once did I notice it being choppy.
So these two I just chalked up to how the software was implemented..it was what it was
So fast forward to now....I'm noticing even more issue with the touch sensitivity....words dont type right , I often miss spaces when typing, I thought it was my bad typing but now I really think it's missing some of my inputs because its worse than just my bad typing. The worst is when I go to correct words and hit the right word on the top of the keyboard is misses the word. It doesn't always put it it..it misses the touch and it does this a lot.
If I try to highlight something it will at times highlight the wrong row or word...every now and then it will highlight something not even close to what I was trying to highlight, like another part of my hand accidentally touched another part of the screen, but it didn't. I try to duplicate this when it happens and I cant.
In the same vein, sometime I touch something on the screen to open a link or something like that and it will touch something else close but not what I was trying to touch, again sometime something not even close will register like I accidentally hit something somewhere else...again I cant duplicate it.
It will register touches when I'm not touching the screen, just holding the phone....I think maybe I accidentally "touched: the edge of the screen but also I can never duplicate the action
Im at a point here to I feel like there is either something wrong with the screen on my phone or I need to turn to rooting to see if the issue really is software and maybe its been fixed by the community.
I came here to check about rooting but I thought I would ask the question first and see what people thought about the issue. I did a search and there definitely seems to be others having similar issues and a lot of those people seemed to be having screen issues. So maybe it really is a hardware issue and I should just skip the root and talk to google?
I have almost the same issue. Any solutions !?!
Try a factory reset and see if that helps any. If it doesn't, contact Google; a warranty replacement may be in your future.