[MMS] not working - Sprint HTC EVO 4G LTE

I cant remember what rom i started on when i first noticed it. but i dont receive any multimedia message, I can get text's all day long, but when someone send me a picture, and they say its sent from there side. i never get it.
funny part is if i send myself a mms, i get that. just none from nobody else. Ive tried flashing different radios, updating my profile. nothing seems to work. ive did clean installs + flashed superwipe for a fresh install.
i currently have
ROM: Fresh LTE 5.2.1 by flipz
BANDBASE: 1.05.11.0606
PRL: 25006
PRI: 2.45_003
KERNEL: 3.0.8-01368-g6fdcee1

http://forum.xda-developers.com/showthread.php?t=1839131
Most likely Sprint problem. I had issues too and was beginning to think it was the Rom I'm running (Cm10) low and behold, mms finally downloaded
Sent from my EVO using xda premium

This happens to me from time to time. I believe it too is a Network/Sprint problem. What I do to remedy the problem is use Google Voice to check for SMS, however you can't receive MMS through GV though.

2LoWw7 said:
This happens to me from time to time. I believe it too is a Network/Sprint problem. What I do to remedy the problem is use Google Voice to check for SMS, however you can't receive MMS through GV though.
Click to expand...
Click to collapse
this would work if i could get google voice to pull MMS from me phone number.

Steven 1 said:
http://forum.xda-developers.com/showthread.php?t=1839131
Most likely Sprint problem. I had issues too and was beginning to think it was the Rom I'm running (Cm10) low and behold, mms finally downloaded
Sent from my EVO using xda premium
Click to expand...
Click to collapse
is this a call in issue or a take your phone in deal?

the MMS not loading thread is different from my issue. He at least receives his MMS, they just don't download. Mines doesn't come through, at all.

So i took my phone into the sprint store, and there response was that the phone checks out ok on there diagnostics. And that they didn't know what was wrong with it. And after a stupid amount of time wasted on the phone with tech support and super geeks and bs. They still didn't know what was going on with the phone. At this point, I'm ready to take my phone back to sprint and demand a new replacement one. The update to 2.13v didn't fixed jack. How disappointing was that. I flashed and updated firmware and radios, profile and still nothing.
Finally, earlier today i updated my hboot with (PJ75IMG_Jewel_Boot.img_2.13.651.1_signed.zip) and boom, i got my mms back. I cant 100% say that's what made it work, since im not sure what made it stop in the first place. but its good to go now.

Related

Radio won't turn on, dead phone?

I was running Devil Toast 0.7.1 just fine, and got a text message. Went to reply, noticed that my signal was X instead of the normal. Thinking it was a fluke, I rebooted the phone. Still X.
Since then, I've wiped caches, switched ROMs, reflashed ROMs, nothing is turning that radio back on. I've also tried using *#*#4636#*#* and that didn't do anything either. It's very odd, i'm wondering if the radio just died or something. My blackberry suffered a similar fate, minus the ROMs and stuff.
Any ideas?
Have you tried calling your carrier? Maybe there's an outage.
sitlet said:
Have you tried calling your carrier? Maybe there's an outage.
Click to expand...
Click to collapse
I haven't, but since this is my only phone, calling would require a bit of effort. I'm going to give it a day or so before I try to hunt down someone with a phone (I live alone and all my neighbors are out of town, as this is a college town).
I was just running devil toast cm9, and flashed back to meanrom ice, and then had a issue sort of like that. When I sent a txt message I would get an error, radio interface resource shortage. Also trying to call out failed, a voice would cut in saying "error 16" in English, then Spanish. I updated everything, PRL, profile, ect. I ended up needing to call sprint for them to do a handsfree reset.
Any one else have an issue flashing back from cm9 like this?
I don't see how it could effect it, but heck, Java runs on black magic and unicorn tears.
Sent from my shooty shoot shoot using xda app-developers app

Cannot receive SMS messages

I have searched this over and cannot find a solution to the issue. I have had my GS3 for a number of months now. Just recently, I could no longer receive SMS messages. MMS works ok. I called ATT, they blamed the phone since it wasnt one of theirs. I just hung up with them, as they're no help anyway. I went to the ATT store and one of the guys there took my SIM card out and put it in another phone. All of my messages immediately downloaded to the other phone. We took the SIM out and put it back in my GS3, and everything worked normal again. One week later, it's doing the exact same thing. I don't have another phone to put my SIM into, and I sure don't want to keep going back to the ATT store each week to dump my SMS messages. I have tried everything I can think of to fix it.
Does ANYONE have any suggestions as to why this is suddenly happening?
I am stock everything.
Check correct number in MMS settings Message Centre first .
jje
JJEgan said:
Check correct number in MMS settings Message Centre first .
jje
Click to expand...
Click to collapse
Did that. It seems there is only one. +13123149810
Can you make phone calls without problems?
ronj1986 said:
Can you make phone calls without problems?
Click to expand...
Click to collapse
Yeah, no problems making phone calls. I will say that the other thing that happens quite often is that my phone will make no noise on incoming calls or SMS messages. Someone can send me a message or call, and I'll be sitting right there with the device in hand, and it won't make a noise to let me know.
I am still awaiting my Jelly Bean update. Hopefully that will clear up most of it. It seems these problems began when it updated to 4.0.4.
But the SMS problem SUCKS.
On another note, if the Jelly Bean update doesn't fix these issues, I will be trading my I9300 for a Nokia 920 quicker than you can shake a stick.
im baffled by this problem too things I would of recommended 1st have already been checked. Have you tried a complete/fresh install?.
Seems your service centre number is correct too, have u tried changing it/deleting it, save then reenter the number again?
also found this page for ATT service centre numbers maybe theres more than 1 for your area?
http://www.att.com/esupport/article.jsp?sid=kb38686&cv=820#fbid=WduP4zjirUk
SwiftSmoke said:
im baffled by this problem too things I would of recommended 1st have already been checked. Have you tried a complete/fresh install?.
Seems your service centre number is correct too, have u tried changing it/deleting it, save then reenter the number again?
also found this page for ATT service centre numbers maybe theres more than 1 for your area?
http://www.att.com/esupport/article.jsp?sid=kb38686&cv=820#fbid=WduP4zjirUk
Click to expand...
Click to collapse
Yup. Wiped and reinstalled at the advice of ATT. No help. I am not the only one with this problem if you Google it. But there are no answers for the problem. I'm beside myself.
Can not receive SMS. (Permanent SMSC FIX)
Ok sorry for lasting so long.
Look at this and try. Maybe this is your problem. Had solved my problem. After flashing a new Rom.
If you have problems as described in first post and your smsc number is showing the right thing so also do this steps.
1. Find out the right SMSC (Short Messenger Service Central) number of your provider (for example O2 Germany is: +491760000443)
2.0 Then you have to translate/calculate it
at this site:
http://www.twit88.com/home/utility/sms-pdu-encode-decode
2.1 Type at SMSC your sms-provider-number (Example: +49xxxxx)
2.2 Delete Receiver and the small text under it
2.3 Click on Convert
3. A number appears at the right side, write it on a paper or copy it
4. Open Dialer and type *#*#4636#*#*
5. Click phone data and scroll down to SMSC
6. Then paste or write the number from 3.
7. Click actualize, update or something similar
8. Wait till your network is online again and then click refresh (about 5 seconds)
9. If your entered number still appears everything is working fine.
Sample for O2 Germany
(+49 is Germany replace it with the one from your country)
[SMSC] number is: +491760000443
[Calculated] number is: 0791947106004034110000910000AA00
[Showed] number after update is: 0791947106004034
(You have to cut "AT+CMGW=8")
Hope I could help some one with this.
UUK3 said:
There is a solution for that problem.
Will post it when I'm on pc. Cause it is a little bit much to write from phone.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I look forward to it!
How far away is your PC?
Anybody else know anything about this? It's doing it again. I cleared my messages on my wifes phone last Friday. It almost made it a week.
UUK said he knew of an answer and would post it when he got back to his computer, but he must be aboard the ISS or something. I can't contact him.
It's driving me crazy, not to mention I miss important SMS messages.
Have you tried flashing a new modem?
Sent from my GT-I9300 using xda premium
After Googling the problem, I am not the only one having this issue. It is happening all over. But I cannot seem to find an answer to it. I have contacted Samsung who was absolutely NO help, and ATT, who have created a ticket to try and help solve the issue. They even acknowledge it seems to be a much larger issue than just my device.
In the meantime, I will keep my eyes peeled here if anyone has any insight. I shouldn't have to flash anything as the device is entirely stock.
However, I think I have narrowed it down to the latest 4.0.4 update. It didn't do it before I got the update.
I will keep checking in here regularly.
My s3 suddenly stopped receiving SMS after flashing 4.1.2 Supernexus also tried Dark paranoid android and same issue. Prior to that 4.1.1 B1ackB3an all was great. On Vodafone UK and the SMSSC was correct, sending SMS was fine and if I'd SMS myself it came through straight away. Occasionally SMS were received early morning but nothing all day until sometimes they came through when I walked back into the house after work and it connected to the wifi. I cleared cache and fixed permissions and even when rolling back to 4.1.1 it still persisted. Unrooted and returned to stock lastest Samsung/Vodafone firmware last night and seems ok, will see how it goes over the weekend.
Happened to me before I rooted and if you search is a common problem unrelated to rooting. Mine just started up again after a couple of days (voda uk, 4.0.4)
Sent using Tapatalk
I am hoping when I get the JB update, it will take care of itself.
nigmol said:
Happened to me before I rooted and if you search is a common problem unrelated to rooting. Mine just started up again after a couple of days (voda uk, 4.0.4)
Sent using Tapatalk
Click to expand...
Click to collapse
Seems so from looking on Vodafone forum. I'd just assumed that it was due my switching ROM's as everything had been fine since I first rooted in August. Just coincidence that it started at the same time I switched. Did wonder if it was an S3 and a carrier thing as my wife's iPhone 4s also on Vodafone as been fine throughout.
---------- Post added at 11:27 AM ---------- Previous post was at 11:21 AM ----------
yeahmon said:
I am hoping when I get the JB update, it will take care of itself.
Click to expand...
Click to collapse
Hope it does for you, as it is so frustrating.
Yes. One thing I've noticed from Googling is that it is not carrier dependent. Interesting that rooted devices with different ROMs are experiencing the same issue. As previously stated, my device is 100% stock, not rooted.
Damn, it's doing it again. It didn't last but about 4 days this time. It worked this morning, but not tonight.

Can't make calls, data and sms/mms works fine

As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.

[Q] AT&T Multiple Texts and Delayed Texts???

Have had this device since the day it came out and not sure if i noticed this issue right off the bat but the last month or so it is now almost an everyday problem. I will get a text message say at 2pm. Then again say at 2:30pm will get a new text message notification, open it and see it is the same exact text message i got at 2pm and it is also time stamped at 2pm even though it is now 2:30pm. This will happen maybe 3-4x all within a 4hr window. This will happen regardless what network the sender is on, can be ATT, Verizon, etc. No real pattern to this issue, i live in an area with literally full 4g network everywhere.
Also i will sometimes get delayed text messages. Say it's 1pm and i get a new text message notification. I check it and the time stamp on it is 12:40am even though that was 20min ago and i'm just now receiving the text message even though this whole time i was in full 4g network?
I don't know if this is a bunk device or maybe bad sim card. Spoke with AT&T numerous times and I swear I don't know where the hell they find these people as they can't find their thumb from their a$$hole it seems like they are so clueless. All they want to do is master reset, that doesn't work then they offer to mail me a replacement device. I flash roms so that in itself i would think in a way is a master reset.
Is there a way maybe to check my network settings on my device and if so what should they be for AT&T in the USA? I use Elegancia roms using the ATT network settings he has in place and no one else is having this issue which makes me think maybe it's a bad sim card or just bunk device as this issue seems to get worse by the day now. First i happened maybe twice a week, now it's more like twice a day.
I can easily get a replacement phone but really want that as a last resort. Not looking forward to unlocking, rooting, etc all from scratch again unless there's no other option and i really do have a bad device.
I have had the same issue, it was pretty bad on stock as sometimes I would get a message hours later as well as multiple messages. Using the Elegancia ROMs has somewhat helped, but it still happens from time to time.
Sent from my HTC One X+ using xda premium
I've experienced this as well; running completely stock and on various roms. I noticed it was really bad if I used any 3rd party messaging apps.
+1 here
Sent from my HTC One X+ using Tapatalk 2
This has just started happening to me within the past few days on stock. So far it's only been with 2 or 3 text messages, but it's interesting to see that I'm not the only one having this issue. Could it be a carrier issue?
My understanding and this could all be BS is that android doesn't have a full good push system. Instead it is a pull system based on periodic checks to the provider carriers.
So if u are scheduled to check text at 1230 and get one at 1201 then u don't get notification until 1230.
I think u can always change the frequency of your checks but it's just more data usage or battery drain.
Sent from my HTC One X+
Rularn said:
My understanding and this could all be BS is that android doesn't have a full good push system. Instead it is a pull system based on periodic checks to the provider carriers.
So if u are scheduled to check text at 1230 and get one at 1201 then u don't get notification until 1230.
I think u can always change the frequency of your checks but it's just more data usage or battery drain.
Sent from my HTC One X+
Click to expand...
Click to collapse
That's not how it works, atleast not that long
Your phone typically checks for texts/calls every 3 seconds not every 30 minutes
There used to be a setting you could access to change this, but I know the default is 3
The problems these people are having are network issues
Slithered from my HTC One X+
I've had this issue and engaged ATT about it extensively. They swear up and down it's not a network related issue or a issue with the rom. They replacement my phone with a refurb, still same issues. They just sent me a replacement sim card (which I just got today but have yet to pick it up from the front office).
Doubt any of this will fix the issue. But yea, it sucks.
ddean5 said:
I've had this issue and engaged ATT about it extensively. They swear up and down it's not a network related issue or a issue with the rom. They replacement my phone with a refurb, still same issues. They just sent me a replacement sim card (which I just got today but have yet to pick it up from the front office).
Doubt any of this will fix the issue. But yea, it sucks.
Click to expand...
Click to collapse
Well seems very odd unless nation wide ATT is doing major network changes. I'm in LA California unless all u live here too with the same problem but unlikely. I've been with ATT since 2004 and had many smartphones since and never had this issue until this device about a month after buying it.
I'm going to try the SIM card replacement and see what that does. If no correction then Mayne I can prolong this til the HTC One comes out and get my phone replaced with that! Wishful thinking but seriously WTF?
deeznuts said:
Well seems very odd unless nation wide ATT is doing major network changes. I'm in LA California unless all u live here too with the same problem but unlikely. I've been with ATT since 2004 and had many smartphones since and never had this issue until this device about a month after buying it.
I'm going to try the SIM card replacement and see what that does. If no correction then Mayne I can prolong this til the HTC One comes out and get my phone replaced with that! Wishful thinking but seriously WTF?
Click to expand...
Click to collapse
May I ask if you are using the HTC message app or a 3rd party app? Or both at the same time? Also is this issue the same for all your contact sending you a text? Or just some of them?
Lucky Thirteen said:
May I ask if you are using the HTC message app or a 3rd party app? Or both at the same time? Also is this issue the same for all your contact sending you a text? Or just some of them?
Click to expand...
Click to collapse
Using stock htc messaging. It's random, really no pattern. Sometimes it happens when texting my wife, sometimes not. Same with other contacts. Even when AT&T sent me a test text it was sent twice as a duplicate.
Have you try to eliminate completely the HTC Message app (you can do so via Aroma or with TB), and installing a third party app to verify if this issue is still occurring?
I guess it was a joke thinking a new SIM card would fix the issue. As soon as the ATT rep put the new SIM in, about 10 minutes later get the ATT text. Then 15min later get a new text message and what do u know, it's a duplicate!
Only other thing I can think of is doing a full master reset, new install of the Elegancia 4.4 Rom with full wipe. This is what I usually do but then restore my data via TWRP Data backup. This time I'll try the above WITHOUT doing the data restore and see if that makes any difference. If not then I guess it's device replacement time.
I don't see how it would only be the HTC messaging app as many people use it on the same Rom as me and/or same android OS version of me and they are not having this problem.
Pretty convinced it's maybe the antennas in my device went bad or maybe my data restore is causing network complications?
See screenshot and see time above and time received second text, duplicate still.
I remember having issues long time ago with another device practically as yours and the issue was effectively an issue with the restoration.
As for the third app choice, well, it's a way of testing if something could be conflicting with the HTC Message app. Your choice for not testing.
Lucky Thirteen said:
I remember having issues long time ago with another device practically as yours and the issue was effectively an issue with the restoration.
As for the third app choice, well, it's a way of testing if something could be conflicting with the HTC Message app. Your choice for not testing.
Click to expand...
Click to collapse
Just wanted to test out other things first and maybe that last as I feel that's the last thing that could he causing this. So far after a full wipe and fresh Rom install, no duplicates yet. Tested multiple people all day for better testing and no issues yet. Will report back...
Same thing happens to my HOX+... 100% exactly as described. I'm using stock Rom and stock messaging app (Rooted and TWRP recovery).
Sent from my HTC One X+ using xda app-developers app
joey-pagan said:
Same thing happens to my HOX+... 100% exactly as described. I'm using stock Rom and stock messaging app (Rooted and TWRP recovery).
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Have u found any fixes? Surprised all these people coming out the wood work with the same exact issue as me but I'm the first to post about it.
Update for me well all went well for about 5 days then boom, freakin dupes came back. I did a fresh install, full wipe, zero restore, all from scratch. I was so happy thought it was fixed then the other day when the wife texted me it came in 3x that day all at difference times hut of course with original time stamp.
Only other thing I can think of is to get my device replaced but just hate to go through the whole unlocking process again and transferring music, etc onto new device and zagg screen replacement... Damn HTC, what r u doin?!?
i know CM10.1 aint stable yet, but you can use it for sms n stuff, can you see if this happens on that rom for me please (CM10.1 ATT/TELUS)
Lloir said:
i know CM10.1 aint stable yet, but you can use it for sms n stuff, can you see if this happens on that rom for me please (CM10.1 ATT/TELUS)
Click to expand...
Click to collapse
I used your AT&T CM 10.1 ROM for 3 days and had no SMS/MMS issues at all. I did add a custom APN with the help of tweaker. The new APN allowed the MMS messages to download faster. The ROM is smooth and fast. I needed my phone app so reluctantly I had to revert back to a sense ROM. Thanks for your hard work on this device.
Sent from my HTC One X+ using xda app-developers app
No doubt it's a network issue. I live in Alaska and have the same problem along with everyone else I know who has att, including people with iphones.

[Q] Cant send MMS...at least not all the time

I just installed Cm10.1 on my Razr, it was working fine. much better then my stock rom. I get better service, my texting app isnt broken and its all around a lot faster too. The only problem i have experienced is the intermittent capacity of my phone to send and/or receive picture messages. Earlier today my girlfriend sent me a picture. It wasnt until i had rebooted my phone 2 times and wiped cache did i finally get the messages. I dont know if it was a fluke that it happened like that or not, but its kind of inconvenient.
Afterwards i tried to send a picture back, it was pretty much just a random picture of where i was standing at the time, nothing important, but it did not want to send. No matter what I did it would not send. I wound up checking back at it about 20 mins later and it said that it sent and it actually did.
Is anyone else experiencing this phenomenon and how do i fix it? or is it just something that im going to hope is fixed with a new update soon?
admjwt said:
I just installed Cm10.1 on my Razr, it was working fine. much better then my stock rom. I get better service, my texting app isnt broken and its all around a lot faster too. The only problem i have experienced is the intermittent capacity of my phone to send and/or receive picture messages. Earlier today my girlfriend sent me a picture. It wasnt until i had rebooted my phone 2 times and wiped cache did i finally get the messages. I dont know if it was a fluke that it happened like that or not, but its kind of inconvenient.
Afterwards i tried to send a picture back, it was pretty much just a random picture of where i was standing at the time, nothing important, but it did not want to send. No matter what I did it would not send. I wound up checking back at it about 20 mins later and it said that it sent and it actually did.
Is anyone else experiencing this phenomenon and how do i fix it? or is it just something that im going to hope is fixed with a new update soon?
Click to expand...
Click to collapse
post this in the development thread of cm 10 and somebody will respond to you if they have experienced it already or with a solution if its been updated.

Categories

Resources