Slashdot Mirror
Chromecast Update Bringing Grief For Many Users
An anonymous reader writes: Last week, many Chromecast users were automatically "upgraded" to build 32904. Among the issues seen with this update are placing some users on the 'beta' release track, issues with popular apps such as Plex, HBO GO, (more embarassingly) YouTube, and others. Google so far has been slow to respond or even acknowledge the issues brought by customers, save for the beta release mishap. If you're a Chromecast user, what's been your experience?
I work for a pretty large video streaming company out of Hollywood. Our chromecast implementation for our streaming player has been doing crazy stupid shit for the last two weeks. Maybe this is why. Knew I read slashdot for some reason.
I am a Chromecast user, and I report that my Roku is working fine.
My sig can beat up your sig.
Looks like Chromecast has gone the way of Google Chrome: Arbitrary and random A/B testing that you're never notified of, and no way to opt out of.
This seriously pisses me the fuck off with Chome. The browser works great on like 20 machines, and then fucks up on one. You think it is the machine's fault, until you dig and dig and dig into vague forum posts on Google's boards. Then it turns out to be a hidden A/B test, where you have to go into the hidden Chrome settings to force enable/disable some very specific feature to get out of the that one and only that one particular test.
This is EXACTLY what happened to my primary development machine. Chrome had a hidden A/B test for ASync DNS requests. This feature is bugged to shit and back during the test. It would lock the entire browser session (all tabs) for 30-60 seconds at a time while making only certain DNS requests.
Another example is with the internal cache system. There was a bug for a while which would also lock up Chrome for 30-60 seconds at a time just waiting to see if a URL resource is locally cached. There was no fix for this that I could find. My resolution was eventually to have the installers handy for both Release and Beta Chrome laying around. Sometimes Release was the broken build, sometimes Beta was the broken build. So when shit got fucked up, I'd just toggle between the builds.
The OP includes a link to an IRAQ user saying he can't set up his Chromecast...
and a 9 day old post from someone saying they're now on the beta track and google saying they'll fix it.
Are we really to believe there's a great google conspiracy to disrupt chromecasts, and
in a week and a half NOTHING has been discussed, but now the only two links are
an IRAQI WINDOWS USER and someone who accidentally got into beta.
My money is on hoax.
Ehud
Among the issues seen with this update are placing some users on the 'beta' release track, ...
Google has a non-beta release track for something?
It must have been something you assimilated. . . .
It has become a running joke at the office. They are buggy, shitty, and mostly sitting in drawers.
Whether or not you approve of the über-casual dress code, that's still not a very nice thing to say about your co-workers.
Il n'y a pas de Planet B.
I'm the Chromecast Community Manager; I noticed your thread and wanted to respond.
I don't know if you saw my response in our forum, but we posted the below around the Beta issue some users were seeing:
"We've recently updated Chromecast and a small percentage of users received a debug message on the home screen. This update should not have any material negative user impact. We are pushing a fix to those impacted users shortly. If you would like to update immediately, please reboot your device (you do not need to factory data reset your device)."
The OP posted links to our forum but if you have specific issues with the release not being addressed, please post in our forum.
Jacky