[solved] com.android.phone has stopped and also contacts and messaging

Search This thread

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
[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)
 
Last edited:
  • Like
Reactions: serkos and servex

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
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?
 
Last edited:

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
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 ...
 

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
SOLVED !!!!

after reactivating Contacts & Phone, also a brand new folder structure with logs.db was recreated automatically !!!!!

Everything is running smoothly now!!! yay!!!
 

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
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
 
Last edited:
  • Like
Reactions: DeViBos

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
You mention this "reactivating" step. Can you explain more about how to do this part?

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.
 
Last edited:
  • Like
Reactions: DeViBos

aztrack

New member
Oct 5, 2013
1
1
THANK YOU!!!!

I forgot to mention, also after the 2nd step you need to reboot.

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!!!
 
  • Like
Reactions: esilence

furboom1240

Senior Member
Dec 19, 2013
293
59
Erie Canal Zone
Namecards cannot be shared

[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)

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.
 
  • Like
Reactions: sorgo

esilence

Senior Member
Aug 1, 2013
74
21
Vienna
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 :)
 

ManSamVampire

Member
Dec 27, 2015
39
31
Same problem on my Redmi 1S

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 ...

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 !!!
 

Lennsen.

New member
Aug 25, 2016
1
0
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?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    [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)
    1
    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
    1
    You mention this "reactivating" step. Can you explain more about how to do this part?

    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.
    1
    THANK YOU!!!!

    I forgot to mention, also after the 2nd step you need to reboot.

    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!!!
    1
    Namecards cannot be shared

    [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)

    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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone