I can't for the life of me get HDR playback working, 4K playback is all good, but tv won't switch to HDR.
Cables are all good as im using the same one on my xbox s that switches to HDR ok.
Using S905 box and panasonic TV.
Matt
tv - Panasonic VIERA TX50DX700B | 50 inch 4K Ultra HD HDR Smart LED TV Freeview Play | Richer Sounds
Sorry mate, but I'm afraid S905 doesn't support HDR. Only S905X supports HDR mode.
Thanks for asking.
I should in fact perhaps repeat upon every update.
- 64bit image is built from same code as 32bit one, all credits to our
hero kszaq.- I never ran 32bit image. I suppose going from 64bit image to 32bit
image or vice versa is similar. Also, I always run from external SD.Perhaps a clean install on dedicated external SD is safest approach.
- 32bit image will need less memory.
- 32bit image runs more addons. One cannot mix 32bit and 64bit code
So only addons without any binary code can work on both.- 32bit image can also, should this ever be needed, use 32bit code
from android partitions. I doubt however if such would ever be needed
for average use. And I also doubt if it would work.- It may be harder to find some 64bit addons. One may need to build
them oneself.
* In short: 32bit image has many advantages. 64bit image has some
disadvantages.
That said. For my, agreed, simple usage, 64bit image with some TV
related addons works just fine. The few other addons I need work fine
too.I use 64bit LE primarily to allow me to maintain a gentoo 64bit
stage3 chroot. And because I have sufficient amount of RAM. And
because I have a 64bit machine.I would say, use at own risk.
But... Does it have any significant improvement talking about performance?
You can only change your local copy.
Thank you very much 
You need to change version.
But sometimes you need to bump other related packages too.
So i would have to fork the entire repo, isn't it?
git pull again and build - kodi package was updated yesterday.
Thank you vpeter. But... if it wasn't the case? I mean, how could I do it if the Kodi package wouldn't have been updated yesterday on LE repo?
Hi there,
recently I discovered how to build LE by myself from github. I was wondering, how can I build a proper LE 8.0 branch build with the latest Kodi 17.1 fc1719b commit?
Hello guys,Iam on the Matricom MX and after installing v8 i get: can't access tty job control turned off
However previous v7 booted fine.
I did run thisCodetune2fs -L LIBREELEC_DISK /dev/data
but i have no idea what the output in ssh should look like.
Just assuming it worked since it didnt return an error.Any ideas?
Same issue here.
Hi, my friends
I am having problems with the final version of libreelec 8 in a RPI3It seems that the corrections that I need are implemented in kodi 17.1
My question is if there is going to be any update with this revision. Or if you otherwise need to change the version of libreelec.
I'm new to libreelec.
Port true because in the information of the system I only appear 750 mb more or less d were when the aprato has 1 gb.
Thanks and a big hug. Great job
He compilado yo una imagen de LE 8 con Kodi 17.1. Si la quieres te la paso.
I've compiled an image of LE 8 with Kodi 17.1. I can share it with you.
Do the external HDD each have a label name?Connect both drives, and give us the result of the following commands
Codeblkid | pastebinit mount | pastebinit
I didn't set any label name
/dev/mmcblk0: PTUUID="99176dab" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" UUID="176D-2AFE" TYPE="vfat" PARTUUID="99176dab-01"
/dev/mmcblk0p2: UUID="f2c26989-d7ab-4c16-9d6a-36e40c02035b" TYPE="ext4" PARTUUID="99176dab-02"
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="5B9AA4821C625CCB" TYPE="ntfs" PARTUUID="24f17d68-01"
/dev/sdb1: UUID="3bc77ff7-b2b5-4e2d-9ad5-98fabc815330" TYPE="ext4" PARTUUID="000dcb72-01"
devtmpfs on /dev type devtmpfs (rw,relatime,size=339620k,nr_inodes=84905,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/mmcblk0p1 on /flash type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/mmcblk0p2 on /storage type ext4 (rw,noatime,data=ordered)
/dev/loop0 on / type squashfs (ro,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /var type tmpfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /var/media/sda1-ata-ST9500325AS_S2WK type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdb1 on /var/media/sdb1-ata-_7475A5E983_4-pa type ext4 (rw,nosuid,nodev,noexec,noatime,data=ordered)How could I set a label name?
[hr]
Ok, I found out how to set a label for an EXT4 filesystem using e2label, but it doesn't work with my NTFS hdd.
[hr]
OK, I got it using ntfslabel. They are set on a fix point right now, exactly as you said. Thank you very much!!!!
[hr]
The workaround is just like this:
For ext2/3/4 you can use e2label like this: e2label /dev/device new-label-name-here
For NTFS you can use ntfs-3g like this: ntfslabel /dev/device new-label-name-here
And the hdd will mount in the same point.
Hi there,
I have two external hard drives connected to my pi2. If I remove anyone of them or I change the plug where they are connected (I'm using a HUB) they mount in another point and all the files added to my library are unable to open.
Is there any way to set a fix mount point for each hdd?
Open the script, find this line:Codegrep OpenELEC /etc/os-release >/dev/null && DDTIME=5 || DDTIME=6
change "OpenELEC" to "LibreELEC" and give it a try.
It works LOL. Thank you 
Where did sdbench come from?
From Milhouse recommendation: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2
sdbench.sh
[hr]
The script (or whatever sdbench is) probably assumes "full" bash or awk/cmd tools and we're using busybox applets.
It used to work fine in older OE versions (6.0.3 included).
Tried to get son benchmarks of my sdcard, it seems that the sdbench script gets some kind of errors:
CONFIG:
CLOCK : 100.000 MHz
CORE : 500 MHz, turbo=1
DATA : 512 MB, /storage/test.dat
HDPARM:
======
Timing O_DIRECT disk reads: 124 MB in 3.05 seconds = 40.72 MB/sec
Timing O_DIRECT disk reads: 124 MB in 3.03 seconds = 40.87 MB/sec
Timing O_DIRECT disk reads: 124 MB in 3.02 seconds = 41.03 MB/sec
WRITE:
=====
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 98.600303 seconds, 5.2MB/s
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 71.782989 seconds, 7.1MB/s
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 62.256726 seconds, 8.2MB/s
READ:
====
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 14.029445 seconds, 36.5MB/s
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 14.040410 seconds, 36.5MB/s
awk: cmd. line:1: Division by zero
536870912 bytes (512.0MB) copied, 14.052803 seconds, 36.4MB/s
RESULT (AVG):
============
Overlay config core_freq turbo overclock_50 WRITE READ HDPARM
500 1 100.000 MHz 0.00 MB/s 0.00 MB/s 40.88 MB/s[font="Monaco, Consolas, Courier, monospace"]awk: cmd. line:1: Division by zero ¿LibreELEC related?[/font]
Same problem here. Just solved downloading manually the tar file ;D
There was a problem booting #0322 (which is no longer available on the server) but the problem is fixed in #0322b, unless it's a different problem. Can you grab a screenshot/photo if it happens again?
Sorry Milhouse, my problem was with #0322 build, and I didn't realize that you updated the file on the repository after that. I've just flashed the new #0322b build and it's working flawlessly.
Thank you very much and sorry for the confussion. My mistake.
Thank you very much.
[hr]
That would be strange. We tested that yesterday in the evening and had the same issue. We reported and Milhouse fixed it. I installed #322b myself yesterday in the evening without having issues.I'll report to him.
Cheers
Sorry mate, I didn't realize that you changed the file in the downloads directory. You are right, my problem was with #322, not with #322b.
I'm going to try the new version right now.
Thank you mate.
[hr]
Working like a charm.
Thank you!
I tried to update from OE 6.95.1 to LE RPi2.arm-7.0-Milhouse-20160322183009-#0322b-g2f1b279 build and it resulted in a Kernel Panic.
After that, I went back to my OE backup and I updated RPi2.arm-7.0-devel-20160321035214-#0321-g3ab346e.tar successfully.
Is that .tar file bugged?
That thread would be better for it. But it takes a while to recieve it. about 15 minutes before I got it.
ON TOPIC Congratz with the initiative and good luck to all!
Gr,
Johan
Have you checked your Spam folder?
Well, thank you guys, that was useful lol. I'm ashamed for being so noob. 