yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] Marine6680:
Well... If cm12 is running well, I may try it.
[Verizon LG G3] jdgesmlls:
If you look at the OP, yes that is correct there will be no more CM11 updates by [MENTION=2385005]invisiblek[/MENTION]. If you still want to sustain your CM11 setup, I recommend PAC ROM 4.4.4. It dirty flashes find over CM11 and has a ton of options.
[Verizon LG G3] Creed14:
Does anyone have a download link for this anymore? I want to stay on a KitKat based ROM until Xposed is working better with Lollipop.
[Verizon LG G3] NewtoneMr:
Hello I have a question:

Does the FULL HD or HD recording work in 60 frames (as is the case with original software)?
[Verizon LG G3] touche112:
holy **** dude you revived a two year old thread haha
[Verizon LG G3] motrue:
Did you find a link to this rom?
[Verizon LG G3] undeadking:
I think I still have a copy of this and many other G3 roms on my Mega cloud storage if you are interested PM me...

I've got CM11, OSE 4.4.4, FLEX OS 5.1.1, Bliss 4.4.4, Euphoria 5.1.1, and Resurrection Remix 5.0.0. All for VS985
[Verizon LG G3] motrue:
Still looking..
[Verizon LG G3] jerryspring:
Could I have some too? Pulled this phone out of the drawer. Haha
[Verizon LG G3] undeadking:
3 years later? Lol Let me check my cloud storage and see if I might have them still(getting out of prison 9 months ago and realizing that the spiteful ex girlfriend deleted almost all accounts or changed all my passwords kinda screwed me up... I'll message you when I get a minute and get things gone thru. Thanks
[Verizon LG G3] jerryspring:
It's ok. I sold the phone....but, posting could help others.
[Verizon LG G3] RPelham:
NP, we all started where you're at. Any time you flash an AOSP ROM (non-stock), you have to flash a gapps package. CM11 = kit Kat, so any KitKat gapps will be good. I think there might be one in the OP.
[Verizon LG G3] 92slammer:
i get a com.android.phone FC everytime i try to install it...suggestions...yes full wipe BTW
[Verizon LG G3] scy1192:
I had this too. Factory resets didn't work. It only started seemingly randomly though, so I was without access to a computer at the time. Reset and flashed LiquidSmooth which seemed to work, but CM wouldn't. I'm going to try the 11-28 build.
[Verizon LG G3] 92slammer:
same issue with 11-29 build
[Verizon LG G3] alpha25100:
I had this issue with 11/28 build.
[Verizon LG G3] mwest316:
Just an FYI. The newest nightly showed available on my phone for 11/29. I downloaded and it brought me to recovery where it automatically updated. When it booted back into the phone it went thru the optimizing apps screen and everything worked perfect. Very happy to have nightlies
[Verizon LG G3] cubsf4n:
Where do we find the change log at?

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

Is there somewhere to look for OTA updates?
[Verizon LG G3] ohlin5:
Question based on that then - what recovery are you currently running that worked perfectly? I only asked because somewhere I swear I read that CM's auto updater wasn't compatible with Philz's recovery.
[Verizon LG G3] mwest316:
Go to about phone. There will be CyanogenMod updates section

---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------

I still use twrp 2.8.0. After it downloaded it went straight to that recovery and did it's thing
[Verizon LG G3] invisiblek:
cm updater should work with this philz:

http://www.invisiblek.org/recovery/vs985/recovery_philz_6.58.9.1_cwmtheme_vs985.img
[Verizon LG G3] jdgesmlls:
FWIW... I started running the 11/23 & 11/26 unofficial builds, downloaded the first official build from 11/28 and manually flashed in TWRP 2.8.0.0. All were dirty flashes. I went through the update in Settings -> About Phone -> CyanogenMod Updates for the 11/29 nightly and it downloaded, rebooted my phone into recovery, installed the new build and rebooted (wiping cache and dalvik). All builds have been rock solid, and the only FC I got was for settings 1 time.

I have been switching back and forth between Beans StockRooted 11C build and trying out new kernels etc. I haven't run into any issues that would make me consider dumping the ROM as of yet. I can't say anything regarding the compatibility of Philz recovery and this ROM but TWRP is working beautiful. I have flashed almost every AOSP ROM to try it out and switching back and forth has given me no issues. I would say if you are not planning on flashing CM12 (which requires Philz) then stick with TWRP. Although with Flashify, it is simple to change between the two. Or you can use adb which is only a few commands, and good experience.

---------- Post added at 04:06 PM ---------- Previous post was at 03:45 PM ----------

Does anyone know if there is a preferred CM modem to use with these builds? I have tried the 10B and 11C modems and my signal doesn't seem as good as when I was running stock based.

The baseband version is showing "Unknown" but it has been that way for every version that I have run.
[Verizon LG G3] invisiblek:
OEMs hack in framework to make it look like you have better signal. Don't pay attention to the bars, pay attention to the numbers in settings.

I'll get the baseband fix in right away, I must not have backported it from cm-12.0 (its purely cosmetic)
[Verizon LG G3] ohlin5:
Ok thanks! So does that mean that it will likely NOT work with the other philz available within your recovery folder? (That's the one I currently have installed haha :))
[Verizon LG G3] Noobla_Khan:
CM Updater did not work for me with the "other" Philz in his folder. I'm running the CWM from his folder and it is working great. Updates are installing perfectly.
[Verizon LG G3] jdgesmlls:
No worries and thanks for the info! If I have to go 2 menu levels deep to show mis-information I am doing OK... :good:

I just walked around my house and I am getting -106 <-> -107 dBm which is just my area and poor cell signal.
[Verizon LG G3] david1985:
hey using a verizon g3 with tmobile i can't seem to get sms working with this rom it works with the other......when I go into hangouts there's no apn settings i have no issues like this with other roms just cm 11 and cm 12 thanks
[Verizon LG G3] 92slammer:
Well....I'm stumped. I installed one of the unofficial files....had com.android.phone FC. Did a factory reset from backup&reset option. Let it reboot and it fixed it....installed the newest nightly....same thing...phone FC. Did another reset and booted. Fixed it installed all my apps..did a reboot and now phone FC again. All other aosp Roms do fine....just doesn't like CM...suggestions
[Verizon LG G3] leeharvey42:
Any way I can put stock camera instead of the one thats on it?
[Verizon LG G3] Big0013:
I really love this rom! My phone has an issue running asop 4.4.4 roms though. I can't seem to get a GPS lock. I'm using twrp recovery and was just hoping to find someone that may of had the same issue that might have a solution any help would be greatful. I've used cm12 and GPS works fine along with stock.
[Verizon LG G3] VinceOB:
I installed the latest nightly, but i couldnt do it i had to go back to stock. Something about AOSP i just dont like. Oh well, not saying its bad. It actually worked well, but i prefer stock.
[Verizon LG G3] cubsf4n:
The sensor issue during calls is still plaguing me. Will a log help you troubleshoot?
[Verizon LG G3] snowcraig:
Does anyone know if the quick circle case works with this Rom?
[Verizon LG G3] jal3223:
Has the sharpening fix been migrated into current builds?
[Verizon LG G3] jdgesmlls:
What is you ROM/Kernel history? This problem sounds kernel related. It sounds like you have already started from scratch so to speak, have you tried flashing back to stock with the LG Flash Tool using the TOT method? I never took an OTA since I have had my phone, always had 10B rooted, and went to BeansTown 11C and AOSP ROMs from there... None of this may apply but when in doubt, look for the unexpected... Good luck.
[Verizon LG G3] droidkevlar:
Getting a logcat will help find the cause of these issues. If not familiar with it, just google logcat android and it will point you in right direction.

Stock camera will not work on her due to framework.
[Verizon LG G3] annoyingduck:
Anyone know why the long press of recents option is greyed out? Kind of a bummer, wanted to avoid running gravity box..
[Verizon LG G3] latincs:
Bluetooh/Android Wear

Thank you for this great Rom and official nightlies. I tried last unofficial build and the 11/28/14 official nightly and I could not connect to my moto 360 via bluetooth. Besides flashing the new version is there an extra step to fix the bluetooth?.. I am making clean installs of the Rom. I read that bluetooth and connection to android wear devices is working fine.
[Verizon LG G3] FreakingThomas7:
Lockscreen

The lock screen slider shortcuts are only limited to a few apps. Is anyone else having this issue?
[Verizon LG G3] scy1192:
Relevant portion (this NullPointerException is what shows when you tap "Report" on the "com.android.phone" dialog):

Line 4607: V/Zygote ( 4249): Switching descriptor 34 to /dev/null
Line 4609: V/Zygote ( 4249): Switching descriptor 9 to /dev/null
Line 4615: D/ActivityThread( 4249): handleBindApplication:com.android.phone
Line 4617: D/ActivityThread( 4249): setTargetHeapUtilization:0.75
Line 4619: D/ActivityThread( 4249): setTargetHeapMinFree:2097152
Line 4621: V/PhoneApp( 4249): onCreate()...
Line 4633: D/MccTable( 4249): updateMccMncConfiguration: mcc=310, mnc=4
Line 4635: D/MccTable( 4249): getLocaleFromMcc to en_us mcc=310
Line 4637: D/MccTable( 4249): getLocaleForLanguageCountry: skipping already persisted
Line 4639: D/MccTable( 4249): getLocaleForLanguageCountry: X locale=null
Line 4641: D/MccTable( 4249): updateMccMncConfiguration updateConfig config={1.0 310mcc4mnc ?locale ?layoutDir ?swdp ?wdp ?hdp ?density ?lsize ?long ?orien ?uimode ?night ?touch ?keyb/?/? ?nav/? themeResource=null}
Line 4647: D/IccSmsInterfaceManager( 4249): IccSmsInterfaceManager: initDispatchers()
Line 4653: D/MockSmsReceiver( 4249): Registered MockSmsReceiver
Line 4655: W/dalvikvm( 4249): threadid=16: thread exiting with uncaught exception (group=0x415c5ce0)
Line 4657: E/AndroidRuntime( 4249): FATAL EXCEPTION: CdmaInboundSmsHandler
Line 4659: E/AndroidRuntime( 4249): Process: com.android.phone, PID: 4249
Line 4661: E/AndroidRuntime( 4249): java.lang.NullPointerException
Line 4663: E/AndroidRuntime( 4249):	at android.telephony.SmsMessage.getOriginatingAddress(SmsMessage.java:553)
Line 4665: E/AndroidRuntime( 4249):	at android.provider.Telephony$Sms$Intents.getNormalizedAddressesFromPdus(Telephony.java:1176)
Line 4667: E/AndroidRuntime( 4249):	at com.android.internal.telephony.InboundSmsHandler.processMessagePart(InboundSmsHandler.java:742)
Line 4669: E/AndroidRuntime( 4249):	at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:371)
Line 4671: E/AndroidRuntime( 4249):	at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
Line 4673: E/AndroidRuntime( 4249):	at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
Line 4675: E/AndroidRuntime( 4249):	at android.os.Handler.dispatchMessage(Handler.java:102)
Line 4677: E/AndroidRuntime( 4249):	at android.os.Looper.loop(Looper.java:136)
Line 4679: E/AndroidRuntime( 4249):	at android.os.HandlerThread.run(HandlerThread.java:61)

Rest of the log is attached, had to zip 'cause it was too big
[Verizon LG G3] digitallure:
I had trouble with my sd card not showing up , so I reverted back to stock. I even used the sd card fix app. Any way to resolve that issue?
[Verizon LG G3] jdgesmlls:
First guess would be how is it formatted, what size and were you using any type of encryption on stock. When you talk about "sd card fix app" are you speaking of the fix in platform.xml for external sd? That doesn't apply to this ROM, and if that was your issue you should be able to see the sdcard in Setting -> Storage but not be able to copy files to it. Check to see if you did anything in Settings -> Security -> Encrypt SD card storage on your stock ROM.

I have seen several posts where the formatting makes a difference on larger cards. I have a 32GB Samsung EVO and it is seen in r/w perfectly.
[Verizon LG G3] digitallure:
I have a 64 GB card. Formatted as FAT32. It shows up fine on stock. I have my titanium backup on the sd card and the card wasn't recognized on cyanogenmod. The card isn't encrypted.
[Verizon LG G3] annoyingduck:
That could be anything... Is it not seen by titanium or is your original backup location not seen? The location is different from stock to aosp, go to preferences, backup location, and tap detect, then when it finds it tap choose current location. My 64g card, fat 32 format is working fine here.
[Verizon LG G3] Ryano89:
ART... Can I do it?

I'm loving my first experience with Cyanogenmod, I Just switched over from Cloudy, which was my first time on a custom rom, and I'm wondering if I can switch to ART while running Cm. I don't really need to do it, everything is running very well as is, just wondering since it worked on Cloudy. I'm curious if anyone knows.
[Verizon LG G3] ohlin5:
I haven't tried it, so I can't say for sure - but if you are using any xposed modules then be aware they will not work with art as xposed is not compatible with the art runtime right now. That's my biggest reason for avoiding it right now, is because the two main advantages of 4.4.4 right now as opposed to 5.0 are stability and the ability to have the additional customization options that xposed affords. Just my humble opinion :) You could always take a backup, and then try it and post back letting us know your experience! ;)
[Verizon LG G3] Ryano89:
Yeah, I'm running xposed, but I'm only using greenify with it right now. I may give it a shot tomorrow just to satisfy my curiosity, but then again, everything is going great right now so maybe I shouldn't rock the boat.. Lol
[Verizon LG G3] zakkyzombie:
If you have xposed installed and try to switch it will default back to dalvik. Basicly, you have a really long ass reboot for nothing

Sent from my LG G3.
[Verizon LG G3] 117micc:
Just wondering but how is xposed running on cm11? I have tried it on a few other rounds and as soon as I out it on and get my phone set up, my Wi-Fi stops working, then this black screen pops up saying my kernel crashed etc... :-\
[Verizon LG G3] jdgesmlls:
Great point annoyingduck! I just wanted to add from my experience with TiBu and using the detect feature that it seems to find the local sdcard directory first and gives that preference. I have had to manually set my backup location (which for this particular ROM for my external microSD was "sdcard1") and TiBu needs to exit and restart before recognizing the external microSD as the backup location.
[Verizon LG G3] Ryano89:
Fine so far, but it's only been about 24 hours. No bugs to speak of, in the rom or xposed( haven't tried Bluetooth or hotspots yet).
[Verizon LG G3] touche112:
I am getting constant com.android.phone FCs, making the handset unusable. Occurs on all nightlies. Literally constant - you click OK and the next one pops up. Anyone else experiencing this?

---------- Post added at 10:06 AM ---------- Previous post was at 09:56 AM ----------

Same thing here. I can run any ROM, except for CM. Identical logcat, as well.
[Verizon LG G3] droidkevlar:
Are you guys wiping system as well before installing the ROM? Only reason I ask is cuz I am not having this issue and have ran this and many other AOSP type ROMs.
[Verizon LG G3] 92slammer:
same here.....complete wipe including system
[Verizon LG G3] cubsf4n:
Crazy. All is good here but when I ran Liquid I would have that happen a few times a day.
[Verizon LG G3] mwest316:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:

I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.

I downloaded CM and Gapps to root of my internal SD storage

I chose to Wipe in TWRP

I chose Advance Wipe

I picked every option except for Internal Storage and External SD Card/Storage

I then Wiped

Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)

I then go back to wipe main screen and slide to do the standard wipe, 3 times

Yes, this is probably overkill!

I then go to install in TWRP

I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/

Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions

I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot

Installed Xposed, and the modules needed, reboot

I never received any error

I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.

I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use

Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.

Hope that helps.
[Verizon LG G3] MetroGnome711:
I follow this procedure

This has been my procedure for awhile now as well and I can confirm no errors either. I had to fix APN's as stated and I don't know what you mean by set WiFi to US, (I had to do an SQL value change) but tether, MMS, wifi, BT (media and calls) All work on the 11/30 build after plashing the 28 build then updating through About Phone>CM Updater>Nightly Build

The only nitpick error i've got is that the phone doesn't recognize when it's charging. The LED light comes on and the icon changes, but the lockscreen doesn't say charging and the screen won't stay awake (or turn on when first plugged in).

And sometimes the wallpaper misses the bottom of the screen, but that could a CM theme issue.

No complaints here!
[Verizon LG G3] Ryano89:
So I am new to Cm, everything has been good, but I can't get my pc to recognize my phone when I plug it in now. Is this operator error, or a bug? Thanks to anyone who can help worth the noob question
[Verizon LG G3] mwest316:
Settings > WiFi > Advanced > Wi-Fi Region Code. Choose United States.

Same here on the charging, I just make sure the circle battery is spinning with the charging bolt in the middle before I walk away. The screen comes on when I unplug though.
[Verizon LG G3] ohlin5:
I have not had any deal-breaking issues with my device either, but I just had to say A+ for the n00b-proof instructions. Great, detailed step-by-step walkthrough for those newer to flashing :)
[Verizon LG G3] epicroot:
What ate you fixing in apns
[Verizon LG G3] mwest316:
Just to be proactive, I reset all apn info in the APN Settings. I then click the last Verizon apn with internet underneath it. Make sure these are input in their respected sections:

MMS Port 80

MCC 310

MNC 012

Click save, then of course it will disappear which means you now have working MMS.

---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------

Thanks. I know that when I first started flashing I needed help and stayed a lurker for a long time until I decided to sign in and ask questions. I figured that guide was the best thing I could do without actually making a video:D
[Verizon LG G3] epicroot:
Guessing there wasn't a nightly for today :/ ahh I will survive
[Verizon LG G3] igloohed73:
Experiencing exact same issue. Had similar problem on the only other AOSP ROM I flashed. Followed standard wipe & flash procedure on both accounts. Didn't occur immediately but within an hour or so of initial use.
[Verizon LG G3] Ryano89:
Anyone? I have drivers installed, and my PC was recognizing it fine when I was running cloudyG3. But now on the CM nightlies, I cannot see the device showing up at all, unless I connect as a camera, which of course does me no good. I am sure that I am just making a stupid mistake, but I sure cannot figure out what it is...ugh
[Verizon LG G3] 117micc:
Do you have usb debugging enabled?
[Verizon LG G3] Ryano89:
Yes, in developer options I have android debugging selected. Is there any other setting that I should be looking at? It says "connected as a media device", if I switch it to camera, then I the phone shows up but I cannot access any of the files that I want to get to.
[Verizon LG G3] goldsmitht:
forgive if you have already done this, but try switching USB cord. sometimes... this is all it is. mine will balk sometimes when i have a different cord when charging

just a suggestion

:cyclops:
[Verizon LG G3] Ryano89:
Thanks for the suggestion, that did not do it though. I feel really stupid that I cannot get this to work. Like I said, it recognizes the phone when set to PTP, but not when I switch it to MTP. I HAVE to just have a setting wrong or something, but I am stumped.
[Verizon LG G3] thedanks:
i too am plagued with this conundrum.
[Verizon LG G3] PiousInquisitor:
You need to find out what is causing the issue (ROM, driver, cable, or USB port). You need to try different combinations of computer, cable and usb port. Also try reinstalling the drivers.
[Verizon LG G3] kaptain120:
I lost my connection to 4g lte. Any suggested fixes?

I lost my connection to 4g lte. Any suggested fixes?
[Verizon LG G3] ohlin5:
Is anyone else experiencing the bug where the expandable volume panel "loses" its ability to expand - it loses the normal "expand" button on the right hand side and just acts like single volume changing style? That, and the proximity screen issue post-game are about the only real consistent bugs I'm having with this rom. Otherwise it's running rock solid, so thank you so much!
[Verizon LG G3] endfro:
I also lost my LTE connection. I compared APN's to people on Verizon and all the settings are identical, also attempted wiping cache/dalvik. This started on the 11/30 nightly and still persists on the 12/03 nightlies. Any advice would be great as it could be a couple of months before I move to CM12. Thanks in advance!
[Verizon LG G3] droidkevlar:
So I had same issues as you guys. Here is what I did. It might be overkill, but it got everything working. I uninstalled all LG G3 drivers that were already installed, I also removed universal ADB drivers too. Rebooted desktop/laptop. Went into PTP mode after reboot and then uninstalled and deleted drivers. Unplug phone and reboot phone and desktop/laptop. Select MTP before plugging into computer and then go into device manager and you should see VS 985 with a yellow ! on it. Right click and hit Update driver software. Then select Browse my computer. Download the files from this post http://xdaforums.com/showpost.php?p=56631767&postcount=3 and unzip. Then select this folder for the drivers and should be all set. It took me some time of going back and forth and trying diff things, but this is what ended up working for me. This is on a Windows x64 machine.
[Verizon LG G3] Ryano89:
So here is a new one, I followed these instructions, and when I go to device manager, my VS985 shows up as "Acer Device". WTH? When I change it to PTP, it shows up correctly in my file explorer, but in Device manager it still shows incorrectly. I have absolutely no idea how that happened. I am currently on the unofficial CM12 build, but this problem first showed up on CM11 nightlies. Any Ideas? Or did I just "invent" a new bug? lol
[Verizon LG G3] droidkevlar:
No idea on the CM12 part as I have not ran any Android L builds yet. I would recommend posting in that thread and showing screen shots if possible to get better assistance.
[Verizon LG G3] touche112:
I guess no one has a fix for this FC problem yet? I'd like to get off CM12 and back to CM11, being it's official and doesn't have bad battery drain. I loved the nightlies while they lasted...
[Verizon LG G3] 117micc:
Ok big question... Out of no where I got com.android.phone force close over and over, I had to reboot into recovery full wipe and reinstall to get it to stop. what could be causing that?
[Verizon LG G3] jlvlawrence:
I had that problem happen twice. I ended just restoring my stock nandroid. Several others have had the same issue as well.
[Verizon LG G3] dewhashish:
Phone connects to my G watch then immediately disconnects.