Prove with evidence that you are not creating so-called "builds" or wizards full of pirate add-on crapware and we will consider further help. Sadly that is the main reason why people hack Kodi apks on Android, and we have no desire to see the same scumbags adopt our distro.
Posts by chewitt
-
-
GitHub - chewitt/LibreELEC.tv at leiot-8.0 has a second 'distro' option (LEIoT) to build that drops Kodi/media stuff and gives you a console-only version of LibreELEC about 75MB in size. Last time I built an image it failed on something, but it's probably minor. It needs further work to add a docker package to the image (which will bump image size); then you can pull the LinuxServer.io tvheadend container and leave it to rot hidden in a cupboard somewhere. I might blow the dust off this in the near future, but no guarantees.
-
Just connect a keyboard and run the USB in 'live' mode.
-
I split the thread because your issue has nothing to do with the other persons issue. I've re-read what you wrote 3-4 times and cannot understand what exactly you're trying to do? - initial install to an SD card or something to do with add-ons/repos?
-
scareyb - repeat with a different SD card, same result?
-
Sounds like something to be reported to Kodi devs via their forums.
-
C2 has an official build. Have you tried it?
-
Was trying to understand the relationship between the two more. Why is it there is a need for community builds?Why do people pimp their cars? .. there's always someone that wants something different.
Unless there is something you really must have that's available in a community build, stick with official.
-
Raspberry Pi hardware is not the fastest out there, and it doesn't play every codec out there, but no other hardware receives anything close to the A1++ support and attention to detail that we see from the Pi Foundation staff to ensure Kodi runs great. The on-board audio is nothing special but there are a huge number of i2s DACs available, and there's no reason why the USB device you already have shouldn't be usable.
-
This is a desktop casting client. It will not help you to 'cast' things to the speakers/display connected to an LE/Kodi HTPC.
-
Kodi runs great on an RPi3 but if you install the amount of pirate add-on crapware that your log shows I would expect problems. Aside from the dubious legal status of those add-ons (and banned in this forum) they are poorly coded and frequently attempt to detect and break other 'competing' add-ons to drive user traffic to their forums where you generate adsense profits for the scum who operate the sites.
As you have discovered, the problem follows you between LE, OE, OSMC, which proves it is not an OS problem. If you purchase a NUC and reinstall the same crap it will run the crap faster, but equally crappy.
-
If you are using Ethernet there is no need for cache tweaking. Your network has to be royally buggered for Ethernet to not work in an out of box config and if that's the case, the solution is fix the network not force Kodi into the unknown with ridiculous cache settings.
No debug log = no problem
-
Stick with the default LE image or @codesnakes image. Report the issue to WeTek support. Let them guide/help you.
-
-
Code
[ 0.000000] Linux version 4.4.32v7-aufs (max@lynx) (gcc version 4.8.4 (Buildroot 2015.02-gf4a5ebb-dirty) ) #1 SMP Fri Nov 18 23:17:35 CET 2016 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383dBerryBoot?
If yes, no further support until you've tried a proper LE image running our kernel not the frankenstein image you're using. Seriously. We build a tightly integrated OS/app package and we do not support someone else's completely different kernel.
-
You need to create different sources for Movies and TVShows. If you add tvshow content to a shared folder that had "content type" movies set, they will not scrape; or to be correct, they will scrape but the scraper won't find movies matches for them.
\\SERVER\MEDIA\MOVIES
\\SERVER\MEDIA\TVSHOWSor
\\SERVER\MOVIES
\\SERVER\TVSHOWSnot
\\SERVER\MEDIA <= with both types in the same location
-
Does anything happen when you run "eject /dev/sr1" from the console? .. on some wireless devices the fake CD device (with drivers etc.) must be ejected before the wireless part is made available. Otherwise there are some messages in dmesg that I haven't found a clean explanation for yet.
The easiest way out of this is to shift the content off the drive and do a clean reformat, copy it back. As much as a I like debug challenge it would be quicker if you have something to temporarily move the data to.
-
hammerboy, that image is updated with a large patch from OE's collection that probably solves a bug in the driver. Test again and report back.