Jump to content

Network Vision/LTE - Kansas Market (including KC, Topeka, Wichita, St. Joseph)


Rickie546

Recommended Posts

24c5edu.png

 

2wdpkwi.png

 

AJ

  • Like 3
Link to comment
Share on other sites

These are only a very few isolated, individual live LTE sites, which may or may not be at their final power levels. So, in building coverage is not a relevant question right now. Wait for the market launch, then even a few months later for all sites to come online before judging coverage footprint and quality. Regardless, since CDMA1X, EV-DO, and LTE will all be deployed in PCS 1900 MHz spectrum, in building coverage should be similar among the three.

 

AJ

Link to comment
Share on other sites

I will have to drive to this area on Wednesday. I will be in that area and will have to test out the 4G LTE airwaves! I will have to do some screen shots and post them up here on my shiny new EVO 4G LTE.

Link to comment
Share on other sites

how's the in building coverage?

 

The speed test shown is inside a building. For the last few weeks, LTE would only work for a few hours out of the day, and now it seems to work all day on this particular site. Hopefully a full blown launch in KC is around the corner. I hope anyway.

  • Like 1
Link to comment
Share on other sites

Heard that the go live date of LTE is in July for Kansas City.

 

FWIW: my source does not work for the company but has some good contacts.

Link to comment
Share on other sites

Heard that the go live date of LTE is in July for Kansas City.

 

FWIW: my source does not work for the company but has some good contacts.

 

Will have to see

 

Sent from my 1/2 G EVO

Link to comment
Share on other sites

I have now heard this rumor from two sources, but nothing in a written document. This is consistent with our article: http://s4gru.com/index.php?/blog/1/entry-265-kansas-network-visionlte-deployment-schedule-update/

 

I've also heard the same rumor about Atlanta too. But I have not received any confirmation of that one, at all.

 

Robert

Link to comment
Share on other sites

Any contacts within HTC regarding the EVO LTE data bug? Do we still suspect that is the hold up or something more?

 

I believe this is the hold up. However, I have no new information other than anecdotal evidence from our members.

 

Robert

Link to comment
Share on other sites

What is the EVO 4G LTE data bug?

 

We reported that in lab testing, the EVO LTE had a connectivity issue with the LTE network. They did not have it worked out before they shipped the device. We believe that an OTA is coming soon to fix the issue, and Sprint is blocking LTE connections to prevent the issue from becoming known.

 

We already had a member who ran the EVO LTE and Galaxy Nexus side by side for a day or so when connected to Sprint 4G LTE in Atlanta. At first, the EVO LTE had no issues and actually performed better than the GNex. But after a few hours, the EVO LTE would not connect to LTE at all. It was almost like the LTE signal was not there anymore. However, his GNex could connect to the LTE still and ran just fine. He tried rebooting, cycling through airplane mode, LTE mode, etc. but could not get the EVO LTE back on the LTE network. The GNex was unaffected and continued to connect and run fast on Sprint LTE.

 

Later, on its own, the EVO LTE came back and connected to the LTE network again...but several hours later. Our member would have had no idea there was an issue with the EVO had he not also owned a GNex. He would have assumed that the tower was just taken down or blocked during the period where the EVO LTE did not get a signal. So we are taking this episode (and another one reported) as anecdotal evidence in support of the LTE Connectivity issue we reported.

 

I don't think we will see Sprint stop LTE blocking until they can fix the problem with the LTE Connectivity issue. Hopefully, Sprint/HTC can issue a fix soon.

 

Robert

  • Like 2
Link to comment
Share on other sites

We reported that in lab testing, the EVO LTE had a connectivity issue with the LTE network. They did not have it worked out before they shipped the device. We believe that an OTA is coming soon to fix the issue, and Sprint is blocking LTE connections to prevent the issue from becoming known.

 

We already had a member who ran the EVO LTE and Galaxy Nexus side by side for a day or so when connected to Sprint 4G LTE in Atlanta. At first, the EVO LTE had no issues and actually performed better than the GNex. But after a few hours, the EVO LTE would not connect to LTE at all. It was almost like the LTE signal was not there anymore. However, his GNex could connect to the LTE still and ran just fine. He tried rebooting, cycling through airplane mode, LTE mode, etc. but could not get the EVO LTE back on the LTE network. The GNex was unaffected and continued to connect and run fast on Sprint LTE.

 

Later, on its own, the EVO LTE came back and connected to the LTE network again...but several hours later. Our member would have had no idea there was an issue with the EVO had he not also owned a GNex. He would have assumed that the tower was just taken down or blocked during the period where the EVO LTE did not get a signal. So we are taking this episode (and another one reported) as anecdotal evidence in support of the LTE Connectivity issue we reported.

 

I don't think we will see Sprint stop LTE blocking until they can fix the problem with the LTE Connectivity issue. Hopefully, Sprint/HTC can issue a fix soon.

 

Robert

 

Thanks for the Info!!

  • Like 1
Link to comment
Share on other sites

I live nearby K7 & 95th Street area in KC area and have seen LTE on my phone since Monday but disappears after an hour or so. Then I go to sleep in the evenings with 3G and wake up to 4G data signal and have run several speed checks and averaging around 4-5Mbps. I have seen many other parts of KC that my 4Gindicator will magically appear. I just thought I would mention this and inform folks that 4G is probably go live soon in the KC zone as I keep getting a lot of non-blocked towers that appear while I am driving along in the Kansas City market. Just my $0.02.

 

Patrick

  • Like 1
Link to comment
Share on other sites

I went on a nerd-quest last night around 9:30 pm to 135th and Switzer, where kckid reported getting LTE signals, and nothing... nothing but a really strong 3G signal!! I live by WOF in a 60-year-old neighborhood, and I know that Network Vision is working in our part of town, but still no LTE of course north of the Missouri River or Downtown (where I work) yet. At this rate, I'm really starting to miss WiMax....

 

J.

Link to comment
Share on other sites

I went on a nerd-quest last night around 9:30 pm to 135th and Switzer, where kckid reported getting LTE signals, and nothing... nothing but a really strong 3G signal!! I live by WOF in a 60-year-old neighborhood, and I know that Network Vision is working in our part of town, but still no LTE of course north of the Missouri River or Downtown (where I work) yet. At this rate, I'm really starting to miss WiMax....

 

J.

 

I did the same thing on Sunday with no luck on getting LTE. I started at the tower in Blackbob Park and head up 35 to Shawnee Mission Parkway.

 

I live in the 135 and Switzer area, but haven't got an LTE signal yet. I've only had my phone for a few days though. I'll keep checking on it.

Link to comment
Share on other sites

  • 2 weeks later...

Can any other KC area members confirm that eHRPD is down today Monday 6/04? Only NID 00041 (KC-LENEXA-MSC_1) and NID 00042 (KC-LENEXA-MSC_2) seem to be affected. eHRPD is restored upon crossing back over to NID 00043 (KC-INDEPENDENCE-MSC_1).

 

AJ

 

New here, from Lenexa, I've never checked before, but I do not see any eHRPD, only EvdoA. Although I have an EVO 3D at the moment, waiting on my EVO LTE. I do not know if that would make a difference?

 

Edit: I just realized this is from a month ago, so maybe not relavent any more.

Edited by Dkoellerwx
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...