dkyeager

https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=Y&application_id=4BAIoTTin%2BqLQVbhAzhkYg%3D%3D&fcc_id=A3LSMS911B I don't see any n70 here for Dish yet.

One of my Nord n200 5Gs bricked this morning after a normal shutdown. Figured out it was in Emergency Download Mode when I connected it to a PC and it wanted to install a new driver. Check out details of fixing it here: https://www.getdroidtips.com/unbrick-t-mobile-oneplus-nord-200-5g-firmware/ Got me back to Android 11. Will see in the coming days if my memory is correct that Android 11 is better than 12 on this phone, especially with SCP.

I have 3 Samsung Galaxy a10e for mapping LTE. For 5G I like the Samsung a32 5g (both factory unlocked). In both cases try to get one with firmware from the spring of this year. Then you can use the Samsung Band Selection app no matter what the carrier. Been trying to get my OnePlus Nord n200 5Gs squared away with android 11 and rooted. OnePlus bought out by Oppo thus service and strategic direction are both problems. Just getting an e-mail back for the unlock the bootloader process is taking a while. Once we get out of NSA, 5g will be much easier to map. Factory unlocked esim issues are plentiful on high end Samsungs. My quest is a factory unlocked phone that works well with SCP and Cellmapper for both SA and NSA, with multiple active esims that work easily with MVNOs, functioning VoNR, great reception and transmission, full band support for AT&T and Dish. My next hopeful candidate is the s23.

Curious as to how SCP works with it regarding NSA, particularly in markets with n41 BW=100 and second channel.

what I found here may apply:

Playing around some more with this, specially setting the preferred network type to NR/LTE/GSM/WCDMA. Seems to produce better results with SCP but drops performance down to 230/7 from 476/33. Basically seems to change it from NSA to SA in terms of 5g. SCP implies n71 only. Noted instability when running speed tests thus needs more tinkering. Rebooting may fix this. Answers calls in LTE.

Factory Unlocked firmware update S2RES32.29-16-1-10-4. 25.51MB, Oct 1 Security Update No changes observed. SCP still very limited with 5G NSA. Never seen a dialer code work other than *#06#

Some day, over the rainbow, it will all be fixed. Until then we live like this while we are the quest for the perfect phone:

I am still getting 900/50 on Samsung Galaxy A32 5g and 1200/65 on S21 Ultra. Both factory unlocked, no recent firmware updates. N25 is present but not accepting connections.

I can confirm the same in Columbus. Seen with *#0011# on a s21 ultra factory unlocked.

must have posted at the same time. was thinking they might have C-Spire., or maybe they are just using T-Mobile Licenses. tried by Alabama and Mississippi and did not see it

FCC broadband map based on June data: fun to play around with the carriers (type in their name). Dish is listed under Hughes. Toggle on and off carrier visbility. drop and add carriers. I started you off with the major carriers looking at the higher level of 5g performance. be sure to drill al they way down in an area. https://broadbandmap.fcc.gov/provider-detail/mobile?zoom=4.00&vlon=-98.221479&vlat=40.113366&providers=130077_500-2_on%2C131425_500-2_on%2C130403_500-2_on&env=0&pct_cvg=0 US Cellular = Telephone and Data Systems, Inc.

Went out to Minneapolis. Saw n7 issue. Returned to Columbus. Now get n38. Sent diags for n38. Narfcn is 520110 on *#0011# service mode. If I force it to SA, it is n41 of course at the same frequency

How soon I forget. Already starred that when first requested.

Above comment was production version. Updated to beta. Status line has band but no RSRP, which does change bands. Maybe just a formating issue on RSRP number? "--". Top lines are much like s21 factory unlocked: 5g-NR heading, followed by SS-RSRP and SS-RSRQ with values. UL and DL Earfcn, CA info displayed. Separately, phone does display correct bands using *#0011#. Gives indication 100MHz of n41 and second n41 carrier at 40MHz plus lte 66 at 20bw. Without load it drops n41 and adds LTE band 2 which is implied in SCP 2xCA 20+20 under LTE AWS heading section. SCP does not change under load (5g NSA).

Sent diags from a S22+ with T-Mobile postpaid on eSIM and US Mobile prepaid on pSIM with eSIM as primary. When a call comes in on the pSIM secondary, data also shifts over to it, but SCP Pro still shows the eSIM LTE and 5G. Cellmapper always shows both. Speedtest assumes primary eSIM, but speed is definitely the pSIM secondary.

Factory unlocked also has the November 1 update on the s22+.

https://www.fiercewireless.com/5g/t-mobile-rolls-out-5g-standalone-25-ghz-spectrum plus at the bottom: "Ray also hinted that the company may consider using its milllimeter wave (mmWave) spectrum. He said that it might extend its reach with mmWave but would not do it at the street level like Verizon is doing with its mmWave spectrum. Instead, he said it would consider building a macro network overlay in areas where it makes sense."

FCC auction 102 key details for 24GHz below. This seems to require 40% of population covered in 10 years. Could be quite expensive unless you can increase radius from a couple of blocks or have a few minutes/seconds of coverage count (hence a freeway location - my closest interchange serves 100,000 people per day). It should also be noted that Samsung expanded mmWave from the s21 ultra to the entire s22 product line sold for the US. The ability of the license holder to partition down to a county is also a way to reduce costs, ie drop the less dense counties to reduce construction costs. This could produce a speculators market at the edge of high growth areas. License Period Initial authorizations will have a term not to exceed ten years from the date of initial issuance or renewal. (See CFR § 30.103) Construction Requirements Upper Microwave Flexible Use Service licensees must make a buildout showing as part of their renewal applications. Licensees relying on mobile or point-to-multipoint service must show that they are providing reliable signal coverage and service to at least 40 percent of the population within the service area of the licensee, and that they are using facilities to provide service in that area either to customers or for internal use. Licensees relying on point-to-point service must demonstrate that they have four links operating and providing service, either to customers or for internal use, if the population within the license area is equal to or less than 268,000. If the population within the license area is greater than 268,000, a licensee relying on point-to-point service must demonstrate that it has at least one link in operation and is providing service for each 67,000 population within the license area. In order to be eligible to be counted under the point-to-point buildout standard, a point-to-point link must operate with a transmit power greater than +43 dBm. Showings that rely on a combination of multiple types of service will be evaluated on a case-by-case basis. If a licensee in this service is also a Fixed-Satellite Service licensee and uses the spectrum covered under its UMFUS license in connection with a satellite earth station, it can demonstrate compliance with the requirements of this section by demonstrating that the earth station in question is in service, operational, and using the spectrum associated with the license. This provision can only be used to demonstrate compliance for the county in which the earth station is located. Failure to meet this requirement will result in automatic cancellation of the license. In bands licensed on a Partial Economic Area basis, licensees will have the option of partitioning a license on a county basis in order to reduce the population within the license area to a level where the licensee’s buildout would meet one of the applicable performance metrics. (See 47 CFR § 30.104)

I wonder what is causing them to use it now. Is this a high demand area? Given the usual mmWave coverage of several blocks, I would not expect to see it along a freeway. It should be noted that mmWave tests in Australia have gotten a distance of 10km, but little was stated about their antennas or pattern (maybe used like microwave backhaul between sites). Another possibility for T-Mobile using mmWave would be possible FCC buildout requirements. They could also have high demand for home internet in the area. Hopefully they don't feel obliged to use it because Verizon does. Any info on speed and distance covered, especially non line of sight? Pictures of equipment? (link if previously posted)

Those look like shorter versions of what Sprint installed in a few cases years ago (often without notice) and then soon abandoned the project.

Here is the other midrange spectrum T-Mobile recently purchased: 3.45GHz (auction 110) T-Mobile's other midband spectrum: 3.5GHz (auction 105) 3.7GHz (auction 107) https://www.sashajavid.com/Auction107_TMo_Final_Demand.php

She forgot about n77, which one our members has found live in Houston. T-Mobile bought more midwave spectrum in major metro areas to address this concern. mmWave is very limited coverage wise (think a couple of blocks outside). T-Mobile's stadium, train station, college campus dorm and high rise apartment approach will have a better return on investment. Cleveland has like 8 mmWave sites for T-Mobile. One of her sources favors mmWave. mmWave made sense for Verizon when they started 5g just like Wimax did for Sprint when they started 4g. however mmWave will have a longer term role.

T-Mobile is buying additional b41 from Shentel in an historic area which they never really extended into in Ohio, plus other spectrum in WV (which should have been included in T-Mobile Shentel deal IMO). https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp;ATTACHMENTS=RtDKjyNpy4rYvhMkGxzfXV21JZqhLGdxyp1sYSjpzc7P4pFkldH4!327797201!925630209?applType=search&fileKey=271306483&attachmentKey=21621747&attachmentInd=applAttach https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp?applType=search&fileKey=1612687808&attachmentKey=21621749&attachmentInd=applAttach And reviving an expired license: https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp?applType=search&fileKey=992785661&attachmentKey=21619170&attachmentInd=applAttach https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp?applType=search&fileKey=620066004&attachmentKey=21619171&attachmentInd=applAttach Other news. STA 600MHz extensions for LA and Grand Forks ND: https://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=4270150 https://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=4274224

Yes, the Buffards Mountain Site broadcasting B26 is reasonable given its likely location versus the curve in US 15 which you were traveling on. The earfcn matches 865Mhz for band 26. The S4GRU New York crew recently spotted a similar site. My guess is Dish will push out a final decision on B26 for as long as possible. B26 is most useful in urban and mountainous locations. (Image easily expandable on the large screen PC).