Command to completely disable CEC in "config.ini"

Did you try all libCEC versions?

What does it have to do with WOL?

The /flash/config.ini file deals with WOL and is the only line present. Mine was set at WOL=0 and was mentioned to me to ensure that this WOL was switched off. Yes I wondered why that was too.

Thanks Portisch. Will have to look at the licCEC 4.0.7. But where do I download it from ?? Or will it already be available in the .config folder though I doubt that ?? I will take a peak.

You can add other options there even if there is only one line currently present.

Is there a list of available options for boot.ini and config.ini?

thx, but why is the max_freq_a55 for C4, which @cdu13a added in nightly_20200725, not shown in the list? Is it complete? What’s about boot.ini?

It is best to look at your own boot.ini. there are variables past to the kernel. Those you can normally change.

You only can modify config.ini. the max_freq_a55 is for the SM1 SoC added.
You can set max_freq_a55=xxxx (SM1) in config.ini and it will be handled correct by boot.ini.
Internal max_freq_a55 is same as max_freq_a53 so you also can use max_freq_a53=xxxx (G12*)

So do I need to add the line cec_func_config=‘00’ to my config.ini file to disable all CEC functions or is it already by default set to all off = ‘00’ ??

Also remember that I have a Tanix TX9 Pro box, not an Odroid so assume this all still applies to my box. Also just awaiting deliver of an X96 Max + S905X3 4/64GB box which is ridiculously cheap for such a high spec box :slight_smile:

As the Tanix TX9 Pro is a S912 SoC I am not sure if it can be disabled completely. At least not in suspend mode as CE does not have control over the bootloader bl301 blob. All other devices using Amlogic-ng image including bl301 injected and/or Odroid N2/C4 also support disable of CEC for Wakeup and can be set in Kodi CoreELEC Settings.

so set in config.ini (if not available in CE settings):

cec_func_config='0'

should disable it, yes

Different libCEC versions can be chosen by open a SSH connection and type:

remove any libcec config (default 4.0.4 will be used):

rm -rf /storage/.config/libcec-4.*.conf

enable libcec-4.0.5:

touch /storage/.config/libcec-4.0.5.conf

enable libcec-4.0.7:

touch /storage/.config/libcec-4.0.7.conf

When CEC is working after booting into CE and CEC is stopping working later it’s more related to libCEC then the CEC driver itself.

The problem is that if you disable libcec the kernel continues processing cec:

So setting cec_func_config to ‘0’ should turn it off completely.
You could also remove it from dtb if it doesn’t.

Sorry to necro post, but setting:

cec_func_config='0'

does not disable CEC for me… It’s extremely annoying. I shut off my box, and then I turn off my TV, and the box senses the TV is turning off and turns itself back on.

OS is 19.5 RC2

I do think that modifying that does however remove the setting from the Kodi GUI configuration, because I can’t find it anymore.

Any help is appreciated.

All documented well (if someone read it):
https://wiki.coreelec.org/coreelec:ce_cec

It doesn’t work… With the CEC adapter showing as disabled, coupled with the setting in config.ini set to ‘0’, all the sliders in the CEC settings set to off, my box is still turning on when the TV is turned on.

Also, the sliders should not make a difference if the CEC is set to disabled.

Someone mentioned that this should be turned off in the dtb.img if all these settings have no effect… If I download an upgrade image for my box, how would I go about doing this?

Thanks

When config.ini value is set to 0 it should not be the reason of CEC it wakes up. maybe a IR code does match…

Nobody knows without any logs…

I considered this, two points though:

  1. If the Android box was picking up the TV controller’s IR code, then the box would respond to it… It doesn’t.
  2. I covered up the IR receiver to test this, the box turned on when I turned the TV on regardless.

What I forgot, if you don’t have bl301 injected or any other device support the feature you can adjust what you want. But again, without any log it’s impossible to help you…

Understood… So the problem is with my device’s bootloader… I will look into bl301 to see if it will work on my device. Thanks