yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] MaddMaxx636:
OS Soft rebooting/crashing after backing up in TWRP

On the 061615 nightly i backed up my phone in TWRP it backs up 100% perfect but after i rebooted it keeps crashing and soft booting and only runs well for 5 mins max and then it just soft boots/crashes. is anyone else having this problem? Also this needs to be fixed soon!!!
[Verizon LG G3] JuailyLiranzo:
Hey , just installed the rom , perfect, without any problem except with the data , I have to reboot to get it and it is only in LTE and if I'm in a range where no LTE I do not have the data ... any of you with this problem that has been resolved ?

Thanks you, I hope for the answer.
[Verizon LG G3] clapper66:
On the previous page I seen something about trying to fix the AUX problem. A simple fix I found for it is. If you Plug the AUX in and it isn't working. Take the end plugged into your car and pull it halfway out then put it back in but try to do it quickly. Doing this 2 or 3 times in a row seems to trigger something and make it start working.
[Verizon LG G3] ohlin5:
Your post isn't clear exactly what your issue is. If you're saying you can only get LTE (e.g. you can't get any 3G signal), then I'd say your best bet is to clean flash both the most updated radio (23C) and full wipe and clean flash the ROM, cause 3G does work.

If your issue is that occasionally data connection dies (like after coming off of WiFi, for example, you have no mobile data connection), then (I believe) this is a known issue - it happens to me every so often. Resetting apn settings instantly fixes it, otherwise adding the LTE toggle to your quick settings and toggling it off and then back on when you see the issue also fixes it.

---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------

TWRP doesn't write/change any of the OS data, it only reads it and copies it to the backup file, so this doesn't make sense. Go with a full wipe and clean flash of the newest nightly with updated gapps.
[Verizon LG G3] JuailyLiranzo:
It is exactly as you described in paragraph number two , sorry if I didn't explain well, but I already uninstall the ROM and waits for it to come out without that error.
[Verizon LG G3] MaddMaxx636:
Its not doing it anymore. Its working perfectly now since i updated to the 061715 nightly
[Verizon LG G3] zebinadams:
I'm currently running the 6/4 nightly and when I tried to update via the updater, I got an error. "Error executing updater binary in zip". I attempted to update to one of the nighties from last week and got the same sit error. Has anyone else had this issue?
[Verizon LG G3] tpayne2345:
Flash the 23C modem and you'll be good to go
[Verizon LG G3] Troop4Christ:
Facebook App crashes on comment

I recently flashed back to CM12.1 from Mokee. I was on CM12 and switched over to Mokee because I was finding too many issues/bugs in CM12 for the vs985 device.

Everything seems to be working very well now w/ CM12.1 but I am finding one frustrating issue w/ Facebook's app where everytime I attempt to leave a comment on a post, the Facebook app just crashes. I can create new posts, share photos, etc. I just can't leave comments.

Mokee is also running on Android 5.1 and I wasn't experiencing the issue there.

I've tried clearing the app data, uninstalling the app and reinstalling. I even cleared cache and dalvik and re-flashed CM12.1. Nothing is working.

Is anyone else experiencing this issue?

Thanks.
[Verizon LG G3] idkwhothatis123:
I have this exact issue. Its been driving me nuts!

Edit: FB just pushed an update to me and now I can comment lol
[Verizon LG G3] funkatronic:
Is anyone else having trouble installing the Google Clock app from the Play Store? Keeps giving me installation error "-505"
[Verizon LG G3] gotroot801:
Yep.
[Verizon LG G3] maximusmullivan:
You need to delete the old Google clock apk, restart and it will let you install. I did it on dirty unicorn's on my N7. http://www.androidpolice.com/2015/0...r-android-is-now-available-in-the-play-store/ Also...make a nandroid backup first!

Sent from my Nexus 7 2013
[Verizon LG G3] funkatronic:
Thanks, that did it. Will futire CM updates try to reinstall the old one?
[Verizon LG G3] maximusmullivan:
I don't know. Probably not.

Sent from my Nexus 7 2013
[Verizon LG G3] frc3260:
Has the black screen of death been fixed?
[Verizon LG G3] crunchybutternut:
I have not experienced a Black Screen of Death running this ROM. I'm currently on the 6/22 build.
[Verizon LG G3] dan411:
double tap to wake issue

Hi, first time posting in this forum, long time user and lover of cyanogenmod.

I have only noticed one thing in the latest build. Anyone else notice a sensitivity issue with the double tap to wake feature? I've noticed that when I have the phone in my pocket and the screen comes in contact with the side of my leg through my clothes it can sometimes wake the device for long periods of time, resulting in overheating, battery drain, etc.

It's easy enough to just turn off the feature, but before I do I wanted to see if this is something I'm doing, or if this is a widespread thing. Thanks! :)
[Verizon LG G3] Punchieo:
This only happened to me once. Maybe it's your pocket or something lol
[Verizon LG G3] dan411:
I don't think you read my question carefully. My question was actually legitimate. The problem with tap to wake never came up when I was on the stock G3 ROM, and I carried it in my pocket all the time. I wanted to know if other people have experienced tap to wake being too sensitive on cm12.1, and if so, if is there a workaround beyond just turning the feature off.
[Verizon LG G3] pairdime:
One thing I noticed this morning is after snoozing the alarm, the screen stayed lit and didn't turn off.

Maybe your issue isn't the tap to wake, but rather something is causing the screen to remain on?
[Verizon LG G3] Tyoryn:
Snapshot Update

Ive been updating the nightlies using the CyanDelta app for about a month now with no problem but with the release of the snapshot update on the 26th Ive hit a speed bump. It isnt showing up in CyanDelta so I downloaded the full file, when I dirty flashed it (wiped dalvik and cache before and after flashing) everything worked through the "preparing apps" to "finalizing boot" then the theme manager and media.something... crashed and it went back to bootscreen and hung up there forever.

Is dirty flashing even an option going from nightlies to a snapshot or is the problem in my use of CyanDelta or my themes not working with the snapshot?
[Verizon LG G3] annoyingduck:
WTF is rainbow mode motherf*****s!? http://review.cyanogenmod.org/#/c/102028/
[Verizon LG G3] J2theMatt:
#scotus
[Verizon LG G3] ericralph:
Facebook Messenger bug

Hi there,

I've been experiencing a very mild but still irritating bug in Messenger for a month or two now, on dozens of different builds. In the app, there is an option to take a photo which is immediately sent to the recipient of the conversation. My issue is that the quality of the picture in-app is extremely low-res, almost as if the app is preventing the full capabilities of the camera from being used. When I use the actual camera app, I have no issues.

One a different note, I am also experiencing severe overheating and consequently my battery life is being destroyed. Google Play Services appears to be the main culprit and this has been unchanged after flashing from a 6/2 nightly to 6/25 and euroskank's 6/21 Gapps package. Anyone else had a similar issue?
[Verizon LG G3] Noobla_Khan:
I believe the snapshot is CM 12 not CM 12.1, that might be your problem.
[Verizon LG G3] Tyoryn:
Ah so it is, thanks. I hope the nightlies start again soon, I was hoping the snapshot would fix the gps and mobile data issues I've been having.
[Verizon LG G3] MaddMaxx636:
Crash to black screen after reboot

I have been having this issue where if i reboot my phone after a while of using it or if my it crashes or a app breaks the OS. For example. If i leave the messaging app on and then lock the screen and then i unlock my phone later if will freeze/crash everything else but that app and will not let me exit the app and if i kill the app is goes to a black screen as if it cant load the System UI or the launcher and forces me to reboot.

Back to the crash to black screen. Well like ive been having this problem since the 6/19 - current date of posting this reply. What it does is if my reboot my phone it will boot up normally and show the lock screen and then the boot animation will show up and then after it "boots up" it will go to a black screen and cook the CPU/overheat and then i have to force reboot and when it reboots (If im lucky which isnt often) it will boot up perfectly but most of the time it will for some ****ing bull **** reason wipe the caches and have to rebuild it and THEN!!! Crash to a black screen and sit there and overheat! CM/phone LOGIC!!!!!

I have tired fresh installs with formatting my system and not formatting my system using every nightly and every time using the stock kernel and all that **** and i STILL get the MOTHER****ING crash to black screen after a reboot or after updating the nightly.

Has anyone else has this issues? Its pissing my off!!! I want CM12.1 to work as perfectly as it was when i first got the damn phone and not all this bull ****! Its like my phone phones im spending hours in setting up my phone after a fresh flash or restoring from a back up and its main goal is to find every damn way to piss me the **** off! Its like When it works perfectly for 1 WHOLE DAY and then when i plug it in to charge and unplug it. It reboots and crashes to black screen! Its like its purposing ****ing itself in the ASS because it knows it will make me angry.

Please tell me im not alone with this bull ****!!!
[Verizon LG G3] bb12489:
Looks like data is broken on the 25th nightly. I can't get it to come up no matter what.
[Verizon LG G3] ohlin5:
While I can honestly say that would frustrate me too, I'm not currently seeing that issue. However, you have to remember that CM (or any other aosp based rom for that matter) was never designed for running on this device. If you want perfect aosp you're gonna need a nexus. If stability is of utmost importance to you, then you have to go stock. CM exists as an alternate choice, but comes with the inherent greatly increased risk of issues. Not trying to be an ass, but these kinds of posts can pretty easily piss off the few devs we're lucky to have.
[Verizon LG G3] pairdime:
Had a problem with my alarm, snoozed it this morning and then it wanted to snooze until tomorrow. Dismissed the defunct alarm, and then it set my next alarm time to Wednesday, when it should have been Tuesday. My snooze length is the default 10 minutes.

I have that issue every time I wipe cache, but doing another reboot fixes it.
[Verizon LG G3] tpayne2345:
Had the exact same problem this morning and was almost late for work.. Mine happened after the 2nd time I hit snooze

kinda scary but more incentive to just get up now so.. thanks? Also I'm curious to see what this commit is
[Verizon LG G3] ericralph:
Just checking in to say that I am also experiencing broken data on the 6/25 build. killall rild with su access fixes it momentarily but the moment data stops being used (no service, wifi instead, etc.) then it goes back to ! nonsense. Very annoying but I'm sure it'll be fixed soon.

---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------

On a side-note, does anyone have a suggestion for the best 5.1 Gapps package out there?
[Verizon LG G3] tpayne2345:
I struggled with this until I landed on TK Gapps, easily the best IMO
[Verizon LG G3] ericralph:
Thanks a lot! I'll check it out!
[Verizon LG G3] ohlin5:
I'm sure its that I don't use the stock alarm app, but fwiw timely has never failed me yet....although I also don't snooze much lol :)

As far as your question on the commit, its related to the cm recovery - it now has rainbow text....you won't see anything if you're using twrp or cwm or philz or w/e.
[Verizon LG G3] pairdime:
cm-12.1-20150630-NIGHTLY-vs985 is out with a bunch of LG G3 fixes, installed fine for me.
[Verizon LG G3] bb12489:
Is anyone using the G3 with android auto while running CM 12.1? I've noticed that there is a problem with ROMs that have a built in DPI changer. It seems that it completely screws up how Android Auto is displayed.
[Verizon LG G3] Zlatty:
Anyone know how to battle the black screen of fai issue?

I have tried underclocking and dimming the screen brightness to 40%. Yet, the phone still crashes.

I've noticed that it's not always due to the heat as it crashes anywhere between 140 and 180 degrees. It also crashes no matter if you are on wifi or LTE nor while you are streaming music through bluetooth. 80% of my crashes happen while watching something in MX player or YouTube. It does not matter if the media is on the SD card or the internal storage.

What can I do to remove this annoying crash? It happens 2-4 times a day, and each time I have to wipe the cache and let it 'update' 230 apps which sometimes crashes the phone.

Yes, I tried a fresh install. Yes, I tried another kernel. Yes, I tried different governors and kernel settings. I cannot afford a new phone and I'm tired of putting up with this garbage.
[Verizon LG G3] digitallure:
I'm coming from PA and installed the latest nightly. I don't have any sound files except for Hangouts and BBM. How do i resolve this besides downloading sounds from Zedge?
[Verizon LG G3] ohlin5:
The rom comes with a small selection of tones, choosable in the settings > sounds area. There's no reason those shouldnt be in there.

On another note, am I the only one here who sees a fairly regular lack of fluidity in this rom? I remember coming to CM originally and be astonished about how much smoother it was than stock....and now what I'm currently seeing almost makes it seem like tables have turned 180 degrees lol.
[Verizon LG G3] ChiefIlliniwek5:
I'm running the 6/25 build and today I attempted to make a conference call (3-way call), but I was never given the option to "merge" the calls. From searching around, it is my understanding that when you have made a connection with the first person you call, you click the phone icon with a "+" and dial the 2nd person (which I did). Once that 2nd person connects, the phone with a + is supposed to turn into a symbol that looks like two lines merging into one. That symbol never appears when the 2nd person connects. Instead, it remains a phone symbol with a +. Has anyone else attempted a conference call on this (or any) builds of 12.1? Anyone having the same issue?
[Verizon LG G3] schleyseiner:
I also have a problem with the Dialer. Every so often (very often) when I receive a phone call my screen will just flash and I am unable to accept the call. Can't even stop the ringing. Have to wait for the call to stop, then look at missed calls and call the person back. Kinda annoying. Anybody else having this problem? Or an idea how I could fix this?
[Verizon LG G3] jazzyyki:
Yes I have this problem on 6/25. Whati s your version?
[Verizon LG G3] schleyseiner:
Honestly, I don't know. I only update sporadically and I don't remember when I did it the last time. Before yesterday, that is. I updated last night and now will see if problem still exist. Otherwise it's a great OS. Works pretty flawless with a very few minor hiccups here and there.
[Verizon LG G3] ngnr3:
Dialer is good on 6/30 nightly
[Verizon LG G3] J2theMatt:
I am on 7/1 build and unfortunately have experienced both the above problems.
[Verizon LG G3] R2D2-AKU2:
3 way and call waiting/swapping have been wonky for me on every version of 12/12.1. Often I have another call coming in, answer it and am unable to get back to the other call afterward. I have to hang up and try again.
[Verizon LG G3] ohlin5:
+1 to this - I've never been able to get "back" to my original call, either, in this type of situation. Gotta resort to acting like its 1999 and actually call again ;)
[Verizon LG G3] tpayne2345:
As in you can't get service no matter what you do?

There are several ways to fix this, what have you tried?
[Verizon LG G3] Nickyro23:
I'm currently running 6/25 and my data is working just fine. Check your connections and maybe try a clean flash if you haven't already.
[Verizon LG G3] schleyseiner:
After update last night to 07/01 nightly Dialer problem still there. Incoming call results in flashing screen and no way to take the call. Unless I'm on bluetooth.

---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------

Have the same problem after updates or reboots. Just reboot twice and if data is not back on, put "LTE" in notification area, then click on it to disable, wait a few seconds and activate it again. Works every time for me whereas turning on/off mobile data does nothing.
[Verizon LG G3] annoyingduck:
This is easy. Go into settings/mobile networks/APN/tap 3 dot in corner/reset to default/reboot. A few changes in the nightlies caused this to change.
[Verizon LG G3] pairdime:
continue to have random problems with alarm snooze here on 07-01

sometimes it works right, sometimes it doesn't

i just tried this, it wiped all my APN configuration and did not enter in any defaults.... sigh time to restore i guess
[Verizon LG G3] funkatronic:
Have you updated your modem to 23c?
[Verizon LG G3] pairdime:
yes, i had to do this to even install cm12.1 in the first place
[Verizon LG G3] 117micc:
Edit: Sorry guys, I guess I was sleep texting and ended up adding to this thread on accident lol.
[Verizon LG G3] curtis8523:
Having issues with WiFi not saving networks after reboot. Say I reboot for any reason when I do non of the networks I have connected to any saved WiFi networks/pass phrase's. Anyone else having this?
[Verizon LG G3] gserp4sox:
Having trouble with data since going to 7/3 build. Reset apn's to default, which wiped all of them out completely. Went back to 7/2 build and apn's were still gone. Built new Verizon apn but now having problems here as well (no problems initially when I first went to 7/2) Currently on 7/2, but data sporadic and unusably slow on LTE, and breaks often. Slow but usable on 3G, but will stick on 3G. Suggestions? Are others having issues? Thanks
[Verizon LG G3] bschmidy10:
Weird problem.... So wifi works at first but if I leave my house and come back it connects but shows the exclamation point next to it and doesn't transceive... I have to force forget the network and re add it to make it work every time... Any ideas?
[Verizon LG G3] ohlin5:
Interestingly enough, mine did the exact same thing yesterday - erased all my apn's, even though I have done this in the past with no issues! It gave me an odd "no access point name settings available for this user" error....almost like I was on a guest account or something lol. Anyways, I ended up wiping cache, dalvik, and system, and flashing a newer nightly and things came back for me.
[Verizon LG G3] x86cpu:
Same issue here. 7/1 build. Reset APNs to default and it wipes them all. Verified that the carriers.db file is completely empty, so it's not importing them properly from the /etc/default apns file. This causes data to not work over mobile. Went back to 6/3 build, as that was the last one android auto would work on. 7/1 finally fixed it, but without data it's useless. Even entering in the APN by hand does not work, it won't show up and do not get data. I'm not sure what build that started happening in, will have to start testing a bunch of them. Usually at least resetting to default APN fixed it (for me), not wiped all APNs from my phone completely.
[Verizon LG G3] gserp4sox:
No fix with the 7/4 build. This is a bummer! I tried to reset the apn's to default again and they did seem to return, but alas still no luck with data at usable speeds. the LTE icon is in the status bar, but data isn't really working. Anyone want to suggest a build to return to? Thanks

Edit: I'm an idiot. Turns out all the issues I was experiencing where actually caused by Verizon's overtaxed data system. I was in a tourist area for the weekend, in a place I know has limited data capacity, and the system had basically ground to a halt. Once I left that area, my phone was fine. Several ROM flashes, resetting apn's, etc. was all for nothing, lol Currently running 7/4 build with no issues.
[Verizon LG G3] lapmv86:
Flash rom "error executing updater binary in zip" because baseband is not up to date?
[Verizon LG G3] :
I'm on 7/5. Dialer and Messenger are still broken.
[Verizon LG G3] DarthDestroyeis:
I have found that if data doesn't come on by itself that I can go to apns and click on the bottom Verizon apn(the one without a radio button next to it) my data always comes on after doing so.

FYI: Android auto is working again as of the 7/4 build!
[Verizon LG G3] gserp4sox:
The Verizon apn without a radio button was removed in the 7/5 build I believe. I don't have it in the 7/7 build FWIW
[Verizon LG G3] x86cpu:
7/7 and I have data back, I can reset all APN's and they come back (I'll have to try just clicking on the Verizon apn next time). Android auto working on 7/7 build.
[Verizon LG G3] ohlin5:
Overall this rom runs pretty slick for me, aside from the occasional lag it's pretty solid. I am wondering, however, am I the only one who (fairly consistently) sees data not coming back after coming off of a wifi network? I use wifi constantly at work and at home so I go "on and off" it pretty frequently, but it's fairly regular where I come off it and my LTE doesn't properly kick back in. I've set the LTE quick settings tiles and clicking that twice works every time, but it's just kind of odd and I was just wanting to confirm I'm not the only one seeing it :)
[Verizon LG G3] crunchybutternut:
You're not the only one. I have to do the same thing all of the time.
[Verizon LG G3] Zlatty:
Is the black screen of death going to get fixed any time soon? I'm on the 7/8 build and its happening more often than with the 6/30 build.

Are there ways around it? Do any of the involve lowering the brightness to unacceptable levels? Is there a different kernel I should be using instead?
[Verizon LG G3] ohlin5:
What do you mean by black screen of death? Doesn't sound like anything I'm seeing....what kernel are you using? Something other than stock?
[Verizon LG G3] cyberhern:
Yes! Very frustrating, after every reboot I have to enter passwords forevery wifi i reconnect to.
[Verizon LG G3] Zlatty:
The black screen of death is just like the name implies, a black screen when the phone has a kernel panic. It usually happens when the phone overheats and the kernel cannot scale back the cores to cool off thereby freaking the fawk out.

This is both with the stock kernel, as well as the 777 kernel. Luckily the 777 kernel lets you set temperatures so that the BSOD is triggered less often.
[Verizon LG G3] ohlin5:
Interesting.... I've had a couple other color (lime green, maybe orange or yellow) crash screens, but I don't recall ever seeing black. Either way though the phone definitely does run hotter than stock or with kk aosp etc. and so I definitely could see that. I installed it on my brothers phone and he likes it but that was the very first comment he made was how hot it ran. I too am hoping for some more kernel optimizations or whatnot as time goes on to hopefully curb these kinds of issues...also may help battery life possibly? Idk lol :)
[Verizon LG G3] Zlatty:
Those were under CM 12 as I recall. 12.1 got rid of them. I'm ok with a days worth of batter and 4 hours of screen time. The only battery killer for me is when the phone gets in a bootloop after a kernel panic.
[Verizon LG G3] ohlin5:
Ive definitely had at least 2 under 12.1. And the phone undeniably runs hotter, easier on cm than stock....and I assume that's gotta be an indication of the CPU working harder at something, right? If so, this would correlate to decreased battery efficiency.
[Verizon LG G3] Zlatty:
The LG G3 runs hot no matter what. Stock has some safeguards baked in like auto dimming the crap out of the screen when the phone gets hot.

CM12 and 12.1 have no such features, so you have to go and mess with the kernel settings to make sure your device does get overly hot, which is annoying. On stock CM12.1 my phone runs about 120℉ and stock is 110ish or so.