Provide a link to the addon sources online so we can see what the addon does, and we'll consider providing further information.
Posts by chewitt
-
-
Add "tty" not "textmode" to kernel boot params in /flash/syslinux.conf (or extlinux?) and you will have an unsecured tty on CTRL+ALT+F3, and the Kodi GUI on CTRL+ALT+F1.
-
cp /etc/swap.conf /storage/.config/swap.conf
^ now edit /storage/.config/swap.conf and enable swap, change the swapfile size to something larger than RAM size. This enables the swapfile. I've no idea if that's what determines hibernate support on an x86 device but it's simple enough to test and if it doesn't work just delete the .conf and swapfile.
-
As long as you install an official LibreELEC image and make zero modifications to the image there is no problem with selling devices that are pre-installed with LibreELEC. If you sell lots of systems and thus profit from our work an occasional donation to support the activities of the project would be appreciated (not required, but appreciated).
-
This is what I was getting at. I just have a feeling that the developers of Volumio and other audio OS would be better using LE as a starting point for a dedicated (no compromise) audio OS.
Having talked to some of them in the past. Most are individual app developers or very small teams and it's easy to package your app into someone else's distro like Raspbian. Taking that a step further and creating your own embedded distro requires a different set of skills, and while LE is fairly simple to manage (when you know how) it's also a little obscure in how things are packaged and that knowledge takes time to learn. I'd love to see more of those app-distros adopt our codebase (similar to Plex and Lakka) and it would also benefit them by broadening hardware support beyond the Pi ecosystem. The desire or initiative to do that needs to come from their side though, else we end up pushing water uphill.
-
Generate an SSH key on the LE box and add this to ~/.ssh/authorized_keys on the server side. Then you can authenticate with keys (not passwords) and push files with scp.
-
leonb It sounds like you have an older OE installation with a smaller 235MB boot partition. Just create a new 8.2.5 install using the USB/SD creator and this will create a 512MB partition. Then you can update to the milhouse image using the .tar file.
-
I confess that it was moOde audio I had a go at porting, not Volumio. An LE image with MPD on its own (no Kodi, less video stuff) came in about 90MB in size which is much nicer than the typical 400MB-1.2GB of debian based things.
-
Make sure Windows updates haven't reset the firewall configuration and blocked access.
-
Yup. If filesystems aren't clean Linux defaults to mounting RO to prevent damage. Depending on what the underlying issue is you might be able to fsck and fix issues, but that's a risk and i'd always advise waiting until the replacement drive arrives and you can transfer data over before you attempt repairs.
-
I did attempt porting Voumio to LE at one point but gave up on the Apache2 dependency. Nothing to stop you from installing the MPD add-on though (which most of the pi audio distros are based on) and then ignoring the fact that Kodi exists in the background
-
As long as the filesystems are clean mounting is handled automatically. You probably 'configured' the drive labels in the past (not mount options) to ensure each drive mounted with a distinct name.
-
wedok Kodi bumped the addon api recently but we (me) didn't build/push updated 3.14 kernel addons to the repo since then so whats in the repo is probably not compatible. I'll update them in the next couple of days when I have time.
-
Are you saying that the mecool ki pro (S905D) does not really have gigabit?
S905X has an internal PHY so is always 100-BaseT while S905D has both internal and external and can support 1000-BaseT via the external PHY if manufacturers choose to implement one. The sample boxes I have are aimed at the "streaming" market where fast LAN isn't needed so they save $$ and use the internal PHY only.
I've no idea about that specific box .. I've never seen one and have no interest in acquiring one.
-
So that's the reason you have a S905D box to go with that OLED TV
I'm still using WP2 as the family daily-driver because I have no HDR media except for some test files and the S905D box I've been poking has the same weakness as the S905X; it has 100-BaseT ethernet which chokes on the full-size BR rips that I made. The WP2 might be "inferior" as the SoC has no HDR support but it has GB ethernet that handles the same files with ease, and I can't be arsed to transcode or re-rip all my media just because people design sh1t hardware. The next daily-use upgrade I make will probably be an Amlogic SBC that partners S905D2 with a GB NIC, or an equivalent RK board. The first manufacturer who gets to a mainline kernel and the next-generation video pipeline in Kodi will have my attention!
-
miniDLNA is in the 9.0 addon repo, it was not submitted to the 8.2 repo
-
I am reading the Amlogic site and it says all S912, S905D and S905X support UHD HDR. So what's the difference?
The difference is how they support it. S905D/X internally convert 10-bit to 8-bit for processing. S912 processes 10-bit. Future devices like S905D2/X2 and S922 process at 10-bit. Most users who obsess over the whole 8-bit/10-bit thing won't be able to tell the difference. More users will just be happy the HDR mode triggered on the TV and they can point at the brighter screen and tell their wives it was in HDR and looks so much better (and thus the purchase of the new UHD HDR TV was justified)
-
Do you confirm that /storage/.kodi/userdata/passwords.xml exists and correctly shows the substitution for each source?
