Posts by Iridium

I found a docker solution that seems to work on Raspberry 2 & 3.

1) Install LE Docker add-on

2) docker pull polinux/stress:armhf

3) docker run -ti --rm polinux/stress:armhf stress --cpu 4 --timeout 10s

Full description Here

I've had a play with my new RPI3 B+ on LE 8.2.5 and rebooted (SSH and Kodi) about 7 times without an issue. However as @HiassofT mentioned, it's rather random.

As the RPi3 B+ is fairly new, it's unfortunate that the timings didn't arrive in time for 8.2.5, so it's better to use a LE9 test build.

Just tried 8.2.5 on my new RPi3 B+ and everything works fine.

Are you sure you are close enough to the router, the internal wifi antenna is not the best in the world.

You also use movieshark and as this is a banned Kodi add-on Banned Add-ons,

NO FURTHER SUPPORT WILL BE PROVIDED until this add-on is removed.

Looking at this, and the other thread you mentioned, it seems to me that it is related to some (or all) add-ons that you are using.

I and others, have been using 8.2.5 on RPi2 & 3 without any issues.

Can you provide kodi and dmesg log files, as explained in my signature, also the url from "top -b -n 10|paste".

Also, if possible explain what is happening prior to a reboot and length of time before a reboot.

Another question? Is this a fresh install or an upgrade from OE?

Can you provide logs files as explained in my signature

To be factual, it's a lack of hardware support for that codec as ozkaradag mentioned, so the decoding has to be done in software and that's where the CPU usage comes in, as the video has to be decoded in software on the fly - which is why it stutters.

You could try a LE9 Milhouse build, but even at 60% usage you might still suffer from stuttering if you have any other processes running (TVHeadend etc) Also you'll need to keep an eye on the temperature as well.

The video requires considerable CPU resources. On my RPi3 (8.2.5) it was using 100% on all 4 cores.

On LE9 it plays, but still uses about 60% on all 4 cores.

So your best bet would be to decode it to something else (If you have a more powerful machine)

As trogggy mentioned, this method is the LE preferred route. If you need to reinstall for whatever reason, write a new image and just restore the backup.

There are methods in Linux to "shrink" and image but I'm not aware of a similar program in Windoze. You could try searching for one.

I've been using NFS as my default on my NAS and it's fairly easy to setup, but as with anything Linux it needs some understanding of all the options.

However in your case it will not work as LE does not operate a NFS server, only a client, so that discounts your idea.

So - in my opinion - I think you'd be better off installing "emby server" on LE Here and use the emby app Here on your Android device to play your media. For more information about Emby see Emby.

Ok, I now have it running successfully. It's my first real play with docker so a few improvements are definite.

As far as I know this only works on X86 and Raspberry Pi 2 & 3 only.

For X86 you’ll need to change a few things – See Here

1) Install docker

KODI: Addons → Install from Repository → LibreELEC add-on → Services → Docker

2) ssh into you machine: SSH

3) Get the pi-hole docker container

## Raspberry Pi

docker pull diginc/pi-hole-multiarch:debian_armhf

4) Create a run-time script:

docker run -d \

--name pihole \

-p 53:53/tcp \

-p 53:53/udp \

-p 80:80 \

-v /etc/localtime:/etc/localtime \

-v /storage/pihole/:/etc/pihole \

-v /storage/pihole/dnsmasq.d/:/etc/dnsmasq.d \

-v /storage/html/:/var/www/html/html/ \

-h $(cat /etc/hostname) \

-e ServerIP=$(ip route get 9.9.9.9 | awk '{ print $NF; exit }') \

-e WEBPASSWORD=libreelec \

--restart=unless-stopped \

diginc/pi-hole-multiarch:debian_armhf

This is set to store pi-hole files locally in /storage and sets a web password of libreelec.

Run your script.

Now log in via a web-browser at <IP-address>/admin

Once you are happy everything is running as it should, change “unless-stopped” to “always”.

Test to see if pi-hole is working correctly, go to Pi-hole test page

Don’t worry is you see an error about blacklist.list, to get rid of it just add an entry to blacklist in the web interface.

Useful commands.

docker logs -f /pihole # Show docker logs

docker stop /pihole # Stop pihole

docker rm /pihole # Remove pihole container

docker ps -a # Show containers

docker system prune # Remove ALL containers (VERY DESTRUCTIVE)

EDIT: 09/06/18.

It make more sense for LE backups, to store the date in .config so:

-v /storage/.config/pihole/:/etc/pihole \

-v /storage/.config/pihole/dnsmasq.d/:/etc/dnsmasq.d \

-v /storage/.config/pihole/html/:/var/www/html/html/ \

Also to remove black.list error just

touch /storage/.config/pihole/black.list

Also - to protect you further from known threats -, use Quad9 as primary and secondary upstream DNS servers.

-e DNS1=9.9.9.9

-e DNS2=149.112.112.112

EDIT 11/06/18

LE is now actively incorporating a LE addon for pi-hole. At the moment it is still in testing, but is looking good.

Depending on you HW and amount of free RAM available. Example for 1G of RAM.

In .storage/.kodi/userdata/advancedsettings.xml

<advancedsettings>
  <cache>
    <buffermode>1</buffermode>
    <memorysize>139460608</memorysize>
    <readfactor>20</readfactor>
  </cache>
</advancedsettings>

memorysize and readfactor can be increased, but will have possible other issues. Try increasing a bit at a time.

A Windoze BAT file on your desktop should work, with

ssh [email protected] 'echo libreelec | reboot'

Where nnn is the IP address of your RPi.

See previous #6 this was solved Here".

If it's the same error as I had it's due to the lack of a MAC address, so it will connect once with a random MAC address but after a reboot, you'll get a new MAC address, so it will forget everything like password or IP address if static.

Obviously set the MAC address to something notable, especially if you're using, or plan to use more than one adapter. I changed the last 3 digits to the 192.168.0.nnn IP address as I have static IPs. Of course you could always add a DHCP reservation in the router if you want.

Otherwise if not the error, post debug logs. dmesg and kodi.log How to provide log files

From Kodi

History buffer, Current buffer and Lookahead buffer.

So it's unlikely to completely fill the buffer if your device is not on 24/7 or you don't watch a lot of media (Which is probably why I didn't see the 3x memory allocation).

Yes I disabled the internal RPi3 wifi with dtoverlay=pi3-disable-wifi in config.txt. I believe you can use both as the internal will show up wlan0 and the external as wlan1.

In my testing/playing I've not seen this 3 times element to actually happen. What I set and what my memory allocation is, is nowhere near the 3x reported (Mind you this has only been on RPi and Cubox-i so other distros might be different).

I've a feeling that this figure is archaic, from a time long ago but is not valid with current Kodi releases. I set my cache to 1G on my cubox with only 2G memory and it worked fine.

As chewitt mentioned, and from my own experiments, the default settings are fine, but you can "tweak" it slightly but don't expect a "magic button" from editing it.

Quote from jglazer63

How did you use that? Drivers? Plug and play?

The ones I used were "almost" plug and play. Because they were cheap, they didn't seem to have a MAC address, this was solved Here