yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] crispy1:
I've been running the 3/04 version of 5.02 on the 26A modem for weeks. It is fully stable. Not noticing any bugs. My phones current uptime is now at 15 days!!

Anyway, just FYI. My experience suggests this is a great ROM.
[Verizon LG G2] z0mghii:
3/04 had google play services battery drain not fixed and also any heavy usage on a 5.0 rom would start killing apps like mad for me.
[Verizon LG G2] JRJ442:
A Google Play Services drain isn't a ROM issue. That's for Google themselves to fix.
[Verizon LG G2] z0mghii:
It is an issue that Google should be fixing, but we all know that's not going to happen. The fix was made in CM which the 3/04 build does not include:

http://review.cyanogenmod.org/#/c/91021/
[Verizon LG G2] xI mEzMeRiZe Ix:
Do you have any explanations or suggestions regarding my issue with multitasking?
[Verizon LG G2] fixxxer0:
This was the last version I was able to run problem free.

i cannot run ANY 39A rom, stock or otherwise, without having a slow charging (5 hours to charge is a dealbreaker) and gps never gets lock (minor issue really since its still usable).
[Verizon LG G2] schwem:
I use the stock charger and cable and I run all 39a roms, aosp, cm and stock. I'm on stock based xtreme 1.1 now and mine charges from dead in a little over an hour. I've never had slow charging with the 39a bootstack except when connected to my P.C. not sure why you're having this trouble and I never have. My phone actually charges faster on 39a than it did on 26a or 12b.
[Verizon LG G2] fixxxer0:
Yea I don't know why either...I'm using stock cable and charger at home and aftermarket 2amp in car and it doesn't charge above 500mah. These same chargers on 28a work just fine. Charge in about an.hour and a half from dead.

Obviously a software issue.

If you Google, you will see many forums with purple complaining of this even on stock OTA. So it's not an isolated thing.
[Verizon LG G2] bouchigo:
Yeah, it's a thing of luck I think. My two LG G2's both charge at about 1200mA - 1400mA with the stock charger and cable on 39A. A lot of other people aren't so lucky it seems. Unfortunately, I broke one of my cables, and when I use a non-oem cable I have lying around, the phone charges at about 120mA - 320mA. Good thing I have my Nexus 7 charger, and can get it to charge at the same level as the stock LG charger and cable.
[Verizon LG G2] Lawlrus:
I got an aftermarket one that works as well if not better than the stock one.

I got it from the vzw store, it has an led on the tip of it, for reference.

Never had an issue with it
[Verizon LG G2] darker_slayer:
Thanks for this and [MENTION=3178281]crispy1[/MENTION] for inadvertently bringing this up by recommending the 3/4 build.

I to had been running the 3/4 build for a while without noticing battery drain, but I had location on battery saving always and manually switched if we needed navigation

After this comment I decided to give the newest build a try, so first I simply clean flashed. I know it said to do stock first, but I'm hard headed. No rotation, no GPS

Off to micromod's debloated stock (using xdabbeb's 39a boot stack both times). Rotation works and GPS lock

Now clean flash JPC's cm12 and gapps. No rotation, no GPS

Thanks to whomever said dirty flashing from micromod's stock fixed the issue for them, because it did for me too. Clean flashed micromod's stock once more, got proximity, rotation, and GPS. Then dirty flashed JPCs cm12

Lots of Google play services crash this way, because I didn't think a gapps package was needed coming from stock. Back to recovery, flashed gapps, then booted without issue

Now I'm on JPC's 39a cm12 with everything working (don't use/have Bluetooth, so can't say). Rotation and proximity sensors were deal breakers for me

Strangely the play app "GPS status and toolbox" picked up a lock and #of SATs on stock, but shows no SATs locking on cm12.

I'll try the one recommended earlier in this thread again, but I'm not too concerned because I opened Google maps, left location on device only, ignored Google's request to change that setting, and got a lock. Then to test it further, I drove to the store (was going there anyway) with airplane mode turned on, and my location (device only) still kept updating for a mile before I switched it back out of airplane.

That just tells me the other app is amiss, but GPS has always worked for me. I've been a happy, lucky G2 owner

Much happier thanks to [MENTION=2941286]xdabbeb[/MENTION] and [MENTION=3727492]JackpotClavin[/MENTION]. I surely wouldn't have used the phone this long if it weren't for the great support

Some new battery stats for me
[Verizon LG G2] JackpotClavin:
Here's a CM12.1 build that I threw together over the weekend. I've been running it for the last few days and have no issues but I could not test everything so your mileage may vary. I'd like to get back into development in the next couple of weeks weeks, so if you have a bug with CM12.1, post in the thread and I'll get on it whenever I'm free.

You should definitely make a backup before installing, as there probably isn't any way to downgrade from CM12.1 to CM12 without doing a factory reset, but you can always restore that backup that I'm advising you to make right now

If you are currently on my CM12, you can flash this (I think you can dirty flash)

If you are not on my CM12, you should install a stock (or stock-based) 39A Lollipop ROM, make sure everything's working (sensors, LTE, GPS, etc) then you can install this build after doing a factory reset

Remember you'll have to install a CM12.1-compatible Gapps package!

https://www.androidfilehost.com/?fid=23991606952593197

Post your findings, I'll get around to fixing bugs if/when I have a chance in the next few weeks

For those looking to build, I just pushed some source to my github under the cm-12.1-JPC branch, it will also needs these three patches:

frameworks/native: http://review.cyanogenmod.org/#/c/93214/

hardware/qcom/gps: https://github.com/CyanogenMod/andr...mmit/79c877db2447b8e08560fa01a5a825ebbb2f58ee

hardware/qcom/media/msm8974:

https://github.com/CyanogenMod/andr...mmit/ceb0707e139a146679d4bdd17be47451a577793d
[Verizon LG G2] :
I haven't flashed this yet (going to be out and about today so I have to make sure my phone's in a working state)

Did this fix the "No GPS lock" issue in GPS test apps that we've been having with non-stock roms?

Edit:

Disregard, it didn't.

For that first commit/review... Doesn't it require something like

NEEDS_LGE_RIL_SYMBOLS := true

added to the boardconfig for it to have any effect?
[Verizon LG G2] jesssiii:
It's like Christmas in April! Thanks!

VZW LG G2
[Verizon LG G2] zman0125:
Everything is working perfectly (didn't test BT). Thank you so much for another great build!
[Verizon LG G2] JackpotClavin:
Yes, whoops forgot that
[Verizon LG G2] :
No worries man. Thanks for what you do.

I just had to ask because I'm trying to build PAC-ROM 5.1 right now, I pulled in the same commits (since they use CM as a base as well) and noticed that being part of the IF switch. I was just making sure I was doing it right :)
[Verizon LG G2] koftheworld:
The one thing I've noticed so far is that no pay with NFC option appears in Google wallet.
[Verizon LG G2] da_reeseboy:
Someone correct me if I'm wrong, but I don't think it is there in any rom based on 39a.
[Verizon LG G2] :
...

You're posing in the thread for one. JPC's CM12 boots on 39a, so does Euphoria.
[Verizon LG G2] jesssiii:
He was referring to google tap to pay in NFC.

VZW LG G2
[Verizon LG G2] :
Oh. Haha... I feel dumb. I misread what he typed.

Sorry about that.... When I was replying I was like... "What's going on here... I know he's better than that.."

lol
[Verizon LG G2] da_reeseboy:
Correct. Koftheworld mentioned it was missing (at least I thought he was) so I was confirming it and stating that it'll be that way with any rom (stock, CM, aosp) based on 39a I believe. Do you know if tap2pay is missing from euphoria?
[Verizon LG G2] :
No idea. I don't use tap2pay... and really, I don't know that I trust Google Wallet enough to add a card/account to it to try and troubleshoot it (plus I'd likely need to actually try to use it at a NFC POS terminal to get anything decent from a logcat/dmesg)

Also, See my previous reply to jessii. Sorry about that. I feel pretty dumb now for mis-reading your post.
[Verizon LG G2] jesssiii:
[MENTION=3727492]JackpotClavin[/MENTION], can't find a thing wrong thus far. With [MENTION=4231562]Yoinx[/MENTION]'s FlusterCluck kernel, it's perfection!

I'd been using xdabbeb's G3 rom, which is kitkat, because it gave me most of the best of lollipop without the issues. But LP 5.1 seems to be a big improvement, especially on 39A. The battery drain being the worst for me,, appears to have resolved.

VZW LG G2
[Verizon LG G2] da_reeseboy:
Haha it's all good. You helped clarify :)
[Verizon LG G2] :
Hey man, I hate to be a bother... But I've tried building CM12, CM12.1 and Pac-Rom 5.1 now off your sources with the commits you've mentioned (at various times). Everytime they've worked perfectly fine except that there's no SIM each time.

I've tried powering down and removing my sim. With no change...

I tried Pac-Rom today (which is mostly CM based). Same thing. with the 3 commits you mentioned, and "NEEDS_LGE_RIL_SYMBOLS := true" in my g2-common device tree.

Are you 100% that there's not some other commit/revert/change that's needed to detect the SIM on the 39A baseband?

this was my roomservice.xm for today:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="JackpotClavin/android_device_lge_vs980" path="device/lge/vs980" remote="github" revision="cm-12.1-JPC" />
<project name="JackpotClavin/android_device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="cm-12.1-JPC" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="JackpotClavin/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-12.1-JPC" />
<project name="JackpotClavin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1-JPC" />
</manifest>

This is really starting to drive me nuts... because it's the same on each rom I try to build... perfectly fine just no SIM detected.
[Verizon LG G2] JackpotClavin:
That's really weird... does the radio on my builds work on your phone? If mine don't work then it might be a problem on your phone/sim. Can you get me a logcat and dmesg?
[Verizon LG G2] koftheworld:
Correct it's missing. The option exists on stock and stock based roms. I just found it curious that the option isn't even there in Google Wallet. I use it infrequently but it's kind of nice anyway.

I know that jpc doesn't use NFC, but I thought I would report it anyway.

Btw Bluetooth audio streaming and GPS are working great here.
[Verizon LG G2] :
Is GPS reporting a lock in gps test apps? Or just working in maps?
[Verizon LG G2] da_reeseboy:
When you say stock, you mean it's in the 39a stock rom? I know it was in all the kitkat based stock roms...
[Verizon LG G2] koftheworld:
Yes. The option exists in 39a and on 39a based roms. Sorry for not being specific.

I haven't checked a GPS app besides using maps sorry.
[Verizon LG G2] :
Probably in one of the umpteen or so proprietary binaries that aren't in custom roms then.

If I ever get a rom building and recognizing the SIM... I'll probably start trying to track down various helper binaries to see if I can fix some other issues like the GPS lock and such. I imagine NFC will be something like that too.
[Verizon LG G2] JackpotClavin:
Can you upload one of your builds so I can diff it?
[Verizon LG G2] :
Sure, give me like 10 minutes for it to upload.

Are you alright with it being a Pac-Rom build? That's what I'm trying to build today...

If not I'll clean build CM12.1 overnight and upload it instead. It'll just take like 5 hours to build.
[Verizon LG G2] JackpotClavin:
Are you sure the issue isn't pac? Have you tried clean flashing?
[Verizon LG G2] :
I have.

I had the exact same issue clean build/flashing off your CM12 sources about 2 weeks ago.

It's really blowing my mind.

I'll try a clean build off 12.1 tomorrow and upload it.

Right now, I'm trying to build off the LG-Devs repos.

I know.. I'm adding variables... But I'm building on an I5 laptop, so I dont have the power to build clean tonight off cm12.1
[Verizon LG G2] JackpotClavin:
Looks like you aren't including the patch in frameworks/native, which is needed for libril.so to link up with libbinder.so.

No RIL library link -> no radio

For some reason or another libbinder is not get getting http://review.cyanogenmod.org/#/c/93214/
[Verizon LG G2] :
I think rashed figuted it out for me...

boardconfig actually needs

TARGET_RELEASE_CPPFLAGS -DNEEDS_LGE_RIL_SYMBOLS
[Verizon LG G2] JackpotClavin:
I just pushed a commit for that just a second ago haha

The reason I never caught that was because I had been cherry-picking this commit but had been telling you to cherry-pick this commit

Notice one has a preprocessor directive and the one I had been using doesn't, so it always built it regardless
[Verizon LG G2] :
lol... bastard (jokingly ofc).

As always Thanks for what you do. The button just isnt enough for me.
[Verizon LG G2] Lawlrus:
People that have issues with tap and pay on 39a.

Does anyone know if cyngyn is packing basebands with the ROMs, just like they added the recovery?

I have seen people report that cyngyn was prepackaging it, and didnt know if that played a part in it saying unknown.
[Verizon LG G2] r_dub:
I've noticed the latest CM 12.1 update brings back the carrier name/nam1 bug. Shows Verizon instead of Verizon Wireless and when trying to the *#*#4636#*#* trick you lose SMS/MMS sending capabilities. Just a heads up, because this wasn't present in the last release.
[Verizon LG G2] :
Yeah. I knew there had to be *something* that you were doing differently than I was... I'm not that horrible at building things.

What was crazy though was that nothing ever failed and the roms booted fine. I just never got my SIM each time.

Definitely explains it though.

Thanks!

*edit*

Yup... that was it, now it's finding my sim on my builds.
[Verizon LG G2] steveo17:
anyone try the 5.1 xposed with this cm12.1? mine won't boot with it
[Verizon LG G2] jesssiii:
Mine says Verizon Wireless. Clean flash of course.

VZW LG G2
[Verizon LG G2] r_dub:
I clean flashed as well even went back to stock 39a made sure my sensors worked then clean flashed 12.1. Still shows Verizon instead of Verizon Wireless I even tried restoring my nandroid of the previous release and dirty flashing on top of that got the same result showing Verizon.
[Verizon LG G2] sunkim50:
Same here. Cleaned flash last night and carrier name shows up at Verizon Wireless. Only minor bug I had was no data for a little bit. Hard to do a reset to get data back.
[Verizon LG G2] :
Probably could've just toggled your mobile data settings and powered the phone off for a minute or so and back on as well to fix that.
[Verizon LG G2] sunkim50:
I tried toggling airplane mode without any success. Maybe I didn't let it sit in airplane mode long enough. Will try again when/if it happens again.
[Verizon LG G2] r_dub:
So I'm the only one experiencing this? If I grab a log after a clean flash can someone help point me in the right direction of fixing this because I'm quite tired of this bug.
[Verizon LG G2] koftheworld:
I clean flashed as well and am experiencing the same issue. Network is listed as Verizon. If it matters, I used banks gapps.
[Verizon LG G2] r_dub:
I used pa gapps and flashed without gapps to test that as well still comes up just Verizon.
[Verizon LG G2] funkybrunk:
I've had data issues before that neither airplane mode toggle or reboot would fix, but a power down/power on did.
[Verizon LG G2] bbender716:
For me, I just go into APN settings then click on the Verizon wireless at the bottom, then without making changes I "save" and voila lte back.
[Verizon LG G2] viper909:
I dirty-flashed from the last nightly with PA GApps, and I'm getting the NAM1 carrier text as well. I'm also getting persistent wakelocks from the phone app (RILJ), and the alarm causing the wakeups is ...telephony.data-reconnect. Never experienced that one before.

On a possibly unrelated note, my camera has been acting strangely since I updated to the 5.1.1 build. It doesn't recognize landscape pictures or videos (they show up as portait in the gallery), and I've lost panorama and photosphere. I'm guessing this could be a GApps thing, but I haven't seen this issue before either.

EDIT: Everything else's been great so far!

EDIT 2: Forgot to mention it, but so far as I can tell all my sensors are working fine. Auto-rotate works normally.
[Verizon LG G2] viper909:
That button did not do what I thought it did.
[Verizon LG G2] drivenby:
Happened to me too
[Verizon LG G2] joedajoester:
Left my phone on overnight and this happened. 5.1.1 I'm on btw. It doesn't seem to be a wakelock, so not sure what's up.

I've also been getting the weird random vibrating that was mentioned. For data issues I switch APN to something else and back to the normal one.
[Verizon LG G2] Lawlrus:
Yeah, its happening to me as well on pretty much every 5.1 ROM I flash. Turns off once you make it vibrate again.
[Verizon LG G2] :
Looks like Rashed's binder patch got accepted into the CM12.1 source now, so that cherry-pick *should* no longer be needed for people building in the future.
[Verizon LG G2] :
So, I kicked up the debugging level during boot today to try and trace down some of the ril issues. For the baseband unknown and GPS lock issues, yes.. I believe the GPS issues to be part of it, since that goes through the telephony provider now.

I think that the device tree's RIL class might need to be updated, but I have no idea how.

But, I do have some stuff like this in my logs now indicating that the modem is actually involved. It could also be some of why the radio logcat is flooded with errors now in CM.

E/LocSvc_eng( 1179): E/void loc_eng_agps_init(loc_eng_data_s_type&, AGpsExtCallbacks*): log_eng state error: agps instance already initialized
D/GpsLocationProvider( 1179): handleEnable ( host? e-slp.lte.911.nj.myvzw.com ,port? 7275 )
D/LgeGpsLocationProvider( 1179): android_location_GpsLocationProvider_lge_gnss_command (vss)
D/LgeGpsLocationProvider( 1179): Received raw command is [lge.gps.extracmd.raw.tls.mode#1] and length is [31]
D/LgeGpsLocationProvider( 1179): [IsHasDelimiter] [tok]=[lge.gps.extracmd.raw.tls.mode], [lasts]=[1]
D/LgeGpsLocationProvider( 1179): Matched!! No#9 Raw:lge.gps.extracmd.raw.tls.mode#, ID:5, Param:1
D/LgeGpsLocationProvider( 1179): request_to_modem: cmd=5, param=1
E/QMI_FW ( 1179): [LGE_VSS_QCCI][AP] Enter qcci_qmi_lge_gnss_send_cmd(0x2).....
E/QMI_FW ( 1179): [LGE_VSS_QCCI][AP] sendind MSG = 0x703
D/LgeGpsLocationProvider( 1179): FAILED!...request_to_modem() ERROR! return1 = 0 , return2 = 1
D/LgeGpsLocationProvider( 1179): handleEnable :native_set_agps_server =e-slp.lte.911.nj.myvzw.com:7275, TlsMode =1

Though, from little bit there... it looks to me kinda like LG couldn't figure it out either and just included a helper :s

[MENTION=3727492]JackpotClavin[/MENTION], if it helps I'd be happy to send you my logs that I took with the log level boosted. I also did a stack trace on rild during boot.
[Verizon LG G2] viper909:
Alright, so I started noticing all kinds of sensor problems, and restoring the backed up sensors didn't help, so I flashed stock and got a GPS lock, etc., then restored.

That fixed all the sensor issues and my camera app is no longer ****ed, but speaking of RILs, I'm still getting the RILJ wakeups. Is anyone else experiencing this? It's crushing my battery, so if I'm the only one I might just try a clean flash and see if that sorts it.
[Verizon LG G2] HueyT:
JackpotClavin released another CM12.1 on androidfilehost: https://www.androidfilehost.com/?fid=23991606952595892
[Verizon LG G2] :
Were you able to flash it and run it sucessfully? The build I made this afternoon crashes phone and nfc, and boot loops after a minute or so of the rom loading.
[Verizon LG G2] JackpotClavin:
I was testing that build yesterday. It has a fixed Power HAL (we were using a semi-broken one before) so the overnight battery drain should be minimal now. Also uses CM source from the afternoon of May 3rd
[Verizon LG G2] JackpotClavin:
http://pastebin.com/raw.php?i=BivxnWJc
[Verizon LG G2] jesssiii:
Thanks, working well!

VZW LG G2
[Verizon LG G2] HueyT:
Yep, installs and works great for me. Taking call all weekend on this ROM and battery life is great. Everything works including DT2W.
[Verizon LG G2] jesssiii:
JPC'S 5.1 latest build is running great.

Question: Anyone using LiveDisplay, and if so, does it work? Also, in theory should it use more or less battery?

VZW LG G2
[Verizon LG G2] Lawlrus:
It does what it says it does, not sure if it helps with eye strain or not like its supposed to.

If you manually change it, I wouldn't think it would use more battery.

Having it set to auto always ques the sensor so that uses a lot
[Verizon LG G2] :
I use it all the time, it's great that they finally added this into the roms. I've always had to use lux or cf.lumen in the past.

Yes it works.

No it doesn't use more battery. Your light sensor is on anyway while the screen is on for adaptive brightness, if your using that (most people do). So all you're doing is adding a color filter by tweaking the drivers run settings. It may use slightly more power to process the colors, but it shouldn't be anything you would ever notice... If you do its probably time for a new battery.

I think Lawlrus is thinking of that other seeing that turns the screen on when you flip it over... Which eats up battery.
[Verizon LG G2] :
Also, not sure if this is the new power hal at work or not... But this is my battery life so far... All wifi connected though at home with just over 2 hours SOT.

Seems pretty legit so far. Though it's on my kernel not the built in one, so they might be why the os draw is the highest....
[Verizon LG G2] dtomlin:
Using 5/2 since release and have no problems. Only "bug" I can find is unknown baseband in settings.
[Verizon LG G2] Dick Ripple:
Is tap to pay working? That's the only thing keeping me on an older build.
[Verizon LG G2] dtomlin:
Not tried it
[Verizon LG G2] jesssiii:
I hadn't been using adaptive brightness nor LiveDisplay. I thought I needed my screen very bright due to poor eyesight, and the brightness really eats battery. I just tried both adaptive brightness and LiveDisplay during my workday today and am surprised I seem to be able to see nearly as well as with brightness turned up high. And it seems to really, in my case, saved quite a bit of battery. Plus, I don't have to mess with the brightness. Thanks for the heads up!

VZW LG G2
[Verizon LG G2] Lawlrus:
I don't use tap to pay. But I'm pretty sure the issue with tap to pay is because of that unknown baseband issue
[Verizon LG G2] rockcipher:
Tap to pay is still non functional on the 5/2 build.
[Verizon LG G2] Cobjones:
Light sensor isn't working 5/3 clean flash. Anyone else?

Edit; just started working out of nowhere.
[Verizon LG G2] steveo17:
works fine for me.
[Verizon LG G2] Cobjones:
I've been having issues with pressing the back button .

When I press back about 1/3 the time it also selects the home button. It happened on kk and I factory reset and even went to lollipop and am having the same problem. Search online came back negative.
[Verizon LG G2] :
So what you're saying is it had nothing to do with this rom, or any other specifically.

Which means you took a wrong turn somewhere, this is the verizon g2 forum... The Q&A forum is a few clicks away.
[Verizon LG G2] Cobjones:
No, I put it in this thread because it is happening on this ROM. I am using the Verizon G2. It is doing this on both KK CM and LP CM.

Since you need details. I am male, 29 and in KS. Need anything else? Just respond dickishly again.
[Verizon LG G2] :
And only on jpc's cm 12 builds? Mind you cm12 was never kitkat.

Based on that your original post stated that it wasn't specific to this rom, so it's not a probably with this rom. Thus, it should be in the Q&A thread, not cluttering up a specific rom's thread.