<?xml version="1.0" encoding="UTF-8"?> 
<rss version="2.0"
        xmlns:content="http://purl.org/rss/1.0/modules/content/"
        xmlns:wfw="http://wellformedweb.org/CommentAPI/"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
        xmlns:atom="http://www.w3.org/2005/Atom"
        xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
        xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
        >
<channel>
  <title>asgaard</title>
  <description>Pokemon</description>
  <link>https://blog.asgaard.co.uk/t/pokemon</link>
  <lastBuildDate>Thu, 16 Apr 26 20:20:10 +0000</lastBuildDate>
  <language>en</language>
  <count>2</count>
  <offset>0</offset>
      <item>
    <title>Pokémon GO is discontinuing support for 32 bit Android devices</title>
    <link>https://blog.asgaard.co.uk/pokemon-go-32-bit</link>
    <pubDate>Sat, 13 Jun 20 11:20:10 +0000</pubDate>
    <guid>https://blog.asgaard.co.uk/pokemon-go-32-bit</guid>
    <description><![CDATA[
<p>
<strong>Update:</strong> Niantic has backed away from this and announced that they are deferring this decision after all.<hr/>
<p>
Niantic, the company behind Pokémon GO, announced recently that <a href='https://www.pokemongolive.com/en/post/32-bit-android-discontinued-support/'>Pokemon GO will no longer work on 32 bit Android devices from August</a>. You&#039;d be forgiven for having missed this, as although it&#039;s on the official blog, it doesn&#039;t show in the in-game news.
<p>
Whilst the announcement makes it sound like only older devices will be affected, this is not the case. Many newer Android phones ship with 64 bit hardware, but a 32 bit operating system, in which case they are, for all practical purposes, 32 bit devices and are restricted to running 32 bit apps.
<p>
Unless a device has more than 4GB of RAM, there&#039;s not any great advantage to using a 64 bit OS, so a lot of budget phones come with a 32 bit operating system. For example, a large number of devices in the Motorola G range and the Samsung A and J ranges have only a 32 bit OS, even some of those released in the last 12 months. The Silph Road co[...]]]></description>
    <content:encoded><![CDATA[
<p>
<strong>Update:</strong> Niantic has backed away from this and announced that they are deferring this decision after all.<hr/>
<p>
Niantic, the company behind Pokémon GO, announced recently that <a href='https://www.pokemongolive.com/en/post/32-bit-android-discontinued-support/'>Pokemon GO will no longer work on 32 bit Android devices from August</a>. You&#039;d be forgiven for having missed this, as although it&#039;s on the official blog, it doesn&#039;t show in the in-game news.
<p>
Whilst the announcement makes it sound like only older devices will be affected, this is not the case. Many newer Android phones ship with 64 bit hardware, but a 32 bit operating system, in which case they are, for all practical purposes, 32 bit devices and are restricted to running 32 bit apps.
<p>
Unless a device has more than 4GB of RAM, there&#039;s not any great advantage to using a 64 bit OS, so a lot of budget phones come with a 32 bit operating system. For example, a large number of devices in the Motorola G range and the Samsung A and J ranges have only a 32 bit OS, even some of those released in the last 12 months. The Silph Road community on Reddit has started to assemble a <a href='https://docs.google.com/spreadsheets/d/1C_Duthd5nqf1JNs4fQC-UQpyBf_xByS9f_I9nmqw-tU/edit#gid=0'>list of modern devices that will be affected by this change</a>.
<p>
Unfortunately, it&#039;s not clear that Niantic has understood the distinction between the architecture of the CPU and the architecture of the operating system. The devices in their list of examples all have 32 bit CPUs. It is very possible that they have made this decision based on data collected on hardware, and have not looked at operating system architecture data. I suspect the fact they&#039;ve given this quite a low-profile announcement means they have estimated that this will not affect many people, and I also suspect that it will actually affect a large number of people. This seems like the kind of announcement that should be made 12 months in advance, not 6 weeks.
<p>
For those who will be affected by this, I recommend waiting until closer to August before replacing your device. Niantic may have made a mistake and may yet back down.
<p>
It&#039;s also worth noting that it&#039;s actually quite difficult to determine if you&#039;re buying a 32 bit or 64 bit device, as a lot of manufacturers don&#039;t publish this information. If you do need to replace your device, choose carefully.]]></content:encoded>
  </item>
      <item>
    <title>Giovanni&#039;s Persian</title>
    <link>https://blog.asgaard.co.uk/pokemon-go-giovannis-persian</link>
    <pubDate>Mon, 03 Feb 20 20:28:38 +0000</pubDate>
    <guid>https://blog.asgaard.co.uk/pokemon-go-giovannis-persian</guid>
    <description><![CDATA[
<p>
<img src='/assets/media/giovanni.jpg' class='width-100 no-touch center' alt=''/>
<p>
<div class='contents'><strong>Contents:</strong><ol><li><a href='#h_3a4718573d9fedf3b3f8f88e2119748b'> So, what&#039;s wrong with Machamp? </a></li><li><a href='#h_4520fd6c1244e7be0766cd42bf1f8537'> So, what should we use instead? </a></li></ol></div>
<p>
Just how do you take down Giovanni&#039;s Persian in <strong>Pokémon Go</strong>?
<p>
Persian is a normal type Pokémon, so, obviously, you want a fighting type Pokémon, and everyone knows the king of fighting types is Machamp, right?
<p>
Well that&#039;s what I thought until I spent Saturday afternoon trying to defeat him and his Persian with (one of) my prize Machamp. The other Pokémon weren&#039;t too difficult, but the Persian was wrecking me and Machamp wasn&#039;t pulling his (substantial) weight.<h2 id='h_3a4718573d9fedf3b3f8f88e2119748b' 2> So, what&#039;s wrong with Machamp? </h2>
<p>
The problem is that Machamp goes down too quickly to get off a charged attack. My CP 2900 Counter + Dynamic Punch Champ was VERY close to getting off his first charged attack, but he was consistently fainting right before he got chance. That&#039;s a big problem, because it means you&#039;re bringing out your second Pokémon and Giovanni hasn&#039;t even used one of his shields yet, and he&#039;s about to mak[...]]]></description>
    <content:encoded><![CDATA[
<p>
<img src='/assets/media/giovanni.jpg' class='width-100 no-touch center' alt=''/>
<p>
<div class='contents'><strong>Contents:</strong><ol><li><a href='#h_3a4718573d9fedf3b3f8f88e2119748b'> So, what&#039;s wrong with Machamp? </a></li><li><a href='#h_4520fd6c1244e7be0766cd42bf1f8537'> So, what should we use instead? </a></li></ol></div>
<p>
Just how do you take down Giovanni&#039;s Persian in <strong>Pokémon Go</strong>?
<p>
Persian is a normal type Pokémon, so, obviously, you want a fighting type Pokémon, and everyone knows the king of fighting types is Machamp, right?
<p>
Well that&#039;s what I thought until I spent Saturday afternoon trying to defeat him and his Persian with (one of) my prize Machamp. The other Pokémon weren&#039;t too difficult, but the Persian was wrecking me and Machamp wasn&#039;t pulling his (substantial) weight.<h2 id='h_3a4718573d9fedf3b3f8f88e2119748b' 2> So, what&#039;s wrong with Machamp? </h2>
<p>
The problem is that Machamp goes down too quickly to get off a charged attack. My CP 2900 Counter + Dynamic Punch Champ was VERY close to getting off his first charged attack, but he was consistently fainting right before he got chance. That&#039;s a big problem, because it means you&#039;re bringing out your second Pokémon and Giovanni hasn&#039;t even used one of his shields yet, and he&#039;s about to make you use one of yours.
<p>
That&#039;s the important thing for the first Pokémon - you need to be breaking down the shields. Machamp has a reasonably fast charging charged move (Dynamic Punch), but he faints too quickly to use it.<h2 id='h_4520fd6c1244e7be0766cd42bf1f8537' 2> So, what should we use instead? </h2>
<p>
I did it with a Tyranitar. Even though Tyranitar&#039;s dark or rock moves have only standard effectiveness against Persian, Tyranitar takes less damage because Persian is less effective against rock types. Tyranitar is a bulky boy on top of that so he stays alive much longer than Machamp and manages to get off charged attacks. So even though his attacks are less effective than Machamp&#039;s, he ends up doing a lot more damage.
<p>
However, even better is if you can field a Pokémon that has resistance versus Persian and simultaneously has super effective moves. An example is Lucario, which has steel type resistance versus normal, but has fighting moves, which are super-effective against normal. A high level Lucario with a three-bar charge move (Power Up Punch) should go straight through the Persian without breaking a sweat.]]></content:encoded>
  </item>
  </channel>
</rss>