Develop Bugs

Hardware Issues? Broken Screen

Well, ive had my first HW issue today. I was using the phone as usual when the screen went funny and looked like it had "split" in two, two identical images one on top of the other. I took the battery out and put it back in and turnede the phone on and the display was flickering badly. It looked like the brightness was totally broken and was increasing and decreasing constantly. After trying to fix it i had to factory reset and i took it back to CarphoneWarehouse and got a replacement. Anyone had any experience of this? I did a Google search and noticed a similar issue with the G2. Im hoping this is just a one off and not and issue with the early devices. If it happens again im asking for my money back.

White static screen

I purchased the LG G4 from best buy about a month ago. My problem is that a quarter, half, or sometimes all of my screen will glitch out to white static. Sometimes it fixes itself, and sometimes it turns the display off. Sometimes when I turn the display on the glitching goes away for a while, and sometimes it just keeps glitching. It seems to happen especially while under load. It can happen on any screen though, including the home screen. After doing a little research I found some people recommending to enable developer options and Disable HW Overlays. This seems to have helped the problem, as with HW Overlays disabled the white static happens far less frequently. It dosent completely solve the problem though.
My question is if this is hardware or software realated. If the phone is running better with HW Overlays disabled, is it simply bypassing a piece of hardware that is causing the problem? My understanding is that it is forcing the GPU instead of the CPU to render the screen. I know very little about mobile phones though so any help would be much appreciated.
If someone could give some insight into what might be causing the static, and whether or not my phone is actually defective or if its some bad software, it would be greatly appreciated.

Something similar has happened to my screen, thought the problem only starts when I'm using Reddit sync. Basically the screen just gets really white for about a second and then fades back to normal. There was another thread about this issue but no solutions.
Sent from my LGLS991 using Tapatalk

Well today my phone glitched out completely and wouldnt turn back on. I had to remove the battery and put it back in to reset it. I still dont know if its a hardware or software issue, but at this point it dosent really matter. Its going back to either verizon or lg. I hadnt bought a lg product in years because I have had similiar experiences with their products as far as quality control. I figured id give them another chance this time. Its a shame they wasted it. To anyone who reads this, id recommend to at least exchanging this phone out for a replacement if possible, and would probably recommend a different model completely. Its a really nice phone when its working, but this particular problem is actually getting worse as time progresses.

LG G3 Screen Flickers, Distorts, and Fades to Black

This problem just started about a week ago. Sometimes after a few seconds of the screen being on, it will flicker, mostly at the corners. However, most of the time it will distort and eventually fade to black. It mostly seems to do it when the phone is warmer. For instance, in my office at work or home, where it's cool, it will not happen hardly at all. But in my truck on the way home, outside, or if I can feel heat on the back of the phone, it does it a lot.
All of that said, I know of the paper/eraser trick on the camera connector (which is very temporary, from what I've researched), but to me this seems to be a GPU/heat problem. Basically, I'm just trying to understand why this might be occurring. I don't want to order a new mobo and have it do the same thing. So, any help would be much appreciated!

How often is this happening to people??

mroneeyedboh said:
How often is this happening to people??
Click to expand...
Click to collapse
It happens to me about 15-20 times a day. More on the weekends because I use it more.

SheaCulb said:
This problem just started about a week ago. Sometimes after a few seconds of the screen being on, it will flicker, mostly at the corners. However, most of the time it will distort and eventually fade to black. It mostly seems to do it when the phone is warmer. For instance, in my office at work or home, where it's cool, it will not happen hardly at all. But in my truck on the way home, outside, or if I can feel heat on the back of the phone, it does it a lot.
All of that said, I know of the paper/eraser trick on the camera connector (which is very temporary, from what I've researched), but to me this seems to be a GPU/heat problem. Basically, I'm just trying to understand why this might be occurring. I don't want to order a new mobo and have it do the same thing. So, any help would be much appreciated!
Click to expand...
Click to collapse
I had a similar problem for about two months. I tried the paper thing over the camera sensor and I felt like it helped some but the problem still continued. The screen would just slowly go dark with vertical lines running through it. All apps would still work in the background while this was happening. I could boot to TWRP and this problem never happened while in TWRP which was odd. Seemed like if it was a screen issues or hardware malfunction it would happen all the time. That's when I decided to just flash back to stock. I was thinking about getting the S8 anyways so what the hell. I flashed to stock 10B and took every single OTA. Took all night but I've been running stock for over a day now and the issue has not replicated itself one time since reverting back to stock. I was on RR Nougat and Fulmics when it happened prior. Has to be a root or Rom issue? What ROM are you on?

Pozman1 said:
I had a similar problem for about two months. I tried the paper thing over the camera sensor and I felt like it helped some but the problem still continued. The screen would just slowly go dark with vertical lines running through it. All apps would still work in the background while this was happening. I could boot to TWRP and this problem never happened while in TWRP which was odd. Seemed like if it was a screen issues or hardware malfunction it would happen all the time. That's when I decided to just flash back to stock. I was thinking about getting the S8 anyways so what the hell. I flashed to stock 10B and took every single OTA. Took all night but I've been running stock for over a day now and the issue has not replicated itself one time since reverting back to stock. I was on RR Nougat and Fulmics when it happened prior. Has to be a root or Rom issue? What ROM are you on?
Click to expand...
Click to collapse
I became so fed up with the issue that I caved and bought the Nexus 6P last year. My G3 was on stock OS, no ROMs. Pretty sure it was a hardware issue. I turn it on every now and again, and the same thing happens. Never really solved it. I may try flashing some ROMs at some point, but I think I'm done with Samsung devices for the time being. I absolutely love my Nexus 6P. Great phone. Waiting for the new version of the Pixel or the rumored new Nexus haha.

It's an issue due to bad quality soldering and the SoC overheating. When the phone is very warm (and the G3 tends to get quite warm on the Camera) and you keep using it, the bad soldering starts losing con ection.
So you're basically losing connection to your chip and that's why the phone is experiencing those problems. That's why putting pressure on the chip helps to restore the connection.
It's best to use a thermal pad and it's the best solution there is. Some people bake their motherboards but I don't recommend it since this always kills the motherboard in a few months.
You can also try looking for a replacement motherboard online.

engmia said:
It's an issue due to bad quality soldering and the SoC overheating. When the phone is very warm (and the G3 tends to get quite warm on the Camera) and you keep using it, the bad soldering starts losing con ection.
So you're basically losing connection to your chip and that's why the phone is experiencing those problems. That's why putting pressure on the chip helps to restore the connection.
It's best to use a thermal pad and it's the best solution there is. Some people bake their motherboards but I don't recommend it since this always kills the motherboard in a few months.
You can also try looking for a replacement motherboard online.
Click to expand...
Click to collapse
Mine screen fades to brightnes, and strips when phone is cold. when it gets worm hot screen is almost perfect. same thing with two mobo's.

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