Discovered this the hard way:
I want to use FLauncher as my main launcher for Chromecast for Google TV / Android TV
I want the home button to always take me to the Flauncher screen, so I disabled the Google TV launcher using the adb command line tool:
adb shell pm disable-user --user 0 com.google.android.apps.tv.launcherx
This causes Stadia to go into an infinite loop on the Stadio loading logo screen.
This appears to be a recent change to the Stadia app, as there were no conflicts before. Is there a workaround for this issue, or can the Stadia team fix this bug?
@scstadio If you're making modifications to how it should work in default settings, there's always a chance of issue happening. I don't think this can be considered a bug from Stadia's side. If you disable the launcher and launch Stadia the normal way, does it work? If it does, I suggest doing it that way.
Hi Ivan, I would argue that this is a regression bug: Stadia launched with no problems when Launcherx was disabled for the last year, and only stopped working recently, which suggests a feature change or bug was introduced in one of the recent Android app releases.
@scstadio Software will keep getting updates, and sometimes it will breaks interaction with 3rd party tools. It's to the 3rd party tools to make sure it's compatible to the latest version of the software.
I suggest sending feedback to the FLauncher dev, or if you really think it's a bug on Stadia side, feel free to send feedback to the Stadia team through the app.
It's definitely related to launcherx and not the third party launcher, so I'll definitely send a message via the app, thanks!