HDMI-CEC not enabled on TV after start (cubox-i, samsung TV)

[martinbalint]

Hi, when OpenELEC 5.0 beta 3 starts, it doesn't respond to TV remote calls. I have to manualy select Kodi device from TV Anynet+ menu. After that, it works great, until next restart.

With same cable,Openelec 4 and Rpi, OpenELEC responds immediately after Kodi start.

Log: http://pastebin.com/aZ2Jg6P5

Doesn't work in: 4.95.4, 4.95.5

[tunf]

also in beta 4 and 5 the same issue.

[wer1976]

Same issue with Philips TV, connected via HDMI over Pioneer receiver.

CEC connection only seems to be lost when I switch the television off and on again. Once it is working, everything remains in working condition if I switch the tv's input selection back and forth. Switching off the television requires me to disable and enable the CEC device (or just set it back to default settings).

If I use a separate CEC-USB connector (between HDMI cable and data in USB), then CEC does always return. This is a dirty workaround, and not a solution to the bug. Also it requires a higher value of config_hdmi_boost to get good signal....

[BrianGilbert]

also ocurring on Cubox under 4.97.1, although manual restart isn't fixing it either.

[jackmort37]

Same issue here on a Panasonic TV with RPi.
Something broke in beta3 release. Same issue occurs in recent MilhouseVH builds.

[tunf]

Still the same in final openelec 5

[BrianGilbert]

For me it does start working eventually.. but after a sizeable delay.. and it is prone to losing the CEC (Anynet) connection and switching back to the HDMI connection alone..

[lucaswalther]

I've been running OpenELEC on a Raspberry Pi with Samsung TV for a couple of years (started w/ version 3.x), and HDMI CEC has always worked perfectly. I didn't even notice any issues after upgrading to 5.0 a little over a week ago (I don't experiment with any of the betas, only stable releases).

However, I just purchased a CuBox i4Pro and set it up with OpenELEC 5.0 last night, and I'm not experiencing the same types of issues described by others here... the HDMI CEC (Samsung calls it "Anynet+") doesn't work initially when the device is first powered on, and also seems to be "lost" after some time (anywhere from a few minutes to several hours). Power cycling the the television, -OR- reconnecting through the television menu usually gets it working again, but there is still a delay of several seconds before the functionality returns.

[zilexa]

For me, OpenElec 5.0 with Cubox-i 4pro with Sony W706 tv CEC works perfect.

[jenkins101]

works here too

[c-o-m-m-a-n-d-e-r]

same problem here with 5.0.8 stable ...and a philips media suite .... it starts but after a few seconds i have to select hdmi port again, then it works

[Colargol59]

Same problem... this issue should be reopened! OpenElec 5.95.1, Samsung LE32C550

[fritsch]

Won't help, cause no one is working on it. But here, you are - reopened.

[tunf]

@fritsch, thanks or reopening. I think this is the general cec issue with all versions and devices. I have it reported several times. it is pitty that i'm not a programmer, otherwise i would have offered my help.
Is this still due to the libcec issue?

[fritsch]

No idea, i don't have a CEC capable device here. CEC3 will soon be integrated - then let's revisit.

[nebuchar]

I have the same problem, it works initially but stops working after some seconds

Didn't had this problem before, even with 5.0.8

[tunf]

on 6.0.1 still no stable / working cec possible.
After the update and reboots the samsung tv sees cec, connects disconnects, manual selecting cec device there one named kodi. If selected for 1 to 2 seconds able to use remote. Then a disconnect. Looking for cec devices manually again it now shows recorder, select this one, cec working for 1 to 2 seconds then disconnects, manually no device visable that is related to openelec/ kodi. Able to use remote. Starting a plugin/ video or so, cec disconnects (or after about 6 seconds)

[apramhaas]

I'm also having HDMI CEC problems with my Panasonic TX-49CXW754 and a Cubox-i on all Openelec 6.0.x versions (including the latest 6.0.3). It was a bit more stable with the 6 beta versions (5.95.x) but currently it's unuseable and I switched it off completely.

Problems are:

• TV switches on when Kodi starts although I configured to not wake any devices
• TV swichtes to other HDMI channel (away from Kodi) whenever I start a movie.
• Remote control is not working

If I can help on this issue with logs, tests whatever - let me know.
Here is the full kodi.log short time after the start of Kodi:
https://gist.github.com/unclejamal3000/c86cebba9a6109047b92

11:51:43 T:1966809648   DEBUG: LoadMappings - loaded node "CEC Adapter"
11:51:43 T:1966809648   DEBUG: LoadMappings - loaded node "Pulse-Eight CEC Adapter"
11:51:43 T:1966809648   DEBUG: SECTION:LoadDLL(libcec.so.3.0)
11:51:43 T:1966809648   DEBUG: Loading: libcec.so.3.0
11:51:43 T:1966809648   DEBUG: GetMappingForDevice - device (0471:1001) mapped to CEC Adapter (type = cec)
11:51:43 T:1966809648   DEBUG: InitialiseFeature - using libCEC v3.0.1
11:51:43 T:1966809648  NOTICE: Register - new cec device registered on cec->i.MX: CEC Adapter (0471:1001)
11:51:43 T:1757504576  NOTICE: Thread CECAdapter start, auto delete: false
11:51:43 T:1757504576   DEBUG: OpenConnection - opening a connection to the CEC adapter: i.MX
11:51:43 T:1747973184  NOTICE: Thread PeripBusCEC start, auto delete: false
11:51:43 T:1765893184   ERROR: CecLogMessage - Write: sent command error !
11:51:44 T:1757504576   DEBUG: OpenConnection - connection to the CEC adapter opened
11:51:44 T:1627837504  NOTICE: Thread CECAdapterUpdate start, auto delete: false
11:51:45 T:1765893184   ERROR: CecLogMessage - Write: sent command error !
11:51:45 T:1765893184   ERROR: CecLogMessage - Write: sent command error !
11:51:45 T:1765893184   ERROR: CecLogMessage - Write: sent command error !
11:51:45 T:1765893184   ERROR: CecLogMessage - Write: sent command error !
11:51:45 T:1765893184   ERROR: CecLogMessage - Write: sent command error !

[sraue]

please report to https://github.com/Pulse-Eight/libcec (CEC support for imx6 has to be implemented there)