My screen has an occasional issue where a bar forms all the way across. In this bar it looks like static, mixed with glitch art. When i lock my screen it usually makes the bar vanish.
It's been about a year since it started. It was never a huge concern since I bought the device while we were still porting Android to it initially.
I assumed the gpu was just dying. Now that it's been so long, I'm thinking it may be something else.
It's happened with the past 3-4 ROMs.
Related
Does upgrading the HBOOT help with the wonky touchscreen heat-related miscalibration issues that every Nexus owner knows about?
I raised this question on a different thread:
http://forum.xda-developers.com/showthread.php?t=903975&page=9
but wanted to throw this question out to a larger audience.
This week I finally got tired of having intermittent but definitive touchscreen miscalibrations, usually associated with charging and/or heavy usage. HTC shipped a swap for me to use.
The new one works pretty well, except the camera takes pinkish tinged images, so it unfortunately will be going back. However, I noticed that the HBOOT is the newer 0.35.0017 (though the date displayed by the bootloader screen is Jun 14, 2010).
So I upgraded the HBOOT on my original N1, and have been trying hard to reproduce the touchscreen craziness. So far I've been unable to do it.
It's difficult for me to make it happen on demand. I "stress tested" it essentially by doing the things that normally bring it on, GPS with charger, and graphics intensive games. But I'm getting really tired of beating angry birds again and again =P
So, if you're still experiencing touchscreen wonkiness that is fixed by turning on and off the screen, which HBOOT do you have?
There are of course many other potential mitigating factors I've thought about. Custom ROMS. Kernels. Touchscreen protector. Radio version.
Just for completeness, there are different part numbers on the two:
Original N1 part # 99hke002-00 F
Replacement N1 part # 99hke002-01
Who knows what the significance of that is.
No it doesn't.
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
You know, as strange as it sounds, since I upgraded to the 0.35 HBOOT about a month ago, I have had zero issue with the digitizer. Call it coincidence, but that is what's happening so far.
We will call it coincidence for now =)
A happy coincidence.
waylo said:
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
Click to expand...
Click to collapse
Not very often, in fact think it hadn't done it over the past week. I've been using the crap out of it customizing CM7 over this weekend and no hiccups.
our touch screen is always a hardware problem..
That's not the question. The question is if you're still having a lot of problems with your touch screen, which hboot do you have?
I was actually kinda wondering the same thing. I finally got around to putting on CM7 (build 39) on Friday (coming from CM 6.1). I right away had the impression that the screen was more responsive (the notification drop-down bar tipped me off) and I have not had a single episode of wonkiness with the screen since. CM 6.1 was a little weird for me and I had screen issues (especially the drop-down).
Oh well, even if it isn't the HBOOT, something has changed for the better for now
Another thing I learned recently is that on the native google navigation app, there seems to be a touchscreen dead zone directly vertical in the center of the screen (in landscape mode at least). It basically corresponds to the current street you're on if your navigation is active and your path is straight ahead.
So if you touch there and try to shift the screen around, you might mistakenly think the whole screen is awry. I think this is by design.
I'm not sure why it's there but it reliably is unresponsive to drags. So I'm not using that center area to gauge if my screens gone wonky.
Now if you hit the menu button, the buttons centrally do respond to taps.
Just had my first case of misregistering digitizer in a while. But instead of the whole bottom 1/3 of the screen going stupid it was just the bottom right corner, around the enter button/backspace if you have a portrait keyboard.
Oh well, it still works better than stock eclair!
So just as an update, the HBOOT definitely does not rid the digitizer issues plaguing everyone. It seems actually that my kernel had more of say in when/how often the issue surfaces.
I found that on Enom's Froyo ROM, problems arose more often with stock Enom than Pershoot or Wildmonks. However, each kernel has its own benefits.
I've noticed the last few days that my nc has a hard time unlocking. I start to swipe my finger across the unlock and it moves about 1/10 of the screen then shoots back. If I do it a few times, I might get lucky and unlock it.
Does this sound like the digitizer is going out? It's one of the first production models (wife bought it for me for christmas right after they came into the store). So I don't know if there was an issue with them at all or not.
Everywhere else on the screen seems to be fine, but it doesn't do me much good if I can't open the thing to read the books inside.
*edit
Just did a test on the bottom row of books, and they seem to be working fine in that general area. Is anyone else seeing this only when trying to unlock the nc from sleep/off?
Do you have it plugged in?
Yeah it seems to happen on my girlfriends NC, at least when it was running 1.1 Stock, not sure I've noticed it since 1.2. It's not a bad digitizer assuming you have the same issue which was right after resuming from sleep it will SOMETIMES be a little pokey for the first 20 seconds or so but after that it slides smooth as butter. It never really bothered me since I just assumed it was reloading some software into memory. The only other common issues I know of are issues when plugged in as mentioned above and the seemingly obvious but often overlooked dirty screen.
I do notice in general that both NC's I use are a little less than perfect when touching the far corners (I often need to jab while making grunting sounds) but I figure it's an e-reader so they probably didn't spend a fortune on the capacitive part of the screen. If you are so inclined, loading up CM7 disables the lock screen by default and there might be a way to do it in stock as well although I suspect you will still occasionally need to give it it's 20 seconds to get things running again.
I've started to have touch screen issues the past few days.
Any idea what may cause it?
Sometimes, when I touch the screen, say in settings, I touch one item, but a different item is selected somewhere randomly on the screen.
Happens in TWRP as well. If I select options to wipe, it will select others, and then it doesn't swipe over to execute the action.
No ideas? What would make touches appear where I don't touch, even on TWRP?
I tried the keyboard calibration on HTC's keyboard.
Any ideas? Screen protector?
It comes and goes.
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
mcwups1 said:
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
Click to expand...
Click to collapse
I opened another thread about a similar issue I'm having after Lollipop. My gesture launch randomly stops working and I have to reboot. No other issues for me though. I have an anti-glare screen protector on mine, but had no issues before the update. I've thought about a factory reset to see if that would cure what ails.
I'm on tmo but have the same exact issues. This is what i've found so far...
I turned on the developer options and turned on show pointer. This will show you where the touches are landing.
If you scroll down slowly, you can see most of the touches are in line (up and down) and not random on the screen.
I've removed all programs that have screen overlays (screen filter, twilight etc)
I've removed the cases thinking they might be causing the issue, but removing them only slightly improved the issue I thought...
Sometimes its hard to reproduce the effect, its not consistent. So this leads me to believe that it could be a process that's running in the background that calls attention at the moment you're touching the screen, and then refocuses the screen to your point of contact. And in between it thinks you're moving your finger when you really aren't.
In any event, I can't find the exact cause of this. But, it definitely started after the update to lollipop. I had none of these issues before. I even got the phone exchanged because I believed the digitizer went bad or something. But this issue exists on my original phone, its replacement, and now on my wife's current phone and that phones replacement (across 4 phones).
I'm currently working on my wife's replacement (4 or 5 non-oem programs installed) and continue to have the problem. But it is not consistent as I can't readily reproduce it.
What i've done to try and learn more is when I see the screen pointer light up in random places, I keep pressure on the screen so I can observe where the screen is registering contact. It almost looks as if it's trying to pull down the shade. Whether it be because of the dual points of contact and it thinks we're swiping down, or because of another program that is stealing focus for whatever reason.
If anyone else has insights into this, please let us know as this is more than frustrating! I keep calling people in hanouts with a lot of people and they aren't happy about it lol.
Also for reference, we're using ADW ex launcher instead of Stock HTC Sense. But even when I remove ADW (uninstall) and run sense, it continues to happen. So it's not that.
Hi! Sadly as many of Z3C users after 2 years of great usage, my touchscreen stopped responding in navigation bar area. I still used my phone using Pie style navigation buttons. Sadly, today a unresponsive vertical stripe showed up, so i guess my touchscreen is slowly dying. My question is - has anyone had some experience with replacing screen? I read few posts from people that replaced their screen, that after few months the problem showed up again. I'm wondering if it is a common thing, and replacing the screen is unprofitable. Replacement would cost about 1/3 price of new phone, and also i really like z3c. I would love to hear your experience if you have any!
Think mine has done the same after 3 years of usage. I have an unresponsive vertical strip on the far right side of the screen, didnt drop it or get it wet or anything. Very annoying
Would also be interested to hear if anyone got the screen replaced. Really enjoyed using this phone, its been through the wars and this is the first problem Ive had with it.
Same problem here, about 3 weeks ago I couldn't pull down the status bar anymore except on the home screen.
Since this morning, my navbar stoped working, after nearly 3 years of using.
I think its a litte odd that it suddenly stopped working in this particular, critical area (nav bar, status bar).
Hi! Same problem here with navigation bar. I don't know what to think about sony anymore. I have been using since xperia active - xperia go - z3 compact.
I can not remember what was wrong with the active, with the x-go the power button broke and now this... I guess is a matter of time for the vertical issues.I also still have this very old LG p500... still working, not like a charm but does the job. I am a little bit sad, all this time fighting against the desire to unlock the bootloader and now this. Is time for LineageOS or CarbonROM and save some money too for a new... sony? I don´t know
same problem
Same problem here after device just a tad older than warranty period. Giving up on Sony devices and their attitude to customers.
Just retired my 2 XL and got a like-new 4 XL. Loving it so far, except one nagging issue.
Randomly the top 30-50% of the display stops registering taps (touch). It's easy to fix by turning the display off then back on, but I'm concerned it may be a hardware issue.
Interestingly, when this happens and something that is full screen and scrollable such as a contact list or app drawer is in the foreground, I can drag from below the "no touch area" to the top of the screen, but I can't start a drag at the top. So, it can sense touch in the troubled half, it just won't register taps.
I have done tons of searches. I see lots of people saying Android 12 had touch issues out of the gate, but was supposedly fixed. I disabled the block_untrusted_touches. I have checked any app that has draw over other apps permissions. I have tried with high touch sensitivity on and off. I have paid attention to running apps when it happens. I installed a LogCat reader looking for touch related issues when the problem occurs. I tried safe mode, but due to the intermittent nature of the problem, and the fact that safe mode disables most functionality, it really wasn't a good long term test.
I have yet to pinpoint this.
Sometimes it doesn't happen for a day, other times it's multiple times per day. So trial and error takes time because just when you think you licked the problem, it rears it's ugly head again.
I'm running LineageOS 19.1 at the moment (which I had also run on my 2XL with no issues). It is rooted. No apps force closing or crashing.
Has anyone else seen this on the 4XL?
Definitely interesting, never heard of that. I had some touch issues, specially if the display gets wet where it register touch, but poorly to the point I need to restart the device and dry out the screen. Though in my case the creen is completely cracked, so I suspect that's the cause as it didn't happened before.
Though I had a similar to yours but with the battery.
The problem was that the phone would randomly shut down, and that would happen more often when it was on my pocket.
This made the phone very un stable as sometimes I would have the phone completely off and didn't even know about it.
So I decided to open it and have a look at it. It turn out that the problem was the flex cable that connected the battery with the logic board, it was just slightly tore on one side, but just a tiny I couldn't nearly see it, I had to use another phone to zoom in.
As it was torn, depending on the way the phone was changed the force the gravity made over the cable, causing that sometimes it not enough energy got the phone, causing it to shut down.
Once I replaced it, it never happened again, not a single time.
Maybe you have a similar problem, though as you are rooted and using a custom ROM, that may be the reason, my case was extremely rare.
anyway, good luck