Is it possible to change the frequency bands on the ASGS2? For some reason I am unable to get data connectivity on the 850MHz band in one part of Houston, while 1900MHz works fine. The phone likes to flip between the two, probably because the 850MHz signal is a bit stronger at that location (850MHz = 3 bars, 1900MHz = 2 bars). I'm not sure if it's an interference problem or if the tower is just overloaded / broken.
I tried the ServiceMode menu, but get a RAT selection option restricted message. The sim card removal / hot-insert workaround doesn't seem to work reliably.
I've contacted ATT multiple times in the past 2 weeks and they say it's impossible that there's a problem with the towers and that it must be my phone. I've tried three different Atrix's and an ASGS2 and they all have the same frequency band issue. ATT wants to swap the phone through their mail warranty service, but I'm almost certain it's not the phone based on my previous devices exhibiting the same issue.
Am I taking the right approach here? Would messing around with the band options even help?
You can do it....but only with an i9100 modem...
Sent from my SAMSUNG-SGH-I777 using XDA App
Related
I'm using a Rogers 920 on T-Mobile. I live in an area where refarming is actively happening but not yet complete and I got curious to know whether my 920 is using T-Mobile's AWS or the refarmed PCS (1900MHz).
Here's how to find out.
First, make sure your phone is actually on 3G (might be labeled '4G' or 'H' or whatever depending on the customizations made for your particular variant). You do this just by looking in the system tray at the top of the screen (swipe down from the top of the screen to expose the tray if it's not visible).
Enter the field test app by dialing ##3282# in the phone dialer. Then select WCDMA. You will see a bunch of info -- if it's not populated then wait a few seconds for it to populate. The third line will say UARFCN and it's this value that tells us the frequency being used.
Match the UARFCN value with a cell in the 7th column ("Channel Number (UARFCN) DL") in the UMTS-FDD table in this Wikipedia article.
In my case I frequently see 2062 or 2087, which are AWS channels. I have occasionally seen 537, which is a PCS (1900MHz) channel.
I've done a bit of speed testing and it feels like the phone gets better speeds on AWS than on PCS. I might be imagining this though.
I have a International Galaxy S3 I9300 bought in India and i have come to US and have took a TMobile connection. Now the issue is that , im not getting 3g(h,h+) speeds all the time. I have set my device in Auto(GSM/WCDMA) . I have another guy under same roof using same Tmobile conn (Nexus 4) and he is getting 3g speeds and im not. Its showing as Edge('E') in my phone. I can confirm that the 3G is working at some places near my apartment so its not an activation issue or something. Does it has to do anything with the ROM/kerner . I have been using the Foxhound/Persus combo. Should i change the modem settings?
Try setting the Network Mode setting to WCDMA only (instead of auto). I am on AT&T, but was having same problem in certain areas and this fixed it.
BaronInkjet said:
Try setting the Network Mode setting to WCDMA only (instead of auto). I am on AT&T, but was having same problem in certain areas and this fixed it.
Click to expand...
Click to collapse
Yes, i tried this, but the network goes blank. I'm sure im covered under a 3G area as the other guy is getting awesome speeds under the same roof. Was it because the other guy got his mobile in US(Nexus 4) and i got the international version that it could not read certain spectrum? Really confused.
Did you compare APN settings with other phone? Somewhere here there are probably APN settings that are optimized for T-Mobile. Or may find them on Google.
My gt-i9300 does the same
ashgan4ever said:
I have a International Galaxy S3 I9300 bought in India and i have come to US and have took a TMobile connection. Now the issue is that , im not getting 3g(h,h+) speeds all the time. I have set my device in Auto(GSM/WCDMA) . I have another guy under same roof using same Tmobile conn (Nexus 4) and he is getting 3g speeds and im not. Its showing as Edge('E') in my phone. I can confirm that the 3G is working at some places near my apartment so its not an activation issue or something. Does it has to do anything with the ROM/kerner . I have been using the Foxhound/Persus combo. Should i change the modem settings?
Click to expand...
Click to collapse
I'm on omega v35 and I have tmobile as well. it seems I get this edge all around were I live but then I'll go about a mile in any direction and I'll "all hspap??, 4g, 3g., all" I guess thats because of the towers mabey and the fact that I have the international as well. If any one knows why I would like to know as well.
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.
I believe this phone is capable of using LTE in the US. It has all the right frequencies so I would believe the hardware should be there. I've tried several different APN settings and called customer service to confirm my IMEI with AT&T customer service but I cannot get LTE speeds. Anyone else in the u.s. experiencing the same problems?
barely works in Europe, from the product page i bought it from on Aliexpress they said the 4g wouldn't work in the States .
here majority of the time it drops to 3g and when it does the internet doesn't work at all.
lost count how many times I've had to search again for my network just to refresh the signal.
the antenna in this phone was poorly placed. putting sim in slot 1/2 doesn't matter.
I've gone back to my nexus 5 with zero problems on 4g.
thats really disheartening. I knew there would be a catch to this phone somewhere. And it would appear that the phone does not support 4G LTE bands in the US. .
3.5G umtcs however it does, which is close to 4G speeds. But I do not know how many towers in the US run those frequencies, I will post my findings if I can get HSPA+ or above on a regular basis.
I have noticed my signal fluctuate a lot, Sad that the most basic feature is the most troublesome, this phone comes so close. I wonder if this is something development can resolve or if its just a poor radio.
It will but with network B bands. I think in July.
Check their blog
Really? A coming update in July? I will look on their blog
I live in the UK, but just holidayed in the US this summer...My 9000 wouldn't work for calls, although I read they're bringing out a US version soon. Used it for satnav in 3 states though with no problems.
Is anyone else whos on sprint/TMobile having issues where the phone cant decide wether to connect to a sprint or TMobile tower? When im at my home i have a very weak TMobile 600mhz signal and a strong sprint band 41 signal due to the magic box. I also can pick up the band 25 signal the box uses and my phone refuses to just use the stronger faster sprint signal. It absolutely insists on using the TMobile signal. Is anyone having similar issues? Even on wifi its causing network interruptions so i have to reload a page several times to make it use the wifi.
jwarrior319 said:
Is anyone else whos on sprint/TMobile having issues where the phone cant decide wether to connect to a sprint or TMobile tower? When im at my home i have a very weak TMobile 600mhz signal and a strong sprint band 41 signal due to the magic box. I also can pick up the band 25 signal the box uses and my phone refuses to just use the stronger faster sprint signal. It absolutely insists on using the TMobile signal. Is anyone having similar issues? Even on wifi its causing network interruptions so i have to reload a page several times to make it use the wifi.
Click to expand...
Click to collapse
Mine jumps a lot but never connects to the magic box. I don't think it's enabled for B41? I have a Pixel 3XL that I activate (and deactivate my V60) when I'm at my camper which is where my MB lives.
henderjr said:
Mine jumps a lot but never connects to the magic box. I don't think it's enabled for B41? I have a Pixel 3XL that I activate (and deactivate my V60) when I'm at my camper which is where my MB lives.
Click to expand...
Click to collapse
Mine works with Band 41. Its a big one in the nearby city. It works with all sprint and TMobile bands. Its just prioritizing TMobile bands over sprint ones regardless of signal quality
Sent from my LM-V600 using XDA Labs
jwarrior319 said:
Is anyone else whos on sprint/TMobile having issues where the phone cant decide wether to connect to a sprint or TMobile tower? When im at my home i have a very weak TMobile 600mhz signal and a strong sprint band 41 signal due to the magic box. I also can pick up the band 25 signal the box uses and my phone refuses to just use the stronger faster sprint signal. It absolutely insists on using the TMobile signal. Is anyone having similar issues? Even on wifi its causing network interruptions so i have to reload a page several times to make it use the wifi.
Click to expand...
Click to collapse
I have no idea of this is related but.. I'm on T-Mobile, with T-Mobile home internet as well, and for the last several days my phone is having issues connecting and the home WiFi is doing the same thing. I'm in a rural area so my signal is weak, but it's been fluctuating WILDLY since the merger and sometimes it does seem like my phone is struggling trying to decide what to connect to. There's definitely something going on with the network at least in my area for the last 2 weeks for sure
Ryano89 said:
I have no idea of this is related but.. I'm on T-Mobile, with T-Mobile home internet as well, and for the last several days my phone is having issues connecting and the home WiFi is doing the same thing. I'm in a rural area so my signal is weak, but it's been fluctuating WILDLY since the merger and sometimes it does seem like my phone is struggling trying to decide what to connect to. There's definitely something going on with the network at least in my area for the last 2 weeks for sure
Click to expand...
Click to collapse
Sounds like this will be happening until the transition is done/5G is more widespread. These are TMobile models. When mine was first turned on at the store it had the T-Mobile splash screen. The ability to access sprint towers was added via software update post merger. I figure once the 600mhz band is fully rolled out the issue will go away as a result of the signal being strong enough.
Sent from my LM-V600 using XDA Labs