<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Re: Samsung 5g bugs in Galaxy S22</title>
    <link>https://us.community.samsung.com/t5/Galaxy-S22/Samsung-5g-bugs/m-p/2676345#M66497</link>
    <description>&lt;a href="https://us.community.samsung.com/t5/user/viewprofilepage/user-id/36635498"&gt;@270&lt;/a&gt;&lt;BR /&gt;no, it's definitely the phone firmware.&lt;BR /&gt;&lt;BR /&gt;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"&lt;BR /&gt;&lt;BR /&gt;The two triggers I mentioned in my OP are clear evidence of that.&lt;BR /&gt;&lt;BR /&gt;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...&lt;BR /&gt;The phone is the limitation that's preventing functionality.&lt;BR /&gt;&lt;BR /&gt;This is 600mhz STANDALONE 5g, it's not mmWave and it's not NSA 5g so stop treating it like it is.&lt;BR /&gt;&lt;BR /&gt;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"</description>
    <pubDate>Fri, 29 Sep 2023 16:40:58 GMT</pubDate>
    <dc:creator>ThymeFlowsOverStones</dc:creator>
    <dc:date>2023-09-29T16:40:58Z</dc:date>
  </channel>
</rss>

