Jump to content

PLMNs / MCC-MNCs (310-120, 311-870, etc.)


Recommended Posts

To condense things to one thread, rather than spreading 'em around (my bad), here's what we know so far:

 

310-120 gets used for band 25 and 26 LTE, leaving anything else for band 41 (except for some odd behavior on Virgin Mobile)

 

The following MCC-MNC pairs are also assigned to Sprint + Nextel:

 

311-490 Sprintcom

311-870 Sprintcom

311-880 Sprintcom

311-940 Clearwire

316-010 Nextel

 

Of those, 311-940 at least is used in Denver's TD-LTE deployment. I'll let others chime in. At least 311-870 is used in Austin. I believe another PLMN is used there, but I'm unsure of which one.

 

Also, according to tommym65's post, 311-870 is used in Chicago as well:

 

http://s4gru.com/index.php?/topic/5107-lte-800-band-26-sites-accepted-discussion/page-25

 

This probably debunks my theory that 311-870 is a "high capacity designation" for sites that could be used for fixed wireless service if the trial in Corpus Christi is successful.

 

My 311-870 view was taken from a "neutral" (T-Mobile) SIM, and that PLMN hasn't shown up anywhere yet where only band 25 LTE is available.

 

What other MCC-MNC combos hve y'all seem for Sprint or its MVNOs?

Link to comment
Share on other sites

Sorry, Ian, I did not intend to bust your chops in the other thread.  You are a valuable contributor, and this is important info.  So, let us keep it in one central location.

 

I had not thought of popping my T-Mobile SIM into my Nexus 5 in a while.  But that was a good idea, since it enables the 3GPP network scan function.  That said, for those who do not also have a non Sprint SIM for the Nexus 5, simply removing the Sprint SIM and rebooting should also reveal the 3GPP network scan.  Screenshots from various markets are welcome.

 

AJ

Link to comment
Share on other sites

Sorry, Ian, I did not intend to bust your chops in the other thread.  You are a valuable contributor, and this is important info.  So, let us keep it in one central location.

 

I had not thought of popping my T-Mobile SIM into my Nexus 5 in a while.  But that was a good idea, since it enables the 3GPP network scan function.  That said, for those who do not also have a non Sprint SIM for the Nexus 5, simply removing the Sprint SIM and rebooting should also reveal the 3GPP network scan.  Screenshots from various markets are welcome.

 

AJ

The chop-busting was warranted. Just this once :)

 

As for the SIM-free ability to scan networks, note that network selection won't show up even after a reboot if you keep the phone in LTE only mode if you go SIM-less. You have to switch to LTE + GSM mode, then wait a little, then back to LTE only, to both get the selection screen and ensure that you're looking only at LTE networks (vs. LTE + GSM + WCDMA). Of course, if you hadn't messed with *#*#4636#*#* you may not have this problem...and here I am derailing my own dang thread.

  • Like 1
Link to comment
Share on other sites

As for the SIM-free ability to scan networks, note that network selection won't show up even after a reboot if you keep the phone in LTE only mode if you go SIM-less. You have to switch to LTE + GSM mode, then wait a little, then back to LTE only, to both get the selection screen and ensure that you're looking only at LTE networks (vs. LTE + GSM + WCDMA). Of course, if you hadn't messed with *#*#4636#*#* you may not have this problem...and here I am derailing my own dang thread.

 

I hate to have my Testing.apk "special sauce" shared for all to know, but those are all excellent tips.  And I have not done enough SIM swapping to encounter all of the idiosyncratic 3GPP/3GPP2 network acquisition permutations that follow.  So, we appreciate the reports of your direct experience, Ian.

 

AJ

  • Like 1
Link to comment
Share on other sites

Chicago area here. A network scan reveals CLEAR and 311-870 PLMN on my Nexus 5. I can see a confirmed B41 site from my window. I can't access B41 normally, but without a SIM, connecting to CLEAR both put me on B41 with an EARFCN of 40056. For some reason, sometimes on 311-870 I can connect to 41, but other times I get B4 with a T-Mobile PLMN. Not sure what's happening there

  • Like 2
Link to comment
Share on other sites

Chicago area here. A network scan reveals CLEAR and 311-870 PLMN on my Nexus 5. I can see a confirmed B41 site from my window. I can't access B41 normally, but without a SIM, connecting to CLEAR both put me on B41 with an EARFCN of 40056.

 

Can we get a screenshot of EARFCN 40056?  This is a new center frequency, one that we have not seen in other markets.  I would like to add it to my band plan spreadsheet.

 

AJ

  • Like 3
Link to comment
Share on other sites

Can we get a screenshot of EARFCN 40056?  This is a new center frequency, one that we have not seen in other markets.  I would like to add it to my band plan spreadsheet. AJ

Does this help?

 

Screenshot_2014-01-13-08-37-53.png

  • Like 1
Link to comment
Share on other sites

Does this help?

 

Good enough for me.  Thanks.  The WiMAX/TD-LTE spreadsheet will be updated in a moment.

 

http://s4gru.com/index.php?/files/file/29-clearwire-wimaxtd-lte-carrier-band-plan/

 

AJ

  • Like 1
Link to comment
Share on other sites

Okay so maybe someone can explain why this is going on...

 

First picture is of my Samsung Galaxy S3 LTE Engineering screen showing 310-120 as the MCC-MNC.

Second picture is from Mike's SignalCheck Pro app showing 311-490 as the MCC-MNC.

 

Yes, I am using VM USA but why would the engineering screen spit out 310-120 which is normally seen on Band 25 but, SignalCheck is putting out 311-490?

Link to comment
Share on other sites

I'm seeing the same issue with SignalCheck on an S4 Mini, showing 310120 on SignalCheck, and 311870 in the LTE Engineering screen.

 

But is the Galaxy S4 Mini connected to band 25 LTE 1900 or band 41 TD-LTE 2600?  That is the question.

 

AJ

Link to comment
Share on other sites

It's connected to B41.

 

And that makes sense.  Band 41 is not going to use the same MCC-MNC as band 25.

 

AJ

Link to comment
Share on other sites

  • 2 weeks later...

Okay so maybe someone can explain why this is going on...

 

First picture is of my Samsung Galaxy S3 LTE Engineering screen showing 310-120 as the MCC-MNC.

 

Second picture is from Mike's SignalCheck Pro app showing 311-490 as the MCC-MNC.

 

Yes, I am using VM USA but why would the engineering screen spit out 310-120 which is normally seen on Band 25 but, SignalCheck is putting out 311-490?

 

I'm seeing the same issue with SignalCheck on an S4 Mini, showing 310120 on SignalCheck, and 311870 in the LTE Engineering screen.

 

A few of you have reported this to me.. JossMan's issue appears to be yet another Samsung enginerring screen bug. It appears to be showing the home/default MCC-MNC for the device in that field, instead of the one it is actually connected to. Especially in JossMan's case, where he's using a Sprint device but is a Virgin Mobile customer, and 311-490 is VM's ID.

 

There are various functions that Android reports the MCC-MNC through. SignalCheck displays the one that has proven to be the most reliable no matter what the connection status is, but the diagnostic reports that can be sent from the app include them all. The evidence I have seen indicates that SignalCheck is correct.

 

In the case of the S4T, the issue is reversed -- the enginerring screen shows the correct ID, but the phone always reports the home/default MCC-MNC. I have been in touch with Samsung, but of course I was left hanging with the dreaded "we will pass it on to the appropriate people".

 

EDIT: To add to this topic overall, I'll toss in this note that I posted in the SignalCheck thread: I was able to confirm with Sprint that Band 25 and 26 are only using PLMN (MCC-MNC) 310-120. Band 41 is only on 311-490 or 311-870. All of this is subject to change in the future if they decide to consolidate IDs. However, I also know that Virgin Mobile users see Band 25 on 311-490.

 

-Mike

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...