When I press on the very bottom of the screen (edge of the glass), it acts as a click to about 1/3 the way up the screen. This is annoying by its self (and doesn't seem ROM related) but also my screen sometimes locks up, with a point at about 1/3 the way up the screen, and horizontally in the middle, and I can't do anything until I lock the screen and leave it off for a second. More recently, but related to this issue, the keyboard when typing hasn't been accurate. I've tried to type 'a' but got caps or 'q' instead, and I get letters I didn't press.
This is not ROM related, as it started happening on CM6 about a week ago, and I've flashed Ava V9, Myn's 2.2, FrEaKy Evo, and CM6, and I have tried stock kernels, and Kings. It seems to lock up more when plugged in also. I've been watching the forums and I haven't seen anyone else post about this, is it just me? It seems very hardware related, but if there is a fix for it that someone knows about, please let me know.
If I get around to it I might take a video of what I'm talking about, but probably only if it's requested.
I'm currently running Myn's Two-Point-Two with King's CFS #11 and am still getting the issues. I've rebooted, and wiped cache/dalvik, flashed new roms, reflashed, nothing.
I am having the exact problem, except that the spot that keeps getting phantom clicks is at the very top of the screen, so the drop down bar starts freaking out. I downloaded the program 'dotty' and it is showing that a touch is being registered in the expect spot, so I'm pretty sure it is just an issue with the screen hardware. I want to take it to a sprint store and see if they can replace just the screen instead of getting a brand new phone because I have so much stuff downloaded on it and I don't want to lose data/settings.
It happens a lot, but then I will have days at a time that it stops happening...its just very strange.
Its good to hear that I'm not the only one with this problem. Currently running rooted stock froyo. unrevoked forever. Original June 7th release device.
same here...was happening witht he W/q as well...but when your viewing a white page you can see a light on the screen brighter than the rest...
mrjeancw said:
same here...was happening witht he W/q as well...but when your viewing a white page you can see a light on the screen brighter than the rest...
Click to expand...
Click to collapse
W/q? what are you talking about there?
also the light bright spot is completely unrelated: evo developing a light spot in middle of screen
Screen burn possibly due to overclock
Bright spot in the lower right of screen
bhughes3 said:
I am having the exact problem, except that the spot that keeps getting phantom clicks is at the very top of the screen, so the drop down bar starts freaking out. I downloaded the program 'dotty' and it is showing that a touch is being registered in the expect spot, so I'm pretty sure it is just an issue with the screen hardware.
Click to expand...
Click to collapse
I downloaded dotty, and it's saying my spot is at:
X: 159.6
Y: 363.5
and P which I'm assuming is the size of the area being touched at .937.
I tested P and it does seem to be how big of an area you're touching but the biggest that I could get using my thumb was only .235, so it's a huge area and constantly in the same spot. Some times it gives me two points or one a bit up and to the left.
Guys
2 quirks
1) sometimes when entering my PIN on voicemail, the screen just blanks out - it doesn't happen every time but probably 1 out of 3 times. I tested dialing 611 and entering digits and it never happens
2) Flipping screens on widgets or apps, sometimes it doesn't move to the next screen. I have to make sure my finger goes all the way to the right of the screen to flip it to the next page. Not sure if this has anything to do with the XO skin protector I put on but don't recollect this problem started right after I installed the protector
Any of you guys seen this?
What version of ICS you have on your phone, custom rom etc..? Also GSM or Verizon?
I notice sometimes the screen goes off when talking on phone, and it doesn't come back on when I move it away from my face (like it's supposed to right?).
Also I just tested flipping pages in the browsing all apps/widgets, and I only have to slide my finger as little as a half inch, to flip pages. However if you do this slowly it will not flip pages, so it depends on the speed to slide and let go of the screen. This is also true for the launcher, flipping screens. So not sure why this would be happening to you?? I also have a screen protector as well (cheap dry application one $1.99 from ebay)
Try turning off the screen next time if happens and then back on and see if it goes back to normal behavior...? Does the phone accurately follow your finger completely? If not it might be some hardware issue with the touchscreen. If it doesn't then I would definitely remove your screen protector and test for the issue.
is there an app i can use to test if the screen is following my finger properly?
verizon and using stock os (rooted it of course)
sam008 said:
is there an app i can use to test if the screen is following my finger properly?
Click to expand...
Click to collapse
It's built in, just go to settings, developer options, show touches (check this)
It will show a small circle following where your finger is touching.
Also there is an even better setting above that called "show pointer location" Which will draw a line showing where you have been touching the screen.
Working fine
sam008 said:
Working fine
Click to expand...
Click to collapse
Strange, is this something new to ICS 4.0.3? Can anyone else confirm? I've only used 4.0.2 and 4.0.1.
If its following your finger accurately the only thing that would make sense to me is the ROM or kernel/drivers...??
i'm on 4.0.2 with verizon - there aren't any other updates available when i check
sam008 said:
i'm on 4.0.2 with verizon - there aren't any other updates available when i check
Click to expand...
Click to collapse
Ah for some reason I thought 4.0.3 was already pushed out to Verizon Galaxy Nexus phones, turns out that is not the case... ignore what I said earlier about it being associated with 4.0.2 I guess..
If you really want to get this fixed one suggestion would be to back up your phone (nandroid and/or titanium backup), and do a factory reset... if the page flipping issue goes away then you can at least isolate it the issue a little better...
I'm curious to see exactly the extent of the page/screen flipping issue you have, if you have the means, and have some time to blow, make a youtube video of the issue in action and maybe it will be a little clearer to see whats happening...
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
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
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.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
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.
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.
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.
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.
kristovaher said:
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.
Click to expand...
Click to collapse
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.
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
gokpog said:
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.
Click to expand...
Click to collapse
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.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
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...
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
Sent from my Galaxy Nexus using XDA
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.
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.
kristovaher said:
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.
Click to expand...
Click to collapse
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
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.
TechNoir said:
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.
Click to expand...
Click to collapse
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.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
OK, so i have been noticing lately that my photospheres have not been turning out that great. I usually see (if i go slow enough) that the little blue target dots move around slowly on their own. so i did an experiment. I placed my phone in my desktop dock sitting vertical at about 10 degrees from completely vertical.
opened up photosphere and the "horizon" blue dot was above where i needed it to be....but slowly the dot started moving down and eventually got to the target and took the first pic...then view kept going town until the transparent circle thing got to the bottom of the first pic...then it just want in a 180 degree circle at that height. there is no way this is normal, and i believe it is causing some issues with my photospheres coming out....not quite right.
so my question is:
is this normal? (i seriously doubt it is)
and how can i fix this?
i have noticed it on the last few ROMs i have tried (CM,AOKP,Mmuzzy ect)
so it is hardware not software IMO.
My gyro is wonky from time to time. Sometimes a good shake up or light tapping seems to get it in line. That said, I get the gyro wandering quite often as well.
Damn. So this is a known issue? It seems it is much worse in portrait mode but almost completely gone in landscape mode for me... Weird
Sent from my Galaxy Nexus using Tapatalk 2
Hello,
Today me and a friend of mine noticed something really weird on the Nexus 5X. If you have the factory default wallpaper enabled (the one that appears on the box of the phone) and try to access the camera while the screen is locked the top of the screen starts to clutter.
In order to observe this you have to have:
1) The wallpaper set to the factory default one.
2) The phone locked.
Then you have to start dragging the camera icon at the lower right corner of the screen slowly without releasing. At some you will notice that a small portion at the top of the screen starts to clutter and display weird colors. At first I thought that this a hardware related issue (faulty screen) but I have verified that the same thing happen on other devices as well. Setting the wallpaper to any other, other than the default one seems to not cause this.
Both phones I tested this on where running Android 6.0.1 and had all the latest updates installed. I know this is something really minor and mostly unnoticeable but it would be really nice to know what could cause this.
I would never have noticed this if it weren't for this thread. It seemed to only happen with the default wallpaper as stated by the OP. Most people would never notice this because they customize the wallpaper and probably never use the camera shortcut on the lock screen.
Sent from my Nexus 5X using Tapatalk