Related
Hi all,
I have a TP-Link TL-WDR4300 at home. My Chromecast is having issue connecting to this router. When i run through Chromecast setup, it goes fine up to the point where it asks me for password of my router. After I enter my password and click next, my TV would just say 'connecting...' and it will stuck forever. And the Chromecast setup app will say "Something went wrong. We weren't able to find your Chromecast on the network." Apparently because it wasn't able to connect to my network.
I'm pretty sure I have my password entered correctly. I tried to changed my router settings but it won't help at all.
One interesting thing is that my Chromecast used to be able to connect to my router before it was updated(which happened automatically when I connected Chromecast to my router for the last time). Although I had similar connection issues in the past, I was able to fix it by a combination of resetting Chromecast, rebooting router and changing router settings. Now, it just won't connect no matter what I do.
Any help is greatly appreciated!
rozzerhmq said:
Hi all,
I have a TP-Link TL-WDR4300 at home. My Chromecast is having issue connecting to this router. When i run through Chromecast setup, it goes fine up to the point where it asks me for password of my router. After I enter my password and click next, my TV would just say 'connecting...' and it will stuck forever. And the Chromecast setup app will say "Something went wrong. We weren't able to find your Chromecast on the network." Apparently because it wasn't able to connect to my network.
I'm pretty sure I have my password entered correctly. I tried to changed my router settings but it won't help at all.
One interesting thing is that my Chromecast used to be able to connect to my router before it was updated(which happened automatically when I connected Chromecast to my router for the last time). Although I had similar connection issues in the past, I was able to fix it by a combination of resetting Chromecast, rebooting router and changing router settings. Now, it just won't connect no matter what I do.
Any help is greatly appreciated!
Click to expand...
Click to collapse
I would reset everything and then try the setup program again if you haven't tried that already.
When you say "changing router settings", does this include channel width? Is it set to auto? Have you tried setting it to something manually, preferably 20MHz? Also what is your Network Mode set to?
mdamaged said:
When you say "changing router settings", does this include channel width? Is it set to auto? Have you tried setting it to something manually, preferably 20MHz? Also what is your Network Mode set to?
Click to expand...
Click to collapse
Yes. I am using the 2.4GHz wireless only
I tried changing all these setting
Mode: abgn
Channel Width: 20mhz-40mhz
Channel: 1 - 6 - 11
rozzerhmq said:
Yes. I am using the 2.4GHz wireless only
I tried changing all these setting
Mode: abgn
Channel Width: 20mhz-40mhz
Channel: 1 - 6 - 11
Click to expand...
Click to collapse
Have you tried using the HDMI extender? That can help a lot in some circumstances. It's amazing how much a TV and other electronics will interfere with WiFi signals.
rozzerhmq said:
Hi all,
I have a TP-Link TL-WDR4300 at home. My Chromecast is having issue connecting to this router. When i run through Chromecast setup, it goes fine up to the point where it asks me for password of my router. After I enter my password and click next, my TV would just say 'connecting...' and it will stuck forever. And the Chromecast setup app will say "Something went wrong. We weren't able to find your Chromecast on the network." Apparently because it wasn't able to connect to my network.
I'm pretty sure I have my password entered correctly. I tried to changed my router settings but it won't help at all.
One interesting thing is that my Chromecast used to be able to connect to my router before it was updated(which happened automatically when I connected Chromecast to my router for the last time). Although I had similar connection issues in the past, I was able to fix it by a combination of resetting Chromecast, rebooting router and changing router settings. Now, it just won't connect no matter what I do.
Any help is greatly appreciated!
Click to expand...
Click to collapse
I experience the same problem with you
bhiga said:
Have you tried using the HDMI extender? That can help a lot in some circumstances. It's amazing how much a TV and other electronics will interfere with WiFi signals.
Click to expand...
Click to collapse
I never had problems with my old router. So I'm pretty sure it to be a compatibility issue.
I have the same exact router (TL-WDR4300 but running dd-wrt) and have zero issues connecting my 2 chromecasts to it.
One chromecast is running PwnedCast and the other is vanilla on the most current update. The router is running both 2.4 and 5 ghz and both chromecasts are connected to the 2.4 bandwidth.
I am using the extender on both.
rozzerhmq said:
I never had problems with my old router. So I'm pretty sure it to be a compatibility issue.
Click to expand...
Click to collapse
Well does the Chromecast Light blink or is it solid?
If it is solid then it is connected to the router and you have some security setting or firewall either on the router or the PC isolating it from other devices.
Typical issue is when you have mis-selected Public for your network type in Windows instead of HOME,
Public isolates the Windows machine where HOME allows Device to Device communication.
Check the firewall settings on your router and try shutting it off and see if that works. If so then turn it back on and look for other settings like Multicast filtering or IGMP and uncheck.
If the light on the CCast is Blinking then it is not connected and you need to re-run the setup.
You say other devices are seeing it so thats probably not the case.
j.a said:
I have the same exact router (TL-WDR4300 but running dd-wrt) and have zero issues connecting my 2 chromecasts to it.
One chromecast is running PwnedCast and the other is vanilla on the most current update. The router is running both 2.4 and 5 ghz and both chromecasts are connected to the 2.4 bandwidth.
I am using the extender on both.
Click to expand...
Click to collapse
Thanks for the info. I am using vendor firmware atm, will try dd-wrt next.
Asphyx said:
Well does the Chromecast Light blink or is it solid?
If it is solid then it is connected to the router and you have some security setting or firewall either on the router or the PC isolating it from other devices.
Typical issue is when you have mis-selected Public for your network type in Windows instead of HOME,
Public isolates the Windows machine where HOME allows Device to Device communication.
Check the firewall settings on your router and try shutting it off and see if that works. If so then turn it back on and look for other settings like Multicast filtering or IGMP and uncheck.
If the light on the CCast is Blinking then it is not connected and you need to re-run the setup.
You say other devices are seeing it so thats probably not the case.
Click to expand...
Click to collapse
Update: It turns out this is not the root cause of this issue(refer to my post below), i will try dd-wrt next!
Thanks for the suggestions!
By following your advise and checking my security settings again. I was able to solve this issue by turning off VPN firewalls. I don't use any VPN thing so i thought the VPN firewalls wouldn't matter. Anyways, thank you very much and now I can enjoy Chromecast again!
However, there is one annoying thing. When casting from Chrome tabs, it won't go into full screen. There are black bars on top and bottom which isn't there if I cast from Youtube. I tried changing all the Chromecast extension options and Tv aspect ratio setting, but had no success. It would be awesome if you can offer some advice.
Thanks again!:good:
rozzerhmq said:
Thanks for the suggestions!
By following your advise and checking my security settings again. I was able to solve this issue by turning off VPN firewalls. I don't use any VPN thing so i thought the VPN firewalls wouldn't matter. Anyways, thank you very much and now I can enjoy Chromecast again!
However, there is one annoying thing. When casting from Chrome tabs, it won't go into full screen. There are black bars on top and bottom which isn't there if I cast from Youtube. I tried changing all the Chromecast extension options and Tv aspect ratio setting, but had no success. It would be awesome if you can offer some advice.
Thanks again!:good:
Click to expand...
Click to collapse
Go into Options of the Googlecast ext on your Browser
Select Full screen zoom and make sure it is enabled.
But there will always be some content that doesn't format the screen properly and will give you black bars...
Asphyx said:
Go into Options of the Googlecast ext on your Browser
Select Full screen zoom and make sure it is enabled.
But there will always be some content that doesn't format the screen properly and will give you black bars...
Click to expand...
Click to collapse
Well, after all, it was too early to call it a success.
So earlier today, I wasn't able to discover Chromecast from my PC(It says something like "device missing" in Chromecast extension). However, my TV shows Chromecast is connected to my network, and the light on Chromecast is stable white. Then, I tried to reboot my router, and that fixed it. This is basically similar to the issues i had in the past where i could just fix Chromecast connection by randomly rebooting router and resetting Chromecast.
I was skeptical and decided to revert my changes on VPN firewalls. After a router reboot, Chromecast still worked!!
At this point, I don't think it's the VPN firewall settings that is causing this issue. This issue looks so random. I would try to go dd-wrt next and hopefully it will fix this issue properly.
rozzerhmq said:
Well, after all, it was too early to call it a success.
So earlier today, I wasn't able to discover Chromecast from my PC(It says something like "device missing" in Chromecast extension). However, my TV shows Chromecast is connected to my network, and the light on Chromecast is stable white. Then, I tried to reboot my router, and that fixed it. This is basically similar to the issues i had in the past where i could just fix Chromecast connection by randomly rebooting router and resetting Chromecast.
I was skeptical and decided to revert my changes on VPN firewalls. After a router reboot, Chromecast still worked!!
At this point, I don't think it's the VPN firewall settings that is causing this issue. This issue looks so random. I would try to go dd-wrt next and hopefully it will fix this issue properly.
Click to expand...
Click to collapse
You mention DD-Wrt are you using that?
Cause I notice most people having these issues seem to be using DD-WRT or Tomato and I'm starting to wonder if perhaps there is some issues with those Custom Firmwares being used.
I do know in the past before I Upgraded my router that I had problems with devices getting booted off the WiFi because I had too many devices connecting and it would seem that when a new device would connect, one would stop getting data despite the fact it said it was connected.
Now this shouldn't ever be the case with WiFi if it has an IP it should not have a limit but I am wondering if your experiencing what I was experiencing before I Upgraded....
Not suggesting you need to upgrade mind you just that what your going through sounds similar to what I went through.
When I bought the new router (LinkSys N900) the Box had this chart of Router Groups and which router was best for X number of devices.
Low end for less than 3, High end for 7+ with the last group being for 7+ and HD.
This chart went against what I believed I knew about WiFi limitations which I thought was only IP and DHCP based...
I wrote it off as pure Marketing with the intention of getting you to buy the most expensive router they had...(which I was going to do anyway LOL)
I'm starting to wonder if maybe there is something to that....Sure would explain my problems with the router that made me upgrade in the first place.
I'm having the same issues with my chromecast and a tp-link wdr4300 router on dd-wrt (latest build from 2014-02).
After either chromecast or router (wi-fi) restart I'm able to cast and chromecast is also shown in chromecast app.
But after some idling (without casting) chromecast is still connected to my wi-fi (ping responses) but I'm not able to cast anything (music, allcast etc..) anymore.
I have already tried enabling/disabling UPNP, changing wi-fi channels, etc
Doesn't look like just a wi-fi issue only, as chromecast is still connected to my wi-fi.
but still could this be related to the Atheros chipset used in the wdr4300 maybe?
Any other routers with atheros chipset running without problems?
Try installing Bonjour Browser or another mDNS browser and monitor what happens in local._googlecast._tcp
Also check router security and firewall logs to see if things are being blocked corresponding to when the mDNS broadcasts fall off.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Seems to be good now for my setup.
I had installed a bonjour browser but couldn't see anything special.
local._googlecast._tcp was present all the time even though I couldn't cast.
I have changed the router firmware from dd-wrt (02-19-2014-r23598) to a self compiled OpenWrt (Barrier Breaker r39770).
I have been able to cast now stable for 4 days. Never had that before on dd-wrt.
nervdoc said:
Seems to be good now for my setup.
I had installed a bonjour browser but couldn't see anything special.
local._googlecast._tcp was present all the time even though I couldn't cast.
I have changed the router firmware from dd-wrt (02-19-2014-r23598) to a self compiled OpenWrt (Barrier Breaker r39770).
I have been able to cast now stable for 4 days. Never had that before on dd-wrt.
Click to expand...
Click to collapse
Thanks for the update. Good to know that OpenWRT is working for you.
I have the same router. Don't recall having any issues on stock firmware. I'm on ddwrt now.
Did that as I plan on converting to extender when I move to the AC router soon.
I can only imagine the Chromecast didn't like something in your settings.
Sent from my SPH-L720 using Tapatalk
"Something went wrong. We weren't able to find your chromecast on the network"
[ this trick worked for me ] .. I had the same issue.. I was trying to connect my lcd remote monitor to my windows 7 pc. In the chromecast setup, I was able to go till the page that asked for the wifi network id and pw.., and later i got the error "Something went wrong. We weren't able to find your chromecast on the network" Many tries and all failed. Later i downloaded the chromecast app in my Android 5.0 smart phone and did the settings and voila! .. it got installed in the first try. Later without factory resetting the chromecast, i reinstalled the chromecast setup in my windows 7 and it got installed without any error. Later i opened up the chrome browser installed the chromecast plugin extension and it worked well. I was able to view my page on my remote monitor. Hope it works for u too..
Hi all,
not sure this is the right forum as I haven't altered my chromecast in any way... Anyway, I used to connect my Galaxy S3 running CM10.2 to my chromecast while being connected to a VPN (PIA). Yesterday I updated to CM11, reinstalled all apps using TB, and found out that my phone now can't see the chromecast anymore when I'm connected to the VPN. When I disable the VPN, the chromecast shows up fine. Has that happened to anyone else? I didn't change any settings so I assume it's somehow related to CM11 / Android 4.4. To be clear, I don't need to have the chromecast connect through the VPN to watch Netflix for example as I am in the US, it's just inconvenient having to disable the VPN every time I use the chromecast...
Any ideas/suggestions/explanations are much appreciated!
Cheers
Mungo Park said:
Hi all,
not sure this is the right forum as I haven't altered my chromecast in any way... Anyway, I used to connect my Galaxy S3 running CM10.2 to my chromecast while being connected to a VPN (PIA). Yesterday I updated to CM11, reinstalled all apps using TB, and found out that my phone now can't see the chromecast anymore when I'm connected to the VPN. When I disable the VPN, the chromecast shows up fine. Has that happened to anyone else? I didn't change any settings so I assume it's somehow related to CM11 / Android 4.4. To be clear, I don't need to have the chromecast connect through the VPN to watch Netflix for example as I am in the US, it's just inconvenient having to disable the VPN every time I use the chromecast...
Click to expand...
Click to collapse
Sounds like in your new configuration the VPN connection has precedence over the local network. I have no clue how to change that, but hopefully you do.
Sometimes there's an option akin to "route all/local/Internet traffic through VPN" that controls what traffic hits the VPN.
Mungo Park said:
Hi all,
not sure this is the right forum as I haven't altered my chromecast in any way... Anyway, I used to connect my Galaxy S3 running CM10.2 to my chromecast while being connected to a VPN (PIA). Yesterday I updated to CM11, reinstalled all apps using TB, and found out that my phone now can't see the chromecast anymore when I'm connected to the VPN. When I disable the VPN, the chromecast shows up fine. Has that happened to anyone else? I didn't change any settings so I assume it's somehow related to CM11 / Android 4.4. To be clear, I don't need to have the chromecast connect through the VPN to watch Netflix for example as I am in the US, it's just inconvenient having to disable the VPN every time I use the chromecast...
Any ideas/suggestions/explanations are much appreciated!
Cheers
Click to expand...
Click to collapse
This happens to me now as well. I no longer use a vpn for this reason unless you can configure your router to use it. Basically it looks at your chromecast as being on a different network since it isn't on your vpn. This is the case for cm11 and stock roms on my Nexus 5.
that's...unfortunate... makes me consider going back to cm10.2...
thanks for your replies!
Since my Chromecast updated to 16664 (official) last week, I have had a bear of a time having any device see the Chromecast. Prior to the upgrade, I didn't have any issues with connectivity. Now the only way I can get the device to work is to do a reset to defaults and go through the setup procedure. The CC will generally work until the next power-up, then the same thing.
When this happens, the ChromeCast's home screen indicates it's connected to my WiFi network, however no Chromecast enabled program, including the Chromecast app on my phone, sees the device.
There have been no changes to my wireless network settings since it worked last. Given that I've not seen anyone else post about this, I must be the only one seeing the problem. Anyone?
I've seen some similar reports over at Plex but not here...
I myself am on 16664 and have no issues seeing my device.
try a Factory reset and see if reconnecting helps at all.
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
SFDave said:
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
Click to expand...
Click to collapse
TiVos use mDNS advertising for their services.
Recent Chromecast firmware also seems to be using mDNS as well.
Try running Bonjour Browser and see if Chromecast is visible before/after reset or reboot.
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
kishke said:
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
Click to expand...
Click to collapse
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
bhiga said:
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
Click to expand...
Click to collapse
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Thanks for your reply tho!
kishke said:
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Click to expand...
Click to collapse
Weird... Might also be a more general network thing like a rogue device with a static IP causing a collision that Chromecast doesn't gracefully recover from, or a multi-interfaced device causing some kind of loop
But yeah, since you have 5 GHz, best to use that and keep your 2.4 GHz usage to a minimum to maximize available bandwidth for Chromecast..
Let me try a few of the suggestions here. I've not had any luck using 2.4 or 5GHz bands on my network...behavior is the same. Also, my router is an ASUS router with Merlin firmware. There is a new thread I've only glanced over, but I'll try some of the things there as well:
http://forum.xda-developers.com/showthread.php?t=2599515
I had to do the factory reset trick again last night so we could watch video on the Chromecast...it obviously hasn't gotten annoying to the point where I'm stopping all other activity until I get it fixed, though. Strange this only started happening after the Chromecast update, but I can no longer remember the sequence of events that go me here (chromecast update, router update, wireless AP added for better wireless coverage, etc).
I've seen similar behavior when there are just too many devices connected to the WiFi at once.
My router maxes out at around 9-10 devices...
Doesn't matter which band they are on either.
But to be sure it isn't an IP conflict I suggest setting DHCP reservations for all your regularly connecting devices to ensure they never get a different IP (especially important to do for servers like Plex) and remove that possibility from the equation.
Just to Add I believe the new 802.11AC Standards solve this problem, But you will need to buy a new router to get it.
Using a bonjour browser, I can see the entry for the Chromecast :
_googlecast._tcp.local.
Bedroom.local.:8009
/192.168.254.193
st = 0
ve = 02
md = Chromecast
ic = /setup/icon.png
id = [a very long number]
fn = Bedroom
ca = 5
Click to expand...
Click to collapse
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
EDIT: I've tried the factory default recovery method a number of times now. I see the bonjour record go away, then come back after the setup app says I'm ready to cast. All apps can see the Chromecast at that time, then after 3 to 5 minutes, they no longer see the Chromecast. I don't see any difference in the bonjour record when it working from when it's not working.
troycarpenter said:
Using a bonjour browser, I can see the entry for the Chromecast :
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
Click to expand...
Click to collapse
Just a longshot....But do you have any security software that could be blocking some Apps from communicating with the Network?
It sounds an awful lot like what happens when an AntiVirus Application Monitor has denied access.
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can). I'm looking for my iPad (I don't use it enough to keep track of it as close as I should) to see if it sees the Chromecast or not.
troycarpenter said:
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can).
Click to expand...
Click to collapse
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
bhiga said:
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
Click to expand...
Click to collapse
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
troycarpenter said:
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
Click to expand...
Click to collapse
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
bhiga said:
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
Click to expand...
Click to collapse
Looks like I switched off TKIP and just went AES on that network at some time. I went back and turned on AES+TKIP and now the Chromecast shows up on my mobile devices again. I'll keep an eye out in case that theory doesn't hold out.
Hey if anyone has the same problem and could share a solution i would be thakful. I'm trying to mirror my cell phone screen throug chromecast app. When in click in cast screen, the app finds my chromecast device connected to the TV. Then i select it, the connection is then stablished, the cell phone screen appears on TV, but imediatelly the chromecast app shows the "Disconnecting" message, automaticaly. After that, the chromecast app can't find the device on my wifi network anymore, just a few minutes later after a new search the device becomes identifiable again. Seems that the app is somehow making the Chromecast device to disconnect from the network. I've tryied to reset the chromecast device, to reinstall the chromecast app and i've disabled the AP isolation in my router and even tryied to disable the firewall, nothing worked what makes me belive it's an app issue.
Cell phone: Samsung S4 mini DualSim GT-I9192 with Andorid 4.4.2
Chromecast app: Version 1.7.4
Chromecast device firmware: 17977
TV: LG LM476200
Router: ARRIS TG862
Sorry for the english and thanks in advance.
RaphaRevolution said:
Hey if anyone has the same problem and could share a solution i would be thakful. I'm trying to mirror my cell phone screen throug chromecast app. When in click in cast screen, the app finds my chromecast device connected to the TV. Then i select it, the connection is then stablished, the cell phone screen appears on TV, but imediatelly the chromecast app shows the "Disconnecting" message, automaticaly. After that, the chromecast app can't find the device on my wifi network anymore, just a few minutes later after a new search the device becomes identifiable again. Seems that the app is somehow making the Chromecast device to disconnect from the network. I've tryied to reset the chromecast device, to reinstall the chromecast app and i've disabled the AP isolation in my router and even tryied to disable the firewall, nothing worked what makes me belive it's an app issue.
Cell phone: Samsung S4 mini DualSim GT-I9192 with Andorid 4.4.2
Chromecast app: Version 1.7.4
Chromecast device firmware: 17977
TV: LG LM476200
Router: ARRIS TG862
Sorry for the english and thanks in advance.
Click to expand...
Click to collapse
Same here, same devices.
With my Note10.1 2014, a supported device, the CC app showed on tv, but the Note froze, which never happened before.
I haven't given it a second try, I'm 99% sure that this will happen every time, and I don't know any variation of the mirroring process or device setup, which might possibly lead to success.
lecorbusier said:
With my Note10.1 2014, a supported device, the CC app showed on tv, but the Note froze, which never happened before.
I haven't given it a second try, I'm 99% sure that this will happen every time, and I don't know any variation of the mirroring process or device setup, which might possibly lead to success.
Click to expand...
Click to collapse
If the device is supported for Cast Screen and it is using the stock ROM, then it should work. If it's not using the stock ROM, there is no guarantee of success.
Still stock & non rooted.
Sometimes I find the casting is flaky if I'm connected to a 5 GHz wifi network, as the phone has to communicate via the router rather than directly with the Chromecast at 2.4 GHz.
Sent from my Nexus 5 using Tapatalk
lecorbusier said:
Still stock & non rooted.
Click to expand...
Click to collapse
I'd try it again. Screen Casting is high load on the system, so it could be heat or stress related.
My Galaxy S3 casts solidly as long as the battery isn't low, it's not overheating from being charged while casting, and the WiFi is strong.
cmstlist said:
Sometimes I find the casting is flaky if I'm connected to a 5 GHz wifi network, as the phone has to communicate via the router rather than directly with the Chromecast at 2.4 GHz.
Click to expand...
Click to collapse
It still communicates through your router in both cases. It's not WiFi Direct like Miracast. That said, I have seen reduced stability when casting from a 5 GHz device in newer firmware builds. It's still less bandwidth load on the bands, but it can be subject to issues if the router doesn't bridge the two networks efficiently.
bhiga said:
I'd try it again. Screen Casting is high load on the system, so it could be heat or stress related.
My Galaxy S3 casts solidly as long as the battery isn't low, it's not overheating from being charged while casting, and the WiFi is strong.
It still communicates through your router in both cases. It's not WiFi Direct like Miracast. That said, I have seen reduced stability when casting from a 5 GHz device in newer firmware builds. It's still less bandwidth load on the bands, but it can be subject to issues if the router doesn't bridge the two networks efficiently.
Click to expand...
Click to collapse
Interesting, I was always under the impression that devices on a wireless LAN could talk to each other directly if they were capable of seeing each other's signal. I guess not, then.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
Interesting, I was always under the impression that devices on a wireless LAN could talk to each other directly if they were capable of seeing each other's signal. I guess not, then.
Click to expand...
Click to collapse
Standard AP/Infrastructure mode routes everything back through the router - it's a star topology. Easiest to manage and control, but you can be limited by the router/AP's processing speed (hence the different classifications for Wireless N, and the different real-world speeds even within those classifications).
Ad Hoc mode is peer-to-peer but has some limitations (fixed channel, limited range, etc)..
WiFi Direct is more of a small-scale AP setup and requires some hardware/driver support.
Things might change with the promise of "cast without being on the host's WiFi network" that was announced, but we'll have to wait and see.
Found some solution?
maufinelli said:
Same here, same devices.
Click to expand...
Click to collapse
Did you managed to find some solution? :good:
Did anyone find a fix to the original problem? I'm having the same issue on my S7 Edge. It worked fine, then one day I tried to mirror my screen and it says "Connecting" then immediately afterwards it says "Disconnecting". However, Chromecast can mirror screen just fine on my S4 that's on the same network.
Setup: Samsung Galaxy S7 Edge (SM-G935T), Chromecast is connected via Mobile Hotspot. Samsung Galaxy S4 is connected to Mobile Hotspot as well. I DO NOT have a wireless router nor do I plan on getting one. Any fixes would be greatly appreciated.
Hi,
Managed to fix this by allowing microphone in permissions for all Google apps including Google play services and Google play services for Instant apps.
Hope this fixes your problem. :good:
Hey! Found a fix for this on the S7 Edge. I think it did have something to do with the 5 ghz band.
1: Turn on your phone's wifi
2: Allow it to connect to your chromecast
3: Turn on Smart Network Switch
4: Allow Aggressive Switching
5: Turn on your Mobile Hotspot
6: Allow your Chromecast to connect
7: Once the Chromecast is connected to the Mobile Hotspot, Pull down menu and click to turn wifi off, wait one second, then turn back on.
You should be able to mirror and cast then.
Hope this helps. Not an engineer, can't tell you why this works, maybe there is a more simplified way. I've also heard of clearing the data and cache from the Google home app, but that stopped working for me as I'm sure this method will someday too.
But for now, enjoy!
Best Regards,
- The Gaffler
KQC said:
Hi,
Managed to fix this by allowing microphone in permissions for all Google apps including Google play services and Google play services for Instant apps.
Hope this fixes your problem. :good:
Click to expand...
Click to collapse
This is not a satisfactory solution for me. Why should I let Google spy on me with my microphone just to cast my screen?
I have 1gen and 2gen Chromecast and both stopped screen casting (mirroring) with Pixel running Oreo. Works fine on Nexus with 7.1.2
I have a first generation CC. For the last few months, we've been using my wife's phone as an hotspot for the CC, and she's been able to cast from that phone just fine. (Set CC up using my phone connected to her hotspot). Last week it stopped working. My phone can cast from her hotspot, but her phone apparently no longer see the CC.
I've uninstalled/reinstalled Home and Netflix, plus I've factory reset the CC, but still no luck.
I switch the CC to using my phone's hotspot and my wive's phone and my phone can cast that way. She is more often home without me, so I'd like to get things working for her again.
I've seen stuff about "Client Isolation" but I can't find any settings in her phone"s hotspot related to that.
Any tip/tricks/suggestions to get her phone casting again?
http://www.androidpolice.com/2017/0...ems-broken-casting-using-android-hotspot-wifi
Please star this bug: https://issuetracker.google.com/issues/62378390