Hello,
I have since yesterday an Chromecast.
I'm so far happy with it and the possibilities.
I have installed my Chromecast on my TV in my bedroom (a dormer window). My WiFi connectivy is very bad so I have a wifi extender so I can normally watch YouTube videos. But the problem is when the WiFi extender is on that I can't stream things to my Chromecast. When the WiFi extender is off the Chromecast works perfect.
How can I fix this?
Thanks in advance.
TheRicolaa10 said:
I have since yesterday an Chromecast.
I'm so far happy with it and the possibilities.
I have installed my Chromecast on my TV in my bedroom (a dormer window). My WiFi connectivy is very bad so I have a wifi extender so I can normally watch YouTube videos. But the problem is when the WiFi extender is on that I can't stream things to my Chromecast. When the WiFi extender is off the Chromecast works perfect.
Click to expand...
Click to collapse
I think it should work? Unless the extender is somehow filtering out some traffic.
If you can set up the WiFi extender as a bridge with its own SSID (essentially just another WiFi access point), then connect Chromecast to its SSID, that might work better.
Another thing g to keep in mind is the chrome cast only works on 2.4 not a 5 GHz signal.
Sent from my Nexus 5 using Tapatalk
So, at work I don't have internet, but I have my phone, and I have a chromecast on the tv. I use my phones hotspot all the time for my ipad and laptop with no problem. I have my chromecast setup on my Nexus 5's hotspot as it's internet connection. It works fine if I use my ipad to push content to the chromecast, but on the phone, all apps hide the chromecast option.
So basically the chromecast is invisible to the Nexus 5. I guess because the Nexus 5 is technically the Chromecast's router, and not a fellow client. There are a lot more apps that have chromecast support, so to get this working from my phone would be great. Is there a way?
I use my phone hotspot and play videos all the time. You can use video caster and chrome beta. I tried Netflix and Youtube but didn't have any luck.
Nexus5 Exp. 5.5 for N4
I would think that putting the phone into tether mode changes the way the networking works and would prevent it from making direct outgoing connections to anything other than the Internet.
I could be dead wrong however.
The problem with Hotspot/tether is that the Chomecast can't see the phone because of AP isolation built into Android. Chromecast or any "client' connected to the hotspot can see the Internet as that is what hotspot is for; connecting clients to the Internet... If you connect a second client to the hotspot I believe it can see an control Chromecast..
rkirmeier said:
The problem with Hotspot/tether is that the Chomecast can't see the phone because of AP isolation built into Android. Chromecast or any "client' connected to the hotspot can see the Internet as that is what hotspot is for; connecting clients to the Internet... If you connect a second client to the hotspot I believe it can see an control Chromecast..
Click to expand...
Click to collapse
Right.... basically the phone is not on the Tether IP subnet and therefore can not communicate with any device that has a Tether IP address. So Android itself has no access to this subnet it is just internet connection sharing with that subnet.
Not exactly a perfect technical description of what is going on but in the ballpark.
Only the App that is doing the tethering is actually seeing the Tether IP the rest of the phone has no access to it.
Put the phone into hotspot mode, use your tablet to navigate and play. I've done it
Sent from my DROID RAZR HD using Tapatalk
ArkAngel06 said:
So, at work I don't have internet, but I have my phone, and I have a chromecast on the tv. I use my phones hotspot all the time for my ipad and laptop with no problem. I have my chromecast setup on my Nexus 5's hotspot as it's internet connection. It works fine if I use my ipad to push content to the chromecast, but on the phone, all apps hide the chromecast option.
So basically the chromecast is invisible to the Nexus 5. I guess because the Nexus 5 is technically the Chromecast's router, and not a fellow client. There are a lot more apps that have chromecast support, so to get this working from my phone would be great. Is there a way?
Click to expand...
Click to collapse
I've been able to use AVIA in the configuration you're referring to.
I recently got a Galaxy S5 and realized that it's one of devices allowed to cast its screen to Chromecast. I installed the lastest ChromeCast app on my rooted S5 running stock Android 4.4.2 and as expected the Cast Screen option on the Chromecast app was available. My Chromecast dongle is running firmware 19084 and both the S5 and the Chromecast dongle are connected to the same SSID in my wireless network. My S5 is rooted, but my Chromecast dongle is not. I'm able to cast content from the Youtube App and other apps from the S5 and from other devices in my LAN without any issues. I just can't get the Screen Cast function of my S5 to work. I keep getting a toast notification that reads "Casting screen to (Chromecastname) has ended" every time I press the Cast Screen button.. After pressing Cast Screen in the S5 the screen of TV sometimes goes black, but during other attempts the Chromecast screen saver remains. I have factory reset and reconfigured the Chromecast dongle, uninstalled and re-installed the app, and cleared the data for the apps as suggested in other forums, but no dice. Given that my old rooted Galaxy S3 is not listed as a supported device, I decided to modify it and use it for testing. I installed #MirrowEnabler V6 (Experimental) to enable the Screen Cast option in the Chromecast App on the S3. The enabler activates the option, but when I try Screen Cast it fails with the same subject error. Is Screen Cast supported from rooted devices? I also have a couple Xposed Framework modules installed, can one of these be causing the problem? What Am I missing?
I have the same problem I'm trying to cast from an LG g2and I have the exact same sympton hope the one you described.
I'm running Android 4.4.2 also my device is rooted but the chromecast is not.
tamanaco said:
I'm able to cast content from the Youtube App and other apps from the S5 and from other devices in my LAN without any issues. I just can't get the Screen Cast function of my S5 to work. I keep getting a toast notification that reads "Casting screen to (Chromecastname) has ended" every time I press the Cast Screen button.
Click to expand...
Click to collapse
Those symptoms can be caused by poor WiFi reception on the Chromecast. I get the same on my CCs that have weak signal.
"Optimized" streaming services/applications like YouTube, can compensate for a slow connection by switching to a lower-bandwidth version of the stream. Screen-casting, however, runs at a high rate, and if your Chromecast's connection can't maintain that rate, you'll get black screens, frozen playback, image breakup, drops back to the backdrop/wallpaper, and even temporary Chromecast disconnect.
speed4cast can help you measure the connection speed, so you can try different things like using an HDMI extender (recommended), other HDMI ports, reorienting/repositioning your router, or using a 2.4GHz WiFi extender/repeater.
bhiga said:
speed4cast can help you measure the connection speed, so you can try different things like using an HDMI extender (recommended), other HDMI ports, reorienting/repositioning your router, or using a 2.4GHz WiFi extender/repeater.
Click to expand...
Click to collapse
Thanks for pointing me to that Chromecast speed measuring tool... I'm about to install it on my SGS5 to test. In terms of performance, what are the recommended speed ranges for Download and Upload for "optimal" Screen-casting from a mobile device connected to the same wireless LAN as the Chromecast? My Chromescast is very close to my Netgear N900 router, but it's connected to a HDMI port on the back of the TV.
My CC that works well for screen casting is reporting 8 Mbps down, 4 Mbps up.
Another CC that's working fairly well for screen casing is reporting 7 Mbps down, 2 Mbps up.
My CC that does what you describes and pretty much can't screen cast except for a few stills is reporting 1.75 Mbps down and 1 Mbps up.
Today it seems to be screen casting without dropping off, but it's choppy and blocky at times. In the past I've had it do what you describe, but I think my repeater wasn't online then. I'd try disabling my repeater but it's in a difficult-to-access location.
bhiga said:
My CC that works well for screen casting is reporting 8 Mbps down, 4 Mbps up.
Another CC that's working fairly well for screen casing is reporting 7 Mbps down, 2 Mbps up.
My CC that does what you describes and pretty much can't screen cast except for a few stills is reporting 1.75 Mbps down and 1 Mbps up.
Today it seems to be screen casting without dropping off, but it's choppy and blocky at times. In the past I've had it do what you describe, but I think my repeater wasn't online then. I'd try disabling my repeater but it's in a difficult-to-access location.
Click to expand...
Click to collapse
Now I think I get it... maybe? When I cast the screen from a mobile device from the LAN the casting still depends on the download/upload speeds of my Internet connection to/from the CC. Just like regular casting from say... youtube. Even while the screen cast content is coming from mobile device connected to the LAN to a Chromecast dongle connected to the same LAN... the screen cast content is also routed via the Internet? Am I making the right assumption here?
tamanaco said:
Now I think I get it... maybe? When I cast the screen from a mobile device from the LAN the casting still depends on the download/upload speeds of my Internet connection to/from the CC.
Click to expand...
Click to collapse
The data isn't routed through the Internet, but the quality of wireless connection between your Chromecast and other devices like your router is critical. I'm not sure if it's different in other scenarios but with my S5 and Chromecast both connected to the same router the data does seem to go through the router, rather than WiFi Direct like Miracast.
bhiga said:
The data isn't routed through the Internet, but the quality of wireless connection between your Chromecast and other devices like your router is critical. I'm not sure if it's different in other scenarios but with my S5 and Chromecast both connected to the same router the data does seem to go through the router, rather than WiFi Direct like Miracast.
Click to expand...
Click to collapse
I believe the quality of the connections and the performance of my wireless LAN is good. The speed4cast tools appears to measure "Internet" connection speed... not WiFi connection speed. It appears to measure the speed performance from either the Android mobile device and the CC or the CC and the Internet. The performance when I stream HD media to/from all my other wireless devices is fine. I made sure to turn off all the other wireless devices when I was testing the CC with speed4cast and when I attempt to cast the screen of my SGS5. My LAN wireless speed is more than adequate. Copying files from my WiFi connected laptop to my wired attached NAS averages 25-35MB/s. The upload speed to the Internet is low... about 1MB, but my down speed is about 10MB. My SGS5 works fine with all other devices on my LAN while connected to the 5,0GHz side of my router. I even tried connecting the SGS5 to the 2.4GHz side of the router where the CC is also connected, but this made no difference. My wireless connected laptop, Vudu Box and Samsung Smart TV play HD streams from the Internet without any issues. I can also stream HD (1080i) YouTube videos from the SGS5 or laptop to the CC without a glitch. If the SGS5 Screen Cast media stream or control protocol(s) aren't being routed through the Internet then something else has to be at play here because the only bottleneck I can identify in my network is the 1MB Internet upload speed.
tamanaco said:
I believe the quality of the connections and the performance of my wireless LAN is good. The speed4cast tools appears to measure "Internet" connection speed... not WiFi connection speed. It appears to measure the speed performance from either the Android mobile device and the CC or the CC and the Internet. The performance when I stream HD media to/from all my other wireless devices is fine. I made sure to turn off all the other wireless devices when I was testing the CC with speed4cast and when I attempt to cast the screen of my SGS5. My LAN wireless speed is more than adequate. Copying files from my WiFi connected laptop to my wired attached NAS averages 25-35MB/s. The upload speed to the Internet is low... about 1MB, but my down speed is about 10MB. My SGS5 works fine with all other devices on my LAN while connected to the 5,0GHz side of my router. I even tried connecting the SGS5 to the 2.4GHz side of the router where the CC is also connected, but this made no difference. My wireless connected laptop, Vudu Box and Samsung Smart TV play HD streams from the Internet without any issues. I can also stream HD (1080i) YouTube videos from the SGS5 or laptop to the CC without a glitch. If the SGS5 Screen Cast media stream or control protocol(s) aren't being routed through the Internet then something else has to be at play here because the only bottleneck I can identify in my network is the 1MB Internet upload speed.
Click to expand...
Click to collapse
Yes, speed4cast measures the speed between Chromecast and the Internet, but you cannot measure the Internet connection speed independently from the wireless connection on Chromecast, because the Internet traffic is flowing through the wireless connection.
So, if the reported upload/download speed is anything LESS than your Internet connection speed, then the Wireless connection* is slowing things down and the reported Internet connection speed is really your wireless connection speed.
For example, I have 50 Mbps down, 20 Mbps up. If I do an Internet speed test on a computer, I see 40+ Mbps down speed.
Yet, my Chromecast is only 8 Mbps down?
If I do the same test on my phone connected at 2.4 GHz I get much better results.
So, the wireless connection between the router and my Chromecast is limiting its transfer speed.
* if your wireless AP is not your router or there are other network segments between the Internet connection and the AP, they may be causing the slowdown instead of the WiFi connection. Also, if your router/AP is slow, the wireless devices may be connected at a high rate, but transfer to/from will never reach the maximum because the router/AP is slowing things down.
Checking the wireless speeds on your other devices doesn't mean anything because those other devices are not where your Chromecast. The closest you can get is maybe to put your phone/tablet as where Chromecast is, which is usually right up against the back of the TV. You're almost guaranteed to notice the speed will drop significantly.
As I mentioned earlier, tests with dedicated streaming video services like YouTube, Hulu, etc will not give you an idea of your wireless transfer speed unless they provide visual feedback for the connection quality.
They are designed to transparently handle a wide range of connection speeds, unlike screen casting which essentially says "I need this much bandwidth, or it's not going to work correctly."
If you have Netflix, you can try their speed test video.
This article talks about it. Note that on my Chromecasts with optimal wireless, I get up to 5300 kbps which appears to be the max.
On suboptimal wireless I get far less.
http://www.wired.com/2014/06/netflix-streaming-test/
Given your other devices have good WiFi performance, at least we can rule out your router slowing things down.
Your phone may be able to send data to the AP very quickly, but if Chromecast cannot receive that data fast enough because it has a poor wireless connection, then that doesn't help.
The data flow for screen casting is this:
Phone/Tablet <--A--> AP/router <--B--> Chromecast
Segment A is great, but segment B is what is suspect. Only hard numbers will tell.
speed4cast measures
Internet <--C--> AP/router <--B--> Chromecast
And you've already said your Internet speed is more than adequate (it should be unless you're on public/hotel connection, dialup, ISDN or repeating another WiFi connection).
B is the common part, and eliminating C, speed4cast will give us a measurement of B.
So run speed4cast on your Chromecast and tell us what it says on the screen.
If it confirms that your Chromecast has a good bandwidth connection, then it's something else in play. But in most cases interference from the TV makes Chromecast have less than optimal wireless speeds, and that's why you see some people complaining about streaming quality, because the streaming server is downgrading the bitrate (and hence quality) to compensate.
Screen casting doesn't do that, so if your Chromecast's wireless connection can't sustain the required speed you'll get blockiness, low framerate, jumps, or disconnection.
bhiga said:
Yes, speed4cast measures the speed between Chromecast and the Internet, but you cannot measure the Internet connection speed independently from the wireless connection on Chromecast, because the Internet traffic is flowing through the wireless connection.
So, if the reported upload/download speed is anything LESS than your Internet connection speed, then the Wireless connection* is slowing things down and the reported Internet connection speed is really your wireless connection speed.
For example, I have 50 Mbps down, 20 Mbps up. If I do an Internet speed test on a computer, I see 40+ Mbps down speed.
Yet, my Chromecast is only 8 Mbps down?
If I do the same test on my phone connected at 2.4 GHz I get much better results.
So, the wireless connection between the router and my Chromecast is limiting its transfer speed.
* if your wireless AP is not your router or there are other network segments between the Internet connection and the AP, they may be causing the slowdown instead of the WiFi connection. Also, if your router/AP is slow, the wireless devices may be connected at a high rate, but transfer to/from will never reach the maximum because the router/AP is slowing things down.
Checking the wireless speeds on your other devices doesn't mean anything because those other devices are not where your Chromecast. The closest you can get is maybe to put your phone/tablet as where Chromecast is, which is usually right up against the back of the TV. You're almost guaranteed to notice the speed will drop significantly.
As I mentioned earlier, tests with dedicated streaming video services like YouTube, Hulu, etc will not give you an idea of your wireless transfer speed unless they provide visual feedback for the connection quality.
They are designed to transparently handle a wide range of connection speeds, unlike screen casting which essentially says "I need this much bandwidth, or it's not going to work correctly."
If you have Netflix, you can try their speed test video.
This article talks about it. Note that on my Chromecasts with optimal wireless, I get up to 5300 kbps which appears to be the max.
On suboptimal wireless I get far less.
http://www.wired.com/2014/06/netflix-streaming-test/
Given your other devices have good WiFi performance, at least we can rule out your router slowing things down.
Your phone may be able to send data to the AP very quickly, but if Chromecast cannot receive that data fast enough because it has a poor wireless connection, then that doesn't help.
The data flow for screen casting is this:
Phone/Tablet <--A--> AP/router <--B--> Chromecast
Segment A is great, but segment B is what is suspect. Only hard numbers will tell.
speed4cast measures
Internet <--C--> AP/router <--B--> Chromecast
And you've already said your Internet speed is more than adequate (it should be unless you're on public/hotel connection, dialup, ISDN or repeating another WiFi connection).
B is the common part, and eliminating C, speed4cast will give us a measurement of B.
So run speed4cast on your Chromecast and tell us what it says on the screen.
If it confirms that your Chromecast has a good bandwidth connection, then it's something else in play. But in most cases interference from the TV makes Chromecast have less than optimal wireless speeds, and that's why you see some people complaining about streaming quality, because the streaming server is downgrading the bitrate (and hence quality) to compensate.
Screen casting doesn't do that, so if your Chromecast's wireless connection can't sustain the required speed you'll get blockiness, low framerate, jumps, or disconnection.
Click to expand...
Click to collapse
I could be wrong, but I still believe that "something" is being routed (uploaded) to the Internet and down to the CC. I guess I was not clear before, but the up/down speeds that I posted (1MB up -10MB down) were the numbers that the speed4cast tool reported from the CC. That's the reason I suspected the up link to the Internet was causing the problem in the first place as those numbers are the same numbers I get when I run Internet speed test from my laptop and from any mobile devices connected via WiFi. Intel PROSet also reports excellent signal quality (300.0 Mbps) when I put my laptop next to the CC. If I put my old SGS3 right next to the CC behind the TV... I can stream HD video using UPNP/DLNA media server and client in both directions while connected to the wireless network via the same AP of the router. I get no blockiness, low framerate, jumps or disconnection when streaming to/from my SGS5 to my SGS3. So, the wireless connection in segment B is fine (router <--B-- > CC). If there was a WiFi connectivity issue in this specific segment then I would experience the blockiness, low framerate, jumps and disconnection when streaming HD video to the CC using the Youtube app from my SGS5. There are no other network segments only one Router with 4 Gig Ports connected to devices that I turn off along with all the other devices that are connected via WiFi to avoid any conflicts/interference during my test.
Ah okay.
I don't think there's communication beyond downloading whatever bits are required for screen casting (the app itself).
And if your other devices are reporting the same up speed then your CC doesn't sound like it's being hampered by the wireless connection itself.
What carrier is your S5? Mine is AT&T and works well.
Is your native screen mirroring enabled? (Mine is)
In some cases it can enable/disable things that help or hurt the Chromecast mirroring.
Screen Casting now works with the new Chromecast App (v1.9.7) on my Nexus 7 running Lollipop 5.0.1. The N7 used to give me the same casting has ended error with prior versions of the app. But... it works fine until you want to disconnect from the casting session. I can not disconnect or try exiting the the app without hanging the N7. Oh well... This function is not mission critical for me anyway.
I still get the casting has ended error from my SGS5 and SGS3 using the same version of the app on KitKat 4.4.2. I guess now I can say with a high degree of certainty that the issue is not with my LAN setup or WiFi performance. There's still something else at play. I few days ago I noticed that the latest version of Speed4Cast (1.02) did not work with any of my devices. Once I updated Google Play Services to version 6.5.99 Speed4Cast started working again on all my devices. I think some authentication needs to happen between the casting device and some Google server... when this connection/authentication fails or is flaky there are issues casting the screen from the device.
I'm trying to get my stock Pixel to screen cast reliably to a Chromecast in my car. I've tried with a wi-fi hotspot and this seemed to drop out randomly which wasn't helpful whilst driving and then other times it wouldn't see an internet connection through it despite the phone being online.
So I've gone down the road of using a raspberry pi as a portable hotspot and rooting a Chromecast. This is more reliable once connected however the process of connecting is a bit tricky. At the moment I have to give the Chromecast an internet connection through a USB tether to the pi then connect to the wi-fi and cast screen. Eventually disconnecting the tether and the phone falls back to cell data whilst still casting the screen. My question is can I stop a rooted Chromecast with Eureka ROM needing an internet connection to be able to receive screen casts? I must note for some reason it only needs to be connected once after boot after that it will still be able to cast to despite complaining of no internet connection. Which is different to what a non rooted Cc did so it's like it's almost there but not quite.
Morphy99 said:
I'm trying to get my stock Pixel to screen cast reliably to a Chromecast in my car.
Click to expand...
Click to collapse
domsch1988 said:
I think the first thing to realize is, that the chromecast is not primarily intended as a screen mirror receiver. [...] There are great miracast receivers that do basically what you want.
Click to expand...
Click to collapse
@Morphy99 - You should try the Miracast receiver from Microsoft (Microsoft Wireless Display Adapter v2). Works great with my Nexus 7 (2013) on Android 6 and the app "SecondScreen" for screen ratio correction! :good:
Yes I realise this unfortunately with the Pixel unrooted miracast is not possible. Another reason I should have gone Samsung. Ive got a cheap ez cast dongle coming which hopefully will do it, although I'm sceptical at the minute. I'll update you if it works.