dkyeager

All tests have been done on 1 sim.  US Mobile has a plan for multiple carriers automatically switching to the strongest signal in dual sim phones (announced on Reddit by CEO) with existing hardware.  Beta testing was to begin right away but now has reportedly been delayed to June.  Perhaps waiting for dual sim firmware updates. 

Tested s21 ultra, s22 plus, s24 ultra all with latest released factory unlocked firmware.  Tested tonight during busiest times and occasionally in the afternoon and as noted above.  Rapid switching between n41 SA 100Mhz and 80 Mhz no longer occurs.  Basically one is chosen and it rarely changes to the other. Checked with other sites.

I also tested for NSA.  The s21 ultra, s22 plus, and s24 ultra all with latest released factory unlocked firmware.  All just displayed 5G-NR with hardly any other details.  SCP diags sent in.  one for s22 plus should be ignored (two sims).

I also tested A32 5G with April 1, 2022 firmware (T-Mobile and Factory Unlocked).  Both displayed NSA fine, ie 5G NR 2500 with details and neighbors.  They do not go into SA 5G, which used to work iirc.  Maybe lack of VoNR?

https://www.fiercewireless.com/5g/verizon-network-slicing-operational-trials

Smart political move bt Verizon. The FCC can't complain about network slicing used to support first responders.

since we started looking in depth at this, the firmware has updated on the s24 ultra and the s21 ultra (both factory unlocked). Doing these tests with only one sim active.  This earlier morning and now I am not seeing rapid switching between the n41 SA 100Mhz and the 80Mhz channels. Nr-arfcn matches in both cases.  s21 switched from 80 to 100 and reported it fine. 

If I airplane mode the s21 I will frequently get the 5G-NR for either band (sent a diag).  I will check again tonight during peak traffic times.

3 hours ago, iansltx said:

...VZW has 100+60 MHz n77; coverage is less consistent than n41 but there are a number of areas where VZW clocks 500+ Mbps...

How did SCP do on reporting the n77? Any SA? Was the full 160 used at once? Did the n77 frequencies change between the two?  Thanks

5 hours ago, mikejeep said:

Another beta is rolling out now with some more adjustments and additional diagnostics. The last two beta releases have taken 48+ hours for approval, hopefully this one clears quicker but that's up to Google Play..

The s21 ultra with the same scp version as yesterday will often show 80 or 100mhz as 5G-NR but will also show either correctly.  sent diags. (dual sim). 

With only t-mobile network sim it only show 100Mhz and stayed on 100Mhz for me tonight.

Verizon only uses 100MHz here as visible to me, even with n77 sa enabled on phone as well.  I asked NYC for help.

I believe Verizon has 160Mhz of n77 licenses in NYC, which have been available since last summer.  Have any of you seen more than 100Mhz? Does SCP report it correctly in terms of band and nr-arfcn? Of course ideally it would be SA lol.

3 hours ago, mikejeep said:

Ahh then it sounds more like yet another dual-SIM bug! Thank you, that is a big help.. I've been working on trying to figure this out.

I will test it on a s21 ultra on T-Mobile and hopefully on Verizon shortly (not sure it matters with them yet - until SA is readily available).

S24 ultra with second sim disabled. Toggles back and forth more slowly between 100mhz and 80mhz with nr-arfcn being reported correctly and band being reported as n41.

My s24 Ultras auto updated to April 1 security patch over night. Not on wi-fi.  Play system remains at March 1. No notice that update occurred on screen.

Got the latest update. On my S24 ultra the NR-ARFCN display remains constant (which is inaccurate according to diags) while n41 and 38 toggle back and forth.  I updated then rebooted before testing. Two sims active.

My security patch level updated automatically to April 1 before this update. Diags sent while n38 was displaying.

Was able to install the March 1 Android security patch. Seems slightly more accurate with 5g ca band id, but can not swear by it. Updated google play system update through the software information screen to March 1. *#73# still works. Froze updates waiting on SCP update beta to fix n41 showing as n38.

Has anyone checked Verizon n77 in areas with more than 100MHZ active? This spectrum has been fully available since August of last year.  Of course they are not typically using SA.

I updated my other s21 ultra factory unlocked to the latest firmware... It behaves like the S24 Ultra n38 or n41 depending on 80 or 100MHz or their nr- arfcn.

On 3/25/2024 at 8:25 PM, chamb said:

That is exaclty the same as my two n-41 arfcn's.The only difference I have is that I have a 100 and a 90 bandwidth.

I am in the old Shentel area in Pennsylvania.  I stilll have a S-22.

What do you see with the latest alpha/ beta version?

1 hour ago, chamb said:

That is exaclty the same as my two n-41 arfcn's.The only difference I have is that I have a 100 and a 90 bandwidth.

I am in the old Shentel area in Pennsylvania.  I stilll have a S-22.

S21 Ultra factory unlocked with firmware current in January does not vary. Always SA n41. Does do n41 CA plus others.

A32 5g factory unlocked does not vary on n41.  This is older firmware.  Can not lock in SA n25. T-Mobile variant does not have n25.

N2 versus n25: nr-arfcn remains the same, bandwidth remains the same on s24 ultra factory unlocked. (when watching diag as well as scp)

S24 ultra factory unlocked still switches back and forth from n41 to n38. Sent diags.  Will check other dual sim phones.

Other factor. Seems that when my bandwidth is 80 it shows n41 (nr-arfcn 502110), when bandwidth is 100 it shows n38 (nr-arfcm 520110).

NP. FYI, No sign of beta yet.  Being in beta instead of alpha is no problem. Perhaps betas only get it once all alphas have been updated.

Edit just got beta a few minutes ago.

Seeing SA n41(100) + n71 ÷ n25 + NR_SLICE/PDU: eMBBFFFFFF/1 NR_SLICE/PDU: eMBBFFFFFF/2 + n41(80)

I  have nit seen this beta update yet. Has anyone else gotten it yet?

Mystery Hole WV

Crab Shack

Shrimp Avocado salad

24 minutes ago, Paynefanbro said:

Dish marks 5G drive test milestone, validating its network speeds

https://www.fiercewireless.com/5g/dish-marks-5g-drive-test-milestone

And yet barely anyone can use it. That's probably the only reason why they're able to meet these network speed milestones. 

 

Or maybe that is why they were holding off.

5 hours ago, cooltech6597 said:

I'm starting to find FDD+TDD UL sites. It seems to be enabled on a per-site basis, rather than market wide from my testing. So far I've found one in my immediate area, which is a site T-Mobile used to have a low 12/66 rack, and moved up to a higher Sprint rack (while adding n41 and the usual bands) within the last week. I've also found a few UL CA enabled sites along US-23 when I was going up to Ann Arbor today. Uploads peaked at 135mbps, which isn't exactly as fast as I had expected, but that's expected given I can't figure out how to enable 256QAM NR upload on my S24 (I could on my S21).

Are you finding the sites with high upload speeds (CA) are also 1Gps+ sites?