Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Anyone managed to get 'USB/BT Joycenter apk' working on non Touchscreen Devices?

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

    Anyone managed to get 'USB/BT Joycenter apk' working on non Touchscreen Devices?

    Hi all

    I have the MK802 III running 2dark4u/finless 1.7 rom and it works great, but one app that I would really like to get working with it is the 'USB/BT Joycenter app'

    For those who are not familiar with it, you can use the app to map your game controller and use it on touchscreen only games i.e games that don't support ps3/xbox game controllers.

    I believe it was working well on the MK802 II which doesn't have a touch screen but would like to know if anyone has got it working on Mk808,UG802,Mk802 or the MK802 III

    I have tried it but while I can make a driver and map my controller I keep getting the message
    'No touchscreen found! Cannot start Joy2touch server'

    Is it still possible to use this app on a non touchscreen device?

    I have posted on the developers main site as well as I believe this would be an awesome app to have working on are mini android PC's

    Here are some logs, maybe I'm missing something (apart from a real touchscreen lol)

    alogcat
    --------- beginning of /dev/log/system
    W/Vold ( 83): subsystem found in netlink event
    D/Vold ( 83): usb, 1
    D/Vold ( 83): == current usb device: 045E/0288 ===
    W/Vold ( 83): subsystem found in netlink event
    D/Vold ( 83): usb, 1
    W/Vold ( 83): subsystem found in netlink event
    D/Vold ( 83): usb, 1
    D/Vold ( 83): == current usb device: 045E/0289 ===
    W/Vold ( 83): subsystem found in netlink event
    D/Vold ( 83): usb, 1
    E/EventHub( 262): could not get driver version for /dev/input/js0, Invalid argument
    D/EventHub( 262): No input device configuration file found for device 'Microsoft X-Box pad v2 (US)'.
    I/EventHub( 262): New device: id=10, fd=265, path='/dev/input/event4', name='Microsoft X-Box pad v2 (US)', classes=0x80000741, configuration='', keyLayout='/system/usr/keylayout/Vendor_045e_Product_0289.kl', keyCharacterMap='/system/usr/keychars/Vendor_045e_Product_0289.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
    I/InputReader( 262): Device added: id=10, name='Microsoft X-Box pad v2 (US)', sources=0x0100053d



    Joy2Touch Analyzer
    Android: 4.1.1
    SDK: 16
    FINGERPRINT: rk30sdk/rk30sdk/rk30sdk:4.1.1/JRO03H/eng.zw.20121112.153208:eng/test-keys
    BOARD: rk30sdk
    DEVICE: rk30sdk
    ROM: rk30sdk-eng 4.1.1 JRO03H eng.zw.20121112.Finless.1.7
    BRAND: rk30sdk
    MANUFACTURER: rockchip
    MODEL: rk30sdk
    PRODUCT: rk30sdk
    RADIO: unknown
    USB Joystick Center: 6.44
    USB Joystick2Touch: 3.24
    Display Res: 1280x672


    Connected USB Devices:

    1) VendorID: 0xbda | ProductID: 0x8179
    2) VendorID: 0x45e | ProductID: 0x289
    Analyzer Logs



    12-18 15:27:49.318 I/TouchAnalyzer( 3242): -------- Init Real Keyboard --------
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): Open /dev/input/event0 ...
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): Input-Device: rk29-keypad
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): id[ID_PRODUCT] 1
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): id[ID_VENDOR] 1
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): key_bitmask: 16
    12-18 15:27:49.318 I/TouchAnalyzer( 3242): key_bitmask: 128
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): Open /dev/input/event1 ...
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): Input-Device: rkxx-remotectl
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): id[ID_PRODUCT] 1
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): id[ID_VENDOR] 1
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 192
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 22
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 30
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 136
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 64
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 128
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 7
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 2
    12-18 15:27:49.368 I/TouchAnalyzer( 3242): key_bitmask: 1
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Open /dev/input/event2 ...
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Input-Device: SONiX USB Device
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): id[ID_PRODUCT] 29699
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): id[ID_VENDOR] 3141
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): key_bitmask: 254
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Keyboard found!: SONiX USB Device
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------RESULT------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Success (/dev/input/event2)
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Open /dev/input/event0 ...
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Input-Device: rk29-keypad
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): No ABS_MT_SLOT (2f)
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Slots (2f): min=0, max=0
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): No ABS_MT_TRACKING_ID (39)
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Tracking-ID (39): min=0, max=0
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): No ABS_MT_PRESSURE (3a)
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): Pressure (3a): min=0, max=0
    12-18 15:27:49.408 I/TouchAnalyzer( 3242): No ABS_X (35)
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): Open /dev/input/event1 ...
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): Input-Device: rkxx-remotectl
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): No ABS_MT_SLOT (2f)
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): Slots (2f): min=0, max=0
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): No ABS_MT_TRACKING_ID (39)
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): Tracking-ID (39): min=0, max=0
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): No ABS_MT_PRESSURE (3a)
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): Pressure (3a): min=0, max=0
    12-18 15:27:49.508 I/TouchAnalyzer( 3242): No ABS_X (35)
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): Open /dev/input/event2 ...
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): Input-Device: SONiX USB Device
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): No ABS_MT_SLOT (2f)
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): Slots (2f): min=0, max=0
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): No ABS_MT_TRACKING_ID (39)
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): Tracking-ID (39): min=0, max=0
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): No ABS_MT_PRESSURE (3a)
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): Pressure (3a): min=0, max=0
    12-18 15:27:49.568 I/TouchAnalyzer( 3242): No ABS_X (35)
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): Open /dev/input/event3 ...
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): Input-Device: SONiX USB Device
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): No ABS_MT_SLOT (2f)
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): Slots (2f): min=0, max=0
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): No ABS_MT_TRACKING_ID (39)
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): Tracking-ID (39): min=0, max=0
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): No ABS_MT_PRESSURE (3a)
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): Pressure (3a): min=0, max=0
    12-18 15:27:49.608 I/TouchAnalyzer( 3242): No ABS_X (35)
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Open /dev/input/event4 ...
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Input-Device: Microsoft X-Box pad v2 (US)
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Slots (2f): min=0, max=0
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Tracking-ID (39): min=0, max=0
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Pressure (3a): min=0, max=0
    12-18 15:27:49.648 I/TouchAnalyzer( 3242): Device failure: xmin == xmax || ymin == ymax
    12-18 15:27:49.688 I/TouchAnalyzer( 3242): ----------------------------
    12-18 15:27:49.778 I/ActivityManager( 262): Displayed com.poke64738.joytouchanalyzer/.JoyTouchAnalyzer: +1s571ms

    #2
    I have the app but not installed it yet. Let me see what it does on my MX1.

    The dev of the app is a good guy and will likely look into it for you, just email him.

    Comment


      #3
      I bought it and get the same error message, waste of money so far. I I'm running a mk808 and finless 1.5a.

      Comment


        #4
        If you're willing to do it that way, it is possible to get it to work if you have Droidmote server running with a client connected when using Joy2Touch. At least that how I resolved it.

        Comment


          #5
          Originally posted by Mow View Post
          If you're willing to do it that way, it is possible to get it to work if you have Droidmote server running with a client connected when using Joy2Touch. At least that how I resolved it.
          I have droidmote, great app.

          So with droidmote i can use my xbox 's' controller on touchscreen only games?

          WOW if that's possible it would solve my problem

          How do i go about doing this?

          Comment


            #6
            Sorry about that,

            I just installed both the joystick center and joy2touch and both work.

            iMito MX1 stock/rooted rom.

            I suggest you guys contact Finless and see if he changed something in his rom. Also check out the stock rom and see what happens.

            Comment


              #7
              That's great news Reddraon72!

              The MX1 is similar to the MK802 III in terms of its ram/processor so I guess there is still hope of getting the Joycenter + Touch server app working on my device.

              I am tempted to reflash my device back to stock firmware just to see if it works but even if it did the trade off between stock firmware compared to Finless/2Dark4u 1.7 is massive.

              No more full market for a start and buggy performance

              But in order to see if it works on the MK802 III it is worth doing I guess.

              @ Finless Bob: Is there anything you can think of that might make this app work on your 1.7 Rom?
              Would be great for us all if we could get it working!

              Comment


                #8
                Actually the MX1 is a MK808 but by a separate company. The MK802.3 may be the same CPU but the iMito is based off of the MK808.

                The other thing is I have an app loaded called Webkey and that may have something to do with it, but I cannot put my finger on that for sure.

                Comment


                  #9
                  Originally posted by reddragon72 View Post
                  Actually the MX1 is a MK808 but by a separate company. The MK802.3 may be the same CPU but the iMito is based off of the MK808.

                  The other thing is I have an app loaded called Webkey and that may have something to do with it, but I cannot put my finger on that for sure.
                  I supposed I couldn't bother you to try the new 1080p beta firmware to let us know if it works?

                  Comment


                    #10
                    Originally posted by no1john View Post
                    I have droidmote, great app.

                    So with droidmote i can use my xbox 's' controller on touchscreen only games?

                    WOW if that's possible it would solve my problem

                    How do i go about doing this?
                    Basically just keep your phone connected to Droidmote server when starting Joy2Touch, and you won't get the error message (at least I don't) Make sure your phone don't turn off wifi when it's idle, and keep it in the charger with Droidmote running

                    Comment


                      #11
                      Originally posted by Mow View Post
                      Basically just keep your phone connected to Droidmote server when starting Joy2Touch, and you won't get the error message (at least I don't) Make sure your phone don't turn off wifi when it's idle, and keep it in the charger with Droidmote running
                      Huh, very simple way to play some games...

                      Comment


                        #12
                        Do you have to root your phone to get droidmote to work?

                        Comment


                          #13
                          Droidmote client works without root. The server (that you run on your tv device) requires root.

                          Comment

                          Working...
                          X