[Q] RubiX 2.0.1 com.android.mms force close - Droid X General

I've been on Rubix since 1.9.0 and this is the second time I've seen this issue.
It's possible that the first time the crash happens is unrelated but here goes: I was out in the middle of nowhere with intermittent service (BLM land in California). I got a decent bit of service, stopped driving, hit send on a text (using GO SMS) and while waiting for it to send I lost service. Then got service back and instantly I got a force close of com.android.mms.
The message will now stay in the thread with the status of "Sending...". When I attempt to send another message using GO SMS it just hangs in the "Sending..." status and does nothing. If I try with the stock messaging app it force closes on me the instant I send.
This happened to me before on RubiX 1.9.7 and happened this weekend on 2.0.1. I did a Titanium Backup of all my stuff, wiped, went back to stock RubiX 2.0.1, restored my TiBackup and I get the same force close. I only restored apps and "green" data items.
I'm about to wipe again and omit restoring anything MMS related (as I believe that's how I fixed it before). I've tried repairing permissions (using ROM Manager), wiping cache, clearing data from the Messaging app in Application Manager, deleting buttloads of messages and nearly all MMS messages, nothing has worked.
Anyone else seen this happen, on RubiX or other ROMs?

I've had something similar happen on liberty 1.5. Whenever I tried to send an mms message, it would force close and not send. I fixed it by reflashing the rom

Jmoney47 said:
I've had something similar happen on liberty 1.5. Whenever I tried to send an mms message, it would force close and not send. I fixed it by reflashing the rom
Click to expand...
Click to collapse
Did you restore all your text messages after re-flashing, and did you have the same issue after restoring?
I used the GO SMS backup service to backup and restore my messages. Sending messages was fine after I just re-flashed yesterday; but after I restored my messages (580, I believe) messaging started force closing on me again. Looks like it's SMS quantity related... they just add up so fast!.
Guess this can be considered closed.

Related

Can't send or recieve picture texts

Skyraider sense 2.5.2. I suddenly can't send or recieve picture text messages. Says generic network error. text only texts go with no problems. Anyone have any ideas of a setting that could have been changes or any other ideas?
Thanks
Rod
What have your done so far? I would do so battery pull first. Second I would do a wipe/reinstall of Skyraider.
Did this just happen or is it native to you installing SR.
Sent from my HTC Incredible «•»Rooted/S-off/Skyraider 2.5.2 Vanilla«•» http://www.unrevoked.com/forever
Everything was working fine. I think I installed Shazam and it quit working. Uninstalled that and didn't change anything. Uninstalled and reinstalled handcent. Nothing. Was trying to avoid a wipe as everything else is running great. I wondered if I killed a service that it needs. I think I saw a post once about turning something off, but was unable to find it.
Thanks
Rod

[Q] htc messaging app force closing, all messages deleted

Has anyone had this issue? I went to check my sms and it just force closes... Rebooted and now it works, just all the messages were deleted. Not a big deal, just not sure if it could have received any messages in that time. Phone is rooted, stock rom, not a lot of apps. Pretty much stock all around (i'm lazy).
Thanks for any replies!
Any Solutions

Odd Texting Issue - Notification Keeps Coming Back!

I have an issue right now that I've never encountered. First of all, I'm running AOKP Milestone 5, but I don't think it is related to the ROM. Also, my texting app is GoSMS. Here's what happened:
I received a text from my friend, and I saw it in my notifications dropdown. I clicked on it and it opened GoSMS as it should, but instead of opening to the text that I clicked on, it opened to a blank text and was prompting me to insert a sender name (as if I want to compose a new text). I thought that was odd, but exited the app and went back into it. The text that I had gotten a notification about was not in my thread list. Again, confusing, but I figured it was a glitch of some sort.
Now comes the weird part... the notification came back again! I thought maybe I forgot to clear it. So I simply swipe it away. Within one minute, it comes back AGAIN! Now I try to open it again, and again GoSMS opens up and I am greeted with the "compose new text" screen, NOT the text I clicked on. This has happened for the last 24 hours now. I've cleared cache, I've restarted the phone multiple times, and nothing worked. I have a constant notification with a preview of the same text. It regenerates within a minute if I clear the notification. Anyone have any suggestions or experience with this? It's irritating because now when someone texts me, the notification says "2 messages" instead of telling me who the ONE and only new message is from. I no longer can preview my texts through my notifications.
Should I just reflash the ROM, or do you think I need to clear all userdata and then reflash the ROM? Or should I uninstall GoSMS and reinstall it? I'm so confused - it would seem to be network related or something.
Help is greatly appreciated!!
i would start with the easiest thing first. uninstall gosms and all data for it, then reinstall it. if that doesnt fix it, id try to do a full wipe and reflash rom.
Wipe the messenger app data also (unless you uninstalled the system app).
That actually does sound more like a possible rom problem though.
Uninstalled GoSMS, wiped data from texting app, now waiting for the magical ghost text. I'll update soon. Thanks guys!
I assume the issue was fixed eh?
To me it sounds like GoSMS just glitched out... app's can be troublesome.
imheroldman said:
I assume the issue was fixed eh?
To me it sounds like GoSMS just glitched out... app's can be troublesome.
Click to expand...
Click to collapse
Unfortunately, the issue isn't resolved. It didn't last long before the text came back.
do a nanddroid backup, then install a non-ICS rom and see if a text comes thru... I'm almost thinking it is an MMS message that isn't getting pushed to the phone properly. And there are different MMS problems on the ICS ROMs.
souleman said:
do a nanddroid backup, then install a non-ICS rom and see if a text comes thru... I'm almost thinking it is an MMS message that isn't getting pushed to the phone properly. And there are different MMS problems on the ICS ROMs.
Click to expand...
Click to collapse
I haven't tried CM9 yet, so I think I'll flash that tonight and see how it goes. I didn't wanna wipe everything but now that I want to try CM9 (seems "everything" is working now - for hacked ICS anyway), I'll go ahead and wipe. That better fix it! Haha.

CM11 M9 Text message issue i9505

Hi all,
I hope I'm in the right forum, wasn't sure.
I've done a few searches and cannot find a solution.
I have the Samsung Galaxy S4 (i9505), which recently had stock android on it (rooted).
I installed CM11 M9 onto it a few days ago, but since then, I cannot receive text messages. I can only send.
This has been confirmed by putting my simcard into my old SGS3 (with stock), and it sends and receives text messages fine.
I've done the *#*#4636#*#* trick, clicking refresh and update for the SMSC, which comes up as Telstra +61418706700
When I run the default messaging app, it forced closes. I usually run Textra.
I have disabled Voice+ as I heard this could be the cause of the issue, but did not make any difference.
Any suggestions would be appreciated, as I need to receive all my text messages...
numloxx1978 said:
Hi all,
I hope I'm in the right forum, wasn't sure.
I've done a few searches and cannot find a solution.
I have the Samsung Galaxy S4 (i9505), which recently had stock android on it (rooted).
I installed CM11 M9 onto it a few days ago, but since then, I cannot receive text messages. I can only send.
This has been confirmed by putting my simcard into my old SGS3 (with stock), and it sends and receives text messages fine.
I've done the *#*#4636#*#* trick, clicking refresh and update for the SMSC, which comes up as Telstra +61418706700
When I run the default messaging app, it forced closes. I usually run Textra.
I have disabled Voice+ as I heard this could be the cause of the issue, but did not make any difference.
Any suggestions would be appreciated, as I need to receive all my text messages...
Click to expand...
Click to collapse
You should post your question here:
http://forum.xda-developers.com/showthread.php?t=2559336
Since the app is force closing, I guess it's a bad download or flash. Take a nandroid and do a clean flash...:good:
a103 said:
You should post your question here:
http://forum.xda-developers.com/showthread.php?t=2559336
Since the app is force closing, I guess it's a bad download or flash. Take a nandroid and do a clean flash...:good:
Click to expand...
Click to collapse
Thanks,
I'll check it out
Have reverted back to stock so I can check my messages, do some backups and give the whole thing another shot with a clean install.
I re-flashed and instead of restoring every app using Titanium backup, reinstalled only the apps with important info, such as Textra etc. Messaging works all good now. Thank you for your help

SMS keeps crashing

Hey guys, so recently I went from one phone carrier to another and my text messages were not working (inbound and outbound). They told me to delete all my messages in order for it to work. So I did a backup with SMS Backup+ and gave it a try and the outbound worked (I had not yet tried getting an inbound yet) So I asked the CSR if I can restore my messages and he said yes everything should work now. Well, that's where the problem started. Once I restored, SMS keep crashing, it says Loading conversations forever and then I had to reboot my phone. Once I was able to get in, I see the messages but when I click on one, its just blank as it trying to load but nothing is happening. I rebooted and tried to delete them all again and its just stuck, nothing happens. I looked around for solutions and someone mentioned to get another text messaging app to at least get in your messages so you can delete it and then use the stock app for messaging again. I got chomp SMS and yes I was able to get in and said delete all, well its says deleting for the past 2 hours now and not sure if it is actually deleting or just stuck. Any help would be appreciated to get this working again
phone_noobie said:
Hey guys, so recently I went from one phone carrier to another and my text messages were not working (inbound and outbound). They told me to delete all my messages in order for it to work. So I did a backup with SMS Backup+ and gave it a try and the outbound worked (I had not yet tried getting an inbound yet) So I asked the CSR if I can restore my messages and he said yes everything should work now. Well, that's where the problem started. Once I restored, SMS keep crashing, it says Loading conversations forever and then I had to reboot my phone. Once I was able to get in, I see the messages but when I click on one, its just blank as it trying to load but nothing is happening. I rebooted and tried to delete them all again and its just stuck, nothing happens. I looked around for solutions and someone mentioned to get another text messaging app to at least get in your messages so you can delete it and then use the stock app for messaging again. I got chomp SMS and yes I was able to get in and said delete all, well its says deleting for the past 2 hours now and not sure if it is actually deleting or just stuck. Any help would be appreciated to get this working again
Click to expand...
Click to collapse
Try deleting the data of the SMS app from the android settings.

Categories

Resources