I've clean flashed a few different ROMs but I keep running into this same problem. My phone application keeps force closing with this message: Unfortunately, theprocess com.android.phone has stopped. So basically, I can't make or receive any calls. I don't know what to do to fix it. Everything else works. Does anyone have any ideas? Thanks.
Related
I am having a constant window that says "weather has stopped" The message comes so frequently and quickly that I am unable to do anything literally. I'm told it's a cache issue and I need to stop the app. I can't find the app listed in Running Apps, and if I could I couldn't do anything about it. How can I stop the app or cure my problem. My phone is totally useless it is a working bricked phone. All help and suggestions are welcome. Thanks.
Didn't you already asked this in another thread? Maybe you need to do a factory reset.
Hi, I've had my 1+ for about a month now running on stock (but rooted). Today my phone has been showing the "Unfortunately, the process com.android.phone has stopped" dialog. I click ok and the signal is lost. Few seconds later signal reappears but then dialog pops up again. It only started this morning. I haven't changed anything or flashed any fw or basebands.
It's a bit of concern. I've got a phone interview this afternoon and I really don't want the phone to cut out during it!!!
Does anyone know of how this happens and what mighht be done to resolve the problem. I'd rather not have to do a reset.
Many thanks.
Update: I seem to have resolved the issue by flushing the cache and data + force closing all phone/txt/contact apps. I also flashed a different modem for good measure. So far (over an hour now) I've not had the message come back. I suspect there was some conflict somewhere with the afore mentioned apps.
I have this issue after 1 week with the phone.
Same problem as yours, I only rooted the phone still running Stock 11S.
This problem happens this morning out of no where.
Been foreclosing all these apps and clear cache/data and hopefully it'll fix it...
OnePlus One - unfortunately the process com.android.phone has stopped
HI,
I have recently bought oneplus one and just couple of hours back I have upgraded to latest updates. After upgrading I am getting "unfortunately the process com.android.phone has stopped" and not allowing me to touch the home screen. Can you guys plz help me out to resolve this?
THanks
Ganesh
virgopunk said:
Hi, I've had my 1+ for about a month now running on stock (but rooted). Today my phone has been showing the "Unfortunately, the process com.android.phone has stopped" dialog. I click ok and the signal is lost. Few seconds later signal reappears but then dialog pops up again. It only started this morning. I haven't changed anything or flashed any fw or basebands.
It's a bit of concern. I've got a phone interview this afternoon and I really don't want the phone to cut out during it!!!
Does anyone know of how this happens and what mighht be done to resolve the problem. I'd rather not have to do a reset.
Many thanks.
Update: I seem to have resolved the issue by flushing the cache and data + force closing all phone/txt/contact apps. I also flashed a different modem for good measure. So far (over an hour now) I've not had the message come back. I suspect there was some conflict somewhere with the afore mentioned apps.
Click to expand...
Click to collapse
I have the facebook messenger app installed. Everytime I send a message to a friend, my phone locks up for 5-15 seconds. Does anyone else have any other issues with this or experience? I just wiped the phone today for an unrelated issue and it's still persistent. I've tried changing keyboards too. It's right after the message is sent.
I'm usually able to bodge my way through this sort of thing, but am at a loss here.
Just downloaded and flashed the latest nightly build for my Moto G 4G (Peregrine) direct from the inbuilt updater.
When it boots up i repeatedly get com.android.phone has stopped and it appears that it has no sim installed.
Have tried wiping everything and reinstalling but doesn't seem to have made much difference.
I'm an intermediate n00b - that is, I don't REALLY know what I'm doing but can usually bodge my way along blindly following forum posts to root/unlock/flash roms etc, but am at a loss this time. Can anyone please help?
OK I seem to have been able to bodge myself back to working phone more or less.
Installed Twrp 2.8.7 and CM13.0 20151204
Everything SEEMs to be ok now except that t keeps popping up a message saying my network (3UK ) is unavailable
This MAY be a problem with the network, but seems a bit of a coincidence seeing as I've been buggering about with the phone
Any known issues with network connectivity in CM13
EDIT: Still somehow managed to receive an SMS message when it said network unavaialbe
Try removing /data/data/com.android.providers.telephony/databases/telephony.db when com.android.phone keeps crashing!
Phone seems to be working now. Though not sure what i did to fix it
Now I can't install apps from Google play. Get the error "Chrome Browser - Google" can'r be downloaded. Try again and if the problem continues, get help troubleshooting
error code RPC:S-7:AEC-7 JZLQ-5JDI-W4ZW6
Edit: Also can't open the clock (eg to set an alarm) tap on the widget and it just says unfortunately clock has stopped
When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
*FIXED*
Uninstall the updates for the package 'com.samsung.android.incallui'.
SmilerOnline said:
When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
Or does anyone know how to fix this?
Click to expand...
Click to collapse
That sounds strange. Never encountered such a behavior on my S8+
SmilerOnline said:
When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
Or does anyone know how to fix this?
Click to expand...
Click to collapse
What version of the phone app are you using?
Do mention other details as well like Exynos or SD, and whether it's a WiFi call, VoLTE or just an ordinary phone call.
I had the same issue a couple weeks after updating the phone or contacts app with an apk file, cant remember which one it was.
Stranger thing was that when I wanted to make a call it actually did make the call while the popup was there that phone app was closed.
As I was not able to uninstall the update I did a factory reset of my S8+. Same issue was there after the reset, I ended up doing a clean flash with odin. Everything is fine now.
thuglife said:
I had the same issue a couple weeks after updating the phone or contacts app with an apk file, cant remember which one it was.
Stranger thing was that when I wanted to make a call it actually did make the call while the popup was there that phone app was closed.
As I was not able to uninstall the update I did a factory reset of my S8+. Same issue was there after the reset, I ended up doing a clean flash with odin. Everything is fine now.
Click to expand...
Click to collapse
That may have been what has happened to me, as I updated the phone/contacts apk's a few weeks back...
Thanks guys!
I'm guessing that I am going to need to find the default apk and restore it (com.android.phone)
*UPDATE/FIXED*
Just in case this affects anyone in the future.
I fixed it by using 'Package disabler pro' to uninstall the updates for the package 'com.samsung.android.incallui'.
I figured it out by monitoring the logcat (to monitor background errors from the developer tools), and I spotted that the error was coming from this package, so after removing all updates for it, now all works fine again.
I hope that this will save anyone from having to re-flash in the future!
I just used PDP to uninstall it as I find that tool to be quite effective at showing all info needed about the package before making any changes, but I'm sure that you can remove the updates with any other app!
@thuglife:
You may want to take note just in case it happens again in the future!