Dear All,
i Just got Samsung Galaxy tab 2 7.0 running Androide 4.0.3 a month back, it's a nice thing to have, however, now for some reason, every app i opens gives me the following msg: "Unfortunately, application stopped", all applications such as whatsapp, messages, anything, i get the same error, for example i open the messages folder, if i click on any msg inside it, i get ""Unfortunately, messages stooped" and the application closes.
i tried, restarting the Tab many times, shut it down, but still getting the same thing.
anyone had this problem before? any ideas how i can fix that?
your help is highly appreciated
have a nice evening
Gea-
[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
Hello, I have a rooted Metro PCS ZTE obsidian z820 and running Android 5.1 , with stock ROM and I really don't know much but I have been starting to learn.
Anyways I've had to restore a backup from recovery at least 4 times already because one day my phone died and I left it off and let it charge but when I powered it back on I got the message 'unfortunately the process com. google.android.gapps' has stopped' repeatedly making it impossible to do anything. once I restored my backup I searched everywhere , started looking at Logs from alogcat(which im also a beginner at), and cant seem to find any thing actuallly related to MY problem. I need to fix that problem from happening before it happens.
sadly when l made my backup my phone was already acting up and FORCE CLOSING MULTIPLE APPS. i.e when try to open a text message (through the notification or the app itself) with the stock messaging app it will force close. I've been unable to reply or read more then the preview of the messages so I tried to just compose a new message to respond but as soon as I click send it force closes, and the message still gets sent.
The play store also started force closing when I would click 'see more' on any apps description.
Gmail & Inbox by Gmail also force close when trying to read a message . These aren't the only apps that have started messing up. I very desperatly need help I CANNOT afford another new phone. I don't know if it's because I rooted in phone or what? but how do I know?
UPDATE!!: I accidently opened Google maps and I started seeing 'unfortunately the process com.google.android.gapps has stopped ' repeatedly again. I restored my back up again and almost every one of my apps force close upon opening now or it seems like once inside an app I try to read anything like 'see more' or description of open emails or messages it force closes?
Firefox, Apptoid app-store, orbot, Esfile-Explorer pro, lucky patcher, catlog, are im pretty sure the only mostly working apps.
GloUnicorns said:
Hello, I have a rooted Metro PCS ZTE obsidian z820 and running Android 5.1 , with stock ROM and I really don't know much but I have been starting to learn.
Anyways I've had to restore a backup from recovery at least 4 times already because one day my phone died and I left it off and let it charge but when I powered it back on I got the message 'unfortunately the process com. google.android.gapps' has stopped' repeatedly making it impossible to do anything. once I restored my backup I searched everywhere , started looking at Logs from alogcat(which im also a beginner at), and cant seem to find any thing actuallly related to MY problem. I need to fix that problem from happening before it happens.
sadly when l made my backup my phone was already acting up and FORCE CLOSING MULTIPLE APPS. i.e when try to open a text message (through the notification or the app itself) with the stock messaging app it will force close. I've been unable to reply or read more then the preview of the messages so I tried to just compose a new message to respond but as soon as I click send it force closes, and the message still gets sent.
The play store also started force closing when I would click 'see more' on any apps description.
Gmail & Inbox by Gmail also force close when trying to read a message . These aren't the only apps that have started messing up. I very desperatly need help I CANNOT afford another new phone. I don't know if it's because I rooted in phone or what? but how do I know?
UPDATE!!: I accidently opened Google maps and I started seeing 'unfortunately the process com.google.android.gapps has stopped ' repeatedly again. I restored my back up again and almost every one of my apps force close upon opening now or it seems like once inside an app I try to read anything like 'see more' or description of open emails or messages it force closes?
Firefox, Apptoid app-store, orbot, Esfile-Explorer pro, lucky patcher, catlog, are im pretty sure the only mostly working apps.
Click to expand...
Click to collapse
Here are the roms that everyone is looking for
drive.google.com/open?id=1Pk-Duhdt0svif8YYLY8NYk6tOG-bRL2k
For a while now I have hardly problems with this android.process.acore has ended message in my cm11 rooted fire phone for months now. I have no idea any more what to do, flashed and backuped everything again and again, deleted and restored the contact-datas. The problem disappears while disabeling the contact-storage, but this way I cannot use my Fire Phone for phoning from the contacs anymore. The problem seems to come along with WhatsApp and Facebook and its Messenger, but once installed the problem android.process.acore does not disappear when uninstalling these programs. Anyone got an idea? Thanks a lot for your help!
Reposted
http://forum.xda-developers.com/fire-phone/general/android-process-acore-cm-11-rooted-fire-t3477414
Thread closed
Hi, i hope to be posting in the correct section since this is my first thread here.
i recently bought a Z3 Dual and everything was fine, i updated firmware to Marshmallow and did factory reset (just to be sure that everything was ok after update), so i started installing various apps i had on other phones (Avast, Truecaller, Dropbox, CCleaner, Clean master, Games and other stuff, i'll post the entire app list if needed) and the phone started randomly crash with on-screen message "System UI unfortunately stopped" giving me only "ok" button, with the message continuously popping out, so i can't pass lockscreen and i'm forced to shutdown phone or reset via power button.
As the phone is on again everything is fine, but after some time it crashes again.
I tried to do a "Manual Debug" and find which app needed to be uninstalled so i tried one by one but without any luck (i've successfully get the device running without problem for 2 days but unfortunately i have not understood which app was causing the crash)
i did a Logcat but since i can't read it (i only found "BEGINNING OF CRASH" with Notepad++) i don't know what else to do, I thank you in advance for your willingness to help me with this (probably the stupidest) problem
HTML:
https://pastebin.com/MWknKjnM
it happened again, here's another logcat, exactly at 02-19 16:05:27.079
HTML:
https://pastebin.com/StBycp9H
just resolved... last poweramp (beta) update caused the issue.
a rollback to stable release solved the problem