What is Chromecast Audio companion device?
Chromecast Audio is not a standalone device: it requires a Chromecast Audio companion device to initiate the streaming.
The companion device usually pass the streaming location and streaming info to Chromecast Audio. Chromecast Audio will then take over the streaming. You may check this guide on how to use Chromecast Audio to stream music and how to control Chromecast Audio from your Chromecast Audio companion device.
If the streaming source requires a membership/subscription, the Chromecast Audio companion device needs to authenticate itself first, then pass the streaming source to Chromecast Audio.
This requirement of a Chromecast Audio companion device is by design.
Chromecast Audio does not have its own dedicated input interface in Chromecast Audio.
Chromecast App and Apps with Chromecast support are required to use Chromecast.
The apps (Chromecast App and individual apps with Chromecast support) must run on a device, which acts as a Chromecast Audio companion device.
Chromecast Audio companion device is not exclusive. There is no “master” device: all devices are equal.
Any devices that can run these apps can control Chromecast Audio. No Chromecast Audio companion device can hog on Chromecast Audio.
What are supported systems for Chromecast Audio companion device?
Chromecast App for Android, Chromecast App for iOS, or Google Cast extension for Chrome browser require the Chromecast Audio companion device to have one of the following supported OSes:
- Android 4.1 (Android Jelly Bean 4.1) or later.
- iOS 7.0 or later.
- Windows 7, Windows 8, Windows 8.1 and Window 10 with Chrome browser.
- Mac OS 10.7 (Mac OS X Lion) and later with Chrome browser.
- Chrome OS (on a Chromebook running Chrome 28 or later).
Please note, Chromecast Audio does NOT work with Windows phone currently regardless of the Windows version on the phone.
For Linux users, you can still use Chromecast and Chromecast Audio, although Linux is NOT officially supported.
To use Chromecast Audio on Linux machines (i.e., using Linux machine as the Chromecast Audio companion device), you need:
- Chromium or Chrome version 28 or later.
- Google cast extension from Chrome web store. You can get it after installing Chromium or Chrome.
- open UDP port 1900. You may need open other ports and traffic depending on your firewall settings.
For Amazon Fire tablet (or Kindle Fire) users, Chromecast Audio are not officially supported. Please refer to this guide to find out how to use Chromecast Audio on Fire tablet.
Do you know the supported OSes for Chromecast Audio companion device?
It should not be difficult to get a Chromecast Audio companion device with officially supported OS. This is the ideal situation if you use Chromecast Audio frequently.
If you have any questions on the supported OSes for Chromecast Audio companion device, please let us know in the comment box below.
The community will try to help you find the solution.
For more Chromecast Audio guides, please visit Chromecast Audio guide page.
If your question is on Chromecast including both 1st generation Chromecast, and new Chromecast (aka Chromecast 2015), please visit Chromecast how-to guides page.
Darren Price says
January 1, 2016 at 5:37 pmI have a Vision smart TV and I would like to cast audio to speakers behind my couch for surround sound. Can this be done? The Vision TV model number is E55-C2.
Thanks
simon says
January 2, 2016 at 2:30 amWhy do you need a TV if you want to cast the Audio? You can connect Chromecast Audio to the speaker directly. Chromecast Audio supports 3 types of Audio output.
To stream local media, please read this guide: Comparison of 5 methods for streaming local media files to Chromecast
Chromecast or Miracast? Please read this guide: Chromecast VS Miracast: everything you need know about Chromecast, wireless display and screen mirroring || Galaxy S6 Guides || Galaxy S7 Guides || Android Oreo Guides || Galaxy S8 Guides || Galaxy S9 Guides || Google Home Guides .
Mark Ram says
October 26, 2017 at 11:14 pmI read much of the helpful information you have provided. Finally I get to Chromecast Audio Companion Device. I’m trying to solve what should be simple, but it’s not. I want to stream “live” analog content to Chromecast Audio. I want something simple that I input stereo to, that then allows me to stream to one or more of my Chromecast Audio devices. They are already set up, “speakered up”, and managed from my current phone or old Galaxy 3 I keep near my audio equipment. I’ve considered several ways and tried a few. The most obvious way would be input the audio into the Galaxy 3, but stereo input is not supported, except perhaps through some Bluetooth workaround. I bought an inexpensive Griffin iMic device which was very helpful as I tried to understand how Windows and Linux handle audio in, out, and through. I was trying to avoid a solution needing a PC for power, simplicity, reliability and maintenance reasons, briefly considered Raspberry, but find the platform slow and inherently flawed due to reliance of SD card for running OS. There is similar hardware that uses stable and cheap built-in memory to run, but the platform offers me little – my Rasp II+ booting with browser to manage my “data center” all mounted to a small section of my garage wall is cheap, is fastened on the back of a wall mounted monitor (with powered HDMI to VGA converter) works, with long periods of downtime should Raspian boot suddenly fail. I can’t afford Sonos, want zero features, no playlists, time offsets, equalizer, sound boost; I’ve been able to use Chrome cast Audio latency adjustments to resolve “other Chromecast Audio within earshot” cognitive torture as a manual version of what audio receivers/amps use a small wired speaker to set up for 5.1 and 7.1 and others – cool and not difficult, just noisy. Before attempting Chromecast Audio I used remote 900 MHz speakers for a second room only (poor quality build, unreliable reception at less than 10m), then attempted Bluetooth but failed because of cheap equipment, poor range, and inconsistent performance. Even with lower-latency implementation for both send and receive all bluetooth reliably lagged wired analog audio connections by > 500 ms. I’ve tested more complex implementatiobs, but none performed better than Soundwire (nominally paid version) running it’s server on a laptop running Mint. Audio is supplied through stereo mic/aux input, from my amp and made available (over WiFi) to the Soundwire app on my old Galaxy 3. I then use Home to “cast all” audio to Comcast Audio. Since streaming is not normally done directly through Home, requiring an app front-end, this method is worrisome and subject to all inherent limitations of C. Audio, including headless and zombie streaming, intermittent missing C. Audio units displayed, etc. Zombie sessions have not improved since the “one play, all display” Chromecast enhancement, and may require surgical session termination or device reboot. In addition, I was experiencing distortion and white-noise static independent of perfecting the analog audio connection (direct wire through auto-switching exclusive headphone jack). Sound became clear and all discernable noise silenced when laptop charger disconnected. The cause could be a ground loop issue (laptop charged, amp and C. Audio powered by 60Hz AC) or caused by RFI from the lapbook charger, the charging circuit within the laptop, or harmonics in environment. Running the laptop on battery alone resolved all noise, but remains impractical. For the record I have Plex and that’s not a good answer for live input, and much too complex with no advantage. I keep looking for < $100 packaged single purpose hardware solutions and find none. Ideas, help, and addressing this question directly in your material would all be helpful.
simon says
October 27, 2017 at 12:17 amThank you for sharing your solutions. Chromecast is not designed for live music. You have to use some middle-man solutions.
To stream local media, please read this guide: Comparison of 5 methods for streaming local media files to Chromecast
Chromecast or Miracast? Please read this guide: Chromecast VS Miracast: everything you need know about Chromecast, wireless display and screen mirroring || Galaxy S6 Guides || Galaxy S7 Guides || Android Oreo Guides || Galaxy S8 Guides || Galaxy S9 Guides || Google Home Guides .
Mark Ram says
October 27, 2017 at 2:58 amAs I described. However, the use of the Android Home app allows any third-party phone app (not using whatever API is specified to cast directly), or any other mechanism to cast whatever content is on the phone, however it receives that, voice and video as well, I believe. It doesn’t matter where or how the media is stored or streamed. In fact, I’d prefer a way to input stereo audio to the phone directly (by wire) but that seems to not be supported except possibly one of a few Xperia devices, which would require a 5-conductor plug, and maybe a software work-around as Sony provisions that to support stereo microphones, not exactly leaping off shelves, even the few Sony could rent. I asked here because of your comprehensive approach and intent, and have noticed others are looking for a solution. I first inquired directly to a Chromecast board but got a party line message, which sounded very familiar, and equally dismissive. Any other ideas would be appreciated. Two thoughts: could this work through one of the many media streaming mini-boxes running Android 6 or 7? The only requirement I can think of is direct stereo audio input via phone plug (3.5 mm) or through optical or digital coax. Any would be fine, I need 2 channel audio only. What about using an iPhone and the Home app (or equivalent) there? I believe iPhones support stereo audio input directly and Wifi will do the rest, if someone can verify that will stream similarly as on Andoid. Even if an iPhone app is required that’s a single system solution. Ideas?
simon says
October 27, 2017 at 10:15 amI am not an expert on live broadcasting. Some comments may be wrong.
There are several obstacles. First, mobile phone is not designed to capture live music. The built in mic (one or two) cannot do a good job for this. You can attach an external mic through the headset jack (you need an adapter). But the signal will be too weak. You need an app to boost the signal to at least -10dB. Then you need an app to process the signal (the default voice recorder apps in most phones are good for “voice recording”. You cannot expect too much from such apps). Second, even you can find a good app to process the anology signal, you still need an app to stream to Chromecast audio. Google home is not such an app. Casting app uses the casting services provided by Google Home and Google play. I don’t think there are any apps in play store that can both process your external mic input and cast to Chromecast. Third, even if you can cast through approach, the audio quality probably will be very poor.
Anyway, personally I would not think it’s a good solution. But if you are interested, you can try to crack the problems one by one.
To stream local media, please read this guide: Comparison of 5 methods for streaming local media files to Chromecast
Chromecast or Miracast? Please read this guide: Chromecast VS Miracast: everything you need know about Chromecast, wireless display and screen mirroring || Galaxy S6 Guides || Galaxy S7 Guides || Android Oreo Guides || Galaxy S8 Guides || Galaxy S9 Guides || Google Home Guides .