Posts by Da Flex

Try this settings: Click!

As I said above, it's possible that some cards use SDXC internally, and they will work fine inside other card readers.

Because the major goal of LE is playing A/V content. Ask the gaming OS experts first, and if they say it's possible, come back here.

Wrong place to ask. Use a gaming OS forum (Lakka etc.).

Crazy. Does the amixer command show something on SSH?

Looks like you did everything right. Hmm, this error is unusual. I assume you don't use overclocking. It could be a hardware defect. The "Raspberry Pi OS" has logging capabilities for sure. Run that OS and read the log from time to time. Maybe you find a defect.

Understand. Please give the LE download link that you've been used.

Thanks for testing. The official standard for Rpi is SDHC. If you use an SDXC card, it could produce reading errors. This means, your card is fine, but the RPi is unable to read it correctly.

PS: Normally 16GB is SDHC, but it looks like they use SDXC internally for some of those cards, too: Example on Amazon. Maybe you should buy another microSD from a different company.

You could try Etcher to write the microSD. Etcher will check for errors after writing, and it's approved to work with LE.

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.