yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rpgmakero:
Like someone said before, I've noticed that the problem depends of the screen brightness (at least the recents button bug).

Honestly I don't know how Google or Samsung can still have this kind of problems. What can we do? The problem is becoming more and more annoying for me. If they don't solve it in a month I want my money back.
[Samsung Galaxy Nexus] Kevindee:
I've just recently got my Nexus and installed Xenon HD, and was affected by this bug. Made my home and recents buttons unresponsive, however my back button always seemed to work. Annoying bug nonetheless. I have since installed CM10 with the AK kernel after reading through some posts here, and it has helped a bit, but I do still experience the lag occasionally.
[Samsung Galaxy Nexus] jeffwei8:
Flash Paranoid Android. I was doubtful at first as well since it is based on cm10 and I've tried so many combinations of roms and kernels to try to make the lag go away. I finally flash PA last night and indeed the sensitivity lag is completely gone. The current PA is also pretty much up to date with cm10 features too. I couldn't be happier now. :)
[Samsung Galaxy Nexus] metal571:
But it doesn't have all the CM10 and AOKP features AND more like Codename Android does. It's a shame or I'd consider that ROM too.
[Samsung Galaxy Nexus] rpgmakero:
I've installed it too and the recents bug is gone, yes, but sometimes I still lose sensitivity and I don't know what causes it.

But yes, it's better than before.
[Samsung Galaxy Nexus] solidspidey:
I agree with the post above. PA is nice but I would ultimately like to run aokp. I really want to know what PA does differently. Maybe something in the display code as PA let's you do tablet mode? I don't know.

Does anyone know the stock kernel that PA uses? It might be worth a shot flashing that kernel and seeing if it helps
[Samsung Galaxy Nexus] guidocioni:
We had argued a few times that is not a kernel-related issue: occurs on stock rom with different kernel like franco and the stock one.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] solidspidey:
Yeah I see what your saying. I just wonder why on AK kernel the bug doesn't occur for me with recent apps but the bug is still there. I can reproduce it with Tapatalk and other apps. Weird...
[Samsung Galaxy Nexus] jeffwei8:
I get the bug still with AK kernel and every rom except PA.

It's definitely not kernel related, because I flashed AK kernel onto PA and still no bug. Definitely something in the rom.

I do agree that it's a shame if you come from AOKP or CNA roms and lose a lot of tweaks and features. But if anyone is coming from CM10 official, PA is quite up to date and has all the new features as of 2 nightlies ago.

One thing I have noticed is that PA's recents menu is slightly modified. They have a clear all apps button in the upper left hand corner. Perhaps something they modified there is helping with the issue (?)
[Samsung Galaxy Nexus] guidocioni:
Mmm don't think so.. The issue trigger in a few case without recent apps tab.. Has surely something to do with brightness adjust.. Maybe the recent apps video transition has something to do with brightness adjust

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] solidspidey:
Its interesting, when the recent apps gets pulled up it seems there is a graphics overlay. Also, I can reproduce the bug using betterbatterystats and tapatalk.

All 3 have the same thing in common. That popup overlay that comes up. For example, from tapatalk "Receiving data from server / Processing...." and from betterbatterystats "Connecting" (When switching from 'since charged' to 'since unplugged' for example)

Do you guys know what im talking about? Do you think something with those overlays is affecting our phones?

Also, do you guys remember before Googles "project butter" update that whenever a graphic overlay would occur there would lag? (ie. a toast notification from superuser when an app requested permissions)

Maybe there are all connected somehow.
[Samsung Galaxy Nexus] metal571:
That's brilliant...now who here can tell Google this
[Samsung Galaxy Nexus] rayiskon:
if that's so , maybe (just wondering) disabling the HW overlays from developer options in roms that contain it (like CNA in my case) and actually letting the GPU do the rendering might help
[Samsung Galaxy Nexus] osm0sis:
That setting disables the triple buffering of Project Butter, and the bug predates Jelly Bean, so it shouldn't really help..
[Samsung Galaxy Nexus] solidspidey:
yep, I noticed that option in dev options and thought it would fix it but after reading about hw overlays it wouldnt fix our bug.

Anyone else have any ideas/thoughts?
[Samsung Galaxy Nexus] jeffwei8:
Sorry if I missed it earlier, but has anyone been able to re-create this bug on PA rom even with brightness jacked up?

I used the phone for 5 mins screen on at 100% brightness just now and purposely tried to produce the bug. Tried everything (betterbatterystats toast pop ups, using the recents button exclusively to switch between apps, typing in whatsapp (always makes it lags after recents used on other roms), texting, browsing, etc.).

I can't get it to appear on this rom at all. From what I can tell so far, I don't see any trend between toast notifications or brightness being the cause of the problem on my phone.
[Samsung Galaxy Nexus] solidspidey:
yea i think the general consensus is that PA fixes it completely. What im thinking is that PA has certain code that affects the graphic overlay (maybe somewhere they tweaked something for their tablet mode compatibility) I donno, I'm just throwing out ideas.
[Samsung Galaxy Nexus] rayiskon:
someone bring moles to this thread maybe he can shed some light on what it might be about in PA
[Samsung Galaxy Nexus] blackhand1001:
Yeah it makes other things laggy as well. Worse that. Ice cream sandwich.
[Samsung Galaxy Nexus] guidocioni:
I'm going to make a video tomorrow, we have to post evidences in the first post.. People still don't believe me when I talk about this bug..:banghead:

Inviato dal mio Galaxy Nexus con Tapatalk 2

---------- Post added at 12:48 AM ---------- Previous post was at 12:40 AM ----------

I'm not saying that "brightness" is the cause, I'm saying that britness adjustment is the cause. Setting the screen at 50%, 100% or 37,695% doesn't matter at all.. In fact we did see that the bug is not triggered with very low brightness (screen filter) but it's more relevant when massive changes of brightness are registered.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] blackhand1001:
We definitely need to track this down. Its really bad at times. I am surprised Google hasn't fixed this yet. Could it possibly be related to content adaptive brightness.
[Samsung Galaxy Nexus] 11768:
I notice something else besides the sensitivity issue: the CPU usage will be maxed out too during scrolling while this bug is there instead of the typical 729mhz. I know this because I always have Cool Tool (an app that shows the CPU usage, etc) on.

---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------

I don't think so as I had content adaptive brightness turned off, but this bug still occur.
[Samsung Galaxy Nexus] guidocioni:
Me too

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] molesarecoming:
what we did wont affect it so much, im coming to that in a second. my theory is that aosp does still leak, but how the effects of it will emerge and when i have no idea, seems random. i have had problems in the past, then i sync my stuff, reflash and its suddenly gone. i did not include the surface flinger fix because it would introduce a new dependency that would be very hard to watch and maintain. i am still waiting for source code and statements from either aosp or cm regarding that issue. if they think its clean, i will assume the same - at least if its seemingly the case on my own device, and it does run fluid currently.

tabUI is another story. if you run tabUI in PA you cant compare it with other roms because they all have honeycomb android 3.0 implementations, just the way google shipped it. google has left the whole codebase untouched, project butter is for phone and phabUI only. i ported project butter 4.1 + Gpu rendering to tabUI in PA, our recents are therefore running considerably faster and theres no lag. heres the first commit that started it: https://github.com/ParanoidAndroid/...mmit/8351bfede34e566f83824b0c82e7e15d4fdc790b several others refine it afterwards. we're currently doing the same for the whole systembar, which at this point is still cpu rendered by aosp default. i doubt though that this has much to do with the issue at large as it applies to tabUI only.
[Samsung Galaxy Nexus] blackhand1001:
My Surface flinger fix is no longer required in cm10 builds from the 19th or newer so if your synced with the cm code you are fine. It been merged. The problem was that Steve (cyanogen) had made a patch for snapdragon devices in surface flinger but had accidently applied it to all devices and not just Qualcomm devices. Late on the 18th he merged a patch that fixed it so that it only applies to snapdragons so that it no longer lags on every other device.
[Samsung Galaxy Nexus] molesarecoming:
Wow, i didnt know that. So it really was a bug. And that didnt fix the issues discussed in this thread?
[Samsung Galaxy Nexus] rayiskon:
It's not related to the recent cm lag thing.

For some guys this issue was present since 4.0.4 , for the rest of us it appeared on jelly bean, some have major problems like total loss of tap registration in the lower part of the screen, others (like in my case) just need to press harder for the tap to get registered (becomes very annoying when trying to write an sms or email). So far it can be replicated by launching an app from the recent apps list, but it happens randomly and not every time.. the tap sensitivity is simply less than normal. Touch sensitivity is restored by pressing poweroff then power on again. However, guys are reporting that PA is the only rom where this issue doesn't occur, and that's in short y they reffered u here.

the sad part is, that many users have the issue on their device but don't realize it.
[Samsung Galaxy Nexus] metal571:
I'd just like to add that I flashed my gnex over to the latest factory image for ICS 4.0.4 and there was no bug there whatsoever. So at least for me, pure AOSP 4.0.4 is bug-free.
[Samsung Galaxy Nexus] guidocioni:
In these days for me the issue has become very annoying. I'm using the phone outside most popular f the time and he starts to slow down even without using recent apps tab... I think I'm gonna try PA : with something like that it's barely utilizable

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] rpgmakero:
I have been using PA these days and the problems with screen sensitivity has been increased. The recents button does not cause the bug, but for unknown reasons I get lag on my screen really fast.

I hope Google is going to hear us soon.
[Samsung Galaxy Nexus] guidocioni:
Anyone confirming this?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] aeoveu:
Okay... now that PA is being talked about in here, I have something to say... not about PA :)

I installed AOKP (my phone kept rebooting with the stock ROM, and despite my strong attempts at not using a custom ROM, I caved in) and for fun, tried out the tablet mode.

After the phone went into tablet mode, i - not having read this thread then - tried out the bug.

And lo and behold - it didn't occur! The tablet mode didn't exhibit the bug. I'm back on the normal mode, and the bug is now present.

So this is definitely a software glitch on some devices... a workaround is to use tablet mode (but that's not for me).

Now what do we do?

sent from my mini tractor
[Samsung Galaxy Nexus] ttabbal:
It seems to happen more on the latest than it did on the prior version. Not sure why.
[Samsung Galaxy Nexus] guidocioni:
Oh my...

Okay I'm staying on minco for now......

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] rpgmakero:
I've to say the best rom to avoid this problem is Miui by far. At least for me...
[Samsung Galaxy Nexus] osm0sis:
That could really narrow down where the bugged code is for us. Could moles or someone take a look?
[Samsung Galaxy Nexus] blackhand1001:
That's cause miui lags all the time so you don't notice.
[Samsung Galaxy Nexus] guidocioni:
Lol

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ttabbal:
Maybe. It's still pretty random. Sometimes I can go as long as I want, other times it can start glitching in a few minutes. Tablet UI seems a little better, but that could be placebo. I haven't run it long enough to be sure.
[Samsung Galaxy Nexus] jeffwei8:
Weird. I've been using PA for about a week now. Still no problems. Using PA 2.13 w/ Franco kernel. Not running tablet mode either. Using stock ui w/o hybrid mode (=basically stock cm10).
[Samsung Galaxy Nexus] rpgmakero:
I've opened the respective post in a spanish forum http://www.htcmania.com/showthread.php?p=5842981#post584298 explaining the issue and linking here. It seems that people don't notice the problem there. Maybe there is a hardware difference or just spanish people are less sensitive? :eek: .
[Samsung Galaxy Nexus] rayiskon:
this thread should be stickied , maybe then people will pay attention more to this issue
[Samsung Galaxy Nexus] osm0sis:
It's always been a bell curve sort of issue, ie. there are different degrees of being effected. Some people have it all the time, some people have it but only notice it when it's exacerbated by a screen protector (especially the Fantom tempered glass), and some people don't seem to have it at all.
[Samsung Galaxy Nexus] rayiskon:
Are u sure about this? I didn't have the bug on ics, later i bought a wet screen protector (extremeguard) , and since then i had a feeling that the touch sensitivity was reduced, but not to the level it is now after the jb update... if those screen protectors have any effect i would remove it without thinking twice
[Samsung Galaxy Nexus] scarmon25:
I know I will be happy when 4.1.2 comes out assuming it fixes that bug. I use the task switcher often and I notice it the most when switching between GTalk and the Messenger. Typing becomes almost impossible. I've searched and looked to try to find a fix either in a lib or binary or something. So far no luck.

Edit: I'm not using any kind of screen protector or any covering. I kind of wish I was so I could take it off and benefit lol.
[Samsung Galaxy Nexus] osm0sis:
Dead positive. I'm in that second group. Until I put a Fantom on my screen there was no noticeable bug. I'm sure it was there, just not affecting me as strongly as those who experience it all the time, so the SP brought it out. I'd try taking it off if I were you.
[Samsung Galaxy Nexus] dannejanne:
I get the sensitivity bug on PA too (2.13 & 2.14). It's not the recent button that triggers it and it happens only occasionaly. But the bug exists for sure in PA too.

Tapatalked
[Samsung Galaxy Nexus] ttabbal:
I have the fantom as well. The issue doesn't happen much without it, but I have scratches from not having a protector and I'm very careful with my phone. I also despise plastic protectors... One thing that helps me, enable 180 rotation and use the phone upside down. :D particularly if you use tablet mode, so that part of the screen has little of interest on it. Not ideal, but until we get a fix for the software, it's a workaround that helps some.
[Samsung Galaxy Nexus] rayiskon:
what about the screen protector that comes with the otterbox commuter case? i use the wet one i mentioned earlier with the case, but i'm very close to taking it off if it really helps get rid of the bug :D
[Samsung Galaxy Nexus] rpgmakero:
+1

Same for me
[Samsung Galaxy Nexus] osm0sis:
I'd say take it off and try. Odds are it will at least improve it.
[Samsung Galaxy Nexus] rayiskon:
i removed the screen protector , it's better, but it's still there, i reupplied the screen protector, the little improvement is not worth the risk of scratches ;)
[Samsung Galaxy Nexus] solidspidey:
Do you guys think its Color Profile/screen adjustment related? I noticed that every time I try to set a color profile through trickster mod the bug will reactivate. The only way to get it back to normal is to flash AK kernel again and just leave the Color Profile set to none. Maybe something to do with Gama Offset/Color Multipliers?
[Samsung Galaxy Nexus] tgyberg:
Not for me. I had the bug way before I ever messed with the colors.
[Samsung Galaxy Nexus] scarmon25:
I'm running stock right now and I have it on stock JB. I haven't messed with anything at this point. I've tried many kernels and such but ended up flashing back to stock with fast boot.
[Samsung Galaxy Nexus] guidocioni:
Yep, PA doesn't have the bug at all.. I think that I'm staying on this for a long time. I've tried roms, including cyanogenmod based rom but the bug is still there; dunno what moles have done here but it's smoother. I don't really care about hybrid or tablet mode but seems the only way to fix this.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] jeffwei8:
Same here. No other rom has fixed this problem for me.

I've been using PA 2.13, then 2.14, now 2.15 and NONE of them have brought the bug back for me regardless what I try to do.

PA 2.16 should be out now and moles says that there is a new Android revision merged that makes the phone even faster/smoother.
[Samsung Galaxy Nexus] scarmon25:
I would like to know what it is exactly that is causing it. Then we could pull that particular piece from PA and implemenet it into a stock ROM
[Samsung Galaxy Nexus] tgyberg:
Hopefully this revision doesn't cause the bug to happen again! :D
[Samsung Galaxy Nexus] jeffwei8:
Yeah wish we could narrow it down too. Moles isn't even sure either.

Flashed on mine just now. Still good. Don't really notice it to be much faster though lol
[Samsung Galaxy Nexus] osm0sis:
I am able to reproduce the bug in PA 2.16 still, but it seems far less frequent or at least less in severity.
[Samsung Galaxy Nexus] Kevindee:
I've never used any of the older PA roms, but I'm on PA 2.16 and I do get occasional sensitivity lags. The recents button seems to work better than when I was on CM10 with AK kernel, however I get more of the random lags with PA.
[Samsung Galaxy Nexus] solidspidey:
One thing I noticed. Using trickster mod I was able to reproduce the bug when I set the 'Gamma Adjustment' from 0 to 5. But from 6 to 10 I cannot reproduce the bug.

This leads me to believe that it's somehow related to brightness settings. Which makes sense as that screen filter app makes the bug go away.

What do you guys think? Does setting gamma to 6 and above help for you?

AK kernel v91

Aokp b3

Auto brightness
[Samsung Galaxy Nexus] solidspidey:
Also before I had Franco app and trickster mod both installed at the same time and I am just using trickster solely. Not sure if the gamma/brightness setting conflict with each other so installed Franco app just in case.

Also, my trickster settings fyi
[Samsung Galaxy Nexus] dmarden:
Wow, this is great... using the controls built into AOKP I set the gamma to 6 and the issue went away entirely. Nice!

Thanks to the discoverer(s).
[Samsung Galaxy Nexus] chlehqls:
Nice!

I can confirm that setting the Gamma DSS to 6 corrects the issue. The colors look more vivid anyways without any burn-in issues (remains to be seen). I'm on CM10 with faux's kernel if that helps.
[Samsung Galaxy Nexus] metal571:
I can confirm that setting the OMAP4 gamma manually using franco.kernel's app also causes the issue to go away, no matter which setting as long as it is not 1.0.

Adjusting the contrast does nothing. Anyone else able to confirm this as well?
[Samsung Galaxy Nexus] solidspidey:
Are you guys still able to reproduce the bug other ways? or it COMPLETELY gone?

Using gamma at 6, as far as recent apps button I can use it without sensitivity loss but I think the bug can still creep up other ways.. Ie for me better battery stats app and sometimes Tapatalk app.

What about you guys?
[Samsung Galaxy Nexus] dannejanne:
Exactly same here.

Have adjusted gamma now will see if it makes any difference. Seemz Tapatalk triggers it a lot for me recently. I'm on PA 2.16.

Tapatalked
[Samsung Galaxy Nexus] scarmon25:
What's crazy. I flashed the stock images in fastboot for FC12 the other day and let it update on its own to FH05. Wanted a clean slate. Since I have done that I haven't noticed the screen lagging issue. I've been using the app switcher pretty often and haven't noticed it, which normally within a few seconds of using the switcher it would be horrid. Not sure if I just got lucky or what. I'm running stock OTA Rooted and using the HotSpot hack. Not sure what to think.
[Samsung Galaxy Nexus] Lostpick:
Setting gamma at 1.6 with franco kernel, the issue using recents apps is gone ! Is it dangerous for the display ?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] tgyberg:
I've got my gamma set to 1.2 and cant get the bug to show! Nice!! :good:
[Samsung Galaxy Nexus] metal571:
If anything (since it darkens the midrange of the displayable color spectrum on the phone), it would reduce the load on the pixels.
[Samsung Galaxy Nexus] tgyberg:
Wow, using my phone quite a bit over the last couple of hours without that bug has been awesome! I now realize that it was happening almost all of the time. :highfive:
[Samsung Galaxy Nexus] RogerPodacter:
Its not physically degrading. Its like a memory leak, and as soon as you lock the screen it fixes itself. Till it starts again a bit later. Repeat.
[Samsung Galaxy Nexus] EP2008:
I'm still getting issues where the soft keys stop responding and I have to keep pressing them several times to get them to work.

Annoying as Hell.
[Samsung Galaxy Nexus] execute_method:
This.

I believe it's due to a hardware variation, but the craziest thing about it is that if I hold the phone on the sides with my thumb and middle finger, then put pressure on the battery it immediately starts working again. This would indicate a true hw issue.

Can anyone with this problem confirm that putting pressure on the battery clears it up? Try taking the back cover off and doing it.

BTW, I'm on a Verizon GneX.
[Samsung Galaxy Nexus] rayiskon:
i'm really surprised to read that so many people are having this issue, makes me wonder if my gnex will start to act that way at any time. so far i had no similar non responsive time intervals and couldn't reproduce it in any way. have the GSM version.
[Samsung Galaxy Nexus] jonstrong:
+1

I will sometimes use mine for LONG periods of time -- emailing, on FB, Twitter, reading Flipboard, other news sites, etc. I simply have not run into any kind of degradation on long sessions, multiple long sessions between reboots, etc -- and I rarely restart the phone. If there's a memory leak of some sort, I suspect it's specific to a particular configuration, i.e., ROM, Launcher, background apps, etc. I'm just not seeing it on my device...
[Samsung Galaxy Nexus] kidrobot52:
Hey roger have you tried going back to pure stock? Locking boot loader and unrooting then trying to duplicate the problem there.
[Samsung Galaxy Nexus] matteventu:
I have this sensivity issue.

Before 4.0.4, i had the multitouch bug that appens after some time, and fix it putting in stand-by the phone and then waking up the phone.

After 4.0.4, i have che sensivity bug, that semms that appens when before happens the multitouch bug. Fix it putting in stand-by the phone and then waking up it.

Related issue?
[Samsung Galaxy Nexus] :
I get this on my droid charge because I have really sweaty hands haha. A quick wipe down solves it for me!
[Samsung Galaxy Nexus] RogerPodacter:
Well yes it happens to me on pure stock 4.0.4 and I flashed it multiple times. Then I tried aokp 4.0.4 release 29 and it still happens. So that's what I'm still running right now.

For those who don't have it, its a very subtle issue. Maybe your usage just doesn't notice it. Or maybe you don't have it. Who knows. Slightly sluggish is the only way I can describe it. Or mushy.