Since I installed the RC version last Sunday, I’ve seen that after powering off the HDMI connected ONKYO amplifier, it automatically powers up again after a few seconds. When I power it off again then, it remains off.
I’ve never seen this behavior before and the exclude the remote control (Harmony One) and/or the amplifier, I decided to go back to OpenElec (version 5.0.6) and now I do not see this strange behavior anymore. Has anybody seen this before and could it be that it is one of the CEC/HDMI setting?
I went through the HDMI section on the Onkyo A/V receiver and played with some settings but it did not resolve the issue (the final results was that the sound of the LG TV was not coming to the A/V anymore…so I had to restore everything as it was before).
Note that I did not change anything on my Onkyo for the last 6 months. The only thing that changed was going from OpenElec to OSMC RC and then the issue started.
Any other suggestions?
There is a trick and that is to “program” the Harmony One to send a double power off with about 5 seconds in between but I do not like this “solution”.
CaNsA: I used your config.txt in /boot and rebooted the device and the problem is still there so I’m back to my original config.txt.
frank_harmann Many thanks for jumping in and welcome to the club…grin…I had Autostanby set to ON and when I set it to OFF, it doesn’t make any difference…a few seconds after I powered it Off, the Onkyo switches itself on again… Note that with my Onkyo there is no “hybrid standby” option.
As reported earlier, the automatic Power On of the Onkyo does not occur with OpenElec, so I decided to compare both config.txt files and in the OpenElec config.txt I found some parameters not present in OSMC. The good news is that after I added the first (and most likely) one to the OSMC config.txt file (hdmi_force_hotplug=1)’ and performed a reboot, the Onkyo does not power up itself anymore after a regular power off.
For your information, the following HDMI parameters can be found in the OpenElec config.txt but not in OSMC:
As the issue was solved by the first parameter, I did not add the other ones to the OSMC config.txt file. I leave it to the OSMC experts what to do with them.