Related
Hello all,
My son's EVO will not send MMS. When he tries to send a text with photo, he gets a failure with "generic network failure". We have tried it with wifi, 3G, with Handcent and the stock messaging app. We can't find any other problems, just that, as far as we know.
He rooted the phone using this procedure:
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/54844-guide-rooting-3-7-hboot2-02-w-screen-shots-1-27-2011-a.html
and everything seemed fine, so his ROM is sprintlovers but maybe one version back from the current one.
So finally to my question - Can I flash a nandroid from my EVO (Vaelpak ROM) to his phone? I just want to see if I can send an MMS from his phone using my system. I figure if not, at least we probably ruled out a problem with his ROM.
Advice appreciated !!
Not a good idea, too many different numbers and variables, things can get worse if you mix software/harware/firmare stuff from different phones. I think there are a lot of little differences in the guts. I would make a nandroid backup and flash another rom right on his phone. Can't hurt to try
Dont do it, you will mess things up worse. Titanium Backups, yes. Nandroid, no.
Seconded... Nandroids don't flash from phone to phone. But Titanium Backup, will do the trick. Also make sure your incoming message size is set to 1mb... Are you using stock messenging or handcent?
In the send/mms setting, I set my cache to the 5MB for evo only, on handcent, never had a problem. Also don't place your backup onto his phone, because it will cause problems. I would try the method I suggested, or flash the newest sprint lovers rom if that's what he likes.
il_padrone said:
Seconded... Nandroids don't flash from phone to phone. But Titanium Backup, will do the trick. Also make sure your incoming message size is set to 1mb... Are you using stock messenging or handcent?
Click to expand...
Click to collapse
OK, I'll scratch the nandroid swap thing. Glad I asked!
Tried with both messaging apps. I don't know what his message size limit is, but he has been unable to send OR receive text w/photos. I'll look into it more this evening after work...
rdmpe said:
OK, I'll scratch the nandroid swap thing. Glad I asked!
Tried with both messaging apps. I don't know what his message size limit is, but he has been unable to send OR receive text w/photos. I'll look into it more this evening after work...
Click to expand...
Click to collapse
He's had his mobile data in some form on while doing both, sending and receiving?
teh roxxorz said:
He's had his mobile data in some form on while doing both, sending and receiving?
Click to expand...
Click to collapse
Yes, tried with 3G and with WiFi, didn't work either time. Of course, we've pulled the battery, etc. etc.
Should we try something like wiping caches? Clear app data? I'm at a loss.
rdmpe said:
Yes, tried with 3G and with WiFi, didn't work either time. Of course, we've pulled the battery, etc. etc.
Should we try something like wiping caches? Clear app data? I'm at a loss.
Click to expand...
Click to collapse
In his receive settings, is auto-retrieval enabled?
teh roxxorz said:
In his receive settings, is auto-retrieval enabled?
Click to expand...
Click to collapse
Yes auto-retrieve is on. His "connection settings" (messaging>settings) look different than mine. His were all blank, where mine showed values below each setting. He is able to edit his, so he made them match mine. Unfortunately it did not fix the problem. Funny thing is my connection settings show but can't be changed.
EVO on VaelPak
Update - we backed up, factory reset, wiped cache, and flashed the latest Vaelpak. MMS worked but he missed all the sense stuff, so we flashed Sprint Lovers. Things seemed to be working. He was messing with settings last night when his phone shut down from battery drain. So he charged all night. Phone stuck on white evo screen when booting this morning, even after battery pulls. We did get into recovery tho, so wiped caches and reflashed SL again. Things seem OK again, we'll see... I wonder if he hosed something up when he was going through the root process. If he keeps having issues I'm gonna go through the whole process again just to make sure there weren't any issues with it...
Alright, so I was trying to use a program that some other people have said work fine but it wouldn't work, so I figured I would unroot/reroot and see if it helped. I restored the phone to factory settings, used the instructions that are readily available here and other places to unroot my phone and rooted it using the manual method (just like I did the day I got my phone) and tried to set everything back up, but have run into a few problems.
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
2) Google Wallet
-Was working fine, even used it at McDonald's, but now when I try to load it up for the first time, it sits at a black screen until eventually it says "Wallet is not responding. Would you like to close it? (Wait) (OK)"
Oh, and the program that I originally went through all of this for is still giving me the same error about not being able to locate a partition to remount to write to. What do I need to do to get this thing back to working correctly?
shane_huskey said:
1) Text messaging
-I have used Handcent for a long time on old phones, and used it just fine on this phone, but when I got my phone set back up, texts were coming in from the wrong people. I would get a text from PersonA, but it would show up as PersonB and when I responded it would go to PersonB. The only way that I could respond to PersonA was to back out, go into the people app, choose PersonA and text them. When I did this, it would take me into the exact same thread but have PersonA's name at the top now. When PersonA responded, it would show up as PersonB again and I would have to do it all over.
Click to expand...
Click to collapse
This is happening to me! I am rooted, completely stock otherwise and using Handcent. Is this a handcent issue? Anyone have more insight into this?
I'm in the process of unrooting my phone again to see if it happens when I'm not rooted.
Update:
Unrooted, same issue with Google Wallet and messaging
Rooted again, same issue
I was kindof hoping that someone would have come in here by now with some "here, try this" or "yeah, that happened to me and this is how I fixed it" type post. Am I the first person that has run across these issues after flashing to stock files from code.google.com?
I'm on 2nd nexus and haven't had that issue with handcent on either phones. Stock or rooted..
Sent from my Galaxy Nexus using XDA App
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Well the 3 obvious problems could be:
1) I am either following the steps to unrooting incorrectly. (I don't think that it is rooting that is causing the problem since I a) didn't have the problem before I unrooted the first time and b) the problem is recreated whether I am rooted or not.)
2) My phone is faulty
3) The files that I am using (downloaded directly from http://code.google.com/android/nexus/images.html) are damaged.
The MD5 matches the .tgz file.
Everything looks like it is going through correctly when I am flashing the files.
I don't think that I am following the instructions in correctly, so that narrows it down (in my head anyway). Has anyone else used the factory images for code.google.com? Have you tried running Google Wallet afterwards?
esuohe said:
Are you uninstalling and reinstalling your apps? Have you tried deleting your apps' respective caches?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I have tried going into settings, force closing the app and clearing cache and I have tried resetting the phone to factory defaults. Neither changed how the app behaved. I still just get a black screen with the not responding message.
I did some more research into the Handcent problem, apparently it is fairly widespread on ICS and goSMS has the same issue. Stock is apparently not affected, so I am using that but it sucks...
I have seen a few of the GoSMS and Handcent posts, but I'm not completely sure that I am experiencing the same issue. Every post I have seen speaks of erratic problems. Mine is with every text message. Also, it didn't start happening until I flashed the factory images from code.google.com. Also, the problem only popped up when I started experiencing other problems (like with Google Wallet). Although we are having a similar issue, I believe the root problem of the issue is different, which is why the issues are slightly different.
Went and exchanged my phone today, rooted as soon as I walked in the door, installed everything back to the way that I had it and everything is working fine again. On my way to McDonald's for lunch.
Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...
I am getting errors with my sms texts on my phone. I am able to receive them just fine, however I can not send them. I am running Blazer Rom v4.1 with Rogue Hitman 1.5 kernel. I have already tried fixing permissions as well as updating the PRL and profile. None of that helped. Any help is appreciated. P.S. Everything else on my phone is working just fine including making and receiving phone calls.
Is it text msgs or pic and vid msgs you're having trouble with? Try going to /data/data/com.android.providers.telephony/databases and delete telephony.db. Reset your phone and let me know if that works.
It is the texts themselves I cannot send, although I haven't tried pic or video. I just deleted telephony.db. Lets hope this works =].
Nothing has changed since I deleted the file. I still get the same error message saying that my text is still sending, but it never goes through.
You may consider reflashing.
Sent from my SPH-D710 using XDA
I was thinking of that, but I dont feel like setting everything up a
gain lol.
Then do a nandroid backup. After you flash, get appextractor from the market. I bought the key for it too. It will recover all you apps and the data. Its well worth the couple bucks.
Sent from my SPH-D710 using XDA
I fixed the problem. I ended up reinstalling the rom and now it works fine. Thank you for helping.
MeWarning said:
Is it text msgs or pic and vid msgs you're having trouble with? Try going to /data/data/com.android.providers.telephony/databases and delete telephony.db. Reset your phone and let me know if that works.
Click to expand...
Click to collapse
Thanks MeWarning. I had been searching around for a solution for my phone and came across your post. There aren't a lot of things out there that mention failed texts. My stock Epic Touch would not send any text messages while roaming. I spent an hour on the phone with Sprint, the level 2 tech guy told me to put the phone in Sprint only mode, no help there. I did a factory reset, didn't fix it. So, I rooted the phone and tried deleting the telephony file and all is working now. My boss was having the same issue and that solution fixed his as well.
I get this error message whenever i try to send a multimedia message. I've been able to send picture messages fine since i got this phone, but now i get this every time i try to send one. just started a few days ago.
I use go SMS pro. but i have tried the stock messenger app too and get the same error.
any idea how to delete just the unsent messages? or any other way to fix this?
jda2631 said:
I get this error message whenever i try to send a multimedia message. I've been able to send picture messages fine since i got this phone, but now i get this every time i try to send one. just started a few days ago.
I use go SMS pro. but i have tried the stock messenger app too and get the same error.
any idea how to delete just the unsent messages? or any other way to fix this?
Click to expand...
Click to collapse
Are you running stock or or a custom ROM?
Sent from my SGSIII with the XDA Premium App
stock, but rooted.
What does the exact message say when you try to send it?
Have you called your phone network yet to see if its a problem on their end?
Sent from my SGSIII with the XDA Premium App
edit: just tried to send one again to check the message, the exact error message i get is: "Can't send message right now. There are too many unsent multimedia messages"
I called AT&T and they said they didnt know, everything looks fine and for me to call tech support.
but i have never had luck with any cell phone tech support, so decided to come here first.
jda2631 said:
I get this error message whenever i try to send a multimedia message. I've been able to send picture messages fine since i got this phone, but now i get this every time i try to send one. just started a few days ago.
I use go SMS pro. but i have tried the stock messenger app too and get the same error.
any idea how to delete just the unsent messages? or any other way to fix this?
Click to expand...
Click to collapse
This just started happening on my gf phone, any solution yet?
bigslimoid said:
This just started happening on my gf phone, any solution yet?
Click to expand...
Click to collapse
found this post on another board:
I trawled through loads of old messaging conversations and managed to find two failed MMS messages in some conversations. I deleted these and now it's working.
Click to expand...
Click to collapse
your gf might have the same situation. there might be a couple failed mms messages in one of her threads
xBeerdroiDx said:
found this post on another board:
your gf might have the same situation. there might be a couple failed mms messages in one of her threads
Click to expand...
Click to collapse
Idk she said she deleted all conversations and tryed sending again with the same results. I got it to work the other day by forwarding the Kmart then deleting the one that wasn't sending, worked for a couple days then started with the error msg again.
She's on straight talk, running wicked sensations rom. It will be a few days till I see her and have 5he chance to try to figure out what's going on.
bigslimoid said:
Idk she said she deleted all conversations and tryed sending again with the same results. I got it to work the other day by forwarding the Kmart then deleting the one that wasn't sending, worked for a couple days then started with the error msg again.
She's on straight talk, running wicked sensations rom. It will be a few days till I see her and have 5he chance to try to figure out what's going on.
Click to expand...
Click to collapse
Has she tried a different MMS app ?
I had an issue with sending an MMS the other day, didn't get an error message though just wouldn't send. It turned out to be adblock plus. So if she has an adblocker on her phone try deleting it and restarting the phone.
hednik said:
Has she tried a different MMS app ?
Click to expand...
Click to collapse
Just had her install handcent. It works but she's up set it ls not pink and don't match the theme on the rest of her phone. I'm never gonna hear the end of it till I can figure it out.
bigslimoid said:
Just had her install handcent. It works but she's up set it ls not pink and don't match the theme on the rest of her phone. I'm never gonna hear the end of it till I can figure it out.
Click to expand...
Click to collapse
I'll assume you aren't married and haven't learned how to smile and nood lol
There's got to be a way to make it look pink haha.
One possibility is to remove the secmms.apk reboot and then pull it from the zip and push it to system again, fix permissions, wipe cache, reboot. Maybe that will clear any lingering issues.
hednik said:
I'll assume you aren't married and haven't learned how to smile and nood lol
There's got to be a way to make it look pink haha.
One possibility is to remove the secmms.apk reboot and then pull it from the zip and push it to system again, fix permissions, wipe cache, reboot. Maybe that will clear any lingering issues.
Click to expand...
Click to collapse
Lol, nope not married yet. I'm sure i can make it look pink, but ill try what u suggest and see if that works
hednik said:
I'll assume you aren't married and haven't learned how to smile and nood lol
There's got to be a way to make it look pink haha.
One possibility is to remove the secmms.apk reboot and then pull it from the zip and push it to system again, fix permissions, wipe cache, reboot. Maybe that will clear any lingering issues.
Click to expand...
Click to collapse
awww, hednik wears a ring.
i'm in the wedded club as well. we'll have to beer it one night. my wife hates android/tech talk...
hednik said:
I'll assume you aren't married and haven't learned how to smile and nood lol
There's got to be a way to make it look pink haha.
One possibility is to remove the secmms.apk reboot and then pull it from the zip and push it to system again, fix permissions, wipe cache, reboot. Maybe that will clear any lingering issues.
Click to expand...
Click to collapse
Lol, in hot water now! Flashed cement and now don't have any service after boot.
Hoping if I flash twrp it will let me restore the back up I made b4 flashing cwm. Keep your fingers crossed or ill be sleeping on the couch
Cement ? The backup should work just fine.
Don't test your luck too much haha
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 10:28 PM ---------- Previous post was at 10:28 PM ----------
xBeerdroiDx said:
awww, hednik wears a ring.
i'm in the wedded club as well. we'll have to beer it one night. my wife hates android/tech talk...
Click to expand...
Click to collapse
Haha likewise.... Speaking of I need a beer...*hello fridge*
Sent from my SAMSUNG-SGH-I747 using xda premium
Need a little over a year and so is it right for me to I suppose people who get this error just can't send mms anymore, unless reverting with Odin to a completely stock ROM? Haha
Here's what worked for me. Have a Xiomi Redmi Note 3 Pro running latest MIUI developer ROM 7.3.23 and Android 6.0.1 on Rogers network in Canada
Couldnt figure out why I was getting this message only on this phone. My other phones with same SIM card had no issues (Sony Xperia Z Ultra, HTC M8).
Was about to do a factory reset when I came upon an old post. I
1) download the app "History Eraser" from the Play Store
2) open the app and make sure "clear all apps cache" box is CHECKED
3) next, scroll down SMS/MMS section and check boxes "SMS/MMS Draft" and "Failed SMS/MMS"
should delete any messages/other stuff you don't need and is clogging up your system.
Am able to send pics once more using the Xiomi. Good luck!
yep that was the fix for me.
Btw, 3rd party apps wont work on my Xiaomi phone to replace the existing messaging app for SMS and MMS. When I used Facebook messenger I could not send MMS and when I reverted back to the xiaomi messaging app all those attempted to send MMS in facebook messenger were put into the messaging app and I had to go through all my contacts and delete the MMS as they said 'Sending'. Once I removed all the MMS that had not sent it then worked properly again. What a PITA! if your messages aren't that important just delete every chat in your messaging app also works.
Saved me!
sprungy said:
Here's what worked for me. Have a Xiomi Redmi Note 3 Pro running latest MIUI developer ROM 7.3.23 and Android 6.0.1 on Rogers network in Canada
Couldnt figure out why I was getting this message only on this phone. My other phones with same SIM card had no issues (Sony Xperia Z Ultra, HTC M8).
Was about to do a factory reset when I came upon an old post. I
1) download the app "History Eraser" from the Play Store
2) open the app and make sure "clear all apps cache" box is CHECKED
3) next, scroll down SMS/MMS section and check boxes "SMS/MMS Draft" and "Failed SMS/MMS"
should delete any messages/other stuff you don't need and is clogging up your system.
Am able to send pics once more using the Xiomi. Good luck!
Click to expand...
Click to collapse
I too was about to do a factory reset on my Mate 9....when I stumbled on your text. Apparently the default SMS/MMS program "sees" failed sends in all other messaging apps (Skype? Viber" Google Voice) because I had ZERO failed messages in the default program. HISTORY ERASER stopped me from pulling the last remaining hairs on my head. Thanks.