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.
Related
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?
EDIT: This is the 32GB model, fwiw.
My new N7 had me very worried this morning.
I woke up and went to use the tablet, only to notice a very skinny - yet very noticeable- black line running the entire length of the screen, about an inch or so away from the right edge (when holding in portrait). I started searching around online, and it seems this was an issue on the older N7 model, and that Google typically replaced those units as it was usually a faulty screen. This made me very nervous as I've only owned this tablet for a week and I figured I would now have to exchange it. I tried everything from powering off, uninstalling the most recently installed apps, changing keyboard and a few other actions, but to no avail. I was about to perform a factory reset, to see if that helped, and decided to take a screenshot before I did that to show others what the issue was. Well, as soon as I took the screenshot (Home + Volume down), it went away! I can't imagine what caused it in the first place, but it's gone now and everything else seems to be OK, so I think this was just a false alarm.
Update: So the black line re-appeared later in the evening yesterday. I noticed that the line persists through the opening splash screen and boot anitmation when you reset the device, so I don't think it's related to the launcher (Nova) or any apps I'm using. I also determined that the line disappears when using the camera, so I'm really not sure what to think about this. If it happens again, I may just exchange it at BB since I've only had it for a week. I still love this tablet, and plan to keep using one for the foreseeable future, but I'm starting to become a bit nervous that this is a hardware defect that will continue to be an issue.
Anyone with a (new or old) Nexus who has experienced anything like this? Thanks very much.
goodwidp said:
EDIT: This is the 32GB model, fwiw.
My new N7 had me very worried this morning.
I woke up and went to use the tablet, only to notice a very skinny - yet very noticeable- black line running the entire length of the screen, about an inch or so away from the right edge (when holding in portrait). I started searching around online, and it seems this was an issue on the older N7 model, and that Google typically replaced those units as it was usually a faulty screen. This made me very nervous as I've only owned this tablet for a week and I figured I would now have to exchange it. I tried everything from powering off, uninstalling the most recently installed apps, changing keyboard and a few other actions, but to no avail. I was about to perform a factory reset, to see if that helped, and decided to take a screenshot before I did that to show others what the issue was. Well, as soon as I took the screenshot (Home + Volume down), it went away! I can't imagine what caused it in the first place, but it's gone now and everything else seems to be OK, so I think this was just a false alarm.
Update: So the black line re-appeared later in the evening yesterday. I noticed that the line persists through the opening splash screen and boot anitmation when you reset the device, so I don't think it's related to the launcher (Nova) or any apps I'm using. I also determined that the line disappears when using the camera, so I'm really not sure what to think about this. If it happens again, I may just exchange it at BB since I've only had it for a week. I still love this tablet, and plan to keep using one for the foreseeable future, but I'm starting to become a bit nervous that this is a hardware defect that will continue to be an issue.
Anyone with a (new or old) Nexus who has experienced anything like this? Thanks very much.
Click to expand...
Click to collapse
A line one the screen is definitely not normal. Specially after you have completed a complete system restore. I would suggest at this point to go ahead and exchange the unit.
[email protected] said:
A line one the screen is definitely not normal. Specially after you have completed a complete system restore. I would suggest at this point to go ahead and exchange the unit.
Click to expand...
Click to collapse
Thanks very much for the response. I'm going to go ahead and exchange it.
Also, apologies for originally posting this in the General thread.
So I decided to exchange my N7 due to the black line occasionally appearing. I took it back to Best Buy and was given another BNIB unit, only to discover that it was DOA when I got home. I tired using 4 different USB cables as well as different power adapters and electric outlets. No response whatsoever each time. Looks like I'll have to take this back tomorrow and hope that I get lucky with number 3.
I am on my second Pixel C where the backlight has stopped working after a month. The screen still works, if I shine a light at it just right I can see the contents (especially when they are white), but the backlight just doesn't come on. The previous one did this on and off for about a week while waiting for the replacement, meaning it would occasionally come back on and work for a little while. But, right before the replacement arrived, it went off and never came back on. My replacement did it for the first time today (it is one month old now), I connected to my laptop when I got home and issued an "adb reboot", and it appears to be working again. I have requested a refund from Google, but they said they couldn't authorize it, so I have filed a dispute with my credit card company in order to get my money back.
Overall, I like the device. I have had to work around a few of its shortcomings, but everything was satisfactory. I just can't keep replacing something every month.
Has anyone else experienced this? I mean, I know how to search and have found similar reports, this exact issue. Where the screen still comes on and is visible under the right lighting conditions, but the backlight is just non-functional. If so, what was the recourse you took to solve it? I have tried not putting it in my case (thinking that was the problem), rebooting (which occasionally has worked, but not always), factory resets (real tough without being able to see), plugging it in when malfunctioning, leaving adaptive brightness disabled, cursing at it and throwing my hands up in the air in frustration, etc. Nothing reliably works, and now I am afraid to let it go to sleep seeing how it came back after the reboot today.
Thanks for reading this...
My Pixel C started doing this last week. Wasn't so bad at first, but it's slowly gotten worse and starting last night the backlight will go hours without turning on. I've tried charging it, hooking it up to my computer, and just finished a factory reset and nothing has worked. Just like you if I shine a light at the right angle I can see things, but that's not exactly fun to do. Bought it at the end of March, so it almost made it 4 months.
One thing I should add, and this is probably a coincidence, is it started happening right after I downloaded the July updates. I only mention this in case someone else has had a similar experience.
My second one had gotten even worse, the screen sometimes comes on now, but the right half is either just fuzz or completely distorted, and the touch screen is non functioning.
I have ordered a Samsung galaxy tab s2, and will get my money back either from Google (doubtful), or my credit card company. Hope Samsung updates it at least to N.
I'm so torn, when it worked the pixel was awesome, I love the screen, closest any has come to the ratio of my camera. But two in a row only lasting a month each, and it's hard to consider a third, or fourth...
Sorry yours is glitching out on you, hope you get a satisfactory resolution.
I have the same problem. Exactly like you describe above. Since my Pixel C is one month out of warranty there is nothing I can do except warn others not to buy this product,
Oliver Browne.
Same here for me. First one started with screen issues as described above, lucky for me i was 3 days before the end of waranty, second one lasted 93 days... 3 days out of waranty for a replacement device! Thanks Google for a cheap device...
Envoyé de mon iPad en utilisant Tapatalk
I face the same issue, and was able to turn on the backlight by adjusting its brightness using the touch screen. Try shining a torch onto it while locating the brightness setting. This temporary fix works for me every time, and hope it helps someone.
Trying the torch was very useful! I now know for a 100% that the backlight doesn't work. I used the torch to see what I was actually doing on the screen, and erased all data & cleaned the cache.
Unfortunately the backlight stayed off, so I assume it's a hardware issue.
I've sent an email to Google support, hopefully they can get this one fixed or replaced.
did you manage to fix your issue ?
Same issue here, and no not resolved.
The only thing I can do to work around it is keep tapping the power button every second. Eventually you get lucky and the backlight will turn on. (Rebooting doesn't seem to be needed.)
Hi all,
I bought this tablet as a gift for my little brother. He encountered the very same issue 2 or 3 weeks ago, and it became worse today, as now backlight won't turn on anymore, even after a reboot and a factory reset.
It must be a hardware issue...
I will try to contact their after sales service, as the tablet isn't even 6 months old.
HI, my first Pixel c met this issues after 20 months... first it was only sometimes and backlight came back after some pushes on the power button... but it get worst and worst: 2 days without backlight and at the end half screen fuzzy issues. I order a replacement product with my warranty (2 years in Europe)... and now my second Pixel meets the same issue... with a no responding screen issue too... it's awful and my warranty is over yet... nothing can fix this...! something seems to be bad quality in this device....
I'm on my 2nd pixel c and final. Google support said that because they had replaced it under warranty the warranty only applies to the original purchase date not the replacement which seemed BS to me because I was shipped a refurb tablet
Never the less using adb/ fast boot I was able to get the device into bootloader and blindly reload the entire operating system. It was only until I performed a wipe within TWRP that the screen started working again. Interesting and now off it is working for the past hour or so. Currently applying latest updates but not holding my breath. Unfortunately it looks like Google is killing off the tablets and I don't know if any of their Engineers have actually tried to use a Chromebook in place of a tablet but it just doesn't translate well. If I cannot get this device working reliably I may buy another refurb to get a few more years out of it. The pixelbook is way too heavy for Couchsurfing
The screen comes and goes with no particular interaction. I'm really bummed because I had gotten so used to this device. I buy another but I'm afraid it's going to happen again. I don't see any tablets that are upgrades either. The Android tablet days are over. Pixelbook is not intuitive. Although it runs Android apps it does so very poorly with in Chrome OS and it's very bulky. I'm a try my luck with another refurb off eBay. Have not been able to find anyone that can repair 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
Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
I've faced the same issue mate....
a_bug said:
Fellow Pixel-ers,
So, I broke my screen about 8 months ago. It had coverage and got it replaced by a Google authorized screen fixer place.
I noticed early on that things didn't seem quite right. If I pushed down too hard on the screen, my touch wouldn't register. But, it didn't happen too often and I didn't want to have to deal with arguing that they may have poorly installed the new screen/digitizer and that it wasn't 'my fault'.
As time went on I started noticing that the almost bottom of my screen would not register a touch but mostly only at night. Again, it didn't happen too often and it usually went away after a little poking/prodding/pushing/.
I also thought it might be an application that I gave 'screen Overlay' rights that I shouldn't have and it was causing issues.
I validated my issue by using a Touchscreen Test app.
When I use an app like Vysor I am able to 'access' that area of the screen even when my fingers cannot. Does that validate this is a hardware issue?
The area affected was definitely more than just a few pixels (see screenshots).
More recently it was happening more frequently (not just at night) and it almost never goes away.
I wanted to make sure it wasn't a software issue. So I planned on dirty flashing my OS (AquariOS), but actually ended up accidentally upgrading to a clean version of Android 10. Unfortunately, the issue was still there.
I then did a clean flash and downgraded back to Pie w/AquariOS.
Shortly after getting back up the issue showed up again.
At this point, I have virtually lost all touch response for the bottom 1/8 (not quite the very bottom) of my screen. I've had to use a floating keyboard because the space bar falls right in that area. Sometimes I can't click 'next' or 'continue' in apps or web sites.
Has anyone ever experienced this very odd digitizer issue like this? Any thoughts/suggestions/ideas.
I'm guessing the only solution is a new phone as it is not worth the money to fix it.
So now I'm just waiting for either the Pixel 4A or 5 to come out so I can get a new phone I guess.
I just find this very odd how specific this area of 'dead pixels' is. I always thought it was more random than a specific rectangle.
I look forward to hearing from anyone.
A (not working with a full screen) Bug
Click to expand...
Click to collapse
Hi bro, I've face the exact same issue, but for me it was at the center of the screen. Luckily my phone was under warranty, but getting them to replace my touch digitizer was a whole different thing. At first they just didn't acknowledge the issue, then I tried showing them proofs but they didn't believe as they were from some third party apps. Finally, I used markup to show them the issue and recorded it took some screenshots as well. So, they replaced my digitizer at last after constantly speaking them for 2-3 weeks. I can only suggest you that if your phone is still under warranty or you have accidental damage coverage, ask them to replace them. Otherwise, it'll be better to buy a new phone as replacing the screen from your pocket may be very costly.
For anyone who reads this thread,
I resigned myself to having a bad digitizer but was starting to look to replace the phone. Then about a week later I inadvertently dropped the phone in a pool. Unfortunately, as the screen had been replaced the waterproofing was no longer good and phone was a brick. So I never resolved the issue but will always assume that the company that replaced the screen did a less perfect job and that when a screen is replace the phone looses it's waterproofing ability
-A (new Pixel 3XL owning) Bug