Jump to content

Current Sprint PRLs


halcyoncmdr

Recommended Posts

If anyone knows, out of curiosity, which roam indicator corresponds to what in Sprint's PRLs (eg. Sprint, Extended, Roaming etc.)?  The ones I see mostly are 0, 1, 160, 162 and there are also a few 228s...

Link to comment
Share on other sites

Were you able to analyze changes in the new 5x054 series yet? Thx!

 

Sorry, have had a hectic week (web server problems, which are on-going) and had completely forgotten. 

 

I'll post some details a little later, but the biggest changes seem to be the addition of a number of "negative" records.  My quick research on the topic means these are networks that the phone IS NOT allowed to roam on.  Looks like this is primarily international operators (Some I can't identify, plus Bell, Nortel, Telus, Newtel, MT Mobility, IslandTel, SaskTel, Aliant Telecom, Hong Kong Telecom, China Telecom, Portatel Del Sureste, Comcel, Telecomunicaciones del Golfo, Operadora Unefon).

 

- Trip

  • Like 1
Link to comment
Share on other sites

I'll post some details a little later, but the biggest changes seem to be the addition of a number of "negative" records.  My quick research on the topic means these are networks that the phone IS NOT allowed to roam on.  Looks like this is primarily international operators (Some I can't identify, plus Bell, Nortel, Telus, Newtel, MT Mobility, IslandTel, SaskTel, Aliant Telecom, Hong Kong Telecom, China Telecom, Portatel Del Sureste, Comcel, Telecomunicaciones del Golfo, Operadora Unefon).

 

In the past, Sprint typically did not NEG certain SIDs, though VZW frequently did.

 

Looking at the list above, I think many/all of those operators are traitors who have switched over to the 3GPP side.  They still may operate skeleton CDMA2000 networks, though.  That could be the reason for the NEG tags.  Sprint now supports various levels of LTE/W-CDMA/GSM international roaming.  The NEG tags could ensure that the roaming does not fall on the barebones legacy CDMA2000 networks instead.

 

AJ

  • Like 7
Link to comment
Share on other sites

In the past, Sprint typically did not NEG certain SIDs, though VZW frequently did.

 

Looking at the list above, I think many/all of those operators are traitors who have switched over to the 3GPP side. They still may operate skeleton CDMA2000 networks, though. That could be the reason for the NEG tags. Sprint now supports various levels of LTE/W-CDMA/GSM international roaming. The NEG tags could ensure that the roaming does not fall on the barebones legacy CDMA2000 networks instead.

 

AJ

I was aware that sprint didn't allow international LTE roaming in any countries?

Link to comment
Share on other sites

I was aware that sprint didn't allow international LTE roaming in any countries?

 

Beep, beep, beep.

 

I am sorry, but you did not pose your response in the proper form of a question.

 

Mr. Connery, you have the board.

 

AJ

  • Like 3
Link to comment
Share on other sites

Beep, beep, beep.

 

I am sorry, but you did not pose your response in the proper form of a question.

 

Mr. Connery, you have the board.

 

AJ

 

Let me try - when did Sprint start offering international LTE roaming?

  • Like 1
Link to comment
Share on other sites

Beep, beep, beep.

 

I am sorry, but you did not pose your response in the proper form of a question.

 

Mr. Connery, you have the board.

 

AJ

I'll take Swords for 500 please.

Link to comment
Share on other sites

Beep, beep, beep.

 

I am sorry, but you did not pose your response in the proper form of a question.

 

Mr. Connery, you have the board.

 

AJ

How's this:

Does sprint offer international LTE roaming?

  • Like 2
Link to comment
Share on other sites

That's what I thought but AJ made it seem otherwise...

I mean they COULD roam on LTE. But for throttled speeds it doesn't really make sense.

 

Sent from my Nexus 6P

Link to comment
Share on other sites

I mean they COULD roam on LTE. But for throttled speeds it doesn't really make sense.

 

Sent from my Nexus 6P

LTE roaming would help with with edge of cell ping as well as unthrottled data (open world/global roaming with high speed pass).

Link to comment
Share on other sites

Trip Ill have some more SCP files ready for you first thing tomorrow morning. 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Sorry, have had a hectic week (web server problems, which are on-going) and had completely forgotten. 

 

I'll post some details a little later, but the biggest changes seem to be the addition of a number of "negative" records.  My quick research on the topic means these are networks that the phone IS NOT allowed to roam on.  Looks like this is primarily international operators (Some I can't identify, plus Bell, Nortel, Telus, Newtel, MT Mobility, IslandTel, SaskTel, Aliant Telecom, Hong Kong Telecom, China Telecom, Portatel Del Sureste, Comcel, Telecomunicaciones del Golfo, Operadora Unefon).

 

- Trip

 

With a mandatory PRL coming up by the end of July for a number of markets (presumably for better LTE refarming since these areas are seeing spectrum swaps), have you noticed any changes in channels being checked?

Link to comment
Share on other sites

With a mandatory PRL coming up by the end of July for a number of markets (presumably for better LTE refarming since these areas are seeing spectrum swaps), have you noticed any changes in channels being checked?

 

Yes.  Something PRL this way comes.  I received this message yesterday from Republic Wireless:

 

Important phone update required.

Our networks are undergoing changes that require a software update on your phone. These changes will impact both voice and data coverage starting July 1, 2016. To continue receiving the best coverage available, please update your Preferred Roaming List (PRL) to the latest version by taking the following steps on your Republic Wireless phone associated with the following phone number(s): (XXX) XXX-XXXX

 

Standard band class 1 CDMA2000 channel assignments all are xxx0 or xxx5.  In other words, they end in 0 or 5

I am awaiting some non xxx0 and non xxx5 band class 1 channel assignments in the PRL -- to reduce the 0.625 MHz guard bands and help enable 10 MHz FDD second carriers in PCS A/B block 30 MHz (15 MHz FDD) markets.

 

AJ

  • Like 4
Link to comment
Share on other sites

  • 3 weeks later...

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

  • Similar Content

  • Posts

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
  • Recently Browsing

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