Open GoogleCodeExporter opened 9 years ago
[deleted comment]
I could also verify using an nmap port scan that port 9222 is not open while my
receiver app is running.
Original comment by dev.nobu...@gmail.com
on 19 Mar 2015 at 5:28
[deleted comment]
[deleted comment]
My Chromecast stick is at a point where I can debug my receiver app again after
rebooting the device. However, every single time the receiver app closes and I
reopen it, I cannot debug it any more. I have to reboot the stick in order to
enable port 9222 again.
Original comment by dev.nobu...@gmail.com
on 19 Mar 2015 at 7:41
Can you submit a feedback report and prefix it with "Issue 537"?
https://support.google.com/chromecast/answer/3187017?hl=en
Original comment by jonathan...@google.com
on 19 Mar 2015 at 10:23
Thanks for the response. I used the Chrome browser extension for Chromecast to
send feedback and attached the Chromecast log.
Original comment by dev.nobu...@gmail.com
on 19 Mar 2015 at 10:41
Thanks, we'll let you know if we need any additional information.
Original comment by jonathan...@google.com
on 23 Mar 2015 at 5:40
I am also experiencing this problem and have submitted feedback as requested by
Leon Nichols and Ali Nadaff in
https://plus.google.com/u/0/+JimRenkel2014/posts/P7VQ8jppuKJ?cfem=1
Jim Renkel
Original comment by jim.ren...@gmail.com
on 29 Mar 2015 at 11:23
yesterday it worked for some reasons but today it again does not work :(
the actual debugging was running on
https://chrome-devtools-frontend.appspot.com/serve_rev/@188559/inspector.html?ws
=*IP*:9222/devtools/page/*UUID*
also i had to click on the shield to load "unsafe scripts".
The Version of my device hasn't changed (still 27946)
Original comment by kujans...@gmail.com
on 11 Apr 2015 at 7:43
Has there been any progress on this issue? I haven't been able to do any
receiver development / debugging for some time now.
Would it help you if I sent you the Chromecast stick that's "stuck"? I'm
planning on buying another one, hoping that I'll be able to do receiver
development on it, so I could spare this one that's "stuck".
Thanks in advance,
Jim Renkel
Original comment by jim.ren...@gmail.com
on 12 Apr 2015 at 1:55
@Jim: doing factory resets up to 3 times in a row gets my Chromecast into a
state where I can debug my receiver app again for a single session - until the
app closes or crashes. After that I need to do several factory resets again.
It's a pain but currently the only way to keep on working on my app. Maybe that
will also work for you.
Original comment by dev.nobu...@gmail.com
on 13 Apr 2015 at 5:44
@dev.nobu...: Thank you for the tip. I may give it a try, but it sounds like it
would be faster, and less expensive in time, to just drive to BestBuy, buy
another Chromecast stick for development and testing, and use the "stuck" stick
for non-development testing, or maybe even use it for real. :-( Again, thanks
for the tip.
Original comment by jim.ren...@gmail.com
on 14 Apr 2015 at 1:21
Hi,
I only have this problem (debugging via port 9222) when the Chromecast is
connected to a bad wifi or with some wifi routers, I don't have this
problem with good wifi without interference, e.g when I using Wi-FI hotspot
on my Android phone. On bad wifi it helps to remove the Chromecast and let
it cold down for a while (30 minutes). The problem began to arise after
Google added the function Guest Mode to Chromecast. I have also reports
from customers that they have increase of wifi issues with Chromecast after
Google added Guest Mode.
Original comment by patrik.c...@magine.com
on 14 Apr 2015 at 11:17
I have the same problem. Because of my server I had timeouts when trying to
launch receiver app via Android sender. I have changed the server to VPS and it
works OK. The problem is with debugging as stated above. I can connect via 9222
only ones. When the app crashes or sth makes senders disconnect so that the app
is teared down, I cannot connect enymore via Google Chrome on port 9222. I get
ERR_CONNECTION_REFUSED I need to do a factory reset, setup everything from
scracth and then I can debug...for one session.
Original comment by tomek.ig...@gmail.com
on 15 Apr 2015 at 10:24
Just stumbled upon this problem as well this night when trying to debug my app
again. It just won't work, even though I didn't change *anything* from last
time I debugged it. What's up with all these stability issues you guys are
having? With the connection, now with the debugger...
Original comment by bogdan.z...@gmail.com
on 18 Apr 2015 at 8:12
We have more customer issues about Wifi connection problems with our App
(MagineTV) after Chromecast firmware update 27946. I hope Google have noticed
this and working on a solution (in stealth mode I guess). We using our Google
contacts to make them aware of the problem.
Original comment by patrik.c...@magine.com
on 20 Apr 2015 at 8:16
Went and bought a new Chromecast stick, installed it, and I am able to debug my
app on it.
So apparently, the old Chromecast stick somehow got "poisoned".
I repeat my offer: if it would help you guys solve this problem, I will gladly
ship the problem Chromecast stick to you.
Original comment by jim.ren...@gmail.com
on 21 Apr 2015 at 2:23
Same Here. I takes 2-5 reboots to get the debuger going.
ERR_CONNECTION_REFUSED... WTF???
If I buy a new Chromecast stick will it "burn out"? How soon?
Original comment by sergey.m...@gmail.com
on 25 Apr 2015 at 3:27
Original issue reported on code.google.com by
dev.nobu...@gmail.com
on 18 Mar 2015 at 8:21