yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] nemolivier:
Sorry fot you, but it looks like you have the exact same issue I had two times, and other too : your screen is partially dead and the only solution is to change it. If your phone is still under warranty, flash the phone back to stock and send it to lg : the repair is totally free.
[G2 Android Development] MBurns2:
when you sent it to lg, Did you have the status "rooted" in download mode?

with root checker my phone is not rooted but in download mode i see "rooted". Thanks

Inviato dal mio GT-I9300 utilizzando Tapatalk
[G2 Android Development] cryptos9099:
Search how to untrip the Root counter... It's a pesky little bit of code that logs if you have rooted so the carrier knows if you have voided the warranty
[G2 Android Development] nemolivier:
I didn't checked that. It was more complicated than that in my case but it was a very specific one. Go to the specific thread you should find everything you need.

Black lines are not a ROM issue but since it can be linked to over heating kernel I guess flashing a new ROM can cause problem.

[MENTION=5188956]cannondaleV2000[/MENTION] maybe you could use another kernel for you builds ?
[G2 Android Development] Lawlrus:
What was your CPU temp when you flashed it and got lines?
[G2 Android Development] khjunior:
The gapps dowbload link bit work, where i can download??

Say in post #2 how can get gapps into the ROM, but can`t see anything un post#2
[G2 Android Development] Lawlrus:
Google 5.0 gapps
[G2 Android Development] michaelearth:
I can't seem to find the option to enable "Double-Tap to wake". Is this feature supported?
[G2 Android Development] tanvir1987:
my phone is restarting continuously from LG screen......

my phone model is LS980. ROM. Cluody G2 2.2 Recovery TWRP.

:confused::confused:
[G2 Android Development] dredq:
You accidentally posted in the wrong thread. Try this one http://xdaforums.com/showthread.php?t=2692223&page=542

There should be someone there that can help you. Sounds like you need to get into TWRP, and restore a backup if you have one. Good luck.
[G2 Android Development] Dr.Vaska:
viber call sound distortion

Has Anyone solved this problem???

D800
[G2 Android Development] Robshr:
I downloaded and did a completely clean flash but it won't boot I get the lg screen then the screen goes black than I can't do a restore because is changes my sd card all around luckily I have a back on ausb stick any idea how I can get this to flash and boot I'm coming from cloudys g3 ROM I'm on the vs980

Thanks Rob
[G2 Android Development] buffal0b1ll:
Been running this rom since 3/4 dropped. I've used blackbird kernel with init.d work around to dt2w from the start. Updated to 3/8 along the way, and stayed on blackbird.

This liquid is the fastest, stablest ROM I've ever run on this device. Battery life is the best I've had on lollipop.

So how do you make perfect even more perfect? Enter blackbird 3/16 with f2fs support. I clean flashed 3/8 with that kernel and data/cache f2fs today. Holy wow!

F2FS = fast 2 faster, Skippy
[G2 Android Development] jmccau1:
I'm running the exact same set up as you. Clean flash 3/8 build with 3/16 blackbird on d800. I'm trying to get d2tw working. I went to settings>performance>wake controls>dt2w fullscreen>apply on boot>reboot. Can't get it to work. Any suggestions? What do I need to do with init.d like in your post?
[G2 Android Development] TDSJR:
I got this one [MENTION=4831195]buffal0b1ll[/MENTION] ;)

Yes, you need to place that file in the init.d directory, and change permissions.

OR, you could flash a REAL ROM & Kernel. :D (Just kidding, inside joke. LOL)
[G2 Android Development] jmccau1:
Ah, duh. I'm an idiot. Thanks!
[G2 Android Development] TDSJR:
An idiot? Based on that? I doubt it.

Enjoy!
[G2 Android Development] buffal0b1ll:
You found the 0 file or the zip flash fix that [MENTION=5560321]TDSJR[/MENTION] referred to? Search buffal0b1ll in this thread and you'll find a link if you haven't yet.

Also, I use Synapse to tweak blackbird and deny native Kernel Tweaker root on my device. Was gonna uninstall kernel Tweaker, but denying root has been working fine for the last couple weeks.
[G2 Android Development] jmccau1:
Yeah, ended up using the 0 file. Thanks for the help!
[G2 Android Development] jesssiii:
This has RRO, not CM theme engine?

VZW LG G2
[G2 Android Development] cryptos9099:
Yes
[G2 Android Development] dredq:
Why use synapse over native kernel? Thanks for the info.

---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------

Why use synapses over native kernel tweaker? Thanks for info.
[G2 Android Development] buffal0b1ll:
If the kernel you choose supports synapse, you should use it. Dozens of options that native doesn't have.
[G2 Android Development] jpeterson:
LG G2 Verizon experieince

Just posting my experience:

I have been holding out for while so I finally gave it a try yesterday. I rebooted into TWRP wiped everything except the sdcard and installed the VS980 ROM (also gapps) latest nightly from 3/19 along with the 12B radio. Factory reset and cleared cache again just for good measure. Took a while to boot, but I have learned to just wait a while. Took about 5 min but it finally came up. Everything seems to be running great I had wifi connection, apps were being restored. On the lockscreen in the notification bar it had "NAM1" display and it went away after unlocking. I tested cellular service and it was working.

After several consecutive reboots it was the same. I rebooted into TWRP and cleared cache dalvik+ and rebooted. Again it too a while to boot but it eventually did.

MAN1 was still displayed on the status bar when locked. Rebooted. This time it started saying "No Service" on the lockscreen. I tested a phone call and wifi but those appeared to be working. still.

Next I installed B14CKBIRD Kernel to see if that would make a difference. Sure enough, it is now displaying Verizon Wireless in the status bar when locked.

I have paired bluetooth with my car, tested NFC, took pictures, made calls.

Very nice work liquid team. I am a convert.
[G2 Android Development] buffal0b1ll:
When you get No Service in carrier text on Lockscreen, just toggle airplane mode. That always fixes it.
[G2 Android Development] andreflex:
Hi guys,somebody can tell me if with this rom i can hear whatsapp's recordings without distortions? Because now i have the CM12 but this bug compromises the daily use....thx
[G2 Android Development] achapman91:
Just curious are you talking about the 3-9 nightly or are you finding a 3-19 build somewhere?
[G2 Android Development] Deeshizzle:
How do I disable the search bar from the home screen in this room? Can someone please help with this?
[G2 Android Development] CyrSyl:
Vertical black lines

0 - Backup actual 02/07 rom

1 - Install from recovery update 02/07 to 03/08

2 - Reboot

3 - Darkness (?!) LG boot screen ...

4 - ... into a grey/black screen (....!)

5 - Waiting

6 - Waiting

7 - Waiting

8 - ...

9 - 3 buttons method to reboot into recovery

10 - VERTICAL BLACK LINES !!!!

11 - Restore 02/07 backup : black lines still there

12 - Flash another rom : black lines still there

13 - Another kernel : black lines still there

14 - Another recovery : black lines still there

15 - Another beer : black lines still there ...
[G2 Android Development] L0nelyE4rth:
Meaning CM Theme ?

Negative, It's RRO Layers
[G2 Android Development] Deeshizzle:
Sorry about that. Flashed the wrong gapps on re-install and got the options for the the google now launcher. My bad.
[G2 Android Development] buffal0b1ll:
That sucks. Bad luck and cpu overheat cause the permanent lines. The best way to avoid them is to read the thread for others posting their black line bad luck, use blastagator thermally protected TWRP, and if others are complaining then use a custom kernel you've already used and trust. Others complained about getting black lines on that build a week or two ago in this thread.

I've clean flashed 3/8 twice with blackbird kernel and no issues.
[G2 Android Development] nemolivier:
With this number of people having the same issue (even if it's a known problem, with hardware link) it can't only be a "bad luck". I've wait fit this ROM but can't take the risk of burning my screen again ?

I hope Dev have answers about where the problem come from and how to solve it.
[G2 Android Development] KoolBurnX8:
I'm having some issues with GPS on 3.2 milestone, VS980. For some reason my location doesn't move at all while I drive and the pointer on my GPS app acts like i'm not even moving. Hopefully this gets fixed. Other than that, I love LS 4.4.4. So many features, smooth and stable. I can't do 5.0.2 because it lacks features, battery drains faster and charging time sucks. Can't wait until 5.1 is released on this rom.
[G2 Android Development] bolt890:
The new kernel that was included in the new RRO build has overclock capabilities and is overclocked by default, atleast on the build that i flashed. MAYBE that overclock is the root cause for overheat.
[G2 Android Development] buffal0b1ll:
This is exactly what I was intimating in my post above. Flashing custom kernel, though not necessarily supported by most devs, affords you a level of protection against potentially overheating stock kernels.

And this is gonna sound stupid, but last May many of us were doing it. After flashing, put your phone in the freezer for 3 minutes before rebooting system from recovery .

Last summer dr87 pioneered the thermally protected TWRP and kernel work for the G2 to protect users from black lines. We had all taken for granted that the problem had been eradicated (haven't used the freezer in ages), but I've seen users of 2 ROMs in last 2 weeks get overheat black lines.
[G2 Android Development] nemolivier:
I've personally many time put my phone on a freeze pack during first boot and setup/restore. And it may be a good idea to remove this huge cases that keep the phone hot...
[G2 Android Development] andreflex:
Have you d802 model?? I mean that when you receive a voice message on whatsapp and bring the phone to your ear the sound is distorted and incomprensible.

if you don't have this problem can you send me every file in your /etc/ folder that contains in the name words like "sound","audio",or "mixer"?? i would understand how to solve this bug for me and to give a contribution to the community because the bug is present in every AOSP rom,also in kitkat roms-

I don't know why but a lot of person in italy have this problem but i see that in other countries is almost absent.

sorry again for my english
[G2 Android Development] SAFAD:
So,

My phone screen is bricked for good ?

I used TWRP W/ Thermal, put the phone into freezer before flash, used the 0 boot file, synapse and still got the black lines.

Is this permanent or there is a fix ?
[G2 Android Development] buffal0b1ll:
You can read about permanent screen damage black lines in an xda thread in G2 forums. Search for it.

It sounds like you didn't use a custom kernel.

I wish the OP would weigh in, but I'll come right out and say it without beating around the bush. The stock kernel is suspect for overheating and causing black lines (another user said it's over clocked by default).
[G2 Android Development] SAFAD:
Maybe instead of people claiming that the fault is not in the ROM, maybe op should update the first post to include a warning about this issue, especially since its unfixable, you don't expect people to read 30+ pages of comments before installing a ROM...
[G2 Android Development] Lawlrus:
Maybe you send a letter to lg so they can include a warning on every single boot so people don't have to do research before they purchase the phone, as this has happened on stock.

You can't expect that disclaimer to be listed on every single ROM, just like you can't expect people to do research before they flash no?

Ultimately you need to take responsibility for failing to research before you decided to flash a rom.

Look at the first result from my google search. That's why google is around. Use it.
[G2 Android Development] ossito2012:
Pointless to even bring this up, go back and read post #84 thru #94, flashing this ROM (like any other I guess) is at your own risk, regardless of your history of flashing other roms, I was told "And one person bootlooped woopdi freaking do"

I would say be patient and wait it out until bugs are worked out. That was all said with restraint :D
[G2 Android Development] jinxmeistr:
GFE stopping on my S3 after liquidsmooth lollipop update

Same here - GFE stopping on my S3 after liquidsmooth lollipop update
[G2 Android Development] Cameron581:
This is cm theme engine....
[G2 Android Development] Dowork009:
Tester

If you still need a vs980 tester I am here to help.
[G2 Android Development] Cameron581:
Building d800 and vs980 now
[G2 Android Development] goast:
I'll test it out here in a minute thanks
[G2 Android Development] LidaFlorida:
Oh, I'm messed up.

Thought that the "• PRO Themer" is the "RRO":D
[G2 Android Development] ajgftw:
Update: D802 Installs/boots without a hitch
[G2 Android Development] Spakainz:
There is a bug. When I change recent button to menu...system UI crashes. Restored Bliss nandroid. D802
[G2 Android Development] bps119:
Why not provide a log before reverting? It's going to be hard to get issues like this fixed without them.
[G2 Android Development] Cameron581:
Choose the V4.0

http://www.drdevs.com/devs/teamliquid/?dir=Nightly/LG_G2_ATT
[G2 Android Development] ajgftw:
Can confirm the bug. I was able to replicate it. Bed time for me now, but if no one else has already done so I will grab a log tomorrow :)
[G2 Android Development] striker661:
Had the same bug. Makes the phone unusable. I'm on d801. I downloaded my apps. Everything fine. Changed the nav keys. Everyything fine. I even tested the nav keys. I swapped recents for menu and addes some hold actions for back, home, and menu. But soon as I opened up hangouts it started crashing and the phone couldn't be used. Even after reboot system ui crashed and I haven't seen the navbar since. Pretty nasty stuff.
[G2 Android Development] Cameron581:
Vs980 UNTESTED http://www.drdevs.com/devs/teamliquid/?dir=Nightly/LG_G2_Verizon
[G2 Android Development] Sgace:
Thnx for the rom! :thumbup::D

Will flash asap, but is active display really in there? If it is, this one is already a winner for me:D

Cheers
[G2 Android Development] Cameron581:
Ambiant display is, I didn't check the feature list to make sure its 100% accurate I just took the liquid template and rolled with it ?
[G2 Android Development] bleedingthru:
Will test vs980 file and report back
[G2 Android Development] analgesic:
Requesting D803
[G2 Android Development] Sgace:
Already realized that, thnx for your answer:thumbup:.

Would be cool tho, something like active display with pocket mode:D

The one thing i miss the most in LP.

Cheers
[G2 Android Development] HueyT:
All good on VS98012B. It's very fast and snappy. Everything works. No more roaming bug!!! Works fine alone or with Render's R6 kernel for LP with Synapse CPU control. Works fine with LolliViper4Audio. Restores old apps fine after clean flash. SMS/MMS, voice, data, 3G/4G/2G, APN, sound, Netflix, Pandora, Google Music, all work fine. Great job, Dev !!! :good::good::good:
[G2 Android Development] mykenyc:
I still get the Bluetooth WiFi bug on D801
[G2 Android Development] bps119:
D800 build working great. One bug I've found though is, when choosing LiquidSmooth Statistics in settings you get an immediate force close.

Let me know if you need a log. Thanks for bringing liquid smooth back to the G2!
[G2 Android Development] nemolivier:
So, no update since 030815 ? Must we move to slimrom ? Or other ?
[G2 Android Development] bps119:
Not sure why I'm even allowing this a response, but I'm sure they're working on getting 5.1 up and running. Have patience dude, it hasn't even been a month since the last build they gave to you for free.
[G2 Android Development] cryptos9099:
If you read the Gerrit (http://gerrit.liquidsmooth.net/), the Liquid team is prepping 5.1. But for us the progress is slower for us as devices outside of South Korea don't even have 5.0.x which limits the blobs they can use to JB or KK... Give the devs time... I'd rather have a stable, minimal bug-filed, fully-baked build than a semi-stable, bug-riddled, half-baked build.
[G2 Android Development] blakeatl:
I'm having issues receiving text messages on the LS980. I've tried using the default messaging and gosms, but neither receives the messages. I now that the texts are sent because I can go into google voice and see the texts there. Anyone know of a workaround for this?
[G2 Android Development] achapman91:
Since verizon released lp for the g2 today will the vs980 get a new rro build at all?
[G2 Android Development] Lawlrus:
Stock firmware upgrade doesn't mean anything less cm can do anything with the kernel
[G2 Android Development] skynet11:
Do you think the 39A modem might do any good for some of these ROMs if it was extracted?
[G2 Android Development] Lawlrus:
The radios really only control data speed, WiFi speed, and sensors.

So as far as battery life, ROM fluidity, stability, VoIP issues, ect.. that's all contained in the kernel and blobs used.

Until source gets updated past 4.2 kernel source, I doubt much will change with it being released.

Dr87 had to make kernel source work back with 4.4, jackpotclavin for the vz980 has done the same with a 5.0 kernel based off 4.4 and now 5.0, and it runs beautifully. Again, its a mishmash of sources to get it working, which kernel devs don't want to use, as they would sooner follow cm.

Lg source with it being closed source, has never played well with cm, and I personally don't ever count on it getting figured out. I hope I'm wrong, but it is what it is.

Hopefully 5.1 fixes some of the issues with have now with 5.0.2
[G2 Android Development] Unn113:
I think LG Devs were planning to port CM to 5.0 sources once they're released by LG.

Unn.
[G2 Android Development] Lawlrus:
Rashed has been working on it for quite some time now.

And reading my previous post, I don't want anyone to take it as disrespect. I know people are doing everything they can, and that sometimes kernel source just doesn't work well with cm on certain devices.

But yeah, once source is released for all devices, that's when they will really be able to take a good swing at it.

Seemed lime we got very close with upgrading the cm kernel to 4.4, so hopefully 5.0 will be a easier merge.
[G2 Android Development] dabug123:
So what's this I here that Ethan kernel is baking g2(eggs Bacon and toast)lol..Is liquid aware of such a rumor!
[G2 Android Development] dredq:
Can you format /system with F2FS with this Rom if you use a F2FS friendly kernel?
[G2 Android Development] buffal0b1ll:
No ROMs that support system f2fs exist to my knowledge, but you can format data and cache. I'm running that now.

My F2FS data and cache during a clean flash recipe (ASSUMES YOU HAVE A PC AND A OTG CABLE)

1.****** Update all apps in play store

2.****** Settings>storage>Clear all caches (this shrinks Chrome and G+--the biggest space offenders)

3.****** Delete all TiBU backups

4.****** Run all TiBU backups (this gets you one copy of everything so you have less to move)

5.****** Reboot to recovery

6.****** Run a nandroid

7.****** Plug into a PC

8.****** Mount>enable MTP

9.****** Copy the following sdcard folders to PC (plus whatever else you don't wanna lose) TWRP, TitaniumBackup, DCIM/Camera, Downloads, Music

10.** Plug your USB thumb drive into PC

11.** Move the following zips onto USB drive: ROM, F2Fs compatible Kernel, gapps, quickremote, supersu, UDK (render only), xposed

12.** Unplug phone from PC and reboot recovery (this will make it so mounting errors won't make you worry when you format things later)

13.** Advanced wipe, tick everything, wipe

14.** Advanced wipe, tick cache, format otpions change to F2fs

15.** Advanced wipe, tick data, format options change to f2fs

16.** Reboot Recovery (I always do this--not sure if it's realy necessary but it makes me feel good)

17.** Plug into phone the USB thumb drive OTG

18.** Mount>OTG

19.** Install from OTG: ROM, F2Fs compatible Kernel, gapps, quickremote, supersu, UKP (render only), xposed

20.** Mount>unmount OTG

21.** Unplug OTG

22.** Boot system

23.** Complete welcome setup

24.** Reboot recovery

25.** Plug into PC

26.** Mount>Enable MTP

27.** Move all your stuff back

28.** Mount>disable MTP

29.** Unplug from PC

30.** Reboot system

31.** Done
[G2 Android Development] Cameron581:
no it is not.
[G2 Android Development] Cameron581:
i was runningit for quite some time and never experienced that issue present, its a luck of the draw issue.
[G2 Android Development] Cameron581:
[MENTION=4831195]buffal0b1ll[/MENTION] i dont believe it was overclocked by default but then again i never use the default settings and end up screwing with them a whole bunch and forget what he had them set at....
[G2 Android Development] dredq:
This is a great post and would be helpful to people setting up F2FS for the first time. Would you think about cross posting this on Blastagator's TWRP 2.8.6.1 http://xdaforums.com/lg-g2/developm...f2fs-tools-t2898705/post59813078#post59813078 I think it would be really useful.
[G2 Android Development] John_0:
After flashing this ROM, phone don't work. Black lines appear. How fix it? Please help me. Sorry my bad english)
[G2 Android Development] buffal0b1ll:
You're the third or fourth one this happened to. If you'd read back a few pages you'd have seen that the stock kernel is suspect for overheating and permanent black line damage.

Google "xda permanent black line damage g2" to weigh your options moving forward.
[G2 Android Development] atifsh:
If you look yourself, you will find he is atleast 10th person.

Because when it happened to me and i told about it and got flamed, there were 3 or 4 on same day after me, and that happened long time back.
[G2 Android Development] buffal0b1ll:
Thanks for correcting my count, Grumpy. I live for constructive criticism.
[G2 Android Development] atifsh:
Haha naa im not grumpy, but i do believe unlike others that op should have a warning that some unknown reason can lead to black.lines with this rom.

Not all of us lives in cooler climates.
[G2 Android Development] ossito2012:
+1

I also mentioned this back in post #84 and was flamed as well, I thought the download link was removed but I guess not. The admins were quick to jump on everybody in the At&t Note 4 root progress thread but now....
[G2 Android Development] Lawlrus:
Its a good learning experience.

Teach them boys how to read real good
[G2 Android Development] Cameron581:
If you felt your phone getting hot then why didn't you go and undervolt or underclock? It should be at a users discretion to read before they do.
[G2 Android Development] nash211:
I had a similar issue with black lines, it was overheating, was under warranty so got it fixed for free, wasn't due to the ROM I thought ir was more the case I was using.
[G2 Android Development] buffal0b1ll:
I think what people are saying is that when they flash this ROM (with stock kernel) it overheats and they get black lines on the first boot, before they ever have the chance to underclock. With all the complainants it doesn't seem to be random.

That being said, I'm still parked on the latest build for near 3 weeks now. It is the best L ROM I've used on G2. I use Blackbird kernel and F2FS data and cache.
[G2 Android Development] atifsh:
nope i didn't felt any hotter than usual, that's what everyone concludes after few blacklines.

it was my first flash of this ROM and it booted fine, after i flashed that dt2w zip and reboot than i saw blacklines, and i forced shut right there and re flashed.

mine was cameback to life [no blacklines] as i said, after i re-flashed with than available other ROM in a zap.

still going fine with multiple ROM's.

i do add that what i have learned from this, i put my phone in front of a/c while i do backup / restores only, as this goes to 80 deg on twrp.

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

correction "with stock [ROM] kernel", i assume if you flash custom kernel right before first boot it will be a safe bet.