Hacker News new | past | comments | ask | show | jobs | submit login
Google Chromecast and Google Home Causes Wi-Fi Drops (myce.com)
189 points by MrCzar on Jan 14, 2018 | hide | past | web | favorite | 115 comments

ChromeCast is such a frustrating product. It does exactly what I want in theory. In practice I have to wait 10 to 60 seconds to get it to connect, or reboot my phone. I've started giving up and just using the computer attached to my TV.

I don't think I've been having the particular Wi-Fi issue described in the article, but ChromeCast has been just slow and flaky in my experience. I've had both v1 and v2. It seems to have problems with older phones, but that's not the only problem.

mDNS on Linux with Avahi doesn't seem particularly reliable either (e.g. pinging a Linux box from a Mac.)

Computers barely work :-( I guess this is why Apple insists on owning the whole stack. The compatibility matrix becomes tractable.

I have a similar experience, though I think a lot of the issues are actually with the apps - e.g. Netflix and Spotify will consistently not show my cast devices unless I quit the app and relaunch it, while other apps work ok.

Google needs to get far more vigilant about ensuring the third parties are implementing it properly though - even if the bug is actually with a third party, it reflects badly on their product.

Yes, Netflix is pretty bad when it comes to connecting to Chromecast

This is the exact opposite of my experience.

My Netflix app is extremely reliable with Chromecast. I had a period of unreliability when I switched to a new phone (Galaxy S8) that applued to Netflix as well as all other chromecast apps, but after an OS update it appears to be much better.

Well Netflix's android app is pretty bad period.

If you want to help make it better https://jobs.netflix.com/jobs/367

The implication of this comment is that the poor quality of Netflix's Android app is due to Netflix having been unable to access sufficient engineering talent to produce a better quality app. As an outsider that has experience developing software, I'm extremely doubtful that this is the case and am apt to blame it on executive-level prioritization almost out of hand.

Oh I didn't mean to imply that at all, I am sorry if that is how it came across. All software is imperfect. If there is software that you care about and want to make better and get paid to do so, that sounds like a potentially good fit.

Spotify will show the devices eventually, but it does seem to be rather slow, unless you've been on the wifi for a little while before starting the app.

I've had a similarly bad experience. I bought the original Chromecast years ago. Since then I've tried using it with two Wi-fi routers, at least three Android phones and an iPad and it never worked for me. The most common problem is that after a while the phone would fall out of sync with the Chromecast. For instance, video would keep playing in the Chromecast, but was paused in the YouTube app on the phone.

Yeah, that keeps happening to me as well. Playback continues, but my phone seems to just lose the connection. When I force it to reconnect, either playback jumps to whatever my phone decides to play, or the Chromecast and my phone will need to restart a new piece of media to sync up again.

When it does work, it's pretty cool with multi-room playback, but I've decided I don't really need that anyway.

I'm working on phasing out the Chromecasts now, because of limitations in which apps support casting, and the inability to block ads and properly cast local content (very format-dependent). The kitchen speakers and CCA have been replaced by a rather good Bluetooth speaker, which is also handy when I go to hang laundry. The CCv2 and second CCA in the bedroom/office is being replaced by a ultra-small form factor PC with a wireless keyboard. For the main stereo in the living room, there's always at least one other device turned on anyway, and all of them can play from Spotify or my file server, so the CCA goes unused.

On the flipside, I plugged my old CCv1 to the TV in my girlfriend's apartment, and that thing has been working absolutely flawlessly, so maybe I'm just unlucky.

> On the flipside, I plugged my old CCv1 to the TV in my girlfriend's apartment, and that thing has been working absolutely flawlessly, so maybe I'm just unlucky.

Sounds like it might be a network problem? Like for instance if you (like a number of other HN-ers I guess) like to restrict firewalls as much as possible?

My router's on default firewall settings. Deny inbound, allow outbound.

It's good to hear I'm not the only one! I always blamed it on the fact that I had an early version. I keep having to disconnect the chromecast, which is very painful because it sits behind my TV...

To counter - I have had an excellent experience with my Chromecasts (I now own 3).

It does everything I need, and while not completely perfect it has been really very reliable and generally 'just works'. As a user experience for playing content on your TV, the 'android as a remote' approach is great.

Those bad experiences are usually due to poor wifi equpment though - many routers mess up mDNS which means that devices that relying broadcasts work poorly. In your case Chromecasts, Avahi and similar (AirPlay falls also into this category).

So I'd check your router if you keep having issues.

Agreed. I downsized my entire media center to just the Chromecast and it was getting quite frustrating. I disabled ipv6 on my LAN a few months ago and it drastically improved the situation. Still it works better on my Android devices and PC's than iOS devices.

I quit using chromecast and a wireless HDMI solution. Does exactly what I want most of the time.

Do you have details on that solution? Is it a small PC?

One problem is that a lot of the things I cast use Android apps. Although I should check if they have web options. But a web browser is also a big dependency.

But you have a lot of flexibility in web browsers: There are a decent number of options, and they're available on every OS. The problem with using "Android apps" is that they tend to lock you into Google's ecosystem. Your solutions are limited to "things that support Chromecast", which is a vastly more limited set of options.

What wireless HDMI solution are you using? Could you leave a link? I was thinking of doing the same.

I'm using one of the Nyrius products. The delay seems imperceptible, but I did have one of their products mysteriously fail right after its warranty period so YMMV.

My Chromecast works quite well, at least the connection is quite stable casting from my mobile. 10s wait is kinda acceptable for me. It'd be nice that resolution could improve.

The Chromecast Ultra does 4K now.

> I guess this is why Apple insists on owning the whole stack. The compatibility matrix becomes tractable.

This is how everyone used to build computers, PCs just became the outliers due to way things went with IBM/Microsoft.

Now with the all-in-one models, it seems even PCs are getting back to those days.

And? There's a reason why all those others died and PC survived.

There are many reasons, none of them was quality.

1 - Mismanagement from Atari, Commodore and others

2 - Microsoft deals with OEMs

3 - Pretty cheap Taiwan and Chinese parts, some of them with doubtful quality

4 - Windows piracy, alongside the cheap parts, allowed many small PC shops to thrive and offer nicer deals

5 - PCs were the majority of computers at work and school, so the only one parents saw as a good buy for their children future.

Really odd. Using an original one for a couple of years now with basically zero problems. This is with an iOS/Mac set-up exclusively, though

Apple isn't immune to WiFi issues. They have had plenty of issues with WiFi reconnecting after a resume on MacBooks.

Lots of anecdotal experience in this thread about how bad Chromecast is so I'd like to offer my opposite:

Chromecast has been one of the nicest additions per dollar for my home. It has been working well for me for a year or so. I even used it today (for the first time in a week or more) while cooking and it worked like a charm first try.

The only real problems I've had with it, I switched hardware, but used the same SSID and it was confused as all heck. To its credit, though, so was my "Smart" TV. I gave up and just used a new SSID and everything worked again without all of the weird-ass problems.

I agree. I also regularly say that it's the best value money I have ever spent.

The only unreliability I have is with certain apps that don't appear to have implemented the functionality that well. The "NFL Game Pass Europe" app for instance sometimes forgets that it's attached to the TV and you can no longer pause/stop (there are workarounds). Other apps like Netflix have been extremely solid.

Indeed; bought first-gen LG webos, top of the line, TV. scratch record bad choice. Severally underpowered hw, like a really old tablet. Thus, it cannot update to later versions of WebOS and apps are constantly crashing (did I mention that the regular TV tuner is considered an app in webos?).

To work around this, I simply bought a chromecast as a target to stream youtube on.

I've never had any real issues with Chromecast other than the volume cutting off a few times. I liked it so much a bought a second to replace the "smart TV" features of the upstairs tv. It's really the best UI in my opinion.

I have same experience, it works for me all the time.

I enjoy my Chromecast but it does crash about once a week. Then I have to physically unplug it. I haven't experienced any other types of issues as of yet. Ideally I would like to replace this with an Apple TV 4 at some point.

Most homes would probably benefit more by having better insulation... If you are only talking about dollars...

Which Android version do your phones run?

Got a pixel 2, Chromecast and a Google home and now have lots of wifi woes. The timing being exactly after the pixel 2 (turned in cast and home before, didn't have problems).

Edit: turning of guest mode on all cast devices makes things better (less wifi dropouts) but still bad. Turning of wifi on both the android phones in my house has cleared up the wifi problem (which was really annoying as even spotify kept failing to stream with phones on wifi).

I wonder if Google employees need to test their consumer devices outside the googleplex where the internet is super fast and the industrial grade networking gear deals with such issues automagically.

In the Googleplex they have networks designed to be slow and crappy to test exactly this.

All people working on consumer facing apps and sites are encouraged to use these crappy networks on a day to day basis.

I wish there was more evidence that they used them. Far too often their software seems to assume a superb connection.

Personal "favourite" is their Newsstand - it will ditch cached stories whilst out and about because it briefly got a connection on the Underground, only for the content to not download (precisely because you're on flakey Tube WiFi) and boom the best use case for that software is ruined!

I was in Costa Rica last week with a slow wifi connection and had a similar experience with a 5MB offline PDF file in Google Drive. For some reason, drive decided to redownload it, but after only a minute it timed out and gave up. I just ended up going for two more days without the file, but I found it pretty ridiculous that Drive failed so miserably on such a simple use case.

I had a nearly seamless (albeit slightly slower) experience browsing Instagram on that slow connection despite the fact that all of the content was photo/video media, so I know the connection was not completely useless. It seems that Google engineers can't even fathom the possibility that someone would have a slow enough connection that a 5MB file might need more than a minute to download. This is frustrating.

It's pretty obvious they're not properly testing with that, though. I'm testing as a developer myself on a 2013 phone on throttled 4G (so I get between 64kbps and 1Mbps, depending on situation), on public transit – so connection drops all the time.

The result is that while some of my apps work fine, and a handful of apps work great, I’ve not yet found a single Google app that actually is usable in that situation.

Encouraged, but not required? Yeah that's going to happen.

I got a Pixel 2 also. So far wifi has been behaving, but Bluetooth has been a pain in the ass.

It's blamed on MDNS packets being spaffed out at high speed. I've got 3 Chromecasts of various flavours in the house and have never seen this behaviour. Has anybody else had the problem?

I also have three Chromecasts and occasionally 7-8 mobile devices that are connected to them in multi-AP network. I have mostly Sony devices and I think they have a rather aggressive powersave profile.

The last 3-6 month or so, the mobile devices have been losing connections to Chromecast while playing, and the network have become markedly more flaky also for other devices.

I actually got a Chromecast Ultra with an ethernet connection in case the wifi was bad, but it didn't really make a difference.

At some point a D-Link AP that is also the main router started to hang at least once per day, occasionally every 5 minutes. I installed Lede on it in order to rule out hardware problems - and then it stopped crashing at which point I stopped bothering, but I suppose the hardware can still be cooked.

I've noticed that the network occasionally is really slow for a short while - I managed to measure the speed to an external provider to be around 4-5 mbit/s instead of 100, but I haven't considered the possibility that it's my own network that goes bananas.

The WAF is declining, but it's so much junk that can go wrong so it will take a considerate amount of time to debug.

Edit: I must say though, that I expect my routers and APs to survive 100.000 packages...

The unnecessary flood of multicast packets these Google devices send is causing your AP to drop to its lowest speed and broadcast those packets.

Its the equivalent of having an 802.11B client that only syncs at 1Mbps and is constantly downloading. There is no airtime left for anyone else!

Things you can try: Block 802.11G and lower clients (increases your minimum WiFi transmission speed), convert multicast packets to unicast (LEDE is apt to support that), or throw the chromecast in the dustbin!

The scary part is that it takes highly involved HackerNews readers to possibly understand what's happening. Most regular folk are going to just think, Wi-Fi got flaky again.

Hang on, if you're converting multicast packets does that mean only one device is receiving them?

The WiFi AP handles unicast packets differently than multicast packets.

So on a network with N devices, you just convert one mulicast packet into N unicast pakcets.

Because multicast packets are sent with the slowest possible rate, this actually speeds up performance as long as N < 20.

I've actually had a weird issue where my wireless mouse freezes for a second (not the OS) and my Chromecast simultaneously disconnects from my Wi-Fi. It's only happened a few times in several months, but the two are definitely linked. I can't rely explain it beyond "interference", not well-versed in wireless tech.

It'll happen when a neighbour uses a dodgy microwave.

My iPad recently quit being able to connect to the 5GHz channel. My Samsung S6 networking is also glitchy and often on cell service while at home.

Timing aligns with me getting a Chromecast.

I have been having wifi issues for the last 3 months and I have 2 Chromecast's Ive had them for much longer but after reading this I'm going to segregate them to a different wifi network and see if the wifi gets better but my understanding of the issue makes me think it won't get better without a Chromecast update

This specifically needs an android update.

Androids the fault here not the Chromecast

Specifically, it sounds like Play Services Cast support has fairly pathological behavior in common circumstances.

same here.

This article was a dawn of light for me.. time to start logging the wifi behavior

After adding a second chromecast video / audio chats are impossible and countless drops at any given time. It's good to know the source of the issue.

I have noticed an issue since grtting a chromecast this Christmas but i cant say for sure its causing the issue

"...If your router vendor has not released an update for the issue..."

Ah good, I feared Google needed to update their devices to stop DDOS-ing my home network, luckily for them they don't get blamed and we think that the router vendors should add more robust DDOS-protection.

Interesting. I have 2 Google Homes (1 regular and 1 mini), a Chromecast and a Chromecast Audio, and a Pixel 2. I haven't noticed any particular network issues.

My network is all Ubiquiti gear. A USG, switch, and AP AC Lite. I have the private WiFi on the same network as my desktop PC and Steam Link. My home lab is on separate VLANs. Other then that its a pretty default configuration.

Not home right now but when I get home I shall look into it a bit more. Curious if whatever update thats causing this hasn't rolled out to Canada or if the Unifi products are handling it better/some special way.

Indeed, my Ubiquiti Unifi AP and Edge router have also been handling the mass influx of Chromecast and Google Home devices in my house - there's one of each in almost every room in addition to the slew SmartTVs of Android devices sitting around the house -- prob at least 5 pairs of Chromecast & Google Home devices (10 total) and prob at least 30 devices in total connected to that AP full time. Over Christmas when the entire family was here there was prob double that (60 total), including all the new devices received as gifts that were connecting to the AP for the first time all at once as people were playing with and configuring the new devices they got. The Ubiquiti wifi AP and router handled it without a blink.

HOWEVER, over the last few weeks I suddenly started experiencing continual wifi drops on my Fedora 26 and 27 desktop workstation. At first I thought it was related to an overflow of devices and/or a noisy channel, but it turned out not to be the case. None of the Chromebooks or other devices were experiencing frequent wifi drops so then I thought it might be related to my workstation wifi card antenna flaking out and causing the signal to weaken and drop. It turned out the issue was also not due to a failing wifi card. It took me at least a week to isolate and resolve the issue, but it's fixed now -- no more wifi drops and the signal is strong -- turns out it was a software issue with the more or less default Fedora 26 and 27 wifi config that I had been running for years. The issue might have been exacerbated by the increased Chromecast and Google Home devices on the network, but the issue wasn't because the devices were overloading the router or AP like I (and I presume others) initially thought.

When I have time, I'll go back through my logs and command history, and distill the resolution procedure into a gist.

I have a very similar setup and similar lack of issues even in a pretty challenging WiFi environment. Ubiquiti is so good for the price, I'm always amazed when I run into technical people who are running something else. It just seems like such an obvious choice to me...

Got into the Ubiquiti gear a while ago and definitely no regrets! Not a network guy myself and so really appreciate the controller just making it easy to mange things. I have myself, my mom's and several other family members properties all managed by one cloud controller. Things just work, and when for some reason they don't I have a fairly easy way of figuring out whats wrong and fixing it remotely. So very happy with their products.

I would consider the Unifi gear, but I have issues with the form factor: how do you put that round thing on the top shelf of a bookcase or whatever?

The in-wall ones might work better for me though -- although I think it's silly to have to terminate an in-wall cable to a plug to plug into the back.

Is there a reason you cannot mount it on the wall just above the bookshelf? One of the things I really like about the Unifi gear is how just small and inconspicuous it is. It really helped sell it when I suggested it to my mom and other family members. Mounted most of the APs for them on the ceilings, but a few of them are wall mounted as well. The ceiling ones look nicer than any smoke detecter I have ever seen.

So I actually really like the UniFi gear for that when compared to some crazy Linksys gamer router that just looks... so over done.

This is unrelated but could you explain what the Chromecast Audio offers over just playing audio on a regular Chromecast?

The Chromecast Audio allows me to plug it into any standard stereo. Bang for the buck I can get much better speakers for the dollar when buying just normal speakers instead of "smart" speakers. I then plug the Chromecast Audio into it and get the same ability to Cast to it, and include it into groups. The ability to add it to Cast groups is one of the key reasons I like it over just a Bluetooth connection.

So to sum up: * Bang for the buck get better audio quality * Still get all of the same Cast features (WiFi casting, group casting, etc.)

Hope that helps! :)

I just got the Google Home Max. It sounds better than the Google Home, but not as good as I'd expected. I'm tempted to send it back and replace it with a Home Mini and a regular set of home stereo speakers.

Not explicitly mentioned elsewhere is the digital audio connector (TOSLINK/optical out) on the Audio.

This allows it to be connected directly to a half decent amp, rather than relying on the onboard DAC.

The ordinary Chromecast is HDMI only, ie. a 100% digital connection. You have to plug it into a HDMI-capable device obviously, but most people use AV receivers these days.

Besides, the onboard DAC in the CCA is more than good enough. No need to mess around with an external DAC.

If you have multiple CCAs, you can set them up for multi-room playback. AFAIK you cannot do that with the ordinary Chromecast.

IIRC you plug it into speakers instead of a TV, which you can't with the regular one for the lack of aux output.

Audio without a display (or audio with an unrelated display) is very nice, especially for parties

I haven't noticed this problem. I've got a Chromecast v1, Chromecast Ultra, Home Mini, Pixel phone, and Google onhub + WiFi mesh, plus a bunch of other non-google devices. Perhaps the Google routers are able to handle the burst? I do wish that Chromecast was in general a little faster at connecting / playing etc.

Oh me either, but then I just have Apple TV and iPhone.

Well, this certainly explains why my wifi has been feeling pretty iffy for the last couple of weeks.

There was an awful lot of mDNS traffic coming from the (new to me) Google Home, and the two android phones, and mythtv (0.27) was sending every couple of seconds too. Running this tcpdump helped me track it down.

    tcpdump -n host and port 5353
For the google home, I just turned it off; does anybody know of an offline voice activated clock/timer? That's the most compelling use for me. (yo clock, what time is it and/or you clock set a timer for 3 minutes / set an alarm for 5:30)

For the phones, in settings / google / cast media controls, you can turn that off, I also turned off 'nearby links' in the google menu, in case that was related.

I've got a pretty good ($100) TPLink router and a 100Mbps Comcast connection in my 1BR apartment. I can almost never find the 5Ghz channel and get constant drops on my laptop, particularly the Linux one.

I've got a 1st Gen Chromecast, a Google Home Mini, and a Pixel XL.

Sounds like this is my culprit. Finally.

I have the same router I bet (Archer c7) and I'm convinced it just hates Android devices in general.

Every time my phone has a connection hiccup it takes several minutes to renegotiate DHCP... But if I turn off WiFi and count to 15 and turn it on, it reconnects in 3 seconds flat.

I'm tempted to throw out my wifi gear but I'm having trouble who in the industry isn't total garbage, because I have an Asus AP that sure isn't helping.

Hmm. I got my parents an Archer C7 based on it being the Wirecutter's pick for Best Wireless Router. It has been having a lot of problems with WiFi dropping out, like you describe. But I now see the Wirecutter have updated their comments [1] on the Archer C7:

"This is the single biggest reason we’re no longer recommending our former pick, the Archer C7. Though the C7 has great range and good single-device performance, it doesn’t have band steering, which means that it stumbles when several devices are connected and there’s a lot going on. The problem is compounded by the router’s relatively weak single-core CPU."

...our former pick, the Archer C7, leap all the way off the top of the chart into “oh, this is horrible” territory shortly past the 75th percentile — which means that roughly one out of every four page loads will leave you wondering if you should hit reload.

[1] https://thewirecutter.com/reviews/best-wi-fi-router/

Well, I'm somewhat relieved to read that, in that I purchased one for the same reason but have been rebooting it at least once a day for a while now. I was initially relieved to see it may have been the Chromecast. Now I suppose it's both!

It sounds like it is only on wakeup of the chromecast? how often is that happening? It wouldn't cause 'constant drops'

From the description, I got that it was app wakeup on the Android, Cast-enabled apps, not wakeup on the Chromecast.

I thought it was the fios router just being shitty but I believe that I've been experiencing this issue aswell.

Sounds like this issue affected my household as well. Been having wifi issues after bringing Pixel and Pixel 2 on to network with Google Home. Initially thought dropouts were due to so many neighbors in proximity.

I have a Google Home and a Pixel 2. I didn't have problems until we added two Google Home Minis. It's knocked out 5G on the Verizon Quantum Gateway router and 2.4G drops out every now and then.

I'm having the same issue. Just bought a Google Home in December and my Verizon quantum router has been dropping repeatedly. I've had a Chromecast and Nexus 6P for years and never had any issues with it. I'm glad I finally discovered the issue, thanks to this article!

Interesting, my wifis been terrible since christmas, ive had casts and a google home for a while but my partner got a pixel 2, the first android device in the house. Could be it!

Weird, I have a Chromecast and Google Home but have had no problems, though I do have Google Wifi...

I have an Onhub with four chromecasts and five google homes and have experienced the issues described. I noticed that sometimes if I wake my galaxy s7, other devices in the room might lose connectivity for a few seconds. I couldn't place why it would happen sometimes but not others, but this makes sense. I wonder if it might also explain why if a media app is casting and goes to sleep, it forgets that it's casting when it wakes up.

I was doing some home automation stuff with Node-RED and spotted that when I tried to figure out when a Chromecast was online - mDNS using ZeroConf would blow up Node-RED for no apparent reason, using SSDP worked OK. Now I know why...

1. My Chromecast is far less reliable than it was a mere 3-4 months ago. I regularly am unable to cast from my desktop and have to resort to my phone. YouTube, especially with multiple tabs, on desktop is a nightmare to use with the Chromecast.

2. I'm basically desperate to find something to take it's place. I'm tired of the Apple-ification of Google, and I resent having to boot up Chrome just to be able to cast a video (they have it locked down to where they effectively control both sides of the infra, such that Firefox can't implement Chromecast support).

Not sure if it's the Chromecast.

> Normally the device should send a couple of packets every 20 seconds, but in recent Android versions the apps sometimes send large bursts [...]. The longer the device has been in sleep mode, the more packets are send.

I wonder if it's a side effect of aggressive battery optimization in the newest Android version (Deep sleep/Doze, etc) where packets are withheld intentionally to only be delivered in bursts and have the wifi/radio sleep in between. Naturally, Pixel get updated first.

edit: typos

Does anyone know if Google is aware of this and is working on a fix?

Has anyone found a good way to troubleshoot and confirm these suspicions? This aligns with our experiences as well since adding more Chromecast devices and Google Home devices.

This tcpdump should show mDNS packets -- if you're getting hundreds per second (in some seconds), like I was, that's probably a good indication that something is misbehaving (or that you have a _really_ big network). If googlecast shows up in the name, it's probably Google Cast misbehaving.

    tcpdump -n host and port 5353

None of my devices have guest mode turned on so I'm unsure. But, I definitely feel like these symptoms have been on our network.

I love Chromecast but a few issues keep making me sad.

1. Casting a photo from Photos app, pressing Android back button makes the TV screen go black. Have to remember to swipe left or right instead, or use in-app back button.

2. Photos on 4k Cast-enabled TV are shown in horrendous quality. It's definitely not 4k and compressed as hell with contrast loss. Same for videos.

There used to be a ton of race conditions in YouTube TV app but those are thankfully fixed.

I use to have my Chromecast plugged into my TV so people could stream videos and photos easily to share with people during gatherings. We use Roku for streaming. Then we took it on vacation and forgot to plug it back in. I realized the reason our WiFi was so awful in that room when I eventually plugged it back in and everyone started complaining.

Now it is only ever used for vacation.

I am also having issues with chromecast and WiFi, weird slowdowns that never happened in the past. Casting pandora to the audio’s and mini’s always has problems. The phone will eventually start playing different songs than the cast, and at this point you are unable to control or reconnect to the cast. Like others I assumed this was a app issue.

I use DD-WRT so there won't be a router update to fix this.

I love my three chromecasts, however I can't really put up with this bug.

What to do?

Maybe some QoS rule on MDNS could help.

Got a chromecast, and my phone has a lot more trouble connecting to it than it used to have. Sounds like this might be the issue. Hopefully now that it's been identified, it'll be fixed.

I set all my chromecast/ home devices (9 devices) to have an assigned IP from my DHCP router (ASUS). Situation has definitely improved. But still not perfect

It would certainly seem like both the Chromecasts and the routers are misbehaving in this case, no?

I'm fairly certain a similar issue is being caused by the Wii U.

I have 7 Google home minis, 2 Chromecast Audios, 3 Chromecasts. Everything has worked fine up until a month or so ago. I've been using Chromecast since its initial launch and have never had these issues until now.

Google severely broke something recently, that's for sure. We had a Christmas party and I gave up playing music because it kept dropping off every few minutes. It seems like it has improved the past few weeks, but still pretty shoddy.

imho, routers either handle this somehow or drop packeta. because mdns is higher level protocol than wifi and mac, router should not deal with those.

also, with same hardware what happens there is whatsapp/hangouts video call? its about firmware

Routers deal with IP traffic (and even have to mess with TCP, e.g. clamp MSS), not just the 802.1 and 802.11. For SOHO routers, high PPS multicast UDP may be something hardware-accelerated routing doesn't particularly account for. And if software routing kicks in, high packet rate can very easily overload poor device's CPU.

It's due to the way multicast packets are transmitted on Wifi...


I've done a LOT of chromecast development/hacking. They are to put it politely, unreliable.

Google employ a small number of people to write TCP/IP core stack functionality. This is not a 'twenty hundred fiddy' people problem, its a six rising ten people problem.

The core issue is: how do we get the team in question to acknowledge and respond, with a timely code change?

It doesn't sound like it's a core TCP/IP stack problem, it sounds like it's a Google Cast support in Play Services problem.

The packet explosion in multicast had me thinking some upper layer call is being made, which the stack interprets to mean "keep going" in ways which then bomb the link layer out of existence. Its not TCP/IP I agree. I mis-characterized that. But I think the essential quality is the same: this heads to a single, or small number of people. Google chooses modes of operation which isolates those people from the feedback channels. I have had experience of this: go into a room, present on observed behaviour of a google service, zero outcome. Go into another room, repeat, the guy who can fix it walks to the microphone and says "thanks, I fixed that"

There is no strong git, or feedback-driven path which determines success or failure notifying google about code problems. Some work, some which used to work don't work now, some which didn't work then work now. Its unstable. Its unpredictable.

(for example, feedback inside bug reporting channels for Android, where the most common response from google staff is "this is the wrong channel to provide that feedback" including things which are bugs)

Other write ups say that on wake(), the device detects a true time difference between when it said "queue up sends" and now, and rather than just sending 5, it sends the sum of all missed sends in the interval.

Sleep for 5min, get 5,000. sleep for 10min, get 10,000

And, it is apparently a known side effect of a given java library, which has hit other people.

(and its not a TCP/IP stack problem, its an upper layer problem so you are right)

Applications are open for YC Summer 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact