Posts by trogggy


    @troggy On some boxes I've seen u-boot adapting to power key code from userspace somehow and I was able to power on the box by any remote from u-boot sleep. Unfortunately in most of the cases you can only power on by original remote, like you said.

    Interesting. I've really struggled to find any documentation on how amremote actually works, so lots of trial and error going on here. I have a pivos Harmony profile working pretty well, still struggling a bit with key repeats - I can get around those by mapping <longpress> to the same function as a single press in keyboard.xml, but it's a big faff.

    I have Minix A2 lite remote for Beelink MiniMXIII box. Power on from suspend is not working with A2 lite. If it is possible can you give me some advice how to change remote.conf to make power on with a2 lite working? Thank you!


    As I understand it the only way you can power-on is to use the original remote - nothing to do with remote.conf.
    If you're using a Harmony or other programmable remote you can copy the power signal from the original (which is what I do).
    Might be wrong though - I'm still trying to get to grips with amremote.

    No idea, as it sounds skin-specific and I only used Estuary for about 5 minutes. It would be worth asking in the skin mod thread over on the kodi forum.
    I'm presuming if you go to programs from the home screen and click on Emulation Station (which I know nothing about) it starts correctly. In my settings.xml (for xonfluence) I see lines like:
    <setting id="UserSubOne.1.Path" type="string">RunAddon(plugin.video.hdtrailers_net)</setting>
    You should presumably end up with something similar for ES, but how you add it - other than by editing the .xml - well, as I said, no idea.


    one question though: if i'm understanding right, only 0-255 (254) are valid key codes. But in my original remote.conf i have entries like

    0x16 396

    This is the "RED BUTTON" on the remote, scancode results in 0x18c (which is 396 in decimal). Does this mean it is assigned like this:
    #define KEY_MEMO 0x18c /* Media Select Messages */ (which is a "button" assignment) and therefore cannot be recognised properly by kodi as it only reads keystrokes?

    And another question: How can i define "long-press actions" in remote.conf - simply add another value to the same ircode but for repeat action? (repeat_key_begin)


    Say you wanted to map that red button to 'up'.

    In your remote.conf:


    Change the '396' to the linux keycode for 'up'.
    That's in the table mmpp linked to:


    So you want to replace the line:
    0x16 396
    with
    0x16 103

    In simple terms ('cos I have a simple understanding of this!) the first column of numbers in your remote.conf (the ones in hex) is a list of the remote keys, the second column is the list of what they're read as.


    Long presses are mapped within kodi, not in remote.conf.

    So my keyboard.xml (/storage/.kodi/userdata/keymaps/keymap.xml) at the moment (it's very much a WIP) looks like this:


    As you can see I've used 'longpress' to perform exactly the same action as a normal press - that's to stop key repeats, something I should probably sort out properly. But you can map whatever action you want with the mod="longpress".

    There have been a few posts here from people trying to register and struggling with "5 minus 5" or something similar. I suggested t'other night that someone check out kszaq's threads here and also that site if they were looking for an s905 device / image / information - and they came across the same issue. It should now work.
    That is all.

    Edit: No it isn't! Oops!
    index.php

    Thanks a lot. I'm sorry to say there is no description of the package in Addons/Program Addons, only "A bundle of network tools and programs". Unlike System Tools, where there is a listing of the tools.

    Nevertheless I've got it


    Took me a while to find it too.


    Hi guys,

    I ordered a MXQ Pro 4K to replace my RPi with Openelec. The problem i had with the RPi is that it corrupts my SD card very often. What is the chance that this will also happen to an Android box with Libreelec installed on a SD card?

    Is it maybe better to install Libreelec to NAND after first trying the SD card method?


    I can't remember the last time I had sd card corruption on the pi - it was well over a year ago, and I have at least a couple running 24 / 7. So 'very often' sounds like something's wrong.
    No problems so far using an sd card on a mini mxiii. It's early days - but if you have a backup it's no big deal.

    Tried with on my minimxiii  with 7.0.2.005 on sd card:

    @kostaman Have you found a way to overcome the lack of options on the MiniMX remote?
    I use a Harmony remote to control these boxes, but since there are very few buttons on the MiniMX remote, I have lost a lot of useful functions with the Harmony remote.

    Also Bluetooth is not recognised - Is that what you have found?

    Stick it (the original remote) in a drawer, delete it from your Harmony and use a different remote.conf with more options.
    I'm using a minimxiii with a remote.conf from a pivos xios ds - there are about 50 discrete inputs in the Harmony profile, so comparable to an mce. It's not perfect - needs some tweaking, which I'm slowly doing - but I have lots of buttons.
    This is where I'm at so far - I've stuck the key id's for existing buttons in there to help me map my keyboard.xml.

    The only problem I'm having now is key repeats, which can be worked around in keyboard.xml by giving the same function to <longpress>.
    If you change your remote then you'll need to learn the power-on command from your original, as it's hard-coded to the box.


    Sounds like a power draw issue. Powered hub is the way to go, especially if you have multiple drives.


    MyBook's a powered drive (3.5") if I'm not mistaken (possible).
    I have no problem running a 2TB mypassport from the pi (with a decent 2A power supply and the config.txt change). I think IIRC mine draws about 700mA max.
    Edit: not saying it's not likely related to power, just prob'ly not for the mybook.