Posts by Da Flex

Quote from mwake

...and then can you put a clean installation of Librelec into the ext4 partition after windows is installed ?

That's how I did it when I had Win10, and it worked. You could use Grub2Win to select an OS.

Just for the records: On x86 machines you could use this add-on: Click! 

PS: It's an add-on question. I've been moved the thread into the right sub-forum.

No Bluetooth on RPi 2B.

Yes, a frozen system will probably stop script execution, and soft-reset will not work anymore. If you can accept the risk of a hard-reset, you can add another button for that purpose. Hard-reset pins are not part of GPIO, you have to use the P6 header instead: Click!

Could be a CoreELEC vs. LibreELEC thing. Can you post the PageUp / PageDown part of that table?

How do you define PageUp / PageDown on your remote control?

They are a bit tight, I mean, they make money with those boards. Interesting that it works different compared to your DSP board.

So I think the driver just provides an input device at the /dev folder. The mixing part is on Kodi then (I was wrong). Install the "Kodi Audio Mixer" add-on. Hopefully that add-on will grab your input device from /dev folder, and mixes everything together.

I can't find Bluetooth errors, too. I guess WiFi (RPi internal) and Bluetooth (RPi internal) share a driver dependency. If you have WiFi disabled, enable it, and try Bluetooth again.

Do you use the internal RPi Bluetooth, or an external adapter?

Please post a link to a kodi.log.

Thanks! This is classic showcase stuff, so I move the thread to that sub-forum.

Quote from Skripo

Thank you very much for your help, I will create a guide from all the help I received on this forum.

Good idea! You can upload that guide to our Wiki, or post it here, and someone else (me) can upload it.

Hedda Because you don't stop to advertise your device, I have to close this thread.

Mario77 Yes, that's right. I use a resistor with the LED, but I forgot the value. You'll find on the web, how to connect an LED to GPIO.

Mario77 No, the dtoverlay implementation only does the shutdown, no reset by long-press. I did a test to be sure.

Here is the original implementation that I used before dtoverlay. You can implement reset by long-press easily from there:

#!/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 = 3
led_gpio_number = 13

# 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)
GPIO.setup(led_gpio_number, GPIO.OUT)

# Switch LED on.
# LED will switch off automatically at shutdown by using normal GPIO state.
GPIO.output(led_gpio_number, True)

# 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()

I agree.

Hmm, then maybe it's broken.

PS: At boot time hardware will get checked. There is a chance that Raspbian ignores a hardware defect, but LE don't. On Raspbian you should find a log, and if there is a defect, the log will name that hardware part.

Stroke_Papy Can you write some more details, please? Does LE audio work with a different firmware? I don't understand what you wrote.

The RPi firmware is written to the chip, so it stays active when you switch to another OS / microSD. config.txt / guisettings.xml are not relevant for this part.

If the firmware is the issue, you have to find a version that works with all your OS'es. Maybe switch from Retropi to Lakka, if Retropi needs incompatible firmware.

Quote from Mario77

I know it's not the point of this thread but all you can access from a windows PC is /flash directory..

Thx, this is helpful. I don't use Windows anymore, so I don't know what they support now.