RAvirani

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 hours ago, mikejeep said:

As dkoellerwx eloquently mentioned, a second carrier would show as DISH Wireless B30². 

Totally missed his message - thanks @Dkoellerwx.

2 hours ago, mikejeep said:

While we are on the subject -- should DISH be capitalized, or no?

I've seen it spelled both ways.  I think officially it's DISH, but I don't have a strong opinion either way.

3 hours ago, Trip said:

Is Dish really green/purple?  I know Genesis is, but aren't they going to be selling their service to the general public under the Boost Unlimited brand, which appears to share the orange theme of Boost Mobile?

- Trip

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. 

21 minutes ago, mikejeep said:

I have the Dish info you sent me, but I haven't implemented any of it yet -- what you are seeing is the app's standard interpretation of cell information. It's on the to-do list!

Sounds good! Can’t wait for this one!!!

22 minutes ago, mikejeep said:

Not sure what you mean here..? By 'carrier' do you mean the second provider? The [2] indicates information coming from the secondary SIM. Without that indicator means the information is coming from the primary SIM.

Ohhh. I misunderstood the display. What’s the denotation for second carrier?

25 minutes ago, mikejeep said:

I went with that shade of red to match the Dish Wireless logo -- but I can change it easily. If we want to differentiate between the major providers, should we go with orange for the Boost connection? I could explore implementing gradients too.. then we could get real crazy.. not sure how tricky that will be, but I'll give it a shot.

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. 

1 hour ago, Trip said:

Green is used for US Cellular because its blue color is a very similar blue to AT&T.  What about an orange color like Boost Mobile uses?

- Trip

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…

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!

On 1/5/2023 at 1:33 PM, PedroDaGr8 said:

Wow, I love those images! 

My only thoughts are

1. They just don't care about that area for some reason. 

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. 

On 1/5/2023 at 1:33 PM, PedroDaGr8 said:

2. This is a formality that is for some reason required due to the level of changes they are doing. 

I doubt this. That’s definitely a demolition permit. 

On 1/5/2023 at 1:33 PM, PedroDaGr8 said:

3. It has something to do with [this permit](https://permitsearch.mybuildingpermit.com/PermitDetails/PUB22-08613/Kirkland) which mentions servicing the the Kirkland Urban site. There are no other permits 

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 hours ago, PedroDaGr8 said:

1. This one is weird, the Sprint site by 85th and I-405 which T-Mobile previously was going to convert now has a Demo permit. Not sure if they cancelled the conversion or what (@RAvirani any thoughts?): Permit

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:

View post on imgur.com

SignalCheck data:

View post on imgur.com

29 minutes ago, mikejeep said:

The current default is 4 seconds, but I'm willing to change it to 3, that seems like it is still a reasonable balance of power/accuracy that should not have a huge impact. I've always changed my own devices to 3. This default will only impact new installs and installs where the user never adjusted their settings.

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.

5 hours ago, mikejeep said:

However, the other possibility might be that she didn't have at least moderate GPS accuracy during the trip. The app may have been humming along and recording all the data points in the trail log, but they are not uploaded to the map unless the accuracy of the point was 75 meters or better. If you have a navigation app running or set the SCP Location Service priority to high accuracy (which will use more battery), you won't have a problem. I probably have usable accuracy outdoors on the balanced setting approximately 85% of the time, but that can vary widely based on device/terrain/signal/wifi/movement/etc.

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…

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. 

On 12/27/2022 at 8:46 AM, mikejeep said:

A new SignalCheck beta is rolling out now.. bugfixes for Dish Wireless, pending web count display, and n2/n25 identification improvements.

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.

3 hours ago, 4GHoward said:

Coming soon..

https://www.fiercewireless.com/tech/pivotal-lights-5g-mmwave-fwa-houston

 

In all but a couple rooms, I get reliable mmWave on my Verizon device inside my place in Houston 🤔. 

@mikejeep ^

Should be resolved.

Looks like a Cloudflare problem  

Working on it…

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?

19 hours ago, PedroDaGr8 said:

The powerline tower overlooking downtown Redmond has FINALLY been upgraded. I guess it took this long due to the large birds nest on top of the tower. During the upgrade, they moved all LTE frequencies including B41 to one eNB 84782 and decommissioned eNBs 97521 and 95988. Additionally, the tower finally has all three 5G-SA bands (gNB 1852420). 

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.

10 hours ago, xmx1024 said:

Is there anything we can do as a community to keep images/attachments like these from disappearing?

I cleared a bunch of stuff out of my imgur…I can remake propagation maps if desired. 

On 11/12/2022 at 5:50 PM, PedroDaGr8 said:

@RAvirani

It looks like they listened to you and shut off the site by the Totem Lake McDonalds.

Added a bit of etilt to lower the noise floor, too. 

13 hours ago, xmx1024 said:

This one seems to be an upgrade
 

Also, it's been a while since I have been up there but I am having trouble locating it on Google Maps street view. The only site visible appears to be an AT&T site due to the raycap visible just above the fence line & gate signage.

https://www.google.com/maps/place/16001+124th+Ave+NE,+Woodinville,+WA+98072/@47.7437861,-122.1749942,3a,19.2y,224.2h,80.66t/data=!3m6!1e1!3m4!1sT9h59Sj7l0YRZH8PxCBWqA!2e0!7i16384!8i8192!4m5!3m4!1s0x54900dda6f2be3cb:0x31061dfdc68aa722!8m2!3d47.7438019!4d-122.1753217


 

This is an AT&T site. WA#### is the AT&T Common ID format. 

On 10/10/2022 at 2:05 PM, mdob07 said:

I don't know if T-Mobile pays the tower crews by the hour or what. A crew has been working on adding 2500 gear to a site that already has everything else upgraded, and they've been working on it for 2.5 weeks. Verizon is doing complete rip and replaces in 2-3 days and I've seen new Dish installs going up in less than a day. T-Mobile work seems to take longer than work for the other carriers around here for some reason. Couldn't ask for better weather for this time of year either. 

I’ve heard a lot of the Nokia AEHCs are defective and that they’re causing a lot of delays. 

21 minutes ago, red_dog007 said:

Hopefully once I start using their network the transition to their roaming partners is seamless. 

Devices are provisioned with dual SIM+DDS, so it’s pretty seamless. 

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

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 .