[Q] SMS problems - Galaxy S I9000 Q&A, Help & Troubleshooting

I'm not sure if this is the relevant forum to post in but I'm having an unusual problem with sms. I have a Bell galaxy s but I've now moved to the U.K. and signed up with O2. Whenever I receive a text from O2 (i.e. the message telling me my balance after I top up), I get the following error message: 'The application Messaging (process com.android.mms) has stopped unexpectedly. Please try again.'
I have tried clearing the memory from the app (although, the cache is always 0.00 for some reason) as well as a factory reset. I've also wiped and loaded Doc's new froyo rom for the bell galaxy s. None of this has rectified the problem - I still always get the force close message after receiving a sms directly from the O2 network - the worst part is that I can't even see the message.
On the rare occasion, a few of my friends have sent me a text that I don't receive (but in this case, I don't receive the force close message - nothing happens at all).
I can send messages with no problem.
Any ideas on how I can fix this?
Thanks

I have very hard solution - download any other sms client that isnt crap from samsung.

dupel said:
I have very hard solution - download any other sms client that isnt crap from samsung.
Click to expand...
Click to collapse
Thank you for your 'hard' solution. Is there anyone who has other suggestions that would help me to ensure my sms service works normally?

namams said:
Thank you for your 'hard' solution. Is there anyone who has other suggestions that would help me to ensure my sms services work normally?
Click to expand...
Click to collapse
And what is wrong with this solution? Have you even tried it? Other are faster, better, more feature rich and actually work.

Related

[Q] Messages Glitch

I have recently flashed DDJG4 and its by far the smoothest eclair for me but I have noticed that some of my contacts have a bug in messaging. Only their number shows up opposed to their name. This is annoying as I dont know who the message is from unless i open the contact details.
Contact details is fine, no problem. Just the messaging app.
Anyone else notice this? any fix ideas?
thanks
don't have enough messages from different people to confirm (only 4 so far). however, on a related note, do you see a long delay between unlocking the screen using the puzzle piece and the corresponding message opening in the messaging app?
Not checked. I use pattern lock. Ill have a go and see.
Sent from my GT-I9000 using XDA App
vega5aw said:
I have recently flashed DDJG4 and its by far the smoothest eclair for me but I have noticed that some of my contacts have a bug in messaging. Only their number shows up opposed to their name. This is annoying as I dont know who the message is from unless i open the contact details.
Contact details is fine, no problem. Just the messaging app.
Anyone else notice this? any fix ideas?
thanks
Click to expand...
Click to collapse
Sorry to say, but its just you.
I have over 41 conversations and all the names display correctly.
I noticed lagging on the lock screen to messaging in ddjf3
In ddjg4 there is no more lag anywhere.
I put the ext2 1gb lagfix just for the heck of it and the phone is now faster than me.
Reflash and see whats wrong.
Use the Backup apps from ritesh sahu.
I use them to backup my data before flashing.
I have the same problem too when I imported/restored about 150 old messages. Did you manage somehow to get rid of the problem? On my phone it's only some contacts where only the number is shown and not connected to a contact. This problem started for me when changing to the jm firmware line. For the jf and jg firmwares this problem does not appear.
Strangely, handcent sms has no problem with the sms/contacts. Therefore, this has to be a bug in the samsung sms application, not in our data.

[Q] Not getting SMS Messages

I'm rooted and running bugless beast v0.4. My phone said my text message inbox was full and that my phone was low on space. I dumped a few apps off on to the SD card and deleted all the text messages. I also tried unsuccessfully to add the new R2-D2 boot animation around the same time. I don't know if i somehow deleted something important when i was in AndroZip deleting the R2-D2 stuff or what is going on but I can no longer receive text messages. I can send them out and everything else works fine. I tried a few different ROMs in ROM manager with no luck. I've since switched back to Bugless Beast since i think it is unrelated to the problem.
I wiped data and cache and it starts working again but after all my apps finished downloading and installing, it quit receiving text messages again.
Auto-retrieve messages is check marked.
I've found out that I can receive picture messages but not text messages. I have an unlimited data, text, and picture message plan so it isn't that I have reached the limit of text messages this month or anything.
I have used Handcent exclusively pretty much since I got the phone. I tried uninstalling it. That didn't help. Reinstalled it and that didn't do anything either.
Does anyone have any ideas what is going on here? Thanks for any advice you can give me. - Kevin
have you tried sending messages to urself? is ur message center properly configured?
Yes, I've tried to send messages to myself and it doesn't work. And I'm assuming everything is configured correctly. As far as I know I haven't changed anything.
Deadohiosky39 said:
Yes, I've tried to send messages to myself and it doesn't work. And I'm assuming everything is configured correctly. As far as I know I haven't changed anything.
Click to expand...
Click to collapse
contact ur telco provider and ask them about this. coz it seems to not originate from your side.
Well, I had an update to the Norton Mobile Security App this morning. After updating, everything seems fine. I'm able to send texts to myself and I've received them from two different people. I don't know if Norton caused the problem in the first place or fixed the problem I already had. It never popped up saying it found any problems so I'm guessing it was just a bug in Norton. I checked the comments in the market and no one mentioned having that problem though so I don't know. I'm just glad it's working now. Thanks for your help guys.
The problem lays probabely in your internal memory being to full. I've heard people with similar problems on the Milestone. After deinstalling some apps it all worked again. Your problems also begin when you have reinstalled all your apps.
Maybe you can move more apps to your SD since, I presume, you have a Droid.
I've got plenty of space. I've moved apps, deleted old texts, etc. none of that fixed it. Its been fine after I got the norton app update though.
The R2D2 boot animation likely filled your /system partition, this happened to me so I moved all the system sounds to sdcard keeping the folder structure intact and all is well. Just remember your phone won't ring if your sdcard is not in the droid afterwards.
Sent from my Droid using XDA App

Text to 1121611611

I have had a strange thing happen occassionally when I reboot my phone. it has happened after restoring to stock using ODIN - it has also happened when flashing a custom ROM,
When the phone boots up I see an error message saying something about a text message could not be sent - to use a valid short code or ten digit number - when I look at waht number it was being sent to - the number is 1121611611
It is very strange - I wasn't sending a text message when this happens - it just happens when the phone reboots - and not all the time - just occasionally -
I am using an ATT SIM Card on a TMOBILE PHONE - and when I did a GOOGLE search for that number - I saw mentions of APPLE phones having issues and something about people on Verizon phones -
If I try to send text messages - no problem - everything works fine.
Does anyone know anything about this and what if anything can I do to make it stop happening?
Very strange indeed....
How to stop this
No responses to my question yestreday - did a little more reseach and while I still don't know WHY it happens - I think the fix for this (in case anyone in the future has this problem and comes accross this thread) is to just send a valid text number to any one in your phone book - say hi to somone you know - just send a real text message that is to a working number - apparently once you send a real text message to someone - this stops and won't happen anymore.
To be honest the whole thing is weird to me - I wish I knew why it happens - but for what it;'s worth - since I sent a text message yesterday after seeing this error message - the error message has stopped.
Im having the exact same issue.. im using tmobile n4 on att network. I tried sending a text to sum1 in my contacts but on reboot i got the same message again from 121611611. Anyone got a solution???
That weird: 112 that is universal emergency number in all gsm phones and 611 is provider service call center
Sent from my SM-N910T using XDA Free mobile app
It's the T-mobile visual voicemail app. I'm on AT&T with the T-mobile Note4 and had this problem as well. With root, you'll need to delete the app from System/App and System/priv-app. Updates might be in Data/App too.
Basically nuke any copies of the T-mob VVM apk and you'll stop getting these messages.
Goronok said:
It's the T-mobile visual voicemail app. I'm on AT&T with the T-mobile Note4 and had this problem as well. With root, you'll need to delete the app from System/App and System/priv-app. Updates might be in Data/App too.
Basically nuke any copies of the T-mob VVM apk and you'll stop getting these messages.
Click to expand...
Click to collapse
thank you so much. i dont have a note 4 i have a tmobile lg g3 on at&t network and after restoring my stock backup i was getting this invalid text going out after every reboot. i treat my phone like my computer so i reboot it every day. this invalid text is really annoying. after trying your suggestion i no longer get this stupid invalid text message. instead of deleting the visual voicemail app i just decided to freeze it and that worked. thank you again.
Goronok said:
It's the T-mobile visual voicemail app. I'm on AT&T with the T-mobile Note4 and had this problem as well. With root, you'll need to delete the app from System/App and System/priv-app. Updates might be in Data/App too.
Basically nuke any copies of the T-mob VVM apk and you'll stop getting these messages.
Click to expand...
Click to collapse
Thank You, thank you that mess was getting hella annoying..
In the body of the message you will note a short message code of 64743. What I did to stop receiving texts was to send 'STOP' to 64743 using my normal SMS application.
I received verification the service was stopped and haven't gotten the error +1121611611 message since.
rustybronnco said:
In the body of the message you will note a short message code of 64743. What I did to stop receiving texts was to send 'STOP' to 64743 using my normal SMS application.
I received verification the service was stopped and haven't gotten the error +1121611611 message since.
Click to expand...
Click to collapse
I tried a restart this morning and the message came back.
What I have done so far is rooted the phone with towelroot, installed ES file manager and removed both MetroPcs visual voice mail apps. The message still comes back after a restart.
I'll try this method next.
It's the T-mobile visual voicemail app. I'm on AT&T with the T-mobile Note4 and had this problem as well. With root, you'll need to delete the app from System/App and System/priv-app. Updates might be in Data/App too.
Click to expand...
Click to collapse
Rooting the phone, installing ES File Explorer and removing all visual voice mail references fixed the issue. It was a little different on my LG F6 than just removing the files from system/.... but the basic idea was the same.

SMS notifications stopped working after Android 7 update

Hi folks.
Last week I received an update from HTC to update my One M9 to Android 7. All went well with one exception: Since the update I no longer receive notifications off new SMS messages. They arrive (and send) fine, just no tone, vibes, or system tray (for want of a better description) alerts. The only way to know if I have a new message is to go into messages and have a look (a real pain). My assumption was a setting had somehow changed during the update so checked them.
There are 2 lots of settings for SMS notifications that I can see, one in the general settings (Settings-Apps-Notifications) which seems to be all as it should be, and a second lot accessible within the app itself (Settings-Notifications) where I think the problem may be. When I try to click the Notifications link the app immediately stops working with the message "Messages has stopped unexpectedly" and an offer of sending an error report. This error report is very long with all the details of my phone, hardware and software, but no other info beyond 'package com.htc.sense.mms has crashed'.
I have rebooted the phone a couple of times since the update but that did not help (although it did revive the playstore app which was also poorly after the update), and disabled 'Hangouts' as I read elsewhere this can sometimes be an issue but that did not help either. I have also tried all of the above in safe mode but the problem is still there.
Anybody have any ideas please? Many thanks in advance.

Can't send SMS after Android 10 update

Hello,
I have an unrooted, p30 pro Canadian model vog-l04. I just got the automatic update to Android 10 but now I am unable to send SMS messages. I can receive them fine but can't send. I have tried everything in the list below. Does anyone have any other suggestions?
Cleared the system cache in recovery mode
Checked SIM card
Cleared network configuration (reset network settings)
Force closed messaging app
Cleared messaging app cache.
Uninstalled messaging app updates
Updated messaging app
Rebooted
Edited contact phone numbers
Confirm Message Center Number is correct
Checked voice calling and mobile data
Deleted old messages conversations
Tried sending from different SMS apps.
I really don't want to do a factory reset if I can help it! Is there anything else I can try?
Thank you!
tedinaldo said:
Hello,
I have an unrooted, p30 pro Canadian model vog-l04. I just got the automatic update to Android 10 but now I am unable to send SMS messages. I can receive them fine but can't send. I have tried everything in the list below. Does anyone have any other suggestions?
Cleared the system cache in recovery mode
Checked SIM card
Cleared network configuration (reset network settings)
Force closed messaging app
Cleared messaging app cache.
Uninstalled messaging app updates
Updated messaging app
Rebooted
Edited contact phone numbers
Confirm Message Center Number is correct
Checked voice calling and mobile data
Deleted old messages conversations
Tried sending from different SMS apps.
I really don't want to do a factory reset if I can help it! Is there anything else I can try?
Thank you!
Click to expand...
Click to collapse
Honestly, although you don't want to, after a major OS upgrade a factory reset is always advised, a vast majority of the time it leaves behind rubbish files which cause inexplicable problems like this one that just cannot be fixed any other way.
The only other thing I can think (but doubt) that occasionally happens upgrading to 10, is the APN settings password needs fixing, but that usually causes a no data problem rather than SMS, but worth a look
Thanks for your reply. For anyone else who has this problem, I managed to fix it without a factory reset, thanks to this post here. It's as simple as downloading huawei backup from the play store, which I think I had previously removed. SMS now works fine
tedinaldo said:
Thanks for your reply. For anyone else who has this problem, I managed to fix it without a factory reset, thanks to this post here. It's as simple as downloading huawei backup from the play store, which I think I had previously removed. SMS now works fine
Click to expand...
Click to collapse
Thanks so much - I had tried what I thought was everything to fix this!!! Reinstalling Huawei Backup did indeed instantly fix it.

Categories

Resources