Jump to content

Network Vision/LTE - Missouri Market (includes St. Louis)


riddlebox

Recommended Posts

So slightly off topic but drove out to Hermann just to see if LTE roaming on US Cellular was indeed working... Had to go to LTE only because my phone was still trying to keep a 1x800 connection speed isn't too bad either for roaming and being in a rural area... I have Signal Check on since Washington and went out Hwy 100 to 19 probably going down 19 to 50 then back to Union had a lot of converted towers that I don't have site notes for if anyone wants the log when I get done let me know

31fafdb4b6a343e227e7036a63996c19.jpg015a295ac49f4d7fbb40169d73dd04f4.jpg

 

Sent from my LGLS991 using Tapatalk

  • Like 2
Link to comment
Share on other sites

So slightly off topic but drove out to Hermann just to see if LTE roaming on US Cellular was indeed working... 

 

Sent from my LGLS991 using Tapatalk

 

You should update your profile to let us know that you now are using an LG G4.  If you still were using an LG G3 and had LTE roaming on USCC, that would have been remarkable -- because it would have required band 26 MFBI or illegal band 5.

 

Also, since SignalCheck Pro does not have USCC GCI to band detection, you should take a screenshot of your LTE engineering screen to check the band, either band 5 or band 12.

 

AJ

Link to comment
Share on other sites

You should update your profile to let us know that you now are using an LG G4. If you still were using an LG G3 and had LTE roaming on USCC, that would have been remarkable -- because it would have required band 26 MFBI or illegal band 5.

 

Also, since SignalCheck Pro does not have USCC GCI to band detection, you should take a screenshot of your LTE engineering screen to check the band, either band 5 or band 12.

 

AJ

Okay I didn't even realize both of those things

aa4f525026e0293852ccc45fc76bd48c.jpg

  • Like 1
Link to comment
Share on other sites

You should update your profile to let us know that you now are using an LG G4. If you still were using an LG G3 and had LTE roaming on USCC, that would have been remarkable -- because it would have required band 26 MFBI or illegal band 5.

 

Also, since SignalCheck Pro does not have USCC GCI to band detection, you should take a screenshot of your LTE engineering screen to check the band, either band 5 or band 12.

 

AJ

My signature says LGLS991 which is the LG G4 I'm using tapatalk so maybe my old phone is also posted on the site that I can't see

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

Okay I didn't even realize both of those things

 

Confirming the band may help mikejeep add USCC GCI to band detection.  In this case, band 12 looks like it could be the primary carrier -- because of the low last two digits of the GCI.

 

AJ

Link to comment
Share on other sites

My signature says LGLS991 which is the LG G4 I'm using tapatalk so maybe my old phone is also posted on the site that I can't see

 

Sent from my LGLS991 using Tapatalk

 

Many of us view the actual website, and underneath your profile picture it also lists your current device. You have to go to your S4GRU profile to update that.

  • Like 1
Link to comment
Share on other sites

My adventure is over i believe I hit 3 unique US Cellular sites two were Band 12 and I was on that first site via all 3 sectors for a long time I did pick up a completely different GCI and I checked and it was Band 5 so I'll post that I guess for the hope that mikejeep can possibly get a pattern to identify... LTE Discovery did not show a band and surprisingly the only indication that I was roaming on the phone was "Extended Area" on the lock screen if you don't notice that or have something like Signal Check you probably wouldn't realize it

65a77a8530bbc3884ead2c18e68b3b83.jpge9a5138b75fd26e06d68a59984a54c07.jpg

 

Sent from my LGLS991 using Tapatalk

  • Like 2
Link to comment
Share on other sites

What would it report? I would think it would map for USCC since the phone is reporting a USCC connection.

Not sure about android but on iPhone the carrier name is always reported as sprint even when roaming. The indicator at the top changes to extended but all of the signalcheck-like apps report the carrier to be sprint. Mb it's different on android idk. I just thought it would be good so that people that looked at sensory would be able to see everywhere they would get LTE on sprint roaming or not.

Link to comment
Share on other sites

Not sure about android but on iPhone the carrier name is always reported as sprint even when roaming. The indicator at the top changes to extended but all of the signalcheck-like apps report the carrier to be sprint. Mb it's different on android idk. I just thought it would be good so that people that looked at sensory would be able to see everywhere they would get LTE on sprint roaming or not.

 

I would almost prefer it not show roaming. That or make a distinction between native and roaming. I'm not sure how Sensorly decides what kind of signal it is getting, so until someone actually attempts to map it, I'm not sure it will show on Sprint. It may, but if it is based on the PLMN then it may get mapped as USCC.

Link to comment
Share on other sites

I would almost prefer it not show roaming. That or make a distinction between native and roaming. I'm not sure how Sensorly decides what kind of signal it is getting, so until someone actually attempts to map it, I'm not sure it will show on Sprint. It may, but if it is based on the PLMN then it may get mapped as USCC.

Either way no harm done right?

Link to comment
Share on other sites

Most towers in Jeff city and all so far on east side of the lake have 2nd carrier.

 

And that probably is quite recent.  I was in Jefferson City once every two weeks this fall, and I did not note a band 25 second carrier.  But it seems to be spreading like wildfire across both the Kansas and Missouri markets.

 

AJ

  • Like 1
Link to comment
Share on other sites

And that probably is quite recent. I was in Jefferson City once every two weeks this fall, and I did not note a band 25 second carrier. But it seems to be spreading like wildfire across both the Kansas and Missouri markets.

 

AJ

Yea wasn't that way Sunday when i went to fly out of stl.

 

Rickie

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

I was out in the Belleville area tonight and when I wasn't on B41 I saw B25 2nd carrier on almost every tower.

Awesome. I'll be in Bellvegas for the holidays - good to know!

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Awesome. I'll be in Bellvegas for the holidays - good to know!

 

Not Belle-tucky?

 

;)

 

AJ

Link to comment
Share on other sites

Not Belle-tucky?

 

;)

 

AJ

Naw, the Illinois equivalent to Kentucky would be southwards where I live. I would love to see sbolen come down just to run Sensorly tracks though Randolph County.

 

Sent from my SM-N920V using Tapatalk

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

  • Similar Content

  • Posts

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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