I just got my HTC Inspire about 2 days ago and just rooted it to run CM7. I was using the latest stable release and noticed when I sent MMS it would just hang on sending. I then updated to the new nightlies thinking that maybe they would have fixed it in there but no luck. Anyone else experience this issue? I would like all the help since I am new to the android scene. (backstory I had a MotoRazor for 4 years)
studdmufin said:
I just got my HTC Inspire about 2 days ago and just rooted it to run CM7. I was using the latest stable release and noticed when I sent MMS it would just hang on sending. I then updated to the new nightlies thinking that maybe they would have fixed it in there but no luck. Anyone else experience this issue? I would like all the help since I am new to the android scene. (backstory I had a MotoRazor for 4 years)
Click to expand...
Click to collapse
For the last week or two, many of the nightlies have had known MMS issues. Your best bet is to go back to 7.0.3 and troubleshoot the problem. I'm assuming you did a full wipe before installing it. I'm not aware of any MMS issues with the stable releases, so the problem may be something specific to your situation or local cell network issues. Something else worth trying is sending MMS messages with a 3rd party SMS app (such as Handcent, Go SMS, ChompSMS, etc) to see if the problem occurs with those apps as well.
I reflashed 7.0.3 multiple times and yes I wiped everything and it still hangs on sending. I tried GO sms and the stock messaging still no luck. I am going to see restore my first backup (fresh rooted stock ROM) and see if that does anything
Edit:
So I restored to the stock ROM and everything works, and re-flashed again to the CM 7.0.3 and MMS didn't work. I then downloaded the radio from here and that didn't fix then I changed my APN according to this http://forum.xda-developers.com/showthread.php?t=1042553 and still no luck.
Anyone else having these issues?
You have to reset your APN settings and your data HAS to be on. Had the same problem with mine. Rooted inspire 4g running cm7 rom. But not anymore. Except that I can't send when I'm 'only' using my phones wifi signal and my data turned off. But that's not biggie for me..
Wow... I literally was just going to update this thread saying i just figured that out. Thanks for the help tho
I am running CM7.1.0 which I flashed a couple of days ago. I am having the same issue with MMS getting hung on sending. I have updated the APNs from the thread here http://forum.xda-developers.com/showthread.php?t=1042553 and still nothing. I also am not on wifi on the phone and showing good h+ signal.
Can anybody help me?
Well, i tried the new ICS AOSP builds and since the kernel is still 2.xx i'm still getting dropped calls, which i almost never get on MIUI. Has any1 been experiencing this?
Sent from my Google Nexus S using XDA App
I'm not sure if ics is to blame but lately i blame sprint. My wife's ota epic 4g did it twice yesterday. Each call was over 10 mins. My nexus has. My evo rarely did. Maybe Samsung?
this is not official ics, may still unstable
I know my phone has this issue; every time i tried to use an AOSP ROM i would get the dropped call issue and the Hold/Un-Hold -to be able to hear the person calling - issue. None of these showed up on any MIUI i tried (so i stuck with it).
5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:
My old GS3 I was on AOKP Nov 16th build. I tried to flash lean kernal to get wifi issues. Ive tried from several version as they were being updated. I had the issue always and just flashed aokp without using another kernal. (I don't understand why I would bc others have it working fine) I would just reflash aokp and everything would go back to normal. Except this last time. Now anytime I flash any rom doesn't matter which one I get wifi on the first boot and than any reset after the initial flash i get wifi is not in range. I tried going back to stock and redoing everything. Always the same issue when I go to install any rom. Stock always works by the way. I finally got a replacement and the first time I went to do everything I get the same result. After flashing AOKP I get wifi is not in range. Or any rom based on cm10.
Can anyone think of anything? Would be much appreciated! Thanks
I have been driving myself nuts for the past few days and can't understand why.
P.S. I have a nandroid backup for aokp nov 16th build that works fine. I can always go back to that. (which sadly I have to stay on) If I flash nov 16th build I get the wifi issue??? So I am not sure what the difference is between the two?
Edit: I tried on a 16 gb version that they sent me by accident and the same results. So that's three phones I have that will not flash correctly?? I also noticed after the flash my icons of apps on the home screen are a little smaller than normal. Really scratching my head!
(Ok that is from when I was on US Cellulars Network with a GS3. I just switched to Verizon with a new gs3 and I am getting the same results as from US Cellulars version. What is going on? Any Idea's?) I have never had issues till now.
Thanks
Could it be that your roms are defaulting to the "Avoid poor connection" setting? I know I've started over with some roms before and not been able to connect to my networks while that option was selected.
broprah said:
Could it be that your roms are defaulting to the "Avoid poor connection" setting? I know I've started over with some roms before and not been able to connect to my networks while that option was selected.
Click to expand...
Click to collapse
If you are referring in advanced settings, avoid poor connections is unchecked. Under wifi region code I am unable to keep united states checked?
Edit: As long as I have it set to a static ip address I can connect every time. If its set to dhtc or whatever its called every time it restarts is it doeasnt connect automatically.
Sent from my SCH-I535 using Tapatalk 2
Bump
Sent from my SCH-I535 using Tapatalk 2
I switched to this Motorola RAZR HD from my GS3 about 2 months ago. I love the phone. Battery life is awesome, and the phone is lightning fast.
However, in the past week or two, I found that I cannot send MMS messages when connected to WiFi. When I turn off WiFi manually, I can then send MMS no problem.
I do recall doing an OTA update about 10 days ago, which is right around the time my problem started, but I'm not 100% sure that this started exactly after the OTA update. I've also been noticing since the OTA update my phone has been a bit laggy. My phone used to be lightning fast, but now its acting like my GS3 that I had. Again, not sure if this is at all related to any of the other things.
So whats the wifi fix? Is there a known problem with the latest OTA update?
I'm on 4.1.2.
Build #9.8.1Q-62_VQW_MR-2.
System version 9.16.6.XT926.Verizon.en.US
Thanks guys?
MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium
slickfing said:
MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I am aware of that. It is my understanding that the phone disables WiFi to send an MMS and then enables it after the message is sent. It used to work just fine. I don't know what could be causing my problem. I have not changed any settings.
Just wanted to update that I'm still having these problems. 50% of the time the phone will send MMS. The other 50% of the time it will just hang there and keep trying to send and I manually have to turn off wifi to get the MMS to send. Phone still lags, probably worse than ever.
This is also not the same phone as when I first posted. I had a replacement from Verizon a few months ago. The problems carried over with the new phone.
I have been using an app called Clean Master to clean my cache and unwanted files. Seemed to work well at first, but now it doesn't feel like it does anything.