The Google TV Streamer is one of the best and most surprising Google products launched this year. It’s Google’s first non-Chromecast streaming product (the Nexus Q doesn’t count), and it incorporates features you don’t find in many other streamers, including access to Google Home controls and working as a Thread border router. During my Google TV Streamer review, I fell in love with how speedy, simple, and powerful the device is.
One thing the streamer does not explicitly do is operate as a gaming machine. However, it runs on the Android TV platform, meaning it at least has the capability of both on-device gaming and game streaming too. This, of course, begets the question: Is the Google TV Streamer any good for gaming?
The headline of this article gives away the answer. Let me break down my experience with using the Google TV Streamer for gaming so you can see how bad things really are.
Do you use Android TV for gaming?
6 votes
Connecting my controller to the Google TV Streamer
C. Scott Brown / Android Authority
To get things started, I grabbed my trusty 8bitdo SN30 Pro Plus controller, specifically because it can operate in three different modes: D-input (a legacy input protocol that works very well in Android), X-input (mimicking an Xbox controller), and Switch (mimicking a Nintendo Switch Pro controller). Theoretically, the Google TV Streamer should support all three modes since Android has natively supported all three input protocols since Android 10. In practice, though, that was not the case.
I started first in Switch mode because the SN30 Pro Plus’ face buttons are in the Japanese configuration (A on the right, B on the bottom, etc.). However, I couldn’t get the controller to connect reliably in this mode. The streamer saw the controller as an available connection option but refused to connect to it. So that was a bust.
The only input protocol I could get to work reliably was D-input, so make sure your controller supports it.
Next, I tried the X-input mode. This connected OK, but the Google TV software didn’t recognize it as an available controller. This is confusing, so let me elaborate. I could connect the controller to the underlying Android TV operating system just fine, but once you pulled up games within the Google TV skin (which exists on top of Android TV, similar to Samsung’s One UI on Galaxy smartphones), it wouldn’t let me play them because it said there was no controller connected. So that was a bust, too.
Ultimately, switching to D-input was the only mode that both connected to Android TV and was recognized within Google TV. As such, if you do want to try to use the Google TV Streamer as a gaming device, I highly recommend ensuring you have a controller that supports D-input. The SN30 Pro Plus is an older controller that isn’t made anymore, but the newer 8bitdo Pro 2 ($49 at Amazon) offers the same functionality and comes in lots of fun colors, so I would recommend that.
Playing native Android games went OK
C. Scott Brown / Android Authority
With my controller connected, I could use it to navigate around the Google TV interface in place of the Google TV Streamer’s Bluetooth remote. Right away, I noticed something was amiss as using the controller to move around was noticeably slower and jankier than using the remote. I noted that as a possible problem for gaming and moved on.
First, I needed some Android games to play. When you open the Play Store on the Google TV Streamer, there’s a section called “Games” that gives you a curated selection of titles that work well with Android TV. However, the list of games here is small, and they aren’t organized very well. For example, you can’t easily find free Android games, nor can you find games that are paid but priced at a certain level. After getting frustrated with this, I just used my phone. I found that Asphalt 8 is free and has Android TV support, so I installed it by using the drop-down menu next to the “Install” button to push it to the Google TV Streamer.
Google doesn’t make it convenient to find games that work with Android TV.
Within a few minutes, I had the game up and running. It immediately worked with my controller — no configuration needed. However, the frame rates were choppy. This is most likely due to the MediaTek MT8696 SoC powering the hardware, which isn’t a high-end piece of kit. Regardless, it worked.
What didn’t work (or, at least, didn’t work well) was my controller. As I feared, there was notable latency between when I hit the button and when my car reacted to it. I decided I should try another, less resource-intensive game to see if there was a difference there, and landed on Double Dragon Trilogy. Unfortunately, this game had the same problem: I’d hit the button for punching, and my character would throw the punch with a considerable delay. This problem made fast-paced games like Double Dragon and Asphalt 8 difficult to enjoy.
Even when you find a good game, controller latency and a sluggish processor makes it difficult to play.
Thankfully, other game genres aren’t affected quite as much by this issue, such as JRPGs like the fantastic Final Fantasy III. However, you could instead opt to emulate the original NES version of that game, too, which brings us to the next trial.
Playing emulated console games was terrible
C. Scott Brown / Android Authority
Let me start by explaining something that came up a few times during my initial review of the Google TV Streamer. There is a solitary USB-C port on the device, and Google told us that it was only used for delivering power to the streamer. After the review embargo lifted, though, other folks said that this lone USB-C port could be used for storage, too, if you connect a powered USB-C hub to it. We did our own testing with this, and it turns out this is sort of true, sort of not. Yes, some powered USB-C hubs will work, but some won’t, and there doesn’t appear to be any rhyme or reason as to which ones work and which ones don’t. Also, for the Google TV Streamer to see your connected storage, it must be formatted in exFAT, not NTFS, which is not ideal. In other words, although users can add expandable storage to the streamer, it is very clear that Google had zero interest in making it easy.
Without expandable storage, getting emulators and ROMs to work is a real pain.
I mention this here because getting your game ROMs onto the Google TV Streamer so you can play them in an emulation app isn’t easy without expandable storage. Even if you use an Android TV-supported web browser to download ROMs to the streamer itself, Google removed the native file explorer within the Android TV operating system. This happened back with the launch of Android TV 12, and I am at a loss to explain why. Regardless, the lack of a native file explorer causes problems as the emulators are looking for your ROMs in the system but can’t find them because, well, there is no file explorer. Even installing a file explorer from the Play Store doesn’t fix this.
In the end, my workaround was to open the ROM directly. The Android system then asked me which app to use to open it, and the only emulator I installed that appeared on this list was Snes9x EX+. This allowed me to fire up Super Mario World without issue. It looked great on the big screen, especially when I switched on a CRT overlay to make it look more like it would have back in the 90s.
Once you do get a ROM working in an emulator, though, it doesn’t matter, because controller latency makes the game unplayable.
However, remember that controller latency problem? Hoo boy, it was even worse here. Getting Mario to jump when I wanted him to was basically impossible, making the best-ever platforming game a frustratingly unplayable experience.
I tried other emulators, too, but some don’t support installations on Android TV devices (Dolphin, for example), while others simply wouldn’t open a ROM because of the file explorer problem (Lemuroid, for example).
At this point, I was too frustrated to continue. Even if I could hack together a way to get a wide selection of emulators and ROMs working well enough on the Google TV Streamer, the controller latency would remain. The whole time I was doing this, I thought to myself that if I hooked pretty much any of the best Android phones to the TV, I would have a better emulation system than this.
The only thing left now was to try streaming some games.
Surprisingly, streaming games was the best experience
C. Scott Brown / Android Authority
My preferred way to game is on PC, so I have a pretty decent rig for that. Because of this, I opted to run Moonlight for this game streaming test. If you’re not aware of Moonlight, it’s an amazing free and open-source service that allows you to play your PC games from anywhere, assuming those games are installed on a connected PC. Its setup procedure is a bit convoluted, but once you get it going, it works great.
Using Moonlight, I saw great visuals and controller latency was low enough that the gameplay was an enjoyable experience.
I got this all set up on the Google TV Streamer and, surprisingly, found that this was the best gaming experience I’ve had thus far. I streamed Horizon Forbidden West, and the visuals, gameplay, and sound quality were all great. There was some slight latency with the controller, but it wasn’t nearly as bad as all the other games I had tried up to this point. Even in a fast-paced game like HFW, the latency was short enough that I could enjoy myself. If I had to guess, streaming video from my PC left the streamer free to process my button presses a bit quicker than when running Android games or emulating even old titles like Super Mario World.
The Google TV Streamer is terrific, but it is no gaming machine
C. Scott Brown / Android Authority
After a frustrating afternoon trying to get the Google TV Streamer to be a gaming machine, I gave up. It’s clear that this device is not going to be anyone’s preferred way to enjoy games on their television. Unless you can live with the controller latency issues while simultaneously accepting that emulation is essentially not an option, this isn’t the gaming device you’re looking for.
Honestly, the easiest alternative would be to use your phone. A lot of Android phones, particularly newer flagship models, support DisplayPort, so you just need a USB-C-to-HDMI cable, and boom: your phone is now a gaming console of sorts. This allows you to play a huge range of games — native, emulated, or streamed — with solid frame rates and broad controller support.
There’s no use forcing a square peg into a round hole. The Google TV Streamer just isn’t built for gaming.
Of course, using your phone will never top the convenience of a streaming device permanently attached to your television. If that’s what you want, then your next best bet would be to invest in the more expensive NVIDIA Shield TV Pro ($199 at Amazon). You’ll have a better experience across the board with this, thanks to better controller support, a much more powerful processor, and multiple USB ports for directly attaching storage.
I want to close this out by saying I still think the Google TV Streamer is amazing — just not for gaming. As a standard media streamer with some specialized smart home tricks, you can’t do much better than this, especially for the $100 price. Maybe if Google launches a follow-up in a few years, it will be better for gaming. Until then, grab this to watch movies and TV, but skip it for games.
Google TV Streamer
Fast processor • Smart home features • Great remote • Flagship product
Google’s boldest streaming device ever.
Carrying on the legacy of the Chromecast, the Google TV Streamer brings a sleek new design, more power, a redesigned remote, and smart home hub features to Google TV.