600 mhz 5G SA is NOT mmWave and should not be treated the same. Your firmware has multiple bugs that "turn off 5g" radio for a number of different causes.... all of them invalid for 600mhz NR and causing total failure of extended range 600mhz 5G in situations where it should be working without issues. Phone constantly disconnecting for no valid reason when 5G is cut off for no valid reason and other alternative signals (lte) aren't available.
Like why turn off the 5G radio because a graphics intensive app is causing device heating? The heat and 5G radio are unrelated. (It's NOT mmWave!!).
And why does 5G get turned off if any lte bands are enabled, phone is connected to 5G SA and a phone call is placed?
Other bugs that turn off 5G appear to use motion sensors!?
Please at least add options in developer settings to "prevent 5G from being turned off"
So those of us in affected service areas can continue to use Samsung phones.
VoNR works perfectly if I use Samsung band selection to disable all the lte bands.
So for the phone app to automatically assume and "turn off 5g" if any lte band is enabled and a phone call is placed is clearly a bug. It doesn't even bother to check if lte is even available, it just "turn off 5g"
please add developer option to "prevent 5G from being turned off"
at least the phone app checks to see if any lte bands are even enabled before automatically "turn off 5G" but it doesn't check if there's actually an lte signal or not.
The thermal guardian that "turn off 5g" when graphics processor warms the phone doesn't even check if lte bands are even enabled. (not to mention the heat has nothing at all to do with 5G 600mhz and turning that off has no effect)
Other procs that "turn off 5G" for whatever mysterious reasons like "signal worse than -110dbm and motion detected" or whatever their problem is don't check for lte availability either, they just "turn off 5g"
If I go to an area with strong lte service as well as the n71 sa the phone isn't dropped from the network when "turn off 5g" it switches to the lte.
It's related to signal in some cases, but the connection isn't being dropped due to technical difficulties with a lower strength signal... the firmware is literally: "turn off 5G"
The two triggers I mentioned in my OP are clear evidence of that.
While it's true that my carrier doesn't provide an lte signal here and that causes the phone to disconnect when the 5G standalone is TURNED OFF inappropriately by the firmware... The phone is the limitation that's preventing functionality.
This is 600mhz STANDALONE 5g, it's not mmWave and it's not NSA 5g so stop treating it like it is.
and T-Mobile tells me they have no plans to turn lte back on, that the 5G signal is all they will provide "for the foreseeable future"
