Database Info

Possible Bluetooth Fix G2x - Works so far

Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot

fix the a2dp on gb and i'll give you your first donation.

What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!

donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..

Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.

The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.

jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.

So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium

ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.

I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).

mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium

All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.

SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?

No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?

Let's recap the new update

After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?

The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.

aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?

I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....

For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...

* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to

htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.

GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server

Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens

MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!

dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.

JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.

alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly

JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck

krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...

JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?

GPS locks on a lot faster...but still loses accuracy in middle of route.

[Q] HTC sensation "wi-fi" error . Can not turn wi-fi on.

Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance

I also had similar issue when I flashed the original recovery to remove the rooting and clock work mod...
Now if u have the original recovery installed...flash the OTA updates through it and if you don't have the OTA you need to flash the original ROM
After the flashing ur wifi will work normal

hello,
actually I am so new to the stuf. I havent applied any updates to the device, but I guesss it has been s-off ed and applied a different ROM before it has been sold to my friend in USA. Now, which exact ROM would you suggest me to flash and actually where I can find it and read the how to ?.
Thanks

after stock and root i was on Revolution 3.6.1 and now i am using S3N5EaY v 1.4.0 -> agree .. its very smooth - fast and looks great. but still the most important thing is : battery life.. so before i had to charge 2 times a day on hard-use.
theres no need anymore at the moment ;-)
try out by yaself..

hasan.acar said:
Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance
Click to expand...
Click to collapse
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.

Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...

bk_25 said:
Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...
Click to expand...
Click to collapse
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.

dladz said:
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.
Click to expand...
Click to collapse
Hi,
I also tried all you tried and no results.
Changed the case with a friends phone but did not help either.
After a lot of reading through the forums did a logcat to see what the hack the phone is saying about this error and it seems it cannot load the driver.
If it helps smb to go deeper can post it.
Gave a thought or two about knocking it against the wall or throw it from the window but after-all, i think i can live for some time without wifi, my GPRS speed is not bad and maybe soon will be having 3G and during work time can use internet pass-through.
Worst case scenario, will sell it and get EDGE the new quad-core monster HTC will be releasing next year Q1 or early Q2.

dladz said:
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.
Click to expand...
Click to collapse
Dude I got the same problem and I did the same procedure so far but same results as well.
I am just wondering if you got any better results for this issue.
Thanks

Same problem, bad results...
I had the same problem. Both my Bluetooth and WiFi would get stuck on "turning on" but never did, I flashed so many ROMs and Kernels, Tried RUU's from Europe,Asia, and USA and nothing worked. SO I CALLED HTC...thankfully I was still under warranty (It's a 12 month warranty) and shipped my phone away after flashing the latest official T-Mobile RUU, Un-Rooting, and going back to S-ON. It's been a week...I called and they said THE MOTHERBOARD needed to be replaced, which I think is the "default fix" if they can't solve the issue. So hopefully in a week I'll have my phone back...Best of Luck...don't mean to be a Debby Downer but I tried EVERYTHING. Give em a call, it won't hurt to try.

Data blinks in and out on AOSP only since getting new SIM

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:

[Q] gps issues, copy/paste issues, OTA fix?

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