Posts by wizardknight

    cozmo. I have a rock64 2gb board and a 55" 4K TCL TV.

    I use CEC with my TV on the latest test release. I did notice that it didn't take effect until after I rebooted. Also it does not work within a few seconds of the system going to sleep. However if I waited a little bit, the TV would turn on.

    I have not noticed any USB keyboard issues.

    I have not seen issues with hanging videos when skipping.

    My 4K HDR videos seem to play fine. I had to force the TV to HDMI 2.0 for the HDR to work however.

    I also see the green flickering horizontal lines previously reported in the GUI when it is running at 4K res.

    You might try this fix someone reported with similar issues.

    Physical keyboard unresponsive after upgrade

    Does anyone know how to remap the browser backward buttons on a Logitech mouse?

    I used to be able to use them to go to the previous menu. Now they do not function at all.

    I had seen a fix about this on a older kodi 15->16 upgrade, but for the life of me I can't find that post anymore.

    The gui keymap utility does not work for me on these mouse buttons.

    For reference, these thumb buttons.


    I finally pieced together enough of the mouse keymap to get a working back button.

    Here it is if anyone else wants to try.

    You might need to try numbers 5-9 for the click id depending on your mouse, and some people might prefer

    This would have been so much easier if the Kodi mouse keymap Wiki had something other than "Further action required"

    <click id="6">Back</click>


    I had seen where 4K media would not play sound out via HDMI to TV, and the TV redirected it to my sound bar over the 3.5mm jack. But as soon as I switched back to 1080p I had no issues (that was v21 however).


    I am trying to upgrade from 21 to 24 on my Rock64. I put the tar I downloaded into the Update folder, rebooted.

    The system stayed at 21, and the tar file was deleted. No upgrade. :(

    I should be able to go from 21 to 24 without the intermediary upgrades, correct?

    I have not started digging into it, but I figured this would be a good thing to double check first.


    The D pad on the remote works fine, so I don't think eventlircd is having issues.

    First I copied the keymap:

    cp /usr/lib/udev/rc_keymaps/rc6_mce /storage/.config/rc_keymaps/rc6_mce

    Second I edited it.

    I fixed the play/pause button, OK, and back.

    Here is my keymap if anyone wants to use it rather than reinventing the wheel.

    Just put it in /storage/.config/rc_keymaps/ or \\LIBREELEC\Configfiles\rc_keymaps if you have samba running.

    It has all the basics working. Volume, mute, D-pad, OK, back, zombie release, play/pause, fast forward, reverse.


    I was just wondering if the ok button on your remote worked. I get no response when I press it.

    I found this error in the kodi log file when I press OK:

    CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(352)

    But if I drop out of kodi, and look at the ir-keytable test I see:

    LibreELEC:~/.kodi/temp # ir-keytable -s rc1 -t
    Testing events. Please, press CTRL-C to abort.
    1514244056.683666: event type EV_MSC(0x04): scancode = 0x800f0422
    1514244056.683666: event type EV_KEY(0x01) key_down: KEY_OK(0x0160)
    1514244056.683666: event type EV_SYN(0x00).
    1514244056.841609: event type EV_MSC(0x04): scancode = 0x800f0422
    1514244056.841609: event type EV_SYN(0x00).
    1514244057.091590: event type EV_KEY(0x01) key_up: KEY_OK(0x0160)
    1514244057.091590: event type EV_SYN(0x0


    Looks like this might need to be updated at the code level.

    I found this git where they did it for the wii mote with a similar issue.

    Add mapping codes for the wiimote by tirithen · Pull Request #13139 · xbmc/xbmc · GitHub

    Would you consider adding these three keycodes?

    It would give the remote a lot of functionality.

    + { 352 , XBMCK_RETURN }, // OK

    + { 226, XBMCK_HOME }, // Home (windows button)

    + { 174, XBMCK_ESCAPE }, // Back


    I am not sure how, but I can redirect to my external hd now.

    The command is the same as the one I first tried.

    rsync -rav --modify-window=300 --homan-readable --progress  --stats --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ > /var/media/8TB_WD2/synclog.txt

    I guess I was not biting my tongue just right.

    Now to stick it in cron and see if it plays nice there...

    wizardknight please have look here infrared_remotes [LibreELEC]

    Disable lirc and create a


    * * rc6-mce

    You can also test the multi keytable

    *       rc-rc6-mce               libreelec_multi

    I have been working from that wiki. I linked to it in my first post asking for ideas on getting the IR remote to work.

    I have not been able to disable lirc as far as I can tell.

    I should be able to disable it in LibreELEC Settings → Services and reboot.

    It was already disabled. I tried enabling it, rebooting, disabling it, rebooting again. No change.

    Lirc still shows as the enabled protocol when I issue the ir-keytable command.

    I created the file and added the code you listed, and rebooted.

    I also tried variations such as: using RC1 rather than RC, calling the driver by name rather than an *.

    ir-keytable does not show any change. It also does not load RC6 protocol upon reboot.

    I can do

    ir-keytable -c -s rc1 -w /usr/lib/udev/rc_keymaps/hp_mce

    That will add RC6 to the ir-keytable, but I get no responses when I test using keytable -s rc1 -t

    I suspect it is because I haven't found a way to get rid of the lirc protocol

    If I kill kodi and eventlircd, then I can get test data from keytable -s rc1 -t after enabling RC6 protocal, but I can't get that to show while kodi is running.

    I have made a little more progress on getting a remote to work.

    If I kill everything, and setup RC1 to catch RC-6, I can get real scan codes from the remote.

    systemctl stop kodi
    systemctl stop eventlircd
    ir-keytable -p rc-6 -s rc1 -t
    Protocols changed to rc-6
    Testing events. Please, press CTRL-C to abort.
    1514012903.765030: event type EV_MSC(0x04): scancode = 0x800f0421
    1514012903.765030: event type EV_SYN(0x00).
    1514012903.924995: event type EV_MSC(0x04): scancode = 0x800f0421
    1514012903.924995: event type EV_SYN(0x00).

    Looking around the forums it was suggested that lirc might be blocking the codes, and that I should disable it in LibreELEC Settings → Services and reboot.

    It was already disabled. I tried enabling it, rebooting, disabling it, rebooting again. No change.

    Getting closer.

    No I don't know, I was going to correct you on your options, but it wouldn't let me, and I realised that your post was deliberately misspelled.

    I'll see if someone higher up the foad chain can help with that.

    PS apparently f o o d is banned too.

    It must be aliens. They don't want the secret getting out. Homans are f00d!


    I didn’t test to output the log to the destination disk maybe is getting deleted at the end. Try another location maybe /storage for the log file

    I redirected the log to storage, and it worked. A gold star to you.

    rsync -rav --modify-window=300 --progress --log-file=/storage/backup/synclog.txt --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ &>/dev/null

    LibreELEC:~/backup # ls

    Now the question is why can't I write to my external HD as root? That is just all kinds of special.


    Can you tell me why is a censored word? I have to admit I am curious.

    Is this place ran by aliens, or powered by the screams of children? That would make sense.

    Thanks for the new version. :)

    I haven't had any luck getting any further with the remote, but I have hit a new snag with rsync.

    Are there any known issues with redirects? That might explain my issue with rsync.

    I have been trying to use this command, but it doesn't generate any redirect output. It works fine otherwise. Just no txt file I can review.

    I use an almost identical command on my dd-wrt router which is acting as a file server for me. I have no issue there.

    rsync -rav --modify-window=300 --progress  --stats --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ > /var/media/8TB_WD2/synclog.txt

    Ignore the period in the word above. For some reason hu man is a censored word on this forum.

    I have tried a few other options that I documented in this other thread, but so far no luck getting redirected output or log files created.

    Help with output redirect please.


    Figured out that I couldn't write a log file or redirect to the external hard drive. If it was sent to /storage/backup it works.

    Does anyone know why I can't write the log file to my external hard drive?

    Any suggestions are welcome. :)

    Just tried both suggestions, and there was no log file created.

    Suggestion #1

    rsync -rav --modify-window=300 --progress --log-file=/var/media/8TB_WD2/synclog.txt --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ &>/dev/null

    Suggestion #2

    rsync -rav --modify-window=300 --progress --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ 2>&1 | tee /var/media/8TB_WD2/synclog.txt

    Terminal output:

    ^CLibreELEC:/var/media/8TB_WD2/Media/Movies # rsync -rav --modify-window=300 --progress --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ 2>&1 | tee /var/media/8TB_WD2/synclog.txt
    sending incremental file list
    deleting synclog.txt
    Media/Epsoides/Hogans Heroes/Hogans.Heroes.S1.DVDRip/
    Media/Epsoides/Hogans Heroes/Hogans.Heroes.S1.DVDRip/Hogans.Heroes.1x32.dvdrip.xvid-BBBear_TMindTV.avi
            314.32M 100%   50.49MB/s    0:00:05 (xfr#1, ir-chk=1013/63529)

    Second SSH to check for log file:

    Am I missing something, or is the system not working right?

    I feel like an idiot. I can't see any reason why all of these would fail to generate some kind of output file.

    I did just notice a .fuse_hidden0000f49000000005 file being created when I kick off these commands.

    I am assuming that is a temp file for rsync, but it is the only thing at the root of that drive which is new.

    It also vanishes when I kill the rsync command.

    Thanks for the suggestions. :)

    Maybe I need to get out my voodoo chicken bones and grass skirt...

    Could be running low on magic smoke.

    It would be nice to get the output in the terminal and the log file, but I can live with not having it in the terminal.

    Thanks for the suggestion, but no luck. The rsync starts, but there is no log file.

    I am using almost identical code on my dd-wrt router, and it works there as expected.

    rsync -rav --modify-window=300 --progress  --stats --force --delete /tmp/mnt/8TB_USB/ /tmp/mnt/5TB_Seagate_USB/ > /tmp/mnt/8TB_USB/rsync_Status.txt

    I have loaded my Rock64 with LibreElec, and I am also using it as my Samba server.

    I want to run a sync between the two USB hard drives I have attached to maintain a backup of my media.

    I can't seem to get the command quite right. I want to copy the data, and redirect the output to a text file so I can see what it is doing later on.

    I do want it to overwrite the old log file.

    This is the command I am trying to use:

    rsync -rav --modify-window=300 --homan-readable --progress  --stats --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ |& tee /var/media/8TB_WD2/synclog.txt 
    -sh: syntax error: unexpected "&"

    I have also tried > but I get no log file output at all.

    rsync -rav --modify-window=300 --homan-readable --progress  --stats --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/ > /var/media/8TB_WD2/synclog.txt 

    If I cut off the redirect, it outputs to bash exactly what I would expect, but I can't get it to output to a log file.

    Works with output to bash ->

    rsync -rav --modify-window=300 --homan-readable --progress  --stats --force --delete /var/media/8TB_WD/ /var/media/8TB_WD2/

    Can someone make a suggestion. I am probably missing something crazy simple, but just can't see it.

    PS for some reason the word is censored here. Please replace the homan with when reading my code above.