I just got the LG G3 on Verizon and flashed CM 11 12/4 and I am getting this error. A few nights ago I originally flashed the nightly from 12/2 and randomly got this error after setting up all my preferences. It's been fine since I went to the 12/3 nightly but I dont think I made any phone calls in that time. I don't know what's causing it and it's really bothersome. This time it happened when I went to make a phone call. This will be the 3rd time I've had to factory reset. Any ideas? I think I've tried all the wipe options possible..clearing caches etc.
I'm getting a similar issue. I've tried the last few nightly cyanogen builds for my G3, and sometimes during a phone call, the "com.android.phone stopped" will pop up, disconnecting the call. Once it pops up, clicking it away only makes it pop up again. A reboot does not fix that; clearing the phone cache does, but obviously that's not desireable because then the phone loses all my apps and saved logins.
Related
I've had some problems with my phone recently as it keeps rebooting itself (sometimes when charging and the battery gets hot.. sometimes randomly). When this happened a few months ago it got to a point where almost everything stopped working.. I did a factory reset but no joy so I took it to a phone shop and the guy said he flashed it and everything seemed to work again for another couple weeks then the rebooting started again but less frequently. Its now become a daily thing and today everything has stopped working again.. my call list.. text & emails won't update if a new message comes in I can't see anything in the list. I keep getting a popup telling me that Open Sense Plugin Manager has unexpectedly stopped along a couple of other error messages. I can't install anything either.
Any suggestions on how to solve this? I'm getting more than streesed by this!
Is it still rebooting? You could use an RUU and it might solve the issue but it might not. A bit of hit and miss if you ask me. If it is still rebooting because its getting hot, give HTC a ring.
Meaple said:
Is it still rebooting? You could use an RUU and it might solve the issue but it might not. A bit of hit and miss if you ask me. If it is still rebooting because its getting hot, give HTC a ring.
Click to expand...
Click to collapse
What's an RUU?
It got to a point last night where it wasn't turning on at all just getting to the T-Mobile screen and then back to the HTC screen continuously. I managed to do a system reboot which stopped the error messages I was getting but it was still doing a number of reboots. Seems to have settled now but obviously there's still an underlying problem there.
Will def be giving HTC a call in a while but want to avoid sending it to them unless absolutely necessary.
Note: this has happened with versions 4.1.x and 4.2.x both, always on a rooted stock image (I do not use any custom roms on a regular basis).
The Problem:
After a call that I initiated (regardless of the call duration, happened after 1minute calls, aswell as after 20+ minutes calls) then phone stops responding after I move it away from my ear (instead of turning the display on and letting me terminate the call). After that the only solution was to pull the battery or to wait for a "application not responding" message. On the ocassions where I was waiting for the ANR screen after force stopping the application everything went back to normal.
The occurrence of this seems to be totally random, and I was not able to reproduce the problem on purpose. I've tried to do a manual force stop + clear data/cache for com.android.phone but that didn't resolve the issue.
At times it seems like its fixed, not happening for days or weeks, and at times it strikes after 3 calls in a row.
The particular error was happening even after full factory resets and stock image flashing.
Any ideas?
Ill give my full story just to try and keep things clear as possible.
I recently rooted my Gnex and had no apparent issues. I was running ParanoidAndroid 3.15 and everything was smooth. yesterday, my phone started freezing at random moments. It quickly escilated to the phone freezing not on start, but once any app was used. Opening the app drawer, google now, text messaging, phone, etc. I whiped dalvik, cache, and it didint help. I did a factory reset and it still was freezing. I whiped the system, and reflashed factory OS, 4.1.1, unrooted, and the issue seemed to go away, but about 10 minutes later, it continued. Factory reset again, and couldnt make it past the activation screen without freezing. I went to the verizon store and reactivated my old DroidX ( the issue continued while at the verizon store). Now that there is no network active on the phone, there is no issue at all. Runs quicker than ever. Im confused as to this issue and google / forum search has given me nothing except topics that are about freezing or softbricking that dont really apply to my issue. I miss my Gnex and i want to reactivate it but not to just have it begin freezing again. Im running TWRP on my phone if it matters. I also was NOT able to collect any bug reports while it was locking up. It would even lock up on the power options menu. Once i reflashed factory OS, it would be inteligent enough to reboot once it realized it freezed but not before. The issue doesnt come up while on WiFi ( i had hoped it would for debugging purposes.) Any advice would make me happy as ball$.
im currenty using liteROM 0.9.0 first 3 days work fine, but after i found this problem.. can anyone help me..
+1.
My phone.android repeatedly shut down in Gingerbread. Only fix i could find was upgrading to ICS.
when arldft
Hmmm.... that is weird, i´m also using LiteRom 0.9, never had that issue, first time i flashed the custom rom i did see that message a couple of times, but no big deal just reeboot and no probs. after that though i decided to install the rom from scratch, never had an issue with it since. only problem ive had is the toggle for gps sattelites and mobile connection giving me some issues, nothing a reeboot cant resolve.
my advice would be to backup all your info & apps and start from scratch. or boot to CWM and fox permissions.
hope i helped
I had similar issues with GB. I was using the latest Osimood rom. Upon receiving a call, my phone screen would go blank (the way it normally does when switching to a call) but then it would freeze. The ringtone would not ring and after a few seconds of this, the phone would go back to the last app and the network signals would be gone. After a few more seconds, the network signals would be back. The same thing would happen if I received another call. The only fix was to reboot the phone.
The annoying part was that there would be NO way for me to tell who was calling me since I would never see their name and no entry would be made in the phone log. I didn't have any success with treating that problem. While it didn't happen very often, the few times it did would be very annoying since I'd often find out several hours later that I had missed an important call.
I've just switched to Pacman rom today in the hopes that this was a rom issue and will be gone now. Let's see.
I have a Verizon VS985 running 5.1.1 completely stock, never rooted or anything.
My phone works perfectly I can use it for days with no problems....
That is unless I make or receive a phone call. During phone calls my phone will freeze for a second lockup, then reboot itself. Once it reboots it's usually fine. It used to happen pretty infrequently like once every couple of weeks, so I ignored it. But now its happening at least once a day.
So I ask does anyone have any ideas at all what might be causing this? It seems to me it's gotta be software related, maybe?
I have 3 different batteries all genuine LG, it happens with all 3 of them, so it seems to be it can't be a battery issue (correct me if I'm wrong).
If there's any other information you need, please ask. Thank you xda community you are awesome.
Same issue
My phone will randomly reboot itself during a phone call. It has happened as many as four times during the attempt to finish one phone call.
Long story short, since my first message got erased by accident. I don't know if mine is fixed or not, since it happens hit and miss. I went to storage options and saw I had like 12 gigs of cached data, since it was counting all of the system files as cached data. I tapped cached data and cleared it. All the system files went back to misc folder where they normally are, and so far after about a week I haven't had a restarted. Could just be a coincidence. Clearing the cache daoesnt lose anything, although for some odd reason some apps seemed to lose random settings,and some required I relogin.