[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 all
It all started last night when I added a second Twitter account to my official Twitter app. The dreaded android.process.acore appeared every second.
I've tried all the fixes - clearing the contact storage, removing my Google Account, deleting all my contacts from google.com/contacts, clearing the cache from recovery, restoring contact storage/Twitter from a Titanuim backup...
The only thing that gets rid of the message is disabling contact storage altogether. That, obviously, isn't a long term solution. The instant it's re-enabled I get the android.process.acore error messages again.
Does anyone have any other ideas? I'm worried if I take the plunge and factory restore It's still going to be there. I really don't want to do that if possible.
Thanks.
EDIT: Found the problem using Privacy Guard in CM12. I reset all the allowed/denied counters, enabled Contact Storage, let it error 3 times, disabled it and went back into Privacy Guard. Google and Telegram had accessed "red contacts" 3 times. Uninstalled Telegram and tried again. Still erroring. Uninstalled Google and all's well. Shame though, I use Google Now a lot. Looking for a fix for that now.
EDIT 2: Writted a post about the whole thing here if anyone wants to read it: http://techspert.info/2015/08/21/solved-android-process-acore-has-stopped-on-cyanogenmod/
T-Mobile S6 running XtreStoLitr 3.3.1. I'm currently dealing with the aforementioned error whenever I open the stock dialer. I've cleared the app data and cache for both Contacts and the Dialer, which alleviates the issue briefly. I initially thought it had something to do with root, so I disabled Greenify, PowerNap, Naptime, and Amplify to no avail. I went into safe mode and cleared the app/data cache--when I first got the issue, simply going into safe mode and clearing the data fixed the issue until the day before, where it popped up again--and that served to be a momentary solution.
I've wiped data, restored the firmware, downgraded to 3.3, deleted my contacts from my phone--and from my Google account apparently, but that's a different story--but nothing seems to have addressed this issue. I'm currently doing another full wipe/restore. The last time I went through this process, I redownloaded all of my apps manually rather than using SmartSwitch, and it didn't help much long term.
And since I figure that this issue will likely happen again once I restore my data, is there a way to determine what the cause is? I assume that it's one of my apps at this point that's constantly causing the issue.
Hi y'all, hope someone can help me with this since I can't seem to find anything on Google about the issue I'm having...
I got adventurous rooting my phone (running Lollipop 5.0) a while back to disable/ delete some carrier bloatware. All was great until the other day when I used Titanium to delete the AT&T Address Book. I immediately got a popup error "Unfortunately, AT&T Address Book has stopped." When I click OK it just keeps perpetually popping up like a zombie. While the phone technically works, it's effectively unusable with that constant popup message.
I tried restoring the system app + data Titanium backup but no dice. Also factory reset the phone with the hope of being able to then flash the stock ROM back to it but not only does the popup STILL happen, but during the welcome setup process I can't get past the screen lock setup part without the Google setup service (or whatever it's called) ALSO giving the "has stopped" error and crashing :laugh::crying: What have I done???
If you haven't solved you problem yet the way to stop the AT&T Address Book from nagging you is:
Open the dialer
Enter *#*#2666#*#*
Click "Registration" and set it to "Completed"
IDK know about Google Setup error, but I'd try clearing that app's cache as a possible fix.
yeswap said:
If you haven't solved you problem yet the way to stock the AT&T Address Book from nagging you is:
Open the dialer
Enter *#*#2666#*#*
Click "Registration" and set it to "Completed"
IDK know about Google Setup error, but I'd try clearing that app's cache as a possible fix.
Click to expand...
Click to collapse
Hi, thanks for reply. Unfortunately I cannot do either of those things because the phone will not let me bypass the new user setup process --- and I can't finish it without it crashing midway through. The only thing that can be done with the phone without completing the new user setup is make Emergency calls only. I'm hoping there's a way to connect it to the computer and do some kind of recovery boot to flash the stock ROM back to it so that I can reset it without the Address Book error constantly popping up.
Hi folks, had an issue with my camera/torch on my U11. I've had it for about 3 yrs and no troubles. It began crashing with the message "Unable to load the camera" and the torch icon was greyed out. I could see the samera dialog when I pressed the "Clear All" button, but it woul;dn't activate. The tech looked at it and said I could try a factory reset to see if that solves the problem, otherwise they could burn several hours troubleshooting software or replacing the camera, if that was the problem.
I have everything backed up on my Google account, messages, contacts, apps etc, so I tried the factory reset. Had some issues with Google Play crashing initially, once I got past the language change. The app crashed several times before I finally got it to load. Not wanting to restore everything at once, I skipped the step to restore apps from back up and data and went right to the clean phone. Now, when I try and open Google Play Store (or add a Google Account or anything Google), the app crashes just as it gets to the login screen. I've tried re-booting, clearing the cache, disabling the Boost+ as someone suggested in another forum, re-started, checked notifications and permissions but nothing seems to work...time for a new phone or does anyone have any ideas... thanks. Chris
ChrisinPerth said:
Hi folks, had an issue with my camera/torch on my U11. I've had it for about 3 yrs and no troubles. It began crashing with the message "Unable to load the camera" and the torch icon was greyed out. I could see the camera dialog when I pressed the "Clear All" button, but it wouldn't activate. The tech looked at it and said I could try a factory reset to see if that solves the problem, otherwise they could burn several hours troubleshooting software or replacing the camera, if that was the problem.
I have everything backed up on my Google account, messages, contacts, apps etc, so I tried the factory reset. Had some issues with Google Play crashing initially, once I got past the language change. The app crashed several times before I finally got it to load. Not wanting to restore everything at once, I skipped the step to restore apps from back up and data and went right to the clean phone. Now, when I try and open Google Play Store (or add a Google Account or anything Google), the app crashes just as it gets to the login screen. I've tried re-booting, clearing the cache, disabling the Boost+ as someone suggested in another forum, re-started, checked notifications and permissions but nothing seems to work...time for a new phone or does anyone have any ideas... thanks. Chris
Click to expand...
Click to collapse
I removed the micro-SD external storage and turned off the WiFi and it connected. Still no camera or torch/flashlight, which is why I went through the whole exercise to begin with. At least I can now log into Google (Play Store, GMail, accounts, etc)....
ChrisinPerth said:
I removed the micro-SD external storage and turned off the WiFi and it connected. Still no camera or torch/flashlight, which is why I went through the whole exercise to begin with. At least I can now log into Google (Play Store, GMail, accounts, etc)....
Click to expand...
Click to collapse
The only other option that i see is a ruu flash, if that doesnt fix the issue it could be a camera gone bad,, easy fix for the diy selfers, if you need a part pm me and i can see if i have it to send you,, good luck ,,, hth
hammered58 said:
The only other option that i see is a ruu flash, if that doesnt fix the issue it could be a camera gone bad,, easy fix for the diy selfers, if you need a part pm me and i can see if i have it to send you,, good luck ,,, hth
Click to expand...
Click to collapse
Thanks bud...while I am capable of going the DIT route, I'm time poor and have already burned a number of hours just getting to the point where I can now at least log in to my Google accounts to re-install apps and such. I will need a camera going forward, but will likely take the easy route that most camera makers prefer and buy a new one...I appreciate you taking your time to reply. Thanks!!