My phone is stuck in digital roaming, but gets no 3g. After i updated to 2.3.6 i my 3g started dropping in and out and was slow so i dialed *228 and pressed 2 and it said it failed to update or something and now i have no 3g
Related
I have been having problems with re-establishing a 3g connection after either being on WiFi or after a phone call after checking settings my phone was set to LTE/CDMA in the setting under mobile network I have sense changed this to CDMA only and now it connects automatically what I am thinking is happening is because Houston is a launch city is that it is connection to the LTE tower but won't connect because it is getting the command not to since the towers aren't live. It appears that the phone isn't releasing the LTE connection like it should. I am not sure if this will affect people not in the 6 core test/launch cities but I am thinking it is here.
On a side note since doing this I have noticed a faster 3g connection.
got a htc desire x and a S2 both on tmobile UK and the signal keeps going on both of them randomly in full signal areas and disconnects from the networks and i get 'emergency calls only'
today the htc lost signal but the s2 didnt - it comes back within 10 seconds. then later the s2 did but the htc didnt this happens wether on 2G or 3G in all areas.
the only thing ive noticed is if i delete/remove the apn i dont drop signal all day at all!
ive tried
general.t-mobile.uk
t-mobile
tm
and
everywhere (EE)
t-mobile
tm
still drops on both of these, its driving me mad and been happening for a month on the s2 since ive had it, and on the htc since i had it saturday. ive done a hard reset on both
I'm having serious issues with AT&T LTE in central Mississippi. The LTE network in my college down has been here for at least 8 months, but after ATT did some network upgrades last month, I can no longer access the HSPA network. If I make a call, it kicks me straight down to the EDGE network after a 30+ second delay. Same thing when I receive a call. As a result of the delay, I frequently miss calls and the phone never rings. The issue just started this month. Tried the new APN settings as suggested on other threads, and that just results in EDGE only access. I called AT&T and they forced me to do a full wipe and have them do a network reset. That didn't really fix the issue.
I am on ViperXL 2.0.0 with the latest radio (have tried the older radio too, no fix). Still on HBOOT 1.32 (I think, If not, it's 1.35) I've researched the issue to no avail as to another solution. If I could just use the HSPA network things would be fine, but when there is no LTE I drop to EDGE and the signal strength on the EDGE network here is 2 bars tops when there is 5 bars LTE, so I frequently have no signal when I used to have 5 bars. AT&T, as always in their valiant effort to cover their own butts, says there is no network issue.
Input and solutions welcomed! Thanks guys!
Just tried a sim swap with a friend. He has the s4 active and it makes the step from LTE to HSPA+ with no issues. However, his SIM in my phone still refuses to acknowledge the hspa network. Any suggestions guys? I'm running out of solutions. Problem exists on elegancia and viperxl ROMs.
This wouldn't be an issue except that I live in an area where there is literally at most one bar of edge once it drops the LTE.
UPDATE: After the new sim didn't work, I went ahead and relocked the bootloader and flashed the official RUU. No luck. It seems as though my HSPA radio has actually gone out and will not work.
Weird. I went back home and it works perfectly. But it didn't work where I currently live or anywhere along the 75 miles of travel. Regardless, the replacement HoX+ will be in next week.
Sent from my HTC One X+ using xda app-developers app
For the past week I've been having problems with my phone seeming locked in "wcdma preferred" mode despite it being actually set to lte/cdma in Phone Info menu. I'm in San Francisco and my daily commute path is completely blanketed with lte, and I have never had any problems connecting to lte until this past week. Usually as soon as I arrive in SF on the train, my phone immediately connects to and stays connected to lte. But at around the time tmobile rolled out their new plans (March 25ish?), my phone has been connecting to hspa 4g and remains on hspa until I force a lte connection by going into phone info menu (*#*#7696#*#*) and choosing lte only. This is particularly irksome because the 4g signal is only 2-3 bars while the lte signal is a full 5 bars. For whatever reason, my phone is clinging onto the hspa connection and passes my signal from tower to tower without actually passing it up to a lte tower. Once I force a lte connection, my phone will remain on lte and will pass back and forth between lte towers as it did before.
Anyone else notice this happenning recently?
gtcardwhere said:
For the past week I've been having problems with my phone seeming locked in "wcdma preferred" mode despite it being actually set to lte/cdma in Phone Info menu. I'm in San Francisco and my daily commute path is completely blanketed with lte, and I have never had any problems connecting to lte until this past week. Usually as soon as I arrive in SF on the train, my phone immediately connects to and stays connected to lte. But at around the time tmobile rolled out their new plans (March 25ish?), my phone has been connecting to hspa 4g and remains on hspa until I force a lte connection by going into phone info menu (*#*#7696#*#*) and choosing lte only. This is particularly irksome because the 4g signal is only 2-3 bars while the lte signal is a full 5 bars. For whatever reason, my phone is clinging onto the hspa connection and passes my signal from tower to tower without actually passing it up to a lte tower. Once I force a lte connection, my phone will remain on lte and will pass back and forth between lte towers as it did before.
Anyone else notice this happenning recently?
Click to expand...
Click to collapse
Try setting it to gsm/wcdma/lte auto under settings -> mobile data -> network mode.
Sent from my HTC One using Tapatalk
The gsm/cdma/lte auto setting is the default setting the phone shipped with, and changing it back to this didn't solve the problem. I use lte/cdma because I wanted to eliminate edge bands altogether since data is practically unusable when connected to edge, and the phone has an annoying tendency to fall back onto edge prematurely.
During the times affected, the phone seems to be locked onto the "wcdma only" setting, regardless of what was actually being selected.
I called tmo a few times and the issue seems to be resolved now. I'm certain it was an issue on their end, probably some software provisioning problem that came up when the new rates rolled out. For what it's worth I am on the now grandfathered $20 unlimited data plan.
gtcardwhere said:
The gsm/cdma/lte auto setting is the default setting the phone shipped with, and changing it back to this didn't solve the problem. I use lte/cdma because I wanted to eliminate edge bands altogether since data is practically unusable when connected to edge, and the phone has an annoying tendency to fall back onto edge prematurely.
During the times affected, the phone seems to be locked onto the "wcdma only" setting, regardless of what was actually being selected.
I called tmo a few times and the issue seems to be resolved now. I'm certain it was an issue on their end, probably some software provisioning problem that came up when the new rates rolled out. For what it's worth I am on the now grandfathered $20 unlimited data plan.
Click to expand...
Click to collapse
I'm still trying to understand what T-Mobile was thinking when they changed their plans. Way to keep themselves super competitive.
Hi everyone,
It's the weirdest thing that this htc m7 has been solid for almost 2 years on the T-Mobile network but about a month ago it suddenly wouldn't connect to LTE. If the radio is set back to GSM only then it will connect and operate on 2g. If switched back to LTE it drops network connection.
Sim was exchanged
In the same location another tmo phone connected without issue to LTE
Traveling its the same issue
Restored to factory
Nothing seems to work