Jump to content

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


riddlebox

Recommended Posts

We have 4G Broadcasting in Godfrey at Bethany and Montclair.. Just pulled 11Mgs up and about 1 down.

 

You can see me setting in my front room on the map.. Time to go out and paint this map purple.

Edited by Perk44
  • Like 1
Link to comment
Share on other sites

We have 4G Broadcasting in Godfrey at Bethany and Montclair.. Just pulled 11Mgs up and about 1 down.

 

You can see me setting in my front room on the map.. Time to go out and paint this map purple.

Please grab 3 digit style SCID!

 

p.s.....i think you live next door to my ex's parents lol.

Link to comment
Share on other sites

Wasn't Portland announced around 25%?

 

It was about 30% for the market.... but that doesn't take into account how many are actually in the city. 25% for the market doesn't equate 25% in the city. It's more along the lines of 10-15% complete in the STL metro. If all those sites that make up the 25% complete were concentrated in STL, then maybe you'd have a launch.

 

Also, that 25% is a combination of 3G and 4G. The SW Washington/Oregon Market (Portland) was at about 52% complete NV wise, 30% LTE. 

  • Like 1
Link to comment
Share on other sites

It was about 30% for the market.... but that doesn't take into account how many are actually in the city. 25% for the market doesn't equate 25% in the city. It's more along the lines of 10-15% complete in the STL metro. If all those sites that make up the 25% complete were concentrated in STL, then maybe you'd have a launch.

 

Also, that 25% is a combination of 3G and 4G. The SW Washington/Oregon Market (Portland) was at about 52% complete NV wise, 30% LTE. 

 

Ah, thanks for the clarification. I remember reading in one of the announcement threads and it seemed like a lot of Portlanders were upset at the premature launch.

Link to comment
Share on other sites

Ah, thanks for the clarification. I remember reading in one of the announcement threads and it seemed like a lot of Portlanders were upset at the premature launch.

 

It was, and still is a bad launch. Similar to Jacksonville, FL. There's not nearly enough coverage inside of the city limits even still. Example, map below:

 

Portland.png

Link to comment
Share on other sites

It was, and still is a bad launch. Similar to Jacksonville, FL. There's not nearly enough coverage inside of the city limits even still. Example, map below:

 

Good to know that Tigard is covered -- that's where my wife is from. :)

Link to comment
Share on other sites

I think the Montclair site might be a record breaker for time from RRU up to acceptance/LTE Live.

I haven't followed that one. Quickest you mean or slowest?

 

I'm thinking of sneaking into Cottleville 2 and painting the tower red...

Link to comment
Share on other sites

I haven't followed that one. Quickest you mean or slowest?

 

I'm thinking of sneaking into Cottleville 2 and painting the tower red...

 

 

Panels going up montclair & bethany

 

 

 

 

Quickest

  • Like 1
Link to comment
Share on other sites

Do we have anyone in Edwardsville?

I'm in Edwardsville Tuesday-Friday mornings.  What do you need?

Link to comment
Share on other sites

Confirmed the 3 digit SCIDs from 270& 159 in Edwardsville this morning:  17 - 186 - 355.  I didn't go very far north, though.  Points up to Cottonwood Rd should be on Sensorly soon.

  • Like 1
Link to comment
Share on other sites

Interested to see how far north the 159 & 270 site goes. 

I'll head over there and do some mapping.

Link to comment
Share on other sites

Band 41 LTE made its way to my work parking lot.

 

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

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: 6.5 dBm

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

A detailed image for this result can be found here:http://www.speedtest.net/my-result/i/611587505

 

Test Date: Aug 14, 2013 11:48 AM

Download: 12.08 Mbps

Upload: 0.21 Mbps

Ping: 115 ms

Connection Type: Wi-Fi

Server: Olivette, MO

External IP: 184.206.34.125

Internal IP: 192.168.1.2

Latitude: 38.7018

Longitude: -90.4230

http://maps.google.com/maps?f=q&q=38.701805,-90.422960

-118dBm. Not bad.

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

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