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!

Multitouch problems on the Note 10.1 (updated 03/05/2014)

[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?

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 Stuttering Scrolling In Some Apps?

Anyone noticed this? Telegram and Twitter for eg, the scrolling is pretty stuttery, it's like the CPU touch boost isn't working on them?

Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?

Morgrain said:
Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?
Click to expand...
Click to collapse
Morgrain said:
Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?
Click to expand...
Click to collapse
Is this an A12 thing? The scrolling on my [email protected] for eg is a heck of a lot smoother in Twitter than on the P6P. Edit: Twitter is running at 120hz, so it can't be that.

Batfink33 said:
Is this an A12 thing? The scrolling on my [email protected] for eg is a heck of a lot smoother in Twitter than on the P6P.
Click to expand...
Click to collapse
We don't know at this point, since no other phones has A12 released yet. It might be A12 related, it might be P6 related. What is clear however, is that this should be easy to fix.

I have noticed this on P5 and a little less on this device. Android 11+12. I don't get why this happens on modern devices.

Golf c said:
I have noticed this on P5 and a little less on this device. Android 11+12. I don't get why this happens on modern devices.
Click to expand...
Click to collapse
Weird. Like I said, it doesn't happen on my s21U. It's obviously a software thing but i wonder what.

Batfink33 said:
Weird. Like I said, it doesn't happen on my s21U. It's obviously a software thing but i wonder what.
Click to expand...
Click to collapse
Did you copy your phones apps over from another device? Have you tried reinstalling your specific app? Maybe it's a glitch or bug that is caused by this. It's usually a wise idea to do a delete cache/data once you encounter problems with a certain app.

It happens on Twitter and Reddit apps for me also. It was mentioned on Verge review too.
Video:
https://imgur.com/a/WUGs0c7

Man, it's happening in more than a few apps for me. Scrolling down a page in Chrome will stutter! (And that's a system app — I can't try uninstalling and reinstalling it.) Yes, clearly a software issue, but it's not trivial. Hope they fix this; the phone is otherwise stellar.

It is not related with Software I guess because it works fluidly SD 888 from last year. I took a video about it Here is the link.
Both have android 12 and both have the same settings on Twitter app.

Lots of stutter in Chrome and the Google app for me. It's really annoying.

xantrk said:
It happens on Twitter and Reddit apps for me also. It was mentioned on Verge review too.
Video:
https://imgur.com/a/WUGs0c7
Click to expand...
Click to collapse
Which app for those graph overlay ?

I can verify that Twitter stutters for me as well

Batfink33 said:
Anyone noticed this? Telegram and Twitter for eg, the scrolling is pretty stuttery, it's like the CPU touch boost isn't working on them?
Click to expand...
Click to collapse
yep, I had this going on in my PayPal App, the display will flicker around almost violently, and I was typing so you wait a sec, it settles down type some more, etc. I made a decent feedback report on my end, with a great screen recording capture of the "seizure-like" display issue, LIVE! es

evnStevn said:
yep, I had this going on in my PayPal App, the display will flicker around almost violently, and I was typing so you wait a sec, it settles down type some more, etc. I made a decent feedback report on my end, with a great screen recording capture of the "seizure-like" display issue, LIVE! es
Click to expand...
Click to collapse
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.

NippleSauce said:
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.
Click to expand...
Click to collapse
Roger that.

NippleSauce said:
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.
Click to expand...
Click to collapse
No way you should have to do that.

awarman said:
No way you should have to do that.
Click to expand...
Click to collapse
I thought the same thing at first - as with my previous phones that had TWRP, this was never a problem. But honestly, I only just started believing in what I mentioned this past week. By February, I hadn't wiped me phone since I had gotten it in December and was experiencing the problems that you described. I thought it was a bad phone, however, after COMPLETELY wiping, then reflashing and setting everything up again the problem was resolved.
But just this week I updated my phone to the June Beta 2 / GPR3 Beta 2 (Build: S3B1.220318.003) and decided not to wipe it clean...and now I'm experiencing the annoying stuttering/temporary freeze issues yet again.
Granted, it's a beta... But I'm not too sure it would have these issues - the same issues that had occurred in the past when I wasn't doing full wipes on my phone when updating. So I suppose I'll have to wipe my phone and start over on QPR3B2 and report back with the results. I'll probably do this within the next few days.

Boom batishta said:
Which app for those graph overlay ?
Click to expand...
Click to collapse
System > Developer options > Profile HWUI Rendering > On screen as bars.

Green tint only on unlocking device - acceptable?

I bought this used s9 for quite affordable price. Everything looked fine during testing except a greenish shade which happens only when unlocked and happens for like a second.
On searching internet, i found threads, yt videos by a number of people, almost all claiming that it is an update consequence. My questions are
1. Is it a software issue? If yes, can I expect some wayto solve - official ota or root and custom or old rom (if possible at all)?
2. If not software issue, is it a software induced hardware issue? Any way to repair without paying full for display?
2.1 If i get it replaced somehow, will itcome back again?
3. In any case, if I don't get it repaired, how long can I expect the deviceto be functional; ie before this green shade becomes permanent instead of being intermittent making device unusable?
Thank you

If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?

blackhawk said:
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
Click to expand...
Click to collapse
Hahah
This is something different. I asked a reseller and he said that such displays may last anywhere from 1 hour to 1 year.
Internet is filled with such questions.
Can you please help answering other questions if not this one, like if downgrading to older android possible or not?

The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.

...

blackhawk said:
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
Click to expand...
Click to collapse
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.

tarun0 said:
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
Click to expand...
Click to collapse
Like I said if it's transient it's no issue.
This is the one I use:

Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.

spamtoaster said:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
Click to expand...
Click to collapse
Try clearing the system cache.
A hard reboot.
Try in safe mode.
A factory reset may help but if that fails try flashing to the same version. If Android 8 or lower it could be caused by a rootkit that a factory reset won't purged. However this isn't a typical symptom nonetheless the firmware maybe corrupted.
If none of the above works it's a hardware failure, likely the display.