If you want the OS to display Japanese text in the Console you need to install "locale" from our addon repo. If you want to change the keyboard layout; this is done in the LE settings addon and the options available are dictated by the graphics stack (as I said in the other thread). Xorg has an extensive list of layout options but the Raspberry Pi has more limited options because we are running directly on the framebuffer, we are not using Xorg like Raspbian. Finally you have the on-screen GUI keyboard and Skin language options in Kodi settings.
Posts by chewitt
-
-
There's no way to discover this without adding additional debug code into Kodi and the Linux kernel, i.e. add printk statements in code, it's not possible to enable some extra debug logging setting. It's a shame the LG panel doesn't show more info (as I have the 65" B7).
-
Zeroconf browsing works fine as long as the SMB shares are advertised via Avahi, which normally implies a NAS using Samba. Windows does not ship with an Avahi/Zeroconf service so Windows hosted shares will not be visible over Zeroconf.
-
Another alternative would be to install portainer via the LinuxServer.io repo (their repo installer is in our repo) as this is wrapped as a Kodi addon and so depends on Kodi; so it won't be started until after Kodi starts, and any containers that it manages are started after portainer.
-
-
I had a usb stick worked well for years now it is stuffed after libre write. I think you need to be prepared to put libre on the stick and then not use it for anything else. i am going to get a cheap one for that purpose. Is 1gb big enough for the write? I know 2 gb is
Windows is retarded when it comes to Linux USB's, but ^ download and restore that .img to the USB using USB/SD Creator (or anything else that writes USB sticks) and Windows will magically see an unformatted full-sized USB stick again.
-
/storage/.kodi/userdata/addon_data/service.libreelec.settings/oe_settings.xml <= OS
/storage/.kodi/userdata/guisettings.xml <= Kodi
-
First you need to tell us the HTPC hardware you have?
-
If you need to delay video to match the slower audio path that makes sense. I'd guess you have HDMI to the TV which has to process the audio to an optical or HDMI output on the TV and from there into the Sonos which then has to process the audio for output. Even if everything is in pass-through audio mode the format might not change but there's still going to be a buffered input/output process somewhere, and that's where delays stack up.
-
I've only ever seen delays on the audio side from processing (requiring video to be retarded, or in kodi-speak the audio to be advanced) never video delays that require a corresponding audio delay. Weird. What TV panel?
-
.tar is only for update.
LE has supported update from .img file (in addition to .tar which is larger but quicker) since an early 7.0 alpha release.
-
Are you routing HDMI through something? .. 735ms is a HUGE delay to incur somewhere in the processing chain
-
-
Network Boot - NFS [LibreELEC.wiki] is probably a good starting point
-
Your box has no user-accessible "firmware" only "software" installed for boot (u-boot) and the OS image which is being booted. The device-tree has to match the kernel version being booted so it will vary between Android and Linux and older versions of Linux and newer.
-
This is headed in a wrong direction so thread is closed.
-
Which version of LE and using what hardware? NB: If not the current alpha, go test the current alpha.
-
It's in the PVR section of the LibreELEC addon repo.