yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] AO4EVER:
That's what I thought. Thank you.

I think I might have found the problem though. Maybe.

To transcribe the problem to my situation - In the updater-script, the device is referred to as vs980, but the actual phone status it says vs98026A. If I am reading the code correctly, it's supposed to put up that very error I received if they don't match.

The solution linked suggests deleting the verification piece all together, I'll try to modify it first, though I am not sure which reference should be modified, as there are a few. Maybe JackpotClavin can chime in if he has time.

If it is indeed the problem and the solution, I wonder why others don't get the error... Theoretically their devices would have a "different" device name also?
[Verizon LG G2] wyrdtrtle:
They most likely will if coming from carbon, since its build.prop is whats setting that vs98026a
[Verizon LG G2] Nandrew:
Oh it feels so good to be back on cm. Thanks a million JPC! Everything is running great here.

Sent from my LG-VS980
[Verizon LG G2] ddzado:
Are people seeing the 3g/4g bug on 26a?
[Verizon LG G2] dtomlin:
I haven't
[Verizon LG G2] AO4EVER:
Carbon being the factory software right? You are probably right.

Ended up deleting part of the verification code, and was finally able to get the latest CM to boot. Everything seems to be running fine.

Still would be very curious to find out how exactly that verification flashed. to give the error message.

---------- Post added at 04:54 PM ---------- Previous post was at 04:49 PM ----------

Was finally able to flash. Working great, thank you!

The only thing I noticed is TWRP app (not the backup itself) crushes every time I open it. Using 26A
[Verizon LG G2] wyrdtrtle:
Well not the factory software, but the software currently occupying the system partition. The recovery has assert checks built-in so that it wont flash say a rom made for the ls980 if the build.prop says that the device is a vs980.
[Verizon LG G2] reklipz:
Hey all. I've been running into issues that seem to stem from proximity sensing. I'm thinking it's something in the software, as my friend with a Samsung Galaxy S5 (CM11) is having the same issue.

When making a phone call, it's virtually impossible to get the backlight/lcd to turn on, and when it does (trick it via plugging in headset or power or spamming the power button and getting lucky), the touch input doesn't work half (all?) the time. If the "prox detection" (prevent accidental wakeup) feature is turned on for the waking the device, it becomes nearly impossible to wake the device as well. Checking that the light sensor works by using the advanced brightness curve adjuster checks out fine (I can make it fluctuate from 10 to 10k lux w/ flashlight) This makes me think something is wrong with the software (because it worked on older CM11 builds, and my buddies Samsung Galaxy S5 has the same issue with a recent build of CM11).

I have the issue on the 09/28 release, and the current 10/19 release. Does anyone else have this issue? Has anyone resolved it?
[Verizon LG G2] steveo17:
try turning off the "prevent accidental wakeup" under display settings
[Verizon LG G2] reklipz:
If you read carefully, you'll note that I have tried this... it's part of the diagnostic that I tried to perform and write-up. Turning it on makes the issue worse: not only can I not use the phone during/after a phone call, I can't even get it to wake.

Are you telling me that you don't experience this issue with either of these builds? What should a typical ambient light reading be in an office/indoor environment: phone laying flat on a desk or such? Mine reads between 10 and 50 on the desk, 0 with finger over, and 100-200 with the desk lamp on overhead, and it goes up to 10k if I use a flashlight.
[Verizon LG G2] ddzado:
NFC Problems on 26A... I saw that others experienced this issue.. any work-around?

---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------

I've seen issues. Tap and Pay didn't work for me just now.
[Verizon LG G2] bouchigo:
You don't have a screen protector that is covering the screen by any chance do you?

I had similar issues to you, especially when making calls; the screen would not light up until a few seconds after the call was over. It happened when I went to 26A. It would seem to work fine on anything 24A, and as soon as I went to 26A, the problems would begin. I ended up cutting the piece of screen protector that was over the proximity sensor, and now it works fine. You can buy screen protectors that don't block that area.

If you use xposed, there is a module to disable the proximity sensor if there is no other remedy.

If you don't have a screen protector, then it may be possible that your proximity sensor is not working properly. Have you tried going back to an older CM11 build, or any other ROM?
[Verizon LG G2] CaptainElwood:
Anyone else having problems with Pandora on the latest build?

I have no audio through the speaker or headset and the songs just keep skipping to the next track.
[Verizon LG G2] Sonic_44:
Does anyone know if the mixer_paths.xml file from a few months back still works with the new build since it's changed the base? I loved having the louder speaker volumes. If anyone knows, let me know. Thank you
[Verizon LG G2] dtomlin:
Still works for me.
[Verizon LG G2] Zaphod-Beeblebrox:
I'm on 26a bootstack and 10/19 build. Have very similar problems, but have had them pretty consistently on any AOSP based rom (even 12b based, etc) .

When in a call, the proximity sensor seems to work until the device hits the normal 'time out' for screen on. I can often hear the little click noise that would normally associate with the screen timeout and cutting off. Once that happens, the screen no longer comes back on when the phone is pulled away from ones face (ie, proximity detector doesn't cut the screen back on). When the call ends the screen comes back on by itself.

So, real world example: I have a several minute conversation, and when the call is over, I pull the phone away from my ear to 'hang up', but the screen won't come back on. I start to hit the power button to bring the screen back on, but by then the other party has hung up, and my screen comes back on just in time to show the call end screen going away.

On relatively short calls, the sensor seems to work fine (ie, if I'm calling into my voicemail system, and I need to hit passcodes, etc, each time I pull the phone away from my ear, the screen comes back on).

Note that I too have unchecked the 'Prevent accidental wakup' in display settings.
[Verizon LG G2] Xyriin:
This is kind of an odd request but is anyone currently on stock that could post some screens (or reply with the pertinent items) of the phone information in the settings. I'm dealing with a phantom mobile data usage (1.5 GB during a 6 hour period while I was home on wifi and my data usage graph doesn't concur with that usage...144 MB). They're running through their script and I got asked about a Last Factory Reset Date entry. I'm assuming they may also try to verify the software version, and other items as well.

To the best of my knowledge...

Android 4.4.2

VS98026A

Kernel same as the CM build but lge@android vice the JPC line

Baseband same as the CM build

Unsure of build number
[Verizon LG G2] ThatKidDrew:
Is this the information you're looking for?

VS980 Stock 4.4.2
[Verizon LG G2] Xyriin:
Perfect thank you! Any chance you can also get the Software Information screen?
[Verizon LG G2] joedajoester:
Im seeing ui lag on this phone on any rom, play store homepage jumps around so much, Google play music is around 30fps and below. I showed my friend who owns a n4, he claims he sees none of it. So that makes me think it's the phones fault or cm. Any ideas?
[Verizon LG G2] ThatKidDrew:
No problem

VS980 Stock 4.4.2
[Verizon LG G2] Xyriin:
As a follow up to the phantom data issue Verizon eventually gave me a $10 credit to my account since I'm more than likely going to go over my limit from normal usage.

They seem to think the 1.5 GB data session was over roaming based on the coding in their system. The obvious conflict is that I don't have roaming data enabled and the mobile data didn't show up in Data Usage History.

I can't think of anything that would cause it but I did flash the 26A baseband and the 10/19 build the day before the phantom data showed up. I would think that if there were some weird data transfer happening it would still show up in the Data Usage History.
[Verizon LG G2] luv2increase:
You say any ROM? Then you say maybe it is CM's fault. That makes me wonder. What all ROMs have you tried? Also, have you tried any tweaking or mods? Have you tried the ART runtime? Have you tried interactive governor?
[Verizon LG G2] joedajoester:
On lgs stock g2 rom the lag is pretty bad, g3 rom its less laggy, probably on the same level as cm. All these roms have some lag in its ui. Perfect example is the play music app. It is possibly the worst app simply because of its terrible lag.
[Verizon LG G2] Lawlrus:
Any cyngn based or aosp based ROM runs infinitely faster for me then what stock does. I use art, and normally ondemand gov, and turn animations off.

Some stock kernels (xdabbeb's) typically run much smoother then what a stock Google complied kernel does, because it is built using linaro. As far as aosp, I don't see much a difference between the two.

As he stated above, try using interactive, or a different ROM that's not cyngn based.

I've been in this thread from pretty much the begining, and I don't remember a single person stating that this ROM is (laggy) you either have an app (xposed module) or a faulty phone acting up.

I find it hard to believe a n4 runs smoother than what this device does with its specs.
[Verizon LG G2] soapinmouth:
Is there any custom kernels that work for this
[Verizon LG G2] Lawlrus:
Negative.
[Verizon LG G2] RunNgun42:
Does anyone know if it's possible to have the "quick pulldown" option function from any area of the status bar and not just right/left? I dont want to have to actually swipe down from the side, but rather swipe down from ANYWHERE and get the quick settings buttons to appear.

And also if it's possible to enable long-pressing home button to bring up recent apps list. This way I dont need to have an extra shortcut just for that purpose.
[Verizon LG G2] joedajoester:
I made a quick video showing the lag. Sorry for the low bit rate. Even right after a flash the fps lag is there. Its just some apps its visible in. The android ui is lagfree like 90% of the time. Soundcloud, play music, play store.. They show some lag, and play music has the most lag. Fps drop so low, like 20fps, making it almost unusable.

I am using interactive governor, and no modifications made. I can clean install this rom and still have this lag.

http://youtu.be/tBzvPxWcqaM
[Verizon LG G2] Sonic_44:
If you use Xposed Modules and use Xposed GEL Settings you can set the swipe down area where you want for what you want. As for the Home/Recents button, you may be able to use Gravity Box [KK] to set that up
[Verizon LG G2] JackpotClavin:
New build is in the OP
[Verizon LG G2] Sonic_44:
The PERFECT birthday present! Haha Thank you!
[Verizon LG G2] soundgirl101:
:highfive::good::cool: Thank you JC for another truly awesome build!! Buttery smooth and wicked fast!! No issues, as usual, bluetooth, gps, sms/mms, xlte, spot on!! Thank you again JC!! Rokks this girl's device all day, every day!! :cool::good::highfive:
[Verizon LG G2] stelthy77:
Pandora?
[Verizon LG G2] drlenny:
No Joke? my birthday was the 26th as well!
[Verizon LG G2] xttapolatakettle:
NFC functionality has RETURNED in the new build, although I haven't tried mobile payments yet. Thanks JPC! :)
[Verizon LG G2] steveo17:
its broken everywhere. stupid Rite Aid, CVS and MCX
[Verizon LG G2] xttapolatakettle:
Sorry, I gotta stop jumping the gun. I get too excited
[Verizon LG G2] steveo17:
Oh I wasn't being serious. I haven't tried it yet. I was making a joke
[Verizon LG G2] stelthy77:
I'll answer this after installing. Pandora is working fine on 26a baseband and 1026 nightly.
[Verizon LG G2] Sonic_44:
No joke. 27 y.o. now
[Verizon LG G2] chiefwigms:
Looks like its working for me - I tried it after 2 reboots and and a kill - started playing without any problems. Thanks JC! :good:
[Verizon LG G2] funkybrunk:
Keep Losing Mobile Data

I recently came back to this CM build after trying several other AOSP builds (Vanir the most recent). On the 10/26 build, which I clean installed yesterday, mobile data was fine until I disconnected from my home WiFi this morning. The device never connected to VZ at this point, even after a reboot and verifying all mobile data settings. I wiped the device, and installed the M11 snapshot build. This time, it never connected to VZ. I restored my Vanir backup, and everything works properly. Anyone have similar issues, and if so, what was the solution? I'll probably keep messing with it today to see if I can replicate the issue again.

26a bootstack (bouchigo). I may flash XDABBEB's bootstack to see if there is a difference.

Update: Flashed XDABBEB's bootstack, and clean flashed 10/26. I've connected and disconnected from WiFi multiple times, LTE connects instantly. Weirdness. I'll update if the issue pops again.

Update: Still seeing the issue occasionally. I noticed that if I reboot, the connection issue persists, but if I power off, then turn on, the mobile network connects correctly.
[Verizon LG G2] xttapolatakettle:
Sometimes after a new install, I have to reset APN settings back to default and choose the correct VZW APN. I'm not sure this has anything to do with your problem, though.
[Verizon LG G2] bouchigo:
The only difference is the one xdabbeb posted has a more up to date recovery, everything else is the same. I have a v2 I use for myself now that has the newer recovery, but there is no point in posting it at this point.
[Verizon LG G2] ddzado:
Anyone had weird in-call screen off isms? I can't get my screen to turn on while in call to save my life. I tried messing with the "Prevent Accidental Wake-up" or whatever. Kinda annoying. Not sure how to fix this.
[Verizon LG G2] acezhi:
I have the same issue on 26A.
[Verizon LG G2] drlenny:
26. Small world.
[Verizon LG G2] simpsonr:
Guys, the latest builds from CM (10/27) and on have a pretty nasty bug that disables all sensors (rotation, light, etc...). Just an FYI. Here's where it's stated. I've built on the latest sources and all sensors are down currently. JPC, be advised.

http://review.cyanogenmod.org/#/c/75698/

and

http://review.cyanogenmod.org/#/c/75302/
[Verizon LG G2] rockcipher:
I can confirm that mobile payments through Google Wallet work again in the October 26th build!

Somewhat related, has anyone been able to install Softcard through the play store? I'm unsure what is needed in build.prop or elsewhere to get the phone to be properly recognized as a Verizon LG G2. I've tried some workarounds using market helper, but haven't had any success.
[Verizon LG G2] :
[MENTION=3727492]JackpotClavin[/MENTION],

I'm trying to build off of your OP. I've tried with and without the RIL patch, just in case. The problem that I'm having is that none of my sesnors work

D/SensorService( 974): nuSensorService starting...
I/libsensor1( 974): sensor1_init_once: Setting log level to 5
I/qcom_sensors_hal( 974): hal_init: Setting log level to 3
D/qcom_sensors_hal( 974): hal_init: smgr support for mag cal 1
D/qcom_sensors_hal( 974): hal_load_oem_lib: Could not open OEM HAL library /system/lib/hw/sensors.oem.so
I/SystemServer( 974): Entered the Android system server!
D/qcom_sensors_hal( 974): _hal_sensors_open: name=poll
I/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list
D/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list: SMGR provides calibrated MAG
I/qcom_sensors_hal( 974): Sensor1 open: 0 45
E/QMI_FW ( 241): xport_send: Sendto failed for port 1536
E/Sensors ( 241): sns_acm_mr.c(348):Transport error -1
D/qcom_sensors_hal( 974): hal_wait_for_response: timeout=10000
E/ThermalEngine( 243): [GPU_MON] 6 percent. Current Sampling Time is 4 sec
E/qcom_sensors_hal( 974): hal_wait_for_response: pthread_cond_timedwait() rc=110 (cond: 0)
E/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list: Request timed out
I/qcom_sensors_hal( 974): hal_sensor1_close: closing sensor1...
E/QMI_FW ( 241): xport_send: Sendto failed for port 1536
E/Sensors ( 241): sns_acm_mr.c(348):Transport error -1
I/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list: Number of sensors: 0:
I/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list
I/qcom_sensors_hal( 974): Sensor1 open: 0 46
E/QMI_FW ( 241): xport_send: Sendto failed for port 1536
E/Sensors ( 241): sns_acm_mr.c(348):Transport error -1
E/qcom_sensors_hal( 974): hal_wait_for_response: pthread_cond_timedwait() rc=110 (cond: 0)
E/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list: Request timed out
I/qcom_sensors_hal( 974): hal_sensor1_close: closing sensor1...
E/QMI_FW ( 241): xport_send: Sendto failed for port 1536
E/Sensors ( 241): sns_acm_mr.c(348):Transport error -1
I/qcom_sensors_hal( 974): _hal_sensors_get_sensors_list: Number of sensors: 0:

What's confusing me is that it's trying to call this file: /system/lib/hw/sensors.oem.so which doesn't exist in the build that you have posted, nor in any of the proprietary trees. I also can't find the references for that file in the working one's logcat (likely because it's working).

Any ideas what I'm doing wrong?
[Verizon LG G2] simpsonr:
Revert the two commits I posted a couple back.
[Verizon LG G2] :
Man, I feel pretty dumb... I didn't even read the solution in the same page... Now I'm THAT guy.

Thanks. For the help.

Looks like we can leave those patches, and pickhttp://review.cyanogenmod.org/#/c/76008/ into the kernel. I'll test it shortly. Though that would break compatability with custom kernels until they also add it. Not really sure what benefit they were after with those patches.
[Verizon LG G2] HueyT:
All good on 26A and ART with highonandroid 1on1 hexoid theme :good:
[Verizon LG G2] JackpotClavin:
Just an FYI, installing the latest build may make your device ineligible for snapshot M12 as it might be right around the corner
[Verizon LG G2] :
Ineligible how? Does it replace something vital?
[Verizon LG G2] Lawlrus:
You would be dirty flashing an older build over a new one = you may have issues.

Clean flashing would be fine.
[Verizon LG G2] :
Thanks. When I hear 'ineligible' I think the worst... like bootloader lockdowns and such.

...didn't make a lot of sense from a CM build though.
[Verizon LG G2] steveo17:
Anyone here use Hangouts as their primary SMS app?

I would like to, and can, but I recently noticed that the APNs in there are way wrong and I can't change them. They show up as Metro PCS default and the rest are Sprint. I try to add the Verizon ones, but it doesn't stick. I have reset the APNs in hangouts and on the phone. The phone shows the right ones, but hangouts reverts to the wrong settings. Also, 8Sms and default messaging app work fine.

Any suggestions?
[Verizon LG G2] jesssiii:
If you're able to use it fine, perhaps it's just reporting incorrect APNs but using correct ones?

LG G2 VS980
[Verizon LG G2] simpsonr:
I have the same issue with no workarounds. :(
[Verizon LG G2] minnysota:
Same issue here. I can't figure out why Hangouts has been so hard to nail down for CM. It feels like I have had MMS issues for years.
[Verizon LG G2] steveo17:
Thanks guys. at least i'm not the only one

Saturday i was having major issues sending/receiving MMS with it. Today i'm testing it though and it seems to be better. not really sure though
[Verizon LG G2] Dick Ripple:
I'll tell you guys how I fixed my mms issues in hangouts. First I googled the correct Verizon apn. I then went into the apn settings on hangouts and clicked the plus button. Enter the correct info there, hit save, then reboot. Mms now works every time for me.
[Verizon LG G2] cazafka:
Mine shows metroPCS; however, works perfectly. Trying to edit causes them to vanish, trying to add Verizon does show after save.
[Verizon LG G2] steveo17:
same with me. could've just been a network issue that day i was trying to use it alot
[Verizon LG G2] Dick Ripple:
After the save it doesn't show up in the list but still works.
[Verizon LG G2] qqzwc:
GPS has been fixed! That's wonderful!
[Verizon LG G2] JackpotClavin:
Unfortunately there will be no build today. My build environment is all mucked up with the new 5.0 Lollipop source so I will have to sort everything out before making a build for us :/

But I did manage to get Lollipop to boot on my device -> http://imgur.com/OF1sNqg

Nothing works (yet) but the biggest obstacle of getting a booting build has been overcome

Next I'll have to start setting up SELinux our device
[Verizon LG G2] soundgirl101:
:highfive::good::cool: You so rokk JC!! Awesome to see ya buildin' Lollipop for us!! :highfive::good::cool:
[Verizon LG G2] EtherBoo:
Quick question.

I'm on a 24A build from August (finally getting around to updating) - I see the newest builds require 26A. Do I need to flash anything additional or can I just flash the ROM. Do I need to find the radios and flash them?

Also, amazing work by JPC getting Lollipop! Really exciting to know we'll be updated.
[Verizon LG G2] joedajoester:
This is amazing news! I had no hope for a lollipop ROM this year, but you just proved me wrong. Thanks so much for your hard work and I hope to see a lollipop build sometime soon, even if its not entirely functioning :P I'm just so excited for lollipop that I'd be so happy to use the current broken build lol
[Verizon LG G2] jesssiii:
They don't require 26A, but recommended, and you can get the bootstack from xdabbeb's rom thread. Flash then reboot recovery first before flashing the rom and gapps.

LG G2 VS980
[Verizon LG G2] jal3223:
So has anyone experienced the black lines on this rom so far? I'm looking to finally try an AOSP rom but I'm nervous about all the talk of hardware damage. Thanks for the input.
[Verizon LG G2] EtherBoo:
Honestly, I'd rather not wipe, so if I have to stay on 24A to not wipe, I'd do that over wiping just to get to 26A (although I'd consider it if it fixes WiFi issues).

So I'm safe to dirty flash from an August build? (Yes yes, making a backup of course).
[Verizon LG G2] jesssiii:
I didn't mention wiping, just rebooting recovery after flashing the bootstack before flashing rom.

LG G2 VS980
[Verizon LG G2] Sonic_44:
I have no idea what you're talking about with the black lines. Haha I waited for the white G2 to come out last year so I've had this phone over a year and have had THIS rom on it ever since and have never experienced anything wrong with hardware except for the photo sensor being weird when the screen was off. But still was able to get it to work...

So I would say this is your best bet for an AOSP based rom for your G2. I trust JPC with my life (and by life, I mean my phone haha).
[Verizon LG G2] marleyinoc:
Yeah, I've read about the black lines for other models of G2. This ROM is for the VS980 and as long as you're using that you should be fine.
[Verizon LG G2] koftheworld:
Fyi a mostly functional build of cm12 was recently uploaded for a different g2 variant here: http://xdaforums.com/showthread.php?t=2938539

Hopefully jpc can take a look at this and use it to move along his own build.
[Verizon LG G2] joedajoester:
Verizon phones are so unloved.... I really hope that helps JC with his development for lollipop on our phone. I'd be thankful just for a broken build that I can play around with, that'd hold everyone over until things get more stable
[Verizon LG G2] Lawlrus:
Off topic, but holy hell what a ****show that thread turned into haha
[Verizon LG G2] joedajoester:
Yeah haha maybe that's why JC isnt releasing anything lollipop yet. Boy I hate XDA sometimes...
[Verizon LG G2] JackpotClavin:
New update is up in the OP

It's a snapshot build (CM11-KitKat M12, not Lollipop)
[Verizon LG G2] Lawlrus:
That the last snapshot for KitKat?
[Verizon LG G2] JackpotClavin:
yep

I'm gonna work on getting Lollipop up to daily driver status (hopefully) this weekend
[Verizon LG G2] Lawlrus:
Hell if you get it up and daily driving by this weekend, that would be amazing.

But take as much time as you need.