yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] RogerPodacter:
Remember its not any type of lag at all. Scrolling is still just as smooth, its just that the sensitivity is decreased.
[Samsung Galaxy Nexus] RogerPodacter:
This sounds like the most plausible answer so far that I've seen. It very well seems like it could be some grounding electrical issue/glitch.
[Samsung Galaxy Nexus] dark06:
Then what would the recent button or any other stuff to trigger it, have anything to do with this?

fod
[Samsung Galaxy Nexus] metal571:
My thoughts exactly...how could this be purely hardware if the recents button fully triggers the issue reliably every time?
[Samsung Galaxy Nexus] malibu_23:
If its hardware its likely only to affect gsm models only. Like the volume bug. I rape this phone with nightly usage. Especially since I broke my tablet. Never had this problem. This isn't a widespread bug in my eyes. Few bad batched phones it seems. Why don't you order a new screen and test the results.

Sent from a G-Nex
[Samsung Galaxy Nexus] guidocioni:
I have tested with my girlfriend's nexus and friend's nexus: they bought the gnex a few days ago while i bought it in decembre... This is a widespread bug, people just don't want to see that.
[Samsung Galaxy Nexus] gokpog:
Mine goes up to .4 and I don't notice it at all. Most likely all are affected but people use/operate their phones different. Plus they have different kind of (dry/wet) skin so many won't notice the difference between 0.3 and 0.4 in day to day use ...at least not until they lock their phones and everything goes back to normal. But it's a bug that should be addressed no matter how many people are really bothered by it.
[Samsung Galaxy Nexus] RogerPodacter:
Exactly. People just aren't knowing they have this bug because they're looking for lag or some kind of change, but its just a difference between 0.28 and 0.40. Some people won't be effected by that if they are hard swiper or press their screen hard most of the time. You wouldn't even notice. But the bug is there.

And I totally agree skin differences could mask this, wet moist vs dry.
[Samsung Galaxy Nexus] metal571:
Totally agreed. I do have a Q for you though; were both of those maguros?
[Samsung Galaxy Nexus] aeoveu:
Another thing: while I don't intend to undermine anyone, this bug never took place in ICS no matter how many times I tried.

So... either your hardware configuration is different, or its something else on your phone... cause I can guarantee you 1000% that if I revert to ICS, the bug will go away.

(The pressure bit - normally, when we tap on the screen, its above 0.3 so 0.4 isn't an issue... for me... although I haven't paid a lot of attention to it lately).

sent from my mini tractor

---------- Post added at 07:34 PM ---------- Previous post was at 07:33 PM ----------

But then... this doesn't happen on a friend's GN...

Talk about partially contradicting myself.

sent from my mini tractor
[Samsung Galaxy Nexus] metal571:
I second this. Flashing AOKP Milestone 6 completely alleviates this bug for me.
[Samsung Galaxy Nexus] delf0s:
Not true...first time this bug appeared for me was when I went from ICS 4.0.1 to 4.x.
[Samsung Galaxy Nexus] rayiskon:
I join my voice to the guys who said the bug was not present for them on ics.
[Samsung Galaxy Nexus] guidocioni:
All of that from Italy :good:

Mine from ebay in december for about 500 € and the other two a few days ago at about 300 € (that made me feel sooo bad :( but my girlfriend was just :victory: cuz i payed the pgone :rolleyes: ).

Anyway i don't remember this bug on ICS but i never used the recent apps task so...i'd have to try again but...no ;)

So....410 messages and still no sign from Google?? :eek:
[Samsung Galaxy Nexus] metal571:
Italy rocks. I'm a Polish-American, but I adore your exotic cars.

Anywho, let's hope Google takes notice soon...I'm willing to bet they'll eventually fix it considering how long this thing *should* be supported by them.
[Samsung Galaxy Nexus] osm0sis:
edit: nevermind, it occurs while charging, so grounding really can't be the problem after all.
[Samsung Galaxy Nexus] metal571:
Is it just me or does the Note section of the OP just simply cut off?
[Samsung Galaxy Nexus] malibu_23:
So this only is present on gsm nexii?
[Samsung Galaxy Nexus] sxayarath:
This is also happening for me. I am on CM10. This did not happen when i was on vanilla ICS. Also, I'm noticing the lag starting on my Nexus 7, but not nearly as bad.
[Samsung Galaxy Nexus] copkay:
Nope, Verizon Nexus here, and I've had the problem since ICS and now to JB.
[Samsung Galaxy Nexus] aeoveu:
I have a friend in Google... I did point them to this thread (they're in Android) but no confirmation as such. Explained to them that this bug want present in ICS, and that there are some devices that strangely don't suffer from this bug as well.

I can't say if the team's doing anything on the bug since I don't have access to that kind of information...

sent from my mini tractor
[Samsung Galaxy Nexus] delf0s:
@aeoveu: that's awesome that you have contacts in Google and that you pointed them to the thread. I hope this bug gets fixed...its really really annoying.
[Samsung Galaxy Nexus] copkay:
Was that supposed to say "wasn't present in ICS"? If so, that's incorrect. As mentioned several times throughout the thread (and in the title itself) this was certainly an issue in ICS as well.
[Samsung Galaxy Nexus] metal571:
I think it wasn't present until 4.0.4 from what some others said earlier in this thread. 4.0.1 for example didn't have this issue afaik.
[Samsung Galaxy Nexus] RoadHazard:
It did, however, have the bug where multitouch would stop working correctly in certain apps after a while (you would suddenly be unable to walk and aim simultaneously in 3D shooters, for example), until you cycled the screen off and on again (just like with this issue). Maybe when that bug was fixed (which I'm pretty sure was with the 4.0.4 update), this one was introduced instead?
[Samsung Galaxy Nexus] metal571:
Very plausible.
[Samsung Galaxy Nexus] sxayarath:
Well after updating to the latest CM10, I am no longer having the lagginess. Hopefully it won't come back but time will tell.
[Samsung Galaxy Nexus] osm0sis:
Holding onto the end of the USB cord while the other is plugged into the phone does seem to improve things slightly... so weird.
[Samsung Galaxy Nexus] aeoveu:
Yup. That was. Thanks for correcting (I hate autoco-wreckts!)

I do now recall vaguely that the bug would creep in randomly with ICS (I bought the GN when 4.0.4 came out - but the navbar buttons not working is a Jellybean thing for me). That said, I did say that I had another friend who did NOT face this problem regardless of the task switching - so I've put forth that as well.

My contact asked me to submit a bug report - turn on USB debugging, and press the power button and vol up/down (yes - that's a feature in ICS 4.0.4 and up - so it's official for those of you who are skeptics on being unable to produce a screenshot). (note - this is the same as a logcat - that's what they said!)

Anyway - I dropped a reminder... and as I said, not sure if they're up to something or not (I seriously hope they are!)
[Samsung Galaxy Nexus] Guicrith:
better fix

Copper tape,(should have)soldering iron,wire,electrical tape and nexus of course.

Permanent fix wire goes to top of sim port as last time.

If you dont have a soldering iron just electric tape the wire on the copper.

DO NOT SOLDER TO SIM PORT electric tape wire on.

If you do not know how severe it actualy is download multitouch tester and put in landscape mode put 3 fingers on right and one on the left move the one on the left up and down and one of the 3 will drop out or wiggle touch the sim port do the same thing and fixed it may take a few trys to make it glitch when not touching the sim.
[Samsung Galaxy Nexus] osm0sis:
Perfect.. but have we figured out how to make it not look like hell yet? :p

Maybe just a small area on the sides at the bottom left or right where a hand tends to always be touching when using the phone.
[Samsung Galaxy Nexus] Guicrith:
You can

1:Put copper tape on the phone and risk it being uncomfortable and having to buy a new 400 $ phone when it wont come off.

2:Buy a metal case.

3:Have it look bad and work.

4:Have it look good and be buggy.

5:Always have usb cord sticking out and wear an aluminum foil bracelet taped to a usb cord.
[Samsung Galaxy Nexus] osm0sis:
:laugh::good:
[Samsung Galaxy Nexus] tgyberg:
So that's how he came to be!
[Samsung Galaxy Nexus] Guicrith:
That would require at least 20 rolls of copper tape,2 cameras,50 feet of wire and a solar panel.

Anyway i switched to aluminum tape for duct work because its sticker.

So now it would be more like r2d2.
[Samsung Galaxy Nexus] Bewinxed:
Tried this, I can confirm the issue too ;O starred the issue, bumb bumb bumb! ouo
[Samsung Galaxy Nexus] kinggroin:
Just a heads up. I had the screen sensitivity problem for some time, but the 9/05 build of paranoid android has yet to exhibit the issue! I haven't changed anything in the ROM yet so its all stock.

I'll report back once I'm on Franco again.
[Samsung Galaxy Nexus] kennethpro22000:
Does this fix help us? I'm not at home now.so i can't try it.

http://xdaforums.com/showthread.php?t=1875490
[Samsung Galaxy Nexus] guidocioni:
Dunno, I'm not sure if can be flashed over an aokp based rom

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bioan:
No problem on MIUI ROM. The bug is gone.
[Samsung Galaxy Nexus] osm0sis:
That's a good sign that maybe Google fixed something in the latest AOSP that everyone's pulling patches from. Fingers crossed!
[Samsung Galaxy Nexus] metal571:
I too can confirm that the in the latest build of Paranoid Android (9/6) the bug is nonexistent. It's been fixed, now it's a matter of rolling out the fixes to everyone hopefully in an OTA at some point. Then for the first time ever I feel like the GNex will have no issues. (except for the obviously terrible audio quality in loud environments)
[Samsung Galaxy Nexus] belton:
I have the same problem too. Mine is Android 4.1.1. Stock OTA ROM. Bought at Hong Kong

The problem persists without touching the recent tasks.

Value of Prs keeps high.

Not sure how the screen filter app help, tried but didn't know how to work it out... (the instruction in the first floor is missing)

TouchScreen Booster could help a bit, but not much.

Looking for a good fix or workaround ... :(
[Samsung Galaxy Nexus] 11768:
Same here.

Running 4.1.1
[Samsung Galaxy Nexus] Guicrith:
If you bought it in hong kong you might want to check if its a real one before trying to fix it.

Its a grounding issue.

All apple products have a metal back and thats ground.

The Samsung galaxy player yp-g70 had a problem where the touch points dropped out after holding them for for a minute.(may have been software i returned it)

And the galaxy nexus is not grounded.

Samsung could not wire an led to a battery if they had every expert working on it.

http://xdaforums.com/showpost.php?p=30954329&postcount=427
[Samsung Galaxy Nexus] whittikins:
How do you explain it only happening when using the Recents button?
[Samsung Galaxy Nexus] metal571:
And to add to that how do you explain it being completely fixed on exactly the same device in the newest build of Paranoid? It's software.
[Samsung Galaxy Nexus] bgdxv:
Maybe it's fixed in the latest AOSP sources?
[Samsung Galaxy Nexus] Alton (Halo 2):
The bug is nonexistent on cna latest also . Just tested it ...
[Samsung Galaxy Nexus] osm0sis:
So, PA, MIUI and now CNA. What's the latest AOSP those builds are based off?
[Samsung Galaxy Nexus] dark06:
Latest xenonhd still has the bug

fod
[Samsung Galaxy Nexus] osm0sis:
Well CNA is JRO03L, but so is XenonHD, so there goes that unless there are newer patches Xenon isn't using yet.

PA and CNA also have Trebuchet in common, but MIUI uses their own, and Xenon uses Apex. :confused:
[Samsung Galaxy Nexus] bgdxv:
Miui doesn't use the AOSP recents menu, so that may be the fixing
[Samsung Galaxy Nexus] metal571:
If Trebuchet was the fix, wouldn't the latest CM10 nightly not have the bug? (it does for me still)

Is it possible for there to be an "updated" version of JRO03L AOSP?

I just tried CNA 3.5.0 stable and it's still there. Were you running a nightly or something? Also, switching to CNA now. Finally a ROM that is uncompromising in terms of CM10 and AOKP features.
[Samsung Galaxy Nexus] metal571:
delete
[Samsung Galaxy Nexus] kinggroin:
Just a heads up. I mentioned that paranoid 9/6 is green of the bug, and it is, but after installing the Franco app and his kernel, the bug came back. Restoring the stock kernel fixed it.

Not sure if this matters, but I had fast charge enabled as well.
[Samsung Galaxy Nexus] osm0sis:
Stock kernel from PA (cyanogenmod) or JB (AOSP/Google)?
[Samsung Galaxy Nexus] guidocioni:
I've tried once with the stock kernel with JRO03H (I'm using franco's one all the time) but the bug was still there.. I'm not sure that is kernel related, also thalamus said that..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renaud:
I cannot replicate that bug (at least on FuguMod)
[Samsung Galaxy Nexus] guidocioni:
Lucky you :D

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] rayiskon:
I'm running cna 3.5 and the issue is still there
[Samsung Galaxy Nexus] metal571:
Same for me.
[Samsung Galaxy Nexus] mariachi202:
Running PA 2.1 with franco.

No issues whstsoever.

Then again, I do not use the nsv bar, I almost always disable it anf use lmt.

Could the navbar be the culprit?
[Samsung Galaxy Nexus] Alton (Halo 2):
I can't find lmt in the play store ? Wtf?
[Samsung Galaxy Nexus] RogerPodacter:
No I use LMT and still I get the bug. Nav bar is hidden always.

Anyway lmt is not in the market, not sure why. Its here on xda...
[Samsung Galaxy Nexus] Alton (Halo 2):
Can u link me?
[Samsung Galaxy Nexus] petrsiri:
I find the issue fixed after updating apex launcher to 1.3 beta 4. Can anyone else try it and report?
[Samsung Galaxy Nexus] metal571:
I kind of doubt that launchers are the problem but it's possible. What ROM are you running?
[Samsung Galaxy Nexus] petrsiri:
Yeah, me too, but this was the only major change I made before noticing the improvement. I am running androidme 1.7 gnex and franco milestone 5.
[Samsung Galaxy Nexus] Lostpick:
I'm trying codename + AK kernel and the sensitivity issue tapping recent apps is gone !!!

EDIT: I'm trying with another ROM (Aosp light) e this kernel seems tu solve the sensitivity issue !! Try please! I'm using experimentale 061

http://xdaforums.com/showthread.php?t=1883298

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Michele02:
codename 3,5 with stock kernel, bug still there... what's wrong with me?:(

edit: latest paranoid android with stock kernel, bug gone :confused:
[Samsung Galaxy Nexus] rayiskon:
same here cna 3.5 with stock kernel and it's still here
[Samsung Galaxy Nexus] dannejanne:
I experienced this bug today for the first time. I can't seem to trigger it in any way though. Doesn't happen often at all.

Didn't the Nexus 7 have this bug? It would lose sensitivity over half the screen and turning it on/off again fixed it when it happened.
[Samsung Galaxy Nexus] osm0sis:
From the Fantom thread:

Can anyone else reproduce an improvement just using the patched surfaceflinger? I'm running stock yakju so don't worry too much about compatibility. My device was one of the borderline ones that didn't display the issue until I put a Fantom on it, so if someone else is in that boat, it would be best for testing, since we'd know if there was a fix for the less-severe cases.
[Samsung Galaxy Nexus] guidocioni:
I'm worried to use that in my phone. I've got MinCO with Franco Kernel and it doesnt seem to be a CM-based rom -.-
[Samsung Galaxy Nexus] osm0sis:
Does stock yakju seem to be CM-based? It works fine here, a bit snappier and the screen sensitivity bug seems lessened.

Obviously back up your original before flashing. That should go without saying.
[Samsung Galaxy Nexus] norpan111:
I had this bug when i was stock unrooted jb :/ cant get rid of it!

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] guidocioni:
just flashed..

For me, same as before.

Maybe a little better, but even noticeable.
[Samsung Galaxy Nexus] blackhand1001:
The surfaceflinger patch is only for cm builds. It doesn't change anything with touch input. It fixes the lag present in recent cm builds by reverting the surface flinger library back to before the change was made in the cm code that caused the large amounts of lag. Surfaceflinger is the display composition engine not the touch input system. I was the one who made and discovered the surfaceflinger fix.
[Samsung Galaxy Nexus] osm0sis:
blackhand, I understand. We're a little desperate in this thread. ;)

If, for no logical reason, it does improve things slightly, we're not going to argue. Just testing different theories.
[Samsung Galaxy Nexus] blackhand1001:
Yeah. The patch is still worth applying. Just not on the stock ROM.
[Samsung Galaxy Nexus] Lostpick:
Please try this kernel ! Maybe It's not the best kernel but for me the issue is gone ! I can use recent apps without problems

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bgdxv:
Hey guys, I'm not entirely sure that i get the same issue this thread is about, but here is my problem: When I open the recents menu and try to swipe away the app from the bottom it doesn't work, and sometimes it even opens that app, because the phone thinks i just tapped it, instead of recording the swipe. I noticed that if I use one of the stock wallpapers, I never get this issue. So maibe it's something related to the wappapers? :confused:
[Samsung Galaxy Nexus] Michele02:
Paranoid Android definitely solves the issue, now the point is to find out where it was hiding:rolleyes:

sent from my galaxy nexus after smootly switching between recent apps :victory:
[Samsung Galaxy Nexus] solidspidey:
AK kernel definitely fixed it for me. But I would like to use AOKP and Franco kernel. Not sure what makes AK kernel not have the bug.

---------- Post added at 01:17 AM ---------- Previous post was at 01:12 AM ----------

forgot to mention this

Here's my recent activity:

clean flash AOKP B2 = bug

clean flash CM 10 official nightly = bug

flash previously posted surface flinger fix = bug

Flash AK kernel = FIXED!
[Samsung Galaxy Nexus] osm0sis:
If we can get a few more confirmations on this somebody should tell thalamus.

If anyone can figure out what code in AK needs to go AOSP for this fix it's him.
[Samsung Galaxy Nexus] Michele02:
alas there's no ak kernel for maguro :rolleyes:
[Samsung Galaxy Nexus] jeffwei8:
I can confirm as well that the lag is gone as well after flashing the latest experimental (063) AK kernel on cm10.

Flashing back to latest Franco nightly or stock kernel brought the lag back after pressing recents and using different messaging apps.

Now I hope somebody can figure out what's wrong with all the other kernels and AOSP.
[Samsung Galaxy Nexus] guidocioni:
Today I can confirm that the issue was not triggered by recent apps. I've never used that tab but a few times the phone became slow and stop registering tap under 0.45, even now! Has something to do with brightness adjust...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] delf0s:
Here's a thought...when I bought my gnex ...it was originally Yakjuxw, as soon as I changed it to Yakju/Takju the issue started. Yesterday I went back to the original Yakjuxw 4.0.1 and let it upgrade by itself to 4.1.1. So far...my phone is running better than ever...and have to yet experienced the issue. There has to be some kind of subtle difference between both builds. This may have something to so with it....just a thought.
[Samsung Galaxy Nexus] blackhand1001:
Kernels aren't variant specific as far as I know for the galaxy nexus.
[Samsung Galaxy Nexus] delf0s:
I believe this is not a kernel issue...its a light sensor issue.
[Samsung Galaxy Nexus] solidspidey:
Yep. Michele try flashing AK and let us know if it's fixed for you.

---------- Post added at 05:34 PM ---------- Previous post was at 05:01 PM ----------

Just fyi for anyone not using cm10, I am running AOKP build 2 (non cm based rom? Or hybrid?) and successfully flashed AK kernel. We will see how stable and how well it sleeps but I would ultimately like to run Franco kernel for the color multiplers and other kernel options.

---------- Post added at 06:09 PM ---------- Previous post was at 05:34 PM ----------

Also, maybe someone else can confirm. I upgraded to AK kernel 64 and the issue returned. Not sure if it's something in the change log or maybe the bug returned when I was doing something else on my phone.

I know for me personally the bug would activate when I use better battery stats app.

Edit: I'm pretty sure it was Tapatalk that reactivated the bug. Version 64 seems fine if I don't use recent apps with Tapatalk app.
[Samsung Galaxy Nexus] rayiskon:
just tried the AK kernel with CNA 3.5 (ya ya, it's more cm based now than it is stock :D ) , anyways the kernel runs fine and all, managed to replicate the bug, although it was less, i mean u can still feel the buttons are "heavier" when typing , but there's surely an improvement... anyways, back to cna's stock kernel now.
[Samsung Galaxy Nexus] solidspidey:
For me it seems as AK kernel fixes recent apps but I can still replicate the bug using better battery stats app and tapatalk app. Im so sick of this bug! lol
[Samsung Galaxy Nexus] jeffwei8:
Hmm I spoke too soon. Sensitivity lag still exists even with AK kernel. Might be slightly less noticeable than stock/cm10/Franco kernels, but still there. Very noticeable when using Whatsapp and swapping out to other apps that use the keyboard via the recents button. :(
[Samsung Galaxy Nexus] Michele02:
Thanks for the info about kernel, but I'll keep PA for a while... It solves the problem and also I'm falling in love with tablet ui :D

Edit: just tried to switch between WhatsApp and xda app... Still no lag or sensitivity issue on navbar :thumbup:
[Samsung Galaxy Nexus] tgyberg:
Hmm, may have to give PA a shot. Stoopid bug!
[Samsung Galaxy Nexus] solidspidey:
Do you guys think PA works because of tablet mode basically? I remember over at the Rootzwiki Fanthom thread people were saying they had improved sensitivity when they changed the nav bar height from 48 to 40 iirc. I tried it but didnt help in my case.
[Samsung Galaxy Nexus] iron and wine:
tried it out, and it didnt help me either. although while in tabletui, and unlocking lock screen, it kills me a little more each time i see that recent navbutton pop up out of time. anyone else experience that too??
[Samsung Galaxy Nexus] Michele02:
It's not tablet ui, bug disappears even if you select "hybrid off" mode
[Samsung Galaxy Nexus] kennethpro22000:
I think the bug is related to light sensor.i am now using pa android rom and fanco. 264 nighty kernel. I have set to the lowest brightness and try to trigger the bug, and it doesn't appear
[Samsung Galaxy Nexus] dannejanne:
I'm on a PA based rom and I can't reproduce this bug no matter how much I try. It does happen occasionally though but I'm not sure it's the recent function that does it.
[Samsung Galaxy Nexus] whittikins:
What brightness setting do you use? Try 50% or higher, and see if you can produce it then.
[Samsung Galaxy Nexus] osm0sis:
Recents doesn't even always make it immediately noticeable, just seems to begin the decline in sensitivity so that it may take another minute or so for it to become noticeably bad. People also report other apps that dim the screen like Tapatalk cause it.
[Samsung Galaxy Nexus] rpgmakero:
Recent make it immediately for me. Always.
[Samsung Galaxy Nexus] metal571:
same
[Samsung Galaxy Nexus] solidspidey:
its weird, AK kernel solves the recent apps bug but I am still able to reproduce it elsewhere. I tried PA and it seemed to squash the bug. Not sure whats so special about PA. But I doubt its a kernel related or light sensor related bug. Maybe something GPU related, though switching between 304 and 584 ghz gpu kernels made no difference for me.
[Samsung Galaxy Nexus] Michele02:
Why don't we submit this topic to pa developers?