Posts by trogggy


    You need to post a debug log of a library scan, otherwise it's just guesswork.

    Thanks for that - you've given me a new angle to think about it from. When I first connected the Harmony on default settings the repeats were a pain - that's the main thing I've been trying to fix, preferably without hacks in keyboard.xml or Harmony settings. It's still a work in progress.


    If you only quote me once you'll have 1 less reply to make.

    Can you link to the people with the same issue? I don't remember reading people had black screens in android, but it's getting to be a long thread.


    Thanks, but that didn't work. I need a OS sollution as the key is never getting to Kodi because the system shuts down whenever this key is pressed.


    It 100% does work. I have a pi3 and the same remote (amongst many others).
    Just tested on a fresh install of libreelec 7.02.
    Without remote.xml power button powers off.

    Code
    06:14:03 1131.469360 T:1962504192   DEBUG: LIRC: Update - NEW at 50610:74 0 KEY_POWER devinput (KEY_POWER)
    06:14:03 1131.469604 T:1962504192   DEBUG: OnKey: rewind (0xc4) pressed, action is ShutDown()

    With remote.xml it does nothing.

    Code
    06:03:28 496.663666 T:1962446848   DEBUG: LIRC: Update - NEW at 78154:74 0 KEY_POWER devinput (KEY_POWER)
    06:03:28 496.663910 T:1962446848   DEBUG: OnKey: rewind (0xc4) pressed, action is noop
    06:03:28 496.703552 T:1962446848   DEBUG: LIRC: Update - NEW at 78194:74 0 KEY_POWER_UP devinput (KEY_POWER_UP)
    06:03:32 500.487885 T:1962446848   DEBUG: LIRC: Update - NEW at 81978:74 0 KEY_POWER devinput (KEY_POWER)
    06:03:32 500.488129 T:1962446848   DEBUG: OnKey: rewind (0xc4) pressed, action is noop
    06:03:32 500.528290 T:1962446848   DEBUG: LIRC: Update - NEW at 82019:74 0 KEY_POWER_UP devinput (KEY_POWER_UP)


    Are you sure you've put the remote.xml in the right place (/storage/.kodi/userdata/keymaps)?
    Sure you've not made remote.xml.txt?

    Your ubuntu wiki info isn't relevant - the power button in libreelec is mapped in remote.xml, you can set it to do nothing (<noop>) or to do something else, just like any other button.



    [hr]

    I exchanged that auto file and did the toothpick reboot, but it did not help either.

    That is really frustrating and I just have only Full HD devices. :\

    Quote


    Would help, if I had visual access to the Android part, but that
    is the same situation like with Libreelec right now.


    As I read it swapping the aml_autoscript for the older one will only help if your android install is working and you set the resolution there - so it's the same when libreelec boots from sd.
    Are you saying your android install was working before you toothpicked but now it's not?

    Yep, I'm quite happy editing the keys in remote.conf and keyboard.xml - I do it manually rather than using keymap editor, just get the keycodes from the kodi log and linux keycodes from t'internet. I try to keep the remote behaviour as consistent as I can across devices.

    What I'm trying to do here is to get the Harmony keypresses working as well as possible... there are settings in the harmony software (inter-key delay, key repeat delay, interdevice delay) that can be tweaked. And then there's the stuff in my first post.I've looked at more than a few remote.conf files, and the values for release_delay, repeat_peroid and repeat_delay are often different.
    Which is why I'm wondering what each one does....

    Ta for the input anyhow.

    Alright, \\libreelec gave me this:

    A directory with a lot of folders/directories named Backup, ConfigFiles, Downloads, ..., Userdata and Videos.

    I guess, I am having this stupid issue with the resolution. Can I SSH or anything else to it and change it in the settings menu, if there is one?


    Good news is your toothpick worked and you have libreelec booting - yay.

    I haven't a clue how to change the res. There have been a fair few posts with similar issues though, I think - so if you root around you'll hopefully find what kszaq had to say about fixing it.

    After the procedure the card has only 511 mb as size and there are those files, that have been mentioned in the post.

    Then I turn off the box, insert the SD, click the reset switch, hold it, give power, wait ... for over two minutes blank screen, but LEDs of the box are there (blue) and of the Ethernet cable, as well.

    Doesn't sound like an sd-card problem, the 511MB is right...

    In the absence of kszaq - who'll probably give you the right answer - is it possible libreelec is running with a blank screen? Might be worth ruling that out - it's a long shot but...
    Try sticking

    Quote


    \\libreelec


    or '\\192.168.x.xx' (with the ackshewal IP of your box, obviously) in the windows explorer address bar on a pc. Anything?


    The card I have treated with Rufus and I dragged/dropped
    the newest img.gz into it (Rufus). The formatting went
    well, I guess.


    Just to check... what exactly do you have in the root of your sd card?
    From the install guide:

    Quote


    As a result, you should have 3 system files: aml_autoscript, kernel.img and SYSTEM and 2 md5 files on your SD card.


    I used win32diskimager, but the result should be the same.

    I've been messing with a remote.conf for a pivos xios ds, to use with a Harmony and give me lots of buttons on my minimxiii.
    I have something that's okay, with a lot of trial and error, but hoping someone can explain what I'm actually changing.

    In remote.conf are the following:

    Quote


    repeat_delay =

    repeat_peroid =

    release_delay =


    For release delay I've found:

    Quote


    unit:ms.release will report from kernel to user layer after this period of time from press or repeat triggered.


    I'm hoping someone can explain in (reasonably) simple terms what each of the settings does.

    Ta in advance (or not! )

    Have you tried the toothpick method?
    On my box (minimxiii) there's a hole in the bottom - stick something in there and you can feel the switch.
    I believe the switch is accessed via the av port on your box.

    Insert toothpick
    plug in
    wait a bit*
    remove toothpick.

    *Exactly a bit - no more, no less. Gotta be precise.

    Code
    <keymap>
      <global>
        <remote>
          <power>noop</power>
        </remote>
      </global>
    </keymap>


    The above in remote.xml (/storage/.kodi/userdata/keymaps/remote.xml) should work.
    Unless the remote's recognized as a keyboard in which case change 'remote' for <keyboard>.

    Logfiles?