Posts by Da Flex

Thanks. Then it could be a playback issue, and the suggestion of smp might help.

parityboy :

Try this.

Thanks.

1. Use the default skin.
2. When high CPU usage happens again, login and use top command to find the most consuming process. (leave top by Strg + C)

Quote from y3ll3r

it starts at 21:00 and till 21:15

What happened at that time and why isn't that period a part of the log?

That looks fine. On an RPi those steps are all you need to get analogue audio, so I guess it's a driver issue.

I suggest to write a bug report. Write all necessary infos, as described on top of that sub-forum. Additionally provide a link to this thread.

Quote from sparky76

What is the KeyID of the "back" button?

Try "275".

At the bottom of guisettings.xml you'll find a setting for volume. Check the value and set it to 1 (max).

spikerguy :

The question of the thread starter has been answered here. You'll find more up-to-date nightly builds now.

Do you have analogue output (like "HDMI + Analogue") activated at the audio settings?

You have to use the pre-defined keywords for images, provided by LE (like "info"). Custom images do not work.

I went into trouble after trying latest Milhouse builds. Some add-ons are disabled on that branch, and when downgrading back to the stable branch, not all add-ons will be reactivated (Python / Kodi Six dependency chaos). My advice is to stay with the stable branch, and wait until Python 3 officially arrives.

I hope you still remember this advice when playing 4K.

Click here to learn how to provide a link to a log file.

This should be visible at kodi.log. You already know how to provide a log file. Illegal add-ons will stop our support immediately.

The CEC adapter settings at Settings -> System -> Input -> Peripherals have options how to deal with changing sources. Play with it.

Try a different microSD card or check your current card for errors.

Big buttons, big trouble.

I learned something, too (gpiopin vs. gpio_pin).

You can mark this thread as solved by editing your initial post.

Line 32 of power_button.py does the shutdown. If you replace it by a power off command, then you hopefully get the right LED result:

os.system("poweroff")

Here we go.

1) Install the add-on Raspberry Pi Tools (probably already installed in your case)

2) Remove this line from config.txt

dtoverlay=gpio-shutdown,gpio_pin=17,active_low=1,gpio_pull=up

3) Copy this /storage/.config/autostart.sh

#!/bin/sh

python /storage/scripts/power_button.py

4) Create a folder for a Python script: mkdir /storage/scripts

5) Copy this /storage/scripts/power_button.py

#!/usr/bin/python

# This script was authored by AndrewH7 and belongs to him.
# (www.instructables.com/member/AndrewH7)
# You have permission to modify and use this script only for your own personal usage.
# You do not have permission to redistribute this script as your own work.
# Use this script at your own risk.

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO
import os

# Replace YOUR_CHOSEN_GPIO_NUMBER_HERE with the GPIO pin number you wish to use.
# Make sure you know which rapsberry pi revision you are using first.
# The line should look something like this e.g. "gpio_number = 7".
button_gpio_number = 17

# Use BCM pin numbering (i.e. the GPIO number, not pin number).
# WARNING: this will change between Pi versions.
# Check yours first and adjust accordingly.
GPIO.setmode(GPIO.BCM)

# It's very important the pin is an input to avoid short-circuits.
# The pull-up resistor means the pin is high by default.
GPIO.setup(button_gpio_number, GPIO.IN, pull_up_down = GPIO.PUD_UP)

# Use falling edge detection to see if pin is pulled low to avoid repeated polling.
# Send command to system to shutdown.
try:
    GPIO.wait_for_edge(button_gpio_number, GPIO.FALLING)
    os.system("shutdown -h now")
except:
    pass

# Revert all GPIO pins to their normal states (i.e. input = safe).
GPIO.cleanup()

6) Make both files executable:

chmod +x /storage/.config/autostart.sh

chmod +x /storage/scripts/power_button.py

The script will wait for a "low" signal at GPIO 17, like the original config.txt line did. On "low" it will shutdown, but additionally it sets all GPIO pins back to default state after shutdown. That's probably the important part for your LED's to switch to red.