Setting default resolution to 1920 in advancedsettings.xml not helping/working.
Try this commands from SSH terminal to enforce a resolution. If it works, you could put it into autostart.sh. Don't buy new stuff yet, there are a couple of other tweaks.
Now obviously I've changed it to /dev/sdb as that's the drive I want to spin down.
/dev/sdb is the whole drive, but the example is only about a partition /dev/sda1.
I'm trying to spin down my western digital hard drive as it always spins and with it being in my tv cupboard it's quite noisy when not in use.
Does your former solution not work anymore?
Read here about special config.txt options for unusual output devices.
This is a very unusual device for LE, because LE is made for playing media, not recording. I would guess the driver is missing. Most people with unusual hardware try to make it work on Raspbian first, because, unlike LE, Raspbian is made for all types of input devices.
Take into account that cameras are time-critical (latency issues). It's very likely that RPi's camera-over-USB is too slow. RPi's have an own port for cameras, so using USB is generally a bad idea.
Create /storage/.kodi/userdata/keymaps/remote.xml with content like:
<keymap>
<global>
<remote>
<red>VolumeDown</red>
<green>VolumeUp</green>
<yellow>RunScript(script.audio.profiles,1)</yellow>
<blue>RunScript(script.audio.profiles,2)</blue>
</remote>
</global>
</keymap>Hi Rob,
the audio output setting is stored at guisettings.xml. I'm not sure whether it has an instant effect when you overwrite guisettings.xml while Kodi is running. So the first thing I would try is to edit guisettings.xml at runtime, and see what happens. If it works, you can script that procedure and call it from a color button.
I haven’t tried a different cable yet, as I only have the one hdmi mini cable. For what it’s worth it’s the official RPi one.
I bet it's the HDMI cable, because your 1024x768 is a typical PC screen resolution. Buy a High-Speed Micro-HDMI to HDMI cable, or an adapter to use a standard HDMI High Speed cable. HDMI High Speed is an official standard, made for high resolutions.
1. Can I add "dtoverlay=gpio-shutdown" in config.txt from SD card while it's plugged to desktop using Notepad++
Yes.
2. The pin 33 and pin 34 will work for ON/OFF plus led status?
No, that's just for the LED. Use pin 5 and 6 for the power button. If you only want the power button, then you can ignore the LED part.
3. For the executed command (chmod +x ), is there a way without the need command from terminal? Like, right click the file (.py & .sh) and change something in Properties?
On a Linux PC (maybe OSX, too), making files executable by right-click-option should work fine. You maybe need root status to do this. I'm not 100% sure whether chmod +x is necessary, so you can try it without this step first.
is "/storage" mean there's a folder inside SD card name "/storage"?
When you plug the microSD card into your desktop PC, then the /storage folder will be represented by the STORAGE partition.
I'm thinking of returning RPI power supply and get this one since it has a switch ON/OFF for $9.
Don't use this product to switch off. An instant power-off can result in write errors on your microSD card.
Always use software shutdown. Keep your PSU and mount a power button at your case (I just love to link to my own posts 
).
How can I have HDMI off after some period of inactivity?
Currently LE has no idle timer, just a screen saver.
-> Write your own script.
Still the same answer:
Check your SDA2 device.
On my RPi 3B+ the kodi.bin is at about 10 - 15% when idle. I think your 18% are still normal.
Currently LE has no idle timer, just a screen saver. Try the CEC Adapter settings at Settings -> System -> Input -> Peripherals.
System.log says:
[ 1.808835] usb 2-5: new high-speed USB device number 3 using ehci-pci
[ 1.830343] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.955525] usb 2-5: device descriptor read/64, error -71Those read errors appear several times. Check your SDA2 device.
Reach a certain amount of posts?
Yes, it's necessary spam protection. I think your primary partner to solve the issue is AMD now. They get payed for providing solutions.
PS: Try plugging the HDMI cable off and on after a bad boot.
This part is interesting:
This works only if UEFI boot type is set to Win7 on Zotac. UEFI and Legacy options do not display anything (TV shows no signal).
So it could be a timing issue, and the box misses the transmission of HDMI modes coming from the TV. Maybe switching HDMI off / on (after booting and running LE invisible) will enforce a complete transmission of HDMI modes. You could script HDMI off / on by using LE's autostart.sh.
