Hello All,
I have had this problems several times in the past and just recently experienced the same issue again. I search for a solution and tried everything from re-entering the message center number to factory resetting the phone and starting again. The latter was the only thing that worked for me in the past, but this time I refused to loose and start over.
My case may not be your case, but it shows that digging a little deeper may help you solve the issue. After solving the issue this time, I realized that the same issue may have been causing this issue in the past. I always install some type of start up manager and it is usually ES Task Manager, which has a Start-Up Manager.
I have always disabled all application from starting on boot that are not android system apps, including the stock messaging app. I believed that starting the app after the boot would be fine, but in the stock messaging app's case this was not true. For some reason if the app is not starting during boot, you are not able to send SMS. So after re-enabling this app all SMS issues disappeared.
I hope this helps those that have been plagued with this issue.
Glad ya fixed it!
Related
This just happened this morning and is a very big problem for me as I message a lot. I got a force close a few hours ago after opening the stock messages app, upon relaunching it all my messages were gone. I luckily had back ups, although I had not run it for about 2 - 3 weeks, so all messages from that time scale are now gone. So I restored what I had using SMS Backup & Restore (which I have now set to auto backup) I sent one SMS before the app force closed again, once again losing all my messages, but this time when I hit 'Compose Message' the app force closes, it does this every time I hit that button. As I said this is a huge problem for me, I'm currently running a stock 2.2 ROM from Vodafone, I have yet to root it.
On a side note, I did find another thread with people that had lost their all their SMS messages, but nobody reported continually force closing, and there weren't any fixes/answers in that thread which is why I created a new one.
EDIT: I had tried restarting the phone a few times which didn't help, but decided to pull the battery this time which seems to have done the trick. Currently restoring my SMS messages atm. I will update this if it happens again. But would still like to know the cause of this, as it seems I am not the only one affected.
Alright, so I was trying to use a program that some other people have said work fine but it wouldn't work, so I figured I would unroot/reroot and see if it helped. I restored the phone to factory settings, used the instructions that are readily available here and other places to unroot my phone and rooted it using the manual method (just like I did the day I got my phone) and tried to set everything back up, but have run into a few problems.
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
2) Google Wallet
-Was working fine, even used it at McDonald's, but now when I try to load it up for the first time, it sits at a black screen until eventually it says "Wallet is not responding. Would you like to close it? (Wait) (OK)"
Oh, and the program that I originally went through all of this for is still giving me the same error about not being able to locate a partition to remount to write to. What do I need to do to get this thing back to working correctly?
shane_huskey said:
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
Click to expand...
Click to collapse
This is happening to me! I am rooted, completely stock otherwise and using Handcent. Is this a handcent issue? Anyone have more insight into this?
I'm in the process of unrooting my phone again to see if it happens when I'm not rooted.
Update:
Unrooted, same issue with Google Wallet and messaging
Rooted again, same issue
I was kindof hoping that someone would have come in here by now with some "here, try this" or "yeah, that happened to me and this is how I fixed it" type post. Am I the first person that has run across these issues after flashing to stock files from code.google.com?
I'm on 2nd nexus and haven't had that issue with handcent on either phones. Stock or rooted..
Sent from my Galaxy Nexus using XDA App
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Well the 3 obvious problems could be:
1) I am either following the steps to unrooting incorrectly. (I don't think that it is rooting that is causing the problem since I a) didn't have the problem before I unrooted the first time and b) the problem is recreated whether I am rooted or not.)
2) My phone is faulty
3) The files that I am using (downloaded directly from http://code.google.com/android/nexus/images.html) are damaged.
The MD5 matches the .tgz file.
Everything looks like it is going through correctly when I am flashing the files.
I don't think that I am following the instructions in correctly, so that narrows it down (in my head anyway). Has anyone else used the factory images for code.google.com? Have you tried running Google Wallet afterwards?
esuohe said:
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I have tried going into settings, force closing the app and clearing cache and I have tried resetting the phone to factory defaults. Neither changed how the app behaved. I still just get a black screen with the not responding message.
I did some more research into the Handcent problem, apparently it is fairly widespread on ICS and goSMS has the same issue. Stock is apparently not affected, so I am using that but it sucks...
I have seen a few of the GoSMS and Handcent posts, but I'm not completely sure that I am experiencing the same issue. Every post I have seen speaks of erratic problems. Mine is with every text message. Also, it didn't start happening until I flashed the factory images from code.google.com. Also, the problem only popped up when I started experiencing other problems (like with Google Wallet). Although we are having a similar issue, I believe the root problem of the issue is different, which is why the issues are slightly different.
Went and exchanged my phone today, rooted as soon as I walked in the door, installed everything back to the way that I had it and everything is working fine again. On my way to McDonald's for lunch.
All on my Zenfone 2. Starting today, in addition to never getting notified when receiving a message I found when emailing people I was trying to text they weren't getting my texts nor I theirs. After going through the helps apps one of the suggestions to do was a factory reset. Reluctantly I did that only to find that the problem persisted as well as realizing I could no longer connect to my WiFi which caused me not to be able to download all my apps that had been backed up. Haven't found any solutions as of yet.
For months I have hardly problems with this android.process.acore has ended message in my cm11 rooted fire phone installed nano GAPPS (but even with other versions of GAPPS the Problem stayed the same). I have no idea what to do any more, flashed and backuped everything again and again, deleted and restored the contact-datas the way it is discussed in many forums. The problem disappears while disabeling the contact-storage, but this way I cannot use my Fire Phone for phoning from the contacs anymore much less using contacts in Whatsapp . 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!
That's strange, has there been any recent updates to your phone?, i don't know how long you've been on cm11 but amazon recently stopped supporting Facebook who also owns whatsapp. I know someone on stock whose messenger and whatsapp stopped working and the tech on mayday had to relay that to them. Idk if they stopped support through an update or some other means since I haven't been on stock for a very long time. My advice would be to take a logcat and post the issue in the cm11 thread if you can
<romario3600> Thanks for yor advice. I've been with CM 11 from the very beginning and I don't really remember when the problem started, might be like half a year before.. That's weird, for any reasons that android. access. accore disappeared now after uninstalling both facebook and its messenger. Didn't know that the support stopped and this might have caused it. I got a solution now with a third party facebook version by apache. It's working well until I found a solution for my problem.
I have still no idea...
Now the android.process.acore is happening again. I uninstalled all the apps (facevook and it's messenger) that caused the malfunction. Now I got another app called Immonet that claimed the same rights with synchronisation owitg contact data. I uninstalled this app with all data and even wiped the old folders. But the error promt does not disappear anymore I did not find anything all over the net anyone having the same problems that I do.. Anyone got an idea how to solve this one out? I'm so much disappointed,hardly thinking of buying another phone but I like this fire phone with CM11 a lot.
ticklisheye said:
Now the android.process.acore is happening again. I uninstalled all the apps (facevook and it's messenger) that caused the malfunction. Now I got another app called Immonet that claimed the same rights with synchronisation owitg contact data. I uninstalled this app with all data and even wiped the old folders. But the error promt does not disappear anymore I did not find anything all over the net anyone having the same problems that I do.. Anyone got an idea how to solve this one out? I'm so much disappointed,hardly thinking of buying another phone but I like this fire phone with CM11 a lot.
Click to expand...
Click to collapse
As a last resort if you have the time and effort to put in, id say revert to stock and do a factory reset the normal way using the fire phone's recovery. That should at least ensure that everything is wiped and back to default. After that try downloading and installing CM11 again, don't cut any corners where you might have to wonder if something went wrong. Once the systems boots properly try installing the play store as well as messenger and whatsapp and see how things go from there. avoid rooting the device until you are sure things work
I got another completely new fire phone, rooten CM11 now from the latest FireOS 4.6.1..1. and at the beginning everything worked fine up to now. Now I got the same android.process.accore message again on this completely different device. As this problems is not very common I got now the idea that it might have anything to do with the synchronisation of google contact and it's permission management with these programs that have the rights to read sync the contact storage. But no idea ehat it might be exactly. A while ago I deleted all my contacts on the Google server. Is it possible that the synchronisation got a problem now with my different devices that were once registered on the server with not always having the very same telephone directories? How to solve it if my venture is right?
I just solved this (I hope, so far so good) on my Sony Xperia Z2 tablet. I cleared data on any and every app that had anything to do with Contacts. I went right down the list in All Apps. If it used contacts, I cleared it. That meant Gmail and Hangouts, Messenger, etc.
Before I did this, I tried to write an email and litterally had the error with every single letter. Since I did this, I haven't seen it once. I wrote out an email address on a draft email and posted 2 posts (this will be the third) here. No error yet!
Not an expert. Just a user and fellow acore victim, sharing what worked for me. Though I have been in tech support for 17 years (just more of a Windows PC tech really).
Gabrielle
I will check this out on the weekend when there's some time for me doing so. Will tell you if it worked.
OK, so I like many others have had some serious problems with the Android 10 in place update. So I decided to do a factory reset, and this time, actually rely (and pray) on Google backup and restore.
Shockingly, restore worked pretty well, and it generally put the phone back to the way it was.
I did the wipe/restore because since the Q update, phone calls don't show up on the sleep screen. The phone remains black, and I have no idea that people are calling if I have it on silent. The restore didn't fix it unfortunately....
But what did happen, is that when SMS was restored, the only app I can see them correctly in is Google Messages. I'd been using Chomp for years, but the messages load completely randomly there. I tried deleting Chomp, clearing its cache and storage, but nothing works. Also tried Textra and its random as well.
Obviously, the SMS database is loaded correctly as it works fine in Googles base app
No idea what to do from here. Any thoughts appreciated.....