I had a look to the Linux kernel CEC driver and found maybe a issue.
So here is a test build. It can be used for all Amlogic-ng devices, not only N2!
Maybe it resolve some CEC & Kodi issues!
Changes:
"hardcode" default bootloader CEC setting to 0x3f
Do not touch received messages if address is not enabled.
Changes:
"hardcode" default bootloader CEC setting to 0x3f
Do not touch received messages if address is not enabled.
Enable rx buffer on all CPUs
Please have a try first with nr 1, then nr 2 if still problem are existing!
This changes will have no affect to any wake-up issues!
EDIT:
About the Couldn't initialize the CEC adapter issue:
On kernel boot the CEC hardware driver aocec get loaded.
On Kodi start libCEC get loaded what is trying to open the driver aocec.
If it got opened it will send F0 by the CEC bus to ping if a TV is connected.
If now no reply is received the known Pule-Eight error pop up will be shown.
So the main reason of this can be, that the initialization is just too fast. Especially if a AVR is connected between the box & TV. When the AVR isn’t ready to forward the message between box & TV the system will not work.
So I guess this high amount of CEC issues seen by the users are related to this change:
Since G12(A/B) CECB is used. The big difference to the “old” CEC system in the SoC is the interrupt handling. So the handling between software & hardware got faster now and maybe Kodi and/or libCEC need to be adapt for this.
EDIT2:
I was digging really deap now in the Kodi & libCEC source about this issue and it is almost impossible to find a solution for me as the source is quit complicated.
The best way to solve your Couldn't initialize the CEC adapter issue:
Enable debug in Kodi and enable debug logging for the libCEC component.
Ask at http://libcec.pulse-eight.com/ for support.
Another “workaround” would be to delay the libCEC init on Kodi startup about ~5-10s until the hardware is ready for communication.