Develop Bugs

Display becoming possessed and unresponsive

Wonder if any of you have had similar issues or know a fix.
Symptoms:
After using the phone for a long time, typically over an hour or do, the onscreen keyboard starts to behave erratically by generating 2 letters if I type one. Then, swyping doesn't give the desired result. If I zoom in and out in internet, it just starts scrolling to one side. Then the whole screen starts fluctuating. In fact the phone seems to have a mind of its own
Video of the issue: :
http://db.tt/W3XkD0z
Troubleshooting steps tried:
I swapped my sim cards and sdcards to rule out their issues. Unrooted with ruu. Problem persisted.
Htc replaced the touch panel, put in an amoled instead of the slcd I had. They also replaced the main board. The problem didn't go away.
Wonder what could be the cause. If nothing works, I'll force them to replace the handset as a whole, but really like the amoled they've provided..

I had some of the same problems with my Desire under US Cellular. I noticed it the first day I purchased my phone.
The keyboard would just become unresponsive and it was like the keyboard was behind about 10 characters as I was typing (and I was a slow typer with a new phone and first full touch screen). It would also add random letters that I know in fact were not pressed.
Scrolling didn't give me as much trouble as you are going through, but still seemed very buggy.
The entire phone would seem to slow down as hours past and it remained on. I tried a hard reset, and even like you, removed the SD Card and nothing.
Took it back to US Cellular, showed the guy what was going on and showed him after a reboot how it would clear up... and they exchanged, no questions asked. I think it was just a corrupted phone. The new phone runs very smoothly.
By the way, the DB link you provided gives a 404 error. I would like to see it to compare with how bad it was for me.

Try this link
http://db.tt/SwYPaIf
Sent from my HTC Desire using XDA Premium App

hardware problem?

hi, had my desire z about a year now, since ive had it, quite rarely ive had a problem of it seeming to have a mind of its own, for example, icons may be selected, or the home screen will slide accross by itself etc. ive always put this down to a trackpad problem.
the other day (after having a miui rom installed for about 2-3 weeks, which was fine untill now), it started acting up strangely, the above problem started happening, but more severe, also the touch screen and softkey buttons would stop working for periods of time (or stop completely untill reset), but screen rotation etc would still be working, which shows that the O/S has not frose and is still working behind the scenes (making me think its a hardware problem).
now, i think ive worked out that this seems to be triggered (mostly) when i open the keyboard. (as also, when the touchscreen stops working etc, sometimes, sliding the keyboard open and close several times, will sometimes seem to unfreeze the touchscreen etc, and will be back to normal, for a while). ive tried doing full wipe and reflashing etc, but i still have the same problems mainly when using the slide out keyboard, which again, makes me think its hardware (possibly keyboard ribbon cable?)
i really dont want to send it off as that means getting it all back to stock etc, and last time i needed the screen replaced, took 6 weeks to get it back!
if anyone could pinpoint the likely source of the problem, id rather replace the part myself..
would anyone have any ideas, as they would be very much appriciated... Thanks...

anyone at all?

I got 2 Zs meanwhile but dont have any problem with the keyboard.
But sometimes when its charging i got the same issues like you - no touch is working and the screens are sliding nearly automatically.
I think this has nothing to do with the keyboard...
Hope this had helped you a bit
Sent from my HTC Vision using XDA Premium App

thanks for the reply, unfortunately im still no closer to finding source of the problem, its intermittant, happened lots yesterday, not so much today, maybe the digitiser? its like there is another invisible finger touching the screen..

This would happen when i was on stock froyo, like it would cause the home screen to hang, but if i was ion an app it worked fine. I would use it to refresh of sorts when my phone was hung up or i need to reload my apps from sd lol. Sounds weird I know, but even with stock froyo i had problems with my keyboard but with the prerooted GB its as smooth as butter...

still going on, and getting more frequent, i dont think it is to do with the keyboard anymore. im now guessing it is the digitizer, its like someone is pressing an invisible finger on the screen, roughly in the center. it comes and goes, it happens for about 3 days, then goes away for a couple of days etc.
also there is very little info anywhere on the net that can help, including replaceing the digitizer itself
anyone ever replaced one on a disire z/g2?

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

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!

Ghost touches in upper third of screen

Hi.
My Z1C seems to have a similar case of faulty display as described in some other threads here, but actually a bit different. The phone is stock, not rooted, running 5.1.1
Whenever I do something, there are ghost touches in the upper quarter or third of the screen. They only happen when I am not touching the screen myself. It happens no matter what I do. When I browse internet, it clicks links, when I scroll contacts, it calls people, when I am on facebook it gives likes etc... It seems like the more demanding task the phone is performing, the more ghost touches.
I turned on the developer settings and the "show pointer location" option, which leaves track of the last touch on screen, so I can research the issue.
I found out that when the phone is on home screen, it happens very rarely or not at all - the track of my last touch stays until screen turns off.
When I jump into the touchscreen service test, it does not happen at all. I can draw a line around the whole screen and it stays higlighted indefinitely.
In lock screen, it also doesn't happen.
I tried it in Sketch and it confirmed what I thought, when I was just sketching, from time to time a dot appeared in the upper part of the screen, but when the phone was downloading or installing in the background, the screen literally had seizures. I touched and released and then a storm of dots started to appear around the top part of the screen. It stopped after 5+ seconds, and after another input from me, the screen got another fit, drawing more dots.
I don't have any experience, but I think that since the problem doesn't happen constantly and it doesn't even happen at all in test mode, it could be a SW mistake.
I have found this thread https://forum.xda-developers.com/showthread.php?t=2691849 and I'm willing to try, but 1) my phone is still under warranty and 2) I have never done a root so I am not too eager. Do you think I should try that? Or has anyone found another solution for this problem?
Thanks.

Slivovidze said:
Hi.
My Z1C seems to have a similar case of faulty display as described in some other threads here, but actually a bit different. The phone is stock, not rooted, running 5.1.1
Whenever I do something, there are ghost touches in the upper quarter or third of the screen. They only happen when I am not touching the screen myself. It happens no matter what I do. When I browse internet, it clicks links, when I scroll contacts, it calls people, when I am on facebook it gives likes etc... It seems like the more demanding task the phone is performing, the more ghost touches.
I turned on the developer settings and the "show pointer location" option, which leaves track of the last touch on screen, so I can research the issue.
I found out that when the phone is on home screen, it happens very rarely or not at all - the track of my last touch stays until screen turns off.
When I jump into the touchscreen service test, it does not happen at all. I can draw a line around the whole screen and it stays higlighted indefinitely.
In lock screen, it also doesn't happen.
I tried it in Sketch and it confirmed what I thought, when I was just sketching, from time to time a dot appeared in the upper part of the screen, but when the phone was downloading or installing in the background, the screen literally had seizures. I touched and released and then a storm of dots started to appear around the top part of the screen. It stopped after 5+ seconds, and after another input from me, the screen got another fit, drawing more dots.
I don't have any experience, but I think that since the problem doesn't happen constantly and it doesn't even happen at all in test mode, it could be a SW mistake.
I have found this thread https://forum.xda-developers.com/showthread.php?t=2691849 and I'm willing to try, but 1) my phone is still under warranty and 2) I have never done a root so I am not too eager. Do you think I should try that? Or has anyone found another solution for this problem?
Thanks.
Click to expand...
Click to collapse
As You have warranty, I would strongly suggest that You go for a repair. I had the same issue in beginning, ghost touches appearing randomly, going away only after reboot. I was rooted and xposed, so went full stock without restoring any apps or data from internal storage, yet the problem remained, thus ruling out the point that it was software problem. And then after a week or so, that much part of screen stopped responding to touch entirely. You can see details over here, Another user had same problem as Mine and had the same end result,

OK then, I'll go for a repair. Thanks for the tip.

Slivovidze said:
OK then, I'll go for a repair. Thanks for the tip.
Click to expand...
Click to collapse
I am having exactly the same behaviour as you described .
Ghost touches happening on the upper part, and triggered when a demanding task is running.
Actually I didn't realized completely about this, I thought it was just random, but right now after I saw your post, I tried an app similar to Sketch while upgrading apps or playing a video in the background. And dots in the upper part start appearing crazily.
Did the phone repair solve your problem ? Mine is not in warranty, so I'll have to pay for it.
But also in my case, before this thing happened, I got some water damage and that upper quarter of the screen stopped responding.
After replacing screen+digitizer I got this very specific behaviour you described.

karamaz0v said:
I am having exactly the same behaviour as you described .
Ghost touches happening on the upper part, and triggered when a demanding task is running.
Actually I didn't realized completely about this, I thought it was just random, but right now after I saw your post, I tried an app similar to Sketch while upgrading apps or playing a video in the background. And dots in the upper part start appearing crazily.
Did the phone repair solve your problem ? Mine is not in warranty, so I'll have to pay for it.
But also in my case, before this thing happened, I got some water damage and that upper quarter of the screen stopped responding.
After replacing screen+digitizer I got this very specific behaviour you described.
Click to expand...
Click to collapse
In my case, I realized that I bought (probably) a badly re-fitted phone. Display's backlight was visible around screen panel edges, where I'd say it shouldn't be visible at all. I decided to return the phone and got a refund.
Sorry for not being able to help you.

Slivovidze said:
In my case, I realized that I bought (probably) a badly re-fitted phone. Display's backlight was visible around screen panel edges, where I'd say it shouldn't be visible at all. I decided to return the phone and got a refund.
Sorry for not being able to help you.
Click to expand...
Click to collapse
Ok. The aftermarket screen I got has that issue with the screen edges also. Very probable you are right.
In my case I water damaged myself. It seems that after 2 years of intensive use, waterproofing is gone, by accumulation of slight hits or so, never had a single crack on the screen. I read many posts reporting this happening, even with much less use time.
Too bad, I loved the phone, but I'm afraid that sending it to repair will mean to change the PCB or similar for a complete fix, which can come to a ridiculous price.
Seems it will be time to move on...

Yeah. If you want it fixed properly, you'd need to send it to Sony, and for the money it would cost you, you can probably gen a new phone. Sadly, similar phones aren't made anymore.

screen stutter, complete loss of touch.

Been using the phone for the last 12 hours and I noticed something towards the end of my use last night.
The screen seemed to become unresponsive. And when it would work it would start to make its own input when scrolling and opening any app or link my finger would drag over while scrolling.
Changed refresh rates, changed resolutions, even seen if the blue light filter was the issue. Nothing.
Almost seems like the screen drops frames when scrolling, like it gets caught on something.

New development. Fingerprint sensor doesn't respond at all and inputting a pattern is damn near impossible. Going to try removing the screen protector to see if that could also be the issue

Did a factory reset
Issue seems to be where the finger print scanner is
It's almost like a dead or unresponsive zone.

Sounds like a factory defect, better have it replaced if resetting didn't worked.

Small video showing when scrolling over the fingerprint reader, the screen almost loses input

Defect.

Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out

imtjnotu said:
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
Click to expand...
Click to collapse
Sounds like Samsung support LOL...sorry you're having issues

Did you remove the factory installed screen protector? Maybe it's the cause of the issue

Return that pal, that doesn't sound good at all.

lovers74 said:
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Click to expand...
Click to collapse
one of the first things i did to trouble shoot. still having the issue. sometimes the screen completely loses all touch registration and it doesnt even know im trying to swipe or push on things. just realized it did this also after tmobiles new software update.
im still waiting here to hear back from samsung on how they are going to fix this issue

The same thing happens to me. Pulling down the notification shade seems to be the only thing that still works. It seems to goose the phone and it starts working again.

Test using the *#0*# diagnostic menu and use the Touch test.