Related
I have been experiencing some pretty severe radio issues. I have been missing calls without the phone ringing and people have to call me multiple times to get through even when I have great signal. My radio switches to 1x for long periods of time and loses all signal randomly (or it goes back and forth between EvDo and and 1x rapidly). This has just started happening over the last week or two and I live in a large city that normally has really great sprint 3g coverage. Today, I got an error that said something about "insufficient radio resources" so I figure that could be related to the problem. I am running Fresh 2.0d and using the 2.42.00.03.10 radio. I think the problems may have started after I tried to update my PRL, but it seemed to update fine and is currently 60664. Has anyone else had this kind of problem and/or know any fixes? Thanks.
This has nothing to do with "Hero CDMA Android Development". I would reload your backup.
.........................
This used to be the area to ask for help when you have problems on the phone running a modded rom/radio. If that has changed I didn't realize it. I have tried going to backups but the problem persists. If you don't want to offer help then don't, but you could be less of a ****.
If this is the wrong forum could a mod plz delete the thread and I'm going to repost in the General forums (although the general forum doesn't seem like the place for Rom/radio problem either)
Maybe flash another radio and see how that works
http://forum.xda-developers.com/showthread.php?t=659762
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
First off I want to start by saying I have flashed my rom to Bamf 1.5 remix. I do not overclock my phone however I have tried limiting my clockspeed hoping to prevent a reboot. The phone did not start the random reboot until I flashed to said rom. I have tried reflashing but no improvements, any ideas?
Sent from my ADR6400L using XDA App
It has happened to me but I believe it just me OCing, flashing back to the kernel that I was using before when my phone was stable and testing it out. If not, I will just go back to 1.5
Also, does anyone know how to edit the power control widgets in the pulldown? I can't find any options. Thanks.
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Happened to me with BAMF 1.6 and leankernel 192X, but only when I set it to ondemandX thru SETCPU. Other than that I've had no reboots.
sent from my BAMF Thunderbolt!
eschelon said:
Did you flash the new radio when you loaded up BAMF 1.5?
If so, there's your problem
Click to expand...
Click to collapse
^^
yeah its pretty common for people who flashed the new radio to have reboots. i have had some of those issues, i found that using different kernels at different clocking speeds made my phone more stable. NOTE: i am not a pro, just something i noticed.
What's really behind all the random reboots?
OK... So I've tried just about every rom on the dev thread, I purchased the TB on launch date and had it rooted as soon as Jcase posted S-off instructions... I am now on the new radio and until today, I haven't had a single random reboot. Then all of a sudden, just about an hour ago, as I'm backing out of Tapatalk, bam... Phone rebooted itself...
Now I've been reading on just about every rom thread where people have been experiencing random reboots. Some think the new radio is the cause, but some people are on the new radio and have not experienced this. Others on the old radio still get random reboots.
Others think its the rom but people have noted this issue on most If not all of the rom threads.
Others think its the kernel that's causing it, but again, there doesn't seem to be any pattern to nail it down to a single kernel. Furthermore, some of these people are not OCing, myself included.
Which leads me to the strangest part of all this. My wife also has the TB. Her phone is totally stock and is not rooted. I got it for her day after launch and for the last few weeks, her phone has also been randomly rebooting. Not constantly, mind you. Just enough to be a nuisance. She has still not updated to OTA... The only suspect to this is that this appears to have started after the 4G outage a few weeks ago... And we are in a 3G only area but there was a day or so we could only connect to 1x...
So what's really causing these random reboots? I'm no expert, never claimed to be one, but is it possible that something going on between our phones and the Verizon network is causing this?
Thoughts... Ideas...?
Sent from my Thunderbolt using Tapatalk
Great post. It's good to know even non rooted users are having reboots.
non-rooted.... Updated yesterday... and got a reboot today.
Sent from my ADR6400L using XDA App
I've had about six lock ups and reboots today since ehrpd has been back up
Sent from my ADR6400L using XDA Premium App
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
GPS was also on when my phone rebooted... Google Maps was running.
Sent from my ADR6400L using XDA App
stock rom, not rooted, has had multiple random reboots
I have had no random reboots, or none that I have personally experienced. I figured if my phone was randomly rebooting I would have noticed a considerable battery drain. I have not noticed that yet. I honestly think that this might be an issue for people with little to no 4g coverage. I am bothered that this has not been addressed yet by verizon as I have seen so many people complain about this.
Hopefully I dont get these either, who knows may it is just phones that are may be defective hardware wise.
Well i just wanted to drop my $.02
I am Rooted and have been just about the same time the OP has been rooted.
I USED to have reboots. I install the full RUU and had reboots i also installed just the RADIO file and had reboots. I also reverted back to stock by the RUU provided by JCase. I Then flashed 1.6 followed 1.6.3 and have not had any problems. I assume that those 2 already had the radio file in them and i didn't not have to flash anything additional. Since being on 1.6 then 1.6.3 i have experienced not 1 reboot. Unless i did it myself.
I did notice then before when i did have the reboots (when i manually flashed RUU or just the RADIO file). I had reboots 3 different ways. I would either get a reboot when my phone had been sitting next to me for a while i would notice the white screen and know it was a reboot. Also the 2 other times was backing out of TapaTalk or native browser/dolphin HD.
So i don't know if that is in a way related. I just don't have them anymore.
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
toebee76 said:
I have had a few reboots across a few different rom, radio, and kernal combos. The only thing that all my reboots have had in common was I had GPS enabled. Ive yet to see a reboot with it off. Could just be a coincidence.
Click to expand...
Click to collapse
This is a possibility... But if that's the case this will be the first Android device I've owned that has rebooted itself randomly due to GPS. Even the Samsung Vibrant, which had horrible GPS right out of the box, didn't reboot itself when it was turned on...
However, if this is the case, why has this only become a recent issue.. now my memory isn't so good... But I don't remember seeing much about this issue on rom threads until recently... I.e the past few weeks... Neither my wife's nor my phone randomly rebooted until just a few weeks ago, and we both have our GPS turned on everyday, all day...
Sent from my Thunderbolt using Tapatalk
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
I live in a strong 3G area and my phone has never re-booted itself as far as I know. I'm doing the update tomorrow and will be interested to see if the problem starts.....I hope not.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
Unfortunately, I had a solid signal when my phone rebooted this afternoon. I was a stone's throw from Philadelphia on I-95. I've never had signal issues along I-95 between New York and Philadelphia. I'm running the released update.
BotsOne said:
I noticed that whenever my phone would reboot (on the leaked radio only,) I had a weak 3g signal. I watched this happen several times. My guess would be the people who aren't having reboots are in an area where they constantly have a good signal. Can anyone else corroborate this?
Click to expand...
Click to collapse
This as well is a possibility... Although I am in an area where 3g is strong... I have seen on my and my wife's phone... Even when standing still... That the 3g icon will vanish and come back seconds later...I am in a decent sized college town, population of about 70000... I couldn't say how strong 3g actually is but its everywhere in the city limits... And most of the countryside...
I have traveled to cities with strong 4g but I didnt stand around long enough in a single place to really watch the phone to see if it was dropping data...
Thanks for the constructive input, everyone... Lets keep the corroboration going and see if we can find a pattern..
Sent from my Thunderbolt using Tapatalk
The only time I had reboot was on the leaked ruu which is now the OTA.
Once I went to BAMF 1.5 with new radio and new base no reboot. About a week ago I flashed back to stock radio just to compare after being on the new one for a while. I see nothing different between them really.
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
sounds familiar....
hey there,
I'm down here in New Zealand with a both versions of device, X & XL
my XL has the problem you speak about.
When i leave my house, it takes for ever to disconnect, pain of course because the 3G or 4G wont flip on while it thinks it is still on wifi.
When i return to my home/SSID the device takes for ever to reconnect, if it even does. i go to the wifi settings, and the connection initiation is just cycling, end attempts to connect, over and over.
I've thought i had fix it once before, by installing a new RUU. I was on RUU 1.77.708.3 Asia, could only find 1.77.708.2.
this seemed to fix disconnection on departure problem, but the cycling and hunting continued when i returned.
I have since found that this must be linked to the bluetooth. I say this because while the wifi is hunting/cycling i flip off the bluetooth and the wifi reconnects within seconds. I tested this more and with bluetooth disabled i have no wifi problems at all, but with bluetooth on, its gives my problems.
The second issue is the bluetooth its self. unlike my flawless desireHD, i can only stream music to my car head-deck, when i get a phone call, the music cuts out like it should, but the phone audio doesn't happen, been like that from the get go. wifi was a problem all the time because this dodgy bluetooth was on all the time so i could listen to music in the car and hopefully one day take calls in the car also.
well i have good news for me, today i flashed CleanROM.3.Standard .
http://forum.xda-developers.com/showthread.php?t=1655011
Today for the first time I can take calls over bluetooth in the car. this is good news because i was certain this was a hardware issue, even it it is, i am confident it can be resolved in the software now.
I'll do a few drive-by's my house tonight to test this wifi, see if that got resolved also. I'll let you know the result later.
I tell you all this in-case our issues are the same, it might save you some time... maybe.
good luck with, and check that bluetooth theory because i'm dying to know if its a common problem.
Cheers
Thank you for that very detailed post.
I also have bluetooth running (connected) to my car and it works flawlessly but it may be a cause for the WiFI staying connected as well. I will turn it off and see how it goes as the week progresses and keep this updated as well.
I would also like to flash clean rom but I am using the Rogers variant so I am worried it might not be compatible.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
This has been a known problem since the HOX has been released.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
First reaction: It's not a glitch, that's just really good WiFi...
Sent from my HTC One X using xda premium
I did those drive-by's......
Me again...
I did those drive-by's of my house, unfortunately there is no joy for me, still the WiFi behaves the same as before.
Its funny, down here we have assumed that the X is the same as the XL apart from the cpu. But in reality they are two completely different machines.
So I turned off Bluetooth and the problem does not occur anymore, WiFi disconnects as needed but it is obviously not a permanent fix. Another problem is the WiFi being on and off with 5 bars swapping between 4G and WiFi...
CleanROM again......
OK, I was doing some more reading and have since found that the developer of CleanROM has released a GSM patch so the hotspot on his ROMs now work.
You might remember i said earlier in this thread that CleanROM.3 worked best for me but the hotspot didn't work so i couldn't use it.
Now i have CleanROM installed again, Hotspot works, bluetooth both Audio & Phone work, and the WiFi at this stage seems to be doing what it should without having to manually toggle the bluetooth on and off. No apparent bugs to report at this stage.
Software Info on phone says this version is built around 1.29.728.12. I don't know if that means all ICS version of that number are good or not, but again its a place to start. Its looking like some versions have the issue and some don't, this re-assures me that it can be resolved within the software. I don't mind testing this stuff, as long as the developers don't mind developing it, and its a good learning curve.... its all good.
Check this CleanROM work out, it could be your answer.
http://forum.xda-developers.com/showthread.php?t=1655011
I'll check back in in a day or so and update you on my WiFi situation.
Cheers!
Thanks again for all your research and assistance.
I have the Rogers variant, should be no problem flashing it to CleanROM correct? Also, for each new CleanROM update, I would have to wipe and flash again? Seems troublesome.
Can you advise on the process required to flash the ROM? I am new to Android and the steps in the thread is not as comprehensive.
Many thanks.
hi there, show you how to load roms, thats a big job for me....
...I'm new to this myself, but i know a tutorial that will save me a ton of typing.
you need to do 2 things first, before flashing roms.
1,Unlock your bootloader
2,Install clockworkmod
have a look at this ,
http://forum.xda-developers.com/showthread.php?t=1647272
Study this thread, very helpfull. He explains how to install clockworkmod on your device, once you have that done you are 80% there, and you only have to do this process once, once done, flashing roms will always be the last 20%, you never do this again.
Infact flashing roms and backing up your own rom is a very simply task. the commands are on a list, just choose them as you go. To backup, wipe, and flash a new rom takes me less than 10 minutes.
Go to you tube and look at this, this shows you how Clockworkmod works.
http://www.youtube.com/watch?v=XOQEmQYFEeY
dont be freaked out, take it step by step, you'll be fine.
I also started this thread, regarding working roms for this wifi issue
http://forum.xda-developers.com/showthread.php?p=27585586#post27585586
no one has replyed yet, but it might yeild helpfull info later on perhaps
Thanks, I will do this shortly. Will unlocking the bootloader or doing any of the aforementioned steps give me the tampered signature?
Yes
yes, your phone will be marked.
Boot loader will be marked "Unlocked" , even if you relock it, its just gonna say "relocked" . nothing you can do about that.
The boot loader will also say "tampered" if you update the rom, but that msg dissappears completely if you update the phone via an RUU.exe
Can this hurt me with regards to warranty requests? I know I can remove the tampered status by flashing a stock ROM but I am concerned re: bootloader.
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: