yashsingh1/xdaforums huggingface dataset:
[G2 General] Compass Linux:
Since it's apparently a hardware defect, yes, it could happen on any variant.

LG as far as I know made no official statement regarding this issue.

Compass.
[G2 General] Manper:
Hi I have a problem happened Mobile

Fallen lines from top to bottom

Black line is so much more that was

Have you ever seen such a problem? Help me please

My English is not that good

Please type in a simple way
[G2 General] Compass Linux:
I forgot to say my panel.

Running CloudyStock 2.2:

$ su -c 'cat /proc/cmdline'

mdss_dsi_g2_lgd_cmd

So I have a LGD Panel.

Compass.
[G2 General] jal3223:
So, is it safe to say at this point that the problem comes from incorrect ROM settings mostly? In pretty bummed out because the day before I was planning on buying this phone (because of all of the dev support) this thread shows up. Lol.

Is it basically a problem only affecting a small percent of display, or has the problem gotten to be pretty common? Also, i wonder how LG will address this problem when warranties start running out being that it is an obvious hardware defect?
[G2 General] MasterTB:
Am I wrong or everyone with the issue was running TWRP?

When I used TWRP on my G2 I had issues with USB connection to pc and file transfers, changed to Philz and never had issues again, of any kind....

I'm on Carbon, 24a sources, June 01 nightly, no black lines. LGD panel also.
[G2 General] Compass Linux:
The G2's with this problem are few. The nasty part is that it is spread between ROMs. Check OP.

Compass.
[G2 General] Compass Linux:
I flashed twrp-2.7.0.0 before flashing P.A. and didn't have any problem at the time. The P.A. upgrade is when the black lines appeared, but again, it isn't exclusive to P.A. as stated in the OP.

I don't think twrp has anything to do with this problem. It's such a popular recovery and the number of reports of G2's with black lines is low. The OP has some explaining of this issue from the developers.

Compass.
[G2 General] Havoc2k:
I was also running PA rom but flashed it with philz recovery. I had no problems with my display. :)

Now i am running on Pardus 7.2 without any problems.

greetings
[G2 General] MasterTB:
Yeah, I've been reading a lot about this but, in order to flash anything you need a recovery and, since they all seem to have the same, maybe there's some operation gone wrong while flashing that ends up causing this, some files copied in the wrong place, or missing ...

What do I know, I'm just guessing at this point. But you're maybe right, recovery shouldn't have anything to do, should it?
[G2 General] NisseGurra:
I had the same bug, Rom: Pa beta. No warranty so it was a very expensive flash...
[G2 General] Compass Linux:
Wild guess: A combination of factors. Certain Panel Displays (defective ones?) + Commits the developers mentioned + Recovery (maybe) + Some Custom ROMs (except Mahdi; didn't include certain commits; read OP) = Issue triggered

I hope my guess is wrong, because there's too many variables to consider.

Compass.
[G2 General] mandroid717:
not sure if it relates but was running stock mod rom with philz recovery, oced kernel, cpu/gpu overheated and froze my G2 after some intense game playing. after reboot 2 lines on right of display. only run stock mod roms. Lgd panel.

anyone tried to kdz back to stock?
[G2 General] vrda08:
So maybe is real problem in overheat on SOC.

maybe for someone temperature throttle stop working in some cases..like when doing flashing\backup in recovery..or like your case oced kernel.. Maybe is real problem high temps on soc and temp. Throtthling not downclock freq. And in that case high temp. impact on glue on display connectors...who knows...
[G2 General] Hiniakel:
Hi there,

both phones are working except of the screen "failure" - one of the phones will be repaired on Monday (warranty - hopefully). I used PA Auto update with TWRP 2.7.0.0. The Screen Problem happens after sudden reboot ~2 days after update...
[G2 General] :
would have been nice to have those logs maybe
[G2 General] reas0n:
About this damages, what about these partitions like rpm and tz? For sure a lot of people didn't upgrade it. I used AutoRec to do it and everything works well. Is it related?
[G2 General] RusherDude:
This is exactly why I think its not ROM-related, but G2-related. When you overheat it (and some are better constructed, better placed glue than others, specially last batches) there's some kind of overheat problem that affects the screen.

The joke here is that it seems that the G2 gets the most overheat while flashing, but gentlemandroid replicated the issue while doing intense gaming. That would also explain why people get it after sudden reboots: sudden reboots happened due overheat (like desktop pcs with thermal problems..) and that caused the problems, not the reboot itself.

If my predictions are true, a great % of the G2's could be afected and get problems absolutely anytime when gaming or flashing. I hope its only the first production batches, if not, we may be talking about 100% affectance.

Just incase, I'd flash stuff with the phone on the freeze for now.
[G2 General] Compass Linux:
Well, Mahdi ROM G2's don't have this issue, and it could be related to the fact that it doesn't over heat due to the non inclusion of the two commits stated in the OP.

My G2 gets very hot while playing Plants vs Zombies 2 but it never rebooted on its own. The accumulated gameplay time + flashing this and that could have contibuted to this problem. My phone was bought last december, and it likely is a early batch. At least it's still under warranty.

What you said makes sense. I'm going to add your post to the OP and see if people can replicate/remember the conditions in which it happened to them.

Even by reading this thread with some posts mentioning heating, I didn't realize it could be related. :rolleyes:

Thanks.

Compass.
[G2 General] RusherDude:
Exactly my thoughts on the bolded part. Acummulated head ended up causing glue damage and in the very end screen problems. This doesn't sound any good since every single G2 and related models (even Nexus 5*) could be affected by this, unless they fixed the issue on later batches.

About Mahdi rom, yeah, one rom that doesn't cause problems and that generates less overheat.. another step into the same direction.

And don't be happy about getting those conclusions, since this is a disgrace for the G2.

* Nexus 5 had thermal screen problems on some first units, when overheated, a part of the screen when lighter than others (permanently). An entire medium-size circled zone in the right-middle of the screen with a tone way more white than the rest and some lines (I will try to find the thread, can't now). Also, Nexus 5 is famous for being one of the worst thermal-controlled devices ever, it can get ultra hot and the performance epicly drops at the minium heat. Since LG made N5 the G2 too, I see a connection here.

EDIT: Some thermal-related causing screen N5 problems in this google products forum thread: Not sure if the issue I was talking about, but related to overheat and some screen damage mentions caused due to it..

EDIT2: XDA thread about the issue. Check the damage pattern:

Coincidence? It's a N5, a brother of the G2..

Thanks! Best of luck.

PS: Also, I still don't think it is "permanent damage". At least, cannot understand why the lines are black normally and white while booting. How could the color values be inversed if its a damaged zone? anyone could explain?
[G2 General] Compass Linux:
I opened a thread in the Q&A asking about the temperature in Mahdi ROM during intensive tasks, which you can follow here.

Compass.
[G2 General] NisseGurra:
The damage i got was permanent black lines, even i recovery. Restoring kdz etc-era did not solve the issue. The lines persists in boot, recovery and all roms i tried.

I was not an heat issue as the last flash was done i rather cold environment.
[G2 General] Compass Linux:
The accumulated use of the phone (wear/tear of the glue due to heating + low quality) seems plausable to me.

If your phone (we can't see it but it is there) wasn't glued properly and is almost coming off, perhaps a simple flash with a slight rise in temperature in a cold environment can trigger the black lines?

Compass.
[G2 General] NisseGurra:
Your guess is as good as any other. Only thing i know that flashing an PA beta damaged permanently my G2. I know there risks in flashing roms but this was 1st time i got HW faults. Anyway, lets hope this bug finds its cause.
[G2 General] :
well I wouldnt support the theory as many devices at once had this, with most common dinominator a series of roms that had the same commits that others didnt have. in the past some devices have run very hot with no such issue.

I would suggest its a dormant bug, triggered in rare circumstances without those commits, but frequently with those commits.

I wonder if those who disabled thermal throttling before experience this more. its a shame we have no logs of when this was happening. they could show temp rises or other info unique to this issue.
[G2 General] Gandalf:
we discussed this earlier (@driodmoaster92 and i) and we won't be updated Omni to the new 4.4 sources until this damaged screen issue is confirmed and verified to NOT be related to the 4.4 kernel/blobs in any way, shape or form.

I'm quite skeptical about them right now and don't want to be pushing nightlies that are breaking hardware because of a fault somewhere.

I just got back from travelling for a few days so I'll be taking a look through this thread and some others, as well as the 4.4 sources soon.
[G2 General] RusherDude:
Thats like saying that there is a ghost that doesn't like LG and haunts the screen of those with a G2 ruining the thermal shield. There is absolutely nothing that points at such scenario. I talk about heat problems because that matches the same situation between flashing and gaming = overheat. With that we can start on something, not with such an arbitrary statement. You can't compare both hypothesis and tell that they're the same. One has arguments, the other is a free idea.
[G2 General] DREWHAMM974:
Looking back when I took that OTA on mine I had gotten into an intense GTA gaming craze for a few days and got upset by the system update keep popping up in game. At the time there was not a reliable recovery method for the ls980 with KK so I was not going to do it in case I wanted to flash AOSP down the line. I took it because it was aggravating me so bad during playing and that's when it happened. My G2 was already quite warm as it was when I did it so the heat theory seems very likely to me.
[G2 General] RusherDude:
Interesting. Very intense gaming "helps" with the issue, as expected with this hypothesis :(. Thanks for your input!
[G2 General] Jank4AU:
I think it's phone related AND possibly commit related. Take my phone for example:

1) had since first 30 days the phone was out (maybe a more well constructed batch)

2) flashed every ROM & PA beta Houston has put out

3) TWRP 2.7

4) running updated tz/rpm partitions

5) stock KK modem

6) no problems

7) no overheating

8) no lines

Common variable is the phone
[G2 General] :
lol, lets not start a flamewar. But previously devices have become very hot without such issues. So the heat itself seems not directly to be the cause of the issue, but perhaps a symptom/trigger?

also coincidental mass derping of a heatpaste thing just doesnt seem likely, as the mass blacklines on devices seem to have dissapeared the moment certain commits were retracted and activities carried out. Thus making the case for certain commits more likely, especially considering roms like Mahdi have not had a single occurance of blacklines perminent or not ever.

all my hypothesis are based on facts, not ghosts. And yes I can combine them cause we are all guessing and have not established anything thats mutually exclusive.

edit except phone and commits, that seems mutually exclusive. Come to mind, also nexus 5 reports seem interestingly linked, could be chance, perhaps not as they are from same manufacturer. Interesting.
[G2 General] F1fan07:
Hey guys, just reporting in with this issue:

http://xdaforums.com/showthread.php?t=2773875

ioroot v25 to root via adb

vs980 AutoRec to flash 2.7 TWRP

backed up EFS

nandroid backup

full wipe

flashed xdabbeb VS98024A v1.1.1

flashed xdabbeb alarm fix

flashed xdabbeb kernel 1.1.0

LGD panel

Let it run all night, took it off the charger this morning and powered it off to put SIM in. Phone rebooted instead and I thought, "that's weird".. Powered it off and it rebooted again, "oh sh!t", I thought.. Then the LG logo came up and sorta went inverse of the colors...white with a dark greenish logo.. Held down the power again and it rebooted again and the normal logo came up but with a parallel white line and the LG logo kinda off center.. Then when the ROM booted up all the way I noticed the horizontal dark lines staggered down then right side of the device. Stays that way in recovery and even after loading stock backup. Guess I gotta get it back to stock and swap it at BB. Pic attached!

Hope this helps people figure out the issue.. Makes me wary of LG phones for sure. Say what you will but my M7 didn't do this sh@t! :)
[G2 General] butler360:
Which panel? LGD or JDI?
[G2 General] RusherDude:
Sorry if it seemed to be an attack, that wasn't the intention.

My point is that we got to start on some base, with nothing supporting an hypothesis it has no weight at all. The problem appeared with those commits? Dunno, maybe those commits forces the phone to do more work, more load, or something? And that generates heat? I'm not sure, I just know that people got problems on stock rom, which for me discarts absolutely any direct relation given by the commits.

By the way, my way of thinking references my Galaxy S2 superbrick issue: For those not aware, when samsung released the 4.0.4 official rom for the S2, and the first custom roms started appearing, a lot of suddent bricks started appearing. They were strange, because the dev flashed the rom 20 times before publishing it with no problem, and some were getting bricked some not. It was a mistery, a pain, terrible, the entire S2 community was in shock for some time, even a loong thread with hypothesis started, and heros started testing. Later, it was discovered that it also happened on stock rom, when doing wipe data. At the end, after some people suceed in getting the brick in their tests, and some google employee helped with the issue: The EMMC was **** and had a terrible but: attempting secure erase on it may randomly lock the chip until it got reseted on factory (very hard brick, not even JTAG could do anything, thats why it got called superbrick). A google employee said that they discovered that when developing ICS on the Galaxy Nexus, that samsung was going to use that **** EMMC and they said go away this sucks. The problem was a simple MMC_CAP_ERASE flag on the kernels, which provoked that doing a wipe tried a secure wipe and blamm... random chance to die. At the end, after months of fighting with samsung, the 4.1 kernels were safe.

What I want to say: at first we also though that the problem was the new ICS commits, until someone found the problem on STOCK. There everyone went nuts until it was discovered that it a simple wipe that could cause the problem. Thats why I say that probably here the explanation is way more simple that the commits or anything KK related: this phone is made like **** (like the Nexus 5) and overheat ****s up the screen. If stock people are getting the problem, you should stop focusing on custom roms and commits: the problem is not there.
[G2 General] :
well, yes and no, yes because it also occurs there and no because it didnt occur on a massive scale there

the fact that the massive scale was on custom and certain commits make it easier to trace then a few stock occurrences. Especially between builds, cause the amount of commits between one build and the other are smaller.

Also you made the case for a possible dormant issue more likely.

What happened with Samsung was bad, a developer found on a Samsung Nexus device this emmc firmware bug before it was out, they fixed it then, Samsung quality did nothing to prevent that, and so it spread across their flagships. By using same emmc chip with same faulty firmware on chip. They denied it, even when the finder developer of Nexus device stepped forward. Oh boy what a fiasco. Entropy guarding the community eventually even had Koreans fly to the US to him to show what and why it was going on. Amazing, goodguy entropy. That bug funny enough was never fixed. The bug was prevented from triggering (not same as fixing it) by having a "safe" kernel. So here its dormant as well, one software update without secure wipe switched off and boom its back. Good thing they stopped updating a lot of those devices.

We have already seen certain bugs being fixed and reappear, so be wary what you flash folks regarding these commits and the blackline issue.
[G2 General] RusherDude:
If you mean my example, it was waaay more massive than this :(
[G2 General] :
agree, but still the scale is big regarding before those commits and after.
[G2 General] turbo8687:
I've seen that exact screen 4 times, held down and power to reset. No black lines yet, feel like I'm pushing my luck at this point.
[G2 General] F1fan07:
LGD using Panel apk

got the phone new last week and not new to the Custom ROM scene
[G2 General] Roseysdaddy:
what is the difference between the LGD and JDI displays?
[G2 General] butler360:
Different manufacturer, from what I have heard. It seems like mostly LGD ones have been going out, while I haven't yet seen a JDI reported. This is very interesting to me since mine is a JDI and I have been too scared to flash for quite some time now... :eek:
[G2 General] Hiniakel:
Hi there,

I have never played games on my phone - so I don't think so theres a overheating.... My wife played games, both phones have the same issue with the black lines... Both D802 16GB with stock modem and latest PA with Pa auto update. Never had other Kernel or Roms on the phones... Both ae actually in warranty repair.. Hope they'll fix it...
[G2 General] thejoshiewawalee:
how do you tell if your phone is a JGD or JDI?
[G2 General] Compass Linux:
Here.

Compass.
[G2 General] abdel12345:
Ok. Checked and i have lgd panel. Now I'm confused on which ones having the issue? Lgd or jdi. Ive flashed kitkat roms with no issues before like paranoid android. But i have no warranty because i bought it used so Im worried about flashing anything now.
[G2 General] kevingokki:
i encountered another screen bug while playing with CM11s quickboot on Carbon. Multiole blue lines on the left, black background. red static lines horizatally across the screen. good thing no permanent damage
[G2 General] Compass Linux:
Mostly LGD but these are more common than JDI, so no conclusion for now.

Can't recommend what's best for you since we don't know all the details yet. One suggestion to be on the safe side is to not flash anymore, or flash a Stock/Custom (safe, read OP) ROM and stay there until we have full information.

Compass.
[G2 General] Jank4AU:
Do you know how old your device is? I suspect the older ones are built better. I have lgd and one of the first ones out (bought about 3 weeks after release) and have been flashing like crazy. I have a feeling its the newer phones, but I can't prove that.
[G2 General] Compass Linux:
I bought mine in December 2013. I don't know when it was manufactured, but judging from when the G2 was officialy launched (September 2013) I have an older one.

Might have abused the quad core with too much Plants vs Zombies 2. :p

This thing ain't a video game but I treat it as such, lol.

Compass.
[G2 General] ckyy:
Let's rewind a few days back :

I was on Mahdi R4 before i flashed PA Beta7. Hearing about those issues i decided to flash carbon nightly 06/01. The first boot after flashing the rom was really strange. After the kernel splash screen the boot animation was REALLY distorted. Half of the LG logo from the kernel splash was on the far right and there where red and green lines EVERYWHERE. I don't know what would have happened after the boot because i always did a force reboot until the boot animation was playing properly. 2 out of 3 boots were like that. There were no lines after the boot however.

This happened to me yesterday :

I turned my phone off (it was totally cool, barely used it before). About an hour later i went to turn it on and it ****ing happened. Kernel splash screen turns ****ing white with random lines. I managed to force reboot it with shaking hands lol. I was lucky, no permanent damage. I immediately flashed a stock rom to be "safe".

Anyway...i'm pretty sure that heat is NOT causing this. It has to be something else.

I'm using a D802.
[G2 General] :
best you feel if its warm/hot near camera, if it is let it cool down. perhaps flash something different first

it seems heat doesnt cause this, but lets not push your luck
[G2 General] simpsonr:
Wow, you are LUCKY. Those are prime conditions to get the dreaded black lines. Wonder what is different about your device.
[G2 General] ckyy:
Indeed i was. I nearly wet my pants when i saw the screen turn white.

I bought it in december 2013 from T-Mobile Germany. It's a LGD panel if that helps somehow.
[G2 General] simpsonr:
Weird. Those are ALL prime indicators of this issue and somehow you were spared. For now... anyway.
[G2 General] ckyy:
OP says that his screen turned black after being white. I managed to turn my phone off before it went black. Guess that's the reason why i was spared.