yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Themes and Apps] Neejay:
yep, it wasn't working. That's why beta 5 was released so quickly
[Galaxy 3 Themes and Apps] cowsquad:
thanks for tapatalk beta 5 yeah
[Galaxy 3 Themes and Apps] ale_bot:
Thanks Halco :). I m using int on AOKP build4 band int works very well

Ale from ICS, Roger
[Galaxy 3 Themes and Apps] Halco:
No problem :) So it works on ICS, i'll try it on GB now :)
[Galaxy 3 Themes and Apps] Dayfid:
It worked in CM7 Alpha 8 for me last night.
[Galaxy 3 Themes and Apps] Halco:
Ok thanks :)
[Galaxy 3 Themes and Apps] Dayfid:
No problem. :)
[Galaxy 3 Themes and Apps] Halco:
Tapatalk 2 update is officialy released today !

Mod plz close this thread, thx :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ian1:
When i try to boot into recovery it just boots into the screen it shows when ics was installing on my phone(Not download mode either) Do i have to flash cwm through odin again? Theres still a backup from clockwork mod on my ext. sd.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mooneyb:
Yes you have to flash CWM through ODIN again. The same way you did under Gingerbread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] droid512:
Search the forums for how to root ics leak
[Galaxy Tab 10.1 Themes and Apps] jacobb23:
anybody have a market apk that has music in it? My tab market has yet to update...even though i have google play and everything else
[Kindle Fire General] michaeldolishny:
Well i watched natmell or what his name is on youtube to root my kindle and after i rooted it didnt get some stuff and i also rooted before so the way i erased the root is deleting internal memory and so i did that and when it turned on it only went to twrp and i didnt do back because i want planning on doing a flash rom or anything just yet. Ive i have spend the last 7 hrs researching every possible way. Ive tried the adb codes to recover or what that didnt work just says cant find the drive. Tried cmd codes like adb shell etc says doesnt exist or whatever. I updated the driver on device manager that didnt work ive serously tried everything including downloading room and then flashing but that didnt work just goes back to twrp. Ive serously tried everything. Is is permantly broken, and ideas of what i can do to fix. please message me or email me.
[Samsung Galaxy Nexus] RogerPodacter:
Problem summary

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).

Please star this issue officially so Google can fix:

Link is http://code.google.com/p/android/issues/detail?id=29734

Note: Downloading & using Screen filter application from play store, with brightness set to
[Samsung Galaxy Nexus] wpghtc:
Your hands are really dirty or really dry. Try moisturizer or something.
[Samsung Galaxy Nexus] @rbiter:
Been using my screen for almost hour straight now. No issues.

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

iphone. helping computer illiteracy become popular since 2007.
[Samsung Galaxy Nexus] RogerPodacter:
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
[Samsung Galaxy Nexus] anfozy:
ios 6.2 doesnt get issues.
[Samsung Galaxy Nexus] Mrbigshot:
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
[Samsung Galaxy Nexus] gokpog:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.

But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
[Samsung Galaxy Nexus] kristovaher:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).

This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).

If problem persists then return under warranty.
[Samsung Galaxy Nexus] adrynalyne:
My wife had this issue once.

It was the third party launcher she was using.

I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.

It was ADW EX, fwiw.
[Samsung Galaxy Nexus] MatAuc12:
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.

And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.

Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
[Samsung Galaxy Nexus] EP2008:
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RogerPodacter:
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.

I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.

Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
[Samsung Galaxy Nexus] RobbyRob:
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
[Samsung Galaxy Nexus] RogerPodacter:
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.

Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
[Samsung Galaxy Nexus] tea_dub84:
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
[Samsung Galaxy Nexus] gogol:
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.

I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.

The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
[Samsung Galaxy Nexus] anMoney Dev:
I know this is my first post, but I can definitely confirm this issue.

I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.

My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
[Samsung Galaxy Nexus] byrds8:
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0 :)
[Samsung Galaxy Nexus] TechNoir:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.

Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
[Samsung Galaxy Nexus] RogerPodacter:
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.

I'll post what I just sent to arbiter which gives more insight.

Yes my face literally flew off!
[Samsung Galaxy Nexus] kennethpro22000:
Shrijith1, You can report to Google by the link below

http://code.google.com/p/android/issues/detail?id=29734
[Samsung Galaxy Nexus] kennethpro22000:
Claud_face, can u provide the link of the version 4 aokp jelly bean rom,thanks a lot!
[Samsung Galaxy Nexus] akarach:
I've capture my problem on my Nexus. What's problem? Touch screen or gravity sensor?

http://youtu.be/arFn95YQ6Hg
[Samsung Galaxy Nexus] shrijith1:
I am afraid, this could be a different issue. I dont see this.
[Samsung Galaxy Nexus] delf0s:
Quick question for everyone... Are you guys using stock keyboard?
[Samsung Galaxy Nexus] franciscojunior:
I also noticed problems with touch sensivity with JB update.

I'm using SwiftKey keyboard. But I also notice that the home, back and multitask soft buttons also suffer from this problem, so I don't think it is related to keyboard.

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] dark06:
Any news about your replacement?:)

fod
[Samsung Galaxy Nexus] niacin77:
Mine was similar to yours. The bottom of the screen, especially the soft keys were affected. It would work a little better when held in hand. But would not work as well when it's on a flat surface. (Maybe the static electricity when hand-held has to do with it?)

I sent it out to Samsung for repair last week. Here's the email I just received:

Original Problem:

TECHNICAL INQUIRY - LCD / TOUCH PANEL / LED - TOUCH SCREEN NOT RESPONDING

Problem found:

TOUCHPAD FAILURE

Solution:

REPLACED LCD - REPLACED TOUCHPANEL
[Samsung Galaxy Nexus] shrijith1:
akarach and niacin77,

Few questions,

1) Do you see this problem all the time ? If so, whats the trigger to reproduce the issue ?

2) Does this problem go off when the screen is locked and unlocked ?
[Samsung Galaxy Nexus] delf0s:
I've noticed that when you open certain apps it starts to happen. I also noticed that my phone got better when I installed SwiftKey. My original version is yakjuxw... I'm wondering if this has anything to do with it. Maybe there is a slight hardware difference from original yakju to other versions.
[Samsung Galaxy Nexus] chrisgtl:
This is what i have just done;

Goto developer options, make sure developer options is enabled via toggle at top right.

Enable pointer location and use a solid black wallpaper so you can see the pointer trace better.

Swipe the top half of screen fast without taking your finger off. I get a solid blue squiggly line, no problems.

Then do the same on bottom half of screen, as soon as my finger starts swiping near the soft keys I get red lines and my squiggle breaks up.

Turning the screen off and on sometimes let's me squiggle constantly without any red lines but most of the time my lines break up if drawing over the soft keys.

This may sound silly but is it something to do with the google circle that appears when you hold down the middle soft key? Can we disable that function?
[Samsung Galaxy Nexus] niacin77:
1) Didn't see it all the time. I don't know what triggers it. It seems to be working much better when my fingers are a bit sweaty though :)

2)Screen lock unlock didn't seem to help it. A reboot would help it for a bit though.

---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------

I had done the same test before and encountered the same exact results you had. The touch sensitivity tapers off gradually towards the very bottom end of the screen. It almost feels like the curved screen has something to do with it..

I had the problem on 4.0.4 also, so I don't think the google circle is causing the issue.
[Samsung Galaxy Nexus] shrijith1:
Steps to reproduce the issue

I think I have nailed down one of the possible triggers for this issue to happen.

1) Open Messaging app.

2) Click on Home softkey.

3) Click on Task list softkey.

4) Select the messaging app.

You should be able to see the issue now.

Some points I have noticed:

1) I can register a touch with a minimum of 0.28 pointer.

2) With this issue I need approximately 0.39-0.40 for the touch to register.

3) The issue is slightly bad when I place the mobile on a flat surface, say table on a table, with messaging app in portrait mode.

4) In all the scenarios, mostly the soft keys are the ones, where the touch sensitivity issue is seen.

Can somebody check if they are able to reproduce the bug with the steps given ?
[Samsung Galaxy Nexus] delf0s:
Did everyone experiencing the issue originally yakjuxw?
[Samsung Galaxy Nexus] metal571:
I figured out that the problem occurs only if you press on recent apps AND select an app from the recent apps menu. Otherwise, the touchscreen will act normally. Once you do that, you will have the issues. This is on a brand spanking new GNex direct from the Play Store that just hit my doorstep a few hours ago after updating to 4.1.1. Someone needs to report this...
[Samsung Galaxy Nexus] akarach:
> 1. Not all time. Just sometimes but ofter. Previously I don't how to trig this issue till I read your comment.

> 2. Yes, it gone when I locked screen and unlocked.
[Samsung Galaxy Nexus] metal571:
I see the issue everywhere after the first 4 steps here. After you select something from the recent apps, the problem begins, and I can't type fast anymore without a huge number of missed keypresses until I lock and unlock the screen again, after which the phone goes back to normal until I use the recent apps key to select another recent app again, then the issue occurs again until I lock/unlock. It's a cycle, and that's definitely the trigger.
[Samsung Galaxy Nexus] dark06:
Tried for a week not using the recent apps and it still gets the issue.i can trigger it 100% when browsing may pics scrolling really fast.also happens more frequently when using xda prem app

fod
[Samsung Galaxy Nexus] metal571:
Try this:

1: unlock phone

2: tap the home button a ton of times, it should register almost every time if not every single time.

3: hit the recent app button and go to any other recent app that was open already.

4: go back to the home screen (i find i have to press the home button twice to even get there at this point)

5: now tap the home button quickly and repeatedly again

I find that the home button only registers if i press pretty hard now, otherwise it never registers my touch at all. Anyone else?
[Samsung Galaxy Nexus] shrijith1:
Yes, I can confirm this. So, looks like selecting a running app using the "recent apps softkey" is one of the most common trigger. Now, how can this be a hardware issue if this goes away by locking and unlocking ?

People who are getting replacement for this - can somebody let us know if the new unit doesnt have this ?
[Samsung Galaxy Nexus] metal571:
I just requested an RMA for mine. I'll post here when I get the new one, not sure when that's gonna be yet. Someone else over at AF responded to the same process and said theirs works fine. Maybe the touchscreen isn't calibrated right in some phones and it would need fixing at a factory.
[Samsung Galaxy Nexus] franciscojunior:
I can confirm that.

I don't think this is a hardware related issue. I think it is a software one. Let's hope Google fixes it in the next iteration.

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] metal571:
Both of you guys are on the 4.1.1 latest OTA right? Anyone know if this does NOT happen on some custom ROMs?
[Samsung Galaxy Nexus] franciscojunior:
Yes. I'm on latest ota. When I was on 4.0.4 I didn't notice this problem.

Maybe this is something about the fix for the delay when showing up recent applications?

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] metal571:
Very possible. I actually reported the problem via phone directly to Google themselves and also cancelled my hardware service with Samsung. I'll update if we get any progress. I'm surprised more people haven't noticed this problem, it's pretty bad, especially for people who are swift with qwerty virtual keyboards.
[Samsung Galaxy Nexus] @rbiter:
Its not that bad if the forum isn't overrun with the problem and it hasn't been narrowed down to a cause yet. The people who have it are acting like everybody has it and some of us don't notice. That is not the case. Early on I tried to replicate it and have had no success.

need more high def music...
[Samsung Galaxy Nexus] aeoveu:
All of the above apply to me as well. I posted this bug in bigxie's rom thread the other day and no one was able to repro it.

Strangely, someone in the office has GN and this bug doesn't show up on their phone (they haven't officially upgraded from the leaked ROM to the full OTA fearing this bug...).

It drives me nuts - but I've managed to find another (rudimentary) workaround: drag (not swipe, drag) the notification bar to the bottom, and in the last centimeter, it'll just lose contact and "drop" the bar. You need to spread the surface of your finger over the screen in order to register it.

When you've spread your finger, move it up and down in haste - and after a little while (totally random), it'll begin to work normally - until you hit the task switcher icon and switch to another app.
[Samsung Galaxy Nexus] metal571:
Thanks for the reply. So far all I know is that this only exists for sure on the latest JB OTA. I assume other ROMs based off of different AOSP code won't have this problem. So I'm glad it's not my phone at least. I'm really confused about your dragging and dropping the notification bar at the bottom...youd probably have to make a video. Once this bug appears I still have to lock/unlock the phone to make it go away again.
[Samsung Galaxy Nexus] guidocioni:
Same problem here. I think that's from 4.0.4 that i've this problem but i thought that was only my problem...now i've seen thera are other people experiencing this issue! BTw now i'm on stock 4.1.1 and i'm trying a new room since the bug is quite annoying : i cant use recent apps cause the bug suddenly appears every time
[Samsung Galaxy Nexus] metal571:
Are there any AOKP or CM10 JB ROMs that don't have this issue? As soon as I activate this phone on T-Mo prepaid I want to flash something that's either CM or AOKP but that hopefully doesn't have this stupid bug in it
[Samsung Galaxy Nexus] guidocioni:
Did anyone tried to flash the factory image instead of the 4.1.1 OTA? I'm on the OTA right now but i think that i'll give it a shot..maybe the bug will not be here..
[Samsung Galaxy Nexus] delf0s:
Tried the factory image (4.1.1)...bug is still there. :(
[Samsung Galaxy Nexus] guidocioni:
****...

Tried superwipe?

Could please someone report if the bug is gone with custom roms?
[Samsung Galaxy Nexus] delf0s:
Wtf is superwipe?
[Samsung Galaxy Nexus] guidocioni:
:p Just wipe cache+wipe dalvik+factory reset

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

Anyway tomorrow i will try MinCo. I don't like too many customization, i like a ROM that just WORKS. That's why i had stock since there but i cant ****in go over this bug.
[Samsung Galaxy Nexus] shrijith1:
Thanks a lot for posting the workaround. However, with whatever I understood, I tried this and could not get it to work. Would you be kind enough to do a video ? :)

Thanks again.

---------- Post added at 05:35 AM ---------- Previous post was at 05:30 AM ----------

claud_face, can you share the link for the JB ROM you have mentioned ? Can you confirm that after installing this ROM, you have never got this issue ?
[Samsung Galaxy Nexus] akarach:
Yesterday, I went to samsung service center. show them about this issue (my video). They said never seen before but they try to change new LCD. After that I never get this problem again.(about a day ago, on same rom jelly bean and all programs)

I don't know what exactly problem, but my thinking is LCD problem or LCD quality problem.
[Samsung Galaxy Nexus] metal571:
There's still something wrong with the software...the screen shouldn't get more sensitive when switching to a recent app no matter how good the touchscreen grid is
[Samsung Galaxy Nexus] RogerPodacter:
This bug existed before that circle for Google now. It happened on 4.0.4 so I don't think disabling the circle will help at all.
[Samsung Galaxy Nexus] RogerPodacter:
This EXACTLY describes the bug for me too, down to the same 0.28 value when its working properly. Then when the bug starts it goes up to 0.40 sensitivity.
[Samsung Galaxy Nexus] guidocioni:
A friend of mine doesnt have this bug on 4.1 (JRN84D)
[Samsung Galaxy Nexus] guidocioni:
Ok, i've just flashed JRO03H and the bug seems to be gone...

testing for a few days
[Samsung Galaxy Nexus] metal571:
Any idea on when that is coming over as an OTA? Sounds like they did a bugfix release. I just read that the binaries got released just 2 days ago
[Samsung Galaxy Nexus] franciscojunior:
Where can you get the 03h from?

Did you compile from sources?

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] guidocioni:
No, there is a thread with flasbable zip here in the forum! I think i'm gonna stay with this build.

The link for forum is http://xdaforums.com/showthread.php?t=1813185

Inviato dal mio Galaxy Nexus con Tapatalk 2