Zwift Companion - no Game mode on Pixel Slate / Chrome OS

I recently picked up a Pixel Slate tablet, specifically to run the Companion app while using Zwift. The Slate runs Chrome OS, and while the app installed and mostly works ok, the game mode has never worked while I’m Zwifting (it doesn’t even show up on the menu). I also have a Pixel 4 with Android and game mode works fine on that.

The phone, my laptop (Zwift app) and the Slate are all o\in the same subnet, on the same access point, on the same wifi band, and I’ve verified that they all at least have basic connectivity (via ping) to each other. Although got a pretty great deal on the tablet, the fact that I have no other use for it than the Companion app has me feeling a little bit of buyer’s remorse. So I’ve got two questions…

  1. Are there known issues with the Companion app on Chrome OS?

  2. Has anyone had success with the game mode screen on a device running Chrome OS?



Hi Josh,
did you tried to contact Zwift`s technical support directly?

Hi Adam,

No not yet, I wanted to see if I could get some feedback from the community before I tie them up with another support ticket. :slight_smile:

1 Like

@Josh_Currier1 I have the exact same problem on my Pixel Slate! It’s so frustrating. Please do file a support request and report back here - I’ll do the same.

The Companion app works fine on my ancient 2014 Samsung tablet, but the version of Android on that is so old that the app seems to be stuck on an old version where half of Watopia isn’t even built yet. EDIT: actually I just managed to update it :slight_smile: But it’s very sluggish so I’d love to be able to use the Pixel Slate instead.

1 Like

I’ve submitted this to support, we’ll see what they say!

I did already - unfortunately so far they’ve only provided completely irrelevant advice as if the problem was related to connecting BLE sensors or to the wifi network, or to interference from microwaves (!) and that kind of thing :frowning:

Got a reply from Zwift:

Hi Adam,

Thanks for getting back to us!

After looking into this further, the main biggest issue here is the fact that the Pixel Slate uses ChromeOS. While you may be able to download the app on your Pixel Slate, ChromeOS is still not a supported OS for Zwift or the Zwift Companion. While there is the option to download it and some of the features work, this isn’t something we can support as ChromeOS is emulating an Android and doesn’t actually run the same. However, since you can get your old device to run the companion, we’d advise just using that in the meantime.

We hope this helps clear things up and if you have any other questions, please let us know!

I’ve replied back as follows:

Thanks for the reply Zachary. I appreciate that you have probably been informed that “ChromeOS is emulating an Android” by other folks at Zwift, but this is technically incorrect.

Chrome OS runs the full Android environment natively within a container on top of the Linux kernel. There is no emulation, or even any virtualization - please see the article I’ve quoted below for proof of this. Therefore even advanced features of Android apps such as talking to Bluetooth hardware work out of the box on Chromebooks. I have first-hand experience of this being true, since other Android apps on my Pixel Slate which use advanced features (e.g. MobileSheetsPro) work flawlessly.

So I repeat my request to have this issue escalated to your engineers for full analysis.

Please see this 2016 article which explains the technical architecture of how Android apps work on ChromeOS:

"The new model dumps the native-client based implementation for an unmodified copy of the Android Framework running in a container. Containers usually bundle an app up with all of its dependencies, like the runtime, libraries, binaries, and anything else the app needs to run. This allows the difference between application environments to be abstracted away. In this case, Google is putting the entire Android Framework into a container, all the way down to the Hardware Abstraction Layer.

It’s a lot like virtualization, but a virtual machine would sandbox the apps away from other apps and the rest of the OS. Containers let the Android apps access the underlying OS, which allows them to communicate with each other. Connectivity, storage, audio, touch, and all the other inputs and outputs get connected to Chrome OS, allowing Android to interact with the outside world."

This is my third attempt to get a technically valid response to the issue via their normal support channels. If I don’t get a decent response this time I’ll escalate via Twitter and any other communication channel I can think of.

1 Like

Thanks Adam, It doesn’t sound like they have any intention of supporting ChromeOS. I kind of don’t blame them, since the Slate is the only tablet running that OS. I’ve ordered a Galaxy Tab A and the Slate is going on Ebay.

We’re not asking them to support ChromeOS though. We’re asking them to support an Android device which happens to also be a ChromeOS device. Furthermore, I’m pretty confident that the lack of Game mode on Pixel Slate is not a conscious decision on their part not to support that device, but rather simply an accidental bug which could probably be easily fixed.

That’s not true - there are several other Chromebooks out there which operate in tablet mode, e.g.

Next instalment:

Hi Adam,

Thanks for the reply, and feedback.

I’m definitely sorry to hear you’ve been unable to get the Companion app, to go to game mode on your Google phone. Just to clarify, are you requesting that our dev team review the possibility of supporting Chrome OS on all devices, or just tablets and mobile devices in general?


and my reply:

Hi Aaron, thanks for the reply. Firstly just to clarify in case there is any confusion, my Pixel Slate is not a Google phone, it’s a tablet. And the problem is that the “Game” entry never even appears in the menu on the left-hand side, so I’m unable to even try to switch to Game mode.

Regarding your question about what I’m asking for, it’s actually neither of the things you described. I’m requesting that the dev team analyse the bug in the Companion app which prevents it from working on this Android device. As explained in my previous message, this device is capable of running all Android apps natively, and indeed I’m running about 50 other Android apps on it with no issues. Unlike in the main Zwift game app itself, switching into Game mode in the Companion app only needs to show a map and some statistics, so it doesn’t even need to do anything complicated relating to the device’s hardware. That is why I believe this is a simple bug and nothing to do with hardware support.


I for one would like to be able to run it on my Chromebook!

1 Like

A belated update - I had a long exchange of emails with a guy called Flint in Zwift’s support team, who was probably as helpful as he possibly could be, but it was clear that his hands were tied by some nonsensical support policy and he was basically powerless to help despite good intentions (or at least reached his personal limit of tolerance / patience in hammering on some internal engineering team).

The last email I wrote was as follows:

Thanks Flint, totally understand your position, and I really appreciate your honesty on this. I’m still very dubious that there is any valid technical reason not to support the Pixel Slate or other Chromebooks, but I’m perfectly willing to be persuaded otherwise, and certainly don’t want to shoot the messenger here :wink:

From my perspective there are three acceptable outcomes:

  1. The engineers perform some quick triage to establish why the Game tab is not appearing, discover it’s as easy to fix as I suspect it is, and fix it. This is obviously the ideal outcome, and I would be perfectly happy even if I had to wait a few months for it.
  2. The engineers perform some quick triage to establish why the Game tab is not appearing, and discover it’s too hard to fix to justify the effort relative to other higher priority items on their backlog. Zwift then provides a public statement (not just to me) explaining why this doesn’t work, which devices it affects, and why it’s considered too low priority to fix.
  3. The engineers already know why it’s not appearing, and Zwift provides the same public statement as in 2. above.

The second and third would obviously be disappointing to me, but still reasonably acceptable first steps although not a full solution.

In addition, as an extension of the above point about making public statement, Zwift really needs to properly document which devices the Companion app supports. I have looked on your website, and I can’t find any useful information on this. For example, support.zwift .com/en_us/categories/what-you-need-to-ride-BJjM4TyeH doesn’t even mention Companion once! If I follow the link to support.zwift .com/en_us/supported-devices-to-run-zwift-H1Cj9QbeB it still doesn’t mention it. I can only find useful information on Companion by searching for it. That leads me to this page support.zwift .com/en_us/using-the-zwift-companion-app-rJ7ayD_ES which again says nothing about which Android devices are supported. The implication is certainly that any Android device is supported. (Even though I won’t personally pursue this angle, I think any paying customer could reasonably argue they were entitled to a refund on grounds of buying a subscription on the assumption that they would be able to use Zwift with the Companion app.)

There are also some outcomes which I would definitely consider unacceptable, e.g.

  1. The Companion app is retracted from Google Play for Pixel Slate devices without any solid technical explanation of why it is any harder to support them than any other Android devices.
  2. Nothing changes with the app, and no solid explanation is given.
  3. The website is not updated to clarify on which devices the Companion app is supported.

I want to emphasise the importance of getting this right, which may be underestimated due to the Companion app being perceived as a “freebie” or unnecessary luxury. This perception would be incorrect, because Companion is absolutely crucial to the functioning of Zwift in certain circumstances, including mine: I run Zwift on an Apple TV and rely on Companion to overcome the limitation around transmitting data over Bluetooth from my sports devices. We customers need to know this kind of thing in advance, before we purchase a tablet or Zwift or any related devices. That’s why it is not sufficient to simply retract it from Google Play, for instance.

So I hope Zwift can manage to avoid these last three, which in my opinion would constitute disappointingly poor customer service. I do appreciate that you are personally limited in how much you can influence the situation, so again please don’t take this as me shooting the messenger :slight_smile:

Finally I wanted to offer some thoughts which of course you are free to ignore if it doesn’t resonate! You wrote “there is just a certain amount of need-to-know when it comes to these types of things”. I’ve worked for software vendors for 15 years, and yes I have experienced this. But the question is - what level of need-to-know is appropriate? Personally I think that unless you are working for some organisation which handles highly sensitive information and has a strong need to keep things confidential (e.g. military / certain government departments), secrecy often hurts more than it helps. Certainly in the case we are talking about here, I can’t think of any good reason to hide any internal conversations from you, your colleagues, or even from customers like me. If there truly is a good reason for not supporting the Pixel Slate or other Chromebooks, then making that explanation available to us would still be far more satisfactory than not addressing it and not explaining why it won’t be addressed. As a customer, feeling ignored is one of the single most frustrating experiences. Clearly you personally are doing the exact opposite of ignoring me, which is fantastic, but if your Android team doesn’t take effective action then unfortunately all your great work would be for nothing. Hope that makes sense.

Anyway, that’s enough (or maybe too much) for now. Once again many thanks for your great support - I really appreciate it!


(Sorry about the broken links but this stupid forum won’t let me post them properly.)

Unfortunately but perhaps unsurprisingly I heard nothing back from anyone after this point. So the TL;DR summary is that despite some valiant efforts from their support team, Zwift deliberately chose the worst possible (non-)response to this issue, clearly showing that they don’t really care about us Chromebook users. I guess we are too tiny a slice of the market and they are not honest enough to tell us the truth. Extremely disappointing.

Did you buy the pixel slate for the sole purpose of running the companion app? or am I reading your opening post wrongly?

if so that seems like a freakishly expensive way to get something that would run the app.

sorry - i know this doesn’t help your problem!

the only workaround i could suggest would be to use a different android device to run the app and have something like teamviewer running on the pixel slate to control it?