Github: hdmi_force_hotplug commented/disabled

fernandog · 2 April 2015 14:36

@DBMandrake hi, why hdmi_force_hotplug is commented/disabled here:

osmc/osmc/blob/master/package/mediacenter-addon-osmc/src/script.module.osmcsetting.pi/resources/settings.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<settings>
    <category label="32001">
        <setting id="display_rotate" label="32003" lvalues="32004|32005|32006|32007|32008" type="enum"/>
        <setting default="false" id="hdmi_safe" label="32009" type="bool"/>
        <setting enable="false" label="32010" visible="eq(-1,true)"/>
        <setting default="false" id="hdmi_ignore_edid" label="32011" type="bool"/>
        <!-- <setting default="false" id="store_hdmi_to_file" label="32012" type="bool"/> -->
        <setting default="false" id="hdmi_edid_file" label="32099" type="bool"/>
        <setting default="false" id="hdmi_force_hotplug" label="32100" type="bool"/>
        <!-- hdmi_edid needs force hotplug but force hotplug doesn't need hdmi_edid, hope this makes sense -->
        <setting enable="false" label="32013" visible="eq(-1,true)"/>
        <!-- hdmi_force_hotplug should be disabled before using a different tv or hdmi port -->
        <setting default="false" id="hdmi_ignore_cec" label="32014" type="bool"/>
        <setting default="0" id="config_hdmi_boost" label="32015" option="int" range="0,1,11" type="slider"/>
        <setting type="lsep" label="32098" visible="!eq(-1,0)"/>
        <setting default="0" id="hdmi_group" label="32016" lvalues="32017|32018|32019" type="enum"/>
        <setting default="0" id="hdmi_mode" label="32020" option="int" range="0,1,86" type="slider"/>
        <setting default="0" id="hdmi_pixel_encoding" label="32087" lvalues="32088|32089|32090|32091|32092" type="enum"/>
        <setting default="0" id="sdtv_mode" label="32021" lvalues="32022|32023|32024|32025" type="enum"/>

This file has been truncated. show original

but not here:

https://github.com/samnazarko/osmc/blob/master/package/mediacenter-addon-osmc/src/script.module.osmcsetting.pioverclock/resources/settings.xml

I was about to make a PR in github but prefer to ask you if there any reason
thanks!

EMJB · 6 April 2015 12:15

I was about to raise a post to the effect that “hdmi_force_hotplug=1” does not appear in the config.txt file for my Pi2 using OSMC, yet the HDMI output is being generated even when the display is not switched on until well after the Pi has booted. It was my understanding that without this command and in the absence of an HDMI display connected at boot time, the Pi will revert to an analogue display output.

If “hdmi_force_hotplug=1” is being implemented in some other way than the config.txt file, how can the user ensure the analogue display output is generated? Should this not be one of the “My OSMC”/Pi/Display options?

EMJB

fernandog · 6 April 2015 12:39

@ActionA can you check this please? thanks!

popcornmix · 6 April 2015 13:10

No. HDMI will be chosen if the HDMI hotplug signal is asserted on boot. It’s up to the TV when that signal is asserted, and most TVs will assert it always. However this behaviour is up to the TV, and some only assert hotplug when powered and not on standby, and on correct HDMI input.

EMJB · 6 April 2015 18:04

@ popcornmix - thanks for the correction - clearly my experiment was not valid in terms of whether or not “hdmi_force_hotplug=1” is currently being implemented in some other way than the config.txt file.

However I think my basic conclusion stands - some users will want it, some will not, but it would now appear some won’t care, so should this not be one of the “My OSMC”/Pi/Display options?

EMJB