yashsingh1/xdaforums huggingface dataset:
[G2 General] :
well those red lines in op make heat definately muchmuch more likely. Compass your theory may be spot on.
[G2 General] Compass Linux:
To give proper credit where credit is due, there are some posts mentioning heat as the possible cause, but not from me (as in it wasn't originally my idea). One theory I put in the OP, but searching there are others too.

Good thinking everyone!

Compass.
[G2 General] NisseGurra:
https://docs.google.com/forms/d/1jpaVYANNn-Cg6Be_EZRJO0FaInzrRodWdHyaRllZ0sc/viewanalytics

This survey show different...
[G2 General] NicoC72:
Great, so now we really don't have possible causes outside of hardware that doesn't like heat. Based off what I have read, I'm going to say it's the LGD panels not liking the heat. Looking at the 15 responses to that survey I made, 13 people who got black lines had a LGD/LGIT panel. Of course 15 responses doesn't really make up a large sample size.

Could be heat messing with the power delivery system throughout the device, just the power delivery to the screen, or just the panel hardware itself.

Reference link to spreadsheet:

https://docs.google.com/spreadsheets/d/1WTeDaDGHOGh4XBZoIrl0MuGr6c8r5gchC6vNlenLrY0/pubhtml

And again, if you have black lines, PLEASE TAKE THE SURVEY! Having information like this is ALWAYS valuable to have around.

---------- Post added at 03:20 PM ---------- Previous post was at 03:11 PM ----------

Not entirely, remember so far it's only a small sample size. There is also 1 report of the black lines popping up while the phone was running hot, but it seems like an outlier as the user was the only one who got the lines while on CM11 and one of the 2 that did a dirty flash.

If anyone is rich, we could use like 20-30 G2's, split by panel type, then just run through some tests to see if we can end up with a true fire method to get the black lines. Then just go from there!
[G2 General] Compass Linux:
No, I like the G3's better! :D

We can get a kickstarter for that! :highfive:

I know, not a constructive post, but I had to say it!

Compass.
[G2 General] hassaan123:
Survey shows 1 victim from mahdi rom too :s I just got my phone repaired today, gonna stay with stock for now.
[G2 General] butler360:
Am I correct in assuming that a phone purchased on Swappa doesn't fall under warranty? :(
[G2 General] NisseGurra:
The strange thing is that this fault has showed up last month. I was one of the first to get in in may. So the cause must be some new stuff added in the latest roms.
[G2 General] Compass Linux:
I think the latest roms you mention accelerated a problem that was already there.

In OP: <+savoca> however pa's kgsl sh*t bumps the probability by like 200%

Compass.
[G2 General] Lawlrus:
The manufacturer themselves have a warranty.

Sent from my Vs980 running Vanir 4.4.3
[G2 General] ephumuris:
I had the problem in March! With my first G2.
[G2 General] :
manufacturers warrantee it should. Phones not a year on the market. lol
[G2 General] kolembo:
I disagree entirely.

Other way around.

The lgG2 feels sturdier, faster, lasts longer, takes better photos and has a lovely screen.

So, I disagree.
[G2 General] butler360:
I wasn't sure whether a receipt is required or something. Often when I try to make a warranty claim they ask for a receipt or invoice for the original purchase, which I don't have.
[G2 General] :
usually yes, cause products are longer on market and one cannot say for sure if its within warrantee period. Shops sometimes dont want the hastle if they didnt sell the product. So choose wisely and try another one. Sometimes you can check if there is a service centre from manufacturer.

In this case product is like not even year on market. I don't know exactly the law and legislation. But try it anyway.
[G2 General] butler360:
I have no problems currently, but I've been on this old PA for a while now and I want to update but I also don't want the lines. Although now there's reports of the lines on stock so I guess no one is safe! That's why I am curious about warranty on a used phone.
[G2 General] elander:
Hi, I don't know if anyone has mentioned this before, but as far as I have read, most (if not all) of the cases have happened while running some sort of KK build (both stock based and AOSP based) so, could it be something in the new KIKAT BaseBand? because it's just too big a coincidence that everyone's G2 decided to get the "too hot to work" attitude all of sudden and on different ROMS. Might be worth a shot taking a look at it.
[G2 General] DREWHAMM974:
Nope no autorec when it happened. Happened directly after OTA
[G2 General] bps119:
Mine was in February and another user reported it before me
[G2 General] NicoC72:
Sadly it's not that simple. If you take a look at the spreadsheet of results for the survey in the OP, at least 1 person was on the 4.2 modem and a ton of people didn't even flash a different modem. Not sure what the AOSP rotation modem is based off of, I'm guessing 4.2?

Most of the cases involve the LG panels, so it just seems like a hardware problem that can only be 100% fixed if LG issues a recall and changes the faulty hardware out free of charge under warranty.

This problem has been on going it seems, at least for the last few months. It's just as of late that more people on XDA have been reporting it to the community. I just can't find a connection between the screen failures and the ROM's that are "causing" it. If it is a purely hardware issue, its just a coincidence that the screens are failing while people are on PA, otherwise we should be seeing problems on Mahdi and the Cloudy ROM's, but for the most part we aren't.

For now, I think its either a commit in the AOSP source code and/or heat not playing nice with LG panels. Heat might be triggering it, but not the root cause, who knows. Hell, I know the kernel has some sort of thermal controls, maybe something is messed up in that.
[G2 General] dr87:
Doing some more research on this I believe the way we are booting 4.4 on the 4.2 boot loader could be causing a huge issue (as houstonn mentioned before we are using the old bootstack and having to trick the aboot into booting the new kernel - which we believe is very important)

I think a possible cause may be coming from the way we boot up https://github.com/dr87/SimpleKernel/commit/1c04dda1c03021d3bba43632e61a79460ef96a59 which was authored back in the days when we first got 4.4 kernel booting.

Now I am not an expert on the bootloader but if we are blanking out the follow commands "qcom,mdss_dsi_lgit_video,qcom,mdss_dsi_lgit_cmd ,qcom,mdss_dsi_jdi_video,qcom,mdss_dsi_jdi_cmd"

Is the aboot actually pulling the correct info? I know that if you look at the actual info DTS panel info that the aboot is looking for it contains some sensitive information like clock rates. Different variants use different clock rates (D802 uses 919 while sprint uses 893, etc) and I am not sure if they are actually being detected correctly if we are inputting blank lines for the aboot to read. Jackpotclavin may know more about that.

Secondly, we are forcing the panel command line instead of having it auto detect like it did back in 4.2 which can cause problems.

The issue with this has already been seen not too long ago when it was found out that there was not only "mdss_dsi_g2_lgd_cmd" but a mdss_dsi_g2_jdi_cmd.

I found there is possibly another G2 screen the aboot can auto detect, the B1 revision of lgd variant. Everyone who currently has that B1 screen revision is being forced to lgd by the command line.

Now if we could possibly work around the fake aboot commands to get the correct command line / aboot info detected by itself it would be a very good thing. I think this could be done without the new aboot as it was automatically being done on our old kernel just a matter of figuring it out.
[G2 General] Homegamer:
Vertical Black Lines..

Well, a few days i ago I charged my phone. When I took it off I had those nasty black lines..

I was running Paranoid, but I didn't think my custom rom could cause that!

Well then, I returned to stock (had a hard time doing that!) and I sent it in a few days ago.

I will keep you informed if they repair it, because i still have warranty!

Kind regards,

Homegamer
[G2 General] erto90:
thanks for the reasearch and the found, got a question:

how i possible if we have b1 version of the panel? and again, b1 is safier or the contrary?
[G2 General] Compass Linux:
I've done a small cleanup of the OP, but I don't think it can get much smaller without leaving information out of it. I don't want to use external links (pastebin comes to mind). Let's see how it goes.

In the meantime I've added the following text below to the OP. I'm open to opinions:

Compass.
[G2 General] NisseGurra:
So the unset parameters could fry part of GPU or screen drivers?
[G2 General] simpsonr:
I'm having a hard time thinking the black lines issue is due to heat related stress. I hadn't heard about it at all until it happened to my device and then Bam! the issue was cropping up all over the place. It happened to me specifically when I updated to a new rom/kernel build... one that had modifications that other folks who had gotten the black lines also had updated to.

If this wasn't some sort of systemic kernel/rom/software related thing, the lines would have been appearing on folks' devices ever since it was first released.

The big question for me is: when is it safe to go back into the water, now that I have a fixed device.
[G2 General] DREWHAMM974:
It happened to me months ago just taking the KK OTA. It also happened to Autoprime (if you don't know he is very respected in the Android community) while completely stock. He was using adb and when he booted to STOCK recovery it happened. It's happening on completely stock devices man. Those commits may make it more likely to happen BUT it is obviously something with the hardware.
[G2 General] simpsonr:
Well, it's damned weird is all I can say.
[G2 General] NicoC72:
So the problem is there is a 3rd display panel that no one knew about? And if the command line is forcing the phone to use the LGD config, is that why most of the responses to the survey have been LGD/LGIT? The 3 JDI responses account for such a small portion of the total responses that they could be ruled as outliers. Sorry if I misunderstood your results, I'm not very clear on how the bootloaders and stuff work.
[G2 General] HueyT:
Ice pack before flashing?
[G2 General] michaelr97:
i can't decide

my question might be a little of topic but i really need some help deciding: Nexus 5 or G2?

I really have to decide quickly and i almost ordered the G2 but then I've stumbled across this thread.

My plan was installing a custom ROM on the device (i guess cm11) but now i don't know if it's safe to do on the G2.

so the question is whether to get the G2 or just go safe and get a N5?
[G2 General] Compass Linux:
Nobody knows.

We do know the screen panel is being damaged, but not if the fault is there. If it is and yours is fixed, you're ok, but we know so little about this that it isn't verifiable yet.

There aren't any reports yet of G2's with replaced screen panels getting black lines. I hope it doesn't happen.

Compass.
[G2 General] Compass Linux:
It would be best to ask here.

If you want to avoid the black lines problem without nightmares, don't buy the G2. Be reminded that the Nexus 5 might have problems of its own (I don't have one, so check its own Forum in XDA).

Compass.
[G2 General] aldaris565:
so the possible causes are not confirmed yet? now i'm a little afraid... i was on cm11 and now on omnirom and my screen is fine...but now i'm afraid of charging the device.. do u recommend going back to stock?
[G2 General] erto90:
Also the nexus 5 got that probem

I read that in some g+ community

maybe is less common there
[G2 General] jal3223:
I'm curious about the reoccurring probability as well. Has anyone who has gotten their screen replaced started flashing custom roms again (as they appear to increase the rate of the issue)? It seems if the panel hardware is to blame, these unlucky devices will continue to repeat the damages. Or maybe the replaced digitizer solves the problem. Just hypothesizing here.
[G2 General] Compass Linux:
Without knowing the problems origins, it's impractical to give good, solid suggestions. I'll tell you this though. Looking at the Survey results there are far less Stock ROM users being affected, but you might also want to consider the other numbers too. In the end, it's up to you.

You will have to charge your device anyway at some point.

Can anyone confirm if USB charging heats less the device, instead of using the power adapter/charger?

I hope the replaced digitizer solves this for good too.

Compass.
[G2 General] aldaris565:
oh well then i will go back to stock anyways...btw my phone doesn't heat even a little while is charging on my laptop or ac... not even when i'm flashing a rom... plus i flashed a lot of roms while the phone was charging..
[G2 General] fordmanck:
I restored my stock rooted ROM I was on before I flashed and got the lines. The only thing I've flashed has been kernels.
[G2 General] Compass Linux:
It confirms this post. You might have flashed a kernel with those commits that have been known to trigger this issue.

Compass.
[G2 General] lacus:
Usb charging indeed heats less, but will take forever to charge to full
[G2 General] LenAsh:
The USB charging rate is limited to 450mA - the maximum a USB 2 port can provide is 500mA, so all phone manufacturers stick to a sensible limit.

The STOCK wallcharger charges at 1250 - 1350mA - which should yield a charging time of about 2 to 3 hours.

Therefore the power management IC and the battery will get very warm. If a kernel has some hideous "fast charging" facility (that actually works) then the heat produced will be rather more. The battery has a thermal sensor integrated within it - this should throttle the charge current if the battery exceeds a prescribed level. Kernels may be able to override this too.

Also note that the CPU is thermally controlled - this CPU is thermally bonded to the chassis/frame. This frame also carries the LCD...

Again, kernels can ignore the thermal CPU throttling, exaggerating any heat build up.

My own panel (HW Build 1.0) is a JDI panel, fortunately. I trust them! However, the problem may be the panel driver rather than the panel. the LG and JDI panels have different driver devices in all probability.

My tuppence. .
[G2 General] generaldizzle:
Have Sprint variant... Flashed EOS also.. got lines after 2 minutes in rom.. Rebooted got the red tint on the LG logo. Restored backup from twrp of superg2... No lines so far but I hate this rom... i wanna use asop!!!
[G2 General] reas0n:
I think it's not the fault http://xdaforums.com/showpost.php?p=53279469&postcount=592

Omni is on 4.2 sources, the issue still appeared to him.

Btw, I'm still changing ROMs like socks and don't have any issues, strange
[G2 General] Matze060906:
Hello and sorry for my bad english. I have a international D802 and I want flash the latest nightly of cm11. If I have white (black) lines after flashing, what can i do? Sent it to a repair service? Did I have to pay for the repair? Or will they repair it for nothing because warranty?

Gesendet von meinem LG-D802
[G2 General] LenAsh:
I've been flashing CM11 for 4 months and Stock (I have 2 d802s) and never had an issue. Both have JDI panels.Your choice.

Why this has (apparently) cropped up now is strange...
[G2 General] Matze060906:
I don't have jdi panel, I have the other one. I have tested it with a app here from xda. I need to know if i sent it to a repair service will they repair it because warranty or do I have to pay for it?

Gesendet von meinem LG-D802
[G2 General] dr87:
Yes I am aware it can happen on 4.2 as a screen fault, however the amount of cases has exploded since 4.4 and this can't be ignored. I do not believe age has anything to do with it.

Everything currently is just a theory, nothing is 100% confirmed. Heat can damage anything so this goes without saying.
[G2 General] Bugox:
Hey everybody,

something changed with my lines today. Apparently the liney decided to change to a bright white during the bootanimation and LG-Screen from time to time. Afterwords they were back in black but that didnt happen for quite some time.

And i got a new black line today. It was pretty warm outside (35degree or 95 degree fahrenheit), went to the park and spend some time in the sun while listening to a podcast. And I noticed a new black line....

Lg wants me to pay for the repair, because i have a crack on my screen...so....yeah....
[G2 General] Jank4AU:
Come on guys, it's all good. I'm sure the ROM will be back up before too long. If Houston can get it narrowed down to specific commits and remove those, then maybe it's all worth while. There were quite a few people with borked screens and not everyone is in a position to be able to either afford a replacement or do without. Just trying to feel their pain too. Personally I love the ROM and have zero issues with it.

I just want to know this: if it's a ROM issue, then why isn't it happening to everyone, or even everyone on the same variant? If we are all flashing the same ROM, why don't we all have lines and broken displays?

Edit: we should also know what recovery everyone was using, whether they just flashed the rpm/tz zip or if they came from an official KK.
[G2 General] Compass Linux:
It is a great ROM, but I suggest not to upgrade anymore until the origin of this bug is found and marked resolved. Since it has been present in other ROMs and we don't know where it came from, how can we be sure which ROMs are safe to flash?

Compass.
[G2 General] Compass Linux:
One possibilty is that some screens (or other part of the hardware that is screen related) are more susceptible to some modification that was done in Paranoid Android (and also other Custom ROMs). We don't know the origin of this yet. When we do, it might become clear why some got affected and others not.

Compass.
[G2 General] wendellp601:
I had been on Beta 7 for a couple of days before my D800 developed black lines on the right hand side of the screen.

They showed up immediately during / after a reboot when I took the PA OTA for their latest GAPPS.
[G2 General] Compass Linux:
So a OTA for only GAPPS gave you this issue?

Compass.
[G2 General] Jank4AU:
If it only happens or manifests on a boot, maybe there's something in the power levels being sent to the screen digitizer...
[G2 General] wendellp601:
I don't know

what

gave me this issue, but like I said earlier, the lines didn't appear on my screen until I took the GAPPS update from the PA OTA.
[G2 General] autoprime:
as mentioned by [MENTION=3130300]Jank4AU[/MENTION] above... it would be good to get more specific info from everyone.

in addition to which rom/gapps used...

1. which recovery was used... cwm? twrp? what version? did it come from autorec, freegee, twrp site with manual loki patch? etc etc..

2. which modem was used... official jb(which build), official kk(which build) or a modified modem(which one?)...

3. which tz/rpm combo are you using... official jb(which build), official kk(which build)? and is this tz/rpm combo for your device model or was another variants used?

4. which touch panel does your phone have?

[B]adb shell
su
cat /proc/cmdline[/B]

should give you a line of code... in mine i have: mdss_dsi_g2_lgd_cmd
ldg = LG panel.
jdi = Japanese panel

without as much info as possible.. it could be a mess trying to sort this out.
[G2 General] bps119:
I found the post I made over on the slim thread when this happened to me. http://xdaforums.com/showthread.php?p=50464160

It would appear that my memory had failed me and that [MENTION=3130300]Jank4AU[/MENTION] may be onto something with his theory of power levels. After reading my post again, mine happened outside of a flash/reboot combo, but rather I had flashed the rom, booted and set up everything, charged up and rebooted after fully charging and unplugging the device.
[G2 General] Jank4AU:
What else is freaky-deaky is that all the panel issues are at the borders or near the edges. Haven't heard anyone or seen screen shots of it happening smack in the middle.

Edit: that leads me to believe it's a hardware issue causing them to fail in the same place because of a problem during production.
[G2 General] bps119:
I also found this post from a user that said he had the issue and contacted LG who indicated that they've had a bunch of devices returned for faulty displays. http://xdaforums.com/showthread.php?p=50487005

Whether it's rom related or not, I think it's fair to say that the op should edit the original post and thread title to ensure that no unfair blame or stigma is attached to any particular dev or rom. It's quite apparent that this has occurred while using at least one other rom by a different dev so calling out houstonn like that is a bit unwarranted.
[G2 General] Jank4AU:
Is anyone getting damaged screens on stock based ROMs?
[G2 General] Compass Linux:
Whenever this issue has been pointed out I've added it to the OP.

Unfortunately I cannot change the Thread Topic Name.

Thanks for adding more information. I will submit to the OP.

Compass.
[G2 General] Jank4AU:
Why can't you change the thread name? Edit the OP and go advanced; that will open up the title for editing.
[G2 General] Compass Linux:
Thanks.

Since I read more than write, I didn't know that. :D

Compass.
[G2 General] Elroyy:
Same thing happened to me. I just accepted the PA gapps update. Beta 7 was working fine for me.
[G2 General] bps119:
Maybe just change it to "permanent screen damage issue" since, at least in my case, it didn't occur while flashing at all. Simply a reboot was what triggered mine.
[G2 General] Compass Linux:
Done.

By the way, it was flashing that triggered your problem. The effects of flashing came only after rebooting, or am I wrong?

Compass.
[G2 General] bps119:
No, I'd been running the ROM for most of the day, I had flashed, rebooted, set everything up, played around with it to find bugs, and set it on the desk for a charge. After it fully charged, I picked it up, unplugged it, rebooted, and blammo, jacked up display.

I really think that jank is onto something with the power being distributed issue.
[G2 General] Jank4AU:
This issue has been reported in the new EOS ROM and the user said he never flashed AOSPA: http://xdaforums.com/showthread.php?p=53069790

In their OP they even go so far as to blame PA if you have any screen problems from flashing their ROM. About to post over there asking them to fix their OP as well.
[G2 General] Ibanez33:
I'm on my second of two LGD panels on a D802 (no black lines on either I dropped the phone)

However on the first panel prior to dropping it the phone did get extremely hot, still no black lines but since then something became unbonded (possible part of the back light ) and I was left with a feint yellow patch on the lower left of the screen.

The second one hasn't been subjected to that heat thankfully but it did what others have described on the first boot where the screen looks all grey on the lg logo and fades it rebooted. so far fingers crossed no black lines.

not debunking the heat theory just adding my experience.
[G2 General] daryelv:
The Stock ROM has temperature controls built-in. I'm in an area of California that hits 110+ regularly and when using my phone (D800) outside the software will drop your display brightness WAY down if the phone temperature rises above a certain point (and it displays a notification). It's a self-preservation measure. I'm not sure if the AOSP based ROMs (or maybe custom kernels) do that.

I just read that someone on the Omni ROM got the black lines... that's a JB ROM, so this truly isn't a "KitKat" issue, I think it's exasperated by running KitKat possibly producing more heat. Maybe the kernel devs should look at tuning the heat protection to engage at lower temperatures.

-Daryel
[G2 General] darkboy654:
it´s true!

OMNI is out of safe list

http://xdaforums.com/showpost.php?p=53281084&postcount=601