Jump to content

Network Vision/LTE - Las Vegas Market


Timbax

Recommended Posts

Seems like it's already a reality...

 

attachicon.gif 2015-10-26 11.57.29.png

 

 

Sent from my SM-N920P using Tapatalk

What area in town is that? I was at Buffalo and Summerlin Pkwy.

 

 

Sent from my Gold iPhone 6s Plus 128GB using Tapatalk

Link to comment
Share on other sites

  • 2 months later...

Was in Vegas this week staying at MGM. Saw a lot of band 25 & 41. Convention center at MGM I think has a DAS as I had strong signal there. Casino has decent band 25 coverage but did see 3G several times.

 

The network at the convention center was great, B41 all the way and speeds were great. The Sands convention center needs support of LTE and my guess the hotel wasn't upgraded much either. I had a solid signal on the -3rd level parking garage but mostly 3G. Casino was LTE but in some areas, more at the back of the convention center, you got at best 3G. LTE speeds were also not very impressive. Again, LVCC showed major improvement but could use a bit more capacity too!

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

Damn, and without band 26. I haven't been there in a year, but when I was, my phone was a brick in most hotels on the strip. According to this report, they only tested in 24 indoor locations? Unless you live there, the only relevant part of town is the strip. I think rootmetrics should have a separate report for the strip.

 

 

Sent from my iPhone 6s

Link to comment
Share on other sites

Damn, and without band 26. I haven't been there in a year, but when I was, my phone was a brick in most hotels on the strip. According to this report, they only tested in 24 indoor locations? Unless you live there, the only relevant part of town is the strip. I think rootmetrics should have a separate report for the strip.

 

 

Sent from my iPhone 6s

 

I'm not sure you understand the absurdity of what you're thinking.  so you want rootmetrics should have a report for every major attraction in every city?  Michigan ave and downtown for chicago?  the theme parks in orlando? times square and central park for new york? etc... 

 

should we mark the states into counties and divides the cities into population density per square miles and test which carrier serves best too? What else?? hmmm

Link to comment
Share on other sites

According to this report, they only tested in 24 indoor locations? Unless you live there, the only relevant part of town is the strip. I think rootmetrics should have a separate report for the strip.

 

I am not sure that the casinos on The Strip would allow RootMetrics to waltz in with its multi handset test gear.  The casinos want people gambling, not talking and idling time on their cellphones.  There are business reasons why casinos tend to be daylight and RF black holes.

 

AJ

  • Like 1
Link to comment
Share on other sites

I'm not sure you understand the absurdity of what you're thinking. so you want rootmetrics should have a report for every major attraction in every city? Michigan ave and downtown for chicago? the theme parks in orlando? times square and central park for new york? etc...

 

should we mark the states into counties and divides the cities into population density per square miles and test which carrier serves best too? What else?? hmmm

I'm just saying that with 24 indoor locations tested, the strip wasn't likely touched, save for a car ride down LVB.

 

 

Sent from my iPhone 6s

Link to comment
Share on other sites

Interesting, I wasn't aware of that. I thought small cells on the Strip was coming as part of NGN.

 

You see on directy in front of the Linq (in the center of the road), same at the MGM/NYNY.

 

 

I travel there a lot for work. While I get great coverage outside half the time I get 3G or little service in some casinos on the strip. But coverage has improved.

 

The Casinos have their own DAS systems in place and most of them are still not LTE

Link to comment
Share on other sites

You see on directy in front of the Linq (in the center of the road), same at the MGM/NYNY.

 

 

 

The Casinos have their own DAS systems in place and most of them are still not LTE

 

I'll take a look the next time I go to Vegas.

Link to comment
Share on other sites

  • 1 month later...

Just got back from the strip. Very hit or miss. Sls was bad. Fremont street was not very good either. But I was sitting in front of NYNY outside patio at Tom's urban diner and my att friend asked if had any data cause his phone was useless. And I looked up whatever he needed just fine. So there's that. Bellagio was good.

 

Sent from my SM-G935P using Tapatalk

Link to comment
Share on other sites

How is the service in Vegas? Is it good LTE and Voice services?

Outside of the The Strip and the downtown hotels, voice is great, and data is getting better. Just not ubiquitous Band 41 coverage yet.

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

    • 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!
    • Oct security update is out.
    • 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.
  • Recently Browsing

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