<?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>Rakumei Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>Rakumei Tracker</description>
    <pubDate>Mon, 16 Jan 2023 10:25:43 GMT</pubDate>
    <dc:date>2023-01-16T10:25:43Z</dc:date>
    <item>
      <title>A fix for wireless controller pairing not working in Chrome</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/A-fix-for-wireless-controller-pairing-not-working-in-Chrome/m-p/22893#M1131</link>
      <description>&lt;P&gt;I don't know about you, but signing in from incognito mode to get wireless controller pairing to work in Chrome was getting annoying. Luckily, I found a fix.&lt;BR /&gt;&lt;BR /&gt;If you're running an adblock software, go in and whitelist&amp;nbsp;&lt;STRONG&gt;yeti.client-channel.google.com&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I dug around in the logs of my adblocker and found that this domain was being called when stadia is opened. Whitelisting this URL solved all issues I had pairing my controller outside of incognito mode. I hope it works for you!&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2020 01:21:27 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/A-fix-for-wireless-controller-pairing-not-working-in-Chrome/m-p/22893#M1131</guid>
      <dc:creator>Rakumei</dc:creator>
      <dc:date>2020-05-21T01:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Why is 4g blocked?</title>
      <link>https://community.stadia.com/t5/Stadia-General/Why-is-4g-blocked/m-p/22892#M10711</link>
      <description>&lt;P&gt;It would be a nice feature but just a word of caution to the overly-optimistic. Stadia would probably play like garbage on a mobile data connection. This is probably part of Google's calculus as well. The reason is the latency. Towers are far away. Communication is limited by physics. Current esimates for 4g latency put it anywhere from 100-600ms on average. Which is...really bad.&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2020 00:20:20 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-General/Why-is-4g-blocked/m-p/22892#M10711</guid>
      <dc:creator>Rakumei</dc:creator>
      <dc:date>2020-05-21T00:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Controller doesn't connect to browser when using 5 GHz network</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Controller-doesn-t-connect-to-browser-when-using-5-GHz-network/m-p/22891#M1130</link>
      <description>&lt;P&gt;I can confirm as well. Doesn't work in regular mode. Only incognito. I went through the massive pain of doing away with all my extensions just to see if that was the culprit, but it wasn't.&lt;/P&gt;&lt;P&gt;This is a MASSIVE inconvenience with a password manager-generated password and 2FA so hopefully they get it resolved soon.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2020 00:14:56 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Controller-doesn-t-connect-to-browser-when-using-5-GHz-network/m-p/22891#M1130</guid>
      <dc:creator>Rakumei</dc:creator>
      <dc:date>2020-05-21T00:14:56Z</dc:date>
    </item>
  </channel>
</rss>

