arabenseifer / google-cast-sdk

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

Chromecast takes control of my TV sources button until disconnected or reboot #453

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I see anything on Chromecast.
2. I want to return to my 'TV' source to see normal television channels.
3. I pulse my remote button to change the source.
4. Nothing happens. I have to power off or reboot from chromecast android app.

What is the expected output? What do you see instead?

I should see my Toshiba LED 32'' menu to change the source, but I'm still on 
chromecast

What version of the product are you using? On what operating system?

Last firmare on Spain and android 4.4.2 on BQ Aquaris 5 FullHD

Please provide any additional information below.

My TV model is Toshiba 32L3433DG

http://www.toshiba.es/television/consumer-tvs/led/l3/32l3433dg/

Original issue reported on code.google.com by imigueld...@gmail.com on 15 Dec 2014 at 11:01

GoogleCodeExporter commented 9 years ago
Have you experienced this issue when you use the Chromecast with a different TV 
or monitor?

Original comment by jonathan...@google.com on 15 Dec 2014 at 11:02

GoogleCodeExporter commented 9 years ago
I have the same issue with a Toshiba TV: 40L544
You really should do some integration test with major tv brands :-(
Workaround: turn of HDMI CEC

Original comment by pebaue...@gmail.com on 21 Dec 2014 at 5:15

GoogleCodeExporter commented 9 years ago
As in issue 460 
(https://code.google.com/p/google-cast-sdk/issues/detail?id=460), this is an 
problem with the TV, not Chromecast.  Please contact Toshiba support.

Original comment by jonathan...@google.com on 22 Dec 2014 at 9:38

GoogleCodeExporter commented 9 years ago
We would like to further investigate this issue so it would be great if you 
could provide some help with collecting information on this. We would need two 
sets of logs from your device. To send us logs from your chromecast device, you 
need to follow the steps outlined in this help page: 
https://support.google.com/chromecast/answer/3187017?hl=en  
When you are sending a feedback, you can enter a keyword in the UI that helps 
us find the log.

We would need two feedbacks:
(1) Just reboot your chromecast. After it is up, send one feedback, and enter 
the keyword "toshiba-1"

(2) A second feedback: use chromecast for whatever you would like. Then try to 
change the input using the remote which should fail (based on the issue that 
you have reported). After doing that, send us the second feedback with keyword 
"toshiba-2".

When you have done these, please enter a comment here so we can go and grab the 
logs that you sent us; we may be able to see why your TV is not happy at that 
point but unless we have the logs, we don't know if we can figure that out or 
not.

Thanks.

Original comment by anad...@google.com on 30 Dec 2014 at 5:44

GoogleCodeExporter commented 9 years ago
Sorry, I've been busy these days and without email... I'll reenable CEC on my 
tv and follow your instructions for the feedbacks :)

Original comment by imigueld...@gmail.com on 31 Dec 2014 at 7:39

GoogleCodeExporter commented 9 years ago
Hi,

Both feedbacks have beens sent following your directions, I sent a third 
toshiba-3 report because my tv can be configured with CEC and with CEC + auto 
switch on, and the tests 2 and 3 are on both configurations after press source 
button.

Hope It helps...

And happy new year! :)

Original comment by imigueld...@gmail.com on 1 Jan 2015 at 6:52

GoogleCodeExporter commented 9 years ago
Thanks and happy new year to you, too.

Original comment by anad...@google.com on 2 Jan 2015 at 4:51

GoogleCodeExporter commented 9 years ago
We looked through the logs and what we see is the following: remote control 
commands are received by the TV and TV then sends those to the HDMI that 
chromecast is connected to. Obviously chromecast cannot do any with those 
commands (they should be handled by TV) and this is the first time we are 
seeing this. Do you see this behavior with other playback devices (e.g., 
HDMI-CEC capable blu-ray players)?

Original comment by anad...@google.com on 15 Jan 2015 at 3:16