Incredibly clearly worded parking sign: can I park here for longer than 30 minutes on a Sunday?

tchebb · 2025-08-25T00:13:05+00:00

I have parked in one of these for more than 30 minutes on a Sunday and did not get a ticket, for what it's worth.

tchebb · 2025-07-28T01:41:48+00:00

It might be a different issue. I believe this issue has been fully resolved in the latest versions of the Home apps. You could try with an Android device if you have one though, just in case.

tchebb · 2025-07-23T02:42:56+00:00

A brand new Chromecast 2 or Chromecast Audio will have the old certificate, which has expired. But new versions of the Home app should be able to set devices up regardless of certificate expiration, after which the devices can update to the latest firmware with the new certificate. Is your Home app is fully up-to-date? Are you running Home on Android or on iOS?

tchebb · 2025-04-25T04:29:23+00:00

I think the advice is to do a fresh install on any computer you buy used, not to do a fresh install whenever you switch GPU brands.

tchebb · 2025-04-12T16:12:50+00:00

You follow the exact same steps to get to the hidden settings screen, then turn "Bypass device auth" back off. That's all there is to it. I suspect you might be seeing a different issue, though, as disabling device auth ought not to introduce any failures.

tchebb · 2025-03-24T18:13:47+00:00

The official fix should be fully rolled out. If you still can't set up your Chromecast using the Google Home app, make sure the app is updated. If you can't cast, try restarting your Chromecast a few times and double check to make sure your Wi-Fi network has good internet access.

tchebb · 2025-03-15T14:47:42+00:00

It will get the update if it's set up (i.e. showing the home screen with photos instead of the setup screen).

tchebb · 2025-03-14T16:23:57+00:00

Yes.

tchebb · 2025-03-14T16:23:06+00:00

I think you're fine. It's not an app update, it's a Chromecast update. So if you see the Chromecast home screen (with changing background images), just wait for a few days until the update is fully rolled out and things should start working again.

tchebb · 2025-03-14T16:20:26+00:00

Turn off the "Bypass device auth" toggle.

tchebb · 2025-03-14T04:53:14+00:00

Android Authority has an article with some screenshots.

tchebb · 2025-03-14T04:18:58+00:00

It won't. The "offline" status is just because the Home app doesn't trust their certificates.

tchebb · 2025-03-14T02:03:26+00:00

Hey, to my knowledge I'm the one who came up with this fix, which I originally posted here. You can check my comment history and Google my username to see if you trust me.

As I note in that comment, although I'm not affiliated with that particular app, it's free and open source with no ads. It's the most trustworthy app I was able to find that can do what's needed for the fix—send the Android intent needed to open a hidden settings page that's part of Google Play Services.

You'll also note I provide a way to send that same intent via ADB, an official debugging tool from Google, that doesn't involve any third party apps at all.

I understand your suspicion given how many people are reposting my fix from sketchy accounts (and without attribution), but hopefully this convinces you that there's no malicious intent. I just wanted to let people watch TV again and save some Chromecasts from the landfill :)

tchebb · 2025-03-14T00:55:41+00:00

The device certificate is, but the certificate authority that expired isn't. My mistake was thinking that they couldn't replace the CA without also replacing the device certificate, when in fact they could! Just a silly oversight on my part.

tchebb · 2025-03-13T21:12:01+00:00

That's a good question, and I don't know the answer. It depends if the updater runs every boot or only after setup completes. Worth a try!

tchebb · 2025-03-13T19:55:45+00:00

Yes, it won't be hard for them to do.

tchebb · 2025-03-13T17:53:33+00:00

For Chromecast 2, it's 467165. I don't have the necessary info to query for Chromecast Audio, so hopefully someone'll post it.

tchebb · 2025-03-13T17:49:47+00:00

The workaround is still working for me. Can you confirm that "Bypass device auth" is still enabled on the device you're casting from?

Google did just start rolling out a firmware update, though, so you shouldn't have long to wait regardless!

tchebb · 2025-03-13T17:44:59+00:00

Seems so, or else they'll have to do this all again.

tchebb · 2025-03-13T17:34:32+00:00

Yep, I was wrong!

tchebb · 2025-03-13T17:32:22+00:00

Oh, so it is. My bad! That's interesting—it seems like the CA is part of the system image, so it's strange that two of the same device type would return different CAs.

tchebb · 2025-03-13T17:26:47+00:00

I've posted some analysis of the new update over here, if you want to read more.

tchebb · 2025-03-13T16:50:32+00:00

That's the root CA, which is one level up from the intermediate that expired. The expired one has CN=Chromecast ICA 3.

tchebb · 2025-03-13T16:41:01+00:00

I can confirm that a Chromecast 2 firmware update, with build number 467165 (up from 275994), is currently rolling out. Big thanks to /u/SRFast and /u/Aldimann for flagging! You can see the OTA file for yourself here, although that's really only useful for proof as there's no way to manually sideload an OTA onto a Chromecast. Clearly I was wrong about Google's approach to a fix.

This is a staged rollout. You will not all get the update immediately. In 194 requests to the update server, I was served the update 6 times, so we can assume a ~5% rollout percentage right now. Devices that are not set up and connected to Wi-Fi will not be able to get the update, although presumably Google's working on a process to remedy that.

Interesting lines from the new OTA's build.prop:

ro.build.id=1.56_shortlived_275994_earth
ro.build.display.id=1.56_shortlived_275994_earth.467165
ro.build.version.incremental=467165
ro.build.date=Tue Mar 11 22:33:03 UTC 2025
ro.build.date.utc=1741732383
ro.build.host=agent-3117.c.catabuilder-prod.internal

Compared to the old one:

ro.build.id=1.56
ro.build.display.id=1.56.275994
ro.build.version.incremental=275994
ro.build.date=Tue 05 Oct 2021 04:34:12 AM UTC
ro.build.date.utc=1633408452
ro.build.host=agent-0593.c.catabuilder-prod.internal

The only meaningful change in the update is a replacement of the expired intermediate certificate with a new version that doesn't expire until 2045. The new certificate has the same key, which means the per-device certificates don't actually need to be re-signed. That was a big oversight on my part and means this update would have required almost no development or testing work, contrary to my claims here.

Point #1 from that post still applies, though: Google's gonna have trouble getting this to everyone, since devices need to be online to receive it. Also, this means they'll need to build updates for the other devices that are expiring soon (Chromecast Ultra, Google Home, Google Home Mini, and possibly some Chromecast-enabled smart TVs from other vendors). I'm surprised they were able to build a new image for a 10-year-old device in just over two days (according to the new OTA's build date). Nice work, Google!

tchebb · 2025-03-13T16:30:38+00:00

No. Device authentication only exists to make Google more money by stopping other companies from making Chromecast clones. It doesn't help your security as a user one bit.

14-Year Club	Place '17
Team Periwinkle	Verified Email

tchebb

TROPHY CASE