Closed GoogleCodeExporter closed 8 years ago
I receive this message wen trying to use play music app with android device
Original comment by gaphyoso...@gmail.com
on 6 Jan 2014 at 6:13
Received the same when the device started to overheat.
Original comment by borki...@gmail.com
on 11 Jan 2014 at 2:48
I revieved this message trying to connect my tv with youtube. My wifi signal is
ok, tw bars.
What does it mean.
Original comment by berthess...@gmail.com
on 21 Jan 2014 at 6:17
I received The same error, when I try to cast via YouTube.
First, chromecast still in black screen, and after crashs!
Original comment by c...@futtura.net
on 22 Jan 2014 at 10:08
Same issue here. Can't get chromecast to work.
Original comment by krezr...@gmail.com
on 24 Jan 2014 at 6:28
Having the same problem this evening
Original comment by brad.m...@gmail.com
on 24 Jan 2014 at 4:43
Having same issue. Network is fine.
Original comment by markal...@gmail.com
on 26 Jan 2014 at 5:45
Having same issue when I attempt to use Hulu+ on my Nexus 7 casting to
Chromecast.
Original comment by micsey...@gmail.com
on 26 Jan 2014 at 8:10
I receive this error message every time I try to cast anything. I'm running the
latest version of Chrome, full strength wi-fi signal on Chromecast and on my
mac, have restarted Chromecast multiple times, have restarted Chrome and my mac
multiple times, yet the problem continues to exist.
Original comment by pduvv...@gmail.com
on 28 Jan 2014 at 4:20
After 10 days, the error continues.
I bought Chromecast last week, used for 2 days, then immediately began the
problems.
Money thrown in the trash.
Original comment by c...@futtura.net
on 31 Jan 2014 at 12:45
Same problem here. Cant cast anymore even after reboot android and chromefast
too.
Original comment by evanedwa...@neo.rr.com
on 3 Feb 2014 at 2:15
Thank you for your support of Chromecast. We've just released a major update
to the Google Cast SDK and will be closing your issue.
Take a look at http://googledevelopers.blogspot.com/ for more information.
Original comment by l...@google.com
on 3 Feb 2014 at 11:29
if you give a link for more information, can you make the damn link more
specific. it just takes you to the blog. i dont want to scroll thru pages of
blogs to find the info. wtH?
Original comment by 705...@gmail.com
on 20 Feb 2014 at 8:10
still not fixed... same issue persist
Original comment by ipan...@gmail.com
on 22 Feb 2014 at 2:48
Even I was facing the same issue in chromecast , following fixed the issue:
1. Remove power from samsung tv. Waited for couple of minutes.
2. Did reset of chromecast (power recycle by holding the chromecast button for
25 seconds)
Should be because of Cec hdmi feature.
Original comment by aditya.m...@gmail.com
on 6 Mar 2014 at 2:42
I believe that Google has decided where we should use the dongle. I am using it
behind a VPN connection to avoid tracking, and it does not work in that way.
But if I run it without any VPN, it works. So Google is trying to control how
we use this device, and where we use it. I guess the problem is worst when you
travel overseas. Less than a month this dongle was working properly and without
any obstruction from Google.
Original comment by rafael.g...@gmail.com
on 6 Apr 2014 at 8:34
Solution in post #15 worked for me. Thanks.
Original comment by greg.j.p...@gmail.com
on 6 Apr 2014 at 12:42
Solution in post 15 did not work for me. Still I have the problem when I
connect to VPN. If I use it without VPN it works properly. So, it is not the
Cec HDMI feature, and my TV is not Samsung. Before March, this Chromecast was
working always fine. So, if they are going to show that they are not spying on
what we do, and getting further the VPN, I believe it is a blocking process
from Google.
Original comment by rafael.g...@gmail.com
on 18 May 2014 at 11:22
[deleted comment]
Solution in #15 didn't work for me and my Samsung tv.
Original comment by benismai...@gmail.com
on 17 Dec 2014 at 12:20
It is very frustrating.
I tried restarting, resetting and so many other option but no solution to this
error.
Many time it does not respond
Original comment by jyothi...@gmail.com
on 30 Oct 2015 at 1:17
Solution in post #15 worked for me. Thanks
Original comment by milehigh...@gmail.com
on 14 Nov 2015 at 2:37
Original issue reported on code.google.com by
kristian...@gmail.com
on 3 Jan 2014 at 1:32