Jump to content

Sprint now show Coverage in Baltimore, Manhattan/Junction City, KS & Sedalia, MO


Rickie546

Recommended Posts

I just checked the coverage for my area - the updated map shows that my house is now in an LTE coverage area, albeit on the edge. Next time my son comes by the house with his EVO LTE I'll have to have him verify that there is coverage #crossingfingers.

  • Like 1
Link to comment
Share on other sites

I really wish Sprint would hire some web page design folks and create some better looking coverage maps. They look like they were created by a 10 year old. For one thing they need to make a national map that takes up the whole web page on the screen like Verizon does it with tabs to show which cities have LTE. Not only that but they also need a dedicated page to show which cities currently have LTE.

 

They used to have a page dedicated to show which cities have Wimax but they took that away.

Link to comment
Share on other sites

I just checked the coverage for my area - the updated map shows that my house is now in an LTE coverage area, albeit on the edge. Next time my son comes by the house with his EVO LTE I'll have to have him verify that there is coverage #crossingfingers.

fingers crossed, but thus far, sprints LTE maps have been generous with showing coverage where there isnt any, as if the tool used to make coverage didnt consider correct down-tilt and/or height of receiver (phone)
Link to comment
Share on other sites

  • 2 weeks later...

Just arrived in Manhattan. Used coverly to update the eastern edge of town. I'll do more tomorrow. Decently fast. Better then my hotel wifi. I also updated parts of 70. I was surprised how spotty and non existent some parts of kc 4G were.

 

Sent from my SPH-L710 using Tapatalk 2

  • Like 2
Link to comment
Share on other sites

Just arrived in Manhattan. Used coverly to update the eastern edge of town. I'll do more tomorrow. Decently fast. Better then my hotel wifi. I also updated parts of 70. I was surprised how spotty and non existent some parts of kc 4G were.

 

Sent from my SPH-L710 using Tapatalk 2

 

 

So that was you on I-70! That was my task for later this week. Did you by chance also pop up the blip in Lawrence?

 

KC LTE coverage is actually very good.... on the SW side of town, mainly Johnson county. Been getting better on the east side and in KC proper as of late.

Link to comment
Share on other sites

 

 

So that was you on I-70! That was my task for later this week. Did you by chance also pop up the blip in Lawrence?

 

KC LTE coverage is actually very good.... on the SW side of town, mainly Johnson county. Been getting better on the east side and in KC proper as of late.

 

Yup that was me. Lawrence wasn't me though. I'll go down to junction city tomorrow and back onto 70. Took me awhile to get 4G in kc driving on 70. Didnt get any at Arthur Bryant either. If Oklahoma Joes was open today i would've tried there.

 

Sent from my SPH-L710 using Tapatalk 2

  • Like 1
Link to comment
Share on other sites

Yup that was me. Lawrence wasn't me though. I'll go down to junction city tomorrow and back onto 70. Took me awhile to get 4G in kc driving on 70. Didnt get any at Arthur Bryant either. If Oklahoma Joes was open today i would've tried there.

 

Sent from my SPH-L710 using Tapatalk 2

 

Looks like Kansas really got some love today, many new LTE sites showing in Lawrence and Topeka. I've had LTE (before I had sensorly) all the way from the toll both to 435. Beyond that, all new sites. Last time I was out past K-7 was early August. But when I was, I was able to get an LTE signal from several miles west of Junction City all the way several miles east of the air field. Hopefully it's gotten better since then. I was using an EVO, not sure how much difference that makes when latching onto the signal. Arthur Bryant doesn't appear to be covered yet. Hopefully soon.

Link to comment
Share on other sites

Did more of Manhattan and did some junction city and fort Riley in between today. Didn't get any lte on 70 west of junction city. That's it. Now I'm in Denver missing lte. Speeds only averaged 7 down and 4 up. Still better then 3g.

 

Sent from my cm_tenderloin using Tapatalk 2

  • Like 1
Link to comment
Share on other sites

Did more of Manhattan and did some junction city and fort Riley in between today. Didn't get any lte on 70 west of junction city. That's it. Now I'm in Denver missing lte. Speeds only averaged 7 down and 4 up. Still better then 3g.

 

Sent from my cm_tenderloin using Tapatalk 2

 

You may want to look in Salina again. I think you may have picked it up and not realized it while driving down I-70. Those two new blurbs on I-70 there were not there last night.

 

Robert

Link to comment
Share on other sites

On my drive back from Denver in early August I picked up LTE in Salina on I-70, just as I did in Junction City. But, unfortunately I didn't know about Sensorly at that point. It's a three/four hour drive from here, so unless someone wants to donate gas money, I'll be sticking around the KC area for now!

 

--

I should also probably say that I had to force into LTE. Not sure how quickly it would pick it up on it's own, may take long enough to completely miss the LTE areas.

Link to comment
Share on other sites

You're right that was me in salina. I saw the number of 4g sites changed in sensorly but didn't see the map update til you told me. I did a small part of 3g in Colby but it isn't updating the map. Weird.

 

Sent from my cm_tenderloin using Tapatalk 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

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