Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

KIII AMLOGIC S905 Not picking up usb controllers (works with others)

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

    KIII AMLOGIC S905 Not picking up usb controllers (works with others)

    Hello guys, I am wondering if i can get some help, recently i bought 2 snes usb controllers from ****. I tried both on my KIII and neither work at all. To rule out controller fualts i tried them on my m8s and they work fine and tried both on my GS5 and Nexus 6, both work great. can someone help me in figuring out if they will work or why the dont? is there something i can install or edit to have the controllers work? I would appreciate some help or info. Thanks alot


    ======

    Seems that the firmware or kernal doesnt have all controller modules installed. Can someone help me with the steps to installing extra ko files? Im knew to all this
    Last edited by cmac86; 23 December 2016, 03:23.

    #2
    Hey,

    See my post here: http://freaktab.com/forum/developmen...704#post601704

    Let me know if you need any extra help.

    Comment


      #3
      Originally posted by darro87 View Post
      Hey,

      See my post here: http://freaktab.com/forum/developmen...704#post601704

      Let me know if you need any extra help.
      Hey Darro thanks for your reply mate. I actually came across your post and couldn't figure out how to get going, I figured that the controllers I have aren't reconized at all with my KIII, I tried some input tests and nothing appears via button presses, This leads me to think that the controllers are not usable. I will try again with your steps to see if i can get any farther. I appreciate your help mate and if I get stuck Ill let you know. Good man

      Comment


        #4
        Originally posted by cmac86 View Post

        Hey Darro thanks for your reply mate. I actually came across your post and couldn't figure out how to get going, I figured that the controllers I have aren't reconized at all with my KIII, I tried some input tests and nothing appears via button presses, This leads me to think that the controllers are not usable. I will try again with your steps to see if i can get any farther. I appreciate your help mate and if I get stuck Ill let you know. Good man
        No problem. Hope you get through!

        Once you have the ko and keylayout files for the controllers, everything else should be a breeze.

        Comment


          #5
          Originally posted by darro87 View Post

          No problem. Hope you get through!

          Once you have the ko and keylayout files for the controllers, everything else should be a breeze.
          Hey mate and thanks for the reply. I tried following your steps and kept getting an error that the file location doesnt exist or something along those lines. The controller works with my GS5 and Samsung tablet. So to figure out how to get those files that will work with the KIII. Much appreciated.

          Comment


            #6
            Originally posted by cmac86 View Post

            Hey mate and thanks for the reply. I tried following your steps and kept getting an error that the file location doesnt exist or something along those lines. The controller works with my GS5 and Samsung tablet. So to figure out how to get those files that will work with the KIII. Much appreciated.
            Hey, at what stage are you getting this error? Which file are you working with?

            The steps I have there are for a specific controller, a PS3 controller, and the files attached to that post are specifically for this, so you'll have to get the files for your controller, and adjust the file names when using the terminal commands. Also, the commands assume that the files are stored in the root of your internal memory, so make sure that's where your files are, or adjust the paths in the commands to suit yours.

            If you walk me through where you get stuck I'll see how best I can guide you.

            Comment


              #7
              I'm sorry mate that's obviously where I'm going wrong from the start. I don't have the files for my controller. As I said it's a cheap usb snes dupe. How would I go about getting such files? If my galaxy s5 reconises the controller does that mean the file I need would be in my file system on s5? I appreciate you trying to help me. Thanks

              Comment


                #8
                Ah, now I understand.

                First thing, follow this guide so we know what device it is specifically, then we'll figure out what ko and kl files you'll need for it. You can copy-paste or type the values you get here.

                Comment


                  #9
                  Hey Darro and and once again mate thanks for the help. i really appreciate it, So both controllers have the same id's and the id is

                  HID\VID_0079 & PID_0011. What is done from here? thanks alot mate. your a gent

                  just an edit, here is another id for a cheap xbox one controller, wired. USB\VID_0E6F & PID_0158. Not sure if they work tho.

                  Comment


                    #10
                    Hey.

                    Sorry for the delay, took some time to research.

                    So I think I narrowed that gamepad down to a generic 'DragonRise Inc. Gamepad'...which uses the ko file 'hid-dr.ko' which I have attached. It's compiled for S905, so it should work fine for you. The keylayout file would be harder to get, so we can ignore that for now, as it'll most likely use the generic built in keylayout file already present in the firmware. You may just have to remap the controls for whatever emulators/apps you plan on using it on, or we can try some more advanced stuff later to help build the keylayout file ourselves.

                    To get this up and running, you can use the post I first sent to you, but for quick reference, I'll restate the key points here, adjusted to suit this file:

                    Insert Module into Kernel
                    From the terminal app, run:

                    su
                    cd /storage/emulated/legacy/
                    insmod hid-dr.ko

                    The above assumes that you have the file in your internal memory storage root directory; if not, you will need to 'cd' into where you have the file.
                    If you reboot your box, you will need to perform the 'Insert Module' step again to re-enable the controller. A fix for this is to download Script Manager - SManager and use it to create a script and run it on boot.

                    Hope you get this to work. If it doesn't, we can try other ko files, but I'm pretty sure that's the correct one based on the vid and pid you gave.

                    Let me know how it goes.

                    Oh, for the cheap xbox one controller, you may need to install 'ff-memless.ko' and 'xpad.ko' (in that order) in much the same way as above. I attached these as well so you can give it a go.

                    darro87
                    Attached Files

                    Comment


                      #11
                      Originally posted by darro87 View Post
                      Hey.

                      Sorry for the delay, took some time to research.

                      So I think I narrowed that gamepad down to a generic 'DragonRise Inc. Gamepad'...which uses the ko file 'hid-dr.ko' which I have attached. It's compiled for S905, so it should work fine for you. The keylayout file would be harder to get, so we can ignore that for now, as it'll most likely use the generic built in keylayout file already present in the firmware. You may just have to remap the controls for whatever emulators/apps you plan on using it on, or we can try some more advanced stuff later to help build the keylayout file ourselves.

                      To get this up and running, you can use the post I first sent to you, but for quick reference, I'll restate the key points here, adjusted to suit this file:

                      Insert Module into Kernel
                      From the terminal app, run:

                      su
                      cd /storage/emulated/legacy/
                      insmod hid-dr.ko

                      The above assumes that you have the file in your internal memory storage root directory; if not, you will need to 'cd' into where you have the file.
                      If you reboot your box, you will need to perform the 'Insert Module' step again to re-enable the controller. A fix for this is to download Script Manager - SManager and use it to create a script and run it on boot.

                      Hope you get this to work. If it doesn't, we can try other ko files, but I'm pretty sure that's the correct one based on the vid and pid you gave.

                      Let me know how it goes.

                      Oh, for the cheap xbox one controller, you may need to install 'ff-memless.ko' and 'xpad.ko' (in that order) in much the same way as above. I attached these as well so you can give it a go.

                      darro87
                      Our a gent mate. I'm going to give this a go now. See how I how I get on. Cheers pal.

                      Comment


                        #12
                        Originally posted by darro87 View Post
                        Hey.

                        Sorry for the delay, took some time to research.

                        So I think I narrowed that gamepad down to a generic 'DragonRise Inc. Gamepad'...which uses the ko file 'hid-dr.ko' which I have attached. It's compiled for S905, so it should work fine for you. The keylayout file would be harder to get, so we can ignore that for now, as it'll most likely use the generic built in keylayout file already present in the firmware. You may just have to remap the controls for whatever emulators/apps you plan on using it on, or we can try some more advanced stuff later to help build the keylayout file ourselves.

                        To get this up and running, you can use the post I first sent to you, but for quick reference, I'll restate the key points here, adjusted to suit this file:

                        Insert Module into Kernel
                        From the terminal app, run:

                        su
                        cd /storage/emulated/legacy/
                        insmod hid-dr.ko

                        The above assumes that you have the file in your internal memory storage root directory; if not, you will need to 'cd' into where you have the file.
                        If you reboot your box, you will need to perform the 'Insert Module' step again to re-enable the controller. A fix for this is to download Script Manager - SManager and use it to create a script and run it on boot.

                        Hope you get this to work. If it doesn't, we can try other ko files, but I'm pretty sure that's the correct one based on the vid and pid you gave.

                        Let me know how it goes.

                        Oh, for the cheap xbox one controller, you may need to install 'ff-memless.ko' and 'xpad.ko' (in that order) in much the same way as above. I attached these as well so you can give it a go.

                        darro87
                        ran the process and get an error hid-dr.ko failed (operation not permitted) any ideas mate?

                        I made sure that i had read write permissions for that area. Not sure if Its correct tho.
                        mount -o remount,rw /storage/emulated/legacy/

                        All seems to be correct. I made the mistake of forgetting to add su in terminal. But now instead of operation not permitted I get failed (no such file or directory)
                        Last edited by cmac86; 06 January 2017, 15:30.

                        Comment


                          #13
                          Can u do a 'ls' command after you 'cd' into the directory? You should see the file listed there with all the other folders in the root of your storage once u copy it in the correct place. Let me know what you get.

                          EDIT: My bad, the 'hid-dr.ko' file depends on the 'ff-memless.ko' file as well..it's in the 2nd zip file I gave you. Once you insmod the ff-memless file before the hid-dr file, it should work. Let me know.
                          Last edited by darro87; 06 January 2017, 16:43.

                          Comment


                            #14
                            Originally posted by darro87 View Post
                            Can u do a 'ls' command after you 'cd' into the directory? You should see the file listed there with all the other folders in the root of your storage once u copy it in the correct place. Let me know what you get.

                            EDIT: My bad, the 'hid-dr.ko' file depends on the 'ff-memless.ko' file as well..it's in the 2nd zip file I gave you. Once you insmod the ff-memless file before the hid-dr file, it should work. Let me know.
                            Ahhh you are a legend Darro. a legend mate. controller has input now via android menu and in some cases emulators. A few of the buttons do not work tho. L1, R1, Y and X dont have an input. do you think its maybe because there is no kl file?

                            Ive tested with some controller input key apps and the buttons that i mentioned that dont work never show any information when pushed. they show they are being pressed but no info attached to those buttons. basically tells me these controllers are very very poor haha
                            Last edited by cmac86; 06 January 2017, 20:45.

                            Comment


                              #15
                              Originally posted by cmac86 View Post

                              Ahhh you are a legend Darro. a legend mate. controller has input now via android menu and in some cases emulators. A few of the buttons do not work tho. L1, R1, Y and X dont have an input. do you think its maybe because there is no kl file?

                              Ive tested with some controller input key apps and the buttons that i mentioned that dont work never show any information when pushed. they show they are being pressed but no info attached to those buttons. basically tells me these controllers are very very poor haha
                              Nice, glad you're having progress.

                              It's probably related to the keylayout file indeed.
                              Did you try GamePad Tester? It's supposed to show 'unsupported' keypresses in a text box on the GUI.

                              If it works, and you got the time, use the following to build your kl file:

                              Code:
                              # Copyright (C) 2011 The Android Open Source Project
                              #
                              # Licensed under the Apache License, Version 2.0 (the "License");
                              # you may not use this file except in compliance with the License.
                              # You may obtain a copy of the License at
                              #
                              #      http://www.apache.org/licenses/LICENSE-2.0
                              #
                              # Unless required by applicable law or agreed to in writing, software
                              # distributed under the License is distributed on an "AS IS" BASIS,
                              # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
                              # See the License for the specific language governing permissions and
                              # limitations under the License.
                              
                              #
                              # DragonRise Inc. SNES Pad (i made this up, you can rename it if you have a model number or something, it's just for documentation)
                              #
                              
                              key 0x131    BUTTON_A
                              key 0x132    BUTTON_B
                              key 0x130    BUTTON_X
                              key 0x133    BUTTON_Y
                              key 0x134    BUTTON_L1
                              key 0x135    BUTTON_R1
                              key 0x136    BUTTON_L2
                              key 0x137    BUTTON_R2
                              key 0x138    BUTTON_SELECT
                              key 0x139    BUTTON_START
                              key 0x13a    BUTTON_THUMBL
                              key 0x13b    BUTTON_THUMBR
                              
                              axis 0x00    X
                              axis 0x01    Y
                              axis 0x02    Z
                              axis 0x05    RZ
                              axis 0x10    HAT_X
                              axis 0x11    HAT_Y
                              You'll probably have to remove a few lines, as this follows the typical Xbox controller layout, so a SNES controller will have less buttons. The ABXY buttons are a little different on SNES vs Xbox pads as well, so keep that in mind when mapping.

                              What you'll need to do is update the key 0x### lines with the corresponding code you get from your controller via the input application. Once you're done, you'll need to save the file as:

                              Vendor_0079_Product_0011.kl

                              This matches your controller's IDs and once installed on your box, will automatically be used for your controller.

                              To install it, use the following:

                              Install Keylayout
                              From the terminal app, run:
                              Code:
                              su
                              mount -o remount rw /system
                              cd /storage/emulated/legacy/
                              cp Vendor_0079_Product_0011.kl /system/usr/keylayout
                              chmod 644 /system/usr/keylayout/Vendor_0079_Product_0011.kl
                              reboot
                              This will reboot your box automatically, so just remove the last line if you want to reboot it on your own. The kl file won't work til you do reboot, though, so keep that in mind. Again, this assumes that you copied the kl file to the root of your storage.

                              That should do it. Good luck! Let me know if you bother giving it a go, and if you get through.

                              darro87

                              Comment

                              Working...
                              X