dkyeager

Just sent a diag for moto g stylus 5g (2021) for Verizon network MobileX on NSA n77.

On my s21 ultras with factory unlocked firmware (January 1, 2023 security patch level), for the Verizon Network on US Mobile, going into SCP system shortcuts, radio info, and setting preferred Network Type to NR/LTE seems to result in better reporting of n77.  AT&T seems to produce similar results but more testing is needed with a nearby n77 site.  More testing need on T-Mobile network.  Network often inclined to put it on n41 SA and will go to AWS to support VoLTE. NR on display appears to be n41, but will send in diags when certain.  Cellmapper supported this plus *#0011#, but network changing to much at this hour.

Oneplus Nord n200 5g with oem firmware, radio mode NR/LTE does not appear to make a difference on the T-Mobile network.  NR only with Boost sim results in no service, while I only see n600 on Tello.*  Send in diags based on speed (600Mbps) identifying NR as N41 if the details in the diags back that up.  Hope to end up with android 11 oem for band locking else android 12 oxygen T-Mobile firmware.  Really only a T-Mobile device for 5g.

Moto g stylus 5g (2021) works great with T-Mobile.  Will check out other carriers.

10 hours ago, mikejeep said:

Excellent, finally!!

 

No, your report showed it as T-Mobile. You can send diags instantly by long-pressing on the "Connected to [LTE|5G-NR]" text line in the top right corner also. You won't have an opportunity to enter a reason but your username is still attached.

Thanks for the tip.  I just was not fast enough.  I have deleted these Verizon n41s from the map several times in the past From the s22+ and the s21s..

Verified that the gear (Services) icon is now locked if the indicator icons are locked on all of my active phones.  Thank you very very much. 🍻

S22+ n38 error with Verizon as secondary fixed.

Sent diags "ere" which hopefully caught a very rare error of n38/n41 being reported as Verizon.  Happens a few times per month on s21+ and s21 Ultras. Used "ere" because I had to type fast since diags are captured at end rather than beginning.

Got 4.757b overnight.  4.758b outstanding. Will test with all my 5g phones later.

Just noticed that SCP is displaying my provider as Boost Mobile instead of AT&T yet the PLMN is 310410.  Cellmapper is doing the same.  310240 is assigned to Boost Mobile (of course  T-Mobile could own it).   313340 is used by Dish Genesis iirc.

Nevermind, switched back to AT&T for both

35 minutes ago, radem said:

I would expect Dish to purchase the 800mhz and use that spectrum as the collateral for much of the purchase.  It may be that T-Mobile would even hold the loan on this deal with the requirement that if Dish defaults on the loan, T-Mobile would get the spectrum back.

I could see that, with Dish getting a very favorable interest rate.

https://www.rcrwireless.com/20230307/5g/dish-testing-the-800-mhz-waters

Moving the band 26 option to likely.

https://www.rcrwireless.com/20230307/5g/dish-testing-the-800-mhz-waters

Sorry dudes, much less likely T-Mobile will keep band 26 800MHz.

I sent in several diags of n38 on T-Mobile on latest s22+ factory unlocked last night. *#0011# only shows n41.  Appears to happen when secondary sim detects change in its carrier band.

On 3/5/2023 at 6:33 PM, dkyeager said:

AT&T managed to tie up T-Mobile's Auction 108 2.5GHz winnings for rural areas for now.  May need to wait for a 5th commissioner.

https://www.cnn.com/2023/03/07/politics/gigi-sohn-withdraws-fcc-nomination/index.html

Clock will start again -- no fifth FCC commissioner anytime soon.

22 hours ago, dkyeager said:

On a 4g phone (rooted) I show MobileX has standard priority with NSG.  Will try at my favor poor performing overloaded Verizon site to test 5g priority.

Here are the speedtest results at a slow site (done in an alternating fashion between the MVNOs:

Red Pocket (low priority): 9/24 2/17 7/24

MobileX 66/16 70/21 72/18

US Mobile (High Priority): 64/22 61/16 99/20

Thus it is safe to say that MobileX 5g is high priority.

Interest quirks are the MobileX tries imperfectly to determine your phone type.  If it does not guess at all then it remains the last one successfully tested.  For example, it does not detect the Samsung 32 5g factory unlocked, but does detect the the carrier version.  It however does not know the firmware loaded.  The T-Mobile firmware does not support n77, while the factory unlocked does.

Premier sponsors can find other related information here: https://s4gru.com/forums/topic/8347-signal-hunter-tips/

2 hours ago, jonathanm1978 said:

Well... I upgraded phones...and went with the Samsung 23 Ultra.. So I assume that I can get all the newer bands of frequency that are being utilized.. I don't think central Alabama is going to light up anything in the ultra wideband in the near future, unless it's birmingham... I live rural between Bham and Montgomery so it's doubtful I see that stuff .. 

I do see the 5G UC when I go into the little town I live close to.. but if I didn't have that Cell Spot... I would be kinda SOL unless it was wifi calling.. hopefully they do some big upgrading soon.

AT&T managed to tie up T-Mobile's Auction 108 2.5GHz winnings for rural areas for now.  May need to wait for a 5th commissioner.

On a 4g phone (rooted) I show MobileX has standard priority with NSG.  Will try at my favor poor performing overloaded Verizon site to test 5g priority.

On 3/3/2023 at 8:02 AM, dkyeager said:

Idea has some promise.  Been unsuccessfully trying to test it for a while, 1st with esim then psim, on a variety of devices.  Could be getting hung up on Verizon network quirks.  Communication is poor, very bot like.  Officially launched, but not ready for prime time.  Usual rule with MVNOs should apply: if automated processes work then great else move on.

Finally have liftoff this morning. Middle of the night messages seemed to work best.  Often seem to be limited to one message per day. If you get desperate, start a new message, but they hate that.  You will get a response.

Works great with MobileX on an A32 5g.

When the Lock Indicator Icons is enabled, can the flower/gear in-between the ligthning bolt and three dots be eliminated? I sometimes manage to hit it twice which disables locations for a trip.  Thanks

Idea has some promise.  Been unsuccessfully trying to test it for a while, 1st with esim then psim, on a variety of devices.  Could be getting hung up on Verizon network quirks.  Communication is poor, very bot like.  Officially launched, but not ready for prime time.  Usual rule with MVNOs should apply: if automated processes work then great else move on.

https://www.telecompetitor.com/5g-revenue-analysis-fwa-ranks-last-out-of-8-services-at-the-top-is/

No mention of network slicing.  Low speed IOT makes sense to me, but how long will it take to ramp up?  How much support costs to help get it launched to a much larger degree?

"70% of T-Mobile network traffic is 5g" - Neville Ray

1 hour ago, Paynefanbro said:

Given the location I'm betting whoever the owner of the building is is is planning to sell/redevelop the site so no lease renewal.

I feel like it's the same deal with 1063 Pacific St.

Edit: 304 Boerum was sold for $14 million just over a year ago so the new owner must've said no.

Also 1063 Pacific changed hands in 2021 as part of a group sale. New owners likely said no to that one too.

Could also be something ad simply as getting new roofs.

1 hour ago, PedroDaGr8 said:

That's been happening in force around me recently, as well. A few sites are unfortunate because they provide some needed in-fill but oh well. 

Now that Neville is retiring soon, they may want all Sprint decoms to occur under his watch.

https://www.t-mobile.com/news/network/t-mobile-advances-5g-standalone-to-deliver-faster-speeds-and-enhanced-performance

4 new VoNR cities: Cincinnati, New Orleans. New York, Seattle.

No mention of official VoNR devices. Previously the s21 was listed iirc

Systems are starting to come back to life: