Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Fury Gran Coupe (My First Car - What a Boat...)
  3. Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed. Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna. Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago). Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area. Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
  4. Mike if you need more Dish data, I have been hunting down sites in western Columbus. So far just n70 and n71 reporting although I CA all three.
  5. Last week
  6. Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  7. At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
  8. Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
  9. Drove out into the country today. Dish stuck to my phone like glue. At least -120 rsrp. Likely only good for phone calls (should have tested.) It then switched to T-Mobile. Getting back on Dish was another issue. I am used to dragging out coverage so I expected a few miles, but had to drive at least 10 miles towards a Dish site. Airplane mode, which worked for Sprint, did nothing. Rebooting did nothing. Finally got it to change over about 2 miles from the site by manually setting the carrier to Dish then it had great reception. Sprint used to have a 15 minute timeout but I did not have the patience today. Previously I did a speed test on Dish out in the country at the edge of Dish coverage. My speeds were 2g variety. Dish has really overclocked some of these sites. Seen rssp readings in the 50s. Would have called them boomer sites with Sprint but much more common with Dish.
  10. Drove from Omaha to KC this weekend. There were a number of n41 sites that previously only had 50 or 50+20Mhz on air and didn't allow for the n41 channel to be the primary channel on SA NR. As of this past weekend (probably sometime last month) all of them had 100 + at least 40Mhz of n41 and had n41 as the primary channel. A couple of them had 100+90. The network in KC was also increased to 100+90 since the last time I was here, giving a total of 15 n71, 20 + 5 n25, 100 + 90 n41. Pulled 1.2Gbps on a random site at 5pm Saturday afternoon.
  11. New T-Mobile site went live earlier this year at 5 W 86th St, just off of Central Park. It's not a Sprint conversion so I hope this means more new builds are gonna stop popping up in areas that need coverage the most. — — — — — Also spotted a unicorn (mapped a new AT&T site) in Greenpoint. It's eNB ID 115932/119932. I spotted the permit a super long time ago but it looks like it finally went live earlier this month. That makes 5 new AT&T sites in Brooklyn in the past 2 years. — — — — — Noticed that I touched a Sprint conversion site while mapping today. It has been live since at least December and is already on the keep site map. Sprint eNB 74215 -> T-Mobile gNB 1371628 Located at: 40.767977371545726, -73.96146218469505 Still a bunch more we've found that don't have any decommission permits submitted yet. — — — — — Adding a bunch of gig+ sites I haven't reported yet. eNB 44076 Located at 40.72513188568983, -73.95130108843207 eNB 44110 Located at 40.78671665921442, -73.97831748836762 eNB 47002 Located at 40.71818871096234, -73.97553242675835 eNB 48023 Located at 40.70014576627346, -73.95511802661758 eNB 129912/130917 Located at 40.71727220756978, -73.95652417532955 eNB 875917 Located at 40.72274052431834, -73.84403351784677 eNB 49849 Located at 40.72181611705532, -73.86627810663067
  12. Here in NYC I don’t think NextWave even has any clients. By my count they only have about two dozen sites deployed across the entire city. It’s pretty much a network only put up to try to pressure T-Mobile into buying them by forcing T-Mobile to switch their n41 configuration from 140MHz to 80MHz over a growing portion of the city. That’s not competitive with Verizon who has 160MHz citywide. I hope we get to the point soon where T-Mobile decides it’s worth it to just buy out NextWave, take over their leases, and finally have a full 190MHz across the city.
  13. Anyone ever try any of these companies in this article? https://www.lightreading.com/5g/redzone-nextwave-also-complain-of-interference-from-t-mobile-s-5g
  14. Earlier
  15. Doubt anyone outside of Colorado would care much. And unless he shows improvement over the entire season in year 2 the Colorado contingent might slide over into the 'could care less' column too.
  16. Finally got a rainbow sim after about a year of occassionally trying. N70, n71, and n66 working on byod s24 ultra. Speed around 550Mbps down, 40 up during rush hour: https://imgur.com/a/ENhnSI2
  1. Load more activity
×
×
  • Create New...