-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB CEC Adapter not fully working with Samsung UE55F6500 #8
Comments
Did you set up the correct "connected to HDMI device" and "HDMI port number" in XBMC? |
In The "Connected to HDMI Device" I have 2 options: TV and my AV Receiver. The HDMI port is 1, so the settings seem correct for me. Here's a screenshot of the settings: Here's another log file from the current setup: https://gist.github.com/robertscherer/9238331 The "PushCecKeypress - received key f7 duration 0" message appeared when I hit the "XBMC Menu" item in the Samsung's Tools menu. It doesn't print any log messages when I hit the cursor buttons on my TV remote. Controlling other CEC devices, like my Philips BluRay Player works fine. |
This looks like a bug in the TV's CEC firmware if your CEC adapter is connected to HDMI 1 of the TV. |
Please test again with libCEC 2.2.0, which will be released today. |
Hi,
I have a PC with Ubuntu 12.10, using the Pulse8 USB CEC Adapter and a Samsung UE55F6500 TV.
I have installed the Pulse8 XBMC build using the install script from the home page. The CEC communication seems to work, including powering off the TV when closing XBMC.
I also see the XBMC device in the Anynet+ Menu on the TV. However, I cannot control XBMC at all with the TV remote.
I have set the XBMC log level to 1, and there are no log entries when I press any of the buttons on the remote. There is some communication when I choose the Anynet+ "XBMC MENU" item in the TV menu.
Please find my XBMC log file here: https://gist.github.com/robertscherer/9158221
Let me know if you need further information or debugging.
Thanks,
Robert
The text was updated successfully, but these errors were encountered: