Leaderboard

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!

Hey Mike—I’ve got a lot of professional experience with this sort of stuff. I’d be happy to help. Feel free to shoot me a PM and we can discuss further!

I posted this in the Nebraska Premier thread last week, but just wanted to share in this thread the progress that T-Mobile has made in filling in the great coverage gap known as Nebraska. Between late last year and this year, they have added 28 new expansion sites filling in the coverage hole, plus 11 Sprint site conversions in eastern Nebraska and far western Iowa. Notably, in the last month n41 coverage was added on over a dozen expansion sites in western Nebraska that were added to the network last year. For comparison, here is the very first map that I created in October of 2022 after we noted expansion sites outside of Sprint conversion in Lincoln and Omaha. It doesn't show any western parts of the state, but just know there was nothing besides roaming coverage and a little B12 coverage leaking down from South Dakota to the west of Valentine, NE.

Thanks for all your contributions to network monitoring and cell spotting the past decade. Can't imagine what it would have been without SignalCheck!!! Robert

As many of you know, SignalCheck is a side hobby for me. I taught myself Java when I began this project over a decade ago and I am still learning. I am far from a professional programmer, but I have figured enough things out along the way to get the app this far. Lately, I have been struggling to find the amount of spare time necessary to keep up with app development and bugfixes, but I am still enthusiastic about pushing SCP forward. If someone with experience in Java and Android app development would like to lend a hand, especially to help eradicate some of the most challenging issues I have been unable to resolve, please message me. Thanks!

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.

On the Florida Atlantic coast this weekend and have watched VZW and T-Mobile. FLL had VZW mmW in Terminal 4. T-Mobile has decent (not perfect) n41 coverage with 100+50 MHz, with 20x20 n25 on top of that. Heading north, n41 switches pretty quickly to 100+80 MHz, with pretty consistent coverage along I-95 and the Turnpike. A-1A coverage is patchier between Stuart and Fort Pierce, so I switched to VZW (which was more consistent there) on part of that drive. VZW has 100+60 MHz n77; coverage is less consistent than n41 but there are a number of areas where VZW clocks 500+ Mbps when T-Mobile is 300-400 Mbps. Some TMo sites do have gig+ backhaul though; I got a 1.1+ Gbps test indoors yesterday in Stuart. I'll report on AT&T and Dish later.

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

T-Mobile is mentioned in the second to last paragraph. "SpaceX is aiming to launch the cellular Starlink system for T-Mobile customers later this year, first to support text messages. But the company still needs full approval from the FCC to operate the cellular Starlink technology commercially. " FCC Lets SpaceX Expand Testing of Cellular Starlink for Phones

Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.

"The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings. Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L No specific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.

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.

Progress!

Musical Plant

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

A SCP beta update is rolling out now.. it includes more adjustments to site note features including saving notes and displaying neighbor notes. If you are seeing odd behavior with notes (especially those of you 'missing' notes that you know should be appearing), please send a diagnostic report soon after you observe this behavior. I have added additional logging that should capture what is going on (it can be seen on the Diagnostic Mode page). A major improvement to the function to clean up duplicate LTE GCIs is included in this release. Instead of deleting all duplicate entries, it will now save the entry that has the highest 'hits' column value, and delete all others. It is not perfect, but should be a huge improvement over deleting all of the entries. Please keep in mind if you have duplicates, this could impact site note display. Duplicate GCI entries are typically a product of quickly-changing PLMNs that the OS does not report in sync with other data, resulting in some information being logged with the wrong PLMN. Similar issues are happening on dual-SIM devices that I have not been able to resolve yet. Keep in mind that dual-SIM functionality is still in testing, and even the new option to disable dual-SIM logging is still buggy. I'm working on it! Thanks for all of the feedback, keep it coming...

Correction: T-Mobile has 100+80 MHz n41 live here. I didn't see it yesterday so either they just turned it on, it's temporary capacity for the eclipse, or maybe something else. But that means that T-Mobile has as much mid-band online here as they do in Austin, though I'm 99.9% sure their sites here only have a gig of backhaul (which is plenty for the area tbh). Also, VZW has B48 on some of their macros here, so a bit better than just AWS-or-less LTE. And AT&T actually *does* have n77 here (standard 80+40 setup), albeit with hit-or-miss coverage so I'm guessing it's only on a couple of sites.

As mentioned on the other thread, thanks to Auction 108 my parents' place (Gillespie County, TX) is now up to 80 MHz n41, which can deliver 600+ Mbps outdoors, at least when CA'd (e.g. with 10x10 n25 that's live here). That means indoor FWA with 3/5 bars on an X55 modem is getting 300-400 Mbps download speeds. The drive between Austin and here on US-290 drops to n71 for a few miles, but that's 20x20 with 15x15 B2 and 10x10 B66 so capacity is still fine. Other than those small stretches everything's either 80 MHz (further west) or 100+80 MHz (closer to Austin) n41. Not sure the sites have more than gigabit backhaul, but they don't need more than that to be pretty consistently the fastest. Meanwhile VZW drops from n77 100+40 to LTE-only, and AT&T from n77 80+40 to n5 10x10, once you get a bit outside Austin, which is disappointing given that VZW could light 100+100 n77 if they wanted here, and AT&T of course has 80+40 everywhere.

I'm back in the land that used to be 40 MHz n41. Now getting 80 MHz, which is enough to get 300+ Mbps on FWA (technically not in the geofence) at my parents' place outside town. Could get more, and better uploads, on either newer hardware or outdoors. By way of comparison, AT&T has mmW down Main Street and n5 elsewhere, while VZW is LTE-only here. They had the perfect excuse to add some C-Band for the hordes descending on this area for the eclipse, and...didn't. So I expect T-Mobile to be the only reliable carrier around here unless you're within range of a small cell in town.

So far all my notes have returned!

Shades of Sprint Nextel? T-Mobile to intro 5G PTT service in April

Yes! That does keep it from wandering off Dish and most importantly, reconnecting immediately (at least where there is n70). Thanks!

I have my Dish phone locked to NR-only. That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time. Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip

This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/

In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices. T-Mobile did not bite on use of their c-band or DOD. mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis. They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation. 50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g. 93% of traffic is on midband. SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.

T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.

T-Mobile and EQT Announce Joint Venture to Acquire Lumos and Build Out the Un-carrier’s First Fiber Footprint https://www.t-mobile.com/news/business/t-mobile-eqt-jv-to-acquire-lumos

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.

NextWave is complaining about interference from T-Mobile's network again. It's super annoying considering the area where T-Mobile operates a full 150MHz of BRS/EBS shrank significantly in late 2023. In a place as dense as NYC, have two operators with such split holdings of this band doesn't make sense. Interference seems nearly inevitable. Next Wave has only submitted permits for 22 sites so far, they honestly should just sell. https://www.lightreading.com/5g/redzone-nextwave-also-complain-of-interference-from-t-mobile-s-5g

Neighbor notes have been available for a long time.. many years. Sorry if my post wasn't clear, I was saying I made improvements to that feature.. fixed some bugs and overhauled how the app looks for notes that may be recorded under a different PLMN (like T-Mobile/Sprint Keep sites/etc). NR sites can be tricky depending on the provider because some use multiple NCIs per site.. and in my area, T-Mobile has changed a lot of them. For T-Mobile, I have not identified a pattern between old and new NCIs, so until you save a note under a new NCI, it's going to be blank. If you long-press on the "Connected to [LTE|NR]" label, it will send diagnostics immediately. There's no ability to add a comment to that report but you can send a few when you're seeing an issue and then send one with a comment referring to the other reports so I know what I'm looking for.

Fish Dance

So, I have some corrections to the above on...all four carriers. Dish: has native service AT&T: has n77 80+40 MHz, though it doesn't appear to be on every site VZW: has B48 20+20+20 MHz on some sites, including tall macros T-Mobile: has 100+80 MHz n41; I didn't see the other 100 MHz pop up until today So, T-Mobile went from 40 MHz n41 to 180 MHz as a result of Auction 108, I believe. That's...phenomenal.

Not seeing it on my S24, but the AT&T side of my Dish/Project Genesis Edge+ 2023 is pulling AT&T n77 as of this morning (didn't test yesterday), with 200+ Mbps download speeds outdoors despite being a few miles from the nearest cell site. Maybe someone used the eclipse as an excuse to build out here after all (not VZW, to be clear). Hopefully I'll catch the signal on my S24 as well (swapped in my Boost AT&T SIM to check), I want to see whether they have both 3900-3980 MHz and DoD spectrum online...at which point they'll have the same amount of 5G deployed to T-Mobile (10x10 n5 + 120 MHz C-Band vs. 10x10 n25 + 20x20 n71 + 80 MHz n41), albeit in a config that *should* allow for higher peak speeds. AT&T seems to be aware they have C-Band here, as this location is marked as covered by Internet Air. So...think I'll try setting that up for the family. EDIT 2: T-Mobile actually has 100+80 MHz here, so they've deployed more mid-band than AT&T owns. Still nice to see AT&T turning theirs on.

So, Dish is continuing to build out their network, it seems. Fredericksburg, TX now has n70 strong enough to be usable (100+ Mbps) indoors a few miles outside town, which means that for most of the area they're now the second-fastest network (behind T-Mobile), since neither AT&T nor VZW have C-Band deployed here. I did lose service for a bit earlier this morning, so this coverage may have just come online and is being optimized as a result. But I'll test later with the Edge+ 2023 to see what state things are in.

Small 2.7 MB GPlay Sys update showing here now on S24+ unlocked. Still March 1st date after.

Cruel Summer

N41 coverage expansion likely related to auction 108 new licenses: the northern run from Columbus to Pittsburgh now shows n41 (except between Coshocton and Newcomerstown, around Tappan Lake, and Hopedale) on the T-Mobile coverage map. The northern run is 161, 37, 16, US 36, US 250, US 22 and is 2/3 divided highway. It is a more picturesque alternate to I-70 and I-79. If true, this would be a big change. I did not see this a month ago. Even if just a plan, it is still good news for Home Internet in new rural areas.

Thank you Robert, that means a lot -- especially coming from you. I appreciate everything you have done to host this site, notably allowing me to make it the de facto discussion forum for SCP. Thank YOU! To be clear, I am not ending my efforts or looking to hand the app off.. just figured a user with more skills than me might be interested in lending a hand with some of the issues I haven't succeeding in resolving. It's more fun to add new features, but I find myself spending more and more time chasing bugs instead of doing cool stuff!

I just got back home and got today's update and my notes fine.

The One UI 6.1 update is out.

The March Play System Update that PythonFan referred to in the S24 thread is also out for S22

I see everything correct. The two ARFCN's you mentioned earlier and they idenitify as n-41. using 4.832b SCP. Only using one TM SIM.

76MB Google Play System update after that, bringing the date up to 3/1 from prior 2/1 date.

April security patch is already out - 738.30 MB download.

100+80 works in Nokia markets though (e.g. here).

Well... I tried to send an email but Gmail doesn't seem to want to send. Never seen that before, just sitting "queued." It may have sent twice now... Lol.

On a related note, I did some diving the through the FCC documents for the AEHC. I couldn't find any that indicated they validated it for NR100+NR90 (just NR100+NR50+LTE20+LTE20). This makes me think we will only see the NR100+NR90 channels in Ericsson markets.

Yes actually, I was wondering if I had somehow deleted them. But the majority of the sites I'm sure I had notes for are blank now.

Yeah, ignore me. I apparently fail reading comprehension.