Jump to content

Network Vision/LTE - Albuquerque market (including El Paso, Las Cruces, Santa Fe, Los Alamos, Roswell)


S4GRU

Recommended Posts

Also, 165 ping 2.53 down and .7 up. I am inside a warehouse, North of Paseo and West of Washington. Things are really getting better.

I was just in that area at Yearout Mechanical's office in September and my Sprint 3G data kept timing out. So that was a pretty bad area. A much needed improvement. I couldn't get a Tmo signal inside the building at all. AT&T LTE was unusable. I had to use my VZW hotspot. :(

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

I was just in that area at Yearout Mechanical's office in September and my Sprint 3G data kept timing out. So that was a pretty bad area. A much needed improvement. I couldn't get a Tmo signal inside the building at all. AT&T LTE was unusable. I had to use my VZW hotspot. :(

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

You too!

 

https://www.dropbox.com/s/wd6f7etkba5tcrf/Photo%20Jan%2001%2C%2011%2009%2042%20AM.png

 

So the link is the speed test at Dillard's at i40 and Louisiana. I can't believe that I got 105 ping with as many people that are here. Speed wasnot outstanding. However I was pulling we pages just fine.

Link to comment
Share on other sites

You too!

 

https://www.dropbox.com/s/wd6f7etkba5tcrf/Photo%20Jan%2001%2C%2011%2009%2042%20AM.png

 

So the link is the speed test at Dillard's at i40 and Louisiana. I can't believe that I got 105 ping with as many people that are here. Speed wasnot outstanding. However I was pulling we pages just fine.

With that kind of ping, things that only use small amounts of data will feel very fast. That could just be a provisioning problem at the switch. I don't recall ever seeing a ping that low with a speed that low before. :fingers:

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 1
Link to comment
Share on other sites

With that kind of ping, things that only use small amounts of data will feel very fast. That could just be a provisioning problem at the switch. I don't recall ever seeing a ping that low with a speed that low before. :fingers:

 

Robert via Samsung Note 8.0 using Tapatalk Pro

I would have to agree.  Interesting was that I took the screen shot on my phone and I was able to upload the picture over 3G. 

  • Like 1
Link to comment
Share on other sites

I would have to agree. Interesting was that I took the screen shot on my phone and I was able to upload the picture over 3G.

Did you try a few servers? It could have actually just been a server problem causing slower throughput.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

Did you try a few servers? It could have actually just been a server problem causing slower throughput.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

I was in the same Dillard's yesterday (unfortunately) and was getting horrible service.  However, not joke, the sheer number of people there was frightening and I suppose the nearest switch could have been a little overwhelmed.  I nearly jumped for joy when my girlfriend agreed, it wasn't worth the efforts to be in that store on that day and we left.

Link to comment
Share on other sites

I was in the same Dillard's yesterday (unfortunately) and was getting horrible service. However, not joke, the sheer number of people there was frightening and I suppose the nearest switch could have been a little overwhelmed. I nearly jumped for joy when my girlfriend agreed, it wasn't worth the efforts to be in that store on that day and we left.

I was patiently waiting in the car.
  • Like 1
Link to comment
Share on other sites

Well I'm wondering what's up there, because I was at the tower on Juan Tabo on the south side of I-40 and got 1.91/0.96 with a ping of 104. I have noticed almost everywhere I'm at that hasn't been upgraded, I'm guessing, I have been getting upload speeds 2X as fast as download.

That's the weird thing - once I get near I-40, the speed shoots up to at least reasonable, but near Central and south of Central it plummets to intolerably slow.

 

 

Sent from my iPad using Tapatalk

  • Like 1
Link to comment
Share on other sites

My speeds are back in the toilet. Calls not going through, network communication issues and so on. Been having this problem from north of Paseo to south of Central. Come on Sprint.

I wouldn't worry too much. This up and down happened in most markets right before they were about to launch lte.

 

Sent from my Nexus 5

 

 

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