Jump to content

Network Vision/LTE - New York City Market


Ace41690

Recommended Posts

I've been away for a long time but this band-forcing thing you guys speak of, is it possible for those of us with iPhones to do it? and, is Band 26 actually active yet?

In NYC no. But it's due to lack of Alcatel-Lucent carrier cards. We should start seeing 800LTE sites before summer though.

Link to comment
Share on other sites

Long time lurker. I luckily live in a fantastic LTE (even Wimax) area in East Harlem. Have perfect band 41 and can pull 50+Mbps.

 

Problem started once they flipped band 25 on a few weeks ago and I can't seem to hang onto the band 41 connection. At best I can stay connect for a few minutes before it falls back to band 25. I've tried every different priority mode in LTE engineering settings but to no avail. Is this likely a phone software problem or a tower issue? Any thoughts?

I assume you're on the G2. Have you received the Spark update, yet?

 

Robert via Samsung Note 8.0 using Tapatalk Pro

 

 

Link to comment
Share on other sites

Connected to B41 on 42nd and 8th ave, seemed to be older backhaul. Still beat the pants out of B25, got 1mb down on B25 and 10mb down 15 up on B41.

I've noticed that pings on B41 are generally slower than the pings on B25. Have you noticed a difference?

 

Wifi always feels a little more responsive than LTE (B25) to me, even with slower DL speeds, although it's only a slight difference. And both are noticeably faster than EVDO at similar DL speeds.

  • Like 1
Link to comment
Share on other sites

Connected to B41 on 42nd and 8th ave, seemed to be older backhaul. Still beat the pants out of B25, got 1mb down on B25 and 10mb down 15 up on B41.

 

Yeah, in Denver, only about 1/3 pf the Band 41 sites had upgraded backhaul.  I think it's why they have not announced that market.  Well, I say that, but CSFB is probably the biggest reason why they have not announced Spark in Denver.

 

Robert

  • Like 1
Link to comment
Share on other sites

I've noticed that pings on B41 are generally slower than the pings on B25. Have you noticed a difference?

 

Wifi always feels a little more responsive than LTE (B25) to me, even with slower DL speeds, although it's only a slight difference. And both are noticeably faster than EVDO at similar DL speeds.

I would say its generally on par with B25, but it is hard to say since I cannot connect to B41 automatically. What i can say is that even with a worse than -100dBm signal, it blows B25 out of the water.

Link to comment
Share on other sites

Yeah, in Denver, only about 1/3 pf the Band 41 sites had upgraded backhaul.  I think it's why they have not announced that market.  Well, I say that, but CSFB is probably the biggest reason why they have not announced Spark in Denver.

 

Robert

I do find it odd that when the backhaul isnt upgraded, that the upload performance is almost always well past the download performance.

  • Like 1
Link to comment
Share on other sites

Once you have the update, your phone should stay nice and clean on B41.

 

My fingers are crossed. It hurts going from over 50Mbps on band 41 to 3Mbps on band 25. Just hope it's not designed to only fallback on 41.

Edited by IHeartLTE
Link to comment
Share on other sites

My fingers are crossed. It hurts going from over 50Mbps on band 41 to 3Mbps on band 25. Just hope it's not designed to only fallback on 41.

If you have a decent ping, you shouldn't really see a difference between 41 and 3 mb down if you're just doing normal phone activities. Unless your downloading files or something. But b41 is definitely tasty

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Link to comment
Share on other sites

Just got my ZVA update on my LG LS980 (LG G2). Around 9:30 PM EDT and couldn't be happier the speeds are blazing fast! file:///storage/emulated/0/Android/data/.cliptray/1391669071869.jpg

Good to hear and welcome....just cant see the pic, Its pointing to a local folder on your android device.

Link to comment
Share on other sites

It usually stays on 41 but if you are inside a building because band 41 doesnt perform well "in building prenetation". Then for now it will search back for band 25 1900 Mhz but as NV progress band 26 should be the band that we all fall back when 41 is out of reach and not band 25.

Link to comment
Share on other sites

It usually stays on 41 but if you are inside a building because band 41 doesnt perform well "in building prenetation". Then for now it will search back for band 25 1900 Mhz but as NV progress band 26 should be the band that we all fall back when 41 is out of reach and not band 25.

For now it looks like sprint is going with 41-25-26, it does make sense, since 26 should be the last stop when signal is not strong enough on 25. But I could see where having 26 first before 25 would make sense in overpopulated areas.

Link to comment
Share on other sites

The band priority for now is 25 (1900MHZ), band 26 (800MHZ), and band 41 (2500GHZ). But that will soon change as they deploy more small cell and increment the capacity using carrier aggregation. Givin the fact that Sprint currently has deployed more cell sites on the 1900MHZ spectrum I can understand why the band priority is with band 25 for now. But they will soon push future updates changing those specs yet again. Because band 25 is only built for now on a 5mhz pipe of spectrum. And that is tge main reason why Sprint lags behind competitors on not only coverage but speed. Capacity wise is not there yet, most carriers use 10mhz of dedicated spectrum for their LTE deployment but Sprint chose to go with 5mhz.

Link to comment
Share on other sites

There, I had to crop the picture...

 

Damn these new Spark speeds are coming alive.  T-Mobile's CEO speed test bash been so quiet lately..

Link to comment
Share on other sites

Connected to B41 on 42nd and 8th ave, seemed to be older backhaul. Still beat the pants out of B25, got 1mb down on B25 and 10mb down 15 up on B41.

 

Interesting, I wasn't able to see B41 at Port Authority this morning.

Link to comment
Share on other sites

My fingers are crossed. It hurts going from over 50Mbps on band 41 to 3Mbps on band 25. Just hope it's not designed to only fallback on 41.

 

The network hands up and down.

 

So when you're walking down the block, and your device idles, the network will push to B41 if available. Once you keep walking out of range, your device will push down to B25.

Link to comment
Share on other sites

Interesting, I wasn't able to see B41 at Port Authority this morning.

I walked up and down between 9th ave and 7th ave on 42nd street and held a decent connection ranging from -77dBm to -99dBm even indoors at a restaurant. But the second I turned the corner on 7th ave heading north, it was gone.

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

    • My S24 Ultra and my two S22s are uploading and working properly today, as another data point. 
    • My hope is they can spot something in the data that was exported. I am going after all 4 carriers on a multitude of phones and Android versions. My S24 did work.  I have not checked another S24 or S22.  S21s failed which are on Android 14 as well. It should be noted I did not reboot after updates and some of the data was captured on the prior update. Data from some new Boost Mobile Dish (Echostar) sites in the Wheeling area did make it in. Was hoping for more SA data from the duo. Many of the phones are just LTE.
    • I was traveling for a couple of days.   Sunday evening, I upload from 3 phones.  A S-22 and two Moto 5G phones.  Everything looked ok.    How do we explain that?   One person has issues and another person does not.  All my phones have the latest update.
    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • 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!
  • Recently Browsing

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