yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] cap1tal1sm:
VS985 here, I'm getting the com.android.phone close errors. i unchecked get time zone automatically and it didn't help. I also went to CM updates and downloaded all the new updates, and rebooted. Then when I went into a few apps that's when I got the messages.

Is there no good fix for this?
[Verizon LG G3] drkow19:
This happens with one of my Bluetooth Jam Classic speakers also. It connects then disconnects. But it connects fine with my Chevy MyLink car, and my Satechi Bluetooth speaker. Bluetooth seems to be buggy. I get some audio buffering when connected to my Chevy playing music, which never happens on a stock rom.
[Verizon LG G3] Zlatty:
This is fantastic. Can't wait for CM12. The unofficial version is fantastic.
[Verizon LG G3] Wolf-Man940:
cool >> and this is for [AT&T Version / Model D850] its frish :D

>> http://download.cyanogenmod.org/?device=d850&type=nightly <<

waiting for my Model D855 :fingers-crossed:
[Verizon LG G3] johnpat:
Hope that d855 can get the official support too>_<
[Verizon LG G3] zebinadams:
As far as I know, its an issue that some have (myself included) that only exists on CM, but no other ROMs. No fix that I know of atm. I went back to stock for now. There are a few other ROMs that don't have this problem, but I've grown so used to CM that being aosp without their tweeks is almost more difficult than staying on stock. Hopefully someone will figure out what's causing it and fix it soon.
[Verizon LG G3] endfro:
I was able to fix my loss of LTE connectivity by performing the following steps;

1) Download and install terminal emulator off the play store

2) open Terminal emulator

3) type "su" with no quotes and press enter

4) give terminal emulator super user permissions

5) type "killall rild" with no quotes and press enter

All was well after that. I found this info on the VS985 CM12 thread but wanted to post it here for anyone who has the same issue.
[Verizon LG G3] bweN diorD:
curious that some of you have this issue, and others dont. there has to be some common factor for those that do.

i have never once had this issue, and i have been using this rom since the original unofficial builds. have dirty flashed every time except the initial flash.

the only notable thing about my setup that could have some possible relevance is, i never updated anything (outside of the rom) except the modem, off 10b. such as the boot partitions, etc.

could be that, or a common app you guys use that i dont.

maybe if you guys started comparing specifics like these, you could narrow the cause down a bit.
[Verizon LG G3] epicroot:
I ran cm11 for 2 weeks no problem then the fc started
[Verizon LG G3] zebinadams:
The first install had the fc right after finishing the initial setup. I downloaded a newer zip and did a new clean install. That one did fine for about an hour then freaked out on me... There hasn't even been consistency on my device for when it starts that I noticed... But I agree, there has to be some common thread causing this frustrating issue. I just don't even know where to begin
[Verizon LG G3] zakkyzombie:
Is there a change log anywhere?

Want to see what's fixed and not, to see if it's flash worthy for me.

Sent from my LG G3.
[Verizon LG G3] imaverik:
11/28 build still the best?

I'm still using the 11/28/14 build. everything works. The bluetooth is a bit unstable... i somes have to reboot the phone to get it working again.

This is a dd for me.

i haven't had any other issues.

Reading this forum has been helpful too, From what i've read i should stay on 11/28 for now.
[Verizon LG G3] bullah:
http://www.cmxlog.com/11/vs985/
[Verizon LG G3] jdgesmlls:
This doesn't appear to be maintained by invisiblek. Not that I don't appreciate the summary, but the latest 12/7 build doesn't list any fixes.
[Verizon LG G3] bL33d:
anyone find a fix for blackscreen on calls other then hitting power buton ofcourse.
[Verizon LG G3] cubsf4n:
Same here. Never updated from 11/28 cause I've never had a reason to. This is my DD and I have no complaints and no FC.
[Verizon LG G3] ohlin5:
I wish. I believe Invisiblek said somewhere that he'd been having trouble replicating it and so if someone got him a logcat he could maybe nail down the problem, but don't quote me on that. Definitely an annoyance though :)
[Verizon LG G3] killmequick:
Has anyone tried this? I am getting the force close error as well and flashed back to stock because of it. CM works fine for a few days then as soon as I make a phone call it gives me the error.
[Verizon LG G3] iBolski:
If you're looking at nightly, it doesn't mean anything. From what I understand, they rebuild automatically through the night, so they may or may not contain changes/fixes. At least, that's what someone else said.
[Verizon LG G3] ohlin5:
Those aren't steps to fix the force close error - those are steps to restore the loss of data connectivity that sometimes occurs after a reboot. 2 different things. Unfortunately I don't have any idea on the phone force closes.
[Verizon LG G3] bweN diorD:
We have a change log with the updates. Most likely that's where he pulled it from. I can't say if there is any official webpage though.

Sent from my G3, Unlocked by Team Codefire
[Verizon LG G3] harry_seaward:
Does anybody know what the last nightly was before all the data/LTE issues? Was it 1128?
[Verizon LG G3] bL33d:
That's cm12. cm11 dies not have connection issues.
[Verizon LG G3] PhonePhapperBYAAAHH:
com.android.phone issue AGAIN

12/10 CM11 nightly build was perfect until com.android.phone came in to make me press the OK button repeatedly. Like so many times before with other CM11 builds. I'm not having this issue whatsoever on [MENTION=2385005]invisiblek[/MENTION]'s CM12, but for some reason it won't stop on all but maybe two official/unofficial CM11's. :confused:
[Verizon LG G3] Noobla_Khan:
I've updated to every official nightly(except 12/10) and have not had this issue. Going to do a backup now then update and see if I get it.

EDIT: So far so good. Running 12/10 nightly with included kernel, no mods. Updated, not a clean install.
[Verizon LG G3] Tillmorn:
I'm going to post this in the troubleshoot section, however I thought I'd see if you guys have noticed anything.

It appears that the Play Store updated today to 5.1.11. Since then, I continuously get the "Unfortunately, Google Play Store has stopped." force close every time I try to open the app. I know it has something to do with this version, because I was able to successfully use the app after uninstalling updates back to 4.6.17. Since it automatically updates though, I'm a little lost as to what to do.

Thoughts? I've already tried wiping cache/clearing data/force stopping for both it and Google Play Services with no luck. "Uninstall updates" seems to be the only thing that works.
[Verizon LG G3] Tillmorn:
Nevermind guys, figured it out. Apparently it wasn't playing well with the CM theme I was using. Odd little quirk, but I'll gladly stick to their standard theme for a few weeks if it means a working Play Store.
[Verizon LG G3] gparmar76:
I've had this too...revert to stock theme, update the play store and then reapply the theme...that worked for me.

---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------

Am I the only one still suffering from the blank screen after call issue? EVERYTHING works beautifully but this one bug is still present...for me anyway...almost after every call, when I pull the phone away from my head the screen stays off...its not a big bug but damn its annoying! Anyone else?
[Verizon LG G3] Tillmorn:
It's about 60/40 for me. Most calls, I have to hit my power button to turn the screen back on. The other times, it works. However, it was the same way with Liquidsmooth and other AOSP ROMs, so hopefully one of the devs will figure it out.
[Verizon LG G3] simollie:
I still have this. Not sure if it happens every time, but it happens more often than not.
[Verizon LG G3] bweN diorD:
Never happened to me. Works as intended, every time.

The only issues I have are the kernel crash from hotspot about once a week, and battery stats not resetting. Neither is a big deal though.

Sent from my G3, Unlocked by Team Codefire
[Verizon LG G3] jlvlawrence:
I just had this happen to me again. It's really a bummer when it happens. The only solution seems to be restoring a nandroid or starting over with a wipe. Other than this, I was having zero issues with the rom.
[Verizon LG G3] ohlin5:
As do I, also probably somewhere around 60/40 as well. It's odd that it's so hit and miss. I'm currently running SlimKat 4.4.4 as I can't seem to sit on the same rom for more than ~3 days lol ;) It does seem just a little better, but still has the issue definitely present. That's easily my biggest annoyance with AOSP right now, so yes, hopefully one of the wonderful devs can crack this!

---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------

Ok, this is going to sound like a stupid question, but I just have to ask as one of the people I saw with this issue posted a screenshot and his signal bar had an "H" in it - which I gathered was maybe HSPA signal, which afaik Verizon doesn't have. So, I'm going to ask the stupid question as much for my curiosity as anything - you guys are on VZW, correct?

---------- Post added at 02:44 AM ---------- Previous post was at 02:43 AM ----------

This is so weird....I've definitely experienced this on every single AOSP rom I've installed. Some have been better than others, but none have been 100%. Extremely weird how it's so intermittent. And none of my flashes experiencing this have ever been dirty flashed, either - I'm very anti-dirty flash haha :)

Question then, just for kicks and giggles - do you have a screen protector on your device? I'm assuming that wouldn't make a difference as I've downloaded sensor detectors and confirmed that the proximity sensor does indeed seem to be reading correctly, but for some reason it definitely sticks post-call on mine (as well as my brothers) and many other devices here on XDA.
[Verizon LG G3] PhonePhapperBYAAAHH:
com.android.phone has stopped

12/11 didn't even last near as long as 12/10. Tried with 11C and 12B modem. Definitely done thinking thats the problem. Super lame. Still waiting on a new CM12 build because that's the only thing my phone works on minus the quirks. I refuse to go back off of AOSP now that it's here. lol
[Verizon LG G3] bweN diorD:
i have the zero lemon tempered glass on.

my question for those having the issues would be, is there anyone who never updated off 10b but the modem?

its just a guess, but thats the situation with my phone. im wondering if it has something to do with files being updated, that i havent done.
[Verizon LG G3] ohlin5:
What do you mean by "never updated off 10b but the mode"? As in never updated to 11c (or 12b)? If so then yeah, I bought the phone way before 11C was released, and had it fully rooted the night I got it. Also bump'ed it the very first night it was available.

My follow up question to that would be if there is anything that I could do on my end (keeping in mind I'm willing to learn, but have basically no in depth dev'ing experience) to possibly help troubleshoot this? If this, and the phone system crash that others are talking about (which I haven't had, but have seen it enough times to know somethings up) could get fixed, then 4.4.4 aosp would be pretty rock solid. Those are the 2 bugs issues right now it would seem.
[Verizon LG G3] bweN diorD:
yes thats what i mean.

did you flash the boot.img from either of the updates?

not sure if its relevant yet, just trying to cover all bases.

if it has nothing to do with upgraded files, i can only suggest that those with the issue start comparing some specifics. downloaded apps, mods, tweaks etc. did you wipe internal storage when clean flashing? could be as simple as that.

not sure what else to suggest.

maybe logcats, if they show any errors.
[Verizon LG G3] ohlin5:
Nope, I have never flashed anything other than modem img's (and roms of course) and I've always just wiped dalvik, cache, system, and data several times before installing a new rom. Always have left internal and external storage intact. As far as mods, I've got xposed and a few modules there....do you use xposed?
[Verizon LG G3] ohlin5:
[MENTION=4132606]bweN diorD[/MENTION] - I believe I've done this correctly - here is a log from my device that I believe I correctly switched to show errors only, and then I made a call and the phone did it's proximity issue, and then I reopened the catlog app and saved the log. Not being a dev I really don't know how to interpret this, but could you (or someone else who knows more than I) look at this and see if anything catches your eye by chance?

-------------

Could one (or both) of you guys possibly install catlog from the play store and set it to log errors, and then try to get this problem to duplicate itself again? Maybe a wise dev here could spot the anomaly and we could get this issue resolved. I don't want to install an AOSP rom on my brother's phone with a bug like this floating out there, as he doesn't know as much about how to "fix" things when they break as I do, and he lives a little ways away....so I'm looking at being stuck installing LG's stock version for him at the moment lol
[Verizon LG G3] bweN diorD:
I haven't used exposed since moving off stock

Sent from my G3, Unlocked by Team Codefire

---------- Post added at 04:53 AM ---------- Previous post was at 04:42 AM ----------

I'll look at it later or tonight, but if it shows any errors, its really [MENTION=2385005]invisiblek[/MENTION] who would need to look at it.

I'm not an expert on this, I just play one on TV ;)

Sent from my G3, Unlocked by Team Codefire
[Verizon LG G3] bweN diorD:
[MENTION=4513259]ohlin5[/MENTION]

I have an idea,

Take out your SD card, then do a nandroid, then wipe everything! and do a clean flash. At setup do not enter any email accounts, so nothing will restore. Then do some test calling to see if the issues are still there with no data, apps or mods.

This seems like a perfect way to tell if its a software issue of some sort.

Sent from my G3, Unlocked by Team Codefire
[Verizon LG G3] ohlin5:
Done, wiped absolutely everything including internal storage 3 separate times and then clean flashed the latest nightly. Restored nothing upon setup, only connected to my wifi, and about the 3rd call in the issue popped up again. This is so weird....and I struggle to believe it's a hardware issue because a LOT of people on here have commented on how theirs isn't working right. Not to mention mine worked 100% on LG's stock rom (or the variants of it).
[Verizon LG G3] bweN diorD:
Well that sux. If you could get a logcat while its in that state, it would be good. It should be more obvious where the issue is I would think. I haven't had a chance to look at the other log yet.

Sent from my G3, Unlocked by Team Codefire
[Verizon LG G3] PhonePhapperBYAAAHH:
Logging com.android.phone
[Verizon LG G3] PhonePhapperBYAAAHH:
LOGS ATTACHED (com.android.phone has stopped)

My CatLog is attached. I hope this captured it. I think it occurred around 9:23AM. If anybody is tight with a dev team member or the OP, please encourage them to look at this. If i missed it, let me know and i'll do it again. I'm going to try the 12/12 CM12 now :D
[Verizon LG G3] ohlin5:
Thanks for this. Hopefully [MENTION=2385005]invisiblek[/MENTION] or someone else can figure this out!
[Verizon LG G3] Rasputitan:
Phone crash

Hello, my phone crashes each time I try to run this rom. I use twrp and it installs successfully but upon boot up, where you hit next, it starts to crash saying "com.android.phone has stopped working". It won't go away even upon rebooting. I always do twrp wipe and then wipe dalvik and cache. Tried without wiping dalvik or cache as well. Any assistance would be greatly appreciated.
[Verizon LG G3] bweN diorD:
when i was mentioning minor issues earlier, i forgot to mention the hotspot reports 0 connections when devices are connected.

i did have something else interesting happen twice in the last few days. im not reporting this as a bug because i havent clean flashed in about a month.

interesting none the less. my dpi reverted to rom stock twice in the last few days

without rebooting

. i wasnt aware that was even possible.

just sharing in case anyone else has had this happen.

---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------

[/COLOR[/quote]

[MENTION=4513259]ohlin5[/MENTION]

[MENTION=6196339]PhonePhapperBYAAAHH[/MENTION]

i just wanted to throw a quick thanks you guys way for pulling these logs.:good:

i was starting to get pretty annoyed at all the people saying thing were broke and not helping to find a fix.

i dont know if i can be of any help, but i am going to take a look at the logs to see if anything obvious pops out.

thanks :)
[Verizon LG G3] PhonePhapperBYAAAHH:
Please read thread above and below your post [MENTION=6240386]Rasputitan[/MENTION].
[Verizon LG G3] bweN diorD:
[MENTION=4513259]ohlin5[/MENTION]

[MENTION=6196339]PhonePhapperBYAAAHH[/MENTION]

so, i looked through the logs, and im not going to pretend i have a clue about this, but im going to point out some things that looked curious anyways.

- both of you had some bluetooth errors, such as "Could not get a handle on Connection object for the call" which seems odd, unless both of you were using a bt device.

- ohlin5 has this error "'/sys/devices/virtual/graphics/fb1/hpd' not found" not sure the relevance, but see if you have this file, i do, inside is a single "1" and the permissions are rw rw r

- both of you have various audio errors

- curious i cant find this folder "Unable to load native code from /data/app-lib/PrebuiltGmsCore/libgmscore.so" yet i can find the libgmscore.so in the lib folder

- olin5 has a bunch of these errors "Failed to find provider info for com.teslacoilsw.notifier", google says this is part of nova launcher, yet i dont see nova in either of the app folders

- this appears to be the most direct error related to the phone app "E/QcrilMsgTunnelSocket(3471): Uncaught exception read length=55Exception:java.lang.NoClassDefFoundError: com.android.internal.telephony.lgdata.LgDataFeature"

from my noob perspective, there seems to be a lot of good error content related to the crash in both logs.

hopefully [MENTION=2385005]invisiblek[/MENTION] has time to look at them and can fix this up for you guys.

wish i knew more about this and could actually help. :(
[Verizon LG G3] ohlin5:
Thanks for the review...I honestly couldn't help but try invisiblek's latest 12/12 CM12 build lol, so I'm currently on that. There's just a small part of me that wishes we had an option of a truly rock solid 4.4.4 build haha, but I know the timing isn't completely ideal with most all the focus right now being geared towards CM12. Whatever, either way it'll all be what it is :) Thanks again!
[Verizon LG G3] annoyingduck:
Anyone else able to change lockscreen wallpaper using nova? Did cm change something I'm not aware of?
[Verizon LG G3] imaverik:
You can change it from CM11 theme system menu baked into cm11.
[Verizon LG G3] annoyingduck:
Of course... I'm asking about through nova. It used to change both the home and lockscreen together without going into the theme manager.
[Verizon LG G3] imaverik:
Nova Launcher itself does not have an independent lockscreen wallpaper changer that I am aware of. If someone one here has better information feel free to chime in with a link or whatever.

With nova launcher you can launch "activities" by adding a new shortcut or widget. It will typically look through your system and find activities that can be invoked. I'm not sure where Nova looks for these though. You "should" be able to find an activity that will launch the interface for chaging the lockscreen wallpaper. The kicker here is that you will end up with a shortcut or widget to launch what is already provided from the settings menu within the rom.
[Verizon LG G3] annoyingduck:
I think I'm misleading the question, I'll be clearer. Changing wallpaper through nova on cm or any other aosp for that matter would change both the home and lockscreen wallpapers to whatever single wallpaper you chose. It's been that way for years. I haven't been back on aosp for the past few months until now... I'm trying to determine if this is a bug or if something has changed in cm in the few months I've been away. This question is better suited to aosp veterans.
[Verizon LG G3] ohlin5:
I can't believe it took me this long to notice this, but after returning to the 12/13 nightly from a CM12 flash I noticed there appears to be no multiple user support. Like in settings there isn't even a choice for "Users" - did I really miss this when I was running all the previous nightlies?!? Or has this always been this way??

So I took a look at the log posted by [MENTION=6196339]PhonePhapperBYAAAHH[/MENTION] just out of curiosity, and I can't help but notice the section of the log that reads:

12-12 09:23:19.592 E/AndroidRuntime( 9873): FATAL EXCEPTION: CdmaInboundSmsHandler

12-12 09:23:19.592 E/AndroidRuntime( 9873): Process: com.android.phone, PID: 9873

12-12 09:23:19.592 E/AndroidRuntime( 9873): java.lang.NullPointerException

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at android.telephony.SmsMessage.getOriginatingAddress(SmsMessage.java:553)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at android.provider.Telephony$Sms$Intents.getNormalizedAddressesFromPdus(Telephony.java:1176)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at com.android.internal.telephony.InboundSmsHandler.processMessagePart(InboundSmsHandler.java:742)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:371)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at android.os.Handler.dispatchMessage(Handler.java:102)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at android.os.Looper.loop(Looper.java:136)

12-12 09:23:19.592 E/AndroidRuntime( 9873):	at android.os.HandlerThread.run(HandlerThread.java:61)

right below the line you noted. I'm assuming the line you noted and this whole block is where the error is occurring, because while I don't know anything about dev'ing, this seems to be occurring every few seconds in a loop on his device. Super strange....and looking at it it looks like [MENTION=4592408]scy1192[/MENTION] posted this same error back on page 5 of this same thread. Guess this definitely appears to be the issues. While I haven't experienced this issue myself, it's a pain thinking it could happen to any one of the phones I've installed this rom on at any moment lol :) Sure wish there was more I could do to help with a potential fix for this.
[Verizon LG G3] bweN diorD:
yep, wish i could help more too, a dev needs to look at this and see if its fixable.
[Verizon LG G3] ohlin5:
So are multiple users really not supported on this rom? Just found that kind of interesting that it took me this long to notice. Like I said in my previous post - I don't seem to have that option anywhere in my settings menu...kinda took that for granted in any aosp rom hahaha :)
[Verizon LG G3] bweN diorD:
sorry, i dont have any use for that, and am not sure what i would be looking for.
[Verizon LG G3] PiousInquisitor:
Do other non 5.0.X ROMs have multiple accounts support? Prior to Lollipop, multiple accounts was a tablet only feature.
[Verizon LG G3] ohlin5:
Officially, yes, but I've been on many 4.x roms in the past that had it baked in. Unofficially, yes, but baked in none-the-less.