dkyeager

3 hours ago, red_dog007 said:

If that sim comes to BM and BI, I wonder if there will be device restrictions or some such.

Where I am at, lacking n70 on your device is pretty big deal.  Dish does not own any n66 here and only 5x5 of n71. 

I am also assuming that Dish needs to do a second tower climb to add their 3.45GHz.  I have not seen any Dish sites get a second antenna added here yet.

I'd still likely give it a go on my Pixel 7.

I think the whole phone issue has them flummoxed. VoNR likely still not working properly and almost zero interest by phone makers to add n70.  Would have thought a lower tier phone brand would have a phone with all their bands and VoNR. Hopefully they will shed some light in their next quarterly report.

All focus might just be on their n71 rollout. 70% of the population must be covered by June 14.

Edit: US Cellular puts reliable VoNR at two years away. https://www.fiercewireless.com/tech/uscellular-sees-no-rush-deploy-5g-voice

https://www.fiercewireless.com/wireless/dish-raise-another-500m-pay-5g-network

Wonder what their burn rate is.

50 minutes ago, Dkoellerwx said:

They are going after American Tower sites pretty heavily

1 hour ago, towerhugger said:

I could be wrong but I do not believe this is an American Tower location

On 1/13/2023 at 8:59 AM, ctcomputers said:

I live in western Nebraska and very interested in the T-Mobile expansion

In case you don't have one, I keep an iPhone for the sole purpose of the American Tower app which gives their sites along with a few details such as height and lat long. I can share some sites for all of you to look at if needed. Just let me know the area and I will get back to you within a few days typically.

Testing the dual sim on a s22+ unlocked, fully patched.

Suggestion #1: instead of [2] on the right for the second sim, use 2) or #2 on the left, which should generate less confusion.  

Glitches observed:

1) Normally see n41 for T-Mobile, but rarely see n38.

2) Sometimes seeing a third line which is either my #2 Verizion repeated, or less common, my #1 sim repeated in #2 slot with the real #2 below it. Also possible this happens when the #2 sim band changes.

*** I likely captured some of the above two in a diag I sent.

3) Sitting in one spot, my Verizon band changed, yet my record count stayed at one.  Verfied by uploading which also showed only one. Should have been at least three imo: T-Mobile n41 (maybe n38), Verizon b5, Verizon b13.

Wifi shows up fine with two carriers listed.  All of this is on a phone where I have limited access. My own s21 ultra dual sim phone is held up by T-Mobile and US Mobile in terms of getting esim working. When my T-Mobile account gets migrated off Sprint billing it finally should work.

My two cents:

The timestamp at the top fits nicely with the IP address, otherwise the location accuracy/timestamp overwrite the IP address. Maybe just have the second timestamp with the second SIM which should also make programming easier.

36 minutes ago, ctcomputers said:

I live in western Nebraska and very interested in the T-Mobile expansion.  As indicated it appears the most recent tower that was lit up is an American Tower Company tower that was being used by Verizon.  Does this mean that T-Mobile co-locates or shares the tower space with Verizon or will it typically be exclusive use?  Would it be a safe assumption that the other American Tower locations in the vicinity may soon be T-mobile or is there anywhere to track or confirm filings and such?  Very exciting to see some changes and progress in the rural area! 

The carriers typically don't own their own sites anymore but rather lease space from tower management companies like Crown Castle or American Tower.  However these companies will build new sites if desired for carriers, but with permit  and construction time and costs, that is much less frequent these days.  Much more common to use an existing tower. Sharing is typically no problem  The tower management companies have lots of data on their clients preferences, thus will often build speculative towers so the carriers can move quicker.

Hearing rumors of a Rainbow SIM:

Any confirmations?

Samsung tweet today:

.@Samsung welcomed @dishwireless to its Headquarters in Suwon 🇰🇷 to discuss its #5G partnership providing cloud-native #vRAN and #OpenRAN radio solutions for #DISHwireless’ nationwide #5Gnetwork rollout. #CloudRAN

Dosh followed up with a picture and list of all their people there.  It would be lovely if they could get Samsung to support n70 in their phones as part of an antenna MIMO deal.

8 hours ago, mikejeep said:

...The "No Signal" alert must also be enabled for the reset to be triggered.

Any other alerts used as a trigger for other behavior? I don't normally use alerts anymore and actually tend to keep sound off on my various phones so as not to distract my driving (Also for the various spam calls and texts that sneak through my preventive measures).

4 hours ago, Dkoellerwx said:

Where do you look up what area the licenses cover? I see ones for Missouri, Iowa, Kansas, and Nebraska. At least, I think I do. I'm not entirely sure what I'm looking at.

Plug in the license or lease "number" here near the top into call sign: https://wireless2.fcc.gov/UlsApp/UlsSearch/searchAdvanced.jsp

Then go to the map tab.

T-Mobile continues to buy up ED licenses plus a few AW and WT in the middle of the country (Iowa etc).

https://docs.fcc.gov/public/attachments/DOC-390578A1.pdf

4 hours ago, mikejeep said:

do not update immediately if you have a critical need for the app in case there are issues that I did not uncover in my testing. The core routines that process signal information have been changed significantly in order to provide dual SIM support.

Not surprisingly, the most notable change in this version is the long-awaited inclusion of dual SIM support. Android 10+ is required...

Thanks for these exciting fearures.  Is Android 10 required for all devices or just to to support dual SIM when enabled?

Lots of new "NE" microwave "CF" licenses for T-Mobile: https://docs.fcc.gov/public/attachments/DOC-390506A1.pdf

new AWS leases for T-Mobile in PR: https://docs.fcc.gov/public/attachments/DOC-390480A1.pdf

4 more long forms for the auction 108 2.5GHz auction announced.  This brings it up to 55 out of 68 firms.  Does not include T-Mobile, winner of about 90% of the licenses in this public auction.

https://docs.fcc.gov/public/attachments/DA-23-12A2.pdf

Here are the others previously released:

https://docs.fcc.gov/public/attachments/DA-22-1243A2.pdf

https://docs.fcc.gov/public/attachments/DA-22-1269A2.pdf

Here is the process for challenging after each batch is released (dates will changes of course):

Petitions to deny the applications listed in Attachment A must be filed no later than December
19, 2022, ten (10) days after the date of this Public Notice.3 Oppositions to a petition to deny must be
filed no later than December 27, 2022, five (5) business days after the filing date for petitions to deny.
Replies to oppositions must be filed no later than January 4, 2023, five (5) business days after the filing
date for oppositions. All pleadings filed regarding any of these Auction 108 long-form applications
should reference the file number of the application. Each application is a restricted proceeding under the
Commission’s rules.4 A petitioner shall serve a copy of its petition to deny on the applicant and on all
other interested parties pursuant to 47 CFR § 1.47. Oppositions and replies shall be served on the
petitioner and all other interested parties....

...We request that one copy of each pleading be delivered electronically, by email to: Madelaine
Maior and Nadja Sodos-Wallace at Madelaine.Maior@fcc.gov and Nadja.SodosWallace@fcc.gov.
The applications listed in Attachment A are available to the public for electronic viewing through
ULS. Any amendments to an FCC Form 601 application also must be filed electronically through ULS.
For technical assistance in using ULS for viewing an application or filing an amendment to an
application, contact the ULS Licensing Support Hotline at (877) 480-3201. The ULS Licensing Support
Hotline is available Monday through Friday, from 8:00 A.M. to 6:00 P.M. Eastern Time. All calls to the
ULS Licensing Support Hotline are recorded. Questions regarding procedural issues should be directed
to Madelaine Maior, (202) 418-1466 or Madelaine.Maior@fcc.gov. Copies of materials can be obtained
from the FCC’s Reference Information Center at (202) 418-0270. Press contact: Anne Veigle at (202)
418-0500 or Anne.Veigle@fcc.gov.

8 hours ago, RAvirani said:

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:

SignalCheck data:

Love the second map. Looks like Signal Detector. A standard signalcheck.net map feature I have missed?

Filled with interesting stats.  Ignore the 940/500 (it should be 940/50.)  https://docs.fcc.gov/public/attachments/FCC-22-103A1.pdf

Commissioner Carr felt the market divisions are ancient and should all be combined together.  I certainly agree in general.  I would buy the best internet for my needs. Be it fiber, cable, WISP, satellite.  Appendices etc.: https://www.fcc.gov/document/2022-communications-marketplace-report

T-Mobile wins a state: Montana. Here is the list (slide from metro to state) https://rootmetrics.com/en-US/rootscore/map

Note that two states are remaining to be completed.

40 minutes ago, mikejeep said:

That's exactly why everyone has the option to change it to their liking

It's probably worth repeating.. all [modern] apps utilize the same core location methods, so any data that is obtained is made available to any other app looking for it. So if you're running a navigation app whenever you drive (or even if you're just plugged into Android Auto but have a navigation app available to it), you're going to get updates about as fast as possible, regardless of your SCP settings. Essentially, only the "most aggressive" app running is actually controlling the refresh rate.

1 hour ago, RAvirani said:

I think that would be a good change.

A standard highway speed of 65 miles per hour...At one second between updates, you'd record a data point every 95.3 feet

Mike point is interesting about frequency increasing with nav apps. I ran through the same basic calculations as RAvirani this morning. Historical the seconds setting was because the processors could not handle 1 second. But even my LG G4 can do this now.

However, I do think we need to look longer term. If you have location feedback to SCP from the mapping process, then the app should become much more popular, hence generating more points, even with 4 second settings. This is provided we keep battery use at more minimum levels. Might actually want the default to go higher so as not to trip the os notifications.  Some data multipled by more users is far better than no data.

For those concerned about AT&T's challenge to T-Mobile's auction 108 winnings in 2.5GHz and their challenge to T-Mobile's overall spectrum position, please see https://wireless2.fcc.gov/UlsApp/ApplicationSearch/applAdmin.jsp?applID=13719003#  which is approval for W.A.T.C.H. TV transferring some BRS and ED licenses to T-Mobile. This was consented on December 7.

Still no Verizon 5G SA in my area yet. Have seen it is starting to pop-up in other places. 3g still alive, so not a fully automated process. Many Toyota owners and others will be surprised when their navigation dies.

Sent in diags to help you identify Verizon n77 NSA as noted in the diag. (Other one was a test of the lightening bolt.)

3 hours ago, PedroDaGr8 said:

Per someone over on Reddit:  Android reports the ARFCN for the SSB of the NR channel. Unlike LTE which had this at the center, it can be any value within the frequency range of the channel for NR. I guess T-Mo is using a non-standard SSB location for some reason. This is really unfortunate because it means the recorded values for n41 are totally wrong. 

I read it a little differently. He did state some Pixels worked correctly and put the blame on firmware.

2 hours ago, PedroDaGr8 said:

This has been something I noticed a while back when n41-SA was rolling out. Just because a band doesn't show up in *#2263# doesn't mean the phone can't connect to it. 

Read this, then goto the 1st page for directions: https://forum.xda-developers.com/t/how-to-enable-all-bands-through-service-menu-on-us-ca-s22-series-including-sub-6-and-mmwave.4488435/page-17#post-87918859

Edit: Good for not only n25 SA on T-Mobile but also frees up more overseas bands if you travel or when Verizon and AT&T get moving on SA.

Band 25 - getting about 230/31 about 0.5 miles from site. Selected naturally by phone. The ability for it to choose it is another story.

1 hour ago, iansltx said:

Am aware, but that would require a factory reset

Unless you need to load new firmware, I did not see that mentioned. Can you point out where that is mentioned in the XDA link?