Jump to content

Galaxy S20 Series Discussion


mdob07

Recommended Posts

I got the S20 FE about a week ago. Couldn't activate it with either my Sprint SIM or the T-Mobile SIM that shipped with the phone. Took it to the local store, they finally got it to activate with the third SIM they tried. Don't know what was up with that, but I'm now on Tmo.

All things considered, I'm pretty happy. Signal strength is comparable to what I had with my LG V30+, and throughput seems faster. I do notice the phone switches bands pretty frequently. Not sure why that is, as signal strength doesn't seem borderline most of the time.

I don't know very much about the various T-Mobile bands. I've seen references to a Samsung Band Selector app, but I don't really want to mess around with that until I learn more about the bands themselves. Does anybody have a link to a post/site with basic band information? I imagine there's plenty of info in the Signal Check thread, but that's a mighty big haystack to search for a needle 😃

Thanks,

Jim

Link to comment
Share on other sites

2 hours ago, jlbattagli said:

I got the S20 FE about a week ago. Couldn't activate it with either my Sprint SIM or the T-Mobile SIM that shipped with the phone. Took it to the local store, they finally got it to activate with the third SIM they tried. Don't know what was up with that, but I'm now on Tmo.

All things considered, I'm pretty happy. Signal strength is comparable to what I had with my LG V30+, and throughput seems faster. I do notice the phone switches bands pretty frequently. Not sure why that is, as signal strength doesn't seem borderline most of the time.

I don't know very much about the various T-Mobile bands. I've seen references to a Samsung Band Selector app, but I don't really want to mess around with that until I learn more about the bands themselves. Does anybody have a link to a post/site with basic band information? I imagine there's plenty of info in the Signal Check thread, but that's a mighty big haystack to search for a needle 😃

Thanks,

Jim

Have a couple posts that might help to at least get you started.

On 6/25/2021 at 2:53 PM, Dkoellerwx said:

Depends on if you are wanting to use T-Mobile or "Sprint" bands. 

B25 - PCS on Sprint. Most channels have been narrowed to 5Mhz.
B26 - SMR on Sprint. 5Mhz channel.

B2 - PCS on T-Mobile - channel widths vary from 5Mhz to 20Mhz. May have multiple channels.
B4/66 - AWS on T-Mobile - channel widths vary from 5Mhz to 20Mhz. May have multiple channels.
B12 - 700 on T-Mobile - usually a 5Mhz channel. Some areas may have 10Mhz. 
B71 - 600 on T-Mobile - Usually a 5Mhz channel. Some areas may have 10Mhz.

B41 - this is a little tricky. T-Mobile has 2x20 channels on most sites with n41. But Sprint B41 is still on air as well.

n71 - 5G on 600, channel width vary from 10 to 20Mhz.
n41 - 5G on 2500, channel widths vary from 40 to 100Mhz.
n66 - 5G on AWS, coming soon. A few select locations on air, but not sure on channel widths.
n25 - 5G on PCS, coming soon.
n260/261 - 5G on mmWave, very select deployment in a few large cities. Channel usually 100Mhz.

There are a couple more posts relating to the band selector following the post quoted below.

On 6/24/2021 at 7:32 PM, Dkoellerwx said:

When you open the app, select "Launch Band Selection." That will open a menu that likely looks familiar. Now, swipe from the left, or tap the menu bar at the top. Select "Band Selection" again. This will show you all of LTE and NR bands your phone is capable of receiving. Select the band(s) you want, then toggle "Selection" on the top right. Apologies if you already tried that, but it sounded like you only got to the first menu.

 

Link to comment
Share on other sites

  • 2 weeks later...
On 7/27/2021 at 11:13 AM, mdob07 said:

Finally got the July update on my AT&T phone this morning. 790 MB. Still waiting for it to hit my T-Mobile phone. 

Still not out for my T-Mobile phone. It's funny that the June update came out super fast and now it'll be August before they push the July update. 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
On 7/31/2021 at 2:27 PM, mdob07 said:

Still not out for my T-Mobile phone. It's funny that the June update came out super fast and now it'll be August before they push the July update. 

Almost 2 weeks later and still no July update. The last time there was a big delay it affected AT&T also but my AT&T S20 got the July update almost 3 weeks ago. I'm really hoping this update finally adds N2 and N66 when it finally comes. 

Link to comment
Share on other sites

9 hours ago, mdob07 said:

Almost 2 weeks later and still no July update. The last time there was a big delay it affected AT&T also but my AT&T S20 got the July update almost 3 weeks ago. I'm really hoping this update finally adds N2 and N66 when it finally comes. 

Only the plus and ultra support N2 and N66 right?  Actually, i wasnt even aware these were disabled right now.  has there been chatter that these would be enabled sometime soon or just wishful thinking?

Link to comment
Share on other sites

3 hours ago, swintec said:

Only the plus and ultra support N2 and N66 right?  Actually, i wasnt even aware these were disabled right now.  has there been chatter that these would be enabled sometime soon or just wishful thinking?

n66 is active on my S21 Ultra, so if the device supports it I would think they would allow it to be turned on soon since n66 is going live in some markets. I believe T-Mobile is going with n25 rather than n2 to make use of the Sprint PCS G-Block, but that is not enabled on any device that I am aware of yet.

Link to comment
Share on other sites

4 hours ago, swintec said:

Only the plus and ultra support N2 and N66 right?  Actually, i wasnt even aware these were disabled right now.  has there been chatter that these would be enabled sometime soon or just wishful thinking?

It's enabled on my AT&T s20 Ultra, they enabled it several months ago, maybe even late 2020. My T-Mobile S20 plus only has n41, n71, n260, and n261 enabled right now.

  • Like 1
Link to comment
Share on other sites

19 hours ago, mdob07 said:

It's enabled on my AT&T s20 Ultra, they enabled it several months ago, maybe even late 2020. My T-Mobile S20 plus only has n41, n71, n260, and n261 enabled right now.

can you share the dialer codes so i can see this info on my s20+?  the ones i used to use for sprint dont work since i swapped SIMs.  no way for you to enable n2 and n66 yourself in the menus?

Link to comment
Share on other sites

51 minutes ago, swintec said:

can you share the dialer codes so i can see this info on my s20+?  the ones i used to use for sprint dont work since i swapped SIMs.  no way for you to enable n2 and n66 yourself in the menus?

On a T-Mobile sim you can use *#2263# to get into that menu. There used to be a workaround on xda that worked to let you enable bands the phone was capable of but were firmware disabled, but that quit working with one UI 3.0. All I see on my S20+ are what I mentioned above. 

  • Like 1
Link to comment
Share on other sites

18 hours ago, IrwinshereAgain said:

Just got the August update on the S20 FE 5G.

I just checked again on my T-Mobile S20+, it's still saying up to date with the June 1st update. 

  • Like 1
  • Sad 1
Link to comment
Share on other sites

40 minutes ago, IrwinshereAgain said:

My Tab S6 was just updated to the August patch.  Hopefully your S20+ will not be far behind.

Funnily enough I was about to post the same thing. My Tab S6 updated today. Honestly at this point I feel like whoever is in charge of pushing the update out either forgot about it or missed it. I expect the August update any day on my AT&T S20 Ultra.

  • Like 1
Link to comment
Share on other sites

As I expected my AT&T S20 ultra got the August update this morning. My T-Mobile S20+ is still happy with the June update. Whatever the holdup is it's only affecting T-Mobile as far as I can tell. I wonder if they'll still push the July update and then the August update separately or just roll them together at this point. 🤷‍♂️

Link to comment
Share on other sites

11 hours ago, mdob07 said:

I just noticed, after the update SA N41 is missing now. It's just NSA N41 and SA/NSA N71. Wonder why they removed it. 🤦‍♂️

Yup just notice it on mine also

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

  • Similar Content

  • Posts

    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
  • Recently Browsing

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