No problem, the file has to be created at /storage/.kodi/userdata/advancedsettings.xml.
Posts by Da Flex
-
-
Do you use your AVR's RC to control your TV? I'm asking because normally an AVR uses different CEC codes than a TV. LE only responses to TV CEC codes.
Some LE users connected an IR receiver element to the RPi's GPIO, and were able to use IR codes to control LE. That could work for you, but it's not easy.
-
The right questions now are:
...
No. The right questions are:
- What do you want to do on your scenario?
- Why don't you upload the log?
-
In such a special case a kodi.log is necessary to see what happens. You can copy kodi.log when you attach your microSD card to your PC. Then upload it to Pastebin and post the link. After a reboot kodi.old.log will be the log of your last session.
-
After reading the thread again, I found a point we haven't discussed yet. Can you please verify that your HDMI cable is HDMI 2.0 or 2.1 standard? It's weird that a DVI -> HDMI adapter limits the resolution. Maybe actually the cable limits data transfer speed, resulting in a reduced color space.
-
After some more reading it looks like HDMI-1 depends on an active HDMI-0. Just for testing, start your RPi with both screens connected.
If it turns out that this dependency is true (do an extra research to be sure), you have to buy an HDMI switch to do what you want.
-
I haven't found a solution that does HDMI0 -> HDMI1 on-the-fly. Using config.txt at boot time seems to be the only software option.
We don't call it a script, config.txt is a configuration file.
The config.txt of the link starts with arm_freq=1500 and ends with hdmi_pixel_freq_limit:1=0x11e1a300. Copy that part into your own config.txt.
If it has no effect, I can only suggest a hardware solution, which is an HDMI switch.
-
Every line containing :1 should be related to the second port, like hdmi_group:1=2. hdmi_safe=1 seems to be important, too, but I can't test it on my RPi 3B+.
-
Using the second HDMI port (HDMI1) is work in progress. I found this config.txt to enable both ports. Give it a shot.
-
Am I editing the correct file?
No, use /storage/.kodi/userdata/keymaps/remote.xml.
What is the correct entry to enable the options menu?
Code<keymap> <global> <remote> <yellow>ContextMenu</yellow> </remote> </global> </keymap> -
I think an installation or update process of this add-on went wrong, and this can cause errors like yours.
Uninstall the YouTube add-on and reboot. If everything works fine after this, install the add-on again.
-
Keep the original URL and redirect the update request on your server.
-
Looks like something went wrong with your YouTube add-on installation. Do you have the ability to uninstall and re-install this add-on?
-
I don't know why, but it seems the player of Kodi uses the RAM more intensely, which then crashes if it is faulty.
I bet Plex has been used higher addressed RAM cells, and they probably worked fine. Interesting that you did the RAM test, as suggested by me, but haven't found errors. Use MemTest86, and let it run for some minutes.
Also, how do a mark it as resolved?
Hit the "Edit Topic" button over your first post (I'm using the German version, so I can't tell the exact button title), and mark the thread as solved.
-
Thanks for testing. Next you can try the alsa mixer this way:
Codeamixer -c 0 set Digital 80% -
Is there a way to install LibreElec in headless mode?
No, but you can turn off the display by using the tvservice command on autostart.sh.
Currently, my strategy is to install Raspbian Buster Lite and install Kodi with "sudo apt-get install kodi."
Most headless LE users only do it, because they need special add-on's, which are not available for other RPi OS'es. If that's not the case for you, go the Raspbian way.
Don't forget that you will run into display package dependencies when you install Kodi on a headless Raspbian. So using a standard Raspbian and switching off the display by tvservice could be the best strategy.
-
Please check whether editing the volume setting of guisettings.xml (bottom of the file) makes a difference for your apps.
-
To my knowledge there is only one sound server available for RPi. The HiFiBerry driver feeds that sound server, and players use both components. It's on you to try different players from add-on repositories. If the sound server is the weak part, then they will have no effect.
There is an exotic Korean LE mod, optimized for audio. Currently I only see RPi 2/3 builds. Maybe they start RPi 4 support, soon.
