Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Please Build MCEUSB driver into R89 111k kernels or enable the IR transceiver port to understand MCE remote.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Please Build MCEUSB driver into R89 111k kernels or enable the IR transceiver port to understand MCE remote.

    Could someone knowledgeable in building drivers and updates be willing to build and include the MCEUSB USB Transceiver driver so my eHome IR device will register as an Input?

    Or - Include the IR USERCODE/SCANCODE info for the MCE remote & Popcorn hour style remote?

    One of the most glaring omissions from every RK89 build (like BeeLink R89 or Tronsmart R28) is any ability to ADD or Modify the acceptable IR commands through remote.conf files. These builds don't even include the necessary binaries like remotecfg and the like to allow us to modify ourselves.

    It appears only the Amlogic builds include the ability to add other remotes. (See Johan's Logitech Harmony remote post for how it's done for those boxes) How can we do this on R89/R28 type boxes?

    • Is there a remotecfg equivalent built-in to the R89/R28 images?

    #2
    I moved you thread to this sub-forum so maybe oman will have a look at it...
    RK3288 Devices
    - Overview BOX (LINK !)
    - Overview STICK (Dongle) (LINK !)

    MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
    UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
    Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
    Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

    RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
    Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

    Comment


      #3
      One Harmony to rule them all..

      Thank's No Spam.

      To clarify for those joining- I'm not looking for an IR Blaster app (that runs on another android phone) to control my TV box.

      The Harmony software lets you emulate any remote and emulating a MCE remote gets you the largest selection of map-able buttons. But, the latest Beelink R89 rom and others only have support for a very limited set of unknown remotes with an even less than appealing list of usable buttons.

      Apparently you have to BUILD the remote support into the kernel/drivers/input/remotectl/rk_pwm_remotectl.c (see Firefly page) or via some other method. If the remote support was controllable in the same way AMLOGIC build is doing it, then I could just create a remote.conf file and be done with it. But, no..

      Comment


        #4
        Ok, if there exist something which only have to be include (http://wiki.t-firefly.com/index.php/...y-RK3288/IR/en), maybe also post at


        with a reverence to this thread...
        RK3288 Devices
        - Overview BOX (LINK !)
        - Overview STICK (Dongle) (LINK !)

        MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
        UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
        Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
        Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

        RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
        Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

        Comment


          #5
          Having read your thread and using some of the info you supplied I decided to mess about a bit and see if I could get anywhere. Do this completely at your own risk but I have found renaming(not deleting just in case you need it) ff680000_pwm.kl (to old so its not used) within the system\usr\keylayout folder disables the ability to use the mouse button (which I will never user) on my harmony (configured as a tronsmart s89) but enables 1,2,3,4,5,6,7,8,9,0 and .+ while this is not all the buttons (fast forward etc still don't work) for me personally this will allow me enough buttons to configure keyboard.xml within xbmc and enjoy almost the same control I have using my htpc. I have literally just figured this out and must sleep but thought I would throw it into the hat as a work around at least for the time being and will do some more fiddling tomorrow. As I mentioned I take no responsibility for any issues that may occur.
          I also noticed changing some of the values in the ff680000_pwm.kl file can also re-configure some buttons but there are less buttons to change - for example I managed to get volume up to insert a 1 instead. Don't this it would matter what rom but using Wasser 2.0.3

          Hope this helps

          Edit 1: After changing a couple of words in the generic.kl file I have re-enabled mouse so now have all the numbers aswell as the mouse and home buttons working
          Last edited by reeso3000; 02 January 2015, 06:33.

          Comment


            #6
            Sorry for the double post check this out :-



            Hope it helps

            Comment


              #7
              As you can see from http://wiki.t-firefly.com/index.php/Firefly-RK3288/IR/en-->

              The most important things IR remote can be recognized is:

              1. .usercode=0xff00,/* need to get the usercode in next step */

              2. Left side in the array is the Code Value from IR remote-->

              staticstruct rkxx_remote_key_table remote_key_table_r66[12]={ {0xeb, KEY_POWER}, // Power
              // Control
              {0xa3, 250}, // Settings
              {0xec, KEY_MENU}, // Menu
              {0xfc, KEY_UP}, // Up
              {0xfd, KEY_DOWN}, // Down
              {0xf1, KEY_LEFT}, // Left
              {0xe5, KEY_RIGHT}, // Right
              {0xf8, KEY_REPLY}, // Ok
              {0xb7, KEY_HOME}, // Home
              {0xfe, KEY_BACK}, // Back
              // Vol
              {0xa7, KEY_VOLUMEDOWN}, // Vol-
              {0xf4, KEY_VOLUMEUP}, // Vol+
              };


              So you cant modify any custom codes other than rewriting
              kernel/drivers/input/remotectl/rk_pwm_remotectl.c
              Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

              Comment


                #8
                This is why the RK build tree sucks

                Hi Oman,

                This is exactly why it would be great if the MCEUSB transceiver driver could be built (link here). That way I can use it as the IR receiver and not the blasted prebuilt kernel. I just don't know how to build drivers... + kernel., etc.

                Comment


                  #9
                  Originally posted by sillykeith View Post
                  Hi Oman,

                  This is exactly why it would be great if the MCEUSB transceiver driver could be built (link here). That way I can use it as the IR receiver and not the blasted prebuilt kernel. I just don't know how to build drivers... + kernel., etc.
                  I see...So you need buy one MCEUSB transceiver..

                  We'll include it in next ROM.
                  Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

                  Comment


                    #10
                    Please Build MCEUSB driver into R89 111k kernels or enable the IR transceiver port to understand MCE remote.

                    Originally posted by oman View Post
                    As you can see from http://wiki.t-firefly.com/index.php/Firefly-RK3288/IR/en-->

                    The most important things IR remote can be recognized is:

                    1. .usercode=0xff00,/* need to get the usercode in next step */

                    2. Left side in the array is the Code Value from IR remote-->

                    staticstruct rkxx_remote_key_table remote_key_table_r66[12]={ {0xeb, KEY_POWER}, // Power
                    // Control
                    {0xa3, 250}, // Settings
                    {0xec, KEY_MENU}, // Menu
                    {0xfc, KEY_UP}, // Up
                    {0xfd, KEY_DOWN}, // Down
                    {0xf1, KEY_LEFT}, // Left
                    {0xe5, KEY_RIGHT}, // Right
                    {0xf8, KEY_REPLY}, // Ok
                    {0xb7, KEY_HOME}, // Home
                    {0xfe, KEY_BACK}, // Back
                    // Vol
                    {0xa7, KEY_VOLUMEDOWN}, // Vol-
                    {0xf4, KEY_VOLUMEUP}, // Vol+
                    };


                    So you cant modify any custom codes other than rewriting
                    kernel/drivers/input/remotectl/rk_pwm_remotectl.c
                    It wouldn't be too hard at add code to read values from a file. I could do the code to do that if you like

                    Comment


                      #11
                      Enabling Remote.conf in R89 builds.

                      This would be great.

                      It would be even better if the file name could be remote.conf and also mirror same format/structure as much as possible to how remote.conf is implemented elsewhere.

                      Comment

                      Working...
                      X