Alot of force closes - HD2 Android Q&A, Help & Troubleshooting and Genera

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,

Related

com.android.mms force close now

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

Market thinks I still have these apps installed. how to Re DL ?

On Dwangs latest. Darn thing wont ever work with nandroid. Had to wipe my EXT3 to recover an old image. All my apps are gone. I had most backed up via Astro.
BUT
Theres a handful that I didnt have but now the market says "Installed".
Ive tried clearing all caches and data that pertain to market. Reboots... no luck.
Is there a way to fix ?
And for future reference ..best way to backup EXT3 without ADB ?
Try downloading the apps on an online market, then installing them off the SDCard.
this should work.
remove the folder /data/data/com.android.vending
then restart. it should refresh you're market.
if all else fails. re-flash.
if removing the vending folder doesnt work, just uninstall the app, and then try re-installing it? if it says it is installed, this should work.
ALSO, if you're apps2sd wasnt automatic and you had not rebooted since your last install of a few apps, they might still be in your internal phone memory. a wipe of NAND and EXT might help resolve any problems if all else fails
Ssantos6981 said:
this should work.
remove the folder /data/data/com.android.vending
then restart. it should refresh you're market.
Click to expand...
Click to collapse
This should work nicely
Thanks for the help guys. Got frustrated just wiped and started from scratch.
Appreciate it.

Force closing issue

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.

S10+ keeps randomly restarting, is there any way to find out what's causing it?

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.

Question com.google.android.documentsui keeps crashing

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..

Categories

Resources