Develop Bugs

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

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!

SwiftKey not working well on 2014 Note 10.1

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

Touch screen sensitivity, shaking when holding something. (possible solution pg2)

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.

Buggy touchscreen which turn swipes into touch gestures or ignores them completely

I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.​http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.

vollekannehoschi said:
I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.​http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.
Click to expand...
Click to collapse
I fear my unit may have the same issue.
You say you bought a second one; did google not just exchange it?

They don't exchange units, at least in Germany. You have to buy a new one by yourself

Your "bad" case looks exactly like what I typically see. Sometimes it's worse; for example in Instragram, flicking sometimes results in scrolling the wrong direction.
I just called Google support to see if it's a known issue, and they said no, so I can imagine it might take multiple exchanges to get one that works.

Pixel C Touchscreen Problem
I am seeing a similar issue. Very sporadic and seem to last through reboots. It renders the touchscreen useless but the tablet operates fine as long as I just use the keyboard. It happens at least once per day. I have tried a factory reset and the issue still came back. Eventually a reboot does fix it but I have not seen any pattern to it, this morning it was a hard reset (holding the power until it rebooted) other times it was 2-3 reboots.
In my video, using the "MultiTouch Tester" app shows the inconsistent readings. XDA is preventing me from posting a link to my video because I am a new user the video ID on youtube is XplgTK3ahL0
I did contact Google and they are sending a replacement, I was hopeful that this was an isolated case.

I haven't had any issues with my touchscreen. I don't have the keyboard though

Same issue but reseting from scratch repair the problem. For how long?
Envoyé de mon ONE A2003 en utilisant Tapatalk

I have just been onto google support and had the problem while using the tablet.
When I booted into safe mode, all seemed to be well.
I have transferred accounts with the google setup and it transferred all my apps too, so I will now factory reset and setup again.

Toninho64 said:
Same issue but reseting from scratch repair the problem. For how long?
Envoyé de mon ONE A2003 en utilisant Tapatalk
Click to expand...
Click to collapse
The problem recurred within 24 hours after a factory reset. I have done a factory reset twice now. It happens at least once per day if not twice. Currently, a hard reset (holding down the power button until it reboots) has fixed it the last 2 times.

FLJ74 said:
The problem recurred within 24 hours after a factory reset. I have done a factory reset twice now. It happens at least once per day if not twice. Currently, a hard reset (holding down the power button until it reboots) has fixed it the last 2 times.
Click to expand...
Click to collapse
Thanks for that.
I insisted google did not close the case until I have tried for a few days withou any recurrence.
Will see.

vollekannehoschi said:
I have serious problems with my Pixel C's touchsreen like Ars Technica:
Our only complaint about the display is that the touchscreen on our device just doesn't work. Taps frequently go unnoticed, which makes navigation and typing on the touch screen very error prone. Scrolling is unreliable, too—swipes meant for scrolling were often interpreted as taps, which led to us accidentally opening things when we wanted to scroll past them. The high error rate makes using the touchscreen an exercise in frustration. If we were given more time with the device, we'd try out a second unit to see if this issue exists in a different model, but with the quick turnaround from receiving a device to embargo, all we can do is list the issues our unit had.​http://arstechnica.com/gadgets/2015...res-an-android-tablets-core-problem-software/
I made two recordings to show them, see good case vs bad case on Youtube. Actually the problems vanish on every second reboot. It is pretty predictable unfortunately, so I return my Pixel C tomorrow and buy a second one.
For me my problem don't look like this http://forum.xda-developers.com/pixel-c/help/pixel-c-touchscreen-issue-video-t3268729 but wanted to reference it for people googling about this kind of problem.
Click to expand...
Click to collapse
Looking at your video it almost seems as you're having issues only when your using your index finger.
Maybe your finger doesn't have enough contact on the screen. When you used your thumb the screen became "responsive"
Just my two cents. I have yet to see a video that shows hard evidence. They all show something similar where someone seems to be making contact with the screen but maybe they aren't.
Sent from my Pixel C using Tapatalk

FLJ74 said:
I did contact Google and they are sending a replacement, I was hopeful that this was an isolated case.
Click to expand...
Click to collapse
So you got already the second tablet and it still has the same problems? Or I missunderstood something?

vollekannehoschi said:
So you got already the second tablet and it still has the same problems? Or I missunderstood something?
Click to expand...
Click to collapse
Google issued a replacement order, but it has not shipped yet. I am still on the first tablet and still having the issue. (twice yesterday and once this morning already). I have a co-worker that also has one but has not seen this issue at all, he has not had to reboot his tablet since he turned it on last week.

superchilpil said:
Looking at your video it almost seems as you're having issues only when your using your index finger.
Maybe your finger doesn't have enough contact on the screen. When you used your thumb the screen became "responsive"
Just my two cents. I have yet to see a video that shows hard evidence. They all show something similar where someone seems to be making contact with the screen but maybe they aren't.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I hit more than I touch with my thumb. Beating the space key for over 15 years now leads through this I think I get your point about the evidence problem in videos, do you have a better idea to demonstrate such issues?

Google somehow made a mistake and sent me two tablets and two keyboards. The first one had this same issue. When I enabled the "show touches" option, it looked like swipes were generally being broken up into separate quick touches instead of a continuous swipe. Generally made the tablet very frustrating to use. I'm attempting to return it. The touch response on the other one is great, and the difference is night-and-day.

A hard reset does not fix this problem for me. The touchscreen isn't working correctly immediately after the reset.

vollekannehoschi said:
I hit more than I touch with my thumb. Beating the space key for over 15 years now leads through this I think I get your point about the evidence problem in videos, do you have a better idea to demonstrate such issues?
Click to expand...
Click to collapse
Use a touch tester app
like the multitouch test app in the play store

My touchscreen seems a little unresponsive at times, I play Vainglory a lot and occasionally it's not picking up quick screen presses and It's got my killed a few times, I'm now noticing this in general use as well.
It's kind of annoying, I hope this is a software issue.

I am 24 hours on my replacement tablet with no issue....fingers crossed.

FLJ74 said:
I am 24 hours on my replacement tablet with no issue....fingers crossed.
Click to expand...
Click to collapse
you have let a new pixel ? you use the guarantee ? what delay ? how works the guarantee
thanks a lot

Question Keyboard delay

Have any of you experienced a lag in the keyboard popping up in some situations. I'm using gboard on the latest update and it's so annoying I have to wait for the keyboard to come up

Seems like there's so many issues with this phone out of the gate!

vibrantliker said:
Seems like there's so many issues with this phone out of the gate!
Click to expand...
Click to collapse
It really does. I'm coming from the op7 pro and I'm starting to regret this move

vibrantliker said:
Seems like there's so many issues with this phone out of the gate!
Click to expand...
Click to collapse
I have to admit i've not come across any problems personally, although I am waiting on my Google Fi SIM (which should be arriving today) so that may change things.

My op9 pro arriving today

I too have the delay with the keyboard

are you all using the standard keyboard as I use SwiftKey and don't appear to get any issues

vibrantliker said:
Seems like there's so many issues with this phone out of the gate!
Click to expand...
Click to collapse
Give examples? I'd like to see what the issues are? Is it software related? They seem to always fix those are time goes.

ddizzy81 said:
It really does. I'm coming from the op7 pro and I'm starting to regret this move
Click to expand...
Click to collapse
Same. I'm holding off on trading in my 7 Pro until the 15-day return period ends.

vibrantliker said:
Seems like there's so many issues with this phone out of the gate!
Click to expand...
Click to collapse
No major issues for me thankfully. Only minor ones I've experienced is that the "1" and "0" keys on the keyboard have a small delay before they appear. I'm guessing edge detection is a little aggressive to make sure I wanted to tap those keys?
And taking video sometimes has this weird wobble effect in the video with occasional brightness flickering on walls for instance.
Other than this, everything is great. It will be fixed in software updates. I still haven't downloaded the latest one which said it improved video so maybe this is already solved.

I have not had any problems. Not sure if matters but I always set the phone from scratch, no copy apps or backups. The most I do is export settings and import setting for some apps.
For me, it has proven to avoid a lot of "weird" things...

Not sure if this is the same issue OP is having but I've noticed since day 1 that there is a noticeable delay when pressing or long pressing the keys on the edge of the keyboard. For example, there's about a split second to full second delay when pressing the backspace key. So that means, I have to wait for that delay and then wait again for the original delay if I want to delete whole words at once. It is super frustrating.
I did some testing to see if maybe it's because I'm using gestures and the delay may be caused by the phone detecting the edge touch and waiting for a swipe inward to go back, but that's not the case as it happens with the button navigations too.

Looks like my issue is known and has been around for a while, even though it was not present in my OP7 Pro as of last week when I switch to the 9 Pro.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

I've been using SwiftKey and haven't had any issues at all. It's the opposite actually, typing feels very fast and smooth, keyboard always appears instantly and the haptics when typing are very satisfying. Hope it gets fixed for you guys.

DashDashCZ said:
I've been using SwiftKey and haven't had any issues at all. It's the opposite actually, typing feels very fast and smooth, keyboard always appears instantly and the haptics when typing are very satisfying. Hope it gets fixed for you guys.
Click to expand...
Click to collapse
Glad to know it doesn't seem to be a universal thing, thanks for letting us know. I'm hesitant to restore to factory settings due to the time it'll take to get everything set up again, but I may have to bite the bullet soon.

ddizzy81 said:
Have any of you experienced a lag in the keyboard popping up in some situations. I'm using gboard on the latest update and it's so annoying I have to wait for the keyboard to come up
Click to expand...
Click to collapse
I've never once encountered the problem you're referring to.
I Use gboard beta (this is better anyway because it has all the cutting edge sh1t), and turn off all system animations.
Problem fixed. You're welcome.

Update: This problem seems to have went away after the latest update

ddizzy81 said:
Update: This problem seems to have went away after the latest update
Click to expand...
Click to collapse
Sadly I can't update just yet as the install fails, likely due to me flashing the EU boot image on my global variant. When I update I hope my issue is fixed. I also just realized that my issue is a tad bit different than OP's. I decided to make a short video for you all to see, link at the bottom.
I started typing in the center of the keyboard so you can see how quick and responsive it is. Then I go to the edges and you'll see there's like a full second delay until the phone picks up the touch for the key. For the scrolling, I tested along the entire edge and it was the same which leads me to believe my issue is not a keyboard typing issue, but a full screen edge touch delay detection issue. You'll see that when I start the scrolling in the center of the screen, it's quick and smooth. When starting the scroll from the edge of the screen, it initially jumps before scrolling smoothly.
I swear it almost feels like the phone detects the touch on the edge but does not register it right away and instead waits a second to see if I will then slide in from the edge to go back since I'm using gestures. But I tried using the button navigation instead of gesture and the delay is still there so idk at this point. I can confirm that this issue never happened on the OP7 Pro that I'm coming from.

elodin_89 said:
Sadly I can't update just yet as the install fails, likely due to me flashing the EU boot image on my global variant. When I update I hope my issue is fixed. I also just realized that my issue is a tad bit different than OP's. I decided to make a short video for you all to see, link at the bottom.
I started typing in the center of the keyboard so you can see how quick and responsive it is. Then I go to the edges and you'll see there's like a full second delay until the phone picks up the touch for the key. For the scrolling, I tested along the entire edge and it was the same which leads me to believe my issue is not a keyboard typing issue, but a full screen edge touch delay detection issue. You'll see that when I start the scrolling in the center of the screen, it's quick and smooth. When starting the scroll from the edge of the screen, it initially jumps before scrolling smoothly.
I swear it almost feels like the phone detects the touch on the edge but does not register it right away and instead waits a second to see if I will then slide in from the edge to go back since I'm using gestures. But I tried using the button navigation instead of gesture and the delay is still there so idk at this point. I can confirm that this issue never happened on the OP7 Pro that I'm coming from.
Click to expand...
Click to collapse
Same here. The 1 and 0 keys have a delay. I assume this has to do with edge touch rejection and it's be nice to have some settings to change this behavior, like Samsung has done (if that is the issue). Could be gestures as well with the OS wondering if you'll do a gesture, but it should not be this much of a delay. It is annoying for sure.

elodin_89 said:
Sadly I can't update just yet as the install fails, likely due to me flashing the EU boot image on my global variant. When I update I hope my issue is fixed. I also just realized that my issue is a tad bit different than OP's. I decided to make a short video for you all to see, link at the bottom.
I started typing in the center of the keyboard so you can see how quick and responsive it is. Then I go to the edges and you'll see there's like a full second delay until the phone picks up the touch for the key. For the scrolling, I tested along the entire edge and it was the same which leads me to believe my issue is not a keyboard typing issue, but a full screen edge touch delay detection issue. You'll see that when I start the scrolling in the center of the screen, it's quick and smooth. When starting the scroll from the edge of the screen, it initially jumps before scrolling smoothly.
I swear it almost feels like the phone detects the touch on the edge but does not register it right away and instead waits a second to see if I will then slide in from the edge to go back since I'm using gestures. But I tried using the button navigation instead of gesture and the delay is still there so idk at this point. I can confirm that this issue never happened on the OP7 Pro that I'm coming from.
Click to expand...
Click to collapse
I'm pretty sure it's due to the gestures. I just tested it on my regular 9, same problem, it takes a fraction of a second to realize I'm scrolling and not trying to do a gesture if I'm at the edge of the screen. Does it happen with button navigation?