Add these two lines to /boot/config.txt and reboot Raspbmc:
hdmi_force_hotplug=1 sets the Raspbmc to use HDMI mode even if no HDMI monitor is detected.
hdmi_drive=2 sets the Raspbmc to normal HDMI mode (Sound will be sent if supported and enabled). Without this line, the Raspbmc would switch to DVI (with no audio) mode by ...
The reason a DVI-to-VGA adapter works on your PC & laptop is that DVI includes analog (RGB) pins. The adapter is passive; It just connects the red analog output of the PC to the red analog input of the monitor, ditto for green and blue. They are included on most PCs and laptops for backward compatibility.
HDMI-to-DVI cables are also passive, but ...
No, the Pi Zero does not support ethernet over HDMI.
Unfortunately the schematics for the Pi Zero are not available (edited: an overview schematics is available now, see updated information below). However since it is essentially an minimized Pi 1 I'd bet that the HDMI circuitry is (nearly) the same - though the Pi 1 features a standard sized HDMI connector ...
Those are explained here: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
There is also this: https://www.raspberrypi.org/documentation/configuration/hdmi-config.md -- But if the group 1, mode 16 as above works, you don't have to worry about all that.
Open /boot/config.txt and apply this settings:
hdmi_force_hotplug=1 to force hot plugin of your screen,
increase config_hdmi_boost to boost the signal. Lower values are meant to be for short HDMI cables, larger for longer ones. But this can also apply for (older) HDMI displays, whose HDMI receivers are not sensitive enough, irrespective of cable length.
tvservice is not the best to turn off and on the screen.
Much better way to do this (found after a day of searching) is using vcgencmd command (more on this here).
vcgencmd display_power 0 turns off the screen
vcgencmd display_power 1 turns on the screen
This allows the Qt application to be visible on the screen after turning it off and back on.
I think you have to decide what matters most to you in the monitor.
Do you want:
The highest resolution possible?
A mountable screen?
An articulated monitor arm?
An inexpensive solution?
The answers to these questions will help you ...
The best information I can find suggests that it's possible to output 4K resolutions, but at fairly miserable frame rates. The Pi 3 has the same GPU as the Pi 2, so the information should still be valid:
I have managed to get 3840 x 2160 (4k x 2k) at 15Hz on a Seiki E50UY04
I would guess that when you say you turn the TV off you are using the remote control to do so, not the switch at the wall.
Most TV's don't actually turn off with the off button, they just go into standby mode. This allows them to monitor your remote control so that they can sense when you command the TV to turn back on again via the remote.
In the same way, ...
CEA modes are intended for TV, they include plenty of interlaced and progressive modes, usually with 25/50/100Hz (PAL) or 30/60/120Hz (NTSC) frame rates and TV resolutions of 288/480/576/720/1080 scan lines. DMT modes are intended for computer monitors, therefore there are none of the interlaced modes, the resolutions are 640/720/800/1024/1280 and the frame ...
A television or monitor will require either an HDMI input for video and audio or a composite video cable for video and a 3.5mm stereo cable for audio. If sound is not required then the minimum will be a composite video connection.
cec-client can tell you the commands it knows
echo h | cec-client -s -d 1
There are a bunch of things that cec can do, that aren't on the list though too. You can press buttons on your remote and see the raw data being passed.
By playing back those same bytes, you can simulate the same functions.
There is a few things you can try:
1) Edit /etc/rc.local and add the following lines above exit 0:
# Disable HDMI
this will turn off the display, but only somewhere during the boot sequence
2) add hdmi_blanking setting to your /boot/config.txt
I found the follwing settings here:
hdmi_blanking=0: HDMI Output will be blank when DPMS ...
AFAIK only one audio output can be selected. You can, however, select one of them manually using amixer command:
sudo amixer cset numid=3 <n>
Where is 0=auto, 1=analog, 2=hdmi. By default it's set to auto which means HDMI if present, analog otherwise. Unlike changing video output, this change does not need rebooting.
You want a HDMI Type A to HDMI Type A; they are the most common cable used to connect DVD players to TVs.
Any type of cable should do. If you want to watch high-quality video and listen to high-quality audio, it's worth spending a little more on the cable. For example, gold connectors will the contact between the cable and the connectors on the RPi or the ...
That cable is most likely a DisplayPort-to-HDMI cable not a HDMI-to-DisplayPort cable (mind the direction). While there are DP ports able to support HMDI signals (DisplayPort Dual-mode) HDMI does not support DP directly. Since HDMI data transmission is very different from DP there will be no simple (passive) cable that just re-routes some signal lines on the ...
I had a similar problem with my Pi, when I connected it first time to my tv (a Samsung D5000): the tv did not understand an HDMI device was connected. I have raspbmc as the os.
There are a couple of instructions you can add to /boot/config.txt to tell your Pi to activate the hdmi output when you connect a cable, and to force hdmi output mode instead of dvi.
I know this isn't exactly what you're looking for, but you might find this interesting.
You can purchase a lapdock, made for a cell phone, that will provide you a portable keyboard and monitor for use with your RPI. Simply connect an HDMI to HDMI micro female adapter to the lapdock.
They are often on sale for ~$60. Likely far cheaper than any other monitor ...
The issue was caused by the length of my HDMI cable which was 3M 1.4a HDMI spec.
It is because the default power output on the HDMI connector is sometimes not enough for longer cables causing the zits, in order to fix this you should edit your config.txt file in the root of your SD card (will be visible under windows explorer, if the text file does not ...
There's a command line utility, tvservice built into Raspbian that will tell you the state of the HDMI.
To detect the full state, you can use the command: tvservice -s. On my RPi this currently outputs:
state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
The states (that I've gathered) are as follows:
0x40001 Not initialized and HDMI cable is ...
While the official Raspberry schematics don't tell a thing about these components we can learn from the picture of the PCB that they are connected to the paired pins 1 and 3, 4 and 6, 7 and 9, 10 and 12 - that's all the differential signal and clock lines.
Since the devices have just four pads (not six) they are not dual-rail clamp ESD protectors, e.g. see ...
sudo sh -c "TERM=linux setterm -foreground black >/dev/tty0"
sudo sh -c "TERM=linux setterm -clear all >/dev/tty0"
This will change the font color to black, than clears the screen.
Or in a single line:
sudo sh -c "TERM=linux setterm -foreground black -clear all >/dev/tty0"
And set it back to normal:
sudo sh -c "TERM=linux setterm -foreground ...