dkyeager

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

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.

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.

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/

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.

A few more auction 108 2.5GHz licenses granted: Licensee Name Market Description Channel Block File Number Callsign City of Ketchikan d/b/a Ketchikan Public Utilities KETCHIKAN GATEWAY, AK 1 0010206478 WRWK290 City of Ketchikan d/b/a Ketchikan Public Utilities KETCHIKAN GATEWAY, AK 2 0010206478 WRWK291 City of Ketchikan d/b/a Ketchikan Public Utilities KETCHIKAN GATEWAY, AK 3 0010206478 WRWK292 Evolve Cellular Inc. CHURCHILL, NV 1 0010205559 WRWK315 Evolve Cellular Inc. HUMBOLDT, NV 3 0010205559 WRWK316 Evolve Cellular Inc. TRINITY, TX 1 0010205559 WRWK317 Inland Cellular LLC ADAMS, ID 1 0010204528 WRWK306 Inland Cellular LLC BENEWAH, ID 1 0010204528 WRWK307 Inland Cellular LLC BENEWAH, ID 2 0010204528 WRWK308 Inland Cellular LLC IDAHO, ID 1 0010204528 WRWK309 Inland Cellular LLC IDAHO, ID 2 0010204528 WRWK310 Inland Cellular LLC LEWIS, ID 1 0010204528 WRWK311 Inland Cellular LLC LEWIS, ID 2 0010204528 WRWK312 Inland Cellular LLC CHELAN, WA 1 0010204528 WRWK313 Inland Cellular LLC FERRY, WA 1 0010204528 WRWK314 Inland MT LLC FERGUS, MT 1 0010204014 WRWK319 Inland MT LLC FLATHEAD, MT 1 0010204014 WRWK320 Inland MT LLC GLACIER, MT 1 0010204014 WRWK321 Inland MT LLC LAKE, MT 1 0010204014 WRWK322 Inland MT LLC LAKE, MT 2 0010204014 WRWK323 Inland MT LLC MINERAL, MT 1 0010204014 WRWK324 Inland MT LLC MISSOULA, MT 2 0010204014 WRWK325 Inland MT LLC PONDERA, MT 1 0010204014 WRWK326 Inland MT LLC POWELL, MT 1 0010204014 WRWK327 Pathfinder Wireless Corp. LIBERTY, FL 3 0010207853 WRWK295 SKYRIDER COMMUNICATIONS LLC DESHA, AR 1 0010206370 WRWK297 SKYRIDER COMMUNICATIONS LLC DESHA, AR 2 0010206370 WRWK298 Xtreme Enterprises, LLC POTTER, PA 1 0010202511 WRWK293 Xtreme Enterprises, LLC TIOGA, PA 1 0010202511 WRWK294

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

Could also be something ad simply as getting new roofs.

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:

Dish statement on outage from website second page https://www.dish.com/statement: Thank you for your patience On February 23, we experienced a cybersecurity incident that has affected some of our internal communications, customer call centers, and internet sites. We immediately activated our incident response and business continuity plans to contain, assess and remediate the situation. We retained the services of cybersecurity experts and outside advisors to assist in the evaluation of the situation, and we notified appropriate law enforcement authorities. On February 27, we became aware that certain data was extracted from our IT systems as part of this incident. It’s possible the investigation will reveal that the extracted data includes personal information. The forensic investigation and assessment of the impact of this incident is ongoing. The security of our customers’ data is important to us, and if we learn that information was compromised, we’ll take the appropriate steps and let any impacted customers know. As a result of this incident, many of our customers are having trouble reaching our service desks, accessing their accounts, and making payments. We’re making progress on the customer service front every day, including ramping up our call capacity, but it will take a little time before things are fully restored. DISH TV continues to operate and is up and running.

I believe T-Mobile said this would happen later this year.