Related
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
So, this seems a little odd, but while in a game (like minecraft or scribblenauts) the touch input is delayed ONLY for specific things. Typing, swiping, etc are fine, but quick tapping on in game controls is delayed. For example, in baseball superstars I can key in the player name fine, but when I go to hit the bat swing icon to hit the ball, I have a 1 second delay.
The issue is consistent, which leads me to believe there is something set in the system intentionally causing the delay.
It doesnt happen in anything else. I can type and web browse and do other things just fine. I know its not the apps because I have 2 note 8.0 devices both setup same rom and everything and the issue is not present on the other one.
Ive done multiple resets, tested different roms and kernels, stock and otherwise, and no change.
I checked with showing touch inputs in developer mode and its showing every touch in all games and apps..... its just as if the games themselves are intentionally delaying the response to the input on certain functions.
Anyone have any advice?
phoenixbennu said:
So, this seems a little odd, but while in a game (like minecraft or scribblenauts) the touch input is delayed ONLY for specific things. Typing, swiping, etc are fine, but quick tapping on in game controls is delayed. For example, in baseball superstars I can key in the player name fine, but when I go to hit the bat swing icon to hit the ball, I have a 1 second delay.
The issue is consistent, which leads me to believe there is something set in the system intentionally causing the delay.
It doesnt happen in anything else. I can type and web browse and do other things just fine. I know its not the apps because I have 2 note 8.0 devices both setup same rom and everything and the issue is not present on the other one.
Ive done multiple resets, tested different roms and kernels, stock and otherwise, and no change.
I checked with showing touch inputs in developer mode and its showing every touch in all games and apps..... its just as if the games themselves are intentionally delaying the response to the input on certain functions.
Anyone have any advice?
Click to expand...
Click to collapse
I SOLVED IT
just fyi for anyone running into similar issues.
My issue was with magnification mode in the accessibility settings. Turning it off fixed the delay. I liked the feature but im glad its no longer an issue
Even- power saver on- can cause such issues
Sent from my GT-N7100 using Tapatalk 2
phoenixbennu said:
I SOLVED IT
just fyi for anyone running into similar issues.
My issue was with magnification mode in the accessibility settings. Turning it off fixed the delay. I liked the feature but im glad its no longer an issue
Click to expand...
Click to collapse
Thanks for causing and solving the problem!
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Ettepetje said:
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Click to expand...
Click to collapse
have you tried beta 4.3
tonytownsend said:
have you tried beta 4.3
Click to expand...
Click to collapse
Am doing so as we speak type. Nope, still buggy (same bugs).
I must be using the iPad too often because I find I'm unable to select words and then, afterwards, apply strike.
Edit: It also inserts spaces after it erroneously inserted "[ strike][ /strike]" (without the spaces) at the start of the post, in stead of around "speak", making me have to edit "[ QUOTE=tonytownsend" afterwards... Hopefully most of this is solvable in future.
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying touchscreen issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds without moving them
- If the touch indicators suddenly disappear, you have the same touchscreen issues
Kizune said:
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying multi-touch issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control. Single-finger operations and the S Pen kept working fine, though.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds
- If the touch indicators suddenly disappear, your touchscreen has multi-touch issues
Click to expand...
Click to collapse
I sure hope not. I started a whole topic on the Note 3 forum because I discovered it had a multitouch problem. Haven't been able to produce that type of multitouch issue on any of my other gear besides a Nexus 7. Will check with your method to see what it gives.
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
I discovered that my fingers got remembered (stayed) on the screen if I left 5 of them on the screen. Happened only ones though. Then I tried puting my whole hand on it for a few seconds and then the multitouch algorithm went bananas. Tried with different Multi-touch app too. I think this is a software issue, from the looks of it.
SwiftKey has been giving me problems on my 2014 Note 10.1 from day 1, but they had become 10 times worse today. I just rebooted my Note and it now behaves as normal (still somewhat buggy SwiftKey, like before). I think there are some issues in the Multitouch driver which can be triggered by the "whole hand" method described above, and possibly by other means. My MT driver had already become unstable, hence I could reproduce a defect (finger touches remaining on the screen) without the "whole hand" thing.
Kizune said:
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
Click to expand...
Click to collapse
Kizune, I included your video in a topic about this Multi-touch issue, I hope you don't mind.
Of course it's okay. Let's just hope that Samsung will fix the problem ASAP, it annoys the hell out of me.
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Itchiee said:
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Click to expand...
Click to collapse
I will very probably be doing the same. Thanks for getting back on topic.
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Sent from my HTC One using XDA Premium HD app
SlimJ87D said:
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Click to expand...
Click to collapse
I use the same (Tablet) version. Possibly it is caused by a combination of settings. I have most (aiding) options switched off. If I find the time I will experiment.
Try "Touchpal"..it's similar to Swiftkey.. it's free and has plenty of thenes. I actually like it better
Sent from my SAMSUNG-SM-N900A using xda premium
Newest SwiftKey is running perfectly for me on the Note 2014. It's so nice to be able to have a compact keyboard you can undock and move from any part of the screen to another. So convenient for applications. Highly recommended, please try it if you haven't
[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?
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.