Text Messaging Force Closes crashes - Fascinate Q&A, Help & Troubleshooting

I've done some searching on Google and didn't find anything helpful yet. I am running a mostly stock (rooted) ED04 w/ OTB 1.6 Kernel.
When I boot up my phone, I get a FC on com.android.mms
When I go into my Messaging and open an existing message it force closes.
This phone is pretty freshly setup. ie: I had a couple text messages on my phone from yesterday. I deleted those with no effect. When I sent a text message to myself (from google voice) and opened it up, I still get the FC on com.android.mms
I booted up into CWR and ran the Fix Permissions. That didn't do any good. I went back to CWR and cleared cache and Dalvik cache. That didn't do any good. Still getting FC. Any advice? I have a logcat of the crash when I try to open the message.
Here is the logcat: http://pastebin.com/YHwYs7ur
Any help in figuring out why my text messaging is crashing would be very helpful. I've been using a Fascinate since September. The only thing I did before this started happening was Titanium Backup was set to backup the green system applications and the user applications last night.
EDIT:
Sending a text message from the phone is causing a force close too. The message does send (I sent it to myself and it showed up a moment or two later after the fore close).
I think the mms database is screwed up but I'm not sure which database it is.
EDIT #2:
Well, I ran Titanium Backup again (just user apps+data, with the reboot option enabled). The system rebooted at the end of the backup and stuck at the SAMSUNG logo and will not boot up and not even into CWM with the three finger salute. Guess I'm doing the odin dance. Damn it. I had just gotten everything setup the way I wanted it. I will be leary of the Titanium Backup rebooting and see if that had anything to do with it. (Titanium Backup rebooted last night, the phone was off by the time I got to it this morning and it turned on fine except for the text messaging FC.)
I've odin'd the CWM (05-08-2011 version) and it still just sticks at the SAMSUNG screen....so ODIN back to ED03. Blech.

Related

[Q] process com.android.systemui has stopped

Hu guys,
i was googling for some hours but couldnt find a soltuion to this. Everytime i install ANY app on my new sgs2 and reboot I get the following error message:
The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again.
I get the message twice and then the bar is gone. When i dont press force close I see the bar just working perfectly in the background.
Only solution is factory reset, but as soon i install apps (no matter which) i start getting the same problems.
Thinking of returning the phone
Marcie
Can you post what's in the 'About Phone's screen, what network you're using and where you bought your phone.
Sent from my GT-I9100 using Tapatalk
Try a reflash as i only got that problem when i pushed systemui.apk and didnt reboot straight after. Sounds like a corruption somewherw
Sent from my GT-I9100 using XDA Premium App
the problem was when ever i made the inital configuration i ticked the box to sync my google config. my google config was from my old sgs1 which must have corrupted my phone. i reset the phone and unticked the google config option and i dont have the problem anymore.
Ahhh!!! I got the same problem!!! Is there any way to fix this? Anyone?
marcie82, i'm having the same problem and your post was the only post I found that addresses the issue. When you wrote that you've reset your phone, did you mean you reflashed it?
I just got the same phone from amazon.. and it worked fine when i first opened it but then the task bar disappeared..
i reset it back to original factory settings.. it's downloading my old apps now.. i'll keep on debugging this thing until something comes up
A buddy of mine had a similar issue, for him it was com.android.phone that kept randomly crashing, sometimes mid-call and thereby terminating the call.
We tried factory reset and other things as well, nothing helped.
So we ended up re-flashing the FW (he was on KE2 and we flashed a stock KE7), that is now ~2 weeks ago and he never had any crashes anymore since then.
So, long story short, try reflashing (a maybe newer) FW with odin, factory once more (if the ROM doesn't do it while flashing) and see if it gets any better.
Also check the CSC setting, we set it to generic XEU after the flash - use w/e suits your region/FW.
installing applications
i noticed that as soon as i go to google market and click on the 'my apps' button.. it starts downloading all the apps i previously purchased automatically.. is there a way to prevent that from happening?
Settings -> Privacy
"Back uo my data" and "Automatic restore"
untick at least the auto-restore, or the auto-backup too, maybe that helps.
I got both disabled by default (first thing I set after a wipe) and it never tried to restore my apps by itself (yay for AppBackupAndRestore ).
could it be a specific application?
debugging progress: i noticed that it's not installing *any* app that causes this task bar thing disappearing (at least not in my case):
i restored my phone to factory default.. then i disabled my automatic restore and defaults. then i installed only one app from my very long list of apps. (for some reason i had to do it from my 3g connection and not wifi.. but that's a different problem)..
anyways i installed it and it worked just fine! i restarted my phone just to make sure and the task bar is still there!
i'm gonna go through my apps ans install them one by one.. i know it's a painstaking process but hey i gotta give back to the android community
A
A trick I used in a similar situation was the following :
Use Titanium Backup. U make a backup of the application that has the problem. Then u wipe the data of this application and then u restore the data.
For me that trick miraculoussly solved that problem ...
http://forum.xda-developers.com/showthread.php?t=1162680
Had the same problem with not working phone/contacts, freezing like "process com.android.phone - Force Close" etc.
I realized the error happens only after upgrading for example to KG, than after a short period making a backup of the whole system, downgrading to KF, then restoring with Titanium Backup.
It restores the whole system, including settings, and accounts and so on. This might be the problem. It seems nobody realized that the MODEM and PHONE is upgraded too, so there might be some components not compatible with earlier versions.
Solution: restore only user apps & data, not the system settings. Use a separate app for SMS, call logs, contacts or calendar. Do a cache wipe and then a fact reset from MENU+UP+POWER (restore menu), then reinstall your choice of firmware, restore user apps&data with Titanium or anything preferred, then enter/restore everything else manually. No problem when upgrading.
Tested, had 3 sleepless nights, but works for me.
Noob in need of androidized kindle help!
Hey ya'll,
I just rooted and downloaded ics4 onto my kindle. It was working great all day and I used the gba emulator for android and everything.
Now, for some reason I keep getting the error "unfortunately, system UI has stopped working".The tool bar on the bottom of the screen with the home and back buttons aren't even there anymore. I have rebooted and gone into TWRP and done a system reboot and everything yet that keeps happening. Why do you think that is ?
caused by Titanium
hlaja said:
Had the same problem with not working phone/contacts, freezing like "process com.android.phone - Force Close" etc.
I realized the error happens only after upgrading for example to KG, than after a short period making a backup of the whole system, downgrading to KF, then restoring with Titanium Backup.
It restores the whole system, including settings, and accounts and so on. This might be the problem. It seems nobody realized that the MODEM and PHONE is upgraded too, so there might be some components not compatible with earlier versions.
Solution: restore only user apps & data, not the system settings. Use a separate app for SMS, call logs, contacts or calendar. Do a cache wipe and then a fact reset from MENU+UP+POWER (restore menu), then reinstall your choice of firmware, restore user apps&data with Titanium or anything preferred, then enter/restore everything else manually. No problem when upgrading.
Tested, had 3 sleepless nights, but works for me.
Click to expand...
Click to collapse
I am sure the problem caused by restore system data by Titanium. I have tried four times today. Factory reset and flash and restore. Only when I restore system data caused this problem.
Why resurrect a two year old thread?
For information, restoring apps WILL NOT cause instability......restoring data ESPECIALLY data from system apps WILL.
RULE OF THUMB......
If you are upgrading your android OS (eg...ICS to JB).....
DO NOT restore system app data....ever
For user apps....if the app runs as soon as you open it, you *should* be ok to re-install the data.
If the app requires the downloading of 'additional files' on first run, DO NOT re-install as this data is likely to be OS version specific......
My wife says I'm a phone geek....She's probably right
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to do a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
com.android.systemui stops working when battwry gets less then 16 %
Hi guys ,
Can anyone upload the system ui file for android KitKat?
I tried all things to fix "Unfortunately com.android.system ui. Has stopped working when battery gets lower then 16% so I think I should replace the system ui file from system app folder
Hey everyone, I just had this same problem pop up onto my phone while I was checking my messages. Ive never rooted my Motorola Droid Razr HD and the power button is jammed at the moment as well. Is there a way around this problem or is this phone done for?
Maybe you should try increasing the heapsize in the build.prop file, the no. of notifications in the status bar causes this crash. if you want to know more about the heapsize etc. google for this crash in cyanogenmod fourms.

[Q] GingerDX v13 text messages

Coming from stock rom I have flashed GingerDX v13 Rom on my sisters mini pro, ive followed the procedures wipe cache/ system / data. When i restore the text messages and open the messaging app it hangs, becomes unresponsive, and eventually wants to force close. If i reboot the phone and reopen its will open the first time but the next time will not open, same cycle repeat rinse repeat. Go sms has same issue.
- the restore app i used is sms backup and restore (ive used this on my N1 without any issues).
- total amount of message +- 8100.
- flashed the room from scratch x2.
Anybody else seen this behavior before? the text backup was from stock rom, never had issues there, 2.2 i suppose unrooted.
Would like to exhaust all options and view other users opinions before moving to minicm7.
any input is greatly appreciated.

[Q] Can't Detect Sim Card - Software Issue

Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
pzling said:
Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
Click to expand...
Click to collapse
If there was a point in time when everything was working and then one change was made, the stock dialer was removed, then things stopped working, the solution would be to revert back to the working point in time.
Curious, what guide suggested the removal of the stock dialer?
As a side note, before removing files it is always best to either make a complete backup, nandroid, or to at least backup the specific file being removed so it can be quickly and easily replaced.
The main issue here seems to be the removal of the stock dialer. On the technical side of things, the dialer is a very integrated component of Android.
In AOSP, which all ROMs to some degree are based off, the dialer apk file contains not only the dialer but also browsing of contacts and links in on the back end with a few files.
Once you restore the Dialer, I think called phone.apk or something similar, the issues should go away such as FC. If there are issues accessing the SIM card after restoring the previously removed file, off the top of my head, my best guess would be to clear out the settings stored on the data partition. A setting could have been created during the dialer removed state which might prevent the system from restoring proper SIM access.
Hope that adds a bit more detail around the standard process of removing files and making adjustments!
Cheers thanks, much appreciated.
Largely the guide of my ignorance that decided to remove the stock dialer. It's only in the last half hour or so that I've just come by a guide that specifically says to *not* remove the stock dialer. In the first instance I thought it wouldn't be such a big deal as Titanium Backup could always restore it ... in which it turned out it couldn't.
So after all's said and done, is there a way (apart from Ti Backup) to restore just the stock dialer phone.apk (say by download or other)?
Another approach I'm considering is to find a way to flash a custom / stock ROM to fix this. However as my phone is unbranded and on HBOOT 1.49.0018, I'm finding this very difficult with the standard methods posted. On the other hand, ideas are starting to run out and desperation running high!
pzling said:
Hi
I recently installed Touchpal Dialer to replace the Android Stock Dialer (Phone). I then used Titanium Backup to uninstall the stock dialer. (I only select Phone and pressed 'Uninstall'). However in the process of uninstall, something crashed (some process stopped working) and I was stuck on Force Close (which repeatedly pops up).
So to return to Android I rebooted. However the phone can no longer detect the the SIM card (and hence the network). I tried to access Settings>Call, but I get the error "The application Settings (process com.android.settings) has stopped unexpectedly".
My first thought was to restore Phone using Titanium Backup, but this seemed to be stuck (or at least it was taking excessively long >20min).
Then I reinstalled the rom but that doesn't affect the files required to detect the sim card.
How do I fix this and get my phone to be able to dial again?
Any and all help is much appreciated.
Click to expand...
Click to collapse
I have had this happen to me a few times, this mostly happens when you apply a mod/tweak to a rom that is not compatible. Do a wipe and re-flash the rom that you want and it should fix the problem.
Thanks so much for this, that's fixed it.
Re wiping, since you can wipe from the Recovery and installation of the rom wipes before flashing anyway, is it necessary to use a wipe img? If so, what is recommended? (As I'm on HBOOT 1.49, I seem to only be able to run CWM 4.0.1.4 Shooteru Recovery).
ROM not booting
Looks like I've dug myself into another hole again.
The 'Sim Card detection' problem was fixed with a wipe from CWM 4.0.1.4 and flashed with ShaWn3D v1.4 rom. Everything works and I was happy.
But I was keen to try out the LeeDroid rom but the WiFi error keeps recurring despite my attempts with the solutions provided at
http://forum.xda-developers.com/showthread.php?t=1248838.
I've tried:
- re-flashing LeeDroid with so many versions of bcm4329.ko I've lost count
- reflashing the kernel with the LeeDroid kernel addet
- re-flashing another rom altogether (King Cobra v1.9) to see if it makes a difference; it doesn't - WiFi persists.
So now I've decided to go back to the ShaWn3D rom but now although the flash is successful, the boot is stuck at the white HTC splash screen.
What have I done wrong?

[Q] com.android.phone problem

Ok, i flashed to ics real lite v1.1 and am using rage kernel. Its a clean install and didnt use any backups. I only restored my contacts via memory card backup and messeges via sms backup app. This is on the mini pro.
My problem is sometimes when i get a call, i get a black screen. I press the power button to turn my screen on then i unlock my screen then answer the call. When i do that i get an error bout "com.android.phone" not responding. Whenni click ok, my prone drops the call and i cant even see the caller via call log, its so frustrating. Ive read around and ppl suggested i delete a few messages from "reject call with message", but i cant find a delete command in there. Secondly, there was this suggestion about clearing the contacts cache and stuff via app manager. This only deleted my whole contact list and was never able to get it back till i did a reinstall of the rom. I dont use facebook or some other app, my setup is bone dry basic, i only use sms backup app.
I also tried using another rom, the full version of real ics v4, still nothing. Any help would be appreciated as i really like this rom.

[Q] Whatsapp Stuck on Initializing after Crash and Reinstall

So I had some sort of crash on my HTC Sensation where the phone rebooted, and all my whatsapp messages were gone. Whatsapp automatically backs up your messages every 24 hours, so I reinstalled to enable the backup.
1. After installation, when inputting information (after restoring your messages) and getting into profile info, I am stuck on an "Initializing: Please wait a moment..." box
2. This goes on forever
3. I have force closed, cleared cash, cleared data and tried again with no luck
4. I have uninstalled and reinstalled (and reboot the phone) with no luck
5. I have uninstalled and installed the latest version from the whatsapp website (which has a different file size than the play store one) with no luck
6. I have redone this WITHOUT recovering my messages with no luck (even deleting the back up messages folder)
7. I can actually receive notifications from whatsapp, showing messages from groups / people, though clicking it takes me back to "Initializing"
8. Sometimes I get an "android.process.acore is not responding. Would you like to tell HTC?". This may be a separate issue as it still continues to "Initialize" no matter what I press
I can see 28 messages from notifications, some which are very important and urgent. Hopefully someone can help
Edit: I am using an unrooted HTC Sensation with ICS
Thanks
Update: Tried reinstalling using safe mode. Same problem happens, though instead of being stuck on initialization, Whatsapp force closes and stops working after about 2 minutes
garronkc said:
Update: Tried reinstalling using safe mode. Same problem happens, though instead of being stuck on initialization, Whatsapp force closes and stops working after about 2 minutes
Click to expand...
Click to collapse
having the same problem on a samsung galaxy s3.
Never seen this, any fix?
I tried everything.
PacinoAllstars said:
having the same problem on a samsung galaxy s3.
Never seen this, any fix?
I tried everything.
Click to expand...
Click to collapse
Same here! having the same problem on my S3 too. I don't know what to do
garronkc said:
So I had some sort of crash on my HTC Sensation where the phone rebooted, and all my whatsapp messages were gone. Whatsapp automatically backs up your messages every 24 hours, so I reinstalled to enable the backup.
1. After installation, when inputting information (after restoring your messages) and getting into profile info, I am stuck on an "Initializing: Please wait a moment..." box
2. This goes on forever
3. I have force closed, cleared cash, cleared data and tried again with no luck
4. I have uninstalled and reinstalled (and reboot the phone) with no luck
5. I have uninstalled and installed the latest version from the whatsapp website (which has a different file size than the play store one) with no luck
6. I have redone this WITHOUT recovering my messages with no luck (even deleting the back up messages folder)
7. I can actually receive notifications from whatsapp, showing messages from groups / people, though clicking it takes me back to "Initializing"
8. Sometimes I get an "android.process.acore is not responding. Would you like to tell HTC?". This may be a separate issue as it still continues to "Initialize" no matter what I press
I can see 28 messages from notifications, some which are very important and urgent. Hopefully someone can help
Edit: I am using an unrooted HTC Sensation with ICS
Thanks
Click to expand...
Click to collapse
android:
1- search for whatsapp 2.8
2- open it and enter ur phone number u'll get stuck on initializing
3- go to task manager and press and all
4- re-open whatsapp and press download
5- open the file u istalled it and replace whatsapp
ps: dnt delete the whatsapp 2.8 before you install the new whatsapp just let it replace the old one
you'll have chats but no contacts
zoox11 said:
android:
1- search for whatsapp 2.8
2- open it and enter ur phone number u'll get stuck on initializing
3- go to task manager and press and all
4- re-open whatsapp and press download
5- open the file u istalled it and replace whatsapp
ps: dnt delete the whatsapp 2.8 before you install the new whatsapp just let it replace the old one
you'll have chats but no contacts
Click to expand...
Click to collapse
I have the same problem. Stuck on "Initializing".
I tried to follow your steps, but they are not very clear.
Can you kindly elaborate the steps?
Thanks
rhumbus said:
I have the same problem. Stuck on "Initializing".
I tried to follow your steps, but they are not very clear.
Can you kindly elaborate the steps?
Thanks
Click to expand...
Click to collapse
Did the steps, but still stuck at initializing.
If your phone is rooted, try clearing dalvik cache. Other than that, I fear the only thing that you could possibly do is wait for an update.
I'm currently having (had) the same issue. I reinstalled a couple of times and suddenly it started working. I wonder if it was a problem on WhatsApp's end, because I didn't do a thing - suddenly everything was fine.
sindrik said:
Did the steps, but still stuck at initializing.
Click to expand...
Click to collapse
Did this:
- Uninstalled already downloaded version from Market on the cell phone.
- Downloaded Whatsapp from my pc, from their official website
- Transferred the APK to the cell phone, installed it.
- Left it a bit (a minute) at "initializing". Worked.
got it solved...
i was having problem with cm7.1.5 so installed cm7.2...
on 1st start of whatsaap it gave me msg about having custom rom can create problem as it does not support whats app..
then also i proceeded n i was facing same problem.it was stuck on initializing.
then after lots of different tries it worked on one trick...
what i did was :
1.1st backup all my contacts(mobile).
2.then cleared data in contact storage in manage apps.
3.installed whatsapp 2.8 which was backup earlier
4.clicked "Agree and continue" then entered my mobile no. but,it told me that whatsapp new version must be installed.
5.i then upgraded whats app from play store.
6.After installation was complete i opened it and it was started from same step of application of entering mobile no.
7. i entered no. , restored data from old backup of whatssapp, all messages were restored.
now my Display Picture , Name got appeared.
8.clicked next, shortcut of whatsapp was created. in 1 sec it got initialized, n continue button got appeared.
9. now i was having messages but no contacts(whatsapp).
10. now i restored contacts(mobile) from softwere i was using. and now after opening whatsapp m having contacts.
It worked on my phone... try it... best of luck...
Found a workable solution. Whatsapp seems to get stuck at the initilization screen bcause of contacts..
Delete all contacts, install whatsapp...
then restore contacts.. it shuold work
kelvin_tan said:
Found a workable solution. Whatsapp seems to get stuck at the initilization screen bcause of contacts..
Delete all contacts, install whatsapp...
then restore contacts.. it should work
Click to expand...
Click to collapse
Thank you so much!
I've been having this problem and this fixed it
mariachi202 said:
If your phone is rooted, try clearing dalvik cache. Other than that, I fear the only thing that you could possibly do is wait for an update.
Click to expand...
Click to collapse
But how to clear the "dalvik cache", i have link2sd nd superuser installed in my htc explorer. Kindly guide me through.
Thanks
wipe data and cache
kelvinvalencio said:
wipe data and cache
Click to expand...
Click to collapse
but if i wipe data would'nt all messages/conversations get deleted
Been getting this error since this morning. Reinstalled whatsapp. Still didn't work. Then I reflashed my ROM completely. Still having this error. Any ideas? Getting android.process.acore has stopped as soon as I open Whatsapp.
Running the Revolutionary S5 mod on my S3.
same problem
I'm having the same problem. As soon as I open whatsapp it gets stuck for a bit in the initializing screen, then crashes and shows "android.acore.process has stopped". This happens in the XRom, Smartdroid rom and S5 revolutionary rom for s3. Any fix for this? :/
ronaldl911 said:
Been getting this error since this morning. Reinstalled whatsapp. Still didn't work. Then I reflashed my ROM completely. Still having this error. Any ideas? Getting android.process.acore has stopped as soon as I open Whatsapp.
Running the Revolutionary S5 mod on my S3.
Click to expand...
Click to collapse
I had the same problem with Revolutionary S5 V3
what did the trick for me was installing an older version which i downloaded somewhere(but not too old cause whatsapp wont accept it) and use it to activate and initialize. Then i updated through google play and everthing seems fine.
As for the android.process.acore follow these steps:
First of all switch off the internet
- tap on setting and navigate to applications
- tap on all options and search for "google services framework" from the list
- tap on it and hit force stop to forcibly stop the application
- now hit force stop for the following apps
-> contacts
-> gmail
-> facebook
-> whatsapp
- reboot your system.
Cheers
WhatsApp slow initializing due to contacts problem. Confirm!
Check out how here...
http://jjpda.blogspot.com/2014/05/whatsapp-stuck-on-initializing.html

Categories

Resources