yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metal571:
Confirmed working. WTF!?

Edit: it works on 48.6%, but doesn't at 100, 96.1, or 92.2%. Would this point to a GPU driver issue or something?
[Samsung Galaxy Nexus] guidocioni:
Dunno wtf to say!! So it's something related to screen brightness!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] metal571:
I don't think so. The navigation buttons below the display stay lit at the current system brightness, but the rest of the screen dims. That points to it literally putting a filter on the GPU's output. That's what I would say, but I'm not an Android dev or expert.
[Samsung Galaxy Nexus] delf0s:
Makes sense...when you turn the screen off and then on it goes away.
[Samsung Galaxy Nexus] guidocioni:
So... Now we have to talk with Google engineers :p

Inviato dal mio Galaxy Nexus con Tapatalk 2

---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------

I think we have to make a new Google issue.. The one existing is not describing well the situation. Maybe the owner is in this thread

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] metal571:
Good luck contacting them...lol. Does anyone know anyone else with Maguro running these builds without the issue?
[Samsung Galaxy Nexus] guidocioni:
Roger can you update the first thread with this new information please?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] delf0s:
Now that I think about it....it CAN be a light sensor issue...not GPU. What do you guys think?
[Samsung Galaxy Nexus] RogerPodacter:
No prob. Which link exactly? Just give me whatever text and links you want added and I'll paste it exactly as you type it.
[Samsung Galaxy Nexus] BrUhNiGGs:
I got my fifth VZW like-new replacement this morning and flashed AOKP (Jelly Bean 4.1.1 JRO03L) and after about 7 hours of usage I haven't gotten the sensitivity issue yet. I've tried the messaging>home>recents>messaging technique to activate the issue but I didn't get it. Let's see till later today as I may be speaking too soon :P it usually happens within an hour with my old gnex after fully wiping and flashing a new rom
[Samsung Galaxy Nexus] delf0s:
What ROM are you using?
[Samsung Galaxy Nexus] BrUhNiGGs:
The latest AOKP nightly (Aug 15).
[Samsung Galaxy Nexus] :
So, I did a bit of debugging with the kernel driver and it turns out that the pressure of the taps registered by the touchscreen driver definitely reduce after the 'recents' menu is entered.

Alas, there is no way of increasing the sensitivity in the driver, that appears to be hardcoded in the firmware.

I found that simply entering the recents menu was enough to trigger this issue, launching an app from there isn't required.

This suggests to me that whatever is happening when the recents menu is entered is triggering the issue, so that narrows down the issue somewhat.

Personally, I would suggest that it could be a TS firmware bug, but I suspect it *could* be worked around, when I have time I will investigate more.

If you want to track my progress, check here.
[Samsung Galaxy Nexus] metal571:
This is great news that we're working towards a solution. Major props.
[Samsung Galaxy Nexus] rayiskon:
and i thought thalamus was a recognized dev , xda admins where u at? :rolleyes:

anyways, if it's a firmware thing, we should really find a way to address it to google or samsung, it really gets annoying after a while.
[Samsung Galaxy Nexus] guidocioni:
Link is http://code.google.com/p/android/issues/detail?id=29734

Also Add the new information about screen filter : Downloading & using Screen filter application from play store, with brightness set to <50% fix the issue.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] whittikins:
Great, thanks a lot for looking into this. We've been trying to find a developer who can figure this thing out! Btw, what type of work do you do for the galaxy nexus? Do you have your own kernel?
[Samsung Galaxy Nexus] delf0s:
@thalamus: I don't think its a recent apps issue. I never ever use the recent apps button and I get the bug. The only thing that fixes the issue is the screen filter app mentioned above. This leads me to the conclusion that it has something to do with the light sensor.
[Samsung Galaxy Nexus] rayiskon:
I only get it with the recent apps menu, no taping home or any other method fixes it except turning screen off then on.
[Samsung Galaxy Nexus] delf0s:
Have you tried the screen filter app mentioned above?
[Samsung Galaxy Nexus] osm0sis:
I have, any change using it is neglegible, especially considering it appears to lag the entire interface. Only solid solution for me is to turn the screen off and on. Recent tasks seems to be involved as the decrease becomes aparent only after using it, naturally it's only minor at first and progressively gets worse.

I didn't know I had this issue until I applied the Xgear Fantom tempered glass screen protector, which seems to have the effect of exacerbating this screen issue to the point of being noticable for those of us that it wasn't obvious for already.

I'm really looking forward to thalamus' work on it, please keep us posted in the thread here as you make progress! :)
[Samsung Galaxy Nexus] delf0s:
Finally after such a long time having this issue... Thalamus is working on it. So exciting.
[Samsung Galaxy Nexus] BrUhNiGGs:
This is weird its been more than a day since i have been using my replacement gnex and I still haven't encountered the sensitivity problem. I've been using the recents from the OS for all my apps and on a regular basis and NOPE, haven't got it.
[Samsung Galaxy Nexus] whittikins:
I mentioned the bug in irc last night and he immediately started investigating. Great dev!

---------- Post added at 02:59 PM ---------- Previous post was at 02:56 PM ----------

I might have missed it, but what rom and kernel (including versions) are you using? Are they the same as what you ran on your previous phone? Thanks
[Samsung Galaxy Nexus] BrUhNiGGs:
I was running the AOKP nightly (Aug 15) and Trinity kernel Alpha 41 (OC'd to 1344mhz and 307mhz min)

And I guess I spoke too soon. I flashed the AOKP nightly today (Aug 17) and the sensitivity issue came back later in the day. Im going to flash the Aug 15 nightly and see if I get the problem again.
[Samsung Galaxy Nexus] RogerPodacter:
I've added this to the first post.
[Samsung Galaxy Nexus] shrijith1:
I can't thank you enough for finding this app :) So this definitely has got to do something with the light sensor ? Is 48.6 the threshold beyond which the issue is seen again ? One more doubt - I see a light blue tint when the screen filter is ON, especially with the messaging app. Is it only me ?
[Samsung Galaxy Nexus] guidocioni:
So you can press the thks button :thumbup:

Anyway I've not investigated where is the threshold, I've just find that with 48% its working.

The blue color it's normal, that screen filter mess up with system color but nothing to be worried about.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] rayiskon:
The screen filter app works for me too, although i don't find it practical to keep it on all the time to evade the problem, but definitely nice finding though.
[Samsung Galaxy Nexus] guidocioni:
Yep, it was just an investigation :D

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] gaw316:
I noticed on cm10 you can adjust the brightness and automatic backlight settings (perhaps this could be used as a remedy?) Also... this screen filter app may explain why when I use Trinity the issue seems less persistent because of the insanely low contrast levels.
[Samsung Galaxy Nexus] osm0sis:
Bad news from thalamus' github..

I've contacted the author of TouchScreenTune (for GNote and GS2) to see if he might be able to help or add GNex support to his app to see if it might help.

TouchScreenTune: https://play.google.com/store/apps/details?id=com.vital.tst.n7000
[Samsung Galaxy Nexus] tgyberg:
That would be great! Actually, anything that helps would be great. :good:
[Samsung Galaxy Nexus] osm0sis:
Here's another tidbit from the Rootzwiki Xgear Fantom Screen Protector thread:

Does this work for anybody else experiencing the touch issues in this thread? I haven't figured out how to change the navbar dpi on stock JB so I can't test it atm.
[Samsung Galaxy Nexus] whittikins:
Nope. It still messes up after you hit the Recents button.
[Samsung Galaxy Nexus] metal571:
Which ROM?
[Samsung Galaxy Nexus] whittikins:
Latest AOKP. I've also tried the new CM10 release.
[Samsung Galaxy Nexus] delf0s:
Any word?
[Samsung Galaxy Nexus] guidocioni:
No news :banghead:

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Ryu234:
Screen filter seems to be working at 48.6 %
[Samsung Galaxy Nexus] I Am Marino:
Wish I had never read this thread, I never noticed the sensitivity being shot until afterwards, /facepalm
[Samsung Galaxy Nexus] metal571:
I had a similar experience. I'm thinking it has something to do with the background dimming when you press the recents button maybe?

Being a recent engineering graduate, I notice everything, especially when I can't type fast for texting people...and man was that obvious after this bug occurred.
[Samsung Galaxy Nexus] RogerPodacter:
Remember I still get this bug and don't use the recent button AT ALL. that is just one of the ways to trigger it reliably, but not the root cause of this.

Anyway still no solution, I get this bug daily still.

BTW engineer here too:) graduates 2002 (ugh seems forever ago)...
[Samsung Galaxy Nexus] crobs808:
No issue here on AOKP JB builds (link for VZW ROMS) using native Launcher. Spent 20 minutes TRYING to get it to happen but couldn't. I am on the August 15th build, but I doubt the latest build from the 19th would have any difference.
[Samsung Galaxy Nexus] I Am Marino:
Is it a 3rd party launcher issue then?
[Samsung Galaxy Nexus] JediNinjafication:
the recent clears those apps. Do you have an otterbox or screen protector on? I noticed my touch is going down the tubes but perfectly ok when not in the case

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] crobs808:
Mine has been in an Otterbox Commuter since day 1 (dual-layer case, rubber+plastic). I also have a ZAGG screen protector shield (very thick rubbery screen protector). Again, I do not have this problem.

This has nothing to do with the hardware and everything to do with the launcher and/or OS. If the issue clears up by quickly power-toggling the screen, then it is not related to the cosmetics.

-edit-

I would challenge anyone having this problem to flash the following and see if they are still having problems:

JB bootloader + latest AOKP JB nightly ROM + latest Franco 384mhz kernel.

NOTE: Use the native Launcher and conduct testing both before and after you load all your 3rd party apps.
[Samsung Galaxy Nexus] JediNinjafication:
Yeah mine in a defender before i left the store. I noticed when screen protectors begin to wear out my touch lags. Was just suggestion. Im not having touch issue and am more than pleased with the excellent work team baked did on my dark ROM. Out of case..no touch issue. in case..issue. For my situation, i would have to say my screen protector needs replaced, suggested they try it before flashing.

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] crobs808:
Sure the case isn't overkill/keeping it hot? When my old Motorola got hot the screen acted up.

As far as the screen protector, I'd get a ZAGG shield if I were you. You have to have incredible patience when applying them, but you never have to buy another screen protector for that device again. They last years with no degradation.
[Samsung Galaxy Nexus] JediNinjafication:
No heat problems. I used to but i just changed kernels and haven't had an issue. The built in protector is known for the touch problems because we can't just change out to a new one when starts to get worn

EDIT defender screen protector can't be changed. Part of case

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] metal571:
Has anyone tried the newest JB b1 of AOKP?
[Samsung Galaxy Nexus] guidocioni:
No,but i'm trying Minco v4 in a few days

Roger, i'd suggest to change the title of the thread so we can gather much more..

Could be something like that: [BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)
[Samsung Galaxy Nexus] petrsiri:
Reassign soft key option

wrong post
[Samsung Galaxy Nexus] crobs808:
Ohh....there's your problem. I stay far far away from the cases with the built in windshields. Terrible for daily usage...fine if you use your phone an hour a day.
[Samsung Galaxy Nexus] RogerPodacter:
No I don't use any screen protector or case, never have.
[Samsung Galaxy Nexus] JediNinjafication:
I'm finding that out. Sucks outside too. Can't see anything. First otterbox and only pink one sprint had

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] metal571:
I second this.

The bug is still there on AOKP JB b1. Just tried it last night.

Currently running CM10 Official w/leankernel and it also still happens.
[Samsung Galaxy Nexus] RogerPodacter:
Thread title updated.
[Samsung Galaxy Nexus] crobs808:
For the record: NEVER buy accessories from your carrier. Always buy on eBay. I got my Otterbox commuter for $11 shipped, and my ZAGG shield for $8. They are lifetime products, and official (not knock-offs). If you use eBay just buy from a seller with 99% rating and 1000 or more feedback ratings and you should never have to worry.
[Samsung Galaxy Nexus] metal571:
I'm a cheap bastard, so I bought an S-Line clear TPU from ebay for $1.75. Took 3 weeks to ship but hey it was super super cheap, and it works great. But no screen protector, yet this issue still happens. Trying desperately not to turn this into an accessory thread lol
[Samsung Galaxy Nexus] crobs808:
I guess I am lucky. I have a 'good copy' GNex
[Samsung Galaxy Nexus] elmerendeiro:
can't reproduce this..gsm nexus, codename android with trinity
[Samsung Galaxy Nexus] akira02rex:
I don't seem to have this bug when pressing the recents button? I'm running paranoid android based off cm10.
[Samsung Galaxy Nexus] malibu_23:
any of u guys with the issue cracked open your phones to see if the ribbon is creased, loose, or ripped? ive had 2 different sprint nexus and ive handled quite i few more, never had the issue. sux for yall, but ive never evenheard of this outside of xda. usually stuff like this ends up on popular blogs like engadget, or BGR or etc..
[Samsung Galaxy Nexus] crobs808:
Agree
[Samsung Galaxy Nexus] RogerPodacter:
I posit that all nexus users have this bug, they just don't notice it. And also their usage pattern doesn't let the bug appear often enough to see it. But the bug is there.

Browse the web for 30 min straight, or text for 30 min, I bet the bug shows up
[Samsung Galaxy Nexus] AdrienC:
You're not nuts. I felt that the TS also feels a bit worse on 4.0.4

but from the severity of the issues you're facing, you might have a faulty touchscreen. Had something similar w/ Moto Milestone.

Try flashing 4.0.2 and stick for a couple days, it might still happen.
[Samsung Galaxy Nexus] boardrx182:
I'm having this same issue. It only started this evening after upgrading from a 4.0.3 ROM (Apex) to AOKP #31. Either it's AOKP, or 4.0.4 or some combination of things, but it's most definitely not the hardware. Been using this phone for months and the issue only appeared today with the install of AOKP.
[Samsung Galaxy Nexus] Ves:
Noticed the same a bit. Touches got detected at the wrong place. And multiple presses to get a button to recognize it being pressed.
[Samsung Galaxy Nexus] RogerPodacter:
Yeah this issue started for me once upgrading to stock 4.0.4, and also on aokp 30+. I was previously on 4.0.1 with no issue, so I don't know where exactly it originated.

Another good way to describe it is scrolling and touch events start to feel "mushy". Locking the screen resets and fixes it. A clear difference before and after. I still can't solve it...
[Samsung Galaxy Nexus] @rbiter:
I was on touch screen about 45 minutes straight last night. No issues.

---------++++---------

iPhone. helping computer illiteracy become popular since 2007.
[Samsung Galaxy Nexus] boardrx182:
I think I figured out what's causing this. I can use my phone all day and the issue doesn't show up, but once I activate the "Recent Apps" menu, the touchscreen sensitivity immediately drops. It stays this way until I turn the screen off and then back on. I can reproduce the issue again by opening the Recent Apps menu.

Can anyone confirm this? Really hoping a fix for this comes out soon, but now that I know what causes, and fixes, the issue, I can live with it for a while.
[Samsung Galaxy Nexus] RogerPodacter:
My issue definitely has nothing to do with the recent apps list. I haven't even pressed that button in a few weeks.

My bug crops up pretty quickly after a few minutes of use. The tapatalk app 100% forces the bug to start, every time without fail. Open that app and the bug starts.
[Samsung Galaxy Nexus] boardrx182:
Well crap. I was hoping we could find a common theme here but it sounds like it's not going to be so easy.
[Samsung Galaxy Nexus] EP2008:
I get the problem often, but not always, when going into the device settings.

Quite frustrating to be hitting the home or back key and getting no response.
[Samsung Galaxy Nexus] xxa:
I confirm this issue.

In the bottom screen is less sensitivity than the top.

The screen sensitivity subside when use the phone, but it is normally again when lock and unlock screen.

Does the issue come from hardware or software ?

Should I go to samsung service center for change the screen ?
[Samsung Galaxy Nexus] dnlsmy:
No problems here, White China Build Galaxy Nexus. Came as Yakjuux, flashed to Yakju. I don't even get the Landscape Keyboard lag bug.
[Samsung Galaxy Nexus] ASKnASK:
I can confirm this. Even made a thread about it here :D

The screen is much less Sensitive than the likes of Galaxy S, S2, Sensation, Wave etc.
[Samsung Galaxy Nexus] :
same

I've experienced a very similar issue several times, and then suddenly the sensitivity will return to normal without me doing anything.

I am very clean when it comes to my phone so I don't think it's because I have grubby hands or a dirty screen.
[Samsung Galaxy Nexus] RogerPodacter:
Oh yeah without question. When my bug happens it eventually fixes itself if I don't manually force fix it by locking the screen. And yes I am one of those insane clean freaks where my screen is pristine at all times.
[Samsung Galaxy Nexus] pai.pradeep:
aokp b34+Franco m3

Me too. Touch sensitivity is not as smooth as before.

Could it be a Kernel issue? I am using Franco Milestone 3.
[Samsung Galaxy Nexus] enigmatikexile:
Glad to know I'm not the only one. Was running 4.0.1 yakjuux from December until yesterday morning. Flashed to stock 4.0.4 yakju and immediately noticed touch sensitivity irregularity, particularly with the soft keys and with the keyboard. The problem usually lasts a few frustrating seconds before disappearing and returning to normal.
[Samsung Galaxy Nexus] execute_method:
I just got a replacement nex, and it has this problem. The previous unit did not. Same rom, same kernel. It has to be a hardware variation that isn't accounted for in most roms.

For instance, it happens on all 4.0.4 Aokp builds, but not on Gummy. There are differences in systemui, but both are using aosp base, so wth.

I'm gonna get another replacement and hope I get a good one...

Sent from my (*) using Tapafux.
[Samsung Galaxy Nexus] wilsonlam97:
You could be having a bad charger. Some chargers make my screen go nuts as well.
[Samsung Galaxy Nexus] danielkuhlman:
Try installing the Samsung galaxy s screen booster from the market. Maybe it's the placebo effect, but I barely have to touch my screen for any desired effect. I use Swype and I can fly with the app.

It says galaxy s only but I notice a huge difference

Oh and set it to super optimized. Works beautifully
[Samsung Galaxy Nexus] jonstrong:
This thread is the first time I'm reading about reduced touch sensitivity... I know it's not that old, but I've been using my Galaxy Nexus a LOT since getting it a little over 5 months ago, and it's as sensitive and responsive as the day I opened it... Also doesn't make sense to me, as there's nothing mechanical / no layer of anything to scrape off, etc. It really shouldn't degrade.... :what:
[Samsung Galaxy Nexus] osm0sis:
My guess is that everyone has it, but to varying degrees. Some have the bug on the naked screen and are the unlucky ones on the far end of the bell curve, and those who don't are on the near. In my case it wasn't apparent until I put a tempered glass screen protector on my Nexus. Clearly not just the protector though, as the screen-off-on restores sensitivity; Further evidence for the varying degree theory as I literally had zero problems before the protector came into the picture, was aware of this thread and had tested for the bug thoroughly back when I first got my phone. The protector just pushed me over the hump of the bell curve ;)
[Samsung Galaxy Nexus] metal571:
The very definition of a software-related bug.
[Samsung Galaxy Nexus] JediNinjafication:
I don't care really. I had the money and i was actually paying off an old Bill from almost 2 years ago and renewing service. expected a deposit and didn't have to so it still cost less than what i intended to give them

*This Jedi master be a Ninj-ESS*

---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------

I browse for four hours...plug in and browse Another 4

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] osm0sis:
thalamus thinks the screen's firmware might also be a possibility, as he saw nothing in his systrace:

https://github.com/thalamus/android-kernel/issues/17
[Samsung Galaxy Nexus] metal571:
Sounds possible. Well, firmware is still software, just at a lower level of course. I doubt we can get our hands on that though...
[Samsung Galaxy Nexus] osm0sis:
Yeah, sadly, desperately hoping for updated proprietary binaries might be all we have left.. :(
[Samsung Galaxy Nexus] metal571:
Hell even I'd like to take a crack at it, even if it's in freaking assembly.
[Samsung Galaxy Nexus] JediNinjafication:
what do we have to do to get it

*This Jedi master be a Ninj-ESS*

---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------

The firmware for screen.

Because I'm straight jacked

*This Jedi master be a Ninj-ESS*
[Samsung Galaxy Nexus] metal571:
Wouldn't that specifically be closed-source if the screen is made by a proprietary manufacturer?
[Samsung Galaxy Nexus] osm0sis:
https://developers.google.com/android/nexus/drivers#maguro:confused:

These are my only guess at what might qualify as screen firmware, and what I was referring to. Anyone know for sure? Or whether it's possible to update your binaries? I see there're some new ones under JRO03H, and then again, downgrading back to the 4.0.3 binaries is another intriguing thought...
[Samsung Galaxy Nexus] crobs808:
I browse for about 30-45 min each night. No lag.
[Samsung Galaxy Nexus] Guicrith:
FIX

Its hardware because this fixed it. tested for 30 min. when not touching it glitches when touching it is fixed.(the red wire is taped to top of sim slot)

It looks bad but works i will come up with something better if it works for 5 days straight.
[Samsung Galaxy Nexus] JediNinjafication:
Nicely done!
[Samsung Galaxy Nexus] delf0s:
So its a Sim slot issue? Maybe a false contact?
[Samsung Galaxy Nexus] metal571:
Looks more like a touchscreen sensitivity booster than anything else. I bet the software problem is still there, but you wouldn't notice it since overall the responsiveness has been improved through hardware.
[Samsung Galaxy Nexus] Guicrith:
It is not a sim slot issue.

Noise builds up in the screen turning it off removes the noise.(and so does touching sim slot)

I would assume that plugging in a usb cord and holding the metal rim of the computer end would also be ground but then your usb cord is always sticking out.

The screen senses the amount of electric current , the top of the sim slot is -(ground) screen is + so touching the screen gives the electricity a full circuit.
[Samsung Galaxy Nexus] delf0s:
So how does one fix this? I mean...theoretically