Develop Bugs

[Q] Advice on unlock/digitiser issue

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.

amazon, all One X are faulty :(

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?

[Q] Touch Sensitivity/Response Problems?

I bought my Nexus 7 2013 32gb model from Amazon and got delivered early before official local availability. I have noticed some touch problems in various apps (Pocket, Youtube, Chrome). I turned on developer settings and then turned on "show touches". When have problems it's like the touches are never registered. It's weird because its not consistent. I am considering sending it back for a replacement, but I have a friend who picked one up locally and has similar issues. I am wondering if this is a bug in 4.3 or something like that.
Any thoughts? Anyone else have this problem? RMA or keep it?

Flashing a different kernel could fix your problem as that is what bridges hardware and software.

Username invalid said:
Flashing a different kernel could fix your problem as that is what bridges hardware and software.
Click to expand...
Click to collapse
Looking to remain stock at the moment. I figure if its a kernel/software problem google will release a fix fairly soon. If it's a hardware problem unique to a small number of devices like mine then I would like to RMA it.

Liquidretro said:
Looking to remain stock at the moment. I figure if its a kernel/software problem google will release a fix fairly soon. If it's a hardware problem unique to a small number of devices like mine then I would like to RMA it.
Click to expand...
Click to collapse
Yesterday mine was fine and today when I was typing in landscape I was having the biggest problem getting the letter b to go through I actually would have to hold it for a brief second.... Then I restarted... And now bbbbbbbbbbbbbbbbbb.... Yup everyone goes through I have a feeling its a software bug but I'm staying unroofed till I know for sure ...
Sent 4rm my Nexus 7 2013... It feels and looks so sexy...

I'm having the same issues in chrome. I do tons of browsing and it seems about every 20 minutes I have to close out and restart the browser session. Anybody recommend another browser in the mean time?

zim2704 said:
I'm having the same issues in chrome. I do tons of browsing and it seems about every 20 minutes I have to close out and restart the browser session. Anybody recommend another browser in the mean time?
Click to expand...
Click to collapse
dolphin does the same sometimes. i like NEXT browser

the screen seems to be too insensitive imo.
i tried on my old nexus 7 and nexus 4 to keep swyping between "n" and "d" in the stock keyboard, they register all the gestures without dropping in between. However in the new nexus 7, it often drops my gesturing if i don't press on the screen hard enough.

Kind of makes me wonder if it's the calice I have on my thumb from using lighter too much
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...

I've noticed touch issues on my otherwise flawless screen (no dust, dead pixels, or multitouch issues other than this specific scenario) due to what I assume are grounding issues. I did some testing:
If I lay the tab flat on a table, and touch it with 1 finger, touches are only registered maybe half the time.
If I touch it with 2 fingers, no issues at all.
If I'm holding the tablet in one hand and touching it with 1 finger, no issues.
If I merely touch the case (not even the screen) with one finger while the tablet is flat on a table, and touch the screen with 1 finger, no issues.
Anyone else notice this?

My keyboard inputs letters that I don't physically touch at times when I'm writing a sentence so there definitely appears to be an issue with some units at least. I've never had this same problem on any other touchscreen device.

SubMatrix said:
I've noticed touch issues on my otherwise flawless screen (no dust, dead pixels, or multitouch issues other than this specific scenario) due to what I assume are grounding issues. I did some testing:
If I lay the tab flat on a table, and touch it with 1 finger, touches are only registered maybe half the time.
If I touch it with 2 fingers, no issues at all.
If I'm holding the tablet in one hand and touching it with 1 finger, no issues.
If I merely touch the case (not even the screen) with one finger while the tablet is flat on a table, and touch the screen with 1 finger, no issues.
Anyone else notice this?
Click to expand...
Click to collapse
Yup, same exact situation here. I hope this is a software issue that can be fixed
Sent from my Nexus 4

Mine doesn't register touches sometimes... contemplating on exchanging.
Sent from my SPH-L720 using xda premium

dcaplinger76 said:
Mine doesn't register touches sometimes... contemplating on exchanging.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Exchanging mine tomorrow.
Kills me, I had a 16gb with no issues at all, then earlier this week, exchanged for a 32gb and this one has touch issues! I also noticed right away that this 32 was noticeably more laggy due to a few milliseconds delay when I tap in one of the "bad" areas, which tends to be the top half of my screen.

Screen Issues: Right side of screen lags

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.

Weird Digitizer Issue (Just me)?

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