I am having an issue with my better 8 keyboard force closing. I backed all my all my apps up with my back up root and reinstalled cm7 to start over fresh. When I unzipped my apps into it all of them worked normally except my key board. I thought maybe there was a problem copying the apk file but have tried multiple known good copies of the file and still getting force closes. I have tried running fix permissions and am at a loss on ideas. Any help would be appreciated.
Related
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
Does anyone else keep getting force close errors? The last 3 builds ive tried keep force closing to the point where I have to delete the data.img and start over. I have tried changing the rom and have tried formatting my sd card. Is anyone else having this problem? Any body have a possible solution?
Which applications do a forced close?
mms, phone, a bunch of other ones. it restarts itself and resets my wallpaper if that helps at all
go into any terminal application (ex: Terminal Emulator)
type in and press enter afterwards
su
fix_permissions
let it do its thing then restart. i make it a habit after a fresh install or after installing many applications to fix permissions.
hope this helps.
-Static
I had the same problem when I switched android builds and tried to restore all my apps. If you clear the problem application's data, uninstall and reinstall, then it should work fine. Statics way might work, Ive never tried it. Jus sayin how I fixed a few of my apps,
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
In the dev forum, there is a helpful post on how to root and then install the google apps:
http://forum.xda-developers.com/showthread.php?t=1349902
Like others on the thread, I had a problem with the market and other apps force closing all the time; what's missing from the instructions there is that when you change the permission of the apk files copied into the /system/apps directory, you must also make sure that they are owned by root. In my case, they were owned by the OS user on the machine I connected the kindle to when I transferred the files.
So, in root explorer, after you change the permissions to rw-r--r--, long press again on the file, choose Change owner, and change both the owner and the group to root.
I'd be stoked if this actually worked for me. It's really weird, everything was working fine this morning then it just randomly started force closing google services framework on me left and right. Now I can't even get talk to work at all.
Damn, I feel stupid. I made the mistake of removing the stock system calendar and contacts files. I found the system dump file and put everything back but either I forgot to install them or the system uninstalled them on me. Anyways, installing solved the problem.
Now I'm having another really weird problem. I do the initial install of the market then I have the market up and running once I do a reboot. After any subsequent reboot, market automatically uninstalls and I have to use TiBackup to reinstall it. Fortunately, once I restore, I don't have to reboot again but that is a major pain.
Hi,
My stock "files" (com.google.android.documentsui) will not open anymore.
I've tried clearing cache and data but it will still instantly crash.
I've also tried uninstalling it with terminal.
That helps with choosing what file manager to choose in some apps.
But a few apps are dependent on com.google.android.documentsui and will not open a pop-up screen to choose a different file manager.
I've searched through the web without an answer. I don't know what to do except factory resetting.
I'm rooted, running the 1.1.3 update, is anyone else experiencing this?
dzjin said:
Hi,
My stock "files" (com.google.android.documentsui) will not open anymore.
I've tried clearing cache and data but it will still instantly crash.
I've also tried uninstalling it with terminal.
That helps with choosing what file manager to choose in some apps.
But a few apps are dependent on com.google.android.documentsui and will not open a pop-up screen to choose a different file manager.
I've searched through the web without an answer. I don't know what to do except factory resetting.
I'm rooted, running the 1.1.3 update, is anyone else experiencing this?
Click to expand...
Click to collapse
Try a factory reset and if it keeps crashing, I recommend upgrading to 1.1.4..