yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] :
When going from 39a back to 12b, you need to restore the /sns partition from backup, assuming you made one... Otherwise you'll need to kdz/tot to fix the sensors. 39a modifies it so 12b can't seem to use it.

I asked blastagator to include this partition for backup in his twrp, so the newest version will let you now to alleviate that. . It's just not selected by default.
[Verizon LG G2] Nafon:
I and others have had success flashing a stock based rom, rotating the phone and getting a GPS lock, then flashing back to your desired ROM. Sometimes I've had to delete sns.reg and then reboot sock again. KDZ/TOT restore hasn't been necessary so far. But the option to back up would still be helpful.
[Verizon LG G2] wsw1640:
Hey guys! Quick question, does anyone have any suggestions for a good camera app? The Google camera just doesn't do it for me. I desperately miss xdabbeb and his app. I'm not bashing this rom because everything else is great but the flipping camera.
[Verizon LG G2] Xyriin:
SystemUpdateService Wakelock after Play Services 7 Update

For those still on the CM11 build you may be getting a battery hit in the form of a SystemUpdateService wakelock after the most recent Play Services update. CM12 apparently has a fix.

For a CM11 work around you can use App ops in the Privacy Guard to Deny permission for 'Wake up' and 'Keep awake'.

If that doesn't solve the problem by itself you can try further steps in...

http://xdaforums.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548
[Verizon LG G2] steveo17:
looks like this was resolved in the latest Google Play services 7.0.99
[Verizon LG G2] Xyriin:
Can definitely confirm that 7.0.99 doesn't resolve the issue on CM11. Pretty sure the fix in x.99 corrects the problem with CM12. Or maybe more accurately 4.4 vs 5.0.
[Verizon LG G2] El Ha$on:
I'm on cm11 and still suffering from that issue. I use the app disableservice to get same results and phone finally started deep sleeping at that point.

On another note. Verizon has made it official, http://goo.gl/XU5dwS

So maybe that might help any last bugs that might exist with cm12

Sent from my LG-VS980
[Verizon LG G2] joedajoester:
Seems like its the same thing that JC found on the Verizon servers. Its still 39a which also hints at it being the same. This ROM has also been using 39a. So yeah sadly it doesn't seem like anything new is coming our way.
[Verizon LG G2] KBizzle:
Put phone into airplane mode. Pull sim card. Power phone off. Put sim card back in and power phone on. Should fix sim issue.
[Verizon LG G2] :
Yeah, I've tried the sim pulling method a few times. Thanks though.

I really think that it might be something I was trying to do to fix the selinux permissions, on my builds rild stopped being allowed to do anything, so I'm *fairly* certain that's what was causing it. But, from the Vold denials... I'm trying to fix that to rule it out as being a cause of the GPS lock issues. somewhere along the line, I think I just straggler files somewhere.
[Verizon LG G2] Nafon:
I'm on the last non-39a CM12 build and I have to open disable service to check/uncheck systemupdateservice after every reboot.
[Verizon LG G2] steveo17:
Update to the latest play services
[Verizon LG G2] xI mEzMeRiZe Ix:
How exactly? I'm on Google Play services 7.0.99 (1809214-438), which according to APK Mirror, is the latest version, and I still have the wakelock issue.
[Verizon LG G2] JackpotClavin:
Hey, what's wrong with your builds? Not booting or not compiling? Also, you might wanna look into adding the following into the build.prop

persist.gps.qc_nlp_in_use=0

ro.gps.agps_provider=1

I wrote a blob utility last year to trace which files should be needed to add to a ROM's build to load a daemon in /system/bin or a library in /system/lib or /system/vendor/lib

http://xdaforums.com/showthread.php?t=2794413

I don't think I'm missing anything for the ROM currently, but if you find a daemon that's needed to fix the GPS, you could run it through the blob utility and it will tell you which libraries to build from source (if they aren't proprietary) or add into the build (if they are proprietary)
[Verizon LG G2] marleyinoc:
Yesterday I tightened my G2 screws and it went from not working at all (I tried the tape under clip/cover connection suggestion and thought I'd broke the whole thing) to working better than it did when I got it.

Not development related but maybe folks could rule hardware out that way.

I was using an old S3 on wifi for a GPS game and felt it was a little wobbly and that was the top fix for those (not sure it helped as I immediately tried on my G2 and haven't bothered with trying S3 yet).
[Verizon LG G2] :
They aren't booting now, and they're ending up about 20 megs smaller than they should be. I cleaned all of my build and ccache stuff out... No change. I'm thinking something synced that shouldn't have when I pulled the other day... Might have to dig through cm's commits since everything else is still the same now.

I'll have to look at that utility again. Thought last time it just have me the other blobs that file needed... Not the binary that used it.

I know on your build though there is still at least a few selinux issues in dmesg. That's what I was trying to work out first.
[Verizon LG G2] JackpotClavin:
Do a diff from your build to mine, perhaps you are using the official CM prop files
[Verizon LG G2] :
Yeah, I was planning on doing that when I got a chance . Just been pretty busy the last few days. I've got some time tonight and this weekend, I should be able to get to the bottom of it. Just gets a bit annoying when you think you fix it, wait the 2-3 hours for the build to finish... then figure it out it wasn't.

It could be using their device trees, but I don't think it is. Repo ignores my LGE devices, vendor and kernel as a mismatch.

By the way, please don't feel like I'm bashing your builds or anything with the spitball ideas I'm putting out... Just trying to come up with some reasoning for the wonky GPS. You know way more about this stuff than I do... I'm more of a hobbyist.
[Verizon LG G2] :
I got my builds working again. Not entirely sure what happened, but it seems like my vendor files weren't getting copied. Which was weird, because I hadn't messed with those previously. But, still getting my no sim indications when I boot up. There wasn't anything else you had to cherry pick to get your RILD working? I saw the commit for the rild symbols crossed out because of the radios, I tried that but can't test until Thursday night.

I'm still getting selinux denials for most of my system services...

<4>[ 534.980117 / 12-31 20:20:47.209] type=1400 audit(4847.209:2073): avc: denied { getattr } for pid=10631 comm="IntentService[M" path="/system/bin/rild" dev="mmcblk0p34" ino=281 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:rild_exec:s0 tclass=file permissive=0

like rild there. I get these for most of my daemons. Its really weird... not sure why selinux is considering them untrusted apps.

Also, I ended up using your utility. I think I got all the files that I'm looking at. Still not sure it will work if SE linux is being stupid about system binaries.
[Verizon LG G2] HueyT:
Stock camera made to work on CM and AOSP with different dpi: http://xdaforums.com/showthread.php?t=2522889 :good:
[Verizon LG G2] darker_slayer:
Sorry this isn't the best place to ask, and I'm not trying to troll by any means but can you elaborate on what selinux permissions mean for the end user (noob like myself)? I've been running JPCs cm builds and selinux has always been shown enforcing in my settings. I've asked before in other threads as well with no answer.

It doesn't interfere with anything as fast as I can tell, but I'm sure there is something I don't know. Doesn't appear to interfere with xposed or root for me since I'm using both without issue
[Verizon LG G2] snake2332:
The stock camera is also the one thing that kept bringing me back to stock-based roms for the LG G2 and the GS4 that I had. I gotta have a good shooter on my phone at all times and even the adapted LG camera is still garbage compared to the official one. Was hoping we'd have a better solution by now but I guess not. Oh well!

Meanwhile, we can do 4K video on our G2 now, though mine was only doing 17fps when I tested it. 1080p @ 60fps also couldn't hold 60fps for very long. Still kind of cool though.
[Verizon LG G2] Lawlrus:
[MENTION=3386918]snake2332[/MENTION]

There's other camera apps, some you pay for that may give you better results. But this isn't the place to discuss it, make a thread in the Q&A or whatever, you'll get a much better response from a larger base of people. Aldo check google, there's all kinds of camera ports from other devices that people say work wonders on this device.

Or there's this really cool thing I found the other day, its called a camera. There's only so much that can be done with aosp because lg frame works are closed source.
[Verizon LG G2] :
Yeah, it very likely won't affect anything. The simplest way of thinking of SELinux is just kinda like user policies. It keeps processes from doing things they aren't supposed to. It's not really anything to give much thought to for the end user as long as everything is developed right.

The other issue with AOSP is that only a few manufacturers/devices (read Nexus) actually put the effort in to implement the Camera 2 api that was added with lollipop which added a bunch of camera functionality. But yeah. If the camera functions aren't good enough for people, I'd say get a camera and let your phone do what it's supposed to... be a phone. The fact that it has a camera is just a convenience... it will never be a full featured replacement for a camera. Even the "features" of the stock framework additions are really just digital hacks on the pictures.
[Verizon LG G2] Lawlrus:
[MENTION=2020879]Yonix[/MENTION]

Have you tried, or had anyone try old gapps packages with this reboot issue?
[Verizon LG G2] :
No I've been focusing on my build issues, hadn't really had anyone try to do anything to be honest.

I finally figured it out. Somehow I had cloned themuppets repo into my vendor tree instead of JPC's....I don't know how I managed that. But that would explain all my SIM card issues I'd been having. I'm guessing when I forked his repos, it forked to the source or something.

Anyway, I'm pulling the right repo now and rebuilding. Hopefully that sorts it, then I can actually try to start modifying things.

I feel like such a noob right now lol.
[Verizon LG G2] z0mghii:
Getting reboots on the 21 build when using pocket casts, think it might be because of viper 4 android. Going to disable it and see how it goes tomorrow

Edit: Seems like my phone is doing a lot of reboots from memory problems. Strange..
[Verizon LG G2] bbender716:
Fwiw, I was using the old original lp cm gapps from November when I was having reboots. Currently running tameseks with the slim gapps he posted and don't have soft reboots for the first time with any 39a base.
[Verizon LG G2] Johnboy666:
All started with cm12

I tried to install cm 12, lost my 4g, no matter what I did I could not get it back and in the process almost bricked my phone. Now I am back up on 39a but still no 4g...anyone have any idea how I can fix this?
[Verizon LG G2] :
Yeah, supposedly has GPS working fine on his builds too... But he doesn't post his device trees like he's supposed to, or at least I can't find them on his posted repo.
[Verizon LG G2] jesssiii:
You might try TOT-ing back to stock. Backup SD card, obviously.

VZW LG G2
[Verizon LG G2] Johnboy666:
Yup did that, no help
[Verizon LG G2] :
Might wanna go back to full unrooted stock, and take it to verizon. Could be a sim card issue. Same thing used to happen if you tried to do the old update method for towers on your 4g sim...

Maybe something similar happened while flashing for some reason.

Could try turning the phone off, remove the sim for at least a minute then put it back in, boot and see if it's fixed.
[Verizon LG G2] steveo17:
i had this problem too.

i had to flash back to a 12B based rom. and flash the 12B bootstack. you should get 4G then. if that doesn't work let me know
[Verizon LG G2] Johnboy666:
Can I do this thru twrp or thru the lgflashtool?
[Verizon LG G2] Johnboy666:
Can you link me to the proper files to do this?...I can't seem to find a working 12b link
[Verizon LG G2] steveo17:
12B bootstack

https://www.dropbox.com/s/7qo7evm5cn6em3a/xdabbeb_vs98012b_bootstack.zip?dl=0

Flash this then

Flash xdadebb's 4.4 stock Rom. You should get 4g then
[Verizon LG G2] Johnboy666:
worked like a charm...now I am right where I want to be...phone went from week long brick to cm12....thanks to all who helped me out.
[Verizon LG G2] xttapolatakettle:
Guess who's got 2 thumbs and just unbricked his VS980 after 1 month in the dreaded Qualcomm QDLoader 9008 mode!

This guy.

It didn't boot. It didn't have Download Mode. It didn't even vibrate or show the LG logo screen. Well, now I'm back and running JPC's CM12. :victory:
[Verizon LG G2] annoyingduck:
This build has been really performing beautifully. I wish cm have us an m5 build, because your alteration would have been great on it. Thanks again [MENTION=3727492]JackpotClavin[/MENTION] . Hopefully all the other big boys can start to get some builds together for 24a users.

-VZW LG G2 VS980

---------- Post added at 07:19 PM ---------- Previous post was at 07:00 PM ----------

Also, just noticed download mode is still broken even after doing the laf.bin partition. Anyone know how to fix it?

-VZW LG G2 VS980
[Verizon LG G2] jschramm:
I have been on and off CM since I got the G2 but now it seems I am here to stay. Been on this version for 24 hrs now and its absolutely flawless, nothing else to say. Thanks.
[Verizon LG G2] JackpotClavin:
I can make an M5 build if it's wanted. The source was frozen to all new patches for stability purposes, so one device's source is the same as the next. There's no one patch that's in one device's build that's not in every other's. If I can obtain a source manifest I can cook up a new build with the M5 manifest
[Verizon LG G2] annoyingduck:
Nice. Any idea on my download mode question?

-VZW LG G2 VS980
[Verizon LG G2] 55Pegasus:
I wouldn't mind giving it a try. Had to go back to stock 24a after doing some testing on Cloudy's ROM, rotation broke.
[Verizon LG G2] jschramm:
I assume Official CM11 Nightlies will eventually work with the 24a, any idea how or when this will happen?
[Verizon LG G2] JackpotClavin:
Try doing it again. Somebody in another thread said it worked after doing it another time. What does md5sum /dev/block/<whatever>/laf yield?

From my LG-VS980 using xda app-developers app
[Verizon LG G2] annoyingduck:
Dev/block doesn't have a laf file in it, and neither do the folders

-VZW LG G2 VS980

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

Found it. There is no md5! Calculation error using solid Explorer

-VZW LG G2 VS980
[Verizon LG G2] steveo17:
Looks like that should be your issue

Mine results in

176266cf5b0f156980955e5603d3f232
[Verizon LG G2] annoyingduck:
Also, what's the exact adb command to push the file directly on my root directory? Instead of copying to my SD then using root explorer to move it...

-VZW LG G2 VS980
[Verizon LG G2] steveo17:
It's in the op

You have to adb shell then cd to the directory and then run dd command
[Verizon LG G2] nitsua98:
Ok, this is seriously annoying. Is anyone else's MMS messages taking forever or failing to send? And the same with receiving?
[Verizon LG G2] annoyingduck:
Your misunderstanding my question....

What I've done is just use root explorer to put the bin file right on my root directory. What I want to do is an adb push, but I don't know what the name to enter is. Everything I try fails.

Is it :

Adb shell

Su

Adb push laf.bin/root

??

-VZW LG G2 VS980
[Verizon LG G2] jesssiii:
I don't believe he misunderstood. The command starts with "dd" and is in the OP.

VZW LG G2 VS98024A
[Verizon LG G2] annoyingduck:
I'm clearly missing something. The way I got the bin file on my phone was to drag and drop it from my desktop to my internal storage. Then I used root Explorer to move the file from my internal SD to the root directory, not root of SD. How do I do that exact process through adb? The dd command is to write the file after it's on your phone. I want to get the file from my desktop to my root directory using adb only
[Verizon LG G2] s_wall98:
What needs to be done before the "dd" command?

I believe this is what is being asked. What specific directory does laf.bin need be in or if using adb to push it to the phone, what is the adb command
[Verizon LG G2] JackpotClavin:
adb push laf.bin /

that will put it in the root directory

by md5sum /dev/block/<whatever>/laf I meant /dev/block/platform/msm_sdcc.1/by-name/laf

I just couldn't remember the path name off the top of my head because I was on my my phone.

So what does "md5sum /dev/block/platform/msm_sdcc.1/by-name/laf" yield?
[Verizon LG G2] da_reeseboy:
adb push laf.bin /sdcard/laf.bin

adb shell

su

dd if=/sdcard/laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf

Done.
[Verizon LG G2] annoyingduck:
Thanks for the command, didn't know just a / would direct to root. I did the process again and I'm able to get into dl mode, but the dl mode screen now shows briefly, then a software update screen then appears. I quickly unplugged the phone. Here's what happens when I try to get md5 of that file:

-VZW LG G2 VS980
[Verizon LG G2] tacosrdelicioso:
It's supposed to go into that software update thing. Don't worry about it anymore. Its fixed.
[Verizon LG G2] joedajoester:
I just recovered from this as well haha. What did you do to get in it and how did you get out? I was on 12b and flashed one of micromods rom and my phone never came back. I ended up shorting different pins accidentally and I got into 9006 mode where I used a dd command for Windows tool and it flashed back the partitons I pulled from a .tot file.
[Verizon LG G2] xttapolatakettle:
I initially flashed the wrong combination of boot/aboot/recovery images and got stuck in 9006 mode. Then I messed up trying to flash the correct partitions and properly bricked it. I mean it was dead as disco--the notification light wouldn't even come on. The only sign that it was alive was that it showed up as Qualcomm QDloader 9008 in Windows.

Finally, someone posted a working version of this tool, which can interface with 9008 and reflash partitions/get me to Download Mode. From there, I KDZ'd to stock 39A.

It feels surreal, because I gave up all hope a few weeks ago and upgraded to a G3. Then I bricked that haha
[Verizon LG G2] stelthy77:
Hey guys,

I am trading in my phone for a new one and want to restore this thing to factory before I do that. Is the fastest way to do this the volume down + power button method?

I have spent the last hour looking and searching to see if this is safe and will work, but can't find anything definitive...

I am literally going to do this right before I hand it to them, and need it to boot to stock and just work, I have already backed everything else up.

Thanks for your help.
[Verizon LG G2] HueyT:
Yes, KDZ to stock using "Download mode". It will be unrooted, stock like it came out of Verizon store. All your data will be gone also: https://www.youtube.com/watch?v=kcFtnZZ7I1U and http://xdaforums.com/showthread.php?t=2797190 :good:

39A (Lollipop) KDZ image: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW809NS032ENA4D1C360LR7/VS98039A_05.kdz

USB driver for Windows: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
[Verizon LG G2] viper909:
So I've got a funny thing to report, maybe it will help sort out the cause of these soft reboots.

I've been running the 39A-based 3/21 nightly for over two weeks now, which I updated to from a previous nightly by flashing the 39A bootstack, flashing stock, getting a GPS lock and testing all sensors, then backing up sensors and EFS. Everything was working perfectly, without a single soft reboot or sensor problem, but after coming back from a short trip to Canada where I was roaming on a different network, I had issues getting back on Verizon. I flashed my EFS backup, which fixed the network issue, but ever since then I've started getting about one soft reboot a day.

I'm guessing the cause of the reboots is the same as everyone else's, but it's funny to me that it only happened now, after flashing a backup of the EFS partition. I might try reflashing stock, then restoring to my CM backup to see if that fixes it.
[Verizon LG G2] stelthy77:
Thanks for this, the only problem I am having now is I can't get in to download mode, keeps going to fastboot...
[Verizon LG G2] da_reeseboy:
I stopped having soft reboots after I switched GPS to device only.
[Verizon LG G2] z0mghii:
Can anyone link a 12b based rom? I'm looking through xdabbeb's rom's and they're all based on 26/28
[Verizon LG G2] jacob019:
Has any progress been made on the VOIP audio problem where everthing sounds slow and robotic? I tried CM12 a few weeks ago and loved it but the audio probem was a deal braker as I need voip for work.
[Verizon LG G2] :
Supposedly, this fixes it.

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

There's an option to download the changed patchset. you can take that file, rename it audio_policy.conf and copy it into your /etc folder.

If I could ever manage to get a build going where the sim is recognized, I'd put on up with it built in. But I haven't managed to do it so far, though admittedly, I stopped trying for the last week or so.
[Verizon LG G2] jacob019:
I tried it, and while it does solve the robot voice problem all calls are on speaker-phone all the time.
[Verizon LG G2] :
Weird, that's what's being used for blisspop now as well and haven't seen anyone report the same there. Might have missed it though. Maybe there's another part that needs to be changed as well.
[Verizon LG G2] steveo17:
Me too!
[Verizon LG G2] jacob019:
Thanks for pointing me in the right direction. I'll think I'll just have to tweak that file a bit.
[Verizon LG G2] edikukraine:
For ppl with the charging issues, I was able to find find my original charger and cable and it changed my charging from 6 hours on LP to abt 1.5hrs.
[Verizon LG G2] markymark567:
Im jealous, I only usemy stock charger and I see 8+ hour charging times. It will charge fine when I first plug it in then at some point the phone acts like the cable is unplugged and replugged (even tho it's not) then drop and complain about using the stock charger. This seems like a hardware issue with my plug but it worked perfect before updating to 39a on Sunday, so I'm not sure
[Verizon LG G2] xI mEzMeRiZe Ix:
I'm on the 3-4 build and having tons of multitasking issues. I get launcher redraws all the time, my background music/audio gets killed if I load a webpage in Chrome, SwiftKey will randomly close in the middle of me typing, switching tabs in Chrome causes every page to reload, etc

I reported this issue before and was told to remove VIPER4Android and that seem to have worked for a while, but now my issue is back. Is there any fix for this or is it due to the memory leak in 5.0?
[Verizon LG G2] z0mghii:
I've been having these problems on all builds, even on stock 5.0. I just switched to Euphoria 5.1 and it's been A LOT better. There's a few bugs like double tap to wake doesn't work, and a reboot every now and then, but 5.0 is a mess.
[Verizon LG G2] xI mEzMeRiZe Ix:
Gotcha. It's really making me consider downgrading to JPC's CM11 build from November. That was rock solid and I never had any issues with it.

Does anyone know if I can just wipe my current CM12 setup and do a straight clean flash of the CM11 build? I used xdabebb's 26A bootstack when I was on CM11 and am still using it on CM12, if that matters at all.
[Verizon LG G2] z0mghii:
You should be fine to just wipe and flash. If your sensors aren't working after the flash, just flash xdabbeb's 4.4 rom, verify sensors are working, and flash back.
[Verizon LG G2] xI mEzMeRiZe Ix:
Great, thanks. Hopefully get to it this weekend.