yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] Plesk8:
Can confirm the charging issue. I drive for UBER so my phone screen, GPS, and UBER App is sometimes on 10 hours straight. I do this often so the circumstances are very repeatable and I know them well. On Friday evening with the 3/4 ROM I lost about 1% every 20 minutes or so (doesn't keep up with my power usage) Where the exact charger setup and exact apps and usage patterns yielded a relatively fast charge on the CM11 ROMs (20-30% additional battery charge each hour while plugged in and using the same stuff: screen, apps, GPS, etc.) My charger is a 1A / 2.1A dual-usb-plug car charger. I am using (and was always using) the 1A plug with nothing else plugged into the 2.1A plug.

I would imagine this is some kind of kernel setting that will get updated with the new KDZ. I'm hoping it's soon in case I set out to drive for many hours and forgot to start with a relatively full battery.. I may be pushing it :-\
[Verizon LG G2] Jojo85-83:
I've had that happen a few times in the past on older builds with my LG HBS750 headset but a reboot would usually help. I haven't had it happen lately and I just tried with some skull candy wired earbuds and they seem to function like they should.
[Verizon LG G2] xI mEzMeRiZe Ix:
A reboot fixed it. I could've sworn I used my car bluetooth to Play/Pause over the weekend, which was why I was so confused when this happened with my headphones.

By older builds, are you referring to older builds of JPC's CM12?
[Verizon LG G2] Jojo85-83:
Yes, it's been a while since I can recall it happening on JPC's CM12 and I think it was with the stock music app, but I remember it happing more in the past on other LP Roms. I am currently using Spotify and Apollo music player with no problems and I use my BT headset daily.
[Verizon LG G2] xI mEzMeRiZe Ix:
I use Pocket Casts and Google Music. Worked for them over the weekend, then today didn't work until I rebooted.
[Verizon LG G2] Jojo85-83:
Glad to hear a reboot fixed it. I'm not sure what caused it I just remembered rebooting working for me.
[Verizon LG G2] Nafon:
Wasn't it brought up previously (or maybe in another thread) that the amperage is lowered if the phone gets too hot? I have had zero problems with my 2.1 amp car chargers and the stock LG wall adapter (all measure about 1.6A). Although I haven't used navigation and other intensive tasks while charging.

---------- Post added at 01:42 PM ---------- Previous post was at 01:37 PM ----------

I have no issues with mine. Holding the button when unlocked brings up voice search and tapping pauses and plays music (even when phone is locked and the music app isn't running).
[Verizon LG G2] Plesk8:
Definitely not related to heat. I'm glad you're not experiencing it. I think it may be a combination of what kind of chargers are used and when people charge their phones, and how much people paid attention to charging times before and after the switch from CM11 to CM12, etc. Considering I've been using Nav while on the car charger ALOT I noticed this immediately, there's no question for me: Suddenly after switching ROMs the difference was clear. There have been a few people confirming this issue I just wanted to add myself to the pile of people have a noticed the stark difference in charging between CM12 and CM11. Given the consistency of my circumstances (I'm not suddenly overheating) before and after moving from the CM11 to CM12 version of this ROM, I'm 100% convinced the CM12 ROM is handling charging differently for me - it feels like its using a "safer" more restrictive algorithm by dropping the voltage coming from a charger if its above some threshold.

My old Galaxy Nexus had a custom Kernel (LeanKernel) which enabled USB Fast Charge - this was super nice because it would allow use of chargers higher than a certain threshold (.5A or 1A?) without the phone chopping the voltage and giving a slow charge. My old GNEX could actually keep up charging in the car with that kernel tweak. I suspect a similar Kernel setting is at play here on my G2 with the CM12 ROM, and whenever we get some updates it may suddenly fix it. Or Perhaps JC has some ideas.
[Verizon LG G2] stelthy77:
I have been running the 3/4 build for 5 days now, and thought I would post some issues I am still having:

1. Bluetooth says it is connected in the live tile, even though it isn't. A reboot fixes it or a cycle of Blutooth on/off.

2. Bluetooth media controls don't always work (same problem reported above). It seems that for me Google Music always works as intended (for me). Pandora won' t work when Pandora is open on screen or when in Navigation, but works fine when on the home screen. This one is weird.

3. I have had a close of programs and redraw issues happen when trying to listen to Pandora and use Waze for several hours during a long drive, a reboot resolved it.

4. Same problems charging as several others here when using my 2.1A car charger while using Pandora and Waze at the same time. The phone looses power (not a lot, but it doesn't charge). It previously charged correctly with CM11. My LG charger charges it fine and quickly at home.

5. Battery life issues are still plaguing me. If i let the phone just sit for 8 hours, I lose 6% an hour battery, with no screen on time. The major culprit is Android OS (with hours and hours of Keep awake) and to a lesser extent, Android System and Google Services. Not sure what this is, but it is VERY frustrating. BBS and WLD are of no help, not really identifying that there is anything wrong with any one service or program, besides no deep sleep happening....

IN no way am I complaining, this is very stable and a great overall rom. Much better than stock. I just want to report issues, so that if possible, they can be fixed.

Thanks again JPC.
[Verizon LG G2] ThatKidDrew:
HD Voice support that me and a few other people were talking about will be supported in android 5.1!

MODEL: VS980 ?

ROM: LiquidSmooth ?

KRNL: B14CKB1RD ?

RCVRY: TWRP 2.8.4.0 ?
[Verizon LG G2] joedajoester:
I don't believe this will make it magically work on our phone. JP would still have to work his magic to get it working specifically for our phone. 5.1 may add support on the software level, but I believe it's still up to JC, if he's up to it, to make it work. Again, this just what I think, and I'm not a developer or anything so there's a chance I'm wrong.
[Verizon LG G2] koftheworld:
[MENTION=3727492]JackpotClavin[/MENTION] it looks like all partitions from 39a are available due to the new lollipop root method http://xdaforums.com/showthread.php?p=59336740
[Verizon LG G2] xI mEzMeRiZe Ix:
No rush, but I'm really looking forward to the 5.1 update. I can't multitask at all on 5.0.2. Listen to Pocket Casts, open Chrome, load a website, and Pocket Casts stops completely. I have to constantly make sure my recent apps are cleared in order to mitigate this.
[Verizon LG G2] rockcipher:
I'm running the 3/4 build (dirty flashed over the previous build) and use both Pocket Casts and Chrome... I have no issues multitasking. Perhaps clear the data on both Chrome and Pocket Casts?
[Verizon LG G2] xI mEzMeRiZe Ix:
It just happened with Google Music, an app that started fresh when data was cleared for flashing the ROM. Opened up Google maps and it stopped playing. Started it up again then loaded Chrome to post this comment and it stopped again.
[Verizon LG G2] HueyT:
Delete any Equalizing apps like AudioFx.apk in \system\app or \system\priv-app and reboot.
[Verizon LG G2] xI mEzMeRiZe Ix:
Does that include Viper?
[Verizon LG G2] xI mEzMeRiZe Ix:
Went ahead and cleared out the Viper stuff I flashed. I'll report back tomorrow after I've tested things out a bit.
[Verizon LG G2] JackpotClavin:
Okay, so you're in fastboot mode. Get fastboot for Windows and then download the aboot and recovery.lok from the OP, then use the command

fastboot flash aboot aboot.bin

and then

fastboot flash recovery recovery.lok

Then boot into recovery using the button combo
[Verizon LG G2] kmcrane:
I did that exactly before using command prompt. but it just says waiting for device.

so i must not have the right drivers for windows to see my phone in fast boot. I have multiple drivers installed. I will try uninstalling all of them and reinstall a set of drivers.
[Verizon LG G2] JackpotClavin:
See if you can run the fastboot.exe as administrator or something. I have never done stuff with Android using windows, so I'm not the best person to ask. Anyways it is definitely recoverable once you get fastboot up and running
[Verizon LG G2] da_reeseboy:
Anything showing up in device manager?
[Verizon LG G2] koftheworld:
There is a recommended driver tool in the galaxy nexus toolbox thread to delete drivers
[Verizon LG G2] kmcrane:
Drivers deleted.

when I plug the phone in it just says "Android" installing drivers then it fails. and I get the yellow sign and exclamation point on my device in device manager.
[Verizon LG G2] justinglock40:
Any confirmation of bluetooth working on the latest CM11
[Verizon LG G2] steveo17:
Jackpot Calvin says it should. I haven't tried yet though
[Verizon LG G2] koftheworld:
You need to reinstall the standard VZW lg g2 drivers. Check the roll up thread for a quick link.

---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------

It's on lol which is better than it was before. I haven't tested yet though maybe tonight.
[Verizon LG G2] wryun:
Anyone having issues playing songs in .m4a format? I've never had issues with any other ROM except this one.
[Verizon LG G2] Dri94:
[MENTION=3727492]JackpotClavin[/MENTION] what files were replaced to get this working?
[Verizon LG G2] kmcrane:
SUCCESS! i had to find some crazy driver on google. but fast boot works and i flashed the 2 files. what is the "button combo"?

edit: lol power off the device, and then power it on holding both volume down + power. As soon as the LG logo comes up release it and immediately do the same thing again and hold them down. It will bring you to a reset screen and you hit power 3 times to reboot into TWRP.
[Verizon LG G2] da_reeseboy:
Entering recovery via button combo -

Turn off the phone, then press and hold power and vol down. When the lg logo appears, release and re-press power (while continuing to hold vol down). Continue to hold power and vol down until the factory reset prompt appears. Press power button twice to confirm factory reset, which will boot into the custom recovery if you've installed it.
[Verizon LG G2] kmcrane:
in recovery!!! Familar teritoy. I'll flash this becasuse i don't know what else to flash. I'd like stock 24a with twrp and linaro kernel. but I'll take a phone for now! thank you everyone! too many to name. I am truly in debt to many on XDA!
[Verizon LG G2] cheami:
There is a flashable 24A on these forums. Flashed it to just activate GPS. It worked flawless for the few minutes I used it for.
[Verizon LG G2] kmcrane:
i am on this cm for now. i'm happy my phone is working. I'll try to get back to stock 24a later. I'm stuck at my phone not being reconized by the computer in download mode. maybe i'll try the flashable version since i'm up and running.

GNEX spoiled me with unbrickability, I was definatly sweating this one. thank you again everyone.
[Verizon LG G2] cheami:
The issue with the download mode is quite recent. http://xdaforums.com/showthread.php?p=51656508&#post51656508

Basically do the same things you did with the aboot/boot/recovery to get CM11 in the first place, then download mode will continue to work.

Edit: It is under 6b in the OP of this thread (not the linked thread in this post) for the step by step process.
[Verizon LG G2] justinglock40:
It does indeed work. Tested in my car and with my fitbit flex BT is good to go on latest CM11 build.

---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------

I wonder do they have any plans to bring other ROMs like PA, Omni, or Mahdi? Or maybe they're leaving it for those respective devs to do?
[Verizon LG G2] tacosrdelicioso:
Because cm11 is built with caf it is easier to get it booting with our caf 4.4 kernel. Lg decided to build our kernel under caf. Currently, nobody has gotten our kernel sources to boot on straight aosp. I'm sure they'll figure it out soon though
[Verizon LG G2] Benny879:
Does wireless charging work with this build?
[Verizon LG G2] soapinmouth:
Audio cuts out in bluetooth in the car when using certain apps. Switching my cars bt between radio and bt usually fixes it without a reboot.

---------- Post added at 04:39 AM ---------- Previous post was at 04:35 AM ----------

So I can flash the 39a bootstack with this rom? As long as I flash the 12b bootloader?
[Verizon LG G2] HueyT:
This rom needs 26A bootstack/bootloader which is has a JB bootloader and 26A modem/baseband/radio which also works with KitKat based stock/CM/AOSP roms

12b modem is needed for other non-jackpotclavin's AOSP/CM LP roms for VS980.

39A bootstack is meant for MicroMod's stock, debloated, rooted LP 39A rom and not for this rom so I doubt it will work.

Bootstack has bootloader + modem/radio/baseband in it.
[Verizon LG G2] TheUnladenSwallow:
Theoretically it could work. Someone could download the 39a bootstack and the 28a one and if it doesn't work just flash back. It'd update you to 28a in the process, plus they both have blastgator's latest twrp.
[Verizon LG G2] HueyT:
CM12 by JC needs 26A bootstack to work as it has JB bootloader. KK bootloader in 27A, 28A, 39A bootstack will cause security boot error. I just tried 39A, 28A, and 27A bootstack and this is confirmed. :highfive:

Now you can flash 27A, 28A radios without issues as long as you have 26A bootstack underneath as it has the JB bootloader. :good:

39A radio will boot with 26A bootstack but the cellular signal will go in and out every second so useless together.
[Verizon LG G2] TheUnladenSwallow:
Right, jackpot hasn't released a bump compatible build yet. Sorry, totally forgot. Next build then.
[Verizon LG G2] steveo17:
So has anyone let the phone die completely? When mine does I plug it into thy charger, wait a few minutes and then try to power it on. It just boot loops at the LG logo. I have to actually boot to recovery and then have that reboot to system.

Anyone else experience this?
[Verizon LG G2] jesssiii:
Never in my life let a phone die completely.

VZW LG G2
[Verizon LG G2] stelthy77:
I have had this happen before, just let it charge for a 10 minutes or so (depending on your charger) and it should boot up normally. The processor and memory usage during startup is draining the 1 or 2 percent of charge you got in those few minutes, faster than the charger can keep up. Recovery uses little to no juice to load in comparison.
[Verizon LG G2] JackpotClavin:
I'm self-testing a new build based on the 39A Lollipop build. All proprietary /system files are from 39A, as well as the 39A modem (all thanks to [MENTION=2941286]xdabbeb[/MENTION]). If things go well, all future builds will be based on 39A, meaning that you'll have to flash a 39A bootstack, and have a KitKat or Jellybean aboot image (for Bump)
[Verizon LG G2] ThatKidDrew:
Is there such thing as a lollipop aboot?

MODEL: VS980 ?

ROM: LiquidSmooth ?

KRNL: B14CKB1RD ?

RCVRY: TWRP 2.8.4.0 ?
[Verizon LG G2] JackpotClavin:
There is an aboot for every version, but the KitKat and Jellybean aboots are exploitable (in a good way) so they can run custom boot images for ROMs. The Lollipop update patched the aboot exploit so we can't run custom kernels unless we use an older aboot
[Verizon LG G2] Lawlrus:
>implying exploitation is ever bad
[Verizon LG G2] ThatKidDrew:
Is it possible that an exploit for the lollipop aboot will be found? How much does the aboot really matter? Sorry if these question are too much lol I tried to search google for more info on what an aboot even is and not much came up

MODEL: VS980 ?

ROM: LiquidSmooth ?

KRNL: B14CKB1RD ?

RCVRY: TWRP 2.8.4.0 ?
[Verizon LG G2] koftheworld:
And I'm guessing this build is absolutely perfect lol
[Verizon LG G2] sunkim50:
It's an "alpha" build. ;)
[Verizon LG G2] Lawlrus:
Possible? Sure, anything is possible.

But lollipop blocked bump.

Kitkat blocked Loki.

But we still have download mode.

Its going to be ****ty for people that get the phone already on lollipop, having to kdz and all, but with that relatively easy way of installing a recovery and rooting, I'm not sure many people will want to spend hundreds of hours finding an exploit.

There's a thread that was made of a way that supposedly roots on lollipop, or should, or something.

I was linked it in a dev hangout I'm in, and someone linked it in one of micromods new threads, if you're really interested in reading up on it.

I didn't really read the thread myself.
[Verizon LG G2] joedajoester:
Fantastic! I don't think performance can get much better from this SD800, but certainly the slow charging issues and a few other minors should hopefully be fixed. Now that its using the proprietary files from LG, could this mean mi2cam will work now ( it always throws an error about not supporting the kernel)? Also is there any real benefit to having proprietary system files, what do other roms do without them lol. Thanks for everything!
[Verizon LG G2] Nafon:
It would seem that LG changed something in their lollpop update to make mi2raw not work. I tried it on the stock 39a OTA and it didn't work. The dev will have to update his app to support lollipop. You could try emailing him and asking. His last update was from months ago stating that he was working on supporting the G3.
[Verizon LG G2] xI mEzMeRiZe Ix:
Honest question: what exactly are the benefits of running a build where all the proprietary/system files are from 39A? More stable? Better battery life?
[Verizon LG G2] jesssiii:
How's battery for you? I had horrendous battery on the stock 39A.

VZW LG G2
[Verizon LG G2] TheUnladenSwallow:
Yup, all currently released LG lollipop ROMs are rootable. I was on the 39a ota unrooted (forced it on w/ the instructions), used the new rooting method, used adb to flash the 28a aboot and blastgator's twrp and then flashed xdabbeb's bumped rooted stock kernel. Came from full unrooted lollipop (cus the ota broke it) and now I'm rooted with custom recovery.

On another note having everything based on 39a sounds great! All we'd be missing is a decent camera lol. Also going from your cm12 builds to stock lollipop, even with almost everything safe to disable disabled, there's way more stutter and jank. Most people probably wouldn't noticed it, but I'm pretty deep into the refresh rate, v sync etc rabbit hole lol, and I can safely say your cm12 builds are the smoothest I've ever used. Stock builds may not have much (really any) actual stutters in the system ui itself once you've disabled all the crap apps and it's stabilized, but things like minor frame lag in list views, which is more noticeable cus I'm on action launcher, or micro stutter in games (zig zag really stuck out to me) is present.
[Verizon LG G2] natemup:
Experienced this just now. Really weird...
[Verizon LG G2] Zaphod-Beeblebrox:
Not to be a smart-a$$, but what's the benefit from updating any software package to the latest release? Those metrics will vary, and in some cases, there is no benefit, and possibly a loss if the updated software is not well written.

That being said, there two general reasons to want to run the latest proprietary modules.

1) We have no access to the source code for these things. So, we are unable to make any improvements to functionality, optimization, fix bugs, etc. We are at the mercy of the manufacturer here. It is presumed that 39A software is better than previous versions.

2) 39A is the first lollipop based release. While it has been proven that various kernels, basebands, and bootloaders can be made to work with previous or newer Android versions, there are sometimes 'hackery' involved :) In this particular case, [MENTION=3416752]Jackpot Clavin[/MENTION] has done an incredible job of managing those differences and creating a more stable system than others. However, I'm sure he would rather have an android sub-system that's designed for the android version he's working with.
[Verizon LG G2] xI mEzMeRiZe Ix:
Thanks for the explaining!
[Verizon LG G2] xdabbeb:
[MENTION=3727492]JackpotClavin[/MENTION] FYI...I'm not sure if the camera driver is part of what you take, but if so, the L G2/GPro2 drivers have a problem that is making raw capture fail. I'm still looking into it, but at this point it doesn't look good.
[Verizon LG G2] JackpotClavin:
I'm beginning to wonder if LG even cares about raw with older devices. They might just use legacy support for phones already released, and use the new API for new phones :/
[Verizon LG G2] xdabbeb:
I don't think they'll ever give older devices full cam2 api either. The bummer here is that with the L driver, even the method I (and others) had been using to get raw sensor data is falling. It looks like the streams/buffers in the isp are being dumped randomly on capture. You can take one or two shots on initial preview start, but then it bombs. G3 L is fine, however.
[Verizon LG G2] drlenny:
Most Current

[MENTION=3416752]Jackpot Clavin[/MENTION] What, then, would you recommend to have the latest of what we can get on your rom when you drop your 39A build?

Would it be:

XDABBEB's 28A Bootstack

XDABBEB's 39A Modem

Blastgator's TWRP 2.8.5.1

Jackpot's CM12
[Verizon LG G2] heleos:
I would assume a 39a bootstack as well
[Verizon LG G2] TheUnladenSwallow:
The 39a bootstack doesn't allow for custom ROMs. Neither loki or bump work. We might get yet another exploit that'd work for this bootloader after the g4 comes out, but it doesn't really matter anyway.
[Verizon LG G2] heleos:
Xdabbeb included the older bootloader that was exploitable in all his bootstacks
[Verizon LG G2] wsw1640:
I've been running the rom the past week or so. A couple issues I've noticed is that the light sensor doesn't seem to work. Example, if I'm on a phone call and remove my phone from my face the screen doesn't light up. Had an issue with it today where I couldn't answer my phone when someone was calling. The other issue is that when I hit the power button on the back the screen doesn't always turn on. I have to hit it two or three times. Any suggestions?

By the way, amazing rom otherwise. Battery life has been very good for me. Only thing is I'm missing the camera app from xdabbeb. Great job!
[Verizon LG G2] Nafon:
Actually, with the exception of the 39a bootstack including the 27a aboot, each bootstack download has it's own bootloader version. 12B uses loki exploit and 24a+ uses bump. http://xdaforums.com/verizon-g2/development/vs980-resources-bootstacks-unofficial-t3050777
[Verizon LG G2] JackpotClavin:
New build is up. Just a summary of the build:

1. You should do a backup before installing, including your EFS partition in the backup

2. There may be regressions in this build since this is the first build with VS980 39A system blobs and I could not test everything (I haven't found anything yet)

3. You must be on the VS980 39A modem

4. You no longer have to be on the 12B bootstack (12B or a KitKat bootstack will work)
[Verizon LG G2] jesssiii:
Hot damn! Thanks JPC!

VZW LG G2