Jump to content

Network Vision and Spark EARFCN logging thread


Recommended Posts

Let me see what I can do about a screen shot...

 

That would be great.  But be precise about location.  Said engineering screen cap basically would need to come from St. Louis proper to be conclusive -- because the Chicago MTA extends surprisingly close to St. Louis exurbs on the Illinois side.

 

AJ

Link to comment
Share on other sites

  • EARFCN 8615 (downlink) [Chillicothe, Ohio (Ross County)]
  • EARFCN 26615 (uplink) [Chillicothe, Ohio (Ross County)]

source: http://s4gru.com/index.php?/topic/4742-columbus-market-mapspreadsheet/page-187&do=findComment&comment=411896

  • Like 1
Link to comment
Share on other sites

I was simply replying to the post above mine that basically the 2nd LTE carrier is more widespread across this region than South Bend.

 

 

 

Let me see what I can do about a screen shot...

I haven't seen any reports of a second carrier in the St. Louis area.
Link to comment
Share on other sites

AJ, here's another 40254 like a few posts up from the Chicago market second carrier FIT.

084cee12d654fd053f2f3717b6b4b8c8.jpg

 

 

Sent from my iPhone 6+

Keep an eye on that TX value. I don't have an iphone, so I can't keep an eye on it myself.
Link to comment
Share on other sites

Keep an eye on that TX value. I don't have an iphone, so I can't keep an eye on it myself.

I always do, although I'm not sure if I should. One of our knowledgable staff members would know more than me if MIMO would be part of this phase of network vision.

 

 

Sent from my iPhone 6+

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

I haven't seen any reports of a second carrier in the St. Louis area.

 

This is my error. First time being outside a Samsung market. Apparently Sector 03 doesn't translate as a 2nd LTE carrier outside of Samsung.  :blush:

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

41176 no longer restricted to Kansas City, also Zanesville Ohio for their b41 second carrier:

0e4e4654abefaa3f9356d35546d7ba2e.jpg

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

2nd PCS LTE carrier found in Flint,  MI

 

 

 

It translates to 1876.8 / 1956.8 MHz which is within the the 30 mhz 1870-1885 / 1950-1965

 PCS B block allocation that Sprint has in East Michigan. 

  • Like 7
Link to comment
Share on other sites

2nd PCS LTE carrier found in Flint,  MI

attachicon.gifScreenshot_2015-07-05-13-27-04.png

It translates to 1876.8 / 1956.8 MHz which is within the the 30 mhz 1870-1885 / 1950-1965

 PCS B block allocation that Sprint has in East Michigan. 

 

Top post updated.  Band 41 spreadsheet updated.

 

AJ

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

B25 second carrier, Danville, IL

bdc83eb000c1a09358b955d38d67dc2f.jpg243453461eca314a4672fba1e9a18a6d.jpgb596310a25638d40a9f84fa85eb3f42c.jpg

 

Possible 10x10 between Indianapolis and Ohio border after Cincinnati market:

0cf787277761f1b171cf82cde15f36cb.jpg7a5356474896826d68f91aa3fe9f771f.jpg966a7e76a7c7a4f34f1a95574e01f229.jpg

 

Sent from my LGLS991 using Tapatalk

  • Like 2
Link to comment
Share on other sites

Normal, IL: 918152f095cf4b62e22d0c1adf5857c0.jpg

 

Plus lots of second carrier set various points since Danville.

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

I noticed that 8315/26315 second carrier when I was making a delivery down in Danville a few weeks ago, and I meant to ask about it. That's the same spectrum used in the Chicagoland area for a second carrier. Did the USCC purchase include this area, too?

 

 

Sent from my iPhone 6

Link to comment
Share on other sites

NOLA B41

 

First carrier 40978

Second carrier 41176

 

Sent from my Nexus 6 using Tapatalk

Screen shots are best

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

NOLA B41

 

First carrier 40978

Second carrier 41176

Screen shots are best

 

Either way, does not really matter.  Those are run of the mill band 41 EARFCNs across numerous markets.  So, they do not really tell us anything new, though it is nice to know that New Orleans has two band 41 carriers running, probably 2x CA, too.

 

AJ

  • Like 2
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

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
  • Recently Browsing

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