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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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