Jump to content

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


riddlebox

Recommended Posts

Can confirm zippy LTE @ the Zoo.

 

===============

Debug

===============

 

Engineering

Current Service for CDMA: N/A

CMDA Signal Strength: N/A

Roaming Indicator value: Not Roaming

Channel: N/A

Latitude: 0

Longitude: 0

RSSI: N/A

SID: 0

NID: 0

Packet Zone ID: 0

Packet Call Control State: Connected

Ec/Io: N/A

Receive Power 0 (CDMA): N/A

Receive Power 1 (CDMA): N/A

Receive Frame Error Rate: N/A

Mobile IP Error Code: 0

IPv4 Address: N/A

PN value: N/A

Subnet Color Code: 0

HDR Session State: Power Save

MAC Index: N/A

Subnet ID: 00 00000000 00000000 00000000

UAY024 value: 00000000 00000000 00000000 00000000

AN-AAA value: No Request

Packet Error Rate value: N/A

DRC Request: 0

P_Rev value: N/A

Dominant PN: 0

Current Service Pilots: N/A

 

eHRPD

Channel: N/A

RSSI: No Signal

Ec/Io: -2.5 dBm

APN: r.ispsn

 

LTE

IMSI: 310120020339171

Connection State: Connected

PLMN ID: 942747955

Band:

[0] type:LTE band:E_UTRA_OPERATING_BAND_41 channel:40978

RSRP: 0 dBm

RSRQ: 0 dB

RS-SINR: -18.4 dB

Tx Power: N/A

APN: r.ispsn

IPv4 Address: 0.0.0.0

IPv6 Address: N/A

IPv4 Call Last Error Code:

IPv6 Call Last Error Code: WDS_CER_UNSPECIFIED_V01

Link to comment
Share on other sites

Signal Check pro vibrated a couple times this morning saying I was connected to LTE. I looked at it and it only said eHRPD, so I hit the reset connection and it said it was connected to LTE for a second. I was not able to get a screen shot fast enough before it went back to eHRPD. I can't get it to connect anymore. I will try to look at towers in this area later, but I can't right now. This is in Wentzville by the intersection of 40 and 70. It might have just been bugging out or something. I haven't heard any news of towers in this area being worked on, nor have I seen any work lately. So I am doubtful.

 

Sent from my EVO using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Signal Check pro vibrated a couple times this morning saying I was connected to LTE. I looked at it and it only said eHRPD, so I hit the reset connection and it said it was connected to LTE for a second. I was not able to get a screen shot fast enough before it went back to eHRPD. I can't get it to connect anymore. I will try to look at towers in this area later, but I can't right now. This is in Wentzville by the intersection of 40 and 70. It might have just been bugging out or something. I haven't heard any news of towers in this area being worked on, nor have I seen any work lately. So I am doubtful.

 

Sent from my EVO using Tapatalk 4 Beta

Never know... keep watch out there
Link to comment
Share on other sites

Anyone else having data issues with the tower at 70 & 79? All of our lines (iPhones) will not connect or have worse than 1rx data speeds. This after several airplane mode and power cycles.

Where are you at in relation to the site? 

Link to comment
Share on other sites

Where are you at in relation to the site?

I have been all around it. On 70 (from mid rivers to hwy K), on Mexico at Salt Lick Rd., at Dierbergs on Salt Lick (79) and 70.

Pic below is the best I could get out of it. The other few tests resulted in complete fails (no ping).

 

Posted Image

Link to comment
Share on other sites

I have been all around it. On 70 (from mid rivers to hwy K), on Mexico at Salt Lick Rd., at Dierbergs on Salt Lick (79) and 70.

Pic below is the best I could get out of it. The other few tests resulted in complete fails (no ping).

 

ypaje4eh.jpg

I pick it up at my house off of Birdie Hills and am having to use WiFi cause the LTE is unresponsive
  • Like 1
Link to comment
Share on other sites

Anyone else having data issues with the tower at 70 & 79? All of our lines (iPhones) will not connect or have worse than 1rx data speeds. This after several airplane mode and power cycles.

Haven't been up that way but I am having the same issues off whatever is serving Zumble and 70. Can't do a speed test, it won't even finish the ping.

Link to comment
Share on other sites

I have been all around it. On 70 (from mid rivers to hwy K), on Mexico at Salt Lick Rd., at Dierbergs on Salt Lick (79) and 70.

Pic below is the best I could get out of it. The other few tests resulted in complete fails (no ping).

 

Posted Image

Typical Sprint legacy lol

 

 

Sent from my iPad using Tapatalk - now Free

Link to comment
Share on other sites

Woo Hoo.  Here's my Sprint haul.  Read 'em and weep.  Gotta love the NV upgrades let alone the LTE.  LMFAO

Screenshot_2013-09-01-16-21-37.png

Link to comment
Share on other sites

Hmmmm same location in Rogersville, MO.  The problem is they (Verizon) have been getting this for over  year we (Sprint) have been sucking hind Ti**y forever.  Will it change?

 

Sprint (my phone)

324 ms ping

43 Kb/s dn

22 Kb/s up

 

Verizon (my wife's phone)

90 ms ping

22 Mb/s dn

2.5 Mb/s up

Link to comment
Share on other sites

Hmmmm same location in Rogersville, MO. The problem is they (Verizon) have been getting this for over year we (Sprint) have been sucking hind Ti**y forever. Will it change?

 

Sprint (my phone)

324 ms ping

43 Kb/s dn

22 Kb/s up

 

Verizon (my wife's phone)

90 ms ping

22 Mb/s dn

2.5 Mb/s up

No one enjoys reading posts about how the Sprint legacy network sucks. We already know. And you know it will change. It is changing. The network is being upgraded.

 

You can sit there and praise VZW. However, my VZW LTE speed was below 1Mbps on Friday evening where I was eating dinner in Albuquerque. Even Sprint 3G was beating it. I had to use T-Mobile LTE to get 20+Mbps. VZW speeds are plummeting in many places at peak times. And they are starting to suck hind teat behind Tmo and AT&T. And even Sprint in many places.

 

Robert via Samsung Galaxy Note 8.0 using Tapatalk

 

 

  • 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

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