Hi,
ever since having updated my unlocked Captivate Glide to ICS on Saturday, I keep getting the message "Unfortunately the process com.android.phone has stopped". Initially I thought this was just a nuisance. But at work today, I found that everytime a call came in this message pops up and on pressing the only option- "OK", the call disconnects. Further more it neither shows whose call got disconnected nor its shows missed calls. What gives?
Was wondering whether anyone knows anything regarding this before I go back to the stock gingerbread from the ROM
Ameyam
ameyam said:
Hi,
ever since having updated my unlocked Captivate Glide to ICS on Saturday, I keep getting the message "Unfortunately the process com.android.phone has stopped". Initially I thought this was just a nuisance. But at work today, I found that everytime a call came in this message pops up and on pressing the only option- "OK", the call disconnects. Further more it neither shows whose call got disconnected nor its shows missed calls. What gives?
Was wondering whether anyone knows anything regarding this before I go back to the stock gingerbread from the ROM
Ameyam
Click to expand...
Click to collapse
When this happened with our Glides we did a factory reset, which fixes the process.com.android.phone issue. Not had a problem with it since.
Same over here. No more problems after factory reset.
guillermogc said:
Same over here. No more problems after factory reset.
Click to expand...
Click to collapse
Yes, did a factory reset on Monday. Just didnt update the post after that
Ameyam
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.
Hey people,
Over the last 2 weeks or so, I've been noticing that I would get random voicemails but my phone would never ring. Just a few days ago, I tried calling my wife and I got a force close error from the phone application (com.sec.android.phone...or something like that). Since then I have not been able to call out to anywhere other that 911 and voicemail. I haven't installed anything new other than a new ROM here and there. I've backed up all of my data and reflashed to other ROMs to try to fix the problem but with no luck.
I've had a hunch that it may have started when I was playing zenonia 3 but that game has been on my phone since May and I've played it here and there with no problems...but I noticed yesterday that I guess I was getting an incoming call or something while I was playing the game that the force close message popped up a few times...
If any of you has had a similar issue or just knows of a way to fix it, I would be totally grateful.
Do you use an Airave? Reset it if you do. Otherwise return to stock and check it. If it still does it call Sprint and the will reset your phone and that should fix it. You can try updating Profile before all that if you like.
Sent from my SPH-D700 using XDA App
First off I want to thank everyone who for there help on here. Yesterday I was able to root my phone and install CyanogenMod 7 Self-Kang #2. Everything was running fine until I got a call. I answered it and the caller couldn't hear me and I couldn't hear him. So I called back and my phone seems to have dialed. It showed that it was connected but again I couldn't hear anything. I then hit the speakerphone button, it didn't light after a couple of second I get a message.
Sorry
Activity Phone (in process com.android.phone) is not responding.
[force close] [wait]
Anyone have any experience with this?
everyone knows i did they say turn on gps and reboot didnt work with me i just went to juggernut
hi guys, i got a d855 and i have some issues which i think they may be stock rom's bugs and i d like to hear your opinion. I have the latest ota V10h-EUR-XX btw.
1) Every time i restart it appears in the notification panel the "voice mate" shortcut. I remove it using the edit at far right but still it reappears every time i reboot the phone.
2) Sometimes after an unanswered call or message the screen turns on as usual but it doesnt turn off. Ofc i ve selected to shut off at 30 seconds from the settings. Even if i change the settings to like 15 seconds the screen still wont turn off unless i manually lock it. This problem fixes if i restart the phone.
3) Every time i boot my phone i get this message: "unfortunately the process com.google.process.gapps has stopped"
So is there someone else who experiences these kind of issues?
wow, these 3 bugs are new to me. haven't experienced any of those at all.
I'm on V10J global though.
You're having permissions issues.
I'd bet my left testicle that a fresh flash back to stock will fix all 3 of your issues.
+1 on the voice mate .. irritating ~
I've encountered the screen on issue - although not only did the screen stay on after a missed call, the phone also became and remained completely non-responding, no screen input registered. Had to reboot manually. It happened only once in 3 weeks though.
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.