Thanks, but I actually want to get the shutdown dialog when pressing the power button on my remote control. I just want to power-off when pressing the power-button on the computer.
That's why remote.xml exists as a separate option.
Thanks, but I actually want to get the shutdown dialog when pressing the power button on my remote control. I just want to power-off when pressing the power-button on the computer.
That's why remote.xml exists as a separate option.
I thought Legacy was for NVidia cards?
Generally yes, but the old X11 can sometimes fix issues like this.
Is the SD card with the problems completely broken, or will formatting it be enough to get it working again?
Use GParted for scan and repair. This tool can leave bad blocks out during formatting.
Yep, if you find a current crash log, post that one, and use the same method as for kodi.old.log. ATM it's unclear whether it's a crash or a hanger.
But when the issue occurs, the system is unresponsive and I have to switch it off to get it to work again.
For such cases use cat /storage/.kodi/temp/kodi.old.log | pastebinit from SSH, and post the resulting URL. kodi.old.log contains the data from the last session with the crash.
Before you start logging, set the log level to 1 at advancedsettings.xml, and reboot.
Just log at log level 1...
Thanks for your prompt reply but I am not sure what you are saying.
Simple: No support until you've cleaned your LE add-ons and repos.
So the DAC doesn't exist at /dev folder after boot sequence, right? What's the /dev path after hot-plugging the DAC?
I guess you have to remove the driver(s) first. Also try to restart the audio server (ALSA).
chewitt Maybe reloading a driver from autostart can do the trick?
Maybe a problem with the USB hub. Connect the DAC without using the USB hub.
Thanks. Please post a complete log for the boot sequence (when the DAC isn't detected).
Is the DAC selected as your default audio device in the settings?
- What's the difference between the versions contained in the pages?
First one is stable, second one is for development builds, which we call "nightly".
- Why "nightly"?
Calling it "development" or "dev" can be misleading, because "dev" packages have a different meaning in Linux world.
- Are these beta versions, not stable?
We don't do formal beta tests, so no. Nightlies are not as much tested as "stable" versions, but still very stable, because our devs are pretty accurate. Most users are happy with them.
- When I need to download a stable version, which page should I use?
The page from your first link, and download the latest version of Generic PC (no NVIDIA support).
...but when you break the board due to lack of soldering skills; expect zero sympathy in this forum.
I agree.
E-book readers even more difficult. They aren't designed to be opened or repaired - you need pro level skills for that. However, feel free to post pictures of your progress here. That's new stuff for us, and maybe LE will run on an e-book reader in the future.
removable
I see. Those e-book readers are usually super flat, so I assume they all use soldered SMD chips.
PS: I don't know whether or not the Onyx Boox has a separate WiFi chip. You probably also need instructions how to open those devices. This can be more stressful than removing an SMD chip.