Something happened to my over the weekend. I found it had reset and kept resetting on the loading screen. I took the battery out, popped it on and turned it on. It made it to the home screen but all the apps I had stored on the SD card would close unexpectedly. It looked like ext2 partition crapped out or something as none of those apps would run. So I restored a backup from Nandroid and everything was working again EXCEPT for my SMS/MMS.
Whenever I go into messages, it crashes with a "force close" prompt stating com.android.mms closed unexpectedly. I'm thinking if I could clear all the messages I had save that would solve the problem, but I have no clue where they're stored.
Any advice?
Found what I needed here: http://forum.xda-developers.com/showthread.php?p=2976069&highlight=messages+stored#post2976069
I deleted the DB with the messages, all is well.
same problem here,
clicking "sms" pops up an error msg "com.android.mms ended unexpected"
I have not found any .db files yet :-(
Hello,
Did you deleted mmssms.db or some of "PART_XXXXXXXXXX" files too?
Thanks!
Deleting the mmssms.db file
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
VirtuallyNadine said:
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
Click to expand...
Click to collapse
I have the same problem. Did you permanently delete the database or is it still there? Cos I tried to delete the database throught root explorer but it still remains altho it has deleted all the messages saved in it.
any news on the com.android.mms subject????? I feel very frustrated with my android and i looked everywhere on the internet and can't manage to fix it!
A possible fix
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
echoota said:
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
Click to expand...
Click to collapse
Works for me thanks
Related
I was getting this error for a while now. So here is the whole thing.
I was using JF1.5 along with Lucid's script. And I started getting errors such as...
"The application Messaging (process com.android.mms) has stopped unexpectedly."
along with, what seemed like, every other application I tried to use. I noticed that it was right about the time that JF1.51 came out, so I thought that maybe the programs I was using got updated without the system being updated or whatever.
I bricked my phone about 1000 times but, with a ton of help from Lucid, I was able to repair the error on the SD card and was problem free... for about a week.
Working fine this morning, I rebooted my phone and am now having the error again every time I try to open a messaging program. I was using ChompSMS the first time and am now using Handcent SMS. I have uninstalled both of them and cannot even open the stock messaging program without getting the error and need to force close.
I did the same steps as last time (as far as I can remember) which were:
- Factory wipe
- Apply JF1.51 update
- Download and run Lucid's script to get e2fsck
- Running e2fsck to make sure no errors
- Run Lucid REM for apps, data and dalvik
When I restart my phone I also get the same error from PF Voicemail+ but the option to wait is also there.
I am driving myself crazy trying to fix it. Everything I have searched for seems to only be problems with images, but mine is even opening the SMS program. BAHHHHHH!!!!!!
JF1.51 w/ Lucid REM
8GB SanDisk MicroSD HC
any news on that?
I also have an com.android.mms error.
I've removed some software via adb pull, rm, etc. but my manage applications list, still shows some of these pieces of software.
How can I clear this data to reflect true, current installations?
Thanks.
riggsandroid said:
I've removed some software via adb pull, rm, etc. but my manage applications list, still shows some of these pieces of software.
How can I clear this data to reflect true, current installations?
Thanks.
Click to expand...
Click to collapse
Was this answered? I need to know how to do this too. Searches throughout forum didn't find any results about this for me. Thanks.
I've found that if I open "com.smithmicro.DM" or "Download Manager" in Manage Applications and then "Clear Data" in either one of them, it refreshes the Manage Apps list and all the ghost apps are gone. But after every reboot these ghost apps are in the list again, so that isn't a permanent fix.
chromiumleaf said:
Was this answered? I need to know how to do this too. Searches throughout forum didn't find any results about this for me. Thanks.
I've found that if I open "com.smithmicro.DM" or "Download Manager" in Manage Applications and then "Clear Data" in either one of them, it refreshes the Manage Apps list and all the ghost apps are gone. But after every reboot these ghost apps are in the list again, so that isn't a permanent fix.
Click to expand...
Click to collapse
never got a response, and just sort of let it go. I'm sure there is a .db file somewhere that stores this information.
Anyone have any idea?
Try adb sync.
HeroMeng said:
Try adb sync.
Click to expand...
Click to collapse
Gosh, I can't find anything out there about how to use adb sync, been searching for a good half hour or more. The few hits I found didn't make sense to me.
I enter 'adb sync' and get returned to me: "Product directory not specified; use -p or define ANDROID_PRODUCT_OUT"
Get that even after entering 'adb remount' then 'adb sync'. I have also read 'adb help all' and don't understand what all that means -- it's a little over my head.
Any further help/thoughts? Thanks.
I'm looking through my nandroids .img files and attempting to determine where this information is stored. I found some stuff in the data/data directory which seems to be folders for all the apps we have ever installed on the phone. even ones I know I have removed.
I'm going to nandroid and attempt to remove them and see if that will fix our problem. It is annoying to go into Applications and have it take forever to load with 30-40 apps that aren't even installed anymore.
I'll update you in a bit.
riggsandroid said:
I'm looking through my nandroids .img files and attempting to determine where this information is stored. I found some stuff in the data/data directory which seems to be folders for all the apps we have ever installed on the phone. even ones I know I have removed.
I'm going to nandroid and attempt to remove them and see if that will fix our problem. It is annoying to go into Applications and have it take forever to load with 30-40 apps that aren't even installed anymore.
I'll update you in a bit.
Click to expand...
Click to collapse
well i removed it and it shows 0kb now as the size where before it showed the size of the folder. I'm rebooting to see if it works.
Well...apparently I'm in a bootloop. let me try clearing Dalvik
Now I have my nandroid, but does anyone know why removing a file in /data/data would cause a bootloop? It was leftover from a program that I removed via ADB when I first flashed my current ROM.
Thanks.
riggsandroid said:
Now I have my nandroid, but does anyone know why removing a file in /data/data would cause a bootloop? It was leftover from a program that I removed via ADB when I first flashed my current ROM.
Thanks.
Click to expand...
Click to collapse
Don't know the answer to that. Side question: Did what you do actually remove those ghost apps/pieces from the Manage Apps list? Or I guess maybe you never found out because of the bootloop?
Thanks for trying something.
chromiumleaf said:
Don't know the answer to that. Side question: Did what you do actually remove those ghost apps/pieces from the Manage Apps list? Or I guess maybe you never found out because of the bootloop?
Thanks for trying something.
Click to expand...
Click to collapse
The item was still in the list, but it showed 0.0 kb where as before it showed like 75kb or whatever. I was trying to reboot to see if it would rebuild the file that it sued, but....i got stuck in my bootloop and had to nandroid...
back to the drawing board.
riggsandroid said:
I've removed some software via adb pull, rm, etc. but my manage applications list, still shows some of these pieces of software.
How can I clear this data to reflect true, current installations?
Thanks.
Click to expand...
Click to collapse
chromiumleaf said:
Was this answered? I need to know how to do this too. Searches throughout forum didn't find any results about this for me. Thanks.
I've found that if I open "com.smithmicro.DM" or "Download Manager" in Manage Applications and then "Clear Data" in either one of them, it refreshes the Manage Apps list and all the ghost apps are gone. But after every reboot these ghost apps are in the list again, so that isn't a permanent fix.
Click to expand...
Click to collapse
Any updates on this anyone? Anyone? Bueller?
No biggie, just kinda annoying and would like to get to the bottom of it .
I've been attempting a solution to this annoying issue. Read somewhere in here someone refer to an app on the market capable of doing this...
Try reflashing your recovery. It seemes like your nandroid your restoring may still have the data from the apps you pulled out. So when you delete them and wipe everything but then do a nand restore I think your putting the leftover data back on. In my experience when I pull or delete system apps that I don't use I always do them this way.
Using TB I delete all the apps I don't use. Then in TB I refresh the app list to show current app installed. Then I go into my manage apps settings to force close TB then clear data then unistall Tb. Then I reboot and let the phone settle in. Then I power down and reboot into recovery with power and home. I used to with the volume down and power but Ive always had bootloops and errors that way. Since I started using power and home I've had no problems. Anyways-- Then I wipe cache and dev cache and reboot once more. After that I reboot and then do a nand backup. I know its a lot and I'm not sure if this will help you at all but just thought Id put it on here in case it might. Well good luck and I hope you get it all worked out.
Root-Hack-Mod-Always™
Thank you, i will try what you have suggested. I use TB, and am familiar with the whole process, but have never wiped cache and dev cache.
I completely agree with your statement of "letting the phone settle in", so true...
EDIT: After studying some logs, and struggling with this issue for some time, I am happy to say I have finally figured out why this happens, and how to fix it.
The issue is with the calendar, which is why what is written below would work for a short time, before the problem would resurface. If you navigate into the calendar settings, you will see an option within Calendar View Settings to "Include Weather". What is happening, regardless of whether this is checked, is upon the gps turning on, and in set intervals afterward, the calendar tries to check the weather. When it does not find the proper apk, the com.htc.bgp message appears.
How To Fix
The files that need to be replaced are WeatherProvider.apk and WeatherProvider.odex (WeatherProvider.zip), which I have attached below for convenience. Simply replace these files using the method you prefer (adb, terminal, root file browser), remembering to remount /system as rw, then fix_permissions and reboot.
Alternatively, I made a flashable version (com.htc.bgp_fix_flashable-signed.zip), which you need only flash from recovery and reboot.
Click to expand...
Click to collapse
I recently started getting notices that com.htc.bgp stopped and needed a force close. Though it seemed not to affect anything, it was annoying.
It happens when one removes the sense apps (though I have not narrowed down exactly which ones).
To fix this, go to settings, applications, manage applications, then clear data in Calendar, Calander Provider, and Gmail.
Thank you! It was starting to really annoy me.
EDIT: It's back.
^ Shift Faced
Came back on me too. Cleared delvik as well. I may have to try and track down all the weather app crap I removed to stop it if no one can figure out a better way.
According to Elixer that process is started by ConnectToPCService. Hope that helps. I no longer get but I'm back to stock with all HTC junk intact, just Sprint crap removed.
^ Shift Faced
Code:
http://forum.xda-developers.com/showthread.php?t=659325
Check the OP for a real fix to this issue.
How do you "flash" from recovery & reboot
does this work on other htc phones?
i flashed this on a desire hd running leedroid 3.0.2 but i still get the FC
din clear data after flashing
note: i used a no sense script but left myhtc and htclocationservice intact
problem parsing package
i had downloaded the said files but when I tried to install the files,it says problem parsing the package..how to fix this?
thanks,
Jovirex
Hi, i'm having an issue with this rom.
I factory reseted and both caches wiped. then installed base and reboot to this firmware and then back to recovery, flash update.
The issue is after I restore my backup with titanium backup pro (free version).
I get everytime "the process com.android.phone stopped unexpectedly"
What can I do to solve this, the dialer application works, but I don't know what keeps causing this error.
Thanks in advance.
what are you restoring from titanium? apps? or everything
i've just restored apps and system config. I unchecked all system files.
I only restore apps with data if I knew I wasn't having issues. I'll typically install fresh from the market no data just to make sure nothing corrupts the ROM. Sounds like like you are restoring an app that requires something that was blurred out. Try mega 2.0 then 4.3 update.
i personally wouldn't restore sys config. only apps plus data
i had a similar issue a while ago where the com.android.phone process was crashing all the time, it was due to a library that was inadvertently removed when i was modding some system apk files. if you could post a logcat capture it should show why it's crashing.
easiest way i found to do this is to forward the adb logcat output to a text file, from a command line type: adb logcat > logfile.txt
once you get the phone process to crash, you can hit ctrl+c to kill the command from the dos window. if you open up the logfile you just created, you should be able to search for com.android.phone and find a stack trace showing why the process ended.
May wanna try posting in Q&A or if you haven't, add your problem to the Homebase thread in development. May help, good luck.
avoid this rom...thats my solution.
And if not would doing a reset of just the settings probably fix it?
Also tried things like clearing cache partition, I didn't really want to do a whole wipe if possible but clearing cache hasn't worked.
It's doing it daily, sometimes a couple of times per day in different apps.
Are there any event logs that would tell me what happened at the point of the restarts?
If I did a while wipe would my settings and apps be restored after? I can't remember about settings but I know it tries to get back your apps but from previous experience you end up with a load you didn't want any more and a load it missed for some reason.
What does anyone think is best?
Thanks
James
A factory data reset might fix it. I would take it to a local repair shop and see what they say. It might be a hardware malfunction in which if so, claim warranty.
I had a problem once with constant restarts, i finally found the problem. I was removing bloatware with ADB and the apps called ANT i removed. They sere somehow linked to the security folder. Once i reinstalled those apps everything was fine.
Also in Device Care you can check if there's an jssue with any apps. (Which May Or May Not Be Related)
my s10 constantly restarts
Darkat70 said:
I had a problem once with constant restarts, i finally found the problem. I was removing bloatware with ADB and the apps called ANT i removed. They sere somehow linked to the security folder. Once i reinstalled those apps everything was fine.
Click to expand...
Click to collapse
Hi
How do I use ADB to remove apps? how can I find out which app is the culprit?
I dont want to factory reset my phone, as I will lose a lot of data, I cant back it up, since it restarts as I start backing app, no matter which app I use
Thanks!
acetrip said:
Hi
How do I use ADB to remove apps? how can I find out which app is the culprit?
I dont want to factory reset my phone, as I will lose a lot of data, I cant back it up, since it restarts as I start backing app, no matter which app I use
Thanks!
Click to expand...
Click to collapse
To get a list of apps
adb shell pm list packages
To uninstall a package
adb shell pm uninstall --user 0 (package name)
Reinstall
adb shell cmd package install-existing (package name)
What is causing is difficult but if you have removed ant services for example, then afterwards setup secure folder access this will cause a loop reboot.
Try remembering if you have recently removed anything.