oralodabas / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

Chromecast does not go into standby mode/switch off HDMI to release control of HDMI #396

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. On TV with single HDMI input, using an HDMI auto switcher with SKY TV and 
Chromecast as inputs.
2. After using Chromecast (eg watching YouTube) Chromecast does not switch off 
HDMI and so TV remains on Chromecast.

What is the expected output? What do you see instead?
I would expect Chromecast to turn off HDMI output which would allow my 
TV/Switch to revert to the previous HMDI source. This could be a configurable 
option.
Problem is made worse in that SKY+HD boxes do not support the HDMI switch so 
turning SKY to standby and back will not force the HDMI source to change from 
Chromecast to SKYTV.

To work around this I have to use my HDMI switcher remote to switch source back 
to SKY TV. 

What version of the product are you using? On what operating system?
Firmware: 19084
Country Code: GB

Original issue reported on code.google.com by cpwern...@googlemail.com on 3 Oct 2014 at 10:25

GoogleCodeExporter commented 9 years ago

Original comment by and...@google.com on 3 Oct 2014 at 8:18

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
This is the intended behavior. Chromecast will remain idle when not playing to 
allow users to cast to it at anytime.

Original comment by and...@google.com on 3 Oct 2014 at 11:21

GoogleCodeExporter commented 9 years ago
For me the Chromecast should get out of the way once the video/photos etc has 
finished.
SCENARIO: Family watching Sat TV. I cast a YouTube Video, we all watch, then 
when it has finished:
1. Ideal behaviour: it should return to Sat TV. Seamless.
2. Sub-optimal behaviour: it returns to Chromecast screen (why?) and I have to 
find the remote control to force HDMI back to Sat TV.
Is this intended?

Original comment by cpwern...@googlemail.com on 4 Oct 2014 at 12:05

GoogleCodeExporter commented 9 years ago
Currently that is the expected behavior. 

Original comment by anad...@google.com on 4 Oct 2014 at 3:18