yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] alves.paa:
Which ROM do you use? Paranoidandroid seems to be less prone to trigger the bug using the recents button, but you can still easily reproduce it by playing Rayman or World of Goo.
[Samsung Galaxy Nexus] osm0sis:
All the real info is in the last 3 pages, so check them for more details.

Alright, in short: Screen sensitivity issues arise after the recents button is used or certain apps dim the screen. This doesn't happen for all devices, I imagine it's a spectrum-like Bell curve or something: Some people have it all the time, some people only have it when there is a tempered glass screen protector on exacerbating it, and some people don't have it at all.

Screen off-on aleviates the problem temporarily (which truly shows it as a device issue and not one of the protector for those in the middle group), and omap4 gamma contrast to 6 or above (5 is default), 1.2 in franco.Kernel, is commonly reported as a more semi-permanent work-around. I brought up the idea of rolling back our device binary drivers to see if we could fix the problem, but we only have graphics binaries, not touchpanel so it didn't make sense at the time; but, since the omap4 gamma thing works, maybe there is a possibility graphics drivers could fix it.

metal571 and I extracted the ICS 4.0.3 binary drivers, nothing older than them work, even in ICS 4.0.4. And even they don't work in JB. So what I want to test is if the 4.0.3 binary drivers fix the sensitivity issue for ICS 4.0.4. If they do, then maybe we can figure out which file in particular fixes things and possibly bring that forward to JB and have it work where the full package doesn't, OR at least direct Google Android Engineers to the fix. If, on the other hand, it doesn't work, well at least we tried, and it helps narrow down where the issue lies a little more.

To be a viable tester you must: Have the issue, reliably reproducable, both currently and have previously had it in ICS 4.0.4 (where it began according to the OP). Have a fresh nandroid backup since that's the easiest way to revert if something goes wrong.

Method: Fastboot flash the factory image of ICS 4.0.4 from Google's Factory Image page. Boot up and reproduce the sensitivity issue. Flash the recovery flashable zip of the ICS 4.0.3 binary drivers (attached). Boot up and see if you can still reproduce the the sensitivity issue. Report back. :good:

[Attachment removed since 4.2 fixes the bug! Maybe?]

You're clearly either in the area of the Bell curve that the issue isn't strong enough to noticably affect things unless there's a tempered glass SP involved, or in the group that just doesn't appear to have it. Lucky you! I assure you the issue is real, however.
[Samsung Galaxy Nexus] adrynalyne:
BAMF Paradigm or stock. Nothing else.
[Samsung Galaxy Nexus] blackhand1001:
I definitely have this issue especially in jellybean. Google better work on fixing this. We are stuck since the drivers for this are closed source. We could try pulling individual blob .so files from 4.03 and see if they still work in 4.12. I still have the issue even with 1.2 gamma. I always used that setting with Franco.
[Samsung Galaxy Nexus] scarmon25:
Since using CM and setting the gamma to 6 I have noticed a decrease in when it pops up. It seems to happen less frequent. But I have noticed occasionally the keyboard will start lagging. Usually it happens after using the task switcher and then typing for a long amount of time. If I keep typing though it starts to disappear just as slowly as it appeared. Kind of wild to be honest.
[Samsung Galaxy Nexus] osm0sis:
Best to test with 4.0.4 and the binaries from 4.0.3 first, since if that doesn't work there's no point in trying to get them to work in JB. I'd test it myself but I'm in the middle group and took my SP of the other week due to lift issues at the curvature.
[Samsung Galaxy Nexus] solidspidey:
Looks like this thread is dying :( maybe 4.2 will have a fix for this bug.
[Samsung Galaxy Nexus] osm0sis:
Heh, yeah. Nobody apparently wants to help see if we can figure out a solution even though I made a pretty clear plan up there...

Franco's latest nightly r298 also has the weird side effect of making touchscreens seem more responsive (including soft keys), as reported by myself, yellowdie and franco himself. So everyone should give that a spin too and see if it might help this issue. Really though my exploratory idea above is the best route forward we have other than vainly hoping, so someone who had the bug in 4.0.4 should really think about stepping forward and helping the community.
[Samsung Galaxy Nexus] \m/aximuS:
This bug is killing me. Does not appear any solutions?
[Samsung Galaxy Nexus] metal571:
The current fix that I've been using is changing the DSS gamma via the Trickster MOD app that you can get for free in the Play Store. It lets you change any kernel's settings for the most part on the GN. Set the gamma to 6 instead of the default 0 and the bug will go away by about 99%. Sometimes it still creeps up at random but it's so infrequent that you'll be fine, especially if you lock and unlock the screen often enough.
[Samsung Galaxy Nexus] osm0sis:
I'm still stunned nobody wants to help test for a possible fix. :mad: It's not dangerous at all, just need a nandroid.

Or perhaps nobody cares anymore since they're all just going to upgrade to an N4? ;)
[Samsung Galaxy Nexus] JediNinjafication:
I offered if would get me up to speed as i don't want to sift thru this entire thread

Nm...i am 4.1.2

*Step Away From The Toolkit And NoROM Gets Hurt*
[Samsung Galaxy Nexus] \m/aximuS:
I can help test. But I am bad understand English.
[Samsung Galaxy Nexus] osm0sis:
No sifting required. Read my posts on this page alone and you're pretty much up to date. 4.1.2 has nothing to do with it, all I'm asking is you make a nandroid then flash back to 4.0.4 since that's where our testing has to take place. If you want to help, the instructions and flashable zip are in that post of mine that I quoted, very simple. It's neither hard nor dangerous, just requires a little bit of time. I'd do it myself if I could; I already did the legwork to see which binaries work on which versions, I just need someone with the bug in severity (since I don't) to do the next part.
[Samsung Galaxy Nexus] hp13:
I will help. tell me what to do? should I flash stock 4.0.4? I had this issue for the longest time. so let me help the community :D

Edit: I am flashing stock 4.0.4 and then I will flash the attached file of binaries. I will report back.

Sent from Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Everybody should thank this man! This is what XDA is all about and what any dev or bug thread should look like.

@hp13: Make sure you can reproduce the bug in 4.0.4 before flashing the binaries, so we have our control/reference for comparison :)
[Samsung Galaxy Nexus] hp13:
i just flashed stock 4.0.4 from google and i am not able to reproduce it anymore. I did not flash the mod yet.

I am going to restart and try it few more tries before flashing that file. be right back in 10 mins.

EDIT: No more lags on stock 4.0.4. so whats next?
[Samsung Galaxy Nexus] osm0sis:
Whoops. Just saw your edit. Sorry to leave you hanging! :)

So clarify for me here, were you: a) just not able to reproduce the bug at all on 4.0.4? Or, b) were you able to reproduce and then flashing the binaries fixed it?

(b) is basically what we want to see since it means the fix is somewhere in the 4.0.3 binaries.
[Samsung Galaxy Nexus] hp13:
I was not able to reproduce it on 4.0.4. I kept everything stock. stock rom stock radio, stock kernel.

May be someone else should flash 4.0.4 to confirm it.
[Samsung Galaxy Nexus] osm0sis:
Hmm. Yeah so what we need are people who definitely, severely had the issue in stock 4.0.4 to go back and try to reproduce it with the factory image. And if they can they should follow my method to see if it resolves. This is definitely some weird stuff. Hopefully if we can fix it for those who had it in 4.0.4 it will also fix the issue for those who appear to only have the issue as of 4.1.x.
[Samsung Galaxy Nexus] solidspidey:
just ran across this 4.2 article and I noticed this:

"The Android 4.2 app switcher (a.k.a. the multitasking tool) now appears as a full-screen interface instead of a transparent overlay with content visible behind it. The thumbnails and icons fly into place with a slick-looking new animation. The background, meanwhile, is the same as your current system wallpaper."

http://blogs.computerworld.com/android/21262/android-42-poise-and-polish

Do you guys think that this change in the app switcher app will squash this bug as far as the recent button is concerned? Obviously it could still creep up through other apps.
[Samsung Galaxy Nexus] metal571:
That should help a lot, at least for our handset. This issue doesn't exist on my Grouper or on Crespo.
[Samsung Galaxy Nexus] aeoveu:
IT BETTER!!!

This bug is sooooo cringe-inducing that I've LITERALLY stopped using the task switcher.

Thanks for the post; reading up on it now.

sent from my mini tractor
[Samsung Galaxy Nexus] scarmon25:
Yeah. That is my main reason for wanting 4.2. I am really hoping that this bug is gone once and for all with the update. Just a few more days and we will know.
[Samsung Galaxy Nexus] aeoveu:
OMG OMG OMG OMG! THE BUG'S FIXED!!! :D I switched (successfully) between the browser and the Gmail app like 9 times in succession WITHOUT producing this bug!

(the background seems black in the new task switcher - maybe cause I'm using a live wallpaper).

@ Others, to upgrade, see http://xdaforums.com/showthread.php?t=1988903

Edit: no Miracast option though - haven't found it. But no biggie - I don't even have one of those things, let alone an MHL adapter!
[Samsung Galaxy Nexus] guidocioni:
Fine! I'm getting 4.2 as soon as anybodumake a custom rom out of this :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
I noticed the new opaque (ie. not an overlay) Recents and was wondering if that would fix it. Awesome! Can anyone else confirm? :)
[Samsung Galaxy Nexus] \m/aximuS:
I can confirm. The bug with recents fixed :D But now recents sometimes not smooth as in 4.1
[Samsung Galaxy Nexus] alves.paa:
Bug completely gone. Couldn't reproduce it through the recent and neither through the apps that used to trigger it. And the ROM is so damn smooth it isn't even funny. It even fixed lag problems in some apps.
[Samsung Galaxy Nexus] osm0sis:
Perfect. Case closed then. That makes a nice happy ending to the thread. :)
[Samsung Galaxy Nexus] jd317:
Bad news. It is not fixed.

I went all day yesterday thinking it was fixed. Today when I unlock my phone, it was back :(
[Samsung Galaxy Nexus] osm0sis:
Seriously? That sucks... Does Recents still trigger it? I noticed on the GN it's opaque and on my N7 it shows translucent over the homescreen wallpaper. So this might have been an attempt of Google's to fix it by making it not an overlay on the GN/phones.
[Samsung Galaxy Nexus] alves.paa:
Yes, what ROM are you using? How did you flash it? Stock kernel? How did you reproduce it? I say that because I can guarantee it's 100% gone in my device. The problem really annoyed me and I've been trying to make it appear since yesterday and I couldn't, even after selecting Google+ countless times through the recents app and after exiting World of Goo with the back button (countless times, too), both methods that would trigger the bug 100% of the time in 4.1.2. I really think yours is an isolated case, or maybe I am a lucky isolated case :D
[Samsung Galaxy Nexus] ttabbal:
It's much improved for me, but still pops up after a while. I only have this bug with the fantom screen protector, but it's good enough now. When it starts having issues, a quick screen off/on fixes it, just like before. It does seem to take much longer to happen though. I had the screen on using the phone for about 45 minutes before it cropped up. I use recents a lot, for what it's worth.
[Samsung Galaxy Nexus] jd317:
I'm on halo86 AOSP ROM. I don't know how to reproduce it, as I said I was under the impression it was entirely gone. This morning k take my phone off my charger and its immediately back. A quick screen off and back on has fixed it and I haven't had an issue since.

Yes I am on the stock kernel. I never flashed the factory images I waited for an AOSP ROM to come out. It rarely happens now though
[Samsung Galaxy Nexus] aeoveu:
Tried performing a factory reset? Backup with Titanium Backup and then restore. Make sure you check what you're restoring just in case.

I did it as a precaution, although I looked for the bug before doing so. And it didn't show up.

There are many people who're facing a host of other problems. The only problem I have is with kernels with smart reflex (which includes the stock kennel...and that's got nothing to do with this thread), but I think you might want to preform a factory reset just in case.

I can't recreate the bug. Tried many times but it's just not happening. Heck, I've begun using the task switcher key once again! :p

sent from my mini tractor
[Samsung Galaxy Nexus] ttabbal:
Yes, full wipe before installing 4.2. Only installed user apps from titanium. I have no trouble with 4.2, those that do seem to have all tried a dirty flash.
[Samsung Galaxy Nexus] jd317:
I performed a full wipe. I wiped data, cache, dalvik, formatted system, formatted cache.

The bug seems to come up for me after unlocking my screen randomly. It no longer has anything to do with recents.
[Samsung Galaxy Nexus] guidocioni:
My Gnex raised again. Now with 4.2 it's blazing fast.. I'm easily switching between recent apps in a perfect way.. That's amazing! I hope that will last till next reset for 4.2 custom rom :cool:

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] \m/aximuS:
Same problem :( Today when I unlock my phone, it was back. But i can't reproduce it in any of the usual ways. Damn Nexus :mad:
[Samsung Galaxy Nexus] osm0sis:
I'm getting my replacement Fantom Tempered Glass Screen Protector sometime in the next week or so, so I'll see how JB4.2 stacks up against the bug for us middle-grounders.
[Samsung Galaxy Nexus] osm0sis:
Turns out JB4.2 fails hard if you've got the bug exacerbated by a glass SP. The bug is still present AND possibly worse than before, just triggering at random and sometimes just one screen-off-on doesn't workaround it, I have to do it two or three times before the touch sensitivity returns to normal. No tangible difference from changing the OMAP4 Gamma either.

SO.. sometime next week looks like I'm flashing back to 4.0.4 and trying those 4.0.3 binary drivers once and for all. ;):fingers-crossed:
[Samsung Galaxy Nexus] dannejanne:
Yeah bug still there on 4.2 unfortunately.

Tapatalked
[Samsung Galaxy Nexus] x_Mischka_x:
The bug actually disappeared for me on toroplus 4.2 with the AreYouJellin' ROM. So I don't know.
[Samsung Galaxy Nexus] osm0sis:
So I went back to 4.0.4 to try out those 4.0.3 graphics binaries, and honestly I can't reproduce the bug. I never realized it before but I guess I'm one of the people who didn't have the bug until Jelly Bean. Meaning I can't test. :(

I tried to detect a reduction in sensitivity and maybe there is a slight one, but even with my glass screen protector on (which is what exacerbates it enough for me to notice it on JB) it's very hard to judge in ICS. After applying the binaries anyway I either couldn't notice a perceptible difference or it got worse, so I guess that might be out anyway.

Back to the drawing board unless someone who legitimately reproducibly had the bug in 4.0.4 steps forward.
[Samsung Galaxy Nexus] alexdemonumber3:
I don't know if I'm just lucky or something, but the bug disappeared for me in 4.1.1 after changing the omap setting to 1.2. I havent dealt with it since then since I've been running Franco's kernel non stop from 4.1.1 til now (4.2.1)
[Samsung Galaxy Nexus] zAlbee:
Take a look at this. Apparently not only does the Nexus 4 have a similar sensitivity issue, but they also claim to have found a fix by downgrading the Synaptics touch driver. I wonder if this can apply to the GNex (and if it does, how did no one find this out sooner?)

Sent from my Transformer TF101
[Samsung Galaxy Nexus] dannejanne:
I would like this fix for our model. Interesting.

Tapatalked
[Samsung Galaxy Nexus] osm0sis:
For me 4.2.x actually worsens the bug. Now it occurs at random, not necessarily from Recents, and one screen-off doesn't always work around it. Sometimes it takes two or three.

Simple. I wouldn't have been messing around with the graphics drivers if we'd had access to the touchscreen driver. i.e. We don't. ;)
[Samsung Galaxy Nexus] maxon_yalta:
I can confirm, flashing stock google image for yakju Gnex 4.2.1 fixed the sensitivity issue.

Hell, i was switching apps like a boss, no issues at all. :cool:

Anyway, I was missing my CM10 customizations, so i restored my 4.1.2 backup. Once I did that, the issue was back.
[Samsung Galaxy Nexus] aeoveu:
Okay... I have managed to trigger the bug - but only when the phone's stressed out (like when I'm playing NFS Most Wanted).

Otherwise, Nada. Zilch. Zut. Nothing. I, too, can switch like a champ.

sent from my mini tractor
[Samsung Galaxy Nexus] fabrizziop:
To be honest, I've had both 4.2 and then 4.2.1 since the day their OTAs came out, and I haven't got that bug at all. Before it was easily reproducible, now I can't do it at all. I'm now having problems with data disconnections during sleep and screen unresponsiveness in the lock screen sometimes (I have to pull battery). TBH I don't know what's worse.
[Samsung Galaxy Nexus] aeoveu:
People have reported stability issues with 4.2 - thankfully, all I needed was a different kernel.

As for the bug - I agree, I can't produce it easily but I won't say it's gone - because it's been minimized. Perhaps my using a livewallpaper sorta muddles it up - or maybe it's something else. Either way, it only seems to happen when I use NFS (and not an Android software function... just a specific app thus far).
[Samsung Galaxy Nexus] thesoldier:
I've sent back 2 (about to be 3) devices to Verizon because of this. My original would ONLY do it on tapatalk and nowhere else. Other two do it whenever they want to, no matter what version of android I'm on. I had one replacement with a horrible purple screen that never had this issue.
[Samsung Galaxy Nexus] blackhand1001:
This has been worse than ever in 4.2 for me. I never really had a problem in 4.0 and then in 4.1 it would do it after using xda or tapatalk and now in 4.2 it happens all of the time.
[Samsung Galaxy Nexus] osm0sis:
Same experience here, but only with my Fantom SP.
[Samsung Galaxy Nexus] blackhand1001:
Yeah. It needs to be fixed. Its incredibly frustrating.
[Samsung Galaxy Nexus] guidocioni:
So i was using Linaro ROM for a long time and nevere experienced the bug on 4.2.1. Today i've changed ROM (Purity 3.1) & Kernel and the bug is here again :crying:

The "good" thing it's that now is totally random and not triggered by recent apps...

What a relief :(
[Samsung Galaxy Nexus] osm0sis:
Yeah, in 4.2 it's not completely random since I guess they "fixed" the Recents by making it opaque. It'll be interesting to see if 4.2.2 improves anything. There are just so many issues in 4.2.x so far.
[Samsung Galaxy Nexus] blackhand1001:
Google needs to fix this asap. It is incredibly annoying and the fact that its still around after all these updates is terrible. Its gotten worse with each update. I barely ever had it in 4.04 and then it was more common in 4.1 and now its random and much more frequent in 4.2
[Samsung Galaxy Nexus] otaconc:
I have this problem since JB 4.1 a it was never solved completely. In 4.1 the problem was triggered as said by OP, on 4.2 the problem was minimized but still there.:(
[Samsung Galaxy Nexus] solidspidey:
Since flashing aokp 4.2 I noticed that I still have the bug but it's about the same as what I had even when using the 'gamma fix' but now I can use whatever gamma I please.

The bug still creeps up other ways but at least recents menu is usable. Really wish we/Google could squash this bug once and for all.
[Samsung Galaxy Nexus] osm0sis:
Probably unlikely that Google will. They've just moved on to the N4 which doesn't have this problem. ;)
[Samsung Galaxy Nexus] blackhand1001:
That thing has plenty of other problems anyway. And lg doesn't seem to care at all about making enough of them. Samsung, htc , or Motorola next time please.
[Samsung Galaxy Nexus] dannejanne:
http://xdaforums.com/showthread.php?t=2028289

Tapatalked
[Samsung Galaxy Nexus] osm0sis:
Very interesting! Not the same issue though.
[Samsung Galaxy Nexus] dannejanne:
Not quite. Still interesting though ;)

Tapatalked
[Samsung Galaxy Nexus] blackhand1001:
Can anyone test if this still occurs in 4.2.2.
[Samsung Galaxy Nexus] Loureiro:
In my case, happens after some minutes of intense tasks, like gaming. Disappear after a minute or two and if I turn off the screen. Only the very bottom section of the screen is affected. Tested with pointer location option available at development options.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] reysonance:
The odd thing is in my case, since 4.2 anyway, the sensitivity drop is much more severe than 4.1, to the point that my touch no longer recognized by pointer location, quickly turning on/off the screen fixes it. And it usually happens when jumping frequently through apps.

Funny thing is the occurrence of the bug multiplied 5 times since I learn about this issue :silly:
[Samsung Galaxy Nexus] pcloadletter1:
Never experienced this issue on any OS version and currently on 4.2.2.
[Samsung Galaxy Nexus] matteventu:
With 4.2 it had seem to be fixied, but it still RARELY happen in my Galaxy Nexus (the most time, when I use it while connected to the AC adapter, I use the original Samsung one).

With about every rom (paranoid, CM10.1, stock...).

But I repeat, it is A LOT seldom respectively from when i was pre-4.2 rom :)
[Samsung Galaxy Nexus] reysonance:
I just realized this! I use my phone a lot when charging, and 80% of the time it happens it happened while I was charging!
[Samsung Galaxy Nexus] reiper:
This bug still occurs on my device on the last CM nightlies (4.2.2) but actually i don't remember if i noticed the bug on android 4.2.1. Today I will flash the older version of CM (4.2.1) and check if it still gonna show again.
[Samsung Galaxy Nexus] matteventu:
With CM10.1 4.2.1 it rarely happens at me (most time while charging).

But IT HAPPENS :(
[Samsung Galaxy Nexus] reiper:
24 hours later I didn't noticed this bug any single time (cm10.1 android 4.2.1) which i can't say about the latest android when i had this every few minutes. Was there a faulty series of touchscreens or it happens to EVERY galaxy nexus?
[Samsung Galaxy Nexus] reysonance:
It looks like it's independent of OS versions, so it looks that it may be hardware.
[Samsung Galaxy Nexus] osm0sis:
I got my screen back from replacement and I can happily say my new one doesn't exhibit the bug at all (knock on wood), even with my tempered glass screen protector which is how I noticed it originally with my original panel. So luck of the draw (or newness) with hardware is definitely a large part of it.
[Samsung Galaxy Nexus] solidspidey:
Interesting. How are you able to reproduce it on 4.2.2 prior?

Before upgrading to 4.2.2 I could replicate it every time using the "recents" trick. Now it just seems to happen randomly with no apparent cause.
[Samsung Galaxy Nexus] osm0sis:
Random since they made the recents opaque, but only with the tempered glass protector.
[Samsung Galaxy Nexus] solidspidey:
Yep I have the same phantom glass protector. The couple days I had it off ( in between getting sent a replacement) I couldn't even notice it even though it was there. :-[

If it was hardware do you think it would have randomly occurred on all previous versions of jb? Not just "recents"?

I guess some type action we do on screen messes with the hardware.

Its weird that the screen off and on trick doesn't fix it anymore if it were truly a hardware issue.