Related
Anyone else getting the ghost touch problem?
I couldn't work out what was causing this on my phone so I enabled show touches in the development menu and it shows.
It goes from 2 to 3 spots on the left hand side of the screen.
It's not a major problem but happens at least 3 times a day and won't snap out of it unless I put the phone back into sleep a couple of times.
Do you think maybe scratches on the screen cause this?
TIA
Is your phone connected to a charger when this occurs? It might be it, since im experiencing the same thing since htc desire hd.
miHah said:
Is your phone connected to a charger when this occurs? It might be it, since im experiencing the same thing since htc desire hd.
Click to expand...
Click to collapse
No. Can happen at anytime. Quite random.
It takes a few on and offs with the sleep button to stop it.
Can't get off the lock screen until it goes away because I can't move the unlock slider.
Very annoying.
I had the same problem - the first day i got my hox. With and without the charger (with charger a litte bit more often i think).
I pushed the complete left side of the screen (top) carefully and now it works well. No more ghost touches ^^.
\/\/iLLow said:
I had the same problem - the first day i got my hox. With and without the charger (with charger a litte bit more often i think).
I pushed the complete left side of the screen (top) carefully and now it works well. No more ghost touches ^^.
Click to expand...
Click to collapse
Ok. Once I pushed around the screen edges, the left side has some play and moves maybe a mm with a slight creak.
I push it in but still that little bit of play on the left side.
It's quite impossible to show the service centre the problem because its so random but now I can show them this.
Cheers.
I hope you'll get a new "perfect" hox and i'll not have the same problem later :fingers-crossed:
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.
My Asus Zenforne 2 suddenly started behaving unexpectedly.
Even if the screen is locked and closed, phone automatically tries to open but as it is locked, it will show wrong password.
But its keep on trying to open the screen, its like a continuous screen touch happens every time.
After I open using my password, it is accessing the phone automatically like opening application what ever is present and keep on doing something.
So basically phone behaves as some one keeps on clicking the phone continuously.
I thought it might be happening only during charging, but it proved me wrong.
I did restart many times, after every restart for few minutes, it works fine but after sometime, the same story.
I did clear the cache partition, but still same issue.
I did factory reset, it took around 3 hours.
Post that it is working as expected. Dont know what was the issue exactly. I had many apps installed.
But again after few minutes, the same issue appeared. System keeps on clicking randomly throughout the screen.
I am not able to do anything.
i have the same problem to...the screen die...change the screen all will work fine again
mine warranty passed...have to paid hopes yours is still under warranty
bishnuprasad14 said:
My Asus Zenforne 2 suddenly started behaving unexpectedly.
Even if the screen is locked and closed, phone automatically tries to open but as it is locked, it will show wrong password.
But its keep on trying to open the screen, its like a continuous screen touch happens every time.
After I open using my password, it is accessing the phone automatically like opening application what ever is present and keep on doing something.
So basically phone behaves as some one keeps on clicking the phone continuously.
I thought it might be happening only during charging, but it proved me wrong.
I did restart many times, after every restart for few minutes, it works fine but after sometime, the same story.
I did clear the cache partition, but still same issue.
I did factory reset, it took around 3 hours.
Post that it is working as expected. Dont know what was the issue exactly. I had many apps installed.
But again after few minutes, the same issue appeared. System keeps on clicking randomly throughout the screen.
I am not able to do anything.
Click to expand...
Click to collapse
Your problem appears consistent with "Ghost touch". It is a well known problem for zenfone 2. You can search about that with the keyword Ghost touch in here or in the google and read about it if you want.
If your phone is under warranty, contact the service center and schedule for the repair. They usually change the digitizer.
If your phone is out of warranty, you can order the digitizer for around US$ 30-50 and change it yourself. There are a couple of instructional video on youtube showing how to replace the digitizer for asus zenfone 2.
Thank you sway8966.
I observed few things
1. When the phone is in charging and little bit heated up, this happens very frequently.
2. After long usage, when the phone is warming up, this issue happens.
3. Sometimes, even it is there lying on the desk, still happens. Wiping up the screen cleanly helps sometimes.
4. Most of the times, the clicks or touches happening on one single row.
5. When the phone is locked as pattern, all the clicks happens on the first row of the pattern lock only.
So not able to conclude, what is the issue exactly. Whether it is screen problem, or due to heating up or due to insulation issue.
I have read multiple posts in many platforms but not able to conclude the root cause of the issue.
p.loong said:
i have the same problem to...the screen die...change the screen all will work fine again
mine warranty passed...have to paid hopes yours is still under warranty
Click to expand...
Click to collapse
My warranty also expired just a month back.
So no idea, how much it will cost and whether it is worth spending the money or go for a new device.
bishnuprasad14 said:
My warranty also expired just a month back.
So no idea, how much it will cost and whether it is worth spending the money or go for a new device.
Click to expand...
Click to collapse
It cost around $40 in indonesia, maybe u should consider to change the screen.
Oh yeah, dont take ur phone to asus service center when ur guarantee is alrd expired, it will cost around $120 to replace the screen :crying:
I also had this issue, but it was due to a cheap glass protector I had got from Aliexpress. I suspected it could be that, since the issue appeared just the day after I put the protector on my phone, about one week ago. This morning it suddenly began happening again and it stopped just after removing the glass protector, and it hasn't happened again yet, so I guess I was right. If any of you also used a cheap protector, that could be the source of the problem. I have now ordered a Nilkin protector, which is supposed to be of superior quality (and is indeed way more expensive) and hope I can use it without any ghost touches.
jman0 said:
I also had this issue, but it was due to a cheap glass protector I had got from Aliexpress. I suspected it could be that, since the issue appeared just the day after I put the protector on my phone, about one week ago. This morning it suddenly began happening again and it stopped just after removing the glass protector, and it hasn't happened again yet, so I guess I was right. If any of you also used a cheap protector, that could be the source of the problem. I have now ordered a Nilkin protector, which is supposed to be of superior quality (and is indeed way more expensive) and hope I can use it without any ghost touches.
Click to expand...
Click to collapse
I had exactly the same problem yesterday but the "ghost touch" problem had happened 3 days after I've put the protector. So I've removed it and the phone works fine again. It was this glass protector : https://www.amazon.fr/gp/product/B01GTE6TUA/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1 so avoid it
This problem just started today, I've done nothing with settings, have not installed any apps recently, did not drop it, expose it to water, or anything that could possibly cause damage. What's happening is that basically about 1 inch-1 inch 1/8 of the bottom of the screen turns black, and at almost random, sometimes it could go a minute and half or so, sometimes 30 seconds, sometimes within 5 or less seconds. The strangest part? The part that goes black still operates fine to touch, so if an icon or letter of the keyboard, or whatever, is located in that area, it can still be selected/operates. Taking a screenshot to try to show it is worthless since it'll show the screen as just fine, so I attached a picture and a video of the problem from an old phone of mine. The blacked out are will go right back to normal if you turn the screen off, wait a second, and turn it back on. Also, if the blacked out area is there, it'll go away after about a half a second when the screen dims right before the screen inactivity turns the screen off. I've only had this phone for a couple months, I got it back on December 7th 2019.
I learned something else. If I manually lower the brightness to a particularly low level, the black goes away, so it seems to in some strange way be related to the phones brightness level (I use auto brightness), this also might explain why the black comes at differing intervals, as my brightness is adjusting constantly to my surroundings, the time before it comes is either shortened or lengthend based on the brightness.
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
I was just thinking I might have to do factory reset, if that doesn't work, and it needs repair/replacement, do I go to an authorized Samsung repair place (I know I have one within about a couple miles of my house), it's
obviously well within warranty, or take it to At&t store as I do have that AT&T Protect Advantage coverage for my phone?
willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Did the factory reset, turned out to be a waste of time. That black bar was showing immediately, right at the setup screen. So I guess it's safe to say that it's a hardware issue, defective whatever. Funny story is that when I bought this phone, my att store only had two of them left, one was immediately defective, it wouldnt get past the main logo screen, and now I got this one and it became defective within just a couple months, got to love it.
willhemmens said:
It doesn't seem that strange that the touch still works in that area as the digitiser and the display are two different things. I would factory reset (because Samsung will make you do this anyway) and if still an issue, take it directly to Samsung, that does not look good.
Click to expand...
Click to collapse
Just left AT&T store where I initially purchased the phone. They're shipping out a brand new note 10+ to me today and I'll get it tomorrow ?
Glad to hear! That definitely sounded like faulty hardware. Funny you saw two failures, I guess it will happen with such complex devices.
Note 10 plus screen goes black
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.
Tech girl99 said:
Hi i thought i was crazy until i saw your thread. The same thing is happening to me but it does not go continuously so id see two red squares first theyre really small and they appear anywhere on the screen then if try to screenshot them they show upblack in the screenshots instead of red . I just need to know if anyone found a solution yet because my phone came with the warranty booklet but it wasnt filled out.
Click to expand...
Click to collapse
You just need the proof of purchase, or, if you got it on contract, the contract itself will suffice
Hi, I’m having a problem with my Huawei Mate 20 that I bought in 2019. The screen brightness is too low even when set to 100%. This started happening two days ago after I spent the day outside in the sun (i don't know if hot temperatures influenced but has already been 2 days so is strange). When I got home, I charged my phone and opened some apps, but it started crashing and the screen went black. I tried force rebooting it multiple times but the screen remained black. I thought it might be a battery issue so I charged it for an hour and a half but still nothing. After 40 minutes, I accidentally pointed a lamp at my phone and could see that it was working perfectly but the brightness was very low. A similar thing happened to me in 2020 but I can’t remember how I fixed it. I tried searching for solutions online and on XDA developers but none of them worked for me except one that involved ADB which I can’t try because for some reason I can’t connect my phone to my PC with USB debugging. My warranty has expired like 2 years ago so lol... and I haven’t received a response from Huawei support yet (i emailed them yesterday)
Welcome to XDA.
It was heat damaged. Anything above 125F can do it. Exposure to direct sunlight on a hot day is especially bad.
I did this accidentally to my Samsung S4+ years ago. Very faded out and got worse the more I used it.
Oddly after sitting unused it got slightly better. After I got a new phone it sat for months unused, it improve further still. After 3 years it appears to operate normally now. The crystals seem to have reverted back. Peculiar critters.
Yours may or may not do the same. There may be a way to accelerate the process. Mine sat in both hot and cold environments during that time.
Putting a charge on the crystals by using the phone is probably what hindered their recovery.
Either replace the display or let it rest. Using it will likely make it worse...
blackhawk said:
Welcome to XDA.
It was heat damaged. Anything above 125F can do it. Exposure to direct sunlight on a hot day is especially bad.
I did this accidentally to my Samsung S4+ years ago. Very faded out and got worse the more I used it.
Oddly after sitting unused it got slightly better. After I got a new phone it sat for months unused, it improve further still. After 3 years it appears to operate normally now. The crystals seem to have reverted back. Peculiar critters.
Yours may or may not do the same. There may be a way to accelerate the process. Mine sat in both hot and cold environments during that time.
Putting a charge on the crystals by using the phone is probably what hindered their recovery.
Either replace the display or let it rest. Using it will likely make it worse...
Click to expand...
Click to collapse
Hi black, thank you for the warm welcome and for responding to me. In fact, now that I think about it, the last time this happened to me, I had exposed it to a lot of sunlight. Would it be a good idea to place it in a cooler or shadier location to speed up its recovery? And approximately how long should I let it rest? About a week?
Luke221 said:
Hi black, thank you for the warm welcome and for responding to me. In fact, now that I think about it, the last time this happened to me, I had exposed it to a lot of sunlight. Would it be a good idea to place it in a cooler or shadier location to speed up its recovery? And approximately how long should I let it rest? About a week?
Click to expand...
Click to collapse
Cooling it might hinder it's recovery. Not really sure. I was surprised when mine eventually recovered. Not saying this will be your outcome.
Also it may take way longer then is practical
If you need to pull data leave it sit for as long as you can wait.
It's back lighting is working, right?
blackhawk said:
Cooling it might hinder it's recovery. Not really sure. I was surprised when mine eventually recovered. Not saying this will be your outcome.
Also it may take way longer then is practical
If you need to pull data leave it sit for as long as you can wait.
It's back lighting is working, right?
Click to expand...
Click to collapse
Lol, it looks like i just ****ed up my phone. Before I started this thread on the forum, for pure curiosity, I tried to activate the torch but it didn’t work despite multiple attempts. I hope it’s not a hardware issue ()
Luke221 said:
Lol, it looks like i just ****ed up my phone. Before I started this thread on the forum, for pure curiosity, I tried to activate the torch but it didn’t work despite multiple attempts. I hope it’s not a hardware issue ()
Click to expand...
Click to collapse
It can easily happen; protect from drops, water... and heat.
The battery may have failed if the phone died completely.