PedroDaGr8

29 minutes ago, floorguy said:

Yup, got 1, then the other popped up right after.. 
It was kind of weird

Has anyone gotten a recent Play System Update? Mine has been stuck on October. Wonder if Samsung screwed something up again. 

14 hours ago, Mooeydj said:

January is out already now too.

Wow. didn't expect them to be released that close together.

December patch is out for TMO locked

Over three years after the Sprint site was turned off and over two years after the TMO conversion was complete, the Cedar Park Christian School site, SW of the 405/522 interchange, has finally gone live. At this point it only serves that immediate area because the four other local sites have the interstate well covered.

Also, with respect to that permit for Bellevue that didn't make sense, I saw that TMO has filed a permit in Bellevue to decommission one of the nearby sites (SE03310A, eNB 81750/99542). That makes a tad more sense but they could still easily decommission two others in that area and still have great coverage. 

On 12/30/2023 at 4:48 AM, jreuschl said:

Guess T-Mobile locked won't get a December security update in December. 

TMo and randomly timed updates. No surprise. 

21 hours ago, jreuschl said:

Running well so far I think. I notice RCS is still not moved over to Jibe.

Running well for me as well.

The island sites have always intrigued me, so many sites floating out in the sound. I just don't h ad out there enough to map those. 

11 hours ago, mikejeep said:

Thank you for the detailed testing results and for sending diagnostics! I was able to identify what was causing those crashes, the fix will be included in the next update.

Glad that it helped! Unfortunately, I won't be able to test on Android 13 anymore. TMo just rolled out Android 14 for the S22U.

9 hours ago, mikejeep said:

Another SCP beta update is rolling out now with a few more bugfixes. If this version proves to be stable, non-beta users can expect to receive it later this week. Thanks for all of the feedback and support!

Just tested the new version on Android 14, everything behaves itself well.

One UI 6.0 dropped for TMO locked this morning! A hefty 3.5GB update!

Sent you a diagnostic report. I did similar, removed all of the permissions (Networking, Phone, and Notifications) and then performed the update. When I started the app, it asked for location permission (but not the other two). I intentionally chose approximate to see how it would handle it.  The app handled this without a problem; it popped up a message explaining that it needed precise location and how to give it that permission.

After giving it precise permission and going back to the app, the app closed itself. From this point, this is where things fell off the rails. When I attempted to reopen the app, it would either immediately close itself or load and show nothing. The latter is expected because it didn't have phone permission but the app also didn't ask for it (or notification permission). I tried this repeatedly with it closing itself around 80-90% of the time and staying open a couple others. Oddly enough, a minute or so after closing the app for the last time, the phone and notification permission request prompts popped up. I have no idea what happened there but I gave the app those permissions and reloaded the app with everything as it should be. 

EDIT: I just attempted to reproduce it and noticed it did not prompt me with the option to "Allow all the time" from the pop-up. I had to go manually enable it. Most of the other behavior is similar other than if I manually selected "Exit" from the menu, that this time it immediately popped up the two permission request prompts upon exit. 

EDIT2: Tried it a third time and I tried backing out of the app. This time when I reopened the app it popped up a SignalCheck warning message (similar to the location one) saying that the Phone permission is blocked and how to enable it. This did not show up in the previous attempts.

The UW Bothell site (northwest corner of the 522/405 interchange) went live just before Thanksgiving. 

This is a permit I do NOT understand: https://permitsearch.mybuildingpermit.com/PermitDetails/23 126540 LJ/Bellevue

This area in Bellevue is already REALLY well covered by multiple sites on either side of the 405. Unless they are planning on decommissioning a bunch, adding this one really makes no sense. 

Also with big updates like this, wipe the cache partition. It helps ensure any lingering cached settings are removed.

I still haven't received either update on my S22U.

3 hours ago, PythonFanPA said:

Welp  not 14 release yet, but just checked & pulled November sec patch

That matches the reports that Samsung is just rolling out the Stable build to beta testers in Europe. I estimate Dec or Jan before TMo gets around to releasing it. 

October Google Play system update is out.

On 10/18/2023 at 6:51 AM, Mooeydj said:

Hmmm, I just downloaded it and it said 10mb. Weird.

There were two for me. One 10MB one and a 1ish MB one.

2 hours ago, S4GRU said:

We have to opt out to keep our Lifetime pricing.  Nice.  But at least we get to keep it. For now.

Robert

There sleazy way of raising people's rates while technically not raising people's rates.

Wow, October Security Patch is already out for TMO locked.

TMO filed a permit to upgrade one of the few remaining non-upgraded TMO sites in the Kirkland area (the monopole site in Kingsgate). At this point, the only ones I can think of that aren't upgraded and don't have  a permit are:

• the NE 104th St site that overlooks Forbes Creek area - that one is likely going to be obsoleted by the new tower going in at the Pines Apartment building
• the McAulliffe park site 

5 hours ago, jreuschl said:

Sounds like the S22 One UI beta 6 is available but not for T-Mobile locked this time?? 

Seems like maybe only plain S22 for TMO is available at this time. I definitely don't see it for my S22U.

September update is out (TMO locked S22U). Pretty light at 382mb

2 hours ago, mikejeep said:

Thanks, should be resolved in next update, which should be out today. Thankfully in July the Android development team reported that the 5G-NR band identification bug was finally resolved on Pixel devices, hopefully similar patches make it to other devices soon.

That's great news!

1 hour ago, red_dog007 said:

Few weeks ago I noticed that 3.7GHz was active on AT&T in my area. Had it basically down the whole interstate, some 15 miles. But it was only 2xCA.  Usually paired with PCS. The signalcheckpro app showed it as 80MHz with a center frequency of 3871.20MHz.  Ok, cool.  Assumed it was 3830 to 3910MHz.  I couldn't remember the exact band layout while I was driving.  Looking at it just now on Spectrum Omega, that was way wrong. AT&T owns B4 through C2, or 3860MHz to 3940MHz.

So instead of having a single 80MHz carrier, it is really 4 carriers? I have a Pixel 7, so not sure if it is 5xCA or 6xCA, but 4 carriers will be taken up by 3.7GHz? With that spectrum ownership, I would have figured a single 80MHz carrier with a center frequency of 3900MHz. Then I could CA 4 or 5 other carriers and be connected to upwards of 200MHz.

Some phones report the SSB instead of the center frequency. In LTE they were the same but in NR the SSB can be any frequency within the range. It makes it a huge pain to identify the center frequency. 

August Play Store update is finally out. Still not a peep for the Sept. Security Update.