Related
Hi
I upgraded to my new DHD less than 3 weeks ago. It is not rooted and I did the recent OTA update over Christmas.
Over the last couple of days I have started to experience difficulty unlocking the device on the slide-to-unlock screen. The problem seems intermittent - somethimes it will unlock fine, and other times the slider just seems to "get stuck" at the bottom of the screen.
At first I thought this a bug or something, but after some investigation I am concerned there is a problem with the digitiser. I opened a picture and zoomed in to fill the screen and tested the touchscreen in different places by sliding the picture around. What I found was that the bottom 1cm of the screen above the keys does not respond properly to Up and Down swipes. It is fine however with side-to-side and also individual taps. This is obviously a problem when trying to move the unlock slider!
I've had a screen protector on for about a week - I don't imagine this has caused the issue but haven't removed it to test as yet as I don't have a spare. Aside from this, the device has been very well looked after, definitely no bumps etc and kept in an HTC leather pouch.
Any ideas? Should I return it to CW?
Thanks
OK, I seem to have resolved this for the time being but expect the problem to return.
I downloaded a screen test app that allows you to draw on the screen and got some very strange results. A 1cm band of screen about 1cm up from the bottom was completely unresponsive. Trying to draw a horizontal line within this band would result in lines being drawn either above or below it, or strange vertical lines "jumping" around. The rest of the screen was fine. I realised this is why I have been struggling to close the keyboard - the button is placed within this band and trying to press it would result in on of the buttons above or below being pressed. Also have had problems with the sapce bar.
I did a restart (not fast) and this has resolved the issue, however I expect it may return as I did a restart only yesterday.
At least it is obviously software and not the digitiser....
Hi again. As expected, the issue returned after a couple of hours. This time however, restarting is not making a difference.
I resorted to a hard rest, which has not changed anything either.
Any help/ideas would really be appreciated...
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
olivierlee said:
Best to return it for repairs or exchange. Seems like the digitiser is faulty.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I agree, this definitely sounds like a hardware problem.
Hello all! Ive just recently got my Xperia arc, and flashed a nightly build of CM7 on it, number 20. Everything seemed to run smoothly, but just now screen started to behave very weird, it almost seem to have osme kind of "ghostly" second touch.
The upper part of the screen is almost impossible to use, when I try select an app to move it on the screen, by holding finger down, it just flickers for a second and gets deselected. If I manage to select it and drag+hold, it starts spazing out all over the screen, with screens switching between eachother by it self.
The problem is especially noticeable in games, where you usually have a joystick controller in bottom left corner. When using it, I usually trigger the buttons above it in the upper left corner which I am no where near at with my finger.
Is this a ROM issue, or hardware issue? Ive been using the rom for couple of days with no strange to it, and now this happens. Any ideas what the source can be?
ROM failure.
Sorry for bump, but apparently the problem remained. I changed to XDA rom, which too is based on CM7 thou and after a day I stumbled upon same problem of ghotsly second touch on screen.
I cant hold to move apps, cant precisely press a button in game on left side of screen, it then triggers some other button nearby. I do get haptic feedback from long press on a homescreen, but the "add new" menu popups only every few tries Any ideas of what may be causing this? I would really like to avoid the hassle of resetting the phone and sending it back for repairs :/
try stock one or miui.
It sounds a bit like your screen had a bad encounter with water...
Could this be the case?
iR¡[email protected]!* via Tapatalk
iridaki said:
It sounds a bit like your screen had a bad encounter with water...
Could this be the case?
iR¡[email protected]!* via Tapatalk
Click to expand...
Click to collapse
No, this phone is only few days old.
I think I am noticing a pattern.. screen behaves this way only late evenings, till next morning. I never noticed the issue during the day, but then it was there again for no reason after I left phone for couple of hours (it's past midnight here at the moment). Now when I think back, same was previous two evening, issue only noticeable during late evenings. Could my phone be possessed lol?
It's quite weird issue too. Upper half of the screen seems to have a ghost touch as I said. When trying to add a widget to upper screen, I only get a haptic feedback from long press. When playing games, all buttons on left side (landscape mode) get activated as soon I press one of them. Most weird of all, is that screens works perfectly in app drawer and settings, but not in app/homescreen. I will test how it is again tomorrow and report. If it works just fine again as if nothing happened I will be really puzzled.
Currently on CM7 Xda version, same was for official version. I am considering updating to MIUI, just gotta figure this radio difference stuff, but am becoming sceptic to whether this issue really lies with ROM and not app/settings.
Yep, issue is gone like nothing happened at the morning, this is is haunted ._.
I've figured the cause, it only happens when the phone is plugged in and charging. Beats me why thou, what remains to see now is if it is tied to the kernel or not. Posting it here in case others with similar problem stumble upon the thread.
Are you using the stock charger, i used to face bit similar problem when i used to connect my old HTC USB charger... later i discover the HTC charger was giving only 500mA , where as sony one is rated at 700mA.
mangemayur said:
Are you using the stock charger, i used to face bit similar problem when i used to connect my old HTC USB charger... later i discover the HTC charger was giving only 500mA , where as sony one is rated at 700mA.
Click to expand...
Click to collapse
Thanks for the tip! Turns out it didn't like my 1000mA charger I am using for all my usb stuff, but the stock on works perfect (it's 850mA).
Hey guys,
today i spoke to amazon germany about the one X, because i had already 3 faulty devices and all devices had the same issue, screen flicker.
The amazon worker said, they tested all devices and every device was faulty, now they are waiting for a statment from HTC. I think its very sad especially for the people who waited for their device, HTC shame on you -.-
picxar said:
Hey guys,
today i spoke to amazon germany about the one X, because i had already 3 faulty devices and all devices had the same issue, screen flicker.
The amazon worker said, they tested all devices and every device was faulty, now they are waiting for a statment from HTC. I think its very sad especially for the people who waited for the device, HTC shame on you -.-
Click to expand...
Click to collapse
This is very well known issue http://forum.xda-developers.com/showthread.php?t=1617009
Sent from my HTC One X using xda premium
Just a bad batch.
Over here in Ireland, very few if any people have had to return faulty devices.
yeah but not in this dimension, i thought a bunch of devices were faulty but not that much, what do you think hardware or software?
The store were I swapped mine 3 times also said there is no "sense" in swapping for a 4th as they are all flawed.
when they cant fix the issue through an ota, then its gonna be expensive for HTC
picxar said:
when they cant fix the issue through an ota, then its gonna be expensive for HTC
Click to expand...
Click to collapse
They may be able to fix it through an OTA. A lot of early ICS ROMs for the Rezound had screen flickering problems, but they've since been worked out. At least there's hope!
Sent from my ADR6425LVW using XDA
If only the level of attention AntennaGate got becomes as widespread for HTCs woes...then we might all get a free case - oh wait that won't fix the Wifi issues, or the flickering...or the yellow spots...
And the transformer prime had the.same.issue, it took 4 ota to fix it. I think I have seen people say it is possibly tegra related
Sent from my HTC One X using xda premium
picxar said:
Hey guys,
today i spoke to amazon germany about the one X, because i had already 3 faulty devices and all devices had the same issue, screen flicker.
The amazon worker said, they tested all devices and every device was faulty, now they are waiting for a statment from HTC. I think its very sad especially for the people who waited for their device, HTC shame on you -.-
Click to expand...
Click to collapse
While the problem is very real, I highly doubt that Amazon ripped open lots of boxes and started testing the phones. There are seals on the tape on the side of the box and they wouldn't have been able to resell the device after opening it I think they probably re-tested the faulty ones returned and judged by the number of returns that there was a general fault. By the way, it is easy to determine if your phone is a new never used one or not. When you switch the phone on, if it takes ages to start, going black for a while, it is new. If someone had switched it on, even if they didn't do anything, and switched it back off again, it would not take long to turn on the next time, due to fast boot. Since the fast boot setting is always on after a factory reset, I believe it is impossible to get the phone back into a state of "reset + long boot".
Also, having now been on my 6th phone, every single one of them had flicker. They were not all built at the same time or bought from the same store. I found a test case that could make any of them flicker
1) Battery below 50%
2) Brightness set to 40%-50% (varies a bit from phone to phone)
3) Go to the XDA forum web page on the phone. As the page is loading up, focus on the background and will see flickering as the CPU activity increases during rendering
I think there are two types of flicker. One that happens all the time on some phones most visible on grey backgrounds. And another type of flicker that happens at certain brightness/battery/cpu levels.
Another test case is:-
1) Set brightness very low, such as 20%
2) Go to app/play store
3) Choose "My Apps"
4) This may only work with a considerable number of apps..I tried it with 60. Rotate to landscape, watch very carefully the grey background...and then when the white re-appears, watch the brightness change upwards after it settles.
5) Rotate to portrait and watch again at the grey, then the white brightness levels
A friend bought a HOX just recently and it shows as well on these 2 test cases.
I bought my HOX from an italian ebay seller (a month ago: htc23) and device has arrived with an Amazon Spain package.
Never had any issue: no screen flicker, no flex ..no gap
When you have to set it up just to see it flicker that shows it's NOT an issue in my eyes - 'battery less than 50%, turn brightness to this level, etc.'
I have my phone on auto brightness, let the battery run to nothing sometimes and I have NEVER had the screen flicker. I'm saying there might not be a problem but when you get it under very precise circumstances I think you're deliberately looking for a problem...
EddyOS said:
When you have to set it up just to see it flicker that shows it's NOT an issue in my eyes - 'battery less than 50%, turn brightness to this level, etc.'
I have my phone on auto brightness, let the battery run to nothing sometimes and I have NEVER had the screen flicker. I'm saying there might not be a problem but when you get it under very precise circumstances I think you're deliberately looking for a problem...
Click to expand...
Click to collapse
I didn't go looking for the problem. I stumbled across it. I am very analytical, so once I find a problem, I determine the test case that produces it. I didn't return any of my phones for this problem. They all had other issues, such as screens that were not seating properly, one that displayed the left part of the image on the right side and vice versa (really weird that one), one that had a massive blue splodge near the middle of the screen etc etc
jonstatt said:
I didn't go looking for the problem. I stumbled across it. I am very analytical, so once I find a problem, I determine the test case that produces it. I didn't return any of my phones for this problem. They all had other issues, such as screens that were not seating properly, one that displayed the left part of the image on the right side and vice versa (really weird that one), one that had a massive blue splodge near the middle of the screen etc etc
Click to expand...
Click to collapse
That I can accept but this whole flickering issue seems a bit far fetched. I've got VERY good eyesight but cannot see anything wrong with my phone so I either have a perfect one or I'm just not bothered by it
Sent from my HTC One X using xda premium
picxar said:
yeah but not in this dimension, i thought a bunch of devices were faulty but not that much, what do you think hardware or software?
Click to expand...
Click to collapse
Not that much? How many does Amazon DE have in stock? 20? If it's more than that I highly doubt they opened every single unit to determine they're "faulty." The flickering's s/w and any phone is subject to it. Not all do, but all could. Last announcement on May 2 was HTC identified the issue and was working on an update specifically to address it. You're better off waiting until that fix is released.
ciubeca said:
I bought my HOX from an italian ebay seller (a month ago: htc23) and device has arrived with an Amazon Spain package.
Never had any issue: no screen flicker, no flex ..no gap
Click to expand...
Click to collapse
you are so lucky! mine is an ht23 too, but it does have flickering and suffers when pressing the LCD left side. HTC says it's normal for an LCD which is pressed, i've tried to explain them that this happens only on screen borders, that most devices have no flex issues and so on.....they don't want to replace it.
really disappointed.
my first and last htc for sure.
EddyOS said:
That I can accept but this whole flickering issue seems a bit far fetched. I've got VERY good eyesight but cannot see anything wrong with my phone so I either have a perfect one or I'm just not bothered by it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Indeed, but also how often are you staring closely at the screen while a web page is loading. It hasn't really bothered me but if it was flickering the whole time on a grey background, that would certainly annoy me.
Don't think I've ever seen a panel phone, tv or monitor that doesn't flicker under certain circumstances if you really look for it. Unless of course it's happening all the time in which case something is wrong.
My One X? No problems here as far as I can tell and I'm not about to start to try and make them happen either.
Don't forget also - everyone's eyesight is different. Anyone familiar with rainbow effect on DLP projectors? Doesn't affect everyone - it's something to do with the way the brain interprets the signals.......
Sent from my HTC One X using XDA
Federic0 said:
you are so lucky! mine is an ht23 too, but it does have flickering and suffers when pressing the LCD left side. HTC says it's normal for an LCD which is pressed, i've tried to explain them that this happens only on screen borders, that most devices have no flex issues and so on.....they don't want to replace it.
really disappointed.
my first and last htc for sure.
Click to expand...
Click to collapse
Strange, as my last 2 had that issue. Made a youtube about it, send the link to HTC support and they contacted me. They told me that it was not the way an One X panel should react on pressure. Got a refund after the 3rd one, now I'm struggling what to do with my premium navigation license.
EddyOS said:
That I can accept but this whole flickering issue seems a bit far fetched.
Click to expand...
Click to collapse
If its far fetched why have HTC admitted to the problem in one of the many threads raised by users facing this issue?
I have my HTC ONE X for more than 3 months now, and I've rooted and installed different ROMs right from the start. However, this problem has started just about a week or two ago.
Upon turning on the screen from sleep, or after using the device for a couple of minutes the screen turns into a total mess! It becomes completely stuttery, garbled, flickers , and basically it looks like an abstract painting. The image gets completely distorted making the phone unusable to the point I can't even restart it except with a long-press shutdown.
I've changed my Rom to a different one with a different kernel but the problem persists, so it's probably not a rom/kernel issue.
Has my hardware malfunctioned? Has anyone experienced this stuff? I'm somewhat amazed because it's worked flawlessly for some good 3 months.
I know there was a problem with flickering that HTC has addressed, but this is not just flickering, the screen becomes completely unviewable, totally garbled.
Would like to know if there's any way to deal with this aside of handing it over for repair.
Thanks!
After using my Pixel daily for 6 months (got the first batch, pre December 25th) and having next to no issues with it (wifi strength sucks, even with Xceed kernel, but it's better than it was), half of my screen decided it wanted to go goofy. I was using it two days ago and everything was working fine, I used it yesterday morning for a few minutes and then plugged it into the Google charger that came with it and let it sit on my couch for a few hours while it was charging. I got on the bus, and pressed the power button to wake the screen and nothing happened. Thinking I had it turned off I held the power button for a few second, and still nothing. So I held it for 30 seconds and when it brought up the bootloader warning the right side of the screen was glitching, same thing happened on the Google logo, boot animation, and continued into Android. I powered it off, hoping it would go away but it didn't. The slight glitch then turned into static "snow" which will then change sporadically based on what I'm doing on the tablet. That area of the screen still works perfectly because touch input works, and when I take a screenshot and view that area of the screen it shows up just as it should. It seems like there is an overlay on the right side of the screen that won't go away. Since it happens from the moment you turn it on makes me think it's a hardware issue but the fact that the screen itself still works perfectly makes me think it's a software issue. I haven't flashed the stock ROM back on it yet or locked it backup yet since I don't have a type c to type a adapter with me, it's still under warranty but I wanted to see if you guys could help me fix it before I sent it back.
TL; DR
This just started happening to me today, exactly as you described.
Interesting. I just RMA'd mine, should be receiving it within the next few days.
I'm returning mine too. I've determined that it's hardware because when I applied pressure around the edges of the screen I felt something slightly pop into place and then the problem was temporarily corrected. If I apply slight pressure to parts of the screen it happens again.
At this point I've flashed back to stock and I'm in an eternal recovery bootloop that I can't fix because acquiring USB drivers that work is incomprehensively difficult.
Just had mine go as well :crying:
Oh wow, that sucks. At least I'm not the only one though. I just got my new one a few days ago and all is well so far, hopefully this one won't screw up. RMA process was very smooth.
As for the USB drivers I usually have to install them manually by using the "select driver from a list"
Sent from my Pixel C using Tapatalk
Same issue on my first one
Here's my post from the mapping problems to serial # thread.
Google RMA process was fine once I was finally able to get a chat window with them.
Be sure to post to the problem mapping thread to help others!!
Add me to the list. Just went through the RMA process and am now waiting for the replacement to come. I can deal with the wifi issue and the random reboots, but having half of your screen corrupted is unacceptable. I don't even know how this is possible unless some genius at the pixel C team decided that it's cheaper to source half a screen and glue them together.
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
brando56894 said:
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
Click to expand...
Click to collapse
Most likely some latently defective silicon from Nvidia.
Sent from my Pixel C using Tapatalk
pkelly517 said:
Most likely some latently defective silicon from Nvidia.
Click to expand...
Click to collapse
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
brando56894 said:
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
Click to expand...
Click to collapse
Of course screenshots would come out perfectly. It's just a memory dump of the video RAM. This is a problem with getting that memory to the display. I think the display driver is part of the SoC. I could be wrong. Maybe it's a cable.
But it seems like a bit in the display driver is never getting enabled.
Sent from my Nexus 5X using Tapatalk
I'm fairly certain that it's a physical issue with the screen or the connection to the screen. When I had this issue I saw a visible change when I applied some light pressure around the edges of the screen. At one point it almost felt like something popped into place and the problem went away (then resumed.) Also, if I applied some pressure on the lagging side of the screen I would see some odd behavior as if the connection was fluctuating. I didn't squeeze hard, but it didn't take much.
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Wow really? That's no good!
Pixel C Screen Issues
Add me to the list, as of this morning. 8 months old.
SpaceGooner said:
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Click to expand...
Click to collapse
what's the serial# of your replacement?
lude219 said:
what's the serial# of your replacement?
Click to expand...
Click to collapse
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
SpaceGooner said:
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
Click to expand...
Click to collapse
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
lude219 said:
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
Click to expand...
Click to collapse
Thanks for the info. Not sure I'll be able to determine what s/n Google sends me next time, but here's hoping I get a good one and that I've just been unlucky so far. I won't be able to RMA until I get home from vacation later in the week anyway. If they send me another Pixel C that develops the half screen problem down the line, I will surely have to get a refund and maybe go for a top end Chromebook (with Google Play of course) next time.