Document the Story of Your Social Life with 8tory

The different forms of social media are growing every day. It’s hard to imagine a day … more

Make Calling Your Loved Ones Easier and Cheaper this Diwali

Diwali, or Deepawali as some Indians call it, is the pride and joy of Indian … more

Big Android BBQ 5.0 Recap – XDA TV

This fifth annual Big Android BBQ has come and gone. The speakers have spoke, the sponsors have … more

Microsoft to Counter “OK Google” with Bing Torque

When Microsoft is making apps for Android, users should be aware that something … more
Post Reply

Chromecast app disconnecting after screen mirroring selected

OP RaphaRevolution

18th August 2014, 07:40 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Aug 2014
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.
4th September 2014, 03:10 PM   |  #2  
Junior Member
Thanks Meter: 1
 
1 posts
Join Date:Joined: Sep 2014
Quote:
Originally Posted by RaphaRevolution

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.

Same here, same devices.
The Following User Says Thank You to maufinelli For This Useful Post: [ View ]
5th September 2014, 09:55 PM   |  #3  
Senior Member
Thanks Meter: 18
 
260 posts
Join Date:Joined: Nov 2012
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.
6th September 2014, 07:49 AM   |  #4  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 866
 
2,225 posts
Join Date:Joined: Oct 2010
Donate to Me
More
Quote:
Originally Posted by lecorbusier

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.

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.
6th September 2014, 03:59 PM   |  #5  
Senior Member
Thanks Meter: 18
 
260 posts
Join Date:Joined: Nov 2012
Still stock & non rooted.
6th September 2014, 04:08 PM   |  #6  
Senior Member
Flag Vancouver
Thanks Meter: 481
 
3,122 posts
Join Date:Joined: Jan 2010
More
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
6th September 2014, 04:20 PM   |  #7  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 866
 
2,225 posts
Join Date:Joined: Oct 2010
Donate to Me
More
Quote:
Originally Posted by lecorbusier

Still stock & non rooted.

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.

Quote:
Originally Posted by cmstlist

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.

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.
7th September 2014, 03:54 PM   |  #8  
Senior Member
Flag Vancouver
Thanks Meter: 481
 
3,122 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by bhiga

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.

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
7th September 2014, 04:42 PM   |  #9  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 866
 
2,225 posts
Join Date:Joined: Oct 2010
Donate to Me
More
Quote:
Originally Posted by cmstlist

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.

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.
8th September 2014, 06:05 AM   |  #10  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Aug 2014
Plug Found some solution?
Quote:
Originally Posted by maufinelli

Same here, same devices.

Did you managed to find some solution?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes


Top Threads in Google Chromecast by ThreadRank