yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
I found screen off still fixed it, it just took multiple tries. It did occur under some other circumstances previously, Tapatalk and/or Whatsapp if I recall correctly. I think it had something to do with overlays. And that's why they tried to fix/decrease it by making recents opaque.
[Samsung Galaxy Nexus] Raijin:
Recents are opaque (black) with live wallpapers. With normal wallpapers the image is shadowed in background. :)
[Samsung Galaxy Nexus] osm0sis:
Ah good to know! Didn't realize that. Still removed an overlay though I'd imagine since a static image could just be processed as shaded fairly easily. Makes a lot of sense really. Live wallpaper would require the "shadowed" overlay, so they just made it opaque on the GN.
[Samsung Galaxy Nexus] blackhand1001:
This bug has been driving me nuts. Its seems to be completely random. Everyone needs to send Google a message about this. My nexus 7 does not do this. Its incredibly annoying and gets to the point where swiping between home screens becomes non responsive unless you push really hard. I don't have a screen protector.
[Samsung Galaxy Nexus] BrUhNiGGs:
I say that I'm totally glad that I was able to switch from this phone to an S3 last summer. Been rockin this phone and it amazes me that this problem still persists after a whole year...
[Samsung Galaxy Nexus] zAlbee:
As far as I can tell, it's a hardware flaw. Our touch screens are capacitive, and the fact that turning the screen off fixes it almost seems like an electrical problem. I don't think Google or any other ROM developer can fix this. Edit: Maybe Samsung knows the answer, but I doubt they'd spend any time on the cheaper Nexus hardware compared to the money-making flagship S3/S4.

And I highly doubt any of the 4.2 background changes were to try and fix this; that's a platform-independent UI choice. Google wouldn't randomly change design elements to fix an unrelated hardware problem that occurs on only one device/platform (haven't heard about this on the Nexus 4).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blackhand1001:
That doesn't explain how this didn't occur on builds prior to 4.04 and seems to be related to what's displayed on the screen.
[Samsung Galaxy Nexus] BrUhNiGGs:
I agree as well when I had my nexus last summer. I went through 7 Like new replacements from Vzw. Every single one of them had that issue. It may be hardware/software issue
[Samsung Galaxy Nexus] solidspidey:
Can anyone running 4.3 comment on this annoying bug if it's fixed or not?
[Samsung Galaxy Nexus] matteventu:
It is generally fixed (like in 4.2), but it still appears some times while charging the phone.
[Samsung Galaxy Nexus] nolez:
It is not fixed, I have been experiencing this issue since I've had the phone, which has almost been a year now, and it never totally went away. I am on 4.3 now, but I've tried every version from 4.0 and all of them had this issue, I have even tried several custom roms, I am on PA currently and the screen sensitivity issue persists. The funny thing is, I don't get the problem when hitting recent apps button, it just seems to appear from time to time.. but it is really frustrating indeed.
[Samsung Galaxy Nexus] matteventu:
I confirm, it appears randomly but usually when connected do the wall plug. (and after intensive use).

But it is still much less present than in the previous version of Android...
[Samsung Galaxy Nexus] ribelle85:
Same. While charging and randomly also when not connected. Can be an hardware issue?
[Samsung Galaxy Nexus] matteventu:
Of course, it is surely an hardware issue, it is on Galaxy Nexus since the day-one.

But now I no longer have that problem... I upgraded to Nexus 5 :D
[Samsung Galaxy Nexus] ribelle85:
Not sure about hw issue...

http://xdaforums.com/showthread.php?p=51339077

Tomorrow I'll try cm 10.2 with franco kernel and gamma 6
[Samsung Galaxy Nexus] ribelle85:
Other exp?
[Samsung Galaxy Nexus] execute_method:
Man I wish the camera sensor wasn't borked on my oe device, it was great other than that. This one just runs like crap in general, at least I have an issue that warrants replacement.
[Samsung Galaxy Nexus] adrynalyne:
Now my wife did have this touch issue on hers; however it turned out to be a resource leak with ADW Ex.
[Samsung Galaxy Nexus] execute_method:
Do you have a good way to check for a memory leak? I've removed just about all apps, i think I'll try a different launcher. I had heard about the adw memory leak. I'm running nova though.

Did you test for the leak on your device?
[Samsung Galaxy Nexus] adrynalyne:
I do not have a good way to check, at least not scientifically. My wife handed me her phone and told me to fix it, LOL.

The screen was barely responsive, the touch keys took several presses to register. I accidently stumbled upon the ADW thing because I was messing with it and launched the stock launcher, which cleared up all of the problems. So I rolled with it ;)

I haven't run any tests on my device because it has stayed responsive for me the entire time. The only tests I have run was that multitouch tester because folks were talking about the MT bug (which I never could get to happen either).
[Samsung Galaxy Nexus] Shellhead:
I find the problem goes away when I switch from using Swiftkey 3 beta back to the stock keyboard. I'm running stock 4.04, unlocked and rooted.
[Samsung Galaxy Nexus] RogerPodacter:
Yes thus is exactly what happens. But I don't get that delay problem. Its just not picking up sensitive taps.
[Samsung Galaxy Nexus] RogerPodacter:
Yes this is it. When the bug kicks in it gets less sensitive and drops data points from the tail end of swipes that would normally be counted as input.
[Samsung Galaxy Nexus] execute_method:
I want to reiterate that I did NOT have this problem on my other nex, running the exact same rom,kernel and apps. Also, it does not happen on all roms. This is why I say it's a hardware variation, not necessarily a defect. It does however Imho warrant a replacement, because it's unacceptable.

For anyone reading this, the problem doesn't occur for me on gummy 1.2, but does on aokp, cm9, and liquid.

Sent from my (*) using Tapafux.
[Samsung Galaxy Nexus] EP2008:
Well the multitouch bug didn't affect all galaxy nexus devices and it was certainly a software bug. Same with the low volume bug and signal drop issues.
[Samsung Galaxy Nexus] adrynalyne:
No necessarily. The signal drop issue was artificially introduced by software, yes. The multitouch bug can be hardware, just like the volume issue of long ago. However, software can remedy some hardware issues.

Remedy, not fix.
[Samsung Galaxy Nexus] EP2008:
If a remedy allows us to use our devices as intended, then it's a fix in my book.

Sent from my HP Touchpad running ICS :-)
[Samsung Galaxy Nexus] player911:
Its all just quirky software. Volume, multi touch and signal are all software tweaks.

I have no problem with the touchscreen. Occasionally the keyboard will stop registering characters in SMS app but the keyboard still shows me touching the letters. The fix is to go back to the Message thread and open the conversation again.

Games and multi touch stuff never give me fits after it was patched a long time ago.
[Samsung Galaxy Nexus] matteventu:
The first crazy-volume bug WAS HARDWARE ;)
[Samsung Galaxy Nexus] execute_method:
Just wanted to stop in and say that it appears there was a hardware defect with my phone. My replacement does NOT have the problem.

Sent from my (*) using Tapafux.
[Samsung Galaxy Nexus] EP2008:
Mine didn't have the problem until 4.0.4. Do you think the update broke our screens? I still say it's a software bug, but I'm living with it.
[Samsung Galaxy Nexus] execute_method:
I'm thinking there is a hardware variation they didn't account for (ie. physically different touch screen, motherboard hardware, etc.), and some change in the software is causing a memory leak.

What I can say now is that my 1st and 3rd devices do not exhibit it. Also, that 2nd device was giving me very intermittent boot loops and I would get a system FC every once in a while.

This new replacement immediately felt faster and more stable.

All of the phones were HW rev. 9, btw.

Hopefully there will be a fix soon, for those who don't want to go the replacement route.

Sent from my (*) using Tapafux.
[Samsung Galaxy Nexus] RogerPodacter:
I don't understand how it could be hardware since I had no problems on 4.0.1 and 4.0.2, only with 4.0.4 did it start for me. And it goes away if I lock the screen.
[Samsung Galaxy Nexus] matteventu:
Simply because with <4.0.4 you had multitouch issue (hardware issue), that is corrected by software in 4.0.4, "changing" the multitouch bug to sensivity bug.

Newer hardware version of Galaxy Nexus doesn't has multitouch bug before 4.0.4 update, and doesn't have sensivity bug after 4.0.4 update ;)
[Samsung Galaxy Nexus] adrynalyne:
How can you verify if the hardware is newer, or different, if a teardown hasn't been done to compare old to new?

I reckon hardware revisions are listed in fastboot of GSM and CDMA devices alike. I'd see if there is more than one hw revision out there.
[Samsung Galaxy Nexus] tracerit:
compared to my Epic Touch 4G, i'm more error prone when using the Nexus. I"m guessing i'm not used to the sharper resolution therefore the areas to touch are smaller.
[Samsung Galaxy Nexus] EP2008:
Let me ask you a question:

In portrait mode, I have the problem with sensitivity (sometimes) on the bottom right. Assuming it's a hardware problem, why don't I have the same problem in the same spot when I rotate the screen? The problem shifts to another area when it's rotated.

This was the case with the multi-touch bug. It always affected the bottom right of the screen, depending on how the phone was rotated. If it was a hardware issue, it should stay in the same spot, no ?
[Samsung Galaxy Nexus] @rbiter:
there is a hw revision 9 and 10. no rhyme or reason to any details or where manufactured. my sister just got a galaxy nexus made in china and it was hw 9 like mine made from korea.
[Samsung Galaxy Nexus] adrynalyne:
I thought only Verizon devices are rev 9 or 10?

They kind of need to be, as they have some different internals and layouts vs GSM.
[Samsung Galaxy Nexus] @rbiter:
Could be. I dont recall if hw 10 was verizon versions or not. Could've sworn there were hw 10 on gsm version also but dont quote me on that.

...
[Samsung Galaxy Nexus] theking_13:
I also have the SMS issue, I use GO Sms and thought that it was an app related issue though.
[Samsung Galaxy Nexus] dcdttu:
I can confirm that, on certain ROMs, it was much more difficult to bring down the notification window by quickly swiping down like I normally do with no issues. I am now running AOKP Build 37 and have had no issues. I also ran Codename Android 1.6 with Android 4.0.3 and had no issues, but Codname 2.0 had the issue.
[Samsung Galaxy Nexus] cldwar:
Having the same issues ...

When i bought the phone it worked fine was on 4.0.1. But now I'm using LiquidSmooth 4.0.4 and the touch sensitivity totally ruins otherwise an awesome experience. Not a problem with the rom i have tried AOKP too, same thing happens. Many key presses are missed. Difficult to bring down the notification window by quickly swiping down etc.

I really dont think its a hardware issue cause it was working fine before .... Someone should come up with the solution ...
[Samsung Galaxy Nexus] notanoob:
Even i experienced this two days back, I'm a flashaholic but mostly use cm,aokp and black ice and i experienced it in all of the roms ... this occurs mostly when i call some one and they dont respond (where you get the line busy screen ) i have press the power button and whola every thing is normal.

currently on stock 4.04 but since this thread puts the issue with that OTA i think i will flash back to a older version and check.
[Samsung Galaxy Nexus] @rbiter:
Has anybody tried flashing the whole imm76i image and not using the ota method?

sahibunlimited picks his nose. in his sleep.
[Samsung Galaxy Nexus] nbell13:
yes, i used it after i had tried out cm9 and then decided to go back to stock. worked fine, used the toolkit.
[Samsung Galaxy Nexus] Lostpick:
So, is there a way to fix this issue ? It's software or hardware ?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] cldwar:
New findings .. . .

I am one of the user being plagued by unresponsiveness of the screen. I found that when i restart my phone, for the first 2-3 minutes the screen works fine ...!!! the keyboard doesn't misses a single key stroke. But after 3 minutes the sluggishness starts ... So someone from the Devs must take notice ....!!! gona try the PARANOIDANDROID rom once again. If I am not mistaken my phone worked fine on that rom.
[Samsung Galaxy Nexus] cldwar:
Confirmed its not a hardware glitch .... my phone sensitive just got normal .... not sure for how long .. must have to do with some sort of software I installed....
[Samsung Galaxy Nexus] delvirtud:
This worked for me as well. I was having the issue where once I accessed the recent apps menu, the degraded sensitivity began. Once I tried SGS touchscreen booster, it seems thus far that my issues have subsided. YMMV
[Samsung Galaxy Nexus] Lostpick:
I've the issue when I launch the recent apps too :(

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] boardrx182:
I wanted to provide an update based on my experiences. I can't say whether it was my ROM or Kernel, but I'm now running AOKP build 38 with Imoseyon's 3.7.0exp2-230 kernel and I'm getting great performance, great battery life, and no touchscreen lag like I was before.

I'd be curious to hear if anyone else is on a similar ROM/kernel combo and has been able to eliminate the issue. I'm very happy that this isn't affecting my device anymore, it was a very irritating problem.
[Samsung Galaxy Nexus] RogerPodacter:
Remember I think there are two issues people are talking about, lag and touch sensitivity. I don't have any lag at all. My problem is the screen suddenly misses presses unless you press harder.
[Samsung Galaxy Nexus] Lostpick:
I have the same issue, no lag..sgs booster doesn't work for me.

Inviato dal mio Maguro
[Samsung Galaxy Nexus] 1977sjr:
I have the screen sensitivity issue as well. I'm completely stock, non-rooted and locked. This just started happening after the 4.0.4 update, so it's clearly not a hardware issue for me. My screen presses were working pretty much flawlessly before the update. One member suggested the problem went away after switching from Swiftkey3 to the stock keyboard. I just did this as well and so far so good. I wonder if everyone else with this screen issue is using Swiftkey3 or not. I'll see if the issue comes back tonight while using the stock keyboard and report back...
[Samsung Galaxy Nexus] 1977sjr:
Switching to the stock keyboard seems to have solved this issue for me. I've been using my phone consistently for the last hour or more and haven't had a single sensitivity issue occur. It's running perfectly fine and as smooth as ever once again.
[Samsung Galaxy Nexus] RogerPodacter:
Well I don't want to jinx myself. But I updated to aokp 38 and so far no sensitivity issues for almost a full day. Interesting...and happy.
[Samsung Galaxy Nexus] apostolos2:
i have the same issue, i thought it was only me and my fingers
[Samsung Galaxy Nexus] BrUhNiGGs:
I can confirm your EXACT problem. I thought I was alone. I had my gnex for about 2 months now and updated it to 4.0.4 and started encountering this problem for about a month now. It seems like a multitouch problem. I've tried whatever I could too: wiped several times and locked my gnex and unlocking it, re-rooting it. I'm just now on Gummy 1.2.11 Linaro and still get this problem in which ever rom or kernel.

I can't tell if it could be my screen protector interfering since the problem persists over an amount of time I use my phone and once I lock the device and turn it back on the touch sensitivity problem is gone. And then, like you said, it comes back. The way I notice it is the way the home screen of my launcher is switched as I swipe it. I have a habit of just swiping back and forth and it looks and feels like it doesn't capture the touch as well and sort of lags as the home screens are switching.

So I downloaded Multitouch Tester from the play store while the touch problem was still there and tested the app. It looks like it is a multi touch problem as when I input my first finger and my second, the second finger 'circle' acts up and goes away if I put it near the corners of my screen.

Try this out and see.
[Samsung Galaxy Nexus] Lostpick:
I'm on rascream with trinity kernel since 2 days..no sensitivity issue for now :D
[Samsung Galaxy Nexus] kennethpro22000:
Lostpick, Ihave try your rom and kernel combination, the issue is much better, but I discover when I use chrome browser for net surfing, the issue will appear again . I have try many browser, opera mini,opera next,original browser and boat browser, the situation isthe same, so lostpick,have u try any browser that have no issue occur,thx!
[Samsung Galaxy Nexus] Lostpick:
I usually use stock browser, no problems:)

Inviato dal mio Gnex con Rascream+Trinity
[Samsung Galaxy Nexus] RogerPodacter:
I honestly think it is some type of memory leak within the systemUI apk. But I have no proof of that. Basically wherever surfaceflinger or the touch events are controlled is acting up.
[Samsung Galaxy Nexus] cldwar:
Sensitivity issue gone

Just flashed Liquid Smooth 1.5 with Franco Linaro kernel. The sensitivity which plagued my typing has gone. Everything working smoothly .... The keyboard responsiveness has increased. Dont know how but everything working smoothly. (Testing the battery life)
[Samsung Galaxy Nexus] cldwar:
Just flashed jelly bean ..... no problem of sensitivity with that too ... I think some specific version of ROM or kernel must be messing things up
[Samsung Galaxy Nexus] gasgiver:
Can anyone of you please try the following.

Get "System Tuner" from Playstore. No root needed for the test.

Start it and go to 'Events'

The list begins to build up, flip the list up and down a few times.

This absolutely always triggers the touchscreen error for me.

I do not know what to make of it, but if more of us can reproduce the error

this way we might find a knowledgeable dev that can help.

Thanks in advance

This is driving me nuts. Happens in all tested roms and kernels for me.

Even tried 4.02 stock and jellybean.
[Samsung Galaxy Nexus] XGrinder911:
Try this:

https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com

It doesn't stick though.
[Samsung Galaxy Nexus] gasgiver:
Hey, thanks for helping.

I tried sgs touchscreen booster before, unfortunately it does nothing for me.

Would you mind trying out the system tuner stuff i described ?

I need to know a way to reliably provoke the error before contacting a dev

and begging for help;)
[Samsung Galaxy Nexus] RogerPodacter:
I tried system tuner and it did make the bug happen. Under events, after it populates the list, then scroll around and touch sensitivity decreased.

I also get it from tapatalk app.
[Samsung Galaxy Nexus] gasgiver:
First of all thanks for testing Roger.

At least we can reproduce it, i started looking for something fishy in the logcat but i cant find anything suspicious.

Unfortunately im no specialist in that. Im not totally noob in linux but for life im just a little windows administrator and networking guy.

Only thing i saw was something like flushing opengl caches but this happens often so this may as well be perfectly normal.

As i wrote i tried nearly every rom and kernel under the sun (stock included ofcoz) with no luck.

And now for the worse - today i couldnt resist getting me an S3 and compared to the our GN (With Nova Prime)

this thing stutters like bloody hell everywhere.

I had never expected something bad like this. Touchscreen responsiveness is most of the time like our GN when its in its 'problem' state.

Now all im gonna try on the S3 is doing one single FW update, if this doesnt fix it @once the thing goes back for now.

But the hardware is really sexy :)

Im a little worried about the warranty when rooting and trying Roms and Kernels on the S3, and also am tired of flashing at the moment.

Sometimes even i just wanna use my gadgets.

Now how frustrating is that ... :(
[Samsung Galaxy Nexus] BrUhNiGGs:
God damn this issue really bothers the **** out of me. I might have to return to stock 4.0.4 and bring it to the Verizon store for another Gnex. It really seems like a hardware problem and a software at the same time. Issue goes away if lock the screen then it comes back like a minute later. VERY IRRITATING. Ive tried every rom and kernel and problem persists. Could it be my screen protector?
[Samsung Galaxy Nexus] petrsiri:
Same problem here with stock rom 4.04 and I am not using a screen protector...
[Samsung Galaxy Nexus] BrUhNiGGs:
Thanks for confirming that because I was about ready to peel off my screen protector and crumple it. It feels like this issue is getting worse for me. The thing is, I don't want a "like-new" replacement shipped from Verizon. Its probably going to turn out much, much worse (from my past experience)

I'm using Jelly Bean and it is said that touch responsiveness should be a lot better. And after that, this proves that my Gnex is **** since the problem persists actually more often than ICS.
[Samsung Galaxy Nexus] petrsiri:
Sad to hear that jelly bean didn't solve it. I was counting on it. Has any of the posters of this thread found a rom where no sensitivity issues arised?
[Samsung Galaxy Nexus] RogerPodacter:
I'm not convinced a new phone would help you anyway, I think its a software issue. The screen physically is capable of being extremely sensitive. It just loses its sensitivity every few minutes. So it works. Seems more like some driver memory leak thing.
[Samsung Galaxy Nexus] BrUhNiGGs:
Im not so sure since only a few actually encounters this problem. I did a little testing on my dad's Gnex and the problem doesn't/never occurs.
[Samsung Galaxy Nexus] gasgiver:
OK, i spent the nearly the whole weekend with getting my new S3 so smooth and fast as the Nexus with mixed success. Finally i chose to keep the Nexus and will give back the S3.

As a last resort i tried yet another ROM (TeamGummy 1.20) on the GNex and there finally is a ROM which doesnt produce our error, at least not for me.

But despite this fact, something must have gotten a "little" broken over time in my Nexus. Maybe timings changed due to HW getting older, but im no engineer...

The problem was totally absent when i got the phone with 4.01.

I had no problems with 4.02/4.03 either. Updating to 4.04 the problem began.

BUT, downgrading to 4.03/4.02/4.01 Stock doesnt help now.

Returning the phone is a mixed bag, too unfortunately (refurbished rubbish ...)

How can we find out whats different in TeamGummy 1.20 compared to the other ROMS. In the end its 4.04 AOSP, too. How to find someone who is interested in fixing an error that maybe only a few ppl have ?

Im lost now, any Ideas ?
[Samsung Galaxy Nexus] jjc_01:
I did notice that TeamGummy had a great, speedy rom, just wasn't as feature rich as some of the other choices, like AOKP and Provision.
[Samsung Galaxy Nexus] BrUhNiGGs:
No matter what rom i use or kernel, the responsiveness issue is still there.

This. Is. Mysterious.

I. Shall. Find. Out. WHAT CAUSES THIS.

I've only had this gnex for about 3 months now and the hw shouldnt degrade so fast... I am going to remove my XO skin screen protector once my ArmorSuit protector comes in and test if the issue is still there without the screen protector.
[Samsung Galaxy Nexus] aeoveu:
I ran the phone in safe mode and didn't face this issue. When I ran it normally, the phone began to slug down at times - unless I lock/unlock.

I think I might reset the phone, and not let Google sync the settings while signing up, and manually restore the backup.

I'm running Jelly Bean at the moment. Didn't know safe mode existed in ICS.

Sent from my mini tractor.
[Samsung Galaxy Nexus] @rbiter:
How is touch sensitivity on 4.1? Mine is fine.

butter and jelly please...