hi everyone
i've searched around google and this forum and haven't found any fixes for this issue that i'm having.
starting this morning, it seems my text messaages are all out of order. the time stamp on my text message is fine and shows the current time but when i receive a reply, it's 5 hours ahead. so when i go to reply to that message, it will display on top instead of in proper chronological order.
i'm pretty confident that it's not because the cell tower time is messed up because this happens for messages received from people in different geographic locations. also it happened to me while i was at another location more than 50kms away (home and work).
i've tried disabling the auto time and timezone, changing the time and timezone and then enabling the auto update but it's still happening.
i'm using the leaked stock touchwiz jellybean so i've flashed from the uxlf3 radio to the uclf6 radio and now i'm using the uclk4 radio thinking that might have something to do with it. but nope. i've wiped the device and re-flashed the CM10 stable rom, same issue. i've switched back to uxlf3 and flashed embryo 5.4, same issue. i'm at a loss.
i'm using fido lte and my apn is set to ltemobile.apn and my signal strength is good.
please help. :good:
Well it was as simple as pulling out the battery for 30 secs then reseat it and power on. That fixed it.
k.i.s.s.
looks like it wasn't the battery pull after all.. it was definitely the UCLK4 radio that was causing it because the problem came back. as soon as i switched to the stock rogers ics, problem went away and hasn't come back since this morning (12 hrs ago)
I was wrong... I was fine since last week and I know exactly what caused the issue. Goddamn speed test app. I just did the speed test after not doing it since last week and boom... mms ****ed up timestamps again.
Sometimes I wish I wasn't so damn curious.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Related
So I am sitting and attempting to watch some videos at work while I tether from my phone to my galaxy tab. Next thing I know my typically solid speedy connection starts to flicker. Downloads are next to impossible and then websites stop loading. I then thought perhaps its just the app and I then try it on the phone and its dead too. The 4G was full strength but there was no data feed. The only "fix" was killing the radio and starting it back up again. Note I even reflashed the radio just incase with the same results and I havent done any new rom or radio flashing since 1.8.6's release.
I finally decided to step back to MR2 which seems to be working perfectly fine. the speeds are all back to normal with no random outtages. Anyone else have a MR2.5 issue last night/this morning?
Good luck getting a response. This happens to me all the time on BAMF (and a few others) and no one seems to know why. The only ROM so far this hasn't happened to me on is Gingeritis 3D. Everything seems to be normal on the phone (ie 3 or 4G signal is strong) but there is no data connection. So far the only link I can find is it seems to happen more when I'm on WiFi but it does happen when I'm not. I started noticing the problem when I was at work and getting e-mails on my PC but not my phone. Sometimes disabling the radio works or it gets stuck on the re-enable & a reboot is required. I randomly Google a solution to the issue but all I can find is more people with the same issue all not getting an answer. All of this happens with no rhyme or reason - so good luck getting an answer. Hopefully you'll get better results than I did.
Where's the ROM? Since you know, you posted in the development section...
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:
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Well the 4.0.4 thazz build should be pretty stable as its essentially stock. That being said my wife (who is INCREDIBLY picky on how her phone functions... I've yet to get her to try something not TW-based) has been using Tweaked since before it was even posted and uses her phone as a phone constantly (... lot's of out-of-state sisters that she's always yapping with) and has yet to report an issue. I am unclear why you would be having these issues with the particular specificity you are experiencing... especially if kernels are remaining consistent across TW-based builds anyway. Without me being able to recreate it on my end or a logcat taken during the premature disconnect on your end I'm at a loss. If nothing else, at least you found something that works for you, so I suppose it a could be worse.
Sorry for the troubles.
Not all stock apps or play store apps work with 4.1, I had the same problem when I let my battery app manage my data. It would wait to connect sometimes up to 20-30 secs later after waking to make a call. Check all your apps your using for compatibility, and when you wake your phone give it a sec before calling out. If your in a bad area the alternating of edge/3g/HSDPA+ doesn't help either. I stopped allowing my battery app data control and that solved 90% of my issues, sometimes it still does it but only when I'm in the boonies.
techclan said:
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Click to expand...
Click to collapse
LOL I am using T-Mobile service with this device, so if that's the case for you I would expect a few drops from time to time
On a serious note, drops can happen with full bars for a variety of reasons. Tower is overloaded (signal shows strong but can't connect/gets dropped), person you have called drops you (calling someone in NY that has AT&T? ), bad/faulty sim card (free to get checked and replaced), etc. No cell phone/ROM is drop call immune, even stock (and yes even those people using Verizon). FWIW, I haven't dropped a single call in over a month using Thomas' PA and Tweaked. That's pretty good considering that's including the holidays and I didn't go home this year.
Thanks for the replies guys. What drives me crazy is that I have absolutely no dropped calls when using the stock ICS ROM, but as soon as I load any of the ICS ROMs mentioned the voice call gets disconnected periodically. Same Location, Same Apps, Same Calling Number, nothing changes except the ROM.
I'm fairly technical and good at troubleshooting but not an expert in reading the Android Logcat and don't know what to look for in the log. I have loaded the UVLH5 radio after flashing the the custom ROMs to see if that might be the cause but same thing.... I wondering if I need to try an older Radio...
Like I said all is running great with Android ICS 4.0.4 UVLH5 (by tthaz777) + merwin's scorched-kernel-t769-ics v1.0.29 OC to 1728 but not knowing what's causing the drops is just driving me crazy....
To test I just load the ROM and then call one of the free news numbers (ABC News etc 650-293-9114) and put the phone on speakerphone, and yes I have tried varies other numbers... JUST WEIRD
Try finding an app of the app store to make logging easier like logcat or something. Then run the app and make a call. If it doesnt disconnect, restart the log. When it does disconnect, end the log and copy+paste it here. That is the only real way to find out whats up.
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
techclan said:
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
Click to expand...
Click to collapse
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
anactoraaron said:
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
Click to expand...
Click to collapse
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
techclan said:
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
Click to expand...
Click to collapse
Ordering a new sim doesn't mean getting a compatible sim. Have you taken the phone to a Tmo store and had someone check it out? They could've sent you another partially compatible sim for it. If I knew more about reading the logs I would love to help you out....
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.
Like the titles states, the first day the md3 ota was out, and seen it had multi window I immediately upgraded. Not long after I noticed, and after reading forum posts, there were quite a few crippling features they also released with it. After doing some more researching and finding time on my hands, finally today I was able to odin my phone back to mb1. The first thing I did was try and send some pic messages and noticed I still had the 4g signal icon popping up while using my wifi inside my house. I then decided to flash the mb1 modem and TZ hoping this would fix the problem. Still a no go, still getting the 4g icon while using wifi, and pic messages take upwards of 5 minutes to send, if they send at all. Any Ideas? Thanks.
hexitnow said:
Like the titles states, the first day the md3 ota was out, and seen it had multi window I immediately upgraded. Not long after I noticed, and after reading forum posts, there were quite a few crippling features they also released with it. After doing some more researching and finding time on my hands, finally today I was able to odin my phone back to mb1. The first thing I did was try and send some pic messages and noticed I still had the 4g signal icon popping up while using my wifi inside my house. I then decided to flash the mb1 modem and TZ hoping this would fix the problem. Still a no go, still getting the 4g icon while using wifi, and pic messages take upwards of 5 minutes to send, if they send at all. Any Ideas? Thanks.
Click to expand...
Click to collapse
That's exactly what's supposed to happen, maybe you never noticed, but you can't send an mms message over a wifi signal. Mobile data will trigger itself on until the data is sent and automatically shut off.
Sent from my SCH-I535 using Tapatalk 2
I could of sworn I never seen it switch over to 4g when sending a text when my wifi is on. Thanks tho.
ignore me