Jump to content

Galaxy S22 thread


PythonFanPA

Recommended Posts

22 minutes ago, PedroDaGr8 said:

Which code? *#73#?

Download SamFW FRP tool 3.1 or latest version from here.
Open SamFW FRP tool and connect your phone to the computer with a USB.
Using SamFW FRP tool, go to MTP tab and click on "Enable Secret Code for Verizon". See the picture below. Note it works on any US CSC even though it says "for Verizon".

 

That part.

The codes do not work for me, I assume without going through these extra steps.

  • Love 1
Link to comment
Share on other sites

26 minutes ago, jreuschl said:

Download SamFW FRP tool 3.1 or latest version from here.
Open SamFW FRP tool and connect your phone to the computer with a USB.
Using SamFW FRP tool, go to MTP tab and click on "Enable Secret Code for Verizon". See the picture below. Note it works on any US CSC even though it says "for Verizon".

 

That part.

The codes do not work for me, I assume without going through these extra steps.

This is correct, the purpose of the Enable Secret Code portion is so that you can use the *#73# code. This code is the one that allows you to move back into the desired Service Menu. 

Link to comment
Share on other sites

1 hour ago, PedroDaGr8 said:

This is correct, the purpose of the Enable Secret Code portion is so that you can use the *#73# code. This code is the one that allows you to move back into the desired Service Menu. 

Got it, now I see all of the options that were shown here.

https://twitter.com/milanmilanovic/status/1564659165183844353/photo/1

Now we'll see if this translates into anything in the real world!

I finally found a 1+gbps site in rural Indiana a few days ago (I have not seen any in the Milwaukee area yet)

  • Like 1
Link to comment
Share on other sites

I can't get past the waiting for DIAG step. I've got the Samsung drivers installed and i did the setting in the *#0808# menu. Not sure what I'm doing wrong...

Link to comment
Share on other sites

2 hours ago, mdob07 said:

I can't get past the waiting for DIAG step. I've got the Samsung drivers installed and i did the setting in the *#0808# menu. Not sure what I'm doing wrong...

Do you have USB Debugging enabled?

- Trip

Link to comment
Share on other sites

1 hour ago, Trip said:

Do you have USB Debugging enabled?

- Trip

Yeah, ended up switching to my laptop and doing the exact same steps including installing the Samsung drivers and it worked on the first try. 

  • Like 2
Link to comment
Share on other sites

1) Does s22 have SCP n7 problem instead of n41? Curious if so, does android 13 fix it?

2) Curious if band selector app or other method allows band selection. Does latest samfw method still work with 13?

Link to comment
Share on other sites

6 hours ago, dkyeager said:

1) Does s22 have SCP n7 problem instead of n41? Curious if so, does android 13 fix it?

2) Curious if band selector app or other method allows band selection. Does latest samfw method still work with 13?

1) Mike's recent changes have fixed that issue for me. That being said, the real cause is the underlying code that assigns bands in Android. Rather than polling the baseband to determine the band, it looks at the ARFCN and compares it to a list of ARFCNs and band assignments. This was a reasonable process in the LTE days because ARFCNs were unique between bands. So a B41 ARFNC was totally different from a B7 ARFCN which was totally different from a Band 40 ARFCN. NR does away with this practice and makes the ARFCNs frequency specific rather than band and frequency specific. As a result, the function now returns the first result it encounters (basically the lowest band). At this time, Google has not fixed this issue in Andorid though CellMapper has opened a ticket.

 

2) Supposedly Beta 5 ended up being the Stable and SamFW still works on that. Until I receive an update that I am for sure is a stable release, I won't know for certain. As for the Band Selector app, it is unfortunately permanently dead. The only way to select bands from here on out is via the ServiceMenu (*#73# or *#2263#). 

  • Like 1
Link to comment
Share on other sites

Factory unlocked users take note: https://www.reddit.com/r/tmobile/comments/yi5klm/removed_band_confusion/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

 

I wonder how this affects roaming. Normally factory unlocked phones should have more band choices, especially overseas.

Link to comment
Share on other sites

4 hours ago, dkyeager said:

Factory unlocked users take note: https://www.reddit.com/r/tmobile/comments/yi5klm/removed_band_confusion/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

 

I wonder how this affects roaming. Normally factory unlocked phones should have more band choices, especially overseas.

He edited/added this at the end:

"Edit. I'm bumb (dumb) and didn't realize that the firmware could change based on the sim card installed."

  • Like 1
Link to comment
Share on other sites

Apparently the s-22 STILL has access to band lock enabled via the #*2263# service menu after installing Android 13????

I want to be sure I can still lock out certain bands at times.  What I hear appears to suggest this is still working but I want to be positive before allowing the update.

Link to comment
Share on other sites

8 minutes ago, chamb said:

Apparently the s-22 STILL has access to band lock enabled via the #*2263# service menu after installing Android 13????

I want to be sure I can still lock out certain bands at times.  What I hear appears to suggest this is still working but I want to be positive before allowing the update.

Still works on my end but I might not the best example.

Link to comment
Share on other sites

9 minutes ago, PedroDaGr8 said:

Still works on my end but I might not the best example.

 OK. Thanks for the answer.  Apparently you have the Ultra that COULD be different. I still might hesitate until somebody with a s22 replies.   I sure do not want to lose the ability to band select.

Link to comment
Share on other sites

4 hours ago, chamb said:

 OK. Thanks for the answer.  Apparently you have the Ultra that COULD be different. I still might hesitate until somebody with a s22 replies.   I sure do not want to lose the ability to band select.

It still works on my S22 after upgrade to the final official release. 

(It also worked during the betas although the settings got reset  a couple of times - that might have been my error).

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

24 minutes ago, comintel said:

It still works on my S22 after upgrade to the final official release. 

(It also worked during the betas although the settings got reset  a couple of times - that might have been my error).

OK, Thanks for the confirmation.  I live between a couple of sites all of which are on the fringe and N-71 tries to aggregate with band 2 or 4.  When it does manage to aggregate, the data will not flow.  Band 2 or 4 will work fine alone, but not with N-71.  N-71 will have  a SINR of zero or maybe 1.  That results in data freezing and refusing to work.

So, I have to disable band n71.

Link to comment
Share on other sites

12 minutes ago, chamb said:

OK, Thanks for the confirmation.  I live between a couple of sites all of which are on the fringe and N-71 tries to aggregate with band 2 or 4.  When it does manage to aggregate, the data will not flow.  Band 2 or 4 will work fine alone, but not with N-71.  N-71 will have  a SINR of zero or maybe 1.  That results in data freezing and refusing to work.

So, I have to disable band n71.

Oh absolutely - the only way I get a usable signal here in North West Raleigh is by locking to LTE band 41.  Otherwise it continually cycles at low speeds between 2, 4, 71 and no signal.  Left to its own ways, It also like to try 5G occasionally before dropping it when it gets zero throughput.

It's funny but the old Sprint LTE band 41 tower is completely reliable and good speeds even at -130 dBm where as the T-Mobile bands are all flaky even at -107 dBm - maybe it is overlapping signals from multiple towers causing the problems?

Edited by comintel
Link to comment
Share on other sites

or not... SMH, this is stupid......

I am not anti-racial.. but.. I want some who speaks my native language.

Their system was having multiple issues with multiple things, and she kept telling me to do the same thing over and over, that we had already tried 6 times before.....

 

Link to comment
Share on other sites

2 hours ago, floorguy said:

or not... SMH, this is stupid......

I am not anti-racial.. but.. I want some who speaks my native language.

Their system was having multiple issues with multiple things, and she kept telling me to do the same thing over and over, that we had already tried 6 times before.....

 

Time to ask to for the next level or say you have a meeting you have to go to and you will be back another day.

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

×
×
  • Create New...