Jump to content

Connecting to SID 22429!


Recommended Posts

Shentel apparently flipped the switch (or Sprint accepted or however it works) on a few upgraded towers in the Lebanon Pa area. My brother reports LTE (and has mapped some on Sensorly) and I am connecting to SID 22429.

 

Now for a couple of questions....

 

SID 22429 is a 800 mhz SID for Utah....this is PA?

 

My phone reports SID 22429 but 1900 MHZ in the advanced menu screen?

 

My Debug screen shows

 

SID 22429

Band Class 10

Channel 476

 

What am I actually connected to, 1900 or 800? The SID would indicate 800 and I believe band class 10 is also 800 but my advanced menu screen reports 1900 and I have never seen this report incorrectly before.

Link to comment
Share on other sites

 

You would need the 800SMR testing PRL to connect to that 22429.

 

Sent from my little Note2

 

 

Unless you are in a market that is up and running with the line prl.

 

Can we get a list of those markets?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • The DAS at LGA Terminal B actually has n41 at 100+20, but if you are deprioritized, good luck on the busy days, as all the bands are congested, even B41 and n41, with data being worse than 128kbps international roaming. It has SA active for n41 as well. The L train tunnel is actually 80+20 for n41, with SA n41 active. Speeds aren't anything compared to Philadelphia's DAS system that has n41 though. The gig+ upgrades are expanding, as eNBs 894588 (Sprint convert site) and 55987 can both pass 1 Gbps now. Clocked nearly 1.3Gbps on eNB 55987 today.
    • Hopefully this goes thru!  https://www.reddit.com/r/tmobile/comments/1211mh7/tmobile_files_another_sta_application_to/
    • Yup 80MHz C-band + 40MHz DoD for a total of 120MHz. They should be pretty well setup post-clearance. — — — — — Famous Verizon site on Atlantic referenced in this reddit post got moved to the top of the building next door. — — — — — Also looks like I mapped a T-Mobile oDAS node eNB 347812 in Brooklyn Heights. Streetview shows it as one of the CC nodes with no antenna on top as of May 2022 but this specific eNB was first mapped this month. I didn't notice that I mapped it until I got home but the range on it is significantly greater than the normal "antenna-less" nodes T-Mobile deploys. I'm wondering if it got upgraded to the new 5G oDAS design but I won't be able to check it out until next weekend.  
    • I didn't know they had access to 80 MHz of c-band that does change some things then once that's online
    • While I've been loath to update my Samsung devices past the May 2022 update to keep the Band Selection tool, I note that it looks like Android 14 is going to add Timing Advance for NR to the API.  (Was looking today as I have another Verizon A42 5G now that I'm going to unlock for T-Mobile, and wanted to figure out if I should let it update or not.)  Since I can technically make band changes from *#73#, on the A42 5Gs, I can probably live without the Band Selection tool if a later Android version adds something useful like TA values. I assume SCP will be updated to support that once it becomes publicly available.  The real question is whether or not the phones will support it.  My S21FE and A42 5G devices do on LTE, but I know the S22 and the A32 5G do not support it even on LTE, providing just zero in that field. - Trip
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...