Jump to content

RAvirani

S4GRU Staff
  • Posts

    3,455
  • Joined

  • Last visited

  • Days Won

    159

Everything posted by RAvirani

  1. Thank you Mike! One more feature request—could you distinguish between LTE AWS and LTE AWS-3? AWS-3 is for B66 center frequencies above 2155/1755 MHz (EARFCN 66886).
  2. Totally missed his message - thanks @Dkoellerwx. I've seen it spelled both ways. I think officially it's DISH, but I don't have a strong opinion either way.
  3. When I think of Dish, I think of Genesis. I don’t think Boost is the brand that will grow because of its existing cheap/non-premium reputation.
  4. Sounds good! Can’t wait for this one!!! Ohhh. I misunderstood the display. What’s the denotation for second carrier? We could do orange for the time being, but I think gradients would be really cool for non-big-three carriers. I’d use red/blue for USCC and green/purple for Dish. It would also be useful internationally. For example, TELUS in Canada is also green and purple.
  5. Alternate idea—maybe gradients could be added? USCC is really red/blue and Dish is really green/purple. That could be a good-looking and functional solution…
  6. Just downloaded the new update and it looks like Dish is working! I notice the ECI calculation is wrong—I sent you a PM about how we’re assigning these because of the virtualized setup. The only other thing I’ve noticed so far is that there are bugs in the second carrier identification. If both SIMs are connected to the same sector, the second SIM displays that it’s connected to the second carrier like so: If an NSA component is present on the second SIM, it also mistakenly shows as a second carrier like so: Also, I noticed you made the Dish indicator red. Would it be possible to change it to a different color to more easily distinguish between it and VZW? Since Dish is selling service under the Project Genesis brand, maybe green? https://launch.5gmobilegenesis.com Thanks for all your hard work on this update!
  7. If they’re meeting KPI targets in the area this is very possible. Verizon left most of Clyde Hill and Medina uncovered for the longest time for the same reason. I doubt this. That’s definitely a demolition permit. Could be a sector add or reconfig. I hope it’s the latter, because that area’s modulation/CQI is already more or less in the toilet (table 2 sub-6 CQIs with efficiency oftentimes <2). I’ll do some digging and see what I can find.
  8. Hmm - not actually sure. The surrounding sites' sector configs look like they were selected with the intention of building that site, and RSRP levels don't look amazing... RSRP:
  9. I think that would be a good change. A standard highway speed of 65 miles per hour is 95.3 feet per second. At three seconds between updates, that's one data point every 286 feet (or more). Another way to think about this is your device will only record 18 points (at best) for every mile you drive on the highway. This still seems pretty sparse to me, but it's a step in the right direction. At one second between updates, you'd record a data point every 95.3 feet. This is equivalent to 55 data points for every mile you drive on the highway. Much better in my opinion.
  10. The location update interval may also play into this. I think it defaults to four seconds but I’ve changed it to one second on all my devices. @mikejeep would it make sense to change the default location accuracy to high and the default update interval to one second? That might eliminate out-of-the-box issues for a lot of users…
  11. I run SCP on an S22 frequently and have no mapping issues; that being said, I always leave the app open while driving. My guess is the multitasking caused the poor quality, but Mike might have a better answer.
  12. Ooh what are these? Dish provisions devices with virtual dual SIM (with DDS) that used AT&T LTE as primary and Dish 5G as secondary. Since SCP doesn’t support dual SIM, I’ve been doing Dish drive testing on CellMapper and more recently my own barebones Android app; but I would like to switch over to SCP if possible… By the way, sent you a DM about Dish NCIs and how we’re assigning them.
  13. In all but a couple rooms, I get reliable mmWave on my Verizon device inside my place in Houston 🤔.
  14. Looks like a Cloudflare problem Working on it…
  15. Can someone having the error go to the website, log in, click on your name in the top right corner, and check if there are any devices added to your account?
  16. I always disliked that site. Its coverage area is too large and it’s easily overloaded. Hopefully they convert the Clear site on 90th by Bella Botega and pull in the range of that powerline site with etilt. That would lower the noise floor in the whole downtown area and add some much needed capacity. A few years back, T-Mobile had a site right next to Bella Botega, but it was decommissioned due to a construction project. I don’t know why they never rebuilt in that location—especially because the decom was a good bit before the merger. Funnily enough, the building that caused the T-Mobile decommission ended up hosting AT&T eNB 421549.
  17. I cleared a bunch of stuff out of my imgur…I can remake propagation maps if desired.
  18. I’ve heard a lot of the Nokia AEHCs are defective and that they’re causing a lot of delays.
  19. Devices are provisioned with dual SIM+DDS, so it’s pretty seamless.
  20. Very interesting—I see the data in my DB, but the map is rejecting it. The map doesn’t display signals worse than -118, so some of the missing data makes sense, but it looks like there are some stronger data points that are missing as well. I’ll have to investigate what’s going on there… https://imgur.com/a/IgHY90f
  21. I’m at the US Open in Flushing Meadows right now and the T-Mobile service is horrendous. My phone is bouncing between unusable NR, unusable LTE and no service. Looks like they’re trying to make use of DTX/DRX/short inactivity timer/etc but I’m getting more RRC connection failures than successes. My phone has dropped down to no service for extended periods of time despite T300 being set to only a couple seconds as well Meanwhile, AT&T and Verizon are both delivering 100+ Mbps .
×
×
  • Create New...