Jump to content

Galaxy S22 thread


PythonFanPA

Recommended Posts

19 minutes ago, dkyeager said:

Interesting add! Now if they would just enable the other bands the phone is capable of as well.

  • Like 3
Link to comment
Share on other sites

2 hours ago, PedroDaGr8 said:

Interesting add! Now if they would just enable the other bands the phone is capable of as well.

I was looking to see if they added n70 for Dish, but not yet.

Link to comment
Share on other sites

on the s22 ultra unlocked(U1) firmware. (..2AVF1)
the band selection menu is gone as stated by others.

I noticed that the wifi calling is gone also.
I cant make calls over wifi when there is no cell service or when I force it on wifi calling.

Ive seen s21 ultra users having similar issues on the new update, so I didnt update my s21u.
I wish i didnt for my s22 ultra also

  • Sad 1
Link to comment
Share on other sites

2 hours ago, sunmybun said:

on the s22 ultra unlocked(U1) firmware. (..2AVF1)
the band selection menu is gone as stated by others.

I noticed that the wifi calling is gone also.
I cant make calls over wifi when there is no cell service or when I force it on wifi calling.

Ive seen s21 ultra users having similar issues on the new update, so I didnt update my s21u.
I wish i didnt for my s22 ultra also

Unless you take special steps, the update to force itself upon your phone.

  • Haha 1
Link to comment
Share on other sites

20 hours ago, dkyeager said:

Unless you take special steps, the update to force itself upon your phone.

yup, i dont worry. I have another s21u lying around with its bootloader still on #1. (and updates disabled)
Im keeping that s21 ultra to unlock its bootloader later. hehe

Link to comment
Share on other sites

something felt very weird about the s22u ..2AVF1 update.

my wireless charging stopped working.
i tried the diagnotic thingy in the settings but the phone didnt detect the charger.
my samsung account wouldnt work with any of its apps.
and then my wifi calling wasnt working.


so i figured to turn off my esim. and turn it back on.
my wifi calling came back. and samsung account started working again.
but wireless charging still didnt work.

first, i thought my wireless charging thing in the phone was fried.
so i finally gave up and backed up my phone with smart switch.

manually reflashed the previous firmware (..2AVE4).
I thought since the bootloader is the same the phone would boot up without an issue.
but nope.
so i had to factory reset.

now everything is back to normal.
esim and wifi calling is normal.
wireless charging is back to normal. (thank god its not shorted or w.e)

might wait until the next stable update or stay so i can use the band selection app lol

Edited by sunmybun
  • Like 1
Link to comment
Share on other sites

It's funny that the size was different for AT&T vs T-Mobile. Pretty sure the update on AT&T was over 800MB, the T-Mobile update was only 551Mb. Doesn't look like any of the known issues were fixed on T-Mobile yet. 

  • Like 1
Link to comment
Share on other sites

5 hours ago, IrwinshereAgain said:

So, are we saying it is safe to download the July update on the S22 for Tmobile?

Guess that was the June update that some people were having trouble with on the S22 Ultra.

My S22 basic seems to work OK for me on the June update. 

Guess I will try the July update after all. 

Link to comment
Share on other sites

3 hours ago, IrwinshereAgain said:

OK.  Looks like the Samsung band selector app does not work, which everyone  knew already.  The *#2263# menu comes up but I have not tried to actually force any band changes.

Is that menu working for anyone on Tmo?

Works fine for me.

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

n41-SA went live in my market over the past couple of days. As such, I have been logging a lot of NR. I noticed yesterday while logging that one of the recent updates fixed the slow update rate for NR, it now seems to update at a rate similar to LTE. That alone is a good improvement and will make logging NR much more accurate. 

  • Like 1
Link to comment
Share on other sites

16 minutes ago, PedroDaGr8 said:

n41-SA went live in my market over the past couple of days. As such, I have been logging a lot of NR. I noticed yesterday while logging that one of the recent updates fixed the slow update rate for NR, it now seems to update at a rate similar to LTE. That alone is a good improvement and will make logging NR much more accurate. 

So if you force n41 it works? I've only been able to get it to work when I get handed off from n71 to n41 and it usually only last a couple seconds. If I try to force to n41 via the 2263 menu it just says no service. 

Link to comment
Share on other sites

8 minutes ago, mdob07 said:

So if you force n41 it works?

Correct. I force n41-SA via the 2263 menu and it will connect with any tower which has the capability. To be clear, hand-off between towers is a bit buggy. I will occasionally have to re-enable all bands via the 2263 menu then re-force n41-SA but otherwise it just works. Plus it allowed me to see the second n41 carrier in my area and confirm that it was 40MHz and located at 2570MHz. 

11 minutes ago, mdob07 said:

I've only been able to get it to work when I get handed off from n71 to n41 and it usually only last a couple seconds. If I try to force to n41 via the 2263 menu it just says no service. 

Previously, outside of one or two towers which had it on all the time (no idea why) and the occasional new tower which would have it on for a couple weeks before turning it off, that's how n41-SA behaved for me until a couple days ago. Now, outside of the buggy hand-offs I mentioned above, n41-SA just works. The metro Seattle area tends to be one of the first Nokia markets for changes and the changes then roll out to other markets over the coming weeks/months. So if it doesn't work yet for your area, expect it to come in the near future. 

As an aside, I wonder if they are testing VoNR here. Since I have an S22 instead of an S21, my phone isn't setup for VoNR. 

  • Like 1
Link to comment
Share on other sites

2 hours ago, jreuschl said:

Nothing new added to the 2263 menu in August unfortunately. 

 

How can N77 not even be supported given that they are starting to test this? 

Still no n2 or n25 either. Really surprised on that one since they've publicly shown tests results using an S22 and n25+n41+n41. To me it kind of takes away from the validity of that test since they used some sort of custom firmware, makes you wonder what else they might have modified. Its not really a "stock" device at that point.

  • Like 2
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

    • A heavy n41 overlay as an acquisition condition would be a win for customers, and eventually a win for T-Mobile as that might be enough to preclude VZW/AT&T adding C-Band for FWA due to spreading the market too thinly (which means T-Mobile would just have local WISPs/wireline ISPs as competition). USCC spacing (which is likely for contiguous 700 MHz LTE coverage in rural areas) isn't going to be enough for contiguous n41 anyway, and I doubt they'll densify enough to get there.
    • Boost Infinite with a rainbow SIM (you can get it SIM-only) is the cheapest way, at $25/mo, to my knowledge; the cheaper Boost Mobile plans don't run on Dish native. Check Phonescoop for n70 support on a given phone; the Moto G 5G from last year may be the cheapest unlocked phone with n70 though data speeds aren't as good as something with an X70 or better modem.
    • Continuing the USCC discussion, if T-Mobile does a full equipment swap at all of USCC's sites, which they probably will for vendor consistency, and if they include 2.5 on all of those sites, which they probably will as they definitely have economies of scale on the base stations, that'll represent a massive capacity increase in those areas over what USCC had, and maybe a coverage increase since n71 will get deployed everywhere and B71 will get deployed any time T-Mobile has at least 25x25, and maybe where they have 20x20. Assuming this deal goes through (I'm betting it does), I figure I'll see contiguous coverage in the area of southern IL where I was attempting to roam on USCC the last time I was there, though it might be late next year before that switchover happens.
    • Forgot to post this, but a few weeks ago I got to visit these small cells myself! They're spread around Grant park and the surrounding areas, but unfortunately none of the mmwave cells made it outside of the parks along the lake into the rest of downtown. I did spot some n41 small cells around downtown, but they seemed to be older deployments limited to 100mhz and performed poorly.    
    • What is the cheapest way to try Dish's wireless network?  Over the past year I've seen them add their equipment to just about every cell site here, I'm assuming just go through Boost's website?  What phones are Dish native?  
  • Recently Browsing

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