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:
Related
I have I think a kind of strange problem. I've had my V or a few months now and all of a sudden it doesn't get move than 2 bars on the reception scale where as before it used to get 3-5 sitting in my rec room. Don't know what changed other than adding and removing some apps that I wanted to try out. Don't know which are still there that weren't before but wouldn't think that apps would cause the reception to be poorer.
Thought about an antenna booster/adapter/extension but thought I'd ask others first.
Also, anyone added any antennas to theirs? I noticed there isn't an external connection for one and everything I've read so far talks about add one with the external connection.
Any help would be appreciated.
Try updating your PRL
http://forum.xda-developers.com/showthread.php?t=991668
My optimus had problems like that too, but after upgrading my by rom, baseband stuff is quite better.
Which one are you using ?
bloodclot said:
Try updating your PRL
http://forum.xda-developers.com/showthread.php?t=991668
Click to expand...
Click to collapse
Agreed, Updating the PRL is highly recommended.
Sent from my VM670
Have you really noticed a difference by upgrading your PRL?
Don't know what PRL is
In reading all the responses I was afraid since I don't know what the PRL is. Several places warned against changing things in the PRL if you don't know what the PRL is.
I have rooted my phone and have changed the rom a couple times including bricking it a couple times but had a backup so I recovered but don't know what the PRL is so didn't try that avenue.
Jim
I flashed my PRL today and could only get data to work. SMS and Phone stopped working so I flashed back to my original PRL. I think it was trying to connect to the tower closests to where I was, but told me to call customer service If I wanted to use it.
ROM issue on signal reception
JimReid said:
I have I think a kind of strange problem. I've had my V or a few months now and all of a sudden it doesn't get move than 2 bars on the reception scale where as before it used to get 3-5 sitting in my rec room. Don't know what changed other than adding and removing some apps that I wanted to try out. Don't know which are still there that weren't before but wouldn't think that apps would cause the reception to be poorer.
Thought about an antenna booster/adapter/extension but thought I'd ask others first.
Also, anyone added any antennas to theirs? I noticed there isn't an external connection for one and everything I've read so far talks about add one with the external connection.
Any help would be appreciated.
Click to expand...
Click to collapse
Recently I upgrade my ROM to cyagenmod 10.1. It shows the signal is very poor, but I did not face the issues on call receiving/making. This is the known issue ( fail to refresh the signal strength in status).
Also faced some other issues ( phone hang while call is coming in 'phone locked' condition'.
Finally changed the OS to Android 4.2.1 & PAC-MAN 19.9.0. Except the battery drain issue, no more issues now.
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.
Hi. I was using my Sensation last night, went to bed and woke up the next day only to find that my 4G connection wasn't working! The signal bars were white and the icon (currently an H) is flashing. What does this mean? How can I fix it? I can only use Wifi at the moment, and I DO NOT pay an extra $10/mo to deal with this! How can I fix this? I've checked my data settings, rebooted my phone, scanned fir viruses, but can't figure it out!
Sent from my HTC Sensation using XDA
611
I don't follow you.
ClipTy said:
I don't follow you.
Click to expand...
Click to collapse
They are referring to the number you call for T-Mobile US costumer service.
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
mulletcutter said:
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
Click to expand...
Click to collapse
this happened to me the other day, even in 3G/4G mode my data would never connect and E would just keep flashing over and over again (in like 10 sec. intervals) thought it was a ROM problem so I restored a backup and sure enough, the problem was still happening. I could still make calls and send texts fine tho. its not happening to me anymore, but I found it weird. could it possibly be T-Mobile messing with their towers or something in preparation for LTE?
Well, I'm not sure what caused this very same issue for me a couple days ago. I can say that it ONLY effected my AOSP (CM9) rom, but my Sense rom was unphased. It seems to be a common recent complaint in the OpenSensation thread...
I've since then done a fresh install of CM9 RC1 with the addition of Tamcore's kernel. Although I'm not experiencing the described symptom any longer, I can say that my data speeds are far from exceptional. I'm not sure what is going on, but it does seem to be carrier related.
I experienced the same 1 day after flashing CM9 RC1. I re-flashed the Virtuous Inq. ROM I was using previously and the problem went away
My phone went back to normal later on. I think you were right mulletcutter, they might have been servicing it.
Sent from my HTC Sensation using xda app-developers app
Same data connectivity issue
I have two sensations, both shows similar data connectivity issue on TMobile. Data signal jump to connected and not connected for couple hours, and eventually problem will go away. I have both phones rooted running either CM9 or Kang. So far I have tried couple following things but no solutions. I believe its HTC Sensation hardware issue:
1. Flickering so far seen usually after night long charge in the morning. It will last couple hours, some time days.
2. Changing/reflashing ROMs did not help at all and saw same issue continued.
3. One of my friend has Sensation and he also has seen same issue.
4. Some time going into Phone application(Dialer) and then Settings/Advance settings and come back without doing anything helps but not always.
Please post here is you have temporary/permanent solution or even know the root cause of this data connectivity issue.
Also thinking to call Tmobile to get some kind of help but not expecting much as I bought phones more than year ago but less than 2 years. I don't want to give any more commitment/agreement with Tmobile as planning to move to value plans to save some money. If Tmobile does not help, thinking to try American Express to conver it under extentended warranty as I paid by AMEX credit card.
Thanks
Have you tried the application get ril? I was having some issues myself, I'm also T-Mobile. I tried get ril and found out my radio and ril we're not matching. The application suggested a ril for download and once I did that I went from one bar of connection to five bars of connection on H. It made a big difference for me. Perhaps it could also help you? You can download get ril from the market. It sure won't hurt to try. Best of luck.
Sent from my HTC Sensation using xda premium
Its a defect in the basic aosp framework. There is nothing you can do to fix it. There is also nothing your usage did to start it.
The good news is that it should disappear on its on after a few hours.
Check my threads started history. You will find a thread near the top of that list showing almost all there is to know about this issue. I think my thread might be linked in the first 2 posts of the cm10 faq thread too.
Sent from my HTC Sensation using xda app-developers app
whenever i copy/paste, the app crashes.
whenever i try and use GPS and a run tracking program, it takes a LONG time to find a lock. sometimes it will work, sometimes it won't. then, sometimes mid-run i will lose the signal, when my Droid Incredible would be strong in the GPS area during the same running route.
Will Verizon's newest OTA fix any of these issues?
funkpod said:
whenever i copy/paste, the app crashes.
whenever i try and use GPS and a run tracking program, it takes a LONG time to find a lock. sometimes it will work, sometimes it won't. then, sometimes mid-run i will lose the signal, when my Droid Incredible would be strong in the GPS area during the same running route.
Will Verizon's newest OTA fix any of these issues?
Click to expand...
Click to collapse
Bump, on cm10, but can't post there. My phone will often show me running parallel to the highway I am on. Or jump around g maps randomly.
UberSuber said:
Bump, on cm10, but can't post there. My phone will often show me running parallel to the highway I am on. Or jump around g maps randomly.
Click to expand...
Click to collapse
You can use gps test to clear your agps and let it resync will probaly fix the gps issue. As for the others I dont know.
As for the latest OTA, it corrected the "no sim" issue, added remote connection for support, and a new radio iirc. No gps tweaks.
x714x said:
You can use gps test to clear your agps and let it resync will probaly fix the gps issue. As for the others I dont know.
As for the latest OTA, it corrected the "no sim" issue, added remote connection for support, and a new radio iirc. No gps tweaks.
Click to expand...
Click to collapse
Thanks. I tried GPS Status & Toolbox and cleared/redownloaded the aGPS data. Should be the same thing, right? It didn't help. I flashed Bean's ICS ROM last night, so I'm going to give it a GPS workout on the highway tomorrow to see if it makes a difference. If not, isn't it likely the phone itself? Can a software GPS issue follow you across ROMS?
UberSuber said:
Thanks. I tried GPS Status & Toolbox and cleared/redownloaded the aGPS data. Should be the same thing, right? It didn't help. I flashed Bean's ICS ROM last night, so I'm going to give it a GPS workout on the highway tomorrow to see if it makes a difference. If not, isn't it likely the phone itself? Can a software GPS issue follow you across ROMS?
Click to expand...
Click to collapse
I have been paying close attention to this issue and this is what I have come up with... On a stock (non-rooted) Verizon galaxy S3 I can lock indoors and even after rooting I can lock indoors. It is always after I unlock that damn bootloader that I start getting the gps issues... It still works but it is flaky! Gotta have the thing in clear view of the sky almost always... I say this cause I have had 3 different refurbs for the VZW S3 and so I tested my theory and to back it up I also have an at&t S3 and a T-mobile S3 and they don't require you to unlock your bootloader and I NEVER have had any issues with those models...? I really think it has something to do with unlocking our Verizon bootloader.... IMO Like I said, I have done extensive gps testing and this has been my only idea of what is borking the I535's gps signal strength or lack thereof! I can lock in my brick house with both of my other S3's but the Verizon model is **** as soon as you unlock the bootloader... I have played with just about EVERY app on the appstore and different mods on xda and some have made it better but nothing compared to the others.... Can anyone else chime in and let me know what you think...?
well, I installed the ota, but no fixed on the copy/paste and GPS. Went on my run and it didn't find a lock until the 3rd mile. I guess they will be sending me a New one. Maybe I'll try to root it and unroot Just to preserve my game data, etc. Can I still root it with this new ota? Never rooted before.
I might not root, in which case is have to transfer everything from the internal storage to a Harris data hard drive?
funkpod said:
well, I installed the ota, but no fixed on the copy/paste and GPS. Went on my run and it didn't find a lock until the 3rd mile. I guess they will be sending me a New one. Maybe I'll try to root it and unroot Just to preserve my game data, etc. Can I still root it with this new ota? Never rooted before.
I might not root, in which case is have to transfer everything from the internal storage to a Harris data hard drive?
Click to expand...
Click to collapse
Well, mine took a long time to lock this morning. But it has been accurate all morning, which is improvement. I was having trouble with getting a lock before putting a ROM on, but I can't recall Having any issues before rooting, which I suppose does mean I pit a ROM on, really. But then, I rooted before I really had it long enough to test the GPS. Please post back if you try rooting the ota. Because if I keep having issues with GPS, that is my next step too.
UberSuber said:
Well, mine took a long time to lock this morning. But it has been accurate all morning, which is improvement. I was having trouble with getting a lock before putting a ROM on, but I can't recall Having any issues before rooting, which I suppose does mean I pit a ROM on, really. But then, I rooted before I really had it long enough to test the GPS. Please post back if you try rooting the ota. Because if I keep having issues with GPS, that is my next step too.
Click to expand...
Click to collapse
First post on XDA!
Now to the GPS issue...My S3 had the same type of issues being described in this thread. My gps would take a LONG TIME (5-20+mins) to lock in and if it did lock in then sometimes it would have me driving along a road parallel to the road i was on and i would hear it trying to get me back onto the road i was already on. I talked with Verizon tech support in this issue and the person i talked with just took me step by step to try to nail down the issue. i told him i already tried GPS Status app with resetting AGPS and downloading a new file but that never really helped. So he had me hard reset the phone with holding power, home, and volume up after the powering off. We opened the Maps app that came stock with the phone and it didnt lock in in the few mins that i had it open. Then we downloaded the newest Maps app and tried locking in again...no luck. I was also not receiving the OTA update (phone was always stock and not rooted) so we checked for that through the setting on the phone and i still couldnt receive it. Before all this happened I already talked to Verizon support and they had send me a refurbished S3 a few days before i made the call to tech support. So i told the guy that the refuribished phone that i had received got the OTA update as soon as i put my SIM card in the first time i powered the phone up and i havent had an issue with the GPS on it. He wanted me to just double check the firmware and the GPS signal on both phones and he said there was definatley something wrong with my original phone so that phone was sent back.
So i would suggest just calling the carrier and have them send out a new phone for you if your having GPS issues.
they're sending me a new one, the tech service guy on the phone has a gs3, and he didn't have any of these issues, so they are replacing it.
hopefully it doesn't have this issue...
now i gotta find a way to save all of my game data...
I had this same GPS issue and I found a post that seemed to fix the issue.
Go to Google Services Framework in application manager and clear all data. Then go to Google in application manager and clear data plus uninstall updates. Reboot, installed google update, and now my GPS locks on within seconds. Good luck, hope this fixes your issues as well.
Sent from my SCH-I535 using xda app-developers app
I saw the post on this and tried it but it didn't help my phone.
Sent from my SCH-I535 using xda app-developers app
thanks, i tried clearing those places, and while i couldn't find "google," i cleared "google maps" and hoped it would work, however, it did not.
Verizon is sending me a new phone, hopefully this phone will be better...
Fwiw, mine seems better now on beans ICS rom
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....