Jump to content

Sprint Roaming+ - Coverage Map Update


clbowens

Recommended Posts

Most of the drive from northwest of Des Moines, IA up to Okoboji, IA is in US Cellular roaming territory. However, for most of the drive despite being connected to US Cellular LTE, I had no data connection whatsoever.

 

Did you restart? I find that once I enter USCC territory that I connect to EVDO / LTE but data doens't work. A restart fixes it for me every time.

 

I go into USCC territory often in TN/NC.

This happened to me in rural KS with my GS7 on multiple occasions. No amount of reboots, air plane mode toggles, or calls to customer service could help me. Something goofy is going on there.

Link to comment
Share on other sites

This happened to me in rural KS with my GS7 on multiple occasions. No amount of reboots, air plane mode toggles, or calls to customer service could help me. Something goofy is going on there.

Where in KS? I had great LTE on NexTech and saw some Pioneer last time I was out there too.

 

Sent from my LG G5

Link to comment
Share on other sites

 

 

Where is KS?

Just north of OK. C'mon! I thought you were a meteorologist? Don't they teach geography anymore? Sheesh!

 

*hides under table*

 

Using Tapatalk on Note 8.0

  • Like 1
Link to comment
Share on other sites

 

This happened to me in rural KS with my GS7 on multiple occasions. No amount of reboots, air plane mode toggles, or calls to customer service could help me. Something goofy is going on there.

 

 

I had trouble getting data to connect on USCC on my GS7 as well.  turning the roaming guard for data ON and getting it to through the prompt up finally fixed it.

 

Also, it was surprisingly hard to get data to stay off while I was out there while still leaving the voice network up.  (several times the restrict background data option would reset itself)

Edited by shockerengr
  • Like 1
Link to comment
Share on other sites

I returned yesterday along the same roads that I traveled on Saturday and therefore came back into USCC territory. I again could not establish any data throughput. My wife's phone worked fine in the same spot.

 

A reboot did not fix it. I also tried to upgrade the PRL even though it didn't need it and did a profile update. Neither fixed it.

 

For some reason, I thought to try to place a voice phone call. The voice call went through and the minute I hung up I had blazingly good LTE data on USCC.

 

It seems as though I just wasn't getting registered properly on their network and by placing a phone call, that flipped the switch somehow.

Link to comment
Share on other sites

For some reason, I thought to try to place a voice phone call. The voice call went through and the minute I hung up I had blazingly good LTE data on USCC.

 

It seems as though I just wasn't getting registered properly on their network and by placing a phone call, that flipped the switch somehow.

 

These things can make phone calls?  You learn something new every day.  I thought that they were just handheld, wireless data computers.

 

AJ

  • Like 3
Link to comment
Share on other sites

I had trouble getting data to connect on USCC on my GS7 as well. turning the roaming guard for data ON and getting it to through the prompt up finally fixed it.

 

Also, it was surprisingly hard to get data to stay off while I was out there while still leaving the voice network up. (several times the restrict background data option would reset itself)

I returned yesterday along the same roads that I traveled on Saturday and therefore came back into USCC territory. I again could not establish any data throughput. My wife's phone worked fine in the same spot.

 

A reboot did not fix it. I also tried to upgrade the PRL even though it didn't need it and did a profile update. Neither fixed it.

 

For some reason, I thought to try to place a voice phone call. The voice call went through and the minute I hung up I had blazingly good LTE data on USCC.

 

It seems as though I just wasn't getting registered properly on their network and by placing a phone call, that flipped the switch somehow.

I was on the phone a couple of times with customer service trying to figure out the problem. Could send texts, too. But no data before or after the calls.

 

One thing I did not try was fiddling with the roaming guards. I'll give that a shot next time around if I still have problems. Thanks for the tip.

Link to comment
Share on other sites

I was on the phone a couple of times with customer service trying to figure out the problem. Could send texts, too. But no data before or after the calls.

 

One thing I did not try was fiddling with the roaming guards. I'll give that a shot next time around if I still have problems. Thanks for the tip.

 

I've noticed that domestic data roaming gets turned off after an automatic profile update, so even after I had turned roaming on for one trip, it was off the next time I was roaming. Not sure if that affects anything on your end, just an issue I've seen.

  • Like 2
Link to comment
Share on other sites

I had similar issues with my G5 in western North Carolina a couple of weeks ago in USCC country; futzing around with the roaming guard settings finally made it work. Probably a bug somewhere in Sprint's LTE roaming implementation (I assume they use the same basic code in every triband device).

 

Alas it'll be a while before I can see if a similar workaround works in CSpire territory, where I've had similar issues (I've never successfully connected to their LTE network in Fulton, Mississippi, despite it being advertised on Sprint's maps).

Link to comment
Share on other sites

  • 2 weeks later...

I successfully got extended network on Carolina West Wireless Sunday, pulled 1Mbps down on EVDO. Completely seemless. Just wish I knew if LTE was there.

It was pretty surprising because I hit it on Hwy 74 between I-24 and I-85. I did not hit it early last weekend when traveling through.

I just happened to look at the right time and pull in a speedtest.

It is interesting though because Sprint doesn't advertise their coverage that far down and neither does CWW. But I have had the same experience with Appalachian Wireless, not advertising coverage that does exist. 

Interesting. Looks like CWW leases PCS D from Sprint in just three counties. L000007757.

Looks like Sprint has 40MHz in Cleveland/Rutherford Counties. Wonder if that lease is why they don't have native coverage.

Link to comment
Share on other sites

I just connected to US Cellular LTE on my note 7 from home. I never get Sprint LTE at home, of course it does show connected to sprint 1x at the same time

 

Sent from my SM-N930P using Tapatalk

This is weird. Does your home get any native Sprint service? I recall U.S. Cellular saying that they've figured out how to have a carrier roam on their LTE network and fall back to native 2G for voice.

 

Perhaps that technology is being implemented and now Sprint phones can favor U.S. Cellular LTE over Sprint EVDO.

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

I got the same screen shot with US Cellular in northwest Iowa earlier this month as well. It showed 1X Sprint and LTE with USCC and I had about 10Mbps speeds.

 

Sent from my SM-T710 using Tapatalk

  • Like 1
Link to comment
Share on other sites

In my situation is was definitely roaming only.

 

Sent from my SM-T710 using Tapatalk

Link to comment
Share on other sites

We already know these devices can't connect to 1x and LTE at the same time. That's just a glitch. My question is, were these native service areas or roaming only? That would go a long way to figuring this out.

 

SRLTE?

 

- Trip

  • Like 2
Link to comment
Share on other sites

We already know these devices can't connect to 1x and LTE at the same time. That's just a glitch. My question is, were these native service areas or roaming only? That would go a long way to figuring this out.

 

That's actually not completely accurate. Your device can *monitor* multiple networks. However, it just cannot transmit and receive on both 1x and LTE at the same time. Every time I have been roaming on LTE, I also have a 1x connection. The signal updates on each independently, but not at the same time. 

 

The interesting thing in this case, is seeing a *Sprint* 1x connection while roaming on USCC LTE. That supposedly should not be possible, because as long as you have a native Sprint connection, any Sprint connection, your device shouldn't be connecting to a roaming signal. At least, that's how it was. It's possible something has changed. When I have traveled to Colorado, when I come into range of Sprint 1x, I immediately lose the LTE roaming connection that I had.

  • Like 2
Link to comment
Share on other sites

I just connected to US Cellular LTE on my note 7 from home. I never get Sprint LTE at home, of course it does show connected to sprint 1x at the same time

 

Sent from my SM-N930P using Tapatalk

 

 

I got the same screen shot with US Cellular in northwest Iowa earlier this month as well. It showed 1X Sprint and LTE with USCC and I had about 10Mbps speeds.

 

Sent from my SM-T710 using Tapatalk

 

This reminds me of the first time I roamed onto NexTech LTE in Kansas. I had a 1x connection along with NexTech LTE, however the 1x connection showed "Sprint." I believe this was in January? When I went through the area again in June, something had changed and the 1x connection correctly showed NexTech. I suspect something similar is going on here, for some reason your device, or possibly SCP, is misidentifying the 1x connection as Sprint when it really is USCC.

 

Unless something has changed to allow LTE roaming to occurring simultaneously with a native Sprint 1x signal. I feel like that's not very likely though.

Link to comment
Share on other sites

That's actually not completely accurate. Your device can *monitor* multiple networks. However, it just cannot transmit and receive on both 1x and LTE at the same time. Every time I have been roaming on LTE, I also have a 1x connection. The signal updates on each independently, but not at the same time.

 

It's also the reason why Carrier Aggregation won't work while our phones are "sniffing" 1x while on LTE. CA capable phones can only receive from 2 different sources at a time, so CA is sacrificed while our phones are sniffing both 1x/LTE. While SRLTE is more dependable than eCSFB for receiving phone calls, it kills CA capability, which hurts user speeds.

 

So why have SRLTE at all? Every CCA/RRPP capable phone was designed that way since not every roaming partner has eCSFB. No SRLTE while roaming would mean no phone calls/texts. Non-CCA/RRPP phones didn't need SRLTE (and didn't have it) since they were never meant to roam other LTE networks.

Link to comment
Share on other sites

On my Project Fi Nexus 6 I frequently park on Sprint 1x and connect to USCC LTE. I figured it was just a Fi thing since it is designed to work on both networks. But seeing how so many on Sprint are having the same issue, it must be by design.

 

Using Tapatalk on Note 8.0

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Yes! That does keep it from wandering off Dish and most importantly, reconnecting immediately (at least where there is n70). Thanks!
    • I have my Dish phone locked to NR-only.  That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time.  Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip
    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...