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!
Hi guys I'm a new registered user, but an old follower. I'm here for a strange problem of my GN. In practice, when I open settings, play store, the browser, a strange thing happens: in pictures of gray, blue, white colours, appears in the background a picture of a conversation WhatsApp with the keyboard open (I came to this conclusion after 34503430 observations and it I'm 100% sure it is an old screenshoot, among other things deleted from WhatsApp). So i have done full wipes and also a super wipe and installed other roms but the problem persists. An other strange thing is that when i do a screenshoot the problem in the .png image doesn't appear. So i have taken some pictures with my S3 for showing you the problem. I don't think that could be an hardware issue, because the phone is very fast and smooth, the resolution and the colours are very amazing and all works perfectly. For me there is a partition of this file in the system files. So what could i do?
Thank you for reading and for your time, i've search but no info about that, thank you.
[img=http://imageshack.us/a/img824/8954/whatsappprioblem3.th.jpg]
[img=http://imageshack.us/a/img405/6914/whatsappproblem2.th.jpg]
[img=http://imageshack.us/a/img22/4407/whatsappproblem1.th.jpg]
I'm triing to restart my phone from the original version and then i'll reinstall all. But if it will not work what could i do?
That's called a screen burn-in.
Do not use your phone all the time at maximum brightness. To fix this issue, try to put your phone for like 20seconds on a 100% white image covering the entire screen (including the navigation bar). It helped to remove my screen burn-in's
Although I never had the problem that my KEYBOARD O___O got burned in but I had it with the navigation bar but I fixed it very easily with someone's app (don't remember it's name but a user on XDA on the Galaxy Nexus forum posted it to fix the screen issue)
tuk1maar said:
That's called a screen burn-in.
Do not use your phone all the time at maximum brightness. To fix this issue, try to put your phone for like 20seconds on a 100% white image covering the entire screen (including the navigation bar). It helped to remove my screen burn-in's
Although I never had the problem that my KEYBOARD O___O got burned in but I had it with the navigation bar but I fixed it very easily with someone's app (don't remember it's name but a user on XDA on the Galaxy Nexus forum posted it to fix the screen issue)
Click to expand...
Click to collapse
initially thank you for reply. So i'm reinstalling all the system now. The problem is not solved. Now i try your method. I must only set a 100 white image for 20 minutes at 100% of luminosity at full screen? i hope to resolve, many thanks for now.
I'm using tools for remove this problem, so what's the best for you?
Hey all.
I've been testing for a few weeks now, on both my recalled note 7 and my replacement and wondered whether anyone encounters the following issues. Think it could be software related bug or sorts. Definitely not hardware.
Sometimes the quick settings toggles can become unresponsive ( will work after a few presses) including the settings cog. I found this to happen mostly if the screen res is changed to QHD and the font set to small. With medium size font all works great.
Although, IF I reboot after I make any display changes, everything will work fine. I've found messing with the font settings and resolution can make the bug appear. I could pull the drop down and press the settings cog, it may or may not respond after the first press.
Now. If I set the screen res to just FULL HD with any size font, big or small every icon/setting/toggle WILL respond immediately, whether I reboot after making the changes or not.
Don't get me wrong, my phone runs GREAT (Touch wood). Just wondering whether anyone else experiences or takes notice of these things?
no, nothing simmilar here, althoug I dont like to play with resolutions, as they scrammble things around
I'm having the same problem though I must add I haven't been fiddling with the resolution or display settings. It is always at QHD.
kEvinErd said:
I'm having the same problem though I must add I haven't been fiddling with the resolution or display settings. It is always at QHD.
Click to expand...
Click to collapse
I've still been testing it, it defo seems to be a random software bug. The Layout boundries option in developer settings also shows how tight the lines are around some icons.
The glass and temperature may play a part in touch sensitivity also. I've cleared cache from recovery and seems to have temporarily solved the issue. Can be fixed I reckon by re-introduced the increase sensitivity option for gloves etc...
I have had this a couple of times. Never changed the resloution.
Same. Also in addition of this, my replacement runs warm idling and quite hot while loading. The whole system seems quite snappy but sluggish. My hope for Samsung is gradually vaporizing...
I have a HTC One m8 and the top half inch of the screen does not respond but occasionally it does sometimes for a little while. The top half inch generally tends to work when the battery is charged to 100% but sometimes that doesn't happen either. if it helps I use a tempered glass as a screen protector and the screen does not have any physical damage and it doesn't help when u boot into safe mode. I have also tried a hard reset.
Coincidentally i am working on a phone with the same problem (not mine). After a lot google research the owner decided to use another Launcher (Smart Launcher). This did not fix it entirely, if you are in Apps you can use the statusbar, but its not working on homescreen. I dont know why it behaves like that, but surprisingly many people get problems like that. I tend to believe that there is some software problem involved, because changing Launcher or using custom rom has been reported helpfull/fixing the problem (not allways tho..).
Now he had some other troubles with this phone and in the process i did a reset, that did not fix things as you said. I will install a custom rom next and will report back next week.
So i was wrong with saying a new lauchner solved the problem. Statusbar(sb) was accessible in home screen but not in app, said it wrong in the other comment. Now i had some time to test this and i can say that at least the phone i was working on is broken.
The top part does not recognize any touch input. The reason the sb showed some reactions is, that the launcher had a bigger trigger area (i guess), so you could pull it down. But still the top part was not responding. I tested it with stock, S-Rom and one Nougat Rom (dont remember), none of that showed an input in the top part.
Solution for now is different launcher or app that pulls down the bar. There are still some problems in daily usage, that this will not fix, so i guess its time for a new phone.
I am facing same problem. Is it any update which was pushed by HTC which makes the top 1 inch unresponsive ocassionally.. Indirectly, a marketing gimmick to push us by a new phone. So if it is really like that, who would buy a HTC phone again anticipating same problem again. Might go for Samsung (my own preference). huh !!!