Blade won't send texts, just crashes, regardless of SMS app. :(

[Guest Rossome]

I'm on GiffGaff and Modaco Custom Froyo R12. I can't remember when this started (possibly when I installed Handcent), but everytime I sent an SMS, the program would FC. It would usually send though. Recently, I uninstalled HandCent and just used the stock SMS app, but that also now crashes when I try to send a message. If I reply to someone it will usually send, but if I send a message to someone who I've never recieved a message from before, it just closes without sending.

Any ideas?

[Guest Pondlife]

Hmm, odd. Anyway an easy thing to try, backup the current rom in clockwork, then reflash the Modaco Custom Froyo R12 rom file over the top without wiping and see if that helps.

Could try GoSms see if it has the same issue. (just like that one)

[Guest flshg]

Corrupt contacts info perhaps? You could backup your contacts somewhere (including sync to google account), delete all contacts, import/sync contacts back in. Actually before importing them back in, create a single contact, send sms, see if that works ok. If yes then probably a problem with one or more contacts. If not then probably a problem with sms software.

[Guest Mushroom_Lord]

Check your APN settings. There is a thread somewhere about them (do a search :) )

[Guest Rossome]

Hey! I've not had a chance to try any of this out, but I have got the error message just now that I can post:

Sorry!

The application Messaging (process com.android.mms) has stopped unexpectedly. Please try again.

[Force Close]

Any ideas how to fix this one? Thanks!

[Guest Tom Kitchen]

Hey! I've not had a chance to try any of this out, but I have got the error message just now that I can post:

Sorry!

The application Messaging (process com.android.mms) has stopped unexpectedly. Please try again.

[Force Close]

Any ideas how to fix this one? Thanks!

That's a standard force close message, it doesn't tell us anything. My suggestion would be a full wipe and re flash the rom but you might as well try the others first as they will be easier and you will lose less stuff.

[Guest Rossome]

That's a standard force close message, it doesn't tell us anything. My suggestion would be a full wipe and re flash the rom but you might as well try the others first as they will be easier and you will lose less stuff.

Did you see it mentioned a certain process? Sorry, I thought the fact that it was related to the MMS process might have helped.

[Guest Trimalchio]

I had the same "com.android.mms has stopped unexpectedly" issue and I just managed to solve it without wiping. So here is the story in case it may help somebody out there.

In my case the issue seems to have appeared after I upgraded to r12 FroYo from an Eclair ROM.

I captured the log while reproducing the issue and this is what I found:

07-10 18:02:59.312: DEBUG/MmsSmsProvider(368): getThreadId:enter cursor.getCount()=0

07-10 18:02:59.312: ERROR/Database(368): Error inserting recipient_bcc_ids= message_count=0 date=1310317379000 recipient_cc_ids= recipient_ids=7

07-10 18:02:59.312: ERROR/Database(368): android.database.sqlite.SQLiteException: table threads has no column named recipient_bcc_ids: , while compiling: INSERT INTO threads(recipient_bcc_ids, message_count, date, recipient_cc_ids, recipient_ids) VALUES(?, ?, ?, ?, ?);

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteCompiledSql.native_compile(Native Method)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteCompiledSql.compile(SQLiteCompiledSql.java:91)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteCompiledSql.<init>(SQLiteCompiledSql.java:64)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:80)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteStatement.<init>(SQLiteStatement.java:36)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteDatabase.compileStatement(SQLiteDatabase.java:1145


07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteDatabase.insertWithOnConflict(SQLiteDatabase.java:

536)

07-10 18:02:59.312: ERROR/Database(368):     at android.database.sqlite.SQLiteDatabase.insert(SQLiteDatabase.java:1410)

07-10 18:02:59.312: ERROR/Database(368):     at com.android.providers.telephony.MmsSmsProvider.insertThread(MmsSmsProvider.java:

46)

07-10 18:02:59.312: ERROR/Database(368):     at com.android.providers.telephony.MmsSmsProvider.getThreadId(MmsSmsProvider.java:7

1)

07-10 18:02:59.312: ERROR/Database(368):     at com.android.providers.telephony.MmsSmsProvider.query(MmsSmsProvider.java:339)

07-10 18:02:59.312: ERROR/Database(368):     at android.content.ContentProvider$Transport.bulkQuery(ContentProvider.java:150)

07-10 18:02:59.312: ERROR/Database(368):     at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:111)

07-10 18:02:59.312: ERROR/Database(368):     at android.os.Binder.execTransact(Binder.java:288)

07-10 18:02:59.312: ERROR/Database(368):     at dalvik.system.NativeStart.run(Native Method)

07-10 18:02:59.312: DEBUG/MmsSmsProvider(368): getThreadId:after cursor.getCount()=0

07-10 18:02:59.322: VERBOSE/Telephony(1049): getOrCreateThreadId cursor cnt: 0

07-10 18:02:59.322: ERROR/Telephony(1049): getOrCreateThreadId returned no rows!

07-10 18:02:59.322: ERROR/Telephony(1049): getOrCreateThreadId failed with uri content://mms-sms/threadID?recipient=%2Bxxxxxx (number withheld)

07-10 18:02:59.322: WARN/dalvikvm(1049): threadid=11: thread exiting with uncaught exception (group=0x2aacc8a8)[/codebox]

The third line suggests that there is some mismatch between the expected and the actual structure of the database that contains the message threads.

(as far as I can tell, the Messaging software is trying to relate the phone number of the recipient of the message with a preexisting message thread, if any).

I fired up a shell and looked around for a db that might have to do with this.

In /data/data/com.android.providers.telephony/databases I stumbled across a file called mmssms.db.

I deleted it and rebooted the phone and the issue has gone away.

(the system recreated the file, this time with the correct database structure)

I wonder if the issue occurred because after upgrading I restored contacts and other things with a data backup that I did on Eclair. :blink:

It would have been nice to get a more meaningful error message from Android, instead of a Force Close (for instance, "Messaging database appears to be corrupted"). Oh well...

Conclusion: if you are expert enough to open a shell, you can avoid wiping all data and just delete the file. If not, a "wipe data" should fix the problem (or at least this specific instance).

Hope this helps.