yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] SquireSCA:
Me too, love that app,

Also, does Netflix work for anyone? I can't get it to work...

So far my impressions...

1) Not as fast or smooth as the stock ROM.

2) Netflix was working on the stock ROM 30 minutes ago, cannot connect now, and it is not Netflix as my PS3 and my Girlfriend can connect to it right now.

3) QuickRemote doesn't work(but we knew that going in)

4) Knock-ON works, but you cannot tap the screen to turn it off. Not sure why one works but not the other...

And yes, for some reason this phone takes FOREVER to do factory wipes, even clearing cache that takes 8-10 seconds on any other phone, takes 1-2 minutes on the LG G2, but that is not a CM issue...
[Verizon LG G2] luv2increase:
Wow! You've got to be kidding me. There is NO lag with this ROM and this phone. This is the only time since I've been using Android since the beginning where I have for the first time a completely smooth and stutter, lag free.

You must be doing something wrong.
[Verizon LG G2] mbh87:
No IR does not work. For Netflix it says right in the OP that it doesn't work.
[Verizon LG G2] lexdad86:
I emailed the developer of smart remote about the possibility of getting smart remote to work with our phones and this is the reply I received....... Unfortunately the*LG*has their communication with the infrared sensor private and we would have to go through their app and use their database which is something that would introduce many other problems , not to mention that the app would be half ours and not having control over the database would mean not having control over what users need .

If their policy will change we will definitely take this into consideration .
[Verizon LG G2] Reginald476:
1) I have not noticed this, is there anything that is increased on battery, CPU usage? I have to think this app based. The ROM is more fluid than stock for me.

2) As others have said this is in the OP

3) I keep hoping Smart iR adds support for our device

4) This is the state of all AOSP or CM based ROMs so far, I think it is still being looked into.

This is an issue with TWRP and has nothing to do with the ROM, remove the format with rm -rf from advanced and see how long it takes.
[Verizon LG G2] polaric:
Is this ready for a daily driver yet? From what I've seen the amount of complaints with issues has decreased in the last few pages. The biggest thing for me from the OP was the 3G roaming issue, is it still around?
[Verizon LG G2] TheBiles:
I think it's absolutely a DD. I have yet to go into 3G coverage, but everything else has been great. No issues so far.

Sent from my G2
[Verizon LG G2] HeXaLox:
It's a first run of literal beta tests, hence nigntly...and just wait for a stable ROM until then use the other ROMS that are available. :silly:
[Verizon LG G2] polaric:
Of course its a nightly, its going to have bugs. I'm more concerned over the 3G roaming issue, I get knocked into 3G pretty often where I am. I'll flash it as soon as thats cleared up. Anyone who has a CM G2 seen the 3G issue lately?
[Verizon LG G2] cheami:
I haven't lost LTE in Tampa, FL since the 10/24 nightly.
[Verizon LG G2] markcyst:
Only big bug that I've noticed is the previously mentioned bluetooth and wifi nastiness. But there's nothing that stops this from being a great daily driver, better than the last 3 months of CM on the gnex!
[Verizon LG G2] Reginald476:
Even dropping into 3G I don't have any issues with roaming after the 10/24 nightly.
[Verizon LG G2] polaric:
I'll flash it and see how it goes. Cyanogen on another great phone.

Sent from my awesome VZ LG G2
[Verizon LG G2] psycho_asylum:
Can confirm. I live near mountains, so I get kicked into 3G all the time. I've been using this as a DD since Thursday. You'll also want to set your governor to interactive instead of ondemand or you'll get hard locks when your phone goes to sleep. I was getting about 6 in a day but I'm down to maybe 1 a day.
[Verizon LG G2] TheBiles:
Did someone say battery life?

Sent from my G2
[Verizon LG G2] ppeklak:
12/14 for me was stuck at the boot logo. Had to restore to 12/13
[Verizon LG G2] seang:
i got 1214 to boot, SMS would FC.
[Verizon LG G2] gr33nd3vil:
Not happening for me ;) But I can say this, if your on any CM version over 12-12-13, use PA Gapps 12-12-13. =)

As for the wallpaper issue I don't have that issue, but I don't use Launcher3.apk

---------- Post added at 11:06 AM ---------- Previous post was at 11:06 AM ----------

Clean flash, 4.4.1 to 4.4.2 caused issues for most.
[Verizon LG G2] Buddyfunlove:
I am on the kitkat launcher but I didn't know pa had a newer gapps out. Good show! ;) thanks!
[Verizon LG G2] spiicytuna:
This happened to me until I updated twrp 3.6.3.3 from 3.6.3.2.
[Verizon LG G2] ppeklak:
I'm running CWM
[Verizon LG G2] TexasRules777:
I've got a weird one. Every time I install a nightly and dirty flash it I'm not able to add a widget to the gel launcher screen. I have a transparent genie widget that is overwritten by the one that comes with the ROM. I push it to system/app..change permissions and reboot. Then when I push on the main screen and select widgets I get a " unfortunately Google search has stopped working" message. It's not just that app but it won't let me add any widget..I don't have time to select anything before I get that message and it goes back to the main screen. The only way I can get it to add widgets again is to clean flash everything again. Not really an optimal way to flash nightlies.. Anyone using the gel launcher have this issue? My Roms are stock with nothing added or removed. Don't wanna really set up my phone if I just have to factory reset every time a new nightly comes out.
[Verizon LG G2] Buddyfunlove:
What gapps are you using?
[Verizon LG G2] jordanl17:
Any solution to random Unknown Issue with Google Play Services? Sometimes a reboot fixes it. I just flashed the new PA 4.4.2. I think that's when it started happening.
[Verizon LG G2] TexasRules777:
The new pa 12 12 apps..it's done it with all gapps I've used though. It's been doing this since the first unofficial nightly.
[Verizon LG G2] Buddyfunlove:
That is strange... Are you going into recovery and wiping cache, then flashing or just through installer? Obviously if you wipe everything you go there...but for when you try just to update ...

Generally that happens when loading system apps over system apps too. When you restore apps do you have system apps backed up or just user apps?
[Verizon LG G2] bL33d:
FYI the volume boost is way to high but if u use the back to stock version it boosts the sound about just the right amount.
[Verizon LG G2] soapinmouth:
Having a freezing issue on 12/14 device randomly becomes unresponsive for minutes at a time. Reverting to 12/13 fixed it. Any ideas?
[Verizon LG G2] TexasRules777:
Yea I'm wiping manually (dalvik,cache) then flashing the update. I've also flashed gapps and not flashed gapps to see if that was an issue. I'm not restoring anything or backing up my apps in any way. If I clean flash I just let my apps auto DL from the play store. I was able to dirty flash the 12/14 over the 13th and it did work..but the clean 13th install I hadn't set up really, just signed into gmail to activate, let my apps DL, then flashed the 14th over that..then I could add widgets.
[Verizon LG G2] Napa7m:
I dirty flashed 12/14 using the CM updater and haven't seen any major issues.

YouTube is fixed. I do here a funny knock-knock sound when making calls sometimes, but it's not a big deal. The volume seems very loud too.
[Verizon LG G2] kei6193:
Cleaned flashed 12/15.. Sms works
[Verizon LG G2] ppeklak:
how about GPS?
[Verizon LG G2] socom36252:
where are the gapps for this rom? i dont see them anywhere? are they included?
[Verizon LG G2] plcdude:
Odd issue with CM11 and Android Device Manager

Android Device Manager features have not worked with my G2 since I updated to CM11. Today I reverted to a CM10.2 backup that I had and Android Device Manager features worked correctly. After restoring back to CM11 Android Device Manager features were broken again (locate and ring do not function). I even did a full wipe and install of CM11 still Android Device Manager Features were broken.

I then investigated the Google Dashboard information for my Android devices. Oddly enough there are two (2) entries under Android devices for my G2. One of the entries is identified, in Android Devices, with an MEID that is actually the IMEI for my G2 it is this entry that is somehow associated with my CM10.2 install, the working install. The second entry for my G2 is identified, in Android Devices, with an MEID that is actually the correct MEID for my G2. It is this second entry that is associated with my CM11 install, the broken install.

I am fairly certain it is the two (2) conflicting entries in the Dashboard, Android Devices, that is causing my issues with Android Device Manager under CM11. I have had this problem with all nightlies of CM11. I am currently running the 12/14 nightly.

Unfortunately, there is no way, that I have been able to find, to remove or edit devices from the Google Dashboard. Does anyone here have any suggestions or recommendations?

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

http://xdaforums.com/showthread.php?t=2397942
[Verizon LG G2] koboltzz:
Nothing is odd with CM11 and Android Device Manger. You have to two VS980 listed there, because your LG G2 StockROM (4.2.2) was once registered with your google account. Now you have a new phone, the G2 CM11 (4.4.2) thinks google. Therefore a second entry will be shown.

Next: Everything works with CM11 and Android Device Manger, if you set location to high performance. Only with this setting, google has access to your device. This is the new way KitKat behaves.

So please no huge (fake) bug reports here, this you get to know yourself if you first do a search in the internet. Thx.
[Verizon LG G2] polaric:
Is it me, or does the volume seem very high on the 12/15 build?
[Verizon LG G2] gr33nd3vil:
Anyone getting random reboots / sods?
[Verizon LG G2] BOY_:
That's a good thing
[Verizon LG G2] drtchocky:
I got one or two random reboots.
[Verizon LG G2] bL33d:
Last 2 night lies seem awesome to me :)
[Verizon LG G2] Buddyfunlove:
I agree. I have had to forgo ART though. Was starting to have lots of reboots and the reboots were not without complications.
[Verizon LG G2] jordanl17:
I'm enjoying these last couple builds. Feels like progress towards snapshot release. Battery life and speed are great. But I used to get one reboot every two days, now I get 1 or 2 reboots a day.

I don't run ART yet.

Ive used the standard CM updater since unofficial cm11. I may be due for a clean flash.
[Verizon LG G2] polaric:
Generally, though its not confirmed, but clearing the cache does seem to reduce the average amount of reboots. Again, not confirmed, and they dont go away, but its been reported to help on many occasions.
[Verizon LG G2] bL33d:
tried to use aosp lg remote mod but my phone just boot looped :/
[Verizon LG G2] Buddyfunlove:
Lol, I shall avoid this.
[Verizon LG G2] polaric:
Well, I think I just noticed a bug in appolo starting from a clean flash on 12/15. Take a look at the positioning of the scrollbar. I never remember it being that far over.
[Verizon LG G2] gr33nd3vil:
How? Its easy to get work...
[Verizon LG G2] bL33d:
ya i got it :silly:
[Verizon LG G2] TexasRules777:
Does anyone know when DSP manager will be active? It's obviously not working yet..does anyone know of any work arounds?
[Verizon LG G2] Polymira:
Is bluetooth stereo working for anyone? The the last couple of nightlys have been bored for me (the phone disconnects from my cars bluetooth as soon as I try and play music over bluetooth). The last nightly that still works for A2DP streaming is 12/13/2013.
[Verizon LG G2] jordanl17:
Tonight, by chance, for the first time on this phone I paired some cheap Bluetooth headphones. Worked great. Listened to some music for about 20 min.

I'm on 12/15.
[Verizon LG G2] kev0153:
Just tried connecting to my car stereo and I get a crash message that bluetooth sharing has stopped working and phone reboots. Just started after the last nightly.
[Verizon LG G2] seang:
yes sir, it was a clean flash.
[Verizon LG G2] gr33nd3vil:
I've noticed that the random reboots come from when using a screen off service, anyone have one that doesn't crash the phone?
[Verizon LG G2] Viper76269:
umm. lock screen widgets?
[Verizon LG G2] geoff5093:
That happened to be last week, so it's not anything new. If you ignore that error it's fine, but your phone is useless.
[Verizon LG G2] gr33nd3vil:
Naw, I use nova launcher, and used "Screen off" from the google play to double tap screen off, but I noticed it causes random reboots.
[Verizon LG G2] Viper76269:
oh i'm sorry. it wasn't related to your issue. i was just saying like where's the lock screen widgets. there's no option to enable them in the security section
[Verizon LG G2] gr33nd3vil:
oh haha, that's in Settings > Lock Screen

;)
[Verizon LG G2] Viper76269:
ahh. thanks. i thought that meant something completely different. on my nexus 5, it was just in security, but i don't know if that was a 4.4.2 change or just CM
[Verizon LG G2] drtchocky:
So I am on the 15th nightly and getting super results. No random reboots since off the charger at 7 this morning. Also, astounding battery life.
[Verizon LG G2] drtchocky:
New Nightly is up.
[Verizon LG G2] TheBiles:
Anyone know what this automatic backup notification is? Clicking it just makes it go away.

Sent from my G2
[Verizon LG G2] tacosrdelicioso:
On the latest nightly I noticed some of the lag was back
[Verizon LG G2] mwolfe38:
Installed the 12-15 official nightly yesterday, did a clean flash as I had originally done a dirty flash from cm10.2 and had a few small issues. For whatever reason I've been getting reboots all day and several Sods. Probably 6 total.

I did have Google glass hooked up for awhile bit most the reboots were when glass wasn't connected.
[Verizon LG G2] z0mghii:
Is anyone getting this bug where right when a notification comes in, the phone will vibrate for a long period of time (say 20-30 sec) then reboot? I'm using ChompSMS and i've also had this in 10.2
[Verizon LG G2] Buddyfunlove:
I have not had that (I use 8sms). Have you disabled the stock messenger? I would suggest trying that.
[Verizon LG G2] ithrewitontheground:
Could be from google+ photo backup. Do you have it set to wi-fi only and never connect to wifi?
[Verizon LG G2] bose301s:
16,004 days is 43.8 years ago, looks like your phone was still reading the 1970 date when it tried to backup.
[Verizon LG G2] datsyuk:
Does anyone know if I can get Visual Voicemail working oncyanogenmod?
[Verizon LG G2] tatootie67:
+1
[Verizon LG G2] TheBiles:
Visual voicemail with Google Voice works. I've never used the Verizon app, so I can't comment.
[Verizon LG G2] sincerity:
about 3-4 times out of the day, no matter what cm11 build I am on...phone won't wake up. just have to hold power down to reboot. Also once in a while a random reboot....always when it starts up again, google play error in notifications. any ideas?
[Verizon LG G2] Buddyfunlove:
I tried to no end to get it to work on 10.2...I am sure 11 has brought us further from success. I finally relented and just used Google voice.
[Verizon LG G2] someotherguy:
Been using nightlies for the last week from the update menu. Last night's won't boot. Using CWM, tried to switch to TWRP as well. Haven't tried wiping yet.

Anyone else try to flash over top and it won't boot?
[Verizon LG G2] gr33nd3vil:
my cm11 build has VZW Visual Voicemail work =)
[Verizon LG G2] desantim:
For the first time on the nightlies for some reason or another, I downloaded the update from the update menu, but decided to TWRP myself and wipe cache/dalvik on my own and install it. So far, and I mean YMMV, so far, the 12/15 release has been the most stable. No SODS or crashes yet. (Fingers Crossed)
[Verizon LG G2] seang:
agreed, i am very cautious about loading another nightly. i made a backup just in case.
[Verizon LG G2] someotherguy:
Decided it try it one more time, this time booting into CWM and wiping dalvik / cache, and flashing manually.

Working now.

Something must have been screwed in cache, does the auto-update script not wipe cache / dalvik, and if not, shouldn't it?
[Verizon LG G2] desantim:
It's supposed to, I never trust it though, and when dirty flashing, formatting cache/dalvik is key (I always wipe them both at least twice for the hell of it). It takes a few extra seconds but saves hours of headache later on, so I figure why not just download it through the upgrade program, reboot to recovery, format cache's and install
[Verizon LG G2] polaric:
For what its worth in contributing to help resolve the SODs, I noticed something today.

-SODs are activated whenever you try to wake the screen, and only then.

-The entire phone freezes, highlighted by the fact that my music playing from Apollo froze when my phone SODed.

-Im not SURE about this one, but Im pretty sure the CPU locks. I was curious, so I left the phone on when it SODed, and after 3 hours it did not even touch the battery, while 3hrs with it in idle normally takes 1-2%.

In the last 2 nightlies there is also a ridiculus amount of SODs, though I could just be having bad luck. I'm getting 6-9 per day.
[Verizon LG G2] bL33d:
been updateing cm11 threw built in updater since preview came out and i use to have sods but not had any since last 2 updates.
[Verizon LG G2] WCM3:
So I flashed the 10.2 perfectly fine. Used it for a day or two and it worked great. Updated to cm11 through the updater and tried to flash using twrp and it failed. Tried a few times with the 12/15 and 12/16 version and they both failed. Any ideas? Thanks for much for the ROM btw.
[Verizon LG G2] ppeklak:
when do the nightlies usually get pushed?
[Verizon LG G2] Zimeron:
You need at least version 2.6.3.3 of TWRP to flash a 4.4 rom.

Builds start at midnight CST (from what I see on jenkins) and our device name is "vs980" so we're almost last. Depending on if any builds fail or if it's the weekend and they're doing older nightlies as well, it can vary quite a few hours. You can always check jenkins (http://jenkins.cyanogenmod.org/job/android/) and see where the build is at in the queue. Most builds take ~30 minutes and there's normally three build bots going. Additionally, as more devices are added to CM11 (four more were added a few days ago) the further it will push our device back for the day. The best way to approach it is that if there's any show stopping bugs, they've had most of the day from the first nightlies to fix them. ;)
[Verizon LG G2] mepo12:
how do you even update twrp?

i dont have ADB setup on my PC it wont recognize device and goomanager wont work when i try to install the .zip
[Verizon LG G2] desantim:
Download the twrp zip and update via twrp. That's assuming you already have twrp installed.

http://xdaforums.com/showthread.php?t=2561553
[Verizon LG G2] mwolfe38:
Really hoping a better build comes out soon. I must have had at least 10 reboots today. I'm clearing cache/dalvik now, hoping that helps. Did a clean build of12-15 (factory reset first). Yesterday had tons of reboots and probably even more today.
[Verizon LG G2] jasondowning85:
Know how to pull a log?
[Verizon LG G2] soapinmouth:
So idk if it's sods like everyone else is having but I've had random freezes where the device just goes unresponsive in whatever I'm doing. The only way to get back is hard resetting. I've tried clean flashing every build and every build after the 13th has this problem. Is there any way to see a nightly changelog? Is this fixed on the 18th nightly?
[Verizon LG G2] polaric:
I can second, there are a lot of sods. Your not the only one.
[Verizon LG G2] ppeklak:
Does GRAM still work in CM? Is it hardware based or do you need LG's ROM?
[Verizon LG G2] mwolfe38:
Just pull the logs with logcat right? I'm an app developer so I know how to do that. Is that the correct log or do you need some other logs as well?
[Verizon LG G2] jasondowning85:
Being that it's causing reboots, my guess would be that it would be kernel related and it won't be found in logcat as I believe logcat is wiped on every boot. However, I think /proc/last_kmsg will have info related to crash/reboots.

I won't be able to help much, but I guess that what I'm saying is that instead of saying "I hope a better build comes out soon", you should probably ask what you can do to help. Find out who the maintainer is for our phone (vs980) and ask if you can help by providing logs.

Lastly, I was having some reboots as well but I clean installed 12/16 using cm gapps (was using PA gapps before) I have had less reboots myself. I can't really recall one to be honest. I don't know that different gapps helped, but just telling you what I experienced.
[Verizon LG G2] mwolfe38:
Good point, I would like to help. Oddly I've had no reboots yet today and I haven't changed anything. Next reboot that I'm near a computer I'll try and pull some logs. Also maybe I'll try a different gaps as well at some point.
[Verizon LG G2] xian_online:
I just though I should chime in here, because I don't think SOD's are indicative of this ROM.

I started using the Official Nighlies since like the 5th or 6th or something like that. And i've had one, 1 SOD since then, really one. And that was just yesterday on the current 12/16 build, and it eventually woke. I've been updating almost daily for since. I clean flashed on 13 and used cmupdater for 15 and 16. So I don't know what the difference is but I've been impressed how there hasn't been any SOD's. I was on the unofficial before that (rhcp) and never had one.

---------- Post added at 02:28 PM ---------- Previous post was at 02:26 PM ----------

Just wanted to also throw in there, I've never had a reboot, not one ever. I think this bad boy is rock solid, and has been daily driver for weeks along with unofficial. I use it heavily all day for all sorts of stuff, and as I said I've had one SOD in weeks, and no reboot. I've ran several builds of the unofficial and almost every official nighly release. I can't explain the difference, but I'm throwing it out there.
[Verizon LG G2] polaric:
All the non stock Roms have SODs. I said I could just be unlucky, there's a equal amount of people getting sods galore as there are no sods.
[Verizon LG G2] KayIslandDrunk:
Not true. I used to get them all the time on CM but once I switched to PA I haven't had a single one.
[Verizon LG G2] polaric:
If you look through the threads, all the non stock roms have them. Some people are lucky and never run into one, some aren't and have a lot of them.
[Verizon LG G2] bose301s:
Sadly this is the case, and none of the devs really seem to have any idea why, and from what I understand it is specific to the Verizon version, doesn't happen on other models of the phone.
[Verizon LG G2] Lawlrus:
I have had really good luck since I started boosting the min MHz higher than 300.

Even on roms i have had sod's on, they are no longer. Been going strong for three days now.
[Verizon LG G2] steveo17:
I'll have to try this. I've had like 4-5 today!
[Verizon LG G2] ppeklak:
this wasnt working for me...i had tried for 15 min to get a lock on maps...i ended up resorting to a stock rom build...got a lock, then restored back to CM and it locked right away.

anyone have any additional info on how android stores gps sat information? it obviously is stored in a persistent area apart from a ROM. does android connect faster and faster as it stores more information about sats each time in locks with gps?

---------- Post added at 04:29 AM ---------- Previous post was at 04:26 AM ----------

do you use a custom set i/o scheduler or governor?
[Verizon LG G2] jordanl17:
I just switched to ART as Whatsapp now supports it. What should I expect with cm11? Better or worse battery? More or less sods? Or both basically the same?

Edit: after the first 10 minutes, no sods and battery life is amazing. Kidding.
[Verizon LG G2] bose301s:
Tried it, no such luck for me, got one pretty quick.