Jump to content

AT&T roaming prioritized over Sprint coverage after PRL update.


Risc

Recommended Posts

On 7/28/2018 at 1:13 PM, lilotimz said:

The thing many of you all seem to be missing is that previously any Sprint signal would immediately override any roaming partner signal. 

I'm pretty sure many of you that experienced this also experienced in the past where a crappy Sprint CDMA 1x signal that's basically unusable would constantly kick you off a usable partner network. Sprint changing over to a setup where partner LTE networks would still be in use where Sprint still has a 1x/EVDO signal is in general a good thing for LTE on network time and for sanity checks as devices would not constantly hop between good roaming and terrible native connections .

I did notice that but was more concerned with why I'm on AT&T versus USCC. In my home of all places. I'm on WiFi for the most part but don't really want to accidently use up my roaming allotment just because Sprint decided to push me to roaming instead of remaining on the existing Sprint signal. It takes 10 minutes or more sometimes for the phone to realize there is a Sprint LTE signal available. 

Link to comment
Share on other sites

ive been seeing the same lately but with USCC.

 

I got to thinking maybe this isnt that huge of a deal though in the grand scheme of things.  They have voice agreements with these networks already so maybe VoLTE falls into those agreements and we just didnt realize it?

Link to comment
Share on other sites

Just to update, today I tried updating my PRL again. The number didn't change but I am back on 3G which is good. I'd rather have slow unlimited 3G than a 100mb roaming limit.

Link to comment
Share on other sites

I keep looking for T-Mobile in all the Ohio logs I do. So far only a few snippets in unlikely roaming places.

Sent from my LG-LS997 using Tapatalk

Link to comment
Share on other sites

One issue I saw with aggressive LTE roaming was AT&T 700 LTE would not let go as I drove through a Sprint town with triband LTE.

Sent from my LG-LS997 using Tapatalk

Link to comment
Share on other sites

The aggressive roaming seems to have mostly stopped for me. I've been dropping to 3G (or just 1x) in Sprint dead spots where I know AT&T has a good LTE signal.

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

That's disappointing.  With yesterday being the first of the month, I kinda wonder if they did that to get some more favorable numbers.
My issue was on August 1.

Sent from my LG-LS997 using Tapatalk

Link to comment
Share on other sites

On 7/28/2018 at 11:57 PM, fizzicsguy said:

However on a more exciting note, for the last few days I've been holding Appalachian B12 LTE while still connected to Sprint 800. I am one happy camper!

Alas, things have reverted back to the way they were. It was a great few days though. ?

Link to comment
Share on other sites

Is it possible to configure devices to roam on T-Mobile or other extended LTE - but not at&t - for volte calls while still on Sprint 1x or is it such that if Sprint allows b12 roaming on 1x there isn't a way to discriminate the lte carrier?
I'm worried that VoLTE may have a very rocky start without roaming...

 

Link to comment
Share on other sites

Is it possible to configure devices to roam on T-Mobile or other extended LTE - but not at&t - for volte calls while still on Sprint 1x or is it such that if Sprint allows b12 roaming on 1x there isn't a way to discriminate the lte carrier?
I'm worried that VoLTE may have a very rocky start without roaming...
 
I was wondering the same thing. I'm not sure how LTE roaming is actually done, if it's part of the PRL or not (I suspect not). I suspect that it's possible though, perhaps as a config pushed to the modem.

What was seen in DC is that T-Mobile may be broadcasting the Clearwire PLMN for Sprint roaming. This still shows as roaming on the device, wheras the Clearwire PLMN from Sprint equipment does not. Several markets (DC and NYC for example) still have Clear equipment, and thus the Clear PLMN, in use.

I suspect that the device will happily connect to the Clear PLMN when the signal gets low (likely via a manual scan only due to low signal, since it won't be broadcast as neighbors. ie, the network will not preemptively move a device there and the device won't know about it with a normal signal level). And only after connecting will it discover it's roaming and be configured as such.

However I'm not sure if it actually works that way, so hopefully someone with more knowledge of the technical aspects can chime in.

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

On 8/6/2018 at 5:43 PM, ingenium said:

I was wondering the same thing. I'm not sure how LTE roaming is actually done, if it's part of the PRL or not (I suspect not). I suspect that it's possible though, perhaps as a config pushed to the modem.

What was seen in DC is that T-Mobile may be broadcasting the Clearwire PLMN for Sprint roaming. This still shows as roaming on the device, wheras the Clearwire PLMN from Sprint equipment does not. Several markets (DC and NYC for example) still have Clear equipment, and thus the Clear PLMN, in use.

I suspect that the device will happily connect to the Clear PLMN when the signal gets low (likely via a manual scan only due to low signal, since it won't be broadcast as neighbors. ie, the network will not preemptively move a device there and the device won't know about it with a normal signal level). And only after connecting will it discover it's roaming and be configured as such.

However I'm not sure if it actually works that way, so hopefully someone with more knowledge of the technical aspects can chime in.

Sent from my Pixel 2 XL using Tapatalk
 

LTE roaming is controlled by the SIM card, which can updated over-the-air. PRL is a CDMA legacy feature. 

Link to comment
Share on other sites

Just want to share my experience from earlier.  My phone didn't connect to at&t LTE until I was roaming on Verizon.  Once it connected to at&t it stayed connected even after I went back on native Sprint coverage.
I also noticed that my phone seems more willing to roam onto Verizon voice while connected to Sprint LTE.  Is this actually possible or just my imagination?

 

Link to comment
Share on other sites

Just want to share my experience from earlier.  My phone didn't connect to at&t LTE until I was roaming on Verizon.  Once it connected to at&t it stayed connected even after I went back on native Sprint coverage.
I also noticed that my phone seems more willing to roam onto Verizon voice while connected to Sprint LTE.  Is this actually possible or just my imagination?
 
Happens to me all the time.

Sent from my SM-G965U using Tapatalk

  • Like 1
Link to comment
Share on other sites

1 hour ago, mnjeepmale said:

Back at the cabin this weekend and not roaming on AT&T this time. Just Sprint 3G.
Something changed.

Sent from my SM-N950U using Tapatalk
 

Good. Sprint needs to spend as little as possible on things like roaming. 

I wonder what happened that LTE roaming was liberally allowed?

Link to comment
Share on other sites

9 hours ago, greenbastard said:

Good. Sprint needs to spend as little as possible on things like roaming. 

I wonder what happened that LTE roaming was liberally allowed?

Personally liked Ingenium's idea that liberal LTE roaming should only be used while on VoLTE to keep a call from dropping.

  • Like 1
Link to comment
Share on other sites

9 hours ago, dkyeager said:

Personally liked Ingenium's idea that liberal LTE roaming should only be used while on VoLTE to keep a call from dropping.

I just don't know if VoLTE roaming will work with At&t anytime soon. At&t doesn't allow VoLTE on non-At&t branded Android phones. At&t users with phones such as the Pixel, OnePlus, and Essential don't get VoLTE.

Link to comment
Share on other sites

On 8/12/2018 at 10:44 AM, greenbastard said:

I just don't know if VoLTE roaming will work with At&t anytime soon. At&t doesn't allow VoLTE on non-At&t branded Android phones. At&t users with phones such as the Pixel, OnePlus, and Essential don't get VoLTE.

That's such a ridiculous policy. On T-Mobile if the phone supports VoLTE it works - my phones I bought when living in China work on VoLTE on T-Mobile no problem. I don't get why they do that. AT&T's network is pretty subpar for such a large carrier anyway honestly, so I'm not surprised they have such backward policies.

Link to comment
Share on other sites

That's such a ridiculous policy. On T-Mobile if the phone supports VoLTE it works - my phones I bought when living in China work on VoLTE on T-Mobile no problem. I don't get why they do that. AT&T's network is pretty subpar for such a large carrier anyway honestly, so I'm not surprised they have such backward policies.
Sprint might do the same. BYOD devices don't get wifi calling or Calling+. It remains to be seen if they'll push their VoLTE config to AOSP (public Android source code), or publish an app that configures VoLTE (part of the Android API since 6.0 I believe). Google makes it really easy for carriers to enable VoLTE on Android, and push it out to all capable phones instead of having to wait for an OS update.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

20 hours ago, ingenium said:

Sprint might do the same. BYOD devices don't get wifi calling or Calling+. It remains to be seen if they'll push their VoLTE config to AOSP (public Android source code), or publish an app that configures VoLTE (part of the Android API since 6.0 I believe). Google makes it really easy for carriers to enable VoLTE on Android, and push it out to all capable phones instead of having to wait for an OS update.

Sent from my Pixel 2 XL using Tapatalk
 

The S9 has WiFi Calling and Calling Plus is in a hidden menu. Also the iPhone has Wi-Fi calling even when you do BYOD.

Link to comment
Share on other sites

The S9 has WiFi Calling and Calling Plus is in a hidden menu. Also the iPhone has Wi-Fi calling even when you do BYOD.
Both are phones that Sprint sells themselves, even if it's not that particular "model" (ie S9 running unlocked vs Sprint firmware). iPhones are all the same firmware and is a device that Sprint sells.

I see BYOD as typically meaning Android phones that Sprint doesn't sell directly, but that are "supported" in that it's whitelisted for the network and that they often have support documentation for (and it shows with the correct device name on your account). Which I guess is a fairly small subset of phones...

Really, it comes down to when Sprint will quit trying to implement it their own way and use the API that every other carrier uses, so that it will work on all phones with capable hardware and FCC certification. It would make it so much easier on Sprint too, since they wouldn't have to make custom software for every phone and get the manufacturer to add it in.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

Still look forward to the day I see T-Mobile roaming, was on 3G quite a bit at my 9-5, but then I think of it maybe T-Mobile has no LTE there too. That would make a lot of sense, I'm usually underground when this happens so not too unexpected I guess.

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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