By 
For the most part, a lot of mobile based games are designed to be played across a variety of devices, whether they’re low-end budget phone or a fully specced out flagship handset. Of course, performance does vary from phone to phone, but usually compatibility isn’t that much of an issue.
Unfortunately for Samsung users who are looking to play Blizzard’s latest mobile title, Diablo Immortal, it looks like depending on your phone, you could be out of luck. This is according to a post on Reddit by Community Lead PezRadar who listed a bunch of Samsung Exynos powered handsets that will not be able to play the game, at least for now. These phones include:
- Galaxy A12
- Galaxy A13
- Galaxy A21s
- Galaxy A51 5G
- Galaxy A Quantum
- Galaxy S10e
- Galaxy S10
- Galaxy S10+
- Galaxy S10 5G
- Galaxy Note10
- Galaxy Note10 5G
- Galaxy Note10+
- Galaxy Note10+ 5G
- Galaxy F12
- Galaxy F62
- Galaxy M12
- Galaxy M13
- Galaxy M62
- Galaxy XCover 5
While Samsung’s latest Exynos-powered Galaxy S22 phones aren’t on the list, SamMobile does report that the game does present some issues on the phone, like visual glitches, so it seems that even Samsung’s latest and most powerful smartphones aren’t coming out of this fully unscathed.
The good news is that these phones won’t be excluded permanently from playing the game (Blizzard most definitely won’t want to exclude a bunch of potential customers). According to PezRadar:
“We are exploring the issues people are experiencing with some Samsung Galaxy specific devices that use Exynos chipsets. For now, we may disable downloads for this set of devices while we work to address this. Apologies on this and we will be working on getting a fix up and ready as soon as possible.”
There is no word on when a fix is expected to arrive for these phones, but if you happen to own any of the handsets (note that this only applies to the Exynos variants, those with Qualcomm chipsets should be fine), it looks like you’ll have to sit this one for now, or play Diablo Immortal on your PC instead until this issue has been resolved.
Source: SamMobile
Comments