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
Related
Every like 5 minutes, a box pops up saying "SORRY!, The application mail (process com.htc.android.mail) has stopped unexpectedly. Please try again."
It also displays this message every time I open either my contacts or the mail app.
So.. I can't open my email or contacts.. and I need those.
Any ideas, or suggestions on how to fix this? Thanks!
did you root your phone?
did you flash any rom?
My first response would be to wipe the app data. Assuming you already did this and it didn't do anything, I searched for a possible solution. I found something below in the link.
http://www.nexusoneforum.net/forum/...android-email-has-stopped-unexpectedly-2.html
I tried deleting the account setup and everything and it did not fix anything.
so FYI, it turns out it had nothing to do with the setup, since it has been working all this time. However, as I found somewhere else, a certain email was causing this problem to happen. For some reason, a newsletter/email from buy.com was causing this problem. I basically went to my inbox from my computer... then moved the last few days of email to a temporary folder. Sure enough the email app stopped crashing. I moved the emails back into the inbox until I found the one that was causing it.
Ever since the ICS upgrade, one contact's message thread refuses to open and is stuck on "O Loading" with that little circle revolving.
I downloaded go sms pro before and I was able to access his thread through that and the message count wasn't over the maximum limit per contact. I've since gone back to the stock app as he's out of the country and it's faster than go sms pro but he recently txted me and caused the problem to occur with other contacts (though a reset of the phone solves their issue)
Does anyone have a solution and failing that, advice? I should say right now that deleting his message thread is the last resort.
and HTC sensation
Android 4.0.3
Software 3.32.401.5
You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/
burningwipf said:
You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/
Click to expand...
Click to collapse
Aye I could try it with a contact whose messages I don't mind losing and seeing if that works, thanks for the tip!
You can also use Google Voice, and have it copy all the messages to your Gmail account.
Sent from my Galaxy Nexus using Tapatalk 2
So I started backing up and restoring and I was able to open all contacts' threads. The backup never fully restores all messages though and I have to keep hitting "restore" so that it'll restore them all up to the present day. Don't know why it's doing it this way.
Just now I've checked and that one contact won't open again. What I might do is try and restore all to the present, delete loads of messages I don't want, and backup this new message history.
I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!
3dd1 said:
I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!
Click to expand...
Click to collapse
Yeah it never resolved itself but I love the customisation of go sms pro so much that I don't mind anymore. Pity go sms pro crashes every so often and I think it slows the phone down.
I was going to start a new thread but see that this is the same problem I have.
I have a mt4gs (Doubleshot) and the problem described in this thread has happened twice. Both times i was receiving a text message and did something else with the phone at the same moment, and it seems to have jammed up the receipt of that text. The first time, i sent a text to the person at the same moment i received one. The second time, i locked the screen at the moment one arrived. Now that thread never loads, and loading other threads or contacts takes much longer than it should. In fact, i don't think contacts would ever load if i were willing to wait forever.
The first time I backed up the texts, reset the device, and restored, and everything worked fine, but that's a really time-consuming process and it seems like a ridiculous workaround for some broken buffer or queue in Android messaging.
It seems that there must be a direct fix for this. If it's easy enough to break messaging that it has happened to me twice, it must be a fairly common problem. But a search has turned up nothing but people saying there are too many messages or to use an alternative app for messaging. That's (1) incorrect and (2) again an ugly workaround for a problem with core functionality.
[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
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?
Hi guys,
I am facing a weird issue with my Whatsapp as mentioned in the title. The Whatsapp keep stopping/force close when connected to the internet (either by WIFI or mobile data).
I have a LG V20, Nougat with latest version of Whatsapp installed. It was all good until a few days ago Whatsapp showed the error message "Unfortunately Whatsapp has stopped". It gave the options to open the app again or send feedback. When clicked on open app again, Whatsapp opened for a split second then showed the message " Whatsapp keeps stopping" and gave the options of close the app or send feedback. When opened Whatsapp again, it force closed and keep repeating the same error.
I did not update my phone nor done anything to it. I have the latest Whatsapp version installed before the error occurred. However, about 2 days before the error occurred, I did remove and re-add Google account. I don't think that would cause Whatsapp error as I don't register Whatsapp through Google account and during those 2 days Whatsapp was operating normally. I don't do backup to Google drive, all backups were done locally on phone.
I have done almost all necessary solutions to fix the error but none of them work. I have:
1. restarted the phone
2. rebooted the phone into safe mode
3. cleared cache and data of Whatsapp
4. uninstalled and reinstalled Whatsapp from Google play store
5. uninstalled and reinstalled Whatsapp from Whatsapp's official website
None of the above works. The Whatsapp will force close when the phone is connected to internet. Until recently I noticed that, when the phone is totally disconnected from internet, Whatsapp can be opened normally. With the Whatsapp opened and I connect the phone to internet, it immediately show the error and force close. How strange is that?
So now, I only can type messages in offline mode and press send before connect the phone to internet. The messages can be sent out by keep opening Whatsapp repeatedly. Incoming messages are delayed and no notification at all, I have to periodically keep re-open the Whatsapp to check for new messages. When there are new messages I have to read them in offline mode. This is so frustrating.
I googled and the only one came to this:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
They seemed to have same problem (with different phones) with me and no solution.
In the mean time, I am also contacting Whatsapp support team, but their replies so far did not answer my problem.
Any solution to this weird issue would be very much appreciated.
Thank you