Jump to content

Stay Connected This Summer: Sprint 4G LTE Expands into 22 New Cities


Recommended Posts

I smell an article coming....

 

Look at your quote. Is this another example of Yabbadabbadotalk...er, I mean...Tapatalk necro quote?

 

 

:P

 

 

AJ

Hahaha.. Yep. The browser is too cumbersome on the phone to fit my A.D.D. needs.

Link to comment
Share on other sites

 

I don't know about the other maps, but the Lansing one isn't just generous on LTE. It's claiming LTE coverage in places where there is no PCS EVDO service at all (even according to Sprint's own maps).

 

 

If you flip between the two, the boundary lines for LTE claim to go out farther than Sprint's own map for voice service. It's showing LTE data coverage in places where they claim to only have voice roaming.

 

As strange as it sounds, I almost have to wonder if Sprint marketing's cartography department does not have the ability distinguish between CDMA2000 RSSI and LTE RSRP. Robert, what was the figure of merit that we saw Sprint determine for the edge of LTE coverage, -119 dBm RSRP? Could it actually be that the maps are being projected out to -119 dBm RSSI instead?

 

 

AJ

This was one of my early hypotheses when the initial coverage maps came out last summer. I believe I even built a signal map with CloudRF software that would support that as a possibility.

 

The LTE coverage map are notoriously bad and just give a really bad image to Sprint and Network Vision. If this is intentional, it's a bone headed move. I have to believe it is just an error along these lines.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

  • Like 1
Link to comment
Share on other sites

This was one of my early hypotheses when the initial coverage maps came out last summer. I believe I even built a signal map with CloudRF software that would support that as a possibility.

 

The LTE coverage map are notoriously bad and just give a really bad image to Sprint and Network Vision. If this is intentional, it's a bone headed move. I have to believe it is just an error along these lines.

 

Robert from Note 2 using Tapatalk 4 Beta

 

A very bad error indeed...I hope.  I really hope they don't base their CSR calls and even network planning for new/filler sites on this.  As there are many many areas on the map that show LTE coverage yet you'll struggle to hold 1X there.  So instead their network group says "nope, that area is covered! move along" when in reality the area needs a site very badly.  Look at the side by side comparison below.  That's a bunch of LTE coverage in a roaming 1X area! I know this site pretty well and I will say the voice coverage for this one is very close.

 

incorrect_LTE.jpg

  • Like 1
Link to comment
Share on other sites

 

A very bad error indeed...I hope. I really hope they don't base their CSR calls and even network planning for new/filler sites on this. As there are many many areas on the map that show LTE coverage yet you'll struggle to hold 1X there. So instead their network group says "nope, that area is covered! move along" when in reality the area needs a site very badly. Look at the side by side comparison below. That's a bunch of LTE coverage in a roaming 1X area! I know this site pretty well and I will say the voice coverage for this one is very close.

 

 

That's just so bad. LTE 1900 shown with greater range than 1x on 1900? Crazy. I don't even think LTE 800 is going to provide but just a small improvement over 1x voice in distance (raw coverage).

 

I think LTE 800 biggest advantage will be signal strength and usability at the edge of current CDMA coverage. I don't expect huge coverage gains on LTE 800. But I do expect pretty good coverage gains on CDMA 800.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

 

 

 

A very bad error indeed...I hope. I really hope they don't base their CSR calls and even network planning for new/filler sites on this. As there are many many areas on the map that show LTE coverage yet you'll struggle to hold 1X there. So instead their network group says "nope, that area is covered! move along" when in reality the area needs a site very badly. Look at the side by side comparison below. That's a bunch of LTE coverage in a roaming 1X area! I know this site pretty well and I will say the voice coverage for this one is very close.

 

 

 

 

That's just so bad. LTE 1900 shown with greater range than 1x on 1900? Crazy. I don't even think LTE 800 is going to provide but just a small improvement over 1x voice in distance (raw coverage).

 

 

 

I think LTE 800 biggest advantage will be signal strength and usability at the edge of current CDMA coverage. I don't expect huge coverage gains on LTE 800. But I do expect pretty good coverage gains on CDMA 800.

 

 

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

 

 

I thought LTE travelled further, but was more fragile (meaning it's more prone to suffer signal loss if there's any obstacles in the way.) You think if I have relatively no 1x signal on 1900 at work as of now, LTE 800 will not either? My signal on 1x is usually around -102dBm at work, I know CDMA 800 will help, but you're making it sound like lte 800 won't help much in my case. (Not that bad since I'll have a Clearwire site right outside my work providing LTE 2500. :D
Link to comment
Share on other sites

I thought LTE travelled further, but was more fragile (meaning it's more prone to suffer signal loss if there's any obstacles in the way.) You think if I have relatively no 1x signal on 1900 at work as of now, LTE 800 will not either? My signal on 1x is usually around -102dBm at work, I know CDMA 800 will help, but you're making it sound like lte 800 won't help much in my case. (Not that bad since I'll have a Clearwire site right outside my work providing LTE 2500. :D

 

In the same exact deployment and all things being equal...1x and LTE on the same frequency will be practically the same signal strength in the same conditions.  The difference being that LTE will not be usable beyond approximately -93dBm and -95dBm RSSI, and 1x will be usable up to -103dBm to -107dBm.  And that is a huge difference when indoors or nearing the edge of service.  LTE does not travel further than 1x, no matter how you define it.  You may be confusing that LTE travels further than WiMax, being that WiMax maxed out around -83dBm to -85dBm and LTE maxes out around 10dBm weaker.

 

I don't believe that LTE 800 will travel much farther than CDMA 1900.  It will some, but not a lot.  There will be a significant difference between CDMA 800 and CDMA 1900, though.

 

Robert

  • Like 1
Link to comment
Share on other sites

This was one of my early hypotheses when the initial coverage maps came out last summer. I believe I even built a signal map with CloudRF software that would support that as a possibility.

 

The LTE coverage map are notoriously bad and just give a really bad image to Sprint and Network Vision. If this is intentional, it's a bone headed move. I have to believe it is just an error along these lines.

 

Robert from Note 2 using Tapatalk 4 Beta

 

If it's really an "error", wouldn't they have noticed it by now?

How many complaints before they seriously take a look at the coverage maps?

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

    • 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.
    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
  • Recently Browsing

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