yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Archpope:
I notice sudden "drops" In touch sensitivity when I play Temple Run.

Sent from a sensor-laden supercomputer that fits in my pocket.
[Samsung Galaxy Nexus] nav200:
Ya I think touch sensitivity is an issue on all nexus devices. I used my bro's nexus s and same thing happens after a while
[Samsung Galaxy Nexus] danielkuhlman:
Seriously, try the SGS touchscreen booster app from the market. It helps. I didn't have issues until I played temple run, and now I can pretty damn well at it
[Samsung Galaxy Nexus] hardiksha:
4.04 update

m checking thru settings but still not getting this update... pl help
[Samsung Galaxy Nexus] execute_method:
This did not fix it for me although I will continue to use this app. Thanks for the recommendation!
[Samsung Galaxy Nexus] delf0s:
I can confirm the same issue. Soft buttons start to get sluggish. I'm on stock 4.0.4. :(

I think it's a software bug with ICS 4.0.4. Also, the auto bightness. Other than that, phone is working awesome!!
[Samsung Galaxy Nexus] execute_method:
This is what I'm seeing :

Swiping up and down to the bottom edge.

Normal (look at left side, swipes clear to the bottom)

Teh suck (won't even swipe onto the nav bar)

Tapping soft keys won't work when this happens.
[Samsung Galaxy Nexus] onthecouchagain:
I don't know if this is at all related, but when using the stock keyboard, does anybody notice sometimes the keyboard will not register any key taps? It usually happens after waking the device, and it lasts for like 3 seconds. I'll wake my device to respond to a text, for example, start typing, and it'll type okay for a few words, then it'll be unresponsive for 3 seconds (so not registering any key taps), then it'll start typing perfectly fine again for the rest of the time it's awake.

This happens randomly. Does it occur with anyone else? It's... bizarre. Don't ever get unregistered taps with other keyboards, but I like the stock keyboard.

I'm on stock 4.04.
[Samsung Galaxy Nexus] EP2008:
THIS! And the bottom right is exactly where my problem happens (the menu soft key).

Sent from my HP Touchpad running ICS :-)
[Samsung Galaxy Nexus] execute_method:
Stopped at the VZW store, and have a replacement inbound. Hopefully the next one doesn't have the same problem... This makes 2 replacements so far.
[Samsung Galaxy Nexus] adrynalyne:
I count myself lucky, because I haven't seen this issue and I have had this device since January.
[Samsung Galaxy Nexus] dannejanne:
Interestingly enough I have not encountered the bug one single time since I raised the gamma. *knock on wood*

Tapatalked
[Samsung Galaxy Nexus] solidspidey:
I'm so glad I was able to find out this solution and others were able to confirm it worked for them. This bug was driving me INSANE.

I found out the solution by noticing that when I flashed AK kernel the bug would be gone (because after new kernel it changed the gamma setting) and whenever I changed my screen profile via trickster mod the bug would return. Then through process of elimination of changing each color setting I was able to pinpoint the gamma control.

Now I'm curious. How does PA rom not experience this bug? Users are able to control their gamma using a variety of kernels as well right? I think somewhere in omapzoom must lie the answer.

What do you guys think?
[Samsung Galaxy Nexus] dannejanne:
PA does have this bug. I'm on PA and had this bjg as you see just a few posts up. It comes with the CM kernel and gamma at 0. After raising it it has vanished (the bug).

Tapatalked
[Samsung Galaxy Nexus] scarmon25:
So it has to be a issue in that lib or binary or whatever does the screen coloring?
[Samsung Galaxy Nexus] guidocioni:
I've never seen the bug on PA, never touched the gamma

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] akira02rex:
Perhaps you just don't notice it then.
[Samsung Galaxy Nexus] dannejanne:
It's there, believe me. Happened frequently for me before I changed gamma.
[Samsung Galaxy Nexus] guidocioni:
No man.. I've experienced this bug on every other roms JUST installed..that was the first thing that I was doing after the flash and every ****in modded rom had that annoying bug except PA..... Never changed the gamma

Inviato dal mio Galaxy Nexus con Tapatalk 2

---------- Post added at 04:46 PM ---------- Previous post was at 04:43 PM ----------

Anyway..just for knowledge..

Someone can post a screenshot of the settings that you use in the color control tab? I've franco app and i'd like to test your settings to see if bug shows up :good:

I've not understand wich gamma are you modifying..
[Samsung Galaxy Nexus] jeffwei8:
I've never seen the bug in PA either. I'm using 2.17 now. Switched to PA at 2.13. And before anyone says I just don't notice it, I've been VERY critical of this bug as well. I just can't get it to pop up any more at all no matter what I try. Tried it on 2 gnex now. Never touched gamma settings. However, I think it's great if that seems to fix it on other rooms :)
[Samsung Galaxy Nexus] solidspidey:
Here is the gamma setting screen. It is the last option in the color tab on Franco app. Set to 1.6 ( though I think anything higher than 1.0 will eliminate the bug) let us know if it works for you.

Fyi my screen shows no option being selected because I set my gamma through trickster mod app.
[Samsung Galaxy Nexus] dannejanne:
Seems like a very weird and inconsistent bug judging by the replies.
[Samsung Galaxy Nexus] guidocioni:
Man..don't take it wrong but...with 1.6 set my screen become too much dark and bluish...
[Samsung Galaxy Nexus] solidspidey:
Try 1.2. You could always change your Red green blue and trinity contrast settings also to compensate for the dark and Blue if you don't like the way it looks.

---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------

I don't see why pa rom wouldn't have it. This bug should affect all roms. It doesn't make sense that one rom doesn't have it and all others do. That's just my opinion. Unless pa rom modifies some code related to gamma settings, I'm not sure.
[Samsung Galaxy Nexus] alves.paa:
I do experience this bug in PA (2.16 and 2.17), but in PA it doesn't seem to be related to multitask anymore. I can easily reproduce by playing some games like Rayman Jungle Run and Jetpack Joyride. Set my gamma to 5 using the trickster app and it's gone, been testing it since yesterday. Thanks solidspidey.
[Samsung Galaxy Nexus] solidspidey:
:) glad to help. My miniscule contribution to the Nexus community. Like I said before this bug was driving me insane. It was so annoying cause the recent apps is a big reason for me why jelly bean is so awesome.

Now I have to retrain my brain to start using it again lol since I avoided it all this time :P
[Samsung Galaxy Nexus] tgyberg:
Thanks man! This one's on me! :good:
[Samsung Galaxy Nexus] Kevindee:
Thanks solidspidey! I'm on Dark PA 2.17 with Fugu Kernel #807, and applied your color settings on Trickster and the lag is gone for me. Plus the colors are much better for me too :)
[Samsung Galaxy Nexus] scarmon25:
There has been an update to AOSP source. I wonder if this update will address this issue or not.
[Samsung Galaxy Nexus] alves.paa:
I'm using Paranoidandroid 2.18 update 1 and I'm not able to reproduce the error in any of the previous ways I did (the most fail-proof method was after playing World of Goo for some time and using the recent apps), so I'd say the bug is gone in PA.
[Samsung Galaxy Nexus] metal571:
But does this affect maguro and/or toro? The current build out is for nakasi only
[Samsung Galaxy Nexus] scarmon25:
I have no clue. I know the devs are updating their ROMs to the latest code. What exactly it does for us I have no clue. I have read through the change log and it is really really long. I'm sure there has to be a few things it improves. Honestly if it just fixes the task switcher bug I'll be extatic.
[Samsung Galaxy Nexus] metal571:
And otherwise we can always just adjust our gamma as we can do now to get rid of the bug from happening when using the recents switching on-screen button.
[Samsung Galaxy Nexus] scarmon25:
Well. I flashed the latest CM10 which has been updated to 4.1.2. So far it seems the recent apps bug is still there. It doesn't seem as bad though. Adjusting the color still seems to help it. Gonna wait for the aosp version and try it and see how it does.
[Samsung Galaxy Nexus] cheeloong1985:
bug

I flashed Rasbean latest version which is 4.1.2 but still having this problem. I think Google haven't solve this problem yet.

At the moment i just set my gamma to 6. Hopefully next update will solve this problem.
[Samsung Galaxy Nexus] scarmon25:
When I tried the new CM10 it seemed to help a little. I'm on an AOSP based on 4.1.2 and it seems a lot better then before. Maybe just this build though.
[Samsung Galaxy Nexus] metal571:
I don't know, I just tried the 10/10 nightly and the bug is there in full effect with just one use of Recents. Psychology maybe on your end? ;)
[Samsung Galaxy Nexus] scarmon25:
What I've noticed is that when I use the Task Switcher to switch to say Talk. The lag doesn't come on right away like it used to. I fan type pit a message or two before the keyboard becomes almost unusable. That's where I notice it the most is in the keyboard. So it is still there for me. But I do notice a difference cause before it was almost instant for me. Now it seems to be on a delay.
[Samsung Galaxy Nexus] solidspidey:
I think the OP should be updated with the gamma fix. It seems confirmed that it will work for everyone. Just for future reference.
[Samsung Galaxy Nexus] osm0sis:
I can't seem to up the gamma without making everything too dark and over saturated looking. Anyone figured out how to balance out with trinity contrast and the other settings?
[Samsung Galaxy Nexus] solidspidey:
I know what you mean. You can keep messing with trinity and rgb till you get to a look you like though right?
[Samsung Galaxy Nexus] tgyberg:
Mine looks pretty darn good like this:

R 200

G 169

B 178

RGB

2

0

0

Trinity

-4

OMAP4 Gamma

1.2

Brightness at 55%
[Samsung Galaxy Nexus] osm0sis:
Haven't found one yet.. I up the Trinity contrast to compensate for the OMAP Gamma darkening and then all the blues and purples are jacked up, and removing them with the multipliers/RGB gammas leaves me with green/yellow.

Thanks I'll give them a shot, but I can tell by looking they'll be a bit too red for all the purple I've got going on on my screen. For an idea of JUST how screwed up my screen is, here is what I have set to make everything look good (but with a little blue tint to the greys - better than purple IMO):

Multipliers 200 245 280, RGB Gamma 0 0 12

Trinity Contrast -24, OMAP4 Gamma Contrast 1.0

CAB Disabled.
[Samsung Galaxy Nexus] solidspidey:
Just glancing at your settings I think your trinity contrast is too low at -24. A higher OMAP gamma (in my case 6 through Trickster app) actually makes it darker for me. Maybe thats why your colors are oversaturated? Try upping your trinity contrast and see if that helps.

As far as RGB gamma and Multipliers I stick with franco default. I cant really tell if its "optimal" or not as I have the brightness set pretty low anyways for battery savings.
[Samsung Galaxy Nexus] osm0sis:
Like I said.. things are pretty bad on my display and the bastards are Telus won't let me return it - they tell me there's nothing wrong with it even though at stock settings the whole upper half of the screen is purple at low brightness. -24 is the only way to effectively kill the purple for me. :(
[Samsung Galaxy Nexus] metal571:
You can't contact Samsung directly for a hardware replacement? They were pretty easy to set up a service call when I called them thinking my phone was broken because of this screen sensitivity issue initially before I cancelled the service call.
[Samsung Galaxy Nexus] osm0sis:
AFAIK Telus was sending it to the nearest Samsung service center guys, and they were the ones telling me it matched their spec device, which either means they're full of **** or their spec device is also a peice of ****. ;) So yeah, haven't explored the call center option though, maybe it'd be better dealing with them directly like you said, or maybe it would be Samsung Canada and not Samsung "Maritimes". Something to think about..
[Samsung Galaxy Nexus] metal571:
hah yep in my experience, the only people who get anything done are people in call centers. emails never get returned and small-time repair centers not directly related to the major ones tend to not get things done either lol
[Samsung Galaxy Nexus] solidspidey:
Aw that sucks. I didnt know you had screen issues, that makes sense now. I hope you are able to replace it! I'm not too familiar with Telus as I'm in the States using Verizon. Do you perhaps have phone insurance through Telus? I pay $10USD a month with Verizon....gives me piece of mind.
[Samsung Galaxy Nexus] osm0sis:
Screen was like this from day one, so it's defective. Whole threads on the purple defect issue. No insurance, but it's under warranty for the first year, that's until Feb. Hopefully that's good enough for Samsung Canada whenever I find time to make that call. :good:
[Samsung Galaxy Nexus] osm0sis:
So... since we determined that OMAP4 Gamma Contrast somehow works around the issue.. perhaps my suggesting we try flashing back to older versions of the display binaries wasn't so far-fetched after all?

https://developers.google.com/android/nexus/drivers#maguro

The bug began with 4.0.4, right? So maybe we should try reverting to the 4.0.1 (ITL41F) or 4.0.3 (IML74K) Graphics driver binaries? Anybody with a linux box set up want to build those from the link for us to experiment?
[Samsung Galaxy Nexus] solidspidey:
It's definitely worth a shot and I'd be interested in the results. Wish I had the know how to do it myself but I do not haha :)
[Samsung Galaxy Nexus] metal571:
That sounds like an awesome idea, I hope some dev can do this for us to confirm if it works or not. If that works, it would be awesome to see that "fix" go into all of the latest ROMs until Google eventually fixes the stupid bug.
[Samsung Galaxy Nexus] osm0sis:
No need for a dev. ;) We just need someone running Linux to execute the compile scripts in the graphics binary zips I linked to. My phone is the only Linux I run or I'd do it myself (I tried it in adb shell anyway but it doesn't seem to work there). So.... any takers?
[Samsung Galaxy Nexus] steven.hh:
Wish I was more linux savvy, else I would try to tackle it. Sounds like a viable answer, hopefully some guru can help us out! :victory:
[Samsung Galaxy Nexus] metal571:
I can do that. I have some experience with Linux as we have a cluster of RedHat 5-running servers at my grad school that I use for research. I can run compile scripts on a personal ThinkPad I have though if I install Ubuntu or use it in a VM. If there are no other takers, I can handle this as early as Friday or this weekend and get it back to whomever needs the compiled binaries.
[Samsung Galaxy Nexus] solidspidey:
That would be amazing. We all very much appreciate your willingness to help.

I believe osm0sis would be your point of contact, but I'm sure he can give you more details himself.
[Samsung Galaxy Nexus] matteventu:
Someone can explain me exactly how to fix the bug with the gamma settings?

Like a quick-guide :D

I've a rooted Galaxy Nexus with 4.1.2 stock ROM.

What kernel does support to thange the colors settings? What app I need to operate over these settings?

What exactly setting i must change to remove the bug?

I read a lot of precedent pages, put I didn't understood so much :(
[Samsung Galaxy Nexus] metal571:
Download Trickster MOD from the play store for free and it will have a DSS gamma setting, which you need to set to 6. If your kernel doesn't support it, flash something like franco.kernel (the latest is r290 i believe), and then that feature will be available. I know that because I use it myself.
[Samsung Galaxy Nexus] osm0sis:
Okay, here's what I got for directions in one of the binary threads:

Be sure to also do one for JZO54K so we can revert easily without a nandroid if the fix doesn't work. As for testing, I won't be a good candidate since I took my Fantom screen protector off last week due to lifting in the curvature. Thanks so much for helping us out though, metal!
[Samsung Galaxy Nexus] metal571:
Looks like a fairly simple process. I'll see what I can do if no one else gets this done by Friday night Eastern Time.

And no problem man...I'm as sick of this problem as we all are. It affects every single Galaxy Nexus. I've tried ones all over stores, my gf has this issue, I have this issue...there's no way it's hardware at all. At least DSS Gamma fixes it for the time being.
[Samsung Galaxy Nexus] hp13:
the status has has my top screen blue when you have a white background. I noticed it in YouTube. its ugly.

Sent from Nexus Prime
[Samsung Galaxy Nexus] metal571:
Alright, I figured out how to extract the tarballs using Cygwin on my Windows machine. I'm left with a directory or two and a bunch of .mk files as well as .so files. Which specific binaries do you need me to extract? I don't know how to make them recovery-flashable, but I have extracted them by running the provided Bash shell script (I only did 4.0.1 as an example for now).
[Samsung Galaxy Nexus] osm0sis:
Just the ITL41F graphics zip from the Nexus binaries page should be good to start. Shouldn't require Cygwin.. just certain browsers download them as .tar when they should be .tgz, once I rename it to .tgz WinRAR handles them fine here. Should just be a file called extract-imgtec-maguro.sh, their version of a self-extracting executable I guess. ;)

chmod u+x on that like Jay Aristide said and it should hopefully work.

There might be a number of files extracted, we need to preserve the directory structure and add it to a recovery flashable zip like Jay did (but he did it for ALL of the different binaries) here. If you can just rezip up the entire directory (everything the .sh extracts) as is and PM it to me I can make an update zip for it if you're not sure about that part.

Edit: Ah now I get you meant a cygwin shell emulator. :good:
[Samsung Galaxy Nexus] osm0sis:
Alright folks, this is not for the faint-of-heart or lacking-in-nandroid. ;)

Those who can readily and reliably reproduce the screen sensitivity bug and can also reliably fix it by changing the OMAP4 Gamma Contrast to 6 (1.2 by Franco's scale), I would like you to disable your OMAP4 Gamma tweak, then make sure you can reliably reproduce the bug again. Now go to the custom recovery of your choice and make a fresh nandroid, then flash the following zip. It will revert your graphics binaries back to ITL41F (ICS 4.0.1r2). Now boot up and see if the bug still exists. If it does, oh well - we tried. If it doesn't, holy ****! In that case we'll knock a zip up based on 4.0.3 and see if it's still gone, and take it from there.

For science! :laugh::D

[attachment removed - 4.0.1 binaries appear to be too old to function]
[Samsung Galaxy Nexus] scarmon25:
If this works then that is awesome. Makes me wonder if it would work on cm as well as other ROMs. I very well may have to give it a shot on stock and cm if it works.
[Samsung Galaxy Nexus] solidspidey:
Can this be used on Toro? Or only maguro? I will definitely give it a try tomorrow morning if it's compatible with Toro.

Awesome work guys. Nexus community ftw! I got my fingers crossed.
[Samsung Galaxy Nexus] scarmon25:
Just flashed on Toroplus CM10 and didn't get a boot. Just hung at the Google Screen. :(
[Samsung Galaxy Nexus] steven.hh:
sadness. just tried and after the google screen it became blank. i was on 4.1.2 btw. thanks for trying :]
[Samsung Galaxy Nexus] osm0sis:
I'm going to say maguro only for now...
[Samsung Galaxy Nexus] metal571:
Does this work with maguro even? I didn't test on my unit yet.
[Samsung Galaxy Nexus] osm0sis:
No idea.. They're the maguro binaries. I'll try it out now even though I won't be able to weigh in on the screen bug. It might be that ICS binaries won't work with JB. :(

We could try again with the 4.0.3 binaries, just to be sure, if these ones don't work.

Another idea is someone who reliably has the bug should downgrade to 4.0.4, reproduce the bug, then flash the 4.0.1 binaries and see if that fixed it. Just so we can narrow down the issue and see if, even though it might not work on JB, something in the graphics binaries is the problem and could be worked around in the future. All valuable information!
[Samsung Galaxy Nexus] metal571:
I actually didn't have the bug last time I flashed the 4.0.4 maguro factory image, or at least not from the Recents list usage.
[Samsung Galaxy Nexus] osm0sis:
Yeah these definitely don't work with 4.1.2 here. Basically gives you an instant SOD, even though my PC still recognizes when I plug it in. I'm flashing back to 4.0.4 factory image to see if we at least have a viable option for further testing, and if that doesn't work then I'll pull the zip.

---------- Post added at 02:52 PM ---------- Previous post was at 02:33 PM ----------

Screen doesn't go black in ICS, but it hangs at the Google logo. Can You do a 4.0.3 for me so I can see if 4.0.1 is just too far back to push it?

---------- Post added at 03:24 PM ---------- Previous post was at 02:52 PM ----------

Nevermind.. I finally figured out how to extract them on my device adb shell. Must have been since I was using terminal emulator before. Okay, looks like I was right, 4.0.1 was just too old. Pulled. Good news is that the 4.0.3 binaries work on 4.0.4 so we can do some testing there. Wiped my sdcard trying to get ICS to boot with the 4.0.1 binaries so I'll report back in 20 minutes or so whether the 4.0.3 binaries will also work on JB/4.1.2.
[Samsung Galaxy Nexus] osm0sis:
4.0.3 binaries in JB is also a no-go. Same problem: screen blanks after the logo. So that leaves us one avenue for testing: 4.0.4 flashed with the 4.0.3 binaries. We need a volunteer who could reliably reproduce the screen sensitivity issue with ICS 4.0.4 to downgrade to that, make sure they can still reproduce the issue and then flash the 4.0.3 binaries to see if it fixes it again. If it doesn't fix it well we're done, BUT, if it does, we'll start whittling down the binaries to see which specific one fixes it and then maybe that can be brought forward to JB. So, I'll ask it again... any takers? ;)

[attachment removed and readded to newer post]
[Samsung Galaxy Nexus] matteventu:
From http://code.google.com/p/android/issues/detail?id=29734

Someone knowns more?
[Samsung Galaxy Nexus] metal571:
I wrote that, and that's my experience since 4.1.1 Jelly Bean. I'm not 100% sure when it happens the rest of the time but some other people have predicted that it happens when other apps try to modify the screen contrast or dim the background, or something like that...search in the thread someone said it before
[Samsung Galaxy Nexus] osm0sis:
So... nobody would like to help possibly solve this bug?
[Samsung Galaxy Nexus] JediNinjafication:
technically i could read thru almost 650 posts to catch up but could someone give me a condensed version before i can commit to being the one to test out whatever issue is at hand?

*Step Away From The Toolkit and NoROM Gets Hurt*
[Samsung Galaxy Nexus] metal571:
All you really need to know is that if you use the recents list even one time on jelly bean, you can barely type at all after that since the screen needs harder taps. This is resolved by locking and unlocking the phone. The only known fix is to change the DSS gamma to 6.
[Samsung Galaxy Nexus] aeoveu:
Not sure if that really is the only fix - since raising the gamma level to 6 doesn't work for me (Trickster mod app / faux kernel v22).

Or maybe I'm doing it wrong.
[Samsung Galaxy Nexus] scarmon25:
Currently running cm10. Raising the gamma to 6 on cm10 fixes it for me.
[Samsung Galaxy Nexus] steven.hh:
I'll help test with the 4.0.3 binaries in 4.0.4 in a couple days. Have to deal with graduate apps first
[Samsung Galaxy Nexus] adrynalyne:
I use Recent menu all the time, and I have yet to see this issue even once in the entire time I have had this device (since release).