[SOLVED]
I can not get into the phone call (green phone button) to the dialer, this is the main problem; when I open it, it hangs for a few seconds then I get a message box centered in the middle of the screen: Contacts has stopped. - only OK button to press; and pressing returns to homescreen.
Everytime after sending an SMS I get: "messaging has stopped", although still I can send.
I can access the contacts normally and also everything else is fine. when I start calling someone from there, it works also fine, with the resemling dialer(?) look while talking. But then right after finishing call, again a message pops up: com.android.phone has stopped
- resulting that the calls are not being logged.
the app "GO Contacts Ex" would be ok as an alternative, but here again, after the call ends, the message comes up: com.android.phone has stopped. also other apps like contact+/dialer+ and exDialer&contacts seem like that all using somehow com.android.phone in the end and causing that error message box coming up.
if no fix, is there an alternative app totally replacing the usage of com.android.phone? so that I could use another app?
I have found and tried some suggestions from google to this problem, but none of them helped..
deleting cache in: apps -> all -> contacts memory and contacts and phone, & reboot; - several tries, also SIM card out, and reloads, re-sync;
uninstalled recent updated apps; reboots, sim out, re sync etc.
It seems like there is one small thing interrupting but I can be wrong.
I dont wish to do a factory reset first, and lose all my apps and settings. Before doing that desperately, I would like know if someone could help me out in here? It could be one small setting or stuff to do
I am using JB 4.1.2 rooted
it is possible that I disabled some important processes earlier which caused that, but I enabled them all again and restarted, still nothing changed. otherwise this problem started surely after recent app updates, which i also tried undone and checked
any help is appreciated!
SOLUTION
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. Activate these apps. Reboot again.
Another reason for "com.android.phone has stopped" coming up is when you previously deactivated com.movial.ipprovider, or if it is damaged, which is needed to connect to the internet. The error starts coming permanently as soon the phone trys to connect to the internet.
Solution: just stop com.movial.ipprovider, delete its cache and reboot! (or reinstall it)
I can avoid the first two problems (contacts and messaging has stopped) by simply using a different app which I at least like better (Dialer+ / Contacts+ including sms), and have deactivated the stock versions now (contact and messaging). - and I am happy with that!
the problem with com.android.phone still remains after each call, for both incoming and outgoing. the bothering thing is that error message box, and that the calls are not being logged at all, but sms messages are logged fine.
(I could not find any app that could be an alternative to this com.android.phone, similar to the contacts and messages app. all the 3rd party caller and dialer apps uses com.android.phone in the end when dialing. if i uninstall com.android.phone, there is only skype as an alternative to call. and uninstalling skype gives then no possible ways to call a number. so I need to fix this somehow.)
problems:
1. message "the process com.android.phone has stopped" after every calls.
2. no calls are logged
please find attached a logcat logs when that happens, maybe someone can understand what is causing this (look for com.android.phone).
what is for example E ActivityThread: Failed to find provider info for logs ?
and what can you suggest me?
I got it !!!
I searched and located the file on where the calls logs are being saved: data/data/com.sec.android.provider.logsprovider/databases/logs.db
As I thought it could be damaged. I cleared the cache from LogsProvider and restarted it, and the error is now gone since then!
But clearing also deleted all the files in its folder including the logs.db. Unfortunately it doesnt recreate this files, even after a reboot. How can I get these structure and basic files again?
Can someone copy this for me? or can I use any logprovider files from internet?...
will check ...
SOLVED !!!!
after reactivating Contacts & Phone, also a brand new folder structure with logs.db was recreated automatically !!!!!
Everything is running smoothly now!!! yay!!!
Just FYI and to summarize, in case it happens to you. it was either logs.db file or something in logsprovider folder damaged.
SOLUTION: just stopped com.android.phone and logsprovider service, and deleted the cache from both. then reactivating them should be ok! then just reboot!
cheers
You mention this "reactivating" step. Can you explain more about how to do this part?
kenkamm said:
You mention this "reactivating" step. Can you explain more about how to do this part?
Click to expand...
Click to collapse
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps. Edit: reboot again.
esilence said:
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps again.
Click to expand...
Click to collapse
Thanks! Next time I feel brave and re install xposed I will give this try.
kenkamm said:
Thanks! Next time I feel brave and re install xposed I will give this try.
Click to expand...
Click to collapse
I forgot to mention, also after the 2nd step you need to reboot.
THANK YOU!!!!
esilence said:
I forgot to mention, also after the 2nd step you need to reboot.
Click to expand...
Click to collapse
OMG, I've been dealing with that darn com.android.phone error for nearly a year now ==== and you solved it for me!!! I can't tell you how happy and thankful I am. After every call in/outbound I would get that pesky error! NOW I'M FREE AGAIN!!!!! WOOO HOOOO!!!
I am glad that I could help! you obviously just joined and posted because of me to tell about this.. thank you
Namecards cannot be shared
esilence said:
[SOLVED]
SOLUTION
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. Activate these apps. Reboot again.
Another reason for "com.android.phone has stopped" coming up is when you previously deactivated com.movial.ipprovider, or if it is damaged, which is needed to connect to the internet. The error starts coming permanently as soon the phone trys to connect to the internet.
Solution: just stop com.movial.ipprovider, delete its cache and reboot! (or reinstall it)
Click to expand...
Click to collapse
I was looking at this and hoping these drastic moves could fix the reason I cannot share my contacts using the share command. It force closes afterwards.
Sadly, I've tried all of this and my contacts still cannot share. So you have any idea what could be wrong with my Galaxy S Relay? I am rooted (but using stock 4.1.2) at this time, and have only removed bloatware such as Evernote, Slacker, etc.
Thank you !!
esilence said:
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps. Edit: reboot again.
Click to expand...
Click to collapse
Worked like a charm on Samsung S5 Mini.
sorry @furboom1240 i missed that topic here and didnt see your message earlier. but i have no idea what could have solved your issue either. it relates to something else i guess, hope u had luck in the meantime and solved
@DeViBos thanks another new user and first post, i appreciate! welcome to xda and have fun
Is it possible to try this method to other brand like HTC example? Because Phone can't force stop and there's no logsprovider. Where it can be found?
Just as I will do now. Thank you sooooo much I thot my phone was a hacked mess. The world just became a better place!
Same problem on my Redmi 1S
esilence said:
I got it !!!
I searched and located the file on where the calls logs are being saved: data/data/com.sec.android.provider.logsprovider/databases/logs.db
As I thought it could be damaged. I cleared the cache from LogsProvider and restarted it, and the error is now gone since then!
But clearing also deleted all the files in its folder including the logs.db. Unfortunately it doesnt recreate this files, even after a reboot. How can I get these structure and basic files again?
Can someone copy this for me? or can I use any logprovider files from internet?...
will check ...
Click to expand...
Click to collapse
Sorry for waking an old thread. I am facing a similar problem.
My Device is -
Xiaomi Redmi 1SW (Rooted)
Android 4.4.4
MIUI 7.2.3.0 KHCMIDA
I have removed all bloatware as mentioned in this post (http://forum.xda-developers.com/xia...-to-remove-bloatware-list-miui-t2999283/page2) and also another app called 'Xiaomi Service Framework' if these are causing the problem.
I was earlier facing this problem when I was using MIUI 7.1.1.0 KHCMICH (Rooted and Xposed installed). It suddenly started occurring as soon as I connected my phone to the PC before even doing anything. The pop-ups (Unfortunately Phone has stopped) became irritating. Luckily, I had USB debugging enabled. I connected the phone to the computer and put the following in the CMD -
adb devices
adb shell
su
pm disable com.android.phone
exit
exit
exit
Then the window stopped appearing. So I (mark this) turned off Wi-Fi and disconnected phone from PC. I was using the phone normally for few hours. But I realized that outgoing calls on my phone were not possible (the system dialer (com.android.contacts) closed after pressing the call button) and no incoming calls were being recorded (I use the in-built call record feature in the system dialer app). So I connected my phone back to the computer and wrote
pm enable com.android.phone
in place of pm disable com.android.phone keeping all above mentioned commands same.
This time the window did not appear. I was able to make and record calls perfectly. But on the same day, when I again switched on Wi-Fi, the window started reappearing. So I used my device by keeping the com.android.phone disabled for few days.
After few days, I got an OTA update to MIUI 7.2.3.0 KHCMIDA. I thought it would solve the problem.
I also wanted to reset my device because it had lot of junk. So, I flashed the update, rooted the device, removed all bloatware apps again (which came after the update) and shut down my phone. The error window hadn't appeared yet though com.android.phone was enabled and Wi-Fi was connected.
Then I booted into recovery and erased the cache and data partitions (NOT the internal storage). Then after phone was booted and as soon as all setup was done, the error window started coming up again.
So, I don't think that data/data/com.sec.android.provider.logsprovider/databases/logs.db has any problem because it was erased completely after I wiped data.
I need HELP !!!
I get the same message (com.android.phone and a few others) over and over again and my phone is veeeeery slow. It all started after I put my SIM-card into the phone for the first time. I have an S7 with SuperMan-ROM installed. I can't deactivate my "contacts", it just doesn't let me push the deactivate-button. Plus I can't find the phone-app or logsprovider. Is there a different appmanager apart from the stock which I could use to delete and deactivate?
Hi
i have problem in samsung j5 2016 regarding com.android.phone has been stop this message shown after each second and also not showing mobile network
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
This issue has just started happening to me over the past 2-3 days, and I cannot figure out a permanent fix for it! Let me start by saying that my OPO is not rooted, and the only updates to the ROM have been the official ones that have been released (I'm currently on CM version 11.0-XNPH44S). Every time I attempt to open the Play Store, it crashes immediately afterward with the "unfortunately google play store has stopped" error. I looked at the error report and it states : [CRASH] com.android.vending threw java.lang.IllegalArguementException as the subject then the first line of the content reads: "java.lang.illegalarguementexception: view android.widget.listview{41ab7730 VFED.VC. .F...... 0,0-1080,1845 #7f0a02dd app:id/play_drawer_list} is not a drawer".
I know nothing about Java, so I have no idea what this means, and there are 18 lines of equally incomprehensible text after that. I've tried clearing the data, cache, etc. from the app with no change. The only thing that works is when I uninstall the updates, taking the Play Store back to v. 4.9.13. However, in almost all cases it auto-updates immediately back to 5.1.1, so I'm still not able to use it. I read somewhere about disabling the background data usage in settings, but then you're not allowed to download anything from the store.
Is anyone else having the same issue, or can you suggest an idea as to how to fix it without my rooting the device and having to back up the nearly 700 apps I have on it? TYSM in advance!
sternrulez said:
This issue has just started happening to me over the past 2-3 days, and I cannot figure out a permanent fix for it! Let me start by saying that my OPO is not rooted, and the only updates to the ROM have been the official ones that have been released (I'm currently on CM version 11.0-XNPH44S). Every time I attempt to open the Play Store, it crashes immediately afterward with the "unfortunately google play store has stopped" error. I looked at the error report and it states : [CRASH] com.android.vending threw java.lang.IllegalArguementException as the subject then the first line of the content reads: "java.lang.illegalarguementexception: view android.widget.listview{41ab7730 VFED.VC. .F...... 0,0-1080,1845 #7f0a02dd app:id/play_drawer_list} is not a drawer".
I know nothing about Java, so I have no idea what this means, and there are 18 lines of equally incomprehensible text after that. I've tried clearing the data, cache, etc. from the app with no change. The only thing that works is when I uninstall the updates, taking the Play Store back to v. 4.9.13. However, in almost all cases it auto-updates immediately back to 5.1.1, so I'm still not able to use it. I read somewhere about disabling the background data usage in settings, but then you're not allowed to download anything from the store.
Is anyone else having the same issue, or can you suggest an idea as to how to fix it without my rooting the device and having to back up the nearly 700 apps I have on it? TYSM in advance!
Click to expand...
Click to collapse
Hallo ,
I have exactly the same problem and fail to solve,If anyone can help I would be grateful !
Same problem here, any fix yet?
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
After many long attempts to fix this I have come up empty handed. I believe the Hardware is either corrupted or damaged but need an expert to help confirm. (it doesnt even seem worth it at this point to fix, but i want to try anyways, its my kids tablet) I will add as much detail as possible.
First the tablet would get stuck in booting (A9 screen) found that this is due to a corrupted firmware. I flashed a firmware onto the device and it was able to boot up, however still with a few issues. google play store when updated would instantly crash "google play store has stopped" the second you clicked to use it. the only fix i found for this was to uninstalled the google play store update back to factory and it would worked, with the problem of some apps had to be downloaded over and over until it decided to complete, often finishing with a package file invalid. but i managed to get a few games and whatever and gave it back to my daughter.
after about a week everything crashed at once on boot up. process.google.gapps would crash over and over and over as soon as you click ok, many other apps crashing as well and just repeating google account manager, Key chain, RS OTA, and others i cant remember at this time (the problem is currently not occurring or i would go get this information.) mostly the gapps process was crashed over and over making the tablet unusable due to constantly trying to click these errors.
Odd behaviour, during that i managed to click and quickly select settings, and went in and deleted a bunch of apps or uninstalled updates on ones that were crashing, i could uninstalled enough to stop all the errors.. then i rebooted the tablet.. and all the errors were back, and everything i uninstalled was back too, how the f**k?! lol.
i attempted such things as going into recovery and deleting all the cache and media, nothing. so i flashed it again.
the above error return after some time. and i flashed it again (my daughter wanted it working this seems to be my only quick and temporary fix, i have disabled many apps and stopped it from automatically updating, however i still found some settings after being changed, to be undone back to the way it was before i changed it after rebooting the tablet. again it always crashes when google play store updates. this time i rebooted the tablet and went to update the store, and now the app can NOT be found in the store. there does not even seen like a way to update the tablet like "here is your only buggy version, have fun"
CORRECTION: Google Play Store could not be updated because after restarting the tablet the updates were back, as if i had never uninstalled them. i didnt bother checking the first time because this is very unusual.
I am willing to root, change, hack, smash, throw out the window, put it in the hydraulic press at work...i dont care lol
i believe the hard drive has damage.
(i didnt run thru all the attempts i have made to fix things, cause i could write a novel. Thank you for reading.
- Kontr4 -