Cast visibility events are inconsistent

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Listen to visibility changed events in a custom receiver app
2. Cast the app to a TV.
3. Turn the TV off and then back on Note: the Chromecast is attached to a wall 
charger so it does not lose power

What is the expected output? What do you see instead?
In the developer console, I logged to the visibility changed events. I get the 
following when I do the step above:
Turn TV off
Turn TV on
[1362.485s] [cast.receiver.IpcChannel] Received message: 
{"data":"{\"type\":\"visibilitychanged\",\"visible\":false}","namespace":"urn:x-
cast:com.google.cast.system","senderId":"SystemSender"}
[1362.490s] [cast.receiver.CastMessageBus] Dispatching CastMessageBus message
[1362.493s] [cast.receiver.CastReceiverManager] Dispatching visibility changed 
event false
Visibility event received (visibility is now: notvisible)
[1375.236s] [cast.receiver.IpcChannel] Received message: 
{"data":"{\"type\":\"visibilitychanged\"}","namespace":"urn:x-cast:com.google.ca
st.system","senderId":"SystemSender"}
[1375.242s] [cast.receiver.CastMessageBus] Dispatching CastMessageBus message
[1375.245s] [cast.receiver.CastReceiverManager] Dispatching visibility changed 
event null
Visibility event received (visibility is now: unknown)

Please provide any additional information below.
I'm not sure if this has to do with how the TV reports changes to the 
Chromecast or not. It's seems strange that the events come sequentially like 
that.

Original issue reported on code.google.com by DanWKenn...@gmail.com on 10 Aug 2015 at 3:51

[GoogleCodeExporter]

Note: I would expect the visibility change to notvisible to happen when I 
turned the TV off

Original comment by DanWKenn...@gmail.com on 10 Aug 2015 at 3:53

[GoogleCodeExporter]

As I was debugging this problem, it seems the visibility events get dropped 
when the TV gets turned off but they happen correctly when you change the input 
on the TV. i.e. The NOT_VISIBLE event gets triggered when you switch input away 
from the Chromecast and the VISIBLE event gets triggered when the input is 
switched back to the Chromecast.

Original comment by DanWKenn...@gmail.com on 10 Aug 2015 at 6:34

[GoogleCodeExporter]

What's the make and model of the TV for which you're seeing this inconsistency? 
Have you seen this occur on any other TVs? 
What's your Chromecast's firmware version number?

Original comment by jonathan...@google.com on 11 Aug 2015 at 6:28

• Changed state: NeedInfo

[GoogleCodeExporter]

We're testing on two TV's and Chromecasts.

The first set up is:
TV: Insignia NS-50D550NA15
Chromecast Firmware: 38401

The second set up is:
TV: LG 42LF5600
Chromecast Firmware: 38401

The issue happens as described with both TV's

Thanks for the quick reply.

Original comment by DanWKenn...@gmail.com on 11 Aug 2015 at 7:05

[GoogleCodeExporter]

Thanks for the information, we'll look into it.

Original comment by jonathan...@google.com on 11 Aug 2015 at 10:07

• Changed state: Acknowledged

[GoogleCodeExporter]

Dan, could you please submit a feedback report with device logs with "icoolidge 
insignia standby" as the title?

Original comment by icooli...@google.com on 31 Aug 2015 at 5:19

[GoogleCodeExporter]

Any updates on this?

Original comment by andrei.z...@noriginmedia.com on 24 Sep 2015 at 11:55

[GoogleCodeExporter]

Dan, did you submit a feedback report with the specified title?

Original comment by jonathan...@google.com on 24 Sep 2015 at 4:45

[GoogleCodeExporter]

Andrei, if you're seeing a similar issue, can you reproduce it and submit a 
feedback report with the title mentioned above? Please also post here the make 
and model for any TVs you used to reproduce the error.

Original comment by jonathan...@google.com on 24 Sep 2015 at 5:00

[GoogleCodeExporter]

Closing this ticket due to a lack of response and because it seems to be 
intended behavior. Sometimes, the TV does not give enough information, so in 
those cases we treat it as "we do not know" -> "the TV is on" just to be on the 
safe side (we do not want to stop playback if there is a chance that the TV is 
actually on). What would be really bad is if we ever report that the TV is off 
when it isn't, since the app could stop playback when the user is actually 
watching TV; if we are not sure, we report "unknown" (as seen in this case when 
the TV gets turned back on) and this should be treated as the TV being "on" 
when it happens because the info provided from the TV is not conclusive.

Original comment by jonathan...@google.com on 9 Oct 2015 at 4:13

• Changed state: Invalid