Posts by trogggy

  • Remote control basics

    Okay, can you do the following...
    Fire up kodi and enable debug logging.
    Open the log on your pc (/storage/.kodi/temp/kodi.log)
    For each of the 3 buttons:
    1. Press the button.
    2. Refresh / reload the log straight away.
    3. Look at the last few lines of the log - there should be a couple of lines describing what you've done (maybe even the last 2 if you're quick and the button's not doing much).
    So you end up with something like:

    Quote


    Exit button: (that's not in the log!!!)
    Keyboard: scancode: 0x0e, sym: 0x0008, unicode: 0x0008, modifier: 0x0
    DEBUG: OnKey: backspace (0xf008) pressed, action is Back


    for each of the 3.
    Post up the results.

  • Remote control basics

    Can you paste your remote.conf into a post here - it's hard to work out what's going on without looking at it, but from what you say you'll need to change some values in there (yes, those linux keycodes).
    Plus an example of a remote button that doesn't work at all, and a remote button that works but doesn't do what you want (including what you'd like it to do in both cases).

  • Remote control basics

    Quote from Virtex



    [hr]
    Just a little step forward. The journalctl output states:

    press ircode = 0x16
    scancode = 0x0067

    I understud this is the corrispondent to remote.conf mapping, but in remote.conf are mapped the ircodes to the decimal scancodes (0x0067 = 103) so 0x16 -> 103.
    Now I have to understand where is done the association of scancode 103 to KODI action ...

    The only 2 places I've looked at for amremote are the remote.conf and the kodi log - anything else I've no clue.
    But that seems to be all that's needed. Remote.conf gives you as a minimum the IR keycode and linux keycode. Checking kodi.log in real time lets you link those to key id and kodi action.
    That 103 (guessing it's an 'up' signal?) is a linux keycode - there's a list in the first post of my linked thread.
    You can change the linux keycodes in remote.conf and that will change the key id / action seen in kodi.log.

  • Remote control basics

    Easy way - fire up the keymap editor from the official repo, press a button that doesn't work and map it to the function you want. I don't like it for a few reasons but it will do the job.
    What I do:
    enable debug logging, bring the log up on my pc, press a key, refresh the log. Read the last couple of lines, it tells you the code (hex) and the action linked to it. List the buttons / codes / actions. Then either edit remote.conf directly (to send different codes) or write a keymap (.xml file) and stick it in .kodi/userdata/keymaps (which is how the keymap editor addon does its stuff).
    If you click the link in my sig there's a bit more detail.

  • Guide - using a Harmony with amlogic devices

    Quote from honolulu1


    It took me a while to figure that gen.xml out but now I understand how it works an what kodis keymap editor does to it. You where right, it's realy confusing but I ended up using it anyway and now I've mapped everything I wanted.
    I don't need more buttons than that but It might be helpfull to others if you could offer a code for another remote control than the pivos xios ds that has even more buttons. The pivos has 42 I think. Including the favourites buttons 1-5 on my Harmony 350 I could theoretically map 48 buttons.
    The one or other person might want to map them all. Could be a nice addition to this tutorial.
    Think about it.


    Glad it all worked.
    I used this remote.conf because it had as many or more buttons than any other I looked at. If someone suggests one with more I'm happy to check it. Tbh though this is probably just a temporary solution - as it looks as though amlogic boxes will probably end up using lirc.
    Expanding gen.xml (as in a few posts up) makes it a lot easier to follow btw - and it still works.

  • Libreelec settings don't display properly...

    Quote from Jester


    Being the current Amber skin dev, I have to agree with this issue,

    It seems libreelec add-on was written only for estuary and is using estuary font names and estuary only included background names, this means it will break on most (probably all) other skins. see -> Merge pull request #20 from lrusak/estuary · LibreELEC/service.libreelec.settings@7b04bb8 · GitHub

    I find it a bit short sighted to say "it works with estuary, so it must be a skin issue" when its actually an add-on "issue", which basically forces ALL skin devs to put changes in their skin just to support this add-on, which to me is going a bit far....

    Just my 2 cents...


    That's the thing. It was written for estuary but there's a fallback background. Which has been missed out - stick it in the libreelec settings folder and it works just fine.
    The skin dev I raised this with was much less polite about it than you. ;)

  • [8.0.2e] LibreELEC 8.0 for S905/S905X

    Quote from infoalter


    Fresh install of 2016-12-01, TVHeadend backend (service) addon installed fine, USB receiver working fine, but, TVHeadend frontend plugin (client) refuses to install. Dependencies not met
    Is there a trick to install it?

    PS First impressions: VERY smooth operation! Cheers! :)


    Are you trying to install from the repo (which won't work) or from kszaq's link a few posts back?

  • Creating my own Kodi build

    Quote from Bowie350z


    First time doing my Kodi build using LibreElec. I have done it before on an Android box using File Manager HD to access the storage card to add picture files . What's the easies way to

    do this using LibreElec.

    thank you


    If you mean customising kodi by sticking your own stuff in the kodi folder the easiest way is to use smb / samba. That way you can copy and paste directly in windows explorer.
    Wiki guide: Accessing LibreELEC - LibreELEC
    To access the whole kodi folder / whole storage partition:
    LibreELEC

  • Guide - using a Harmony with amlogic devices

    Quote from honolulu1


    Where exactly do I paste that first code?
    In the gen.xml where I previously changed fullscreen to back?


    You can add it to that or stick a new .xml file next to it. If you intend to use keymap editor again it's better to add it to that, because it has the nasty habit of nuking any other custom keymaps if you so much as look at it.
    Any .xml file in that folder is loaded to keymaps (in alphabetical order, so if there's a conflict the last one loaded wins).
    Edit: you can't just paste the code into gen.xml - you have to paste into the relevant sections - ie 1 line into the global section, 1 line into fullscreenvideo. Or add via the gui - can't help with that but it's certainly the recommended way.

  • Guide - using a Harmony with amlogic devices

    Quote from honolulu1


    Yep everything is fine now. Thanks again.
    I just have some problems with mapping the home button, the equivalent to pressing "esc" on a keyboard. In your KODI map it resembles pressing "z" I think.
    How do I change the "z" to "esc"? Because I can't find a home screen command in the keymap editor addon.


    IIRC that key was originally mapped to KEY_HOME / 102, which wasn't recognised as a command in libreelec. I mapped it to z to use as a utility key, then decided to use that to jump to the home screen. So in my keymaps I have:


    If you want it to point to escape just edit the relevant line in remote.conf - the replacement would be:

    Code
    0x95    1      ; ESC          61467           escape


    But you'll still face the same issue - that key maps to back / fullscreen rather than ActivateWindow(Home).

  • Guide - using a Harmony with amlogic devices

    Quote from honolulu1


    <keymap><home><keyboard><key id="61489">activatewindow(videos,tvshowtitles )</key></keyboard></home><global><keyboard><key id="61656">contextmenu</key><key id="61623">play</key><key id="61623">pause</key><key id="61623">playpause</key><key id="61660">stop</key><key id="61625">fastforward</key><key id="61624">rewind</key><key id="61585">osd</key><key id="61448">fullscreen</key><key id="61585">info</key></keyboard></global><osdvideosettings><keyboard><key id="61585">info</key></keyboard></osdvideosettings><fullscreenvideo><keyboard><key id="61585">info</key></keyboard></fullscreenvideo></keymap>


    Now do I just replace "61448">fullscreen< with "61448">back< or "61448>backspace< ?


    I take it that's a file called gen.xml
    Bloody keymap editor - it's always unreadable.
    So what you've actually configured there is:


    Change <key id="61448">fullscreen</key> to
    <key id="61448">Back</key>
    and re-start.
    That should sort it.
    Actually just deleting that entry should do the same thing, as it should be mapped to 'Back' in the default keymap.

    User error - you broke it. ;)
    Let me know if it works / not - but it should be fine now. Phew.