Google Stadia has come as a revolution in the way we understand the world of video games. Some claim that it is the end of hardware and consoles as we know them, although others claim that there is still enough time for that. Google Stadia is also available for mobile phones, although unfortunately Google limits this function to its Pixel and another very limited handful of Android phones. However, there is always a backdoor to skip this restriction.
The new Google gaming platform allows you to enjoy some of the best titles on the market without the need for a specific console, or a powerful computer. Just have a screen, including a compatible Android mobile , to work the miracle. Stadia has not been external to a certain controversy since its launch, such as some lag problems or games that do not run at the promised quality of 4K at 60 fps.
How to run Stadia on any Android mobile
Google Stadia is compatible with Android, but officially only with Pixel 2, Pixel 3, Pixel 3a or Pixel 4 and other terminals such as ASUS ROG Phone I and II, Razer Phone 1 and 2, and several Samsung mobiles including the new Galaxy series S20.You can also play using Google Chrome, but not all controls are compatible with this option. Now, from the XDA forums they have shared a very simple method to play Stadia on any Android mobile . The only requirements to achieve this are:
- Google Stadia application installed ( download from Google Play )
- A mobile with Android 6 or better
- Mobile rooted with Magisk
The method involves simply opening Magisk Manager and installing the custom module made by the XDA user. However, the steps can also be performed manually:
Manual method
- We open MagiskManager and look for the MagiskHide Props configuration module.
- We install the module and restart your phone.
- Now, we write “props” (without the quotes) in the ADB shell or in the terminal application to enter the MagiskHide command line interface:
- We write “5” to add / edit custom props.
- We write “n” to add a new custom prop.
- We write “ro.product.model” to configure this prop.
- We write “Pixel 4” to set it as the value of “ro.product.model”
- We write “and” to accept the change.
- We write “n” because we still don’t want to restart.
- Now, we repeat steps 5 and 8, but this time we set “ro.product.manufacturer” to “Google.”
- Finally, we restart the phone. Once it is restarted, we verify that “ro.product.model” and “ro.product.manufacturer” are set to “Pixel 4” and “Google” respectively, by entering the following commands: getprop ro.product.model and getprop ro .product.manufacturer
Ready to play
The trick allows Stadia to think that it is running on a Pixel 4 . The tests have been successfully performed on many types of terminals, including OnePlus or Xiaomi. However, it is possible that a future update of Stadia could disrupt this kind of backdoor so that any mobile phone sneaks into this gaming platform.
Source>XDADevelopers
