yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rayiskon:
I have an international yakju gnex, i thought i was one of the rare who doesn't have any major issues, great display etc... but after following this thread for a while, and even though i think i posted here a couple of months earlier that i'm not facing this issue, i tried to replicate it by opening an app from the recent app list , and in most of the times (not always), the touch sensitivity is reduced, i don't have major problems like some of the guys here, like touchscreen not registering a tap, but it's clear that i have to press harder. Turning screen off and then on brings the phone back to normal performance. The thing is that many people have this issue,but they are not realizing it because some of us have lil issues (i.e small drop in sensitivity), other guys notice it bcoz of the obvious problems i causes (completely losing sensitivity in the lower part of the display). My opinion is that it is a software thing, hopefully the guys at google will take a look at it. I'm using stock JB with stock kernel.

P.s. for anyone who wants to try to replicate it, just go to the recent apps list and launch an app from there, it might not cause an issue everytime, but if u try it several times i'm pretty sure u'll see it.
[Samsung Galaxy Nexus] guidocioni:
Iper quote :p

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] aeoveu:
I'll try making a video tomorrow... provided I can find a camcorder :)

The workaround requires pulling the notification bar down and up several times.

Strangely, this never happened with ICS.

sent from my mini tractor
[Samsung Galaxy Nexus] BrUhNiGGs:
This just has to be a software issue. I have had 5 VZW replacement gnex's so far and every time I flash JellyBean 4.1.1 the issue is there. I rarely see it happen on stock 4.0.4 IMM76D or IMM76Q. Its not a hardware issue after all.

I'm possibly going to make a video to show the type of issue I have and see if anyone can relate to it.
[Samsung Galaxy Nexus] metal571:
Bug is still there for me on JRO03H.
[Samsung Galaxy Nexus] guidocioni:
Yep, bug it's still on JRO03H But less. Anyway i decided To flash Back again JRO03C cause the latest build had some problems.. I think we just should to be used to this bug, and I think that most of the people here don't notice at all, cause it's not the same in every phone. I hope that Google will fix this but I'm not sure that someone can report this bug in a correct way, so, for now, I'm trying not to use recent apps :p... And I still don't remember if I had this with ics...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] metal571:
If someone can link me real quick to 4.1 AOSP for a takju-maguro I'll see if I too can confirm that the problem wasnt there at that point.
[Samsung Galaxy Nexus] hp13:
i installed xneon hd rom + trinity kernel JRO03H binaries and bug is gone for me.. i am using it for few days... feel better now.. hated stock JB 4.1.1 screen sensitivity.
[Samsung Galaxy Nexus] guidocioni:
I've tried xenon with stock and franco but bug was still there for me

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] metal571:
Maybe it's the Trinity kernel that helps?
[Samsung Galaxy Nexus] whittikins:
Trinity didn't help me (running latest AOKP JB 4.1.1).

Is using the Task switcher the only way to produce this issue? If so, I'm going to find a 3rd party task switcher to use until it's fixed. Let me know if you come up with another way to produce it. Thanks!
[Samsung Galaxy Nexus] metal571:
My GF just got the phone and she also has the same issue. It seems to be Nexus-wide as far as I can tell as long as the ROM is JB-based. The recent apps button seems to be the only way to reliably produce the bug still. Also whittikins, what task switcher do you think would work best as a replacement for now?
[Samsung Galaxy Nexus] RogerPodacter:
It definitely gets triggered in all sorts of situations, not just the task switcher. that's just one way to trigger it for me.
[Samsung Galaxy Nexus] shrijith1:
Even I thought the same and tried to use "Notification Toggle" app. It has a shortcut for Recent apps, but, again it reproduces the issue :(
[Samsung Galaxy Nexus] whittikins:
I haven't had a chance to try very many, but right now I'm using one called Simple Task Switcher. You can choose to display a grid or icons or a list of the recent apps. Since I'm using AOKP, it allows me to re-assign the navigation buttons. I assigned the Recents button to "Simple Task Switcher" to completely take the built-in task switcher out of the equation. I'll post back and report whether or not this prevents the issue from occurring. It definitely appears to avoid the issue that the built-in switcher causes.

---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------

If the app is simply activating the built-in task switcher, then that makes sense. You should try a 3rd party "task switcher" from the play store. Avoid using the "recents" navigation button (or re-assign it to a different app/action) to see if that prevents the issue. That's what I'm trying, and so far it appears to be good.

---------- Post added at 08:54 AM ---------- Previous post was at 08:52 AM ----------

Please let me know if you find a way to reproduce it without using the Recents menu at all. I'm at work and haven't been able to test it too much, but so far I haven't experienced the sensitivity increase as long as I avoid the built-in Recents (task switcher).

Thanks
[Samsung Galaxy Nexus] BrUhNiGGs:
So I captured the problem I am experiencing with this issue and uploaded it

http://www.youtube.com/watch?v=3RXqMIJEJJE

Please watch and see if any of you guys relate to my issue.

its the same lock/unlock that fixes it but comes back later.

And at 0:06 you can really tell how the screen does not register the swipes.
[Samsung Galaxy Nexus] whittikins:
Yeah I've experienced the same thing. This is probably the same issue.

Basically we've found that selecting an app from the Recents list (task switcher) reduces the sensitivity for the entire screen. To reproduce just open Messaging, hit Home, hit Recents, select Messaging. Now your screen is less sensitive. Turning screen off/on temporarily fixes this until you use the Recents again.

From your video, I don't know if you had used the Recents list before your issue showed up, but I'm hoping you did so that we can narrow it down. What I'm doing now is completely avoiding the Recents list by using a 3rd party task switcher instead. I've done this all day and haven't experienced the reduced sensitivity at all, but I'm going to continue this for a few more days. Details here: http://xdaforums.com/showpost.php?p=29992410&postcount=240
[Samsung Galaxy Nexus] metal571:
Yeah probably the same sort of issue from that video. I just tested CM9 9.0.0 and AOKP milestone 6, and neither of them have the bug at all with recents. This is because they are 4.0.4. So this is related to JB's AOSP code from what I can tell so far.
[Samsung Galaxy Nexus] whittikins:
Aren't people saying 4.0.4 is the version that introduced this bug? Sorry, just trying to get caught up with all this. I owned every iPhone since release, so Android is very new to me!
[Samsung Galaxy Nexus] metal571:
Glad you at least made the switch. People were saying 4.0.4 (ice cream) introduced the problem, but i didnt see the bug on AOKP or CM9 9.0.0 "stable" when I just flashed both of those today. Very strange
[Samsung Galaxy Nexus] BrUhNiGGs:
I may have used the recents button before I shot the video and had the problem. Cause I just flashed a CM10 kang jellybro and if I press the recents and press any app on the list the issue comes. So I guess it has something to do with the recents button!

I too am going to see if the I get the issue without pressing the recents.
[Samsung Galaxy Nexus] metal571:
Yay another confirmation. Yeah it seriously looks like everyone has this problem. What's the best way to get in touch with Google about this bug?
[Samsung Galaxy Nexus] tgyberg:
I had it on 4.0.4 after I flashed franco's linaro kernel. Didnt have it on stock JB but now have it after flashing the JB franco linaro. No idea if related but want it to go away!
[Samsung Galaxy Nexus] rayiskon:
Swiping like a mad man is not a way to show the problem :D so far the recent apps method has been the only solid and reproductable one.
[Samsung Galaxy Nexus] metal571:
Yeah, typing fast is the best way to feel the problem. open messaging, go back home, open messaging again through recents, start typing fast. youll miss about half the letters due to the bug. lock/unlock and youll type fine again
[Samsung Galaxy Nexus] BrUhNiGGs:
Well, in my case yes lol. In reality you would really be able to see what I was producing in the video.
[Samsung Galaxy Nexus] rayiskon:
I know man, u don't even have to type fast, just type, u'll feel the feedback from the keyboard is different, u have to press harder. The video above shows some maniacal swiping skills :D
[Samsung Galaxy Nexus] hp13:
Avoid recent button and problem solved...:D
[Samsung Galaxy Nexus] metal571:
The AOKP method is best for me, where you nuke the recent apps button and replace it with something like Simple Task Switcher. That's a great way to get around the problem without deleting much functionality.
[Samsung Galaxy Nexus] tgyberg:
Agreed! I was waiting for a friction fire to start! :laugh:
[Samsung Galaxy Nexus] BrUhNiGGs:
Well actually I can confirm that the issue persists even without pressing the recents button. It happened to me already.

I noticed that if I go to home and press tapatalk I get the issue. This **** is just random and I'm getting fed up with it
[Samsung Galaxy Nexus] metal571:
Me too but I have no idea why and it seems to happen far less often as well
[Samsung Galaxy Nexus] BrUhNiGGs:
For me, it happens every 30 seconds. This phone is almost unusable.
[Samsung Galaxy Nexus] metal571:
What in the world? That's never been the case for me. What ROM is that?
[Samsung Galaxy Nexus] petrsiri:
is there any app allowing us to reassign the navigation buttons? (For those of us who don't have aokp)
[Samsung Galaxy Nexus] BrUhNiGGs:
Just about every ROM I've ever used for my Nexus. I'm currently on AOKP nightlies. Jellybro, Liquid, JellyBelly, Vicious, etc. Same thing happens
[Samsung Galaxy Nexus] whittikins:
That's really weird because I still haven't noticed the issue since avoiding the Recent button. Let us know if you find another way to produce it.

---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------

When it happens, does it ever go away without turning the screen off?
[Samsung Galaxy Nexus] metal571:
No, never on its own. And it happens very, very rarely without using the recent apps button.
[Samsung Galaxy Nexus] hp13:
hope google looks at this thread and fix it in its next update
[Samsung Galaxy Nexus] guidocioni:
I think someone has to change the title of the thread including our last statements : bug on 4.x.x rom...etc. We have to make this thread more visible so people will start to notice on their phone.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] whittikins:
100% agreed. I was hoping someone else would step up :)

I might do this sometime today if no one else has!
[Samsung Galaxy Nexus] RogerPodacter:
I updated the thread title. Let me know if you'd like it changed more.
[Samsung Galaxy Nexus] whittikins:
Summary of the issue and possible workaround

Would you mind including some of the recently discovered info about what seems to cause it and possible workarounds? You can copy/paste this if you want:

Known cause

(might be others): selecting an app from the Recents list (Task Switcher)

Temporary fix

: turn the screen off, then back on

Workaround

: avoid using Recents list (you can use a 3rd party task switcher instead)

How to test

: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.

Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
[Samsung Galaxy Nexus] Snow02:
Yep. I can confirm this. My nav bar is basically useless until I turn the screen off/on. Definitely an odd bug.

I'm on AOKP JB.
[Samsung Galaxy Nexus] RogerPodacter:
Updated. Let me know if that's good.
[Samsung Galaxy Nexus] whittikins:
Great, thanks. I actually just added some color/bold to the Prs numbers for visibility, but feel free to make any changes as needed :)
[Samsung Galaxy Nexus] blackplague1347:
Either I use my phone like a Neanderthal or this bug is constant, because I've been trying this for a little while now and my taps have never been under .32 or .34. Most are in the 30's and 40's. Using the Messaging -> Home -> Recents -> Messaging doesn't seem to make any noticeable difference.

This thread is interesting, however. For the longest time I thought I was always just tapping my screen too lightly or something. I never really notice unless I'm typing on the keyboard, because I tend to type pretty quickly.
[Samsung Galaxy Nexus] whittikins:
Do you have a screen protector by any chance? 0.28 is the lowest I can ever get with a light tap, but many times I'm getting .32 or so. The problem is that after the bug is introduced, I almost can't get below 0.40 at all.
[Samsung Galaxy Nexus] BrUhNiGGs:
Is Simple Task Switcher an app on the market cause I dont see it

Edit: Nevermind got it. I'm going to test with this also and see if the issue comes back. I really don't like how it looks though...lol
[Samsung Galaxy Nexus] BrUhNiGGs:
Okay so even with the simple task switcher set for the recents I still got the touch issue.

I'm going to try to figure out what else reproduces the problem other than pressing the recents button.
[Samsung Galaxy Nexus] dark06:
Try darkjelly theme. Sometimes after unlocking it would trigger the bug again instsntly, possibly a gpu bug?

fod
[Samsung Galaxy Nexus] blackplague1347:
Yeah I have some generic screen protector from wal-mart on it right now. I'd like to get a glass screen protector, but I don't want to shell out the money until I know it will work with my Case-Mate Pop case. I imagine the sensitivity would be even worse with one of those on my phone.
[Samsung Galaxy Nexus] rayiskon:
More people should step up and make some noise about this issue, otherwise i'm afraid i don't see a fix on the way.
[Samsung Galaxy Nexus] tgyberg:
For the past couple of days I have not touched my recents button and I have not had the bug at all. Guess I'll just pretend recents doesnt exist! :victory:
[Samsung Galaxy Nexus] jtseidner:
I'm on my 3rd Nexus. Dropped the first one, and my replacement had horrible purple screen and insurance replaced it again. The odd thing is that my first 2 never had this touch sensitivity problem. This third one has this bug :(

Avoiding the recent apps button does help the issue for me.

Should we be telling people to "star" or comment in Google's issue tracker?

http://code.google.com/p/android/is...r Summary Stars&groupby=&sort=-stars&id=29734
[Samsung Galaxy Nexus] metal571:
How can we?
[Samsung Galaxy Nexus] petrsiri:
Anyone knows any mod (not rom) or application allowing us to remap the soft keys? This way we could at least reassign the recent button to open a third party task switcher...
[Samsung Galaxy Nexus] Petrovski80:
Yup, I can reproduce this since I have updated to JB. Didn't have or didn't notice it on ICS.

I don't use a screen protector by the way.
[Samsung Galaxy Nexus] delf0s:
I get this bug a lot..and I don't ever use the recent apps button. I think it's a sort of memory leak, but can't be sure.
[Samsung Galaxy Nexus] BrUhNiGGs:
Same here. I get the issue even without using the recents. And when I do, I get it too.
[Samsung Galaxy Nexus] whittikins:
Can anyone find another cause of this besides the recents list? I haven't noticed it happening since I switched to a 3rd party task switcher.
[Samsung Galaxy Nexus] dark06:
Can anyone confirm on latest franco, bug has disappeared? It has not occured since i flashed 5 hours ago, or maybe my phones trolling again :/

fod
[Samsung Galaxy Nexus] whittikins:
It definitely still occurs after I use the recents button. I'm on Franco 241.
[Samsung Galaxy Nexus] BrUhNiGGs:
I dont think it has to do with the kernels. I've tried just about every kernel for the Nexus. Issue still persists... Later when I have time I am going to try to reproduce the problem other than using the recents button because It still happened when I used a third part task switcher.
[Samsung Galaxy Nexus] dark06:
Yeah it still does occur.going back to trinity now. Well try this, go to a site with alot of text and links, for example gerrit commits, i try to flicker through the text with my finger, it lags for a microsecond, then i know that the bug is there.

fod
[Samsung Galaxy Nexus] x_Mischka_x:
I just got my GNex today, and also have this problem. It isn't as bad as some others have, but opening an application with the recents menu consistently increases the minimum Prs for my lightest touches, and typing seems difficult at times. I really am hoping this is merely a software issue, because I got it used, so if it is hardware I'm basically out of luck.

I'm on stock, unrooted Sprint Galaxy Nexus running 4.0.4.
[Samsung Galaxy Nexus] metal571:
Yeah, it's definitely software. The issue is just more severe on 4.1.1.
[Samsung Galaxy Nexus] x_Mischka_x:
It does make me feel better that others are having the same problem. It's really not a major issue, because simply slowing down typing and pressing a little harder seems to work fine, but I certainly can notice the difference from my Nexus S. Been wanting this phone forever, and overall am happy with it (even though the previous owner did get a few scratches on the screen :'( ).
[Samsung Galaxy Nexus] metal571:
If the issue was hardware, locking and unlocking the screen wouldn't help at all. Here, it completely eliminates the issue for me.
[Samsung Galaxy Nexus] x_Mischka_x:
Yeah, for me as well. Just curious that more people haven't noticed the problem and that this thread hasn't blown up. Maybe most people just naturally press harder or something.
[Samsung Galaxy Nexus] metal571:
You aren't alone. I'm kind of very surprised this wasn't caught by a lot more people. All we can do is continue to ***** at google.
[Samsung Galaxy Nexus] whittikins:
I think there are many people that don't use the Recents list. :)
[Samsung Galaxy Nexus] x_Mischka_x:
I just tried the pointer location on my Nexus S 4G, and even hovering my finger over the screen registers as a press, and I can get Prs as low as 0.11. Much better than the GN when it's at its best. Slightly disappointing to say the least.
[Samsung Galaxy Nexus] rayiskon:
Maybe adding a poll question to OP would help see the number of people who have recognized this issue..
[Samsung Galaxy Nexus] aeoveu:
I know I was asked to make a video - but couldn't. And still can't - cause my phone's gone for warranty (messed up USB socket). But I see someone else has made an attempt at the video.

That said, I strongly believe it's a software issue - I ran a logcat, went to the recent apps menu, got the bug, and copy-pasted the log.

Inspecting it resulted in lots of dalvik messages before the screen went off. It also mentioned velvet.apk - which is the Google search/Google Now file. Disabling Google search disables Now as well - but doesn't quite help.

It's definitely a change in the core service - so here's a question: what if you use a custom keyboard? Does that help? I don't know how I reached to this conclusion, but could some of you try another keyboard and see if the recent apps issue persists?

(yeah, I know I sound silly - but the keyboard is something which changed in Jelly Bean as well).
[Samsung Galaxy Nexus] guidocioni:
I'm using SwiftKey from ics..

Inviato dal mio Galaxy Nexus con Tapatalk 2

---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------

I meant "since"

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] guidocioni:
Roger maybe you can add the link to Google issue on first post!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ac3theone:
This happens to me to and I'm on stock jb
[Samsung Galaxy Nexus] iankellogg:
Stock jb also having major issues. The issues in OP is exactly the problem I am having. Work around works just fine but still annoying issue.
[Samsung Galaxy Nexus] BrUhNiGGs:
So I have been using a third party task switcher (simple task switcher) this whole day and found that the sensitivity doesn't persist. Then once I used the regular recents function from the OS the issue came back instantly - after selecting any app.

What I really wonder is if the issue is still there if you use a different style of task switching. Back in ICS in a rom like AOKP, you could switch to a different style like Sense 4, or WebOS. Once AOKP implements those into JB rom, I would like to see if it the sensitivity comes back when using those different styles. Has anyone thought that, that would be a possible solution?
[Samsung Galaxy Nexus] whittikins:
I'm glad the workaround is helpful for you. I wish a developer could look into this and see if it's a rom or kernel issue. It seems like someone knowledgeable could monitor what happens when selecting a "recent app" from the list and find the problem. Any takers? :)
[Samsung Galaxy Nexus] BrUhNiGGs:
The thing is, Im not a fan of the UI of it. The only closest thing I could find that looks like the original is "Perfect Task Switcher" but it FC's every time you try to select an app off the list... Oh how I wish Google could fix this already.
[Samsung Galaxy Nexus] metal571:
I'm not exactly sure how to take a logcat after or while hitting the recents button but if anyone needs that information I could provide it to a dev after I figure out how.
[Samsung Galaxy Nexus] whittikins:
Trust me, I'm right there with ya. I'm not crazy about the appearance either. I'm currently using the list view because the icons don't sort the way I'd like. I also got force closes with that other app, so it must be a jellybean problem.
[Samsung Galaxy Nexus] BrUhNiGGs:
Yeah same. I dont like the way the icons sort either... I really have to look for which app I would like to go to. Another one I found was Task Trey - Beta. It resembles the UI of iOS except it is VERY low quality and the icons are too pixelated and blurry. And Visual Task Switcher was good but only shows apps that are running...
[Samsung Galaxy Nexus] guidocioni:
Anyone have tried JRO03L

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] kennethpro22000:
I have tried the jro03l already,the issue happened again. Bros here can have a try.

P.S.

1.For my nexus,the issue will disappear after some time without locking and unlocking the phone. I am quite sure it's a software bug.

2. The issue can be triggered by typing msg>home>menu>msg and also opening the browsers browsing a specific page.My methed to delay the issue is to use the non-full screen browser, e.g. floating browser
[Samsung Galaxy Nexus] BrUhNiGGs:
I think everyone should make multiple google accounts or use all that you have and star this issue so it can be noticed by google. Haha worth a try!
[Samsung Galaxy Nexus] guidocioni:
Ok.. Thinks I've found something!!!!

Try to download screen filter from the market and lower the brightness of the screen (I'm using 48% slot). I've tried to reproduce the issue a dozen times but...nothing! If I turn the off screen filter the issue is still there.. Can someone try that plz?? :eek:

Inviato dal mio Galaxy Nexus con Tapatalk 2