Database Develop

[Q] Galaxy Tab (P1000) Wireless-N Speeds at 5ghz... (What are your results?)

Hello,
Regarding dual-band Samsung Galaxy Tabs correctly operating on 5Ghz/40mhz...
Is anyone seeing 150mbit (or better) with their Galaxy Tab using 5Ghz at 40Mhz?
Only respond if you have a galaxy tab, and you know that you are using 5ghz. Also please quickly review ALL of the following relevant information before attempting to respond to the above questions;
According to the following search info the galaxy tab supports 5ghz dual-band wireless-n, and the overcome rom v1.6.4 supports 5ghz wireless-n also.
"Dual Band Wi-Fi"
http://www.google.com/search?hl=&cat=&meta=&num=&ie=utf-8&q=galaxy+tab+5ghz
"WiFi-N on the 5ghz band now works"
http://www.google.com/search?hl=&cat=&meta=&num=&ie=utf-8&q=galaxy+tab+overcome+rom+5ghz
Additional info:
I am using a Linksys e3000 (dual band) router, and can connect at 300mbit stable link-speed (file transfer speeds are 15MegaBYTE/sec average) using a Linksy AE1000 USB adapter (with any pc or notebook) which I purchased to resolve similar (speed/streaming/transfer) issues with the onboard single-band 2.4ghz wireless-n adapter in another device I was working on.
I have both 2Ghz and 5Ghz networks and devices completley seperated. 5ghz is operating at 40Mhz (specifically wireless-n) only (automatic channel) and 2.4ghz operating at 20Mhz (wireless-g only) with a specified channel that is not being used by any neighbors.
I do not have any issues with connection, stability, or speed/transfers with any other N or G devices...
I can connect to the 5ghz (wireless-N only) network with the galaxy tab although it is not very stable. Speed fluctuates btwn 11mbit and 65mbit, and is pretty much bunk for video streaming (standard xvids or mkvs) via smb/cifs using MoboPlayer (and others).
Both video formats (xvid & mkv) play fine locally via (8GB class4) sdcard upto 720p. 1080p mkv (using ext2/ext3 on a second partition on the external sd) are completely unwatchable on (16GB class2) sdcard. For that reason and the flakey 5ghz wireless-N speed which effects the (unwatchable) playback/streaming of even small 30 minute fast-motion (action and/or animated) xvids almost makes me want to return the TAB.
I am running Overcome 1.6.4 rom+kernel (froyo) and have no issues other than the battery life seems to deteriorate rather quickly (and it seems to generate more heat) while using 5ghz for long periods.
Has anyone here successfully connected at 150mbit (stable) or better (using 5ghz) with their Galaxy Tab (P1000) yet? And if so, was there anything extra that you needed to do to accomplish that speed and/or stability with this device?
Please review all of the above before answering, thanks.

bump. Anyone?

Couple of questions for you first.
1- How are you measuring your speed?
2 - You do realize that SMB/CIFS sharing is not the ideal way to stream video? Thereis much more overhead in you bandwidth versus say using a streaming server (ie Plex) or using a DLNA player/server to stream.
3 - The MKVs that you're streaming, are they all 720 or are some 1080? Do some have DTS? Both the 1080 and the DTS will cause playback issues streaming as both need alot of work done to be processed correctly by the device.
For streaming video I have found, after much testing, that anything that has DTS or is high bitrate HD content will cause thetab to stutter. I find that remuxing to an MP4 with AAC 2 channel audio and your streaming problems will disappear even using SMB.
Think of it this way, we don't have 1080 resolution nor surround sound, why even strain the device to process it. I use a Plex setup with an AppleTV using dual band N with a G signal as well and never have issues even over 3G. My router is a Linksys E3000 with Bell Fibe 25 down with 7 up VDSL internet connection.
Lemme know how you make out.
Sent from my GT-P1000 using XDA Premium App

I just got a Linksys E3000, and I can't seem to get my Galaxy Tab to see the network at 5 GHz at all.
The E3000 is simultaneous dual band, and it's connecting fine to the 2.4 GHz network.
Did you have to do anything to get it to just connect?

Hey slimdizzy, thanks for responding to a question with a question.
If you pay more attention to the post you might notice at least one of your questions was already answered prior to your reply.
Correct me if i am wrong but the overhead in CIFS/SMB is minimal/insignificant in respect to my request/questions.
There is also no need to implement other technologies (client/sever software) to accomplish the task of streaming using pre-existing technlogy that has been used for numerous years over much less powerful (or capable) hardware or infrastructure.
The question is NOT concerning what technolgy to use, but rather what connection (and link) speeds people are getting over 5ghz Wireless-N, with this specific device, so if you cannot answer the question there is really no need to respond.
Thank you.

Again unrelated to my request/questions. (manekineko),
You might want to read the original post again more thoroughly.
See the second paragraph after "additional info" in the first post. Also notice I mentioned a rom/kernel that supports 5GHZ Wireless-N specifically.

Bump from the dead.
commenter, were you able to find a solution to this problem?

chrome tab over wifi

So my PC is connected to my router by Ethernet cable. I can cast my chrome tabs and watch video play smooth with no issues. If i use my laptop that has similar specs as my pc and i connect via wifi, video will play very choppy on my tv. I have even tried it right next to my router to ensure the highest speed. A friend of mine is having the same issue with his computer which is also connected over wifi. Even at the lowest video settings its still choppy. Is this a known issue with trying to cast your tab over wifi or am I missing something?

herculese1 said:
So my PC is connected to my router by Ethernet cable. I can cast my chrome tabs and watch video play smooth with no issues. If i use my laptop that has similar specs as my pc and i connect via wifi, video will play very choppy on my tv. I have even tried it right next to my router to ensure the highest speed. A friend of mine is having the same issue with his computer which is also connected over wifi. Even at the lowest video settings its still choppy. Is this a known issue with trying to cast your tab over wifi or am I missing something?
Click to expand...
Click to collapse
I'm guess that if your router is not an "N" router (802.11n), it's probably having a hard time taking the stream from your laptop then sending it back to the Chromecast (I could be wrong). I have an N rounter and can stream wirelesly from my desktop to the chromecast with little to no stutter.
Also, make sure your chromecast has a good wifi signal. I had to use the included HDMI extender to give mine a little extra boost in signal.

Instead of telling us it's similar specs, what are the actual specs?

lebeauc said:
I'm guess that if your router is not an "N" router (802.11n), it's probably having a hard time taking the stream from your laptop then sending it back to the Chromecast (I could be wrong). I have an N rounter and can stream wirelesly from my desktop to the chromecast with little to no stutter.
Also, make sure your chromecast has a good wifi signal. I had to use the included HDMI extender to give mine a little extra boost in signal.
Click to expand...
Click to collapse
Yes my router is a "N". I have a Cisco E4200V2 which is a pretty good router.

Also, make sure your chromecast has a good wifi signal. I had to use the included HDMI extender to give mine a little extra boost in signal.[/QUOTE]
luega said:
Is your tab configuration a little low? Try another tab one more time,if still choppy,that is not issue of tab but TV.
Click to expand...
Click to collapse
My chromecast doesn't move and it has enough wifi signal to stream when using the ethernet connected computer so it should have the wifi signal. How would it be the tv? It works fine with my desktop.

Wireless connection will always be less reliable than a wired connection. I also doubt that your laptop has the same specs as your desktop in reality. Also, keep in mind that the tab/screen casting feature is still under development and not entirely reliable.

Roberek said:
Wireless connection will always be less reliable than a wired connection. I also doubt that your laptop has the same specs as your desktop in reality. Also, keep in mind that the tab/screen casting feature is still under development and not entirely reliable.
Click to expand...
Click to collapse
Yea i am hoping that when it comes out of beta it will be better over wifi. my pc (6 years old) is has a core 2 quad and it runs perfectly. My friend has a less than 1 year old mac that is quad core and has the issue over wifi. Theirs no way his 1 year old mac is not strong enough to support chromecast. I was ready to say "oh well it doesn't work over wifi smoothly" however it seems some people on here are claiming it should.

herculese1 said:
Yes my router is a "N". I have a Cisco E4200V2 which is a pretty good router.
Click to expand...
Click to collapse
Even with good N router, you still need to setup right
For example use only G and N mix better yet N only
Set router to use 40MHz instead of 20Mhz
Use WPA2 AES for security instead of something else
There are tons of optimization that you can do to the network.
Best way is to hack your router firmware and replace it with DDWrt
There is a large community full of people over at DDWrt that know their wireless stuff.
I have a D link router cheap but hack with DDWrt and I am streaming ok
Sent from my Nexus 7 using Tapatalk 4

WiFi Bandwidth and Router considerations

Because Chromecast communicates solely via WiFi, the minimum sustained wireless bandwidth is critical for streaming quality.
This is usually not a problem for "normal" Chromecast applications that pull streams from the Internet - those services are designed to adapt to and scale with the available connection speed.
Content streaming from local devices is a different scenario altogether.
Chromecast doesn't necessarily work the same as traditional set-top media players (Apple TV, WDTV, Roku, etc) when streaming media from your phone/tablet/computer (device-local) and LAN-based (from a server) media can consume more bandwidth than you would expect.
Depending on where the media is located and how it is being sent to Chromecast, up to 3x the media's bitrate may be consumed (and required) on the WiFi network. If you have high bitrate media, this can easily overload an 802.11g connection or even an 802.11n connection.
Keep in mind that connection speed is not constant, and is limited by both your environment and your router.
Other nearby WiFi devices can cause interference, and the 2.4 GHz wireless band that Chromecast uses is "crowded" with many devices like cordless telephones and microwave ovens using overlapping frequencies.
Also, routers vary in the wireless speeds they can maintain. Just because you have a 802.11n 150 Mbps connection, that does not mean your router can truly sustain 150 Mbps throughput.
Better routers advertise use cases for "HD streaming" and have Gigabit LAN ports rather than 100 Mbps LAN ports found on cheaper models.
Just like a Gigabit Ethernet USB 2.0 adapter will never reach full Gigabit speed due the USB 2.0 bottleneck (480 Mbps), cheaper routers often are limited by their internal processor's lack of forwarding speed.
See the attachments for use examples and how the required bandwidth can multiply: Note that the 10 Mbps figure is just an example.
Standard Internet stream example
YouTube, Hulu Plus, HBO Go, VEVO, etc use this methodology
Direct stream from LAN storage example
Plex (from a local Plex server) and fling (from a desktop) work this way. Desktop and Tab casting from Chrome also uses this data flow.
Data is sent from the LAN device via WiFi
Chromecast receives data from the LAN device via WiFi
Streaming from wireless device storage example
Casting content stored on the device (device-local) from Avia or RealPlayer Cloud use this method.
Data is sent from the casting device via WiFi to Chromecast
Chromecast receives data via WiFi
Forwarding from LAN storage example
Casting content stored on a LAN device (DLNA, network share, etc) from Avia uses this method.
Data is sent from the LAN device to casting device running Avia via WiFi
Data is sent from the casting device running Avia via WiFi to Chromecast - this is the forwarding piece, data travels through
Chromecast receives data via WiFi
To optimize available bandwidth for Chromecast:
Use an 802.11n dual-band router and put your other wireless devices on the 5 GHz access point whenever possible
or use a separate WiFi access point connected to the wired network for Chromecast
Use wired connections for cast sources (server/desktop/laptop) wherever possible
Reencode high-bitrate media to lower bitrate (4 Mbps should be fine for most use)
Optimize Chromecast's ability to get a stable WiFi signal - move it away from the TV using the HDMI extender or an HDMI extension cable
and/or move your router so it's closer to Chromecast (but not too close - too close can get into a "drowned in the noise" situation)

Great Post this deserves a Pin!

One big thing a lot of people don't realize is that wireless is half duplex...
If you have 2 devices on the same wireless network transferring data between each other, they will do so at half the speed, because only one device can talk at a time.
Say for example you have a PC wired to your router, and another PC on wireless.. You can copy a file between these computers at around 6MB/sec. Now you take the wired PC and connect it to the same wireless network instead. You will notice your copy speed is now around 3MB/sec.
If you are utilizing a wireless repeater to connect any of your devices to your wifi network, those connected to the repeater will experience the same halving of speed as well.
This is why having your local media source on a different band or wired helps so much.

stevewm said:
One big thing a lot of people don't realize is that wireless is half duplex...
If you have 2 devices on the same wireless network transferring data between each other, they will do so at half the speed, because only one device can talk at a time.
Say for example you have a PC wired to your router, and another PC on wireless.. You can copy a file between these computers at around 6MB/sec. Now you take the wired PC and connect it to the same wireless network instead. You will notice your copy speed is now around 3MB/sec.
If you are utilizing a wireless repeater to connect any of your devices to your wifi network, those connected to the repeater will experience the same halving of speed as well.
This is why having your local media source on a different band or wired helps so much.
Click to expand...
Click to collapse
Here's a scenario I would appreciate your comment on:
I have a bridge that connects to my main router. The media source (laptop) is connected direct to the bridge which is in the living room with my CC, the CC is wireless to the bridge. Will the distance the bridge is from the main router come into play if doing local media?

sherdog16 said:
Here's a scenario I would appreciate your comment on:
I have a bridge that connects to my main router. The media source (laptop) is connected direct to the bridge which is in the living room with my CC, the CC is wireless to the bridge. Will the distance the bridge is from the main router come into play if doing local media?
Click to expand...
Click to collapse
It shouldn't.... Unless the run to the main router is abnormally long.
My current setup has my plex server across the house from my TV room. Two out of three routers are upstairs and one is in the room with my plex server. All but one router is set up as access points. The distance combined between the three routers is roughly 200 feet. The distance is split between the three. Then roughly 25 feet from the closest router to the ccast. I have no more noticeable lag in the TV room than using the ccast in the back bedroom that the plex server is in.
I am sure if I was going to ping test this I would have a higher latency the further away it goes.... But like I said to real world use I can't tell it slows it down.
Sent from my Nexus 5 using Tapatalk

rans0m00 said:
I am sure if I was going to ping test this I would have a higher latency the further away it goes.... But like I said to real world use I can't tell it slows it down.
Click to expand...
Click to collapse
Exactly that. For home use, distance of wired connections doesn't matter much, as long as it's within specs and packets aren't being lost.
Distances for wireless connections, on the other hand, make a huge difference both in terms of latency and sustained transfer speed (bandwidth).

I've noticed that video casted from a tab is barely smooth at 480p. I am upstreaming at approx 150kbps.
When I try 720p, it struggles at 300kbps dropping to 150 alot. Using "extreme" it about the same rate but more choppy.
I have a N network with my laptop connected at 300M. I can usually transfer files around 3-6Mbps.
I'm a little confused why with chromcast, I can barely maintain 150kbps. Even if you multiply by 3, I'm not getting over 1mbps.

enricong said:
I've noticed that video casted from a tab is barely smooth at 480p. I am upstreaming at approx 150kbps.
When I try 720p, it struggles at 300kbps dropping to 150 alot. Using "extreme" it about the same rate but more choppy.
I have a N network with my laptop connected at 300M. I can usually transfer files around 3-6Mbps.
I'm a little confused why with chromcast, I can barely maintain 150kbps. Even if you multiply by 3, I'm not getting over 1mbps.
Click to expand...
Click to collapse
It's likely not a wireless connection issue but rather a processing limitation on the computer you're casting from.
I just casted a 480p tab of full-tab video and my network utilization ranged from about 1.25 Mbps to bursts of 12 Mbps. The average was around 2-3 Mbps. What's the CPU utilization look like when you're casting?
Do other Chromecast apps like YouTube work okay with 720p or 1080p videos?

bhiga said:
It's likely not a wireless connection issue but rather a processing limitation on the computer you're casting from.
I just casted a 480p tab of full-tab video and my network utilization ranged from about 1.25 Mbps to bursts of 12 Mbps. The average was around 2-3 Mbps. What's the CPU utilization look like when you're casting?
Do other Chromecast apps like YouTube work okay with 720p or 1080p videos?
Click to expand...
Click to collapse
CPU is an i5-2520M. Utilization is only around 20-30%. I've tried with and without Nvidia GPU.
Youtube seems ok at 720 and 1080, however, I thought that youtube videos get streamed directly to chromcast vs the laptop.
Also, when I stream a youtube video, I have no idea if chromecast sticks with my browser setting or figures out its own quality setting based on bandwidth. I thought it was the later.
Are you using regular Chrome, or Chrome Canary?

enricong said:
CPU is an i5-2520M. Utilization is only around 20-30%. I've tried with and without Nvidia GPU.
Youtube seems ok at 720 and 1080, however, I thought that youtube videos get streamed directly to chromcast vs the laptop.
Also, when I stream a youtube video, I have no idea if chromecast sticks with my browser setting or figures out its own quality setting based on bandwidth. I thought it was the later.
Are you using regular Chrome, or Chrome Canary?
Click to expand...
Click to collapse
Interesting... You're correct that YouTube grabs the stream directly and determines the best settings. But if you have a 1080p TV and YouTube is pulling a 480p stream, it'll definitely be noticeable - especially on things like text.
My Chrome is Version 32.0.1700.107 m
and Google Cast Extension is 14.123.1.4
My system is relatively old, but it was a powerhouse in its day and still fine for what I do with it.
Windows 7 Professional 64-bit
Dual Quad-Core AMD Opteron 8389 2.9 GHz
32 GB RAM
AMD Radeon HD 7750​

bhiga said:
Interesting... You're correct that YouTube grabs the stream directly and determines the best settings. But if you have a 1080p TV and YouTube is pulling a 480p stream, it'll definitely be noticeable - especially on things like text.
My Chrome is Version 32.0.1700.107 m
and Google Cast Extension is 14.123.1.4
My system is relatively old, but it was a powerhouse in its day and still fine for what I do with it.
Windows 7 Professional 64-bit
Dual Quad-Core AMD Opteron 8389 2.9 GHz
32 GB RAM
AMD Radeon HD 7750​
Click to expand...
Click to collapse
I'm running 35.0.1840.2 of Chrome and 14.123.1.5 of the extension.
I just tried installing regular chrome and had the same results.
your computer is def more powerful than mine, but I don't think thats the issue with such a low cpu utilization.

enricong said:
I'm running 35.0.1840.2 of Chrome and 14.123.1.5 of the extension.
I just tried installing regular chrome and had the same results.
your computer is def more powerful than mine, but I don't think thats the issue with such a low cpu utilization.
Click to expand...
Click to collapse
Weird... do you have the Automatically resize the browser to best fit the receiver screen when casting a tab option enabled? That should provide lowest impact as it should eliminate the need to scale.
Does it make a difference if your laptop is plugged into wall power, or on a wired instead of wireless connection?

bhiga said:
Weird... do you have the Automatically resize the browser to best fit the receiver screen when casting a tab option enabled? That should provide lowest impact as it should eliminate the need to scale.
Does it make a difference if your laptop is plugged into wall power, or on a wired instead of wireless connection?
Click to expand...
Click to collapse
ok, I just tried the wired connection and got some results. on 480p I got 150kbps, 720p got 300kbps, and extreme got around 600kbps.
720 and above started looking a little choppy. Picture Quality even at extreme was quite poor.

enricong said:
ok, I just tried the wired connection and got some results. on 480p I got 150kbps, 720p got 300kbps, and extreme got around 600kbps.
720 and above started looking a little choppy. Picture Quality even at extreme was quite poor.
Click to expand...
Click to collapse
My CPU load jumps about 15-20% when casting too, so that seems in-line.
Weird, it's almost like something in Windows is throttling something...
You don't have some kind of third-party firewall or anything, do you?
If you're using the Windows Firewall, check the Advanced Settings for Inbound and Outbound rules on Wireless Portable Devices. My rules for those are disabled, but some folks have reported toggling them helped.

bhiga said:
My CPU load jumps about 15-20% when casting too, so that seems in-line.
Weird, it's almost like something in Windows is throttling something...
You don't have some kind of third-party firewall or anything, do you?
If you're using the Windows Firewall, check the Advanced Settings for Inbound and Outbound rules on Wireless Portable Devices. My rules for those are disabled, but some folks have reported toggling them helped.
Click to expand...
Click to collapse
I have Avast which has some network protection
Tried toggling the settings in Windows firewall
I even tried disabling the firewall and anti-virus completely.
no difference

enricong said:
I have Avast which has some network protection
Tried toggling the settings in Windows firewall
I even tried disabling the firewall and anti-virus completely.
no difference
Click to expand...
Click to collapse
Only other thing I can think of is to try unbinding Avast's network filter from the network interface (Properties the device itself and try un-checking any extra computer-looking icons) and trying it, often times disabling the firewall doesn't fully disable the network filter.

bhiga said:
It's likely not a wireless connection issue but rather a processing limitation on the computer you're casting from.
I just casted a 480p tab of full-tab video and my network utilization ranged from about 1.25 Mbps to bursts of 12 Mbps. The average was around 2-3 Mbps. What's the CPU utilization look like when you're casting?
Do other Chromecast apps like YouTube work okay with 720p or 1080p videos?
Click to expand...
Click to collapse
Just to clarify, are you referring to BITS or BYTES?
I refer to bytes, 150kbytes/sec = approx 1mbit/sec

enricong said:
Just to clarify, are you referring to BITS or BYTES?
I refer to bytes, 150kbytes/sec = approx 1mbit/sec
Click to expand...
Click to collapse
I'm usually pretty careful about MB (Megabytes) vs Mb (Megabits) so I'm referring to megabits. so divide my figures by 8 for bytes.

bhiga said:
I'm usually pretty careful about MB (Megabytes) vs Mb (Megabits) so I'm referring to megabits. so divide my figures by 8 for bytes.
Click to expand...
Click to collapse
well, even with bits, you're still faster than me.
I submitted a support ticket to google. still trying to get through the general "is it plugged in?" questions.

enricong said:
well, even with bits, you're still faster than me.
I submitted a support ticket to google. still trying to get through the general "is it plugged in?" questions.
Click to expand...
Click to collapse
Yeah, it took me 2 or 3 rounds to get past the basics... Please keep us updated on what you find out.

Casting screen to "ChromecastName" has ended

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.

Problems streaming media from phone, but not pc

I just got my chromecast last week. The only reason I bought my chromecast is because I have an older (non-smart) tv that has no streaming capabilities, and my ps3 died. I have a PS4 but the ps4 does not support any playback of files (mp3, mp4, avi etc) like you could on the ps3. I had a big library of music and home movies on my ps3., and now I had no way to play this media on my tv. So I bought a chromecast.
Streaming from the PC works great. I use the videostream extension with the remote app for android. And videos/movies stream great with no lagging at all.
So I decided to try and stream data from my android phone. I tried just about every app on the play store. From Avia, to AllCast and everything in between. Yet everything I try lags terribly. Every video that I try and stream (even very short 10-20 second videos) freeze and buffer every few seconds.
I know my network can handle the streaming. I have a wireless AC router and 50+MB/s ISP connection. Also Once again streaming from my pc works flawlessly. Streaming from youtube app on my phone to the tv also works flawlessly. So why is it that I can't stream videos taken by my phone properly?

What is your phone? Can you try to upload a video from the phone to the pc and check the speed?

philip67 said:
What is your phone? Can you try to upload a video from the phone to the pc and check the speed?
Click to expand...
Click to collapse
Sorry I should have specified that. I have the HTC ONE M8.
EDIT:
Using the wifi file transfer app, I downloaded a 126MB video file to my PC and it averaged at around 5.5MB/s (seems slow for wireless AC). Also my PC is hard wired to my router, and I was sitting about 2 feet away from my wireless router. So signal strength shouldn't cause an issue.

The phone has to work as a tool that not only transfers the video to the Chromecast, but it must also work as an on the fly media transcoder and server. This is a lot of strain for one phone.

Try casting a video with format and resolution that is natively supported on chromecast. But the speed from 5.5 Mb is also a bottleneck for casting a video with higher resolution.

The HTC one M8 is still pretty powerful in terms of phones.
I think I figured out the problem. I have a dual band router. I connected the chromecast to the 5G band (for obvious reasons. Faster speeds) but as it turns out I'm having issues with my router
I did a test on my phone. Sitting right next to my router so signal strength was excellent, I checked the link speed of both the 5G band and the 2.4 and the 5G band is only showing 24mbps Where as 2.4 band is maxed out at 74mbps. I'm not sure why my 5GHZ band is so slow. It's wireless AC and should be way faster.
I also did a speed that that confirmed it. While connected to my 5ghz band my speed was It 20mbps download. On 2.4ghz I averaged over 30, and then I suspect that the rest was limited by my isp.
So I believe since I have my chromecast connected to the 5ghz band, this is causing the sluggish playback.

The Chromecast doesn't support 5 GHz, only 2.4 GHz. In any case most people find that the range isn't very good with 5 GHz. If the signal has to go through a few walls, you might be better off with 2.4 GHz anyway.
But keep in mind that if both your phone and the Chromecast are using the 2.4 GHz band, streaming from the phone to the router and then from the router to the Chromecast is using 2x the wireless bandwith compared to your hard-wired PC streaming to the Chromecast.
The M8 is fairly fast for a phone, but nowhere near the performance of a desktop PC, so it might still be lagging due to memory/CPU performance issues.