Genshin Impact 7.0 asks no more of your phone, unless it has one of these chips

Version 7.0 arrived on 12 August and took the game somewhere it has never rendered before: Snezhnaya, a frozen nation of ice cities, snowfall and a new elemental reaction that detonates a vortex in the middle of a fight. The obvious question for anyone playing on a phone is whether the phone is still invited.

HoYoverse answered it a month in advance, in a notice that is easy to read as reassuring and worth reading twice. Not one number in the published minimum moved. The list of chips the game expects to have trouble got eleven entries longer.

What did not change

The notice is explicit about which figures are carried over untouched: the supported and recommended specifications for PC, iOS and consoles, the recommended specifications for Android, and the minimum values inside the supported Android specification — the SoC, the 4 GB of RAM and the Android 10 floor. In full, as published:

The Android supported line also requires ARMv8-A 64-bit. Read on its own, that table says a game HoYoverse describes as entering its sixth year, opening a whole new region, is asking the same of your hardware this month as it did last month. For a title of this size that is worth noticing before the rest of the notice complicates it.

The list that did change

Underneath the table sits a second list, and it is the one worth checking your phone against. HoYoverse's wording is that a small number of Android devices may experience stability issues because of compatibility constraints inherent to their older GPU architectures. Two architecture families are added starting with Version 7.0.

• Mali-G52 MP2 or Mali-G57 MP series GPUs. The notice names UNISOC T606, T612, T616, T618, T619 and T610 as examples.
• Imagination (IMG) BXM series GPUs. The notice names MediaTek Dimensity 7020, Dimensity 7025, Dimensity 7025 Ultra, Dimensity 7030 and Dimensity 930 as examples.

A third group was already there from earlier versions: early PowerVR GE, GM and Rogue series architectures, with Helio P35, Helio G36 and Helio G25 given as examples.

Why the two lists are not the same test

This is the part that makes "does my phone meet the minimum?" the wrong question. The minimum is a speed threshold expressed as an SoC, an amount of memory and an OS version. The risk list is about graphics architecture — what a GPU family can and cannot do, rather than how fast it does it.

HoYoverse writes the exclusion into the floor itself. The supported Android SoC line reads "Snapdragon 660 (Adreno 512) or Helio G88 (Mali-G52 MC2) or above", and then adds, in the same breath, excluding certain architectures with compatibility risks. A phone can clear every published number and still be named a few lines further down.

What "stability issues" means here

The notice does not leave it vague. If a device's specifications are too low, it says, the game may fail to install, fail to start, display black screens, experience freezing, or demonstrate other technical issues.

Note the word may. Nothing in the notice says a listed chip will be blocked, and nothing says the game has been withdrawn from those devices. HoYoverse's stated reason for publishing the list at all is to inform players of the situation in advance — and that warning is the whole of what the company has said about the outcome, so it is also the whole of what there is to plan around.

On iPhone and iPad, one line does not match the store

The iOS side of the notice is unchanged in every respect, and the supported entry point is still an iPhone 8 Plus or iPhone X. One detail is worth flagging, because it is the kind of thing that decides whether an old iPad can install anything at all.

Both were published by the same company and they do not agree. The App Store record is the one your device actually checks against when it offers you the download; the specification notice is the one that describes what HoYoverse will treat as supported. An iPhone left on iOS 13 sits in the gap between them, and the gap is not documented anywhere either record explains. If you want the general version of that problem, we keep a table of the oldest iOS these games still run on.

The question the notice does not answer

Storage. The notice says outright that for details regarding required storage space, players should stay tuned for future announcements — and a new nation with new environment textures is exactly the kind of update where that number matters more than the GPU does.

What can be checked today is the download rather than the install. Apple's lookup service returns version 7.0.0, released on 11 August 2026, at 3,711,529,984 bytes — a shade over 3.7 GB before the game unpacks or downloads anything else. That is the figure to plan free space against, and why mobile games eat your storage covers what happens to it afterwards.

What to actually do

1. 1

   Find your SoC, not your phone's marketing name

   Settings, then About Phone. HoYoverse points here explicitly, and adds the manufacturer's own site as the fallback. Two phones sold under the same model name can ship different chips in different regions.

2. 2

   Match it against the three risk groups

   Mali-G52 MP2 and Mali-G57 MP series, Imagination BXM series, and early PowerVR GE, GM and Rogue. The named parts are examples of those families rather than the whole of them.

3. 3

   If it is not on any of them, read the table instead

   The supported column is what you need to clear. Nothing in it moved for Version 7.0, so a device that ran the last version to your satisfaction is being asked for no more than it was.

4. 4

   If it is on one of them, expect the named symptoms

   A failed install, a failure to launch, a black screen or freezing. Those are HoYoverse's words for what the risk looks like, and knowing the cause in advance is worth more than a fix nobody has published.

The wider point outlasts this version. A minimum specification is a promise about speed, and it has become the number everyone quotes — but the thing that actually removes a phone from a game now is a graphics architecture a developer has stopped being able to support. Those two facts live in different paragraphs of the same notice, and only one of them ever makes a headline.