r/Chromecast
•
u/matthijspc
•
Mar 09 '25
r/Chromecast • u/my_bday_is_tomorrow • Mar 08 '17
Google Play should include a "Chromecast" icon for eligible apps.
r/Chromecast
•
u/tchebb
•
Mar 11 '25
Here's why a fix is taking so long
As of March 13th, Google is rolling out a fixed firmware version. If you haven't received it yet, there are still temporary workarounds posted here.
As this outage drags on, lots of us are wondering what's taking Google so long. Certificate expirations are usually resolved in minutes, so why is this different? Although I briefly spoke to that in my other post and elaborated in the comments, I know folks are still looking for answers.
TL;DR
Google will either need to put in over a month of effort to build and test a new Chromecast update to renew the expired certificates, or they will have to coordinate internally between what's left of the Chromecast team, the Android team, the Chrome team, the Google Home team, and iOS app developers to push out new releases, which almost always take several days to build and test. I expect them to do the latter. A server-side fix is not possible.
Background
First, it's important to understand how Chromecasts work in a broad sense. A Chromecast is basically a glorified web browser, capable of loading web pages and displaying them full-screen on a TV. When you press the "Cast" button on your phone or computer, that device (the sender) uses a proprietary network protocol called CastV2 to connect to your Chromecast (the receiver) and send it the URL to load, along with extra information like what account to use and what video to play. The Chromecast then loads that URL and streams the media entirely on its own.
Any device at all can be a sender: although Google provides official senders for Android (inside a system component called Google Play Services), Chrome, and iOS (as a downloadable SDK that developers can include in their apps), there are plenty of unofficial ones too. VLC has its own sender implementation, for example, as does Home Assistant.
The same is not true for receivers. Because Google went to all the effort of building the Cast ecosystem and getting content providers on board, they don't want other companies creating Chromecast clones and piggybacking on their hard work. This is where device authentication, the antagonist of our story, comes in. When a sender connects to a receiver, it has the option of asking that receiver to prove that it's an authentic Google device. The receiver will then create a cryptographic signature using a key that was installed at the factory when it was manufactured. That key is in turn signed by a higher-level key (the certificate authority, or CA) only known to Google. Since knockoff devices don't have access to Google's certificate authority, they can't sign their keys the same way.
[Note that, although a device authentication certificate is like those used by TLS/SSL, it's not technically a "TLS certificate" because it is not used to establish a TLS connection. The CastV2 TLS connection uses a separate self-signed certificate that isn't relevant to the security model.]
Key expiration
Every key in this system comes with some additional metadata called a certificate. Among other things, a key's certificate specifies when the key expires. Most cryptographic libraries will by default reject a signature if the key that created it has expired. Note that this is the only effect of expiration. A key doesn't magically become unusable once it expires, and all your Chromecast 2s are still happily signing device authentication requests using their expired keys. But, because Google's senders use standard cryptographic libraries, they no longer see those signatures as valid.
This wasn't always the case: the original device authenticator code in Chrome, circa 2013, did not check expiration dates at all, which makes sense for certificates you never intend to renew. Unfortunately, a change in 2016 replaced most of the custom code with calls to standard libraries that do check expiration. Based on the code review comments, it appears that no one at Google noticed the mistake at the time.
The Chromecast 2 and Chromecast Audio certificate authorities expired two days ago, within seconds of each other. Thanks to the excellent research of /u/meatbox in my other post, we know that more expirations are coming up: the Chromecast Ultra and Google Home CAs will expire in March 2026, and the Google Home Mini CA will expire in January 2027. So how will Google fix this?
Why Google won't renew the certificate
When a key expires, the solution is almost always to renew it—replace its certificate with a new one, signed by the same CA, that has a later expiration date. But the situation here isn't so simple: after renewing the expired CA, Google would also have to renew every key signed by it—meaning the factory-provisioned key on every Chromecast 2 and Chromecast Audio in the world. There are lots of obstacles to that:
EDIT March 13th: That last sentence is wrong. I overlooked the fact that the factory-provisioned certificate doesn't embed the CA's expiration date. That means that, instead of reissuing all the per-device certs, Google was able to reissue only the intermediate and push out a device update containing the new CA which, unlike the per-device keys, is stored on the system image and shared across all devices. See here for more details.
It won't reach everyone. Many people have factory reset their devices as a result of this issue, and there are likely at least some Chromecast 2s still sitting unopened in boxes. None of those devices have a way to reach the internet unless the Google Home app can set them up, which it can't right now because it checks key expiration. So a device update alone is not enough: at a minimum, the Google Home app would also need an update.
It's hard. The final update for the Chromecast 2 was built on October 1st, 2021. Google has shut down the Chromecast product line and presumably disbanded the Chromecast teams. Their internal OS build infrastructure has almost certainly been decommissioned. Just bringing back the infrastructure would likely take upwards of a week, and that's not to mention actually making the changes, which wouldn't be at all trivial. Device authentication keys were never meant to be changed, so they're stored on a read-only partition and there's no code in the Chromecast OS to renew them. It's possible Google could piggyback on some server-side infrastructure used by Android-based Cast devices for certificate issuance, but they'd still need to build a renewal client into the Chromecast OS, which is quite different from Android. Designing and building that would likely take at least two weeks.
It's risky. Replacing a key, especially one on a read-only factory partition, carries lots of risk. The process must be built so it can withstand interruption (e.g. someone unplugging the device) at any point in the process while still being secure (i.e. not issuing a certificate to any device that isn't a genuine Chromecast). Code like that takes a long time to test and validate, so add another couple weeks to the timeline.
It doesn't help security. Renewing the certificate brings no security benefit, as a hypothetical renewal service would issue a new certificate to anyone in possession of an old, expired one. That's in contrast to certificate renewal for websites, for example, where you need to prove continued control over your domain in order to renew its certificate.
Of course, this is all speculation—I have no insider information. Perhaps Google is at this very moment dusting off the old Chromecast OS build infrastructure and preparing a special version of the Google Home app that can get a Chromecast on Wi-Fi to receive an update. I find that highly unlikely, though.
What they'll do instead
What they did before 2016, of course! Since key expiration is checked by the senders, Google can update all their senders to ignore expiration when performing device authentication. This is really how it should have been all along, since these keys are supposed to last for an indefinite period. Chrome already has code to fetch a Certificate Revocation List (CRL) for device authentication, which lets Google mark specific keys as compromised, so Google wouldn't give up any control by removing expiration checks.
However, even this will probably take about a week, since it requires updates to senders like Chrome and Android. Luckily, Google Play Services, where the Android Cast SDK lives, can be updated independently of the OS, and Google obviously has full control over Chrome releases. But since many teams within the company will need to collaborate, creating and testing such updates isn't a one-day thing.
iOS is another matter, though. My understanding is that, since Google doesn't control any centrally-updated component of iOS like they do Android, they instead give each Cast-enabled app its own copy of the sender code. So, if they release a new iOS SDK, we'll still have to wait for each content provider (Netflix, Hulu, etc) to update their apps before the fix takes effect. Hopefully most will do it promptly, but there'll probably always be some old unsupported apps that are broken for good.
The only faster option for Google would have required some foresight on their part: client features like device authentication, which aren't crucial to a product's core functionality and carry a risk of breaking, often have remote "kill switches" built in that let the vendor disable them temporarily with a server-side change. But if one of those existed, I'm sure Google would have already flipped it. I didn't see evidence of a way to disable device authentication in the Chrome source code. Google Play Services does have a toggle, which is what the workaround I posted uses, but I haven't seen evidence of a way for Google to toggle it remotely.
r/Chromecast
•
u/tchebb
•
Mar 09 '25
The Chromecast 2's device authentication certificate has expired
As of March 13th, Google is rolling out a fixed firmware version. If you haven't received it yet, there are still temporary workarounds posted here.
I'm sure you've all seen the numerous posts today about broken casting and setup for Chromecast 2s and Chromecast Audios. Many people are assuming this was an an intentional change pushed by Google, or related to some recent device release or feature rollout, but that doesn't seem to be the case.
Let's figure out the real reason. The first step is to find some logs of the failure. Android might have these in logcat, but Chrome's an easier target since it's trivial to enable debug logging. I did that, then navigated to a YouTube video, opened the cast menu (which lists the Chromecast as "Available for specific video sites" and forbids casting), and saw many of these in chrome_debug.log:
1254:[502880:502907:0309/184942.218048:VERBOSE1:cast_socket.cc(229)] [192.168.86.26:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
1255:[502880:502907:0309/184942.218068:VERBOSE1:cast_socket.cc(389)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoTcpConnect
1260:[502880:502907:0309/184942.226508:VERBOSE1:cast_socket.cc(403)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
1261:[502880:502907:0309/184942.226513:VERBOSE1:cast_socket.cc(420)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoSslConnect
1266:[502880:502907:0309/184942.261447:VERBOSE1:cast_socket.cc(443)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoSslConnectComplete: 0
1267:[502880:502907:0309/184942.261454:VERBOSE1:cast_socket.cc(474)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoAuthChallengeSend
1268:[502880:502907:0309/184942.261458:VERBOSE1:cast_socket.cc(479)] [192.168.86.26:8009, auth=SSL_VERIFIED] Sending challenge: {source_id: sender-0, destination_id: receiver-0, namespace: urn:x-cast:com.google.cast.tp.deviceauth, payload_binary: (22 bytes)}
1269:[502880:502907:0309/184942.261475:VERBOSE1:cast_socket.cc(490)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoAuthChallengeSendComplete: 0
1270:[502880:502907:0309/184942.313883:VERBOSE1:cast_socket.cc(536)] [192.168.86.26:8009, auth=SSL_VERIFIED] DoAuthChallengeReplyComplete: 0
1272:[502880:502907:0309/184942.314118:VERBOSE1:cast_socket.cc(667)] [192.168.86.26:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
1274:[502880:502907:0309/184942.314137:VERBOSE1:cast_socket.cc(627)] [192.168.86.26:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING192.168.86.26 is indeed the address of my Chromecast 2, so this looks promising. com.google.cast.tp.deviceauth is the namespace Google's CastV2 protocol uses for device authentication, which lets clients ensure a Chromecast is genuine by having it sign a challenge using a keypair that's installed at the factory and signed by Google. Note that device authentication is performed by the client (e.g. Chrome, the Android Cast SDK, or the Google Home app) and is optional. All of Google's official clients do it, but many unofficial clients don't. For example, VLC can still cast just fine to my device.
So, it's a problem with device auth. But what exactly is going wrong? I didn't feel like patching Chrome to get more debug information, but luckily there are numerous other implementations of CastV2 that are easier to work with. openscreen is Google's official one, but node-castv2 is easier since it comes with some example tooling to debug device auth issues. Let's query my Chromecast for its device auth certificates:
$ cd node-castv2
$ npm install
$ node bin/dump-auth-response 192.168.86.26
(node:523150) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
output written to auth-signature.sig and auth-certificate.pem
CA written to auth-ca1.crtWe got two certificates. auth-certificate.pem is the per-device certificate corresponding to the keypair inside my Chromecast, and auth-ca1.crt is the intermediate Certificate Authority that chains up to the device auth root CA. Let's check the per-device cert first:
$ openssl x509 -in auth-certificate.pem -noout -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1482187900 (0x5858647c)
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=US, ST=California, L=Mountain View, O=Google Inc, OU=Cast, CN=Chromecast ICA 3
Validity
Not Before: Dec 19 22:51:40 2016 GMT
Not After : Dec 14 22:51:40 2036 GMT
Subject: ST=California, C=US, L=Mountain View, OU=Cast, O=Google Inc, CN=<redacted>
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:c3:61:c8:ea:06:fc:7e:ba:5b:d9:f5:b6:39:08:
7c:f3:dc:a0:f0:07:44:e6:e2:de:b2:63:9b:20:9b:
f3:4f:00:6d:a8:f8:9d:26:64:a5:70:a2:77:61:07:
50:31:1f:9a:07:ed:f2:4a:e6:4f:1f:db:13:f5:22:
96:53:02:05:fe:37:eb:0f:bb:69:7d:93:6e:95:78:
26:7f:36:e0:54:f0:42:63:fd:d7:65:0a:70:88:06:
e6:ba:5c:65:6d:0a:63:fc:e8:af:a5:de:49:ec:cd:
63:ff:e5:cb:1e:a7:a7:49:d0:0f:e2:6a:45:a1:26:
8c:94:a8:63:86:51:ab:1c:f1:65:bd:55:3e:58:0e:
b3:54:92:c7:89:a8:73:ba:65:0d:36:7d:c5:46:5c:
f6:99:a3:aa:94:9f:93:4d:d7:b4:d7:e4:29:3f:2c:
75:b8:fb:64:e1:31:05:45:d3:40:bc:3e:33:2a:02:
3f:79:ed:23:c0:b8:77:b3:b8:db:6d:7e:aa:d0:fb:
b8:d2:df:55:97:24:65:45:f8:47:5c:e4:1d:96:15:
03:d9:90:89:93:53:11:a8:02:d1:96:06:3d:e7:a7:
bf:28:23:85:5b:7c:35:81:3d:05:09:2e:8d:99:13:
b5:58:5e:73:6b:73:82:4d:2e:40:02:08:26:2e:48:
56:d3
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Extended Key Usage:
TLS Web Client Authentication
Signature Algorithm: sha1WithRSAEncryption
Signature Value:
a5:d5:8a:e5:ae:c1:1a:4c:52:42:e0:74:54:d5:68:01:31:ac:
d2:92:60:1b:15:de:cd:4a:7f:ad:2e:c4:38:06:91:70:15:da:
af:69:9b:8e:6d:2d:0c:b0:08:8f:0f:66:1f:3a:4e:7f:8a:ae:
56:a2:59:be:7d:da:65:d3:0a:2a:4b:93:37:70:e1:3b:74:18:
81:f0:c6:68:10:81:1a:fa:7f:fd:1a:ba:2d:d8:17:8e:9d:50:
ba:3b:13:e7:bd:90:47:b2:0a:b1:5e:c3:c4:ea:99:45:ad:67:
c6:e5:54:47:bf:bf:4f:c2:1a:43:f9:5d:62:44:cd:55:55:62:
0a:60:18:95:ef:ae:00:aa:af:da:b3:5a:cc:19:0f:37:5c:dd:
23:01:0c:34:44:e0:d2:4c:07:8d:7f:fd:ae:32:9f:45:77:71:
87:13:49:81:a1:d6:08:0f:4c:fc:38:cf:dd:41:ae:ce:85:7f:
58:c1:08:73:fd:f5:b6:5c:bc:55:c2:c2:95:88:63:34:c7:d7:
d2:23:d0:26:57:52:ff:c2:4d:ee:79:90:94:4a:ea:25:58:63:
b2:a0:de:9c:b4:be:13:4c:e0:b1:f7:5a:54:46:85:57:ab:9e:
0b:be:ba:5d:17:d1:3f:29:67:c6:f3:29:20:7e:5f:bd:6d:01:
36:bb:af:e4All good there, looks fine and doesn't expire until 2036. But what about the intermediate CA?
$ openssl x509 -in auth-ca1.crt -noout -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 36 (0x24)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=US, ST=California, L=Mountain View, O=Google Inc, OU=Cast, CN=Cast Root CA
Validity
Not Before: Mar 12 16:44:39 2015 GMT
Not After : Mar 9 16:44:39 2025 GMT
Subject: C=US, ST=California, L=Mountain View, O=Google Inc, OU=Cast, CN=Chromecast ICA 3
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:d1:de:fb:ad:8b:43:07:28:ae:56:2d:f2:73:2a:
1f:63:43:76:6d:8d:b8:d1:d4:90:29:1b:91:68:4a:
55:41:a0:d5:61:b4:ec:dd:ae:e1:fa:a7:b6:38:c4:
de:19:e1:33:4d:9a:29:f1:48:e2:6b:a7:2c:21:14:
22:3f:87:81:f3:71:2c:e6:43:1c:b8:d4:ec:cf:67:
2f:b2:a2:75:8b:10:bd:f9:e7:c9:5c:de:05:a9:b4:
86:b7:68:7d:a7:76:85:e2:65:b8:76:51:4f:b9:60:
5d:7e:2b:64:48:12:66:d9:a7:bb:7c:d7:48:88:8a:
89:f9:18:14:8a:15:32:6a:1b:3f:40:64:3c:80:d3:
e5:72:ee:3b:6f:88:bb:93:1a:17:3c:35:cb:d4:5b:
d8:f4:50:06:08:88:0a:e5:c2:3c:b5:8d:9b:99:82:
26:a3:9b:b9:e5:01:90:b7:c9:dd:ff:0f:f6:cf:b4:
9b:f8:4a:70:40:03:ed:aa:38:35:92:49:4a:5a:20:
67:92:5e:25:a8:6b:6c:49:28:45:41:b3:95:1d:a1:
ad:ef:c3:5a:12:35:a6:2f:44:f4:fb:36:cc:f9:ff:
d4:6c:a8:60:e6:09:17:a6:a0:13:23:09:96:6f:dd:
3e:fd:fa:5a:e7:9a:06:13:e5:07:0e:7d:5c:0f:d1:
46:85
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Basic Constraints:
CA:TRUE, pathlen:0
X509v3 Subject Key Identifier:
42:D6:3C:83:4E:4E:83:36:F4:2D:80:12:18:B0:FA:64:ED:CB:91:DD
X509v3 Authority Key Identifier:
7C:9A:1E:7D:DF:79:54:BC:D7:CC:5E:CA:99:86:45:79:65:74:28:19
X509v3 Key Usage:
Certificate Sign, CRL Sign
Signature Algorithm: sha256WithRSAEncryption
Signature Value:
4c:c7:77:4b:09:75:84:ab:84:0c:93:1a:a3:1f:0a:02:b2:28:
00:f3:eb:c1:e9:52:0c:7b:38:7b:02:d4:32:31:21:d1:85:b0:
23:42:e0:26:05:e0:11:21:fc:b4:b3:7e:3d:aa:4a:54:a9:08:
e6:79:27:fc:bd:fd:31:d8:d2:c2:de:96:0e:36:f9:f8:67:ca:
f3:59:7a:a8:ef:a2:bd:a6:73:ea:e8:ab:5d:25:05:9d:72:2d:
ff:0a:2c:7f:af:97:c6:c3:bf:b5:76:05:a0:00:11:1b:83:99:
4c:8b:c8:b8:4b:76:79:03:56:cb:ea:cc:f2:02:bc:23:8b:1a:
a6:7f:7f:4b:9d:7d:6a:69:cd:e3:50:78:b9:5c:ad:59:3e:dd:
d3:8c:2f:0a:fb:dd:03:c0:77:84:e6:a9:26:17:14:24:a2:7b:
3d:3c:b7:3c:d8:08:31:a4:4b:68:8b:0c:83:25:69:eb:68:42:
a2:87:a0:a1:dd:5a:1a:4a:1c:ed:28:01:3d:ad:51:d6:5c:ef:
4b:80:d2:7e:23:fc:bd:1a:02:30:d0:46:b8:b1:ab:0f:c7:28:
ee:da:ba:e7:d6:3e:a4:a9:26:ec:d4:73:41:c5:9b:68:8a:a8:
c6:15:39:33:4d:48:7e:6a:2f:4b:1c:6d:af:23:02:6d:e8:2f:
ce:16:b8:4bThere's our problem: Not After : Mar 9 16:44:39 2025 GMT! Google issued an intermediate CA, presumably the one for all 2nd-gen devices, with a validity period of only 10 years, and it just expired. As a result, none of Google's official clients succeed in validating the device as genuine and they refuse to talk to it, including during initial setup.
Google can fix this. Not by rotating every device's auth certificate to a new CA, which would take significant development work and is probably infeasible, but by hardcoding the fingerprint of the problematic CA into their clients and either pinning it as a root of trust (in which case the expiration date is ignored automatically) or ignoring its expiration date when performing device auth. I expect them to do exactly that, but it'll probably take a week or so, as it'll require syncing up with the release cycles of Chrome, Google Play Services, and the Google Home app. Some iOS apps that embed the Cast SDK may take significantly longer to resolve the issue.
So there you have it. Google didn't make any change at all, and in fact that's why things broke. They should have seen this coming, but clearly they didn't. Although I can't disprove that the expiration is planned obsolescence, I did also check my 1st-generation Chromecast, and its CA certificate has 20-year validity, just like the Chromecast 2's device certificate. If this were intentional, why would they have given an older device a later "obsolescence date"?
Edit: Interestingly, up until 2016, Chromium's certificate verification code hardcoded all the intermediate CAs and didn't validate expiration time at all. So it's possible that whoever issued these certificates believed the expiration time would never be checked. Unfortunately, a later change in Chromium (and presumably the other clients, although we don't have source for those) introduced the current (and much more conventional) chain validity check, which does care about expiration.
r/Chromecast • u/catsx3 • Jan 22 '17
Google, please, for the love of god, grant us the ability to privatize our Chromecasts to specific, approved Google accounts.
I live in a house of 5 techies with Chromecasts, other DLNA devices and SmartTV's that are cast capable. They love to interfere with eachother (hardware, that is) but that's a topic I'll save for another post.
While in a familiy or social gathering environment, I see the advantages of allowing "everybody" access to all Chromecasts but that's not how I think Chromecasts are typically used and Google neglected to foresee a tremendous amount of personal privacy concerns Chromecasts exhibit.
I can see what my roommates are watching. They can see what I'm watching. They can hijack my TV (my roommates haven't but youv'e heard the stories..) and play stupid shit. I can hijack theirs. I have access to my roommates backdrops and they mine. I can reboot their Chromecasts and they mine. Shit, if the Chromecast is powered by the TV and HDMI-CEC capable I can turn their TV on in the middle of the night with this WARNING: VERY FUCKING LOUD, DON'T CLICK. JUST DON'T
Unaccepable.
Here's a simple fix. Allow Chromecast owners to privatize or hide their personal Chromecasts from other users on the same network AND/OR at the very minimum grant us, as stated above, the ability to link only personally accepted usernames access to your Chromecast.
Google, please.
r/Chromecast • u/collectpond • May 18 '15
Chromecast on a 1984 coaxial analog TV--success!
r/Chromecast • u/AbortToddlers • Feb 03 '14
ABOUT GOD DAMN TIME Chromecast SDK has been released
r/Chromecast • u/DiscussionGrouchy322 • Mar 09 '25
Chromecast is untrusted
Hello
I have 2nd gen Chromecast, why is it all of a sudden untrusted?
It was working just minutes ago. Nobody asked about updates nobody sent an email to tell me. Why?
I also cannot see the Chromecast in home app, idk how to ask it to perform an update.
Please someone tell me what is going on.
Update: chat support of Google said, after an hour of reset this unplug that, this is a new issue and many people have it. My only resolution was to send feedback with logs from the app.
During troubleshooting they suggest factory reset but the problem persists and you will not be able to join WiFi. You then lose the wallpapers.
Seems like a big problem that they (now) know about, the support will be a waste of time until they make an announcement.
Update 2: I don't think they'll fix this. Just my opinion, but from my reading it looks like they simply forgot to tell us they were turning it off. If you use YouTube TV, picture quality will improve when you move to a newer device.
Update 3: they will fix
https://arstechnica.com/google/2025/03/googles-10-year-old-chromecast-is-busted-but-a-fix-is-coming/
r/Chromecast • u/Jennica • Nov 23 '14
I wish they would get rid of this backdrop on the YouTube app
r/Chromecast • u/gurdulilfo • Feb 12 '15
VLC 3.0.0 will support Chromecast
According to the changelog, VLC will support Chromecast with its 3.0.0 release. Current stable release is 2.1.5 and 2.2.0 is expected to be released soon (in weeks), but -unfortunately- there is no estimated date for the release of version 3.0.0. At least, we now know it's not coming any time soon.
If you are interested, you can check their VLC FOSDEM 2015 presentation via Phoronix.
r/Chromecast • u/illuuu • Feb 17 '15
HUGE: VLC's popular media player will soon support Chromecast
r/Chromecast • u/TheSuddenFiasco • Oct 21 '14
john oliver Chromecast screenshot perfectly illustrates error message
r/Chromecast
•
u/Playful_Jury7342
•
May 20 '26
My Chromecast with Google TV bricked itself during an automatic update. I spent days trying to recover it. Here's what I found.
Some months ago my Chromecast with Google TV 4K died mid-OTA update. Rebooted and never came back. Now it boots to the Google TV logo and sits there forever. Tried the obvious stuff like hard resets, different cables, button combinations. Nothing. Put it in a drawer.
Recently I got annoyed enough to actually dig in. I'm not a developer, so I had no idea what I was doing but I was too stubborn to stop. What followed was several days across four computers and three operating systems, Windows ARM, Windows x64, and MacOS before finally remembering I had an old Linux laptop gathering dust somewhere. Things started making sense on Linux. And then got worse.
What I tried:
ADB/Fastboot: Device shows up as "GX-CHIP" meaning the hardware is alive, but standard Android tools can't communicate with it.
Amlogic USB Burning Tool: Actually detects it and shows "Connect success." But no compatible firmware image exists for this model in the format the tool needs.
Also fought driver issues on both the ARM laptop and the x64 workstation before giving up on Windows entirely
sabrina-unlock repair script: A community tool built specifically for this device. Runs fine on Linux, immediately hits: "Error: device is protected by password", a hardware password Google burned into the chip's eFuses via the February 2021 security update. It's physically etched into silicon. Not bypassable in software.
UART serial console: I soldered wires directly to test points on the board to read boot logs. Found the failed OTA corrupted the boot partition ramdisk. Also found Google disabled serial input entirely in their bootloader, you can watch the boot process, you just can't touch it. I even wrote a Python script to automate keypresses at the exact right millisecond to make sure it wasn't just human error.
USB hub boot: Bought a powered USB-C hub hoping to boot from a flash drive. Requires loading a custom bootloader first, which requires the exploit the eFuse password blocks. Circular dead end.
The hardware is completely fine, the chip, storage, WiFi, all of it alive and responding. The device is being killed by its own security architecture with no official recovery path.
The part that genuinely bothers me: the February 2021 "security update" that burned this password into the hardware is exactly what makes recovery impossible when a future update goes wrong. Google removed the community recovery tools and replaced them with nothing.
I'm in Argentina, bought through unofficial resellers so no warranty, but that's almost beside the point.
Did anyone actually solve this? Am I missing something obvious? Did I do a ton of dumb shit for nothing?
r/Chromecast • u/majikmixx • Jan 24 '15
Rented a cabin in the mountains for the weekend. Thought it'd be a good idea to bring my Chromecast. I don't think it's gonna work.
r/Chromecast • u/[deleted] • Oct 02 '15
What most Amazon/Chromecast articles miss: "The only reason that Prime Video doesn’t exist on the Chromecast is because Amazon simply doesn’t want it to."
r/Chromecast • u/grillinbeans • Feb 06 '15
[Deal Alert] Get $6 In Google Play Credit For Each Chromecast In Your House
r/Chromecast • u/Frexxia • Nov 28 '16
I'm at a hotel right now, and these are my notifications. This is unacceptable Google.
r/Chromecast • u/[deleted] • Jun 16 '14
I like how you are notified when Chromecasts sell out in physical stores
r/Chromecast • u/[deleted] • Jan 07 '15
Go upvote support for Chromecast in Spotify
r/Chromecast • u/Jacky_Chromecast • Oct 16 '14
We're 6 members of the Chromcast team--Ask Us Anything!
Hey Reddit,
We're six members of the Google Cast team:
[Majd Bakar] (https://plus.google.com/+MajdBakar/posts), Engineering
Ambarish Kenghe, Product
[David Allison] (https://plus.google.com/114000335013548614241/posts), Product
[Mark Scott] (https://plus.google.com/+MarkScott0/about), Product
Sarah Walter, User Experience
[Jacky Hayward] (https://plus.google.com/+JackyHayward/posts), Community
Curious about how a Chromecast feature works -- or what our favorite snack is? We’ll be around between 2 to 5 pm PT to answer your questions. Many members of the Chromecast team pay close attention to all you talk about on /r/Chromecast, and we’re excited to hear from you directly now. Ask us anything!
Here's a photo of us, taken piecemeal as we don’t all work in the same office (clockwise starting at the upper left hand corner Ambarish, David, Mark, Sarah, Majd, and Jacky): http://imgur.com/wFCOOMr
Update: Just realized we typed Chromecast wrong in our title--whoops! Guess our excitement got the better of us.
Update #2: Thanks for asking us so many things! We had lots of fun--hopefully you did too. We’ll stop by tomorrow to see any important questions/comments. For now, real work--and snacks!--await.
r/Chromecast • u/quiro91 • Apr 04 '14
Want Chromecast support by Spotify? Kudos this thread
r/Chromecast • u/Rabbitinyourhat • Jul 25 '14
A little mock up of what I wish the Chromecast could display.
r/Chromecast • u/majik122 • Feb 27 '15
How many of you have little to NO issues with your Chromecast?
I for one have not had one single issue with mine. From the get go everything just worked. Even my girlfriend has no problems and she always gets lost with anything techy. Looking through this subreddit one would think we're a minority. How many others have had relative ease of use with their chromecast?
Edit: Great to see so many have responded and shown that their experience has been a positive one, despite this subreddit being filled with problems and issues users encounter. I do understand that people with problems are bound to seek help and ask about their specific issues than people happy with theirs. I just hope this will show the people on the fence about getting one that it's an easy to setup and reliable device. The more units sold ensures a brighter future for further applications and development. :)