minitouch is not supported by Meizu Pro7 Plus

[rockywhisper]

Hi, buddy.

Meizu Pro7 Plus doesn't respond to the minitouch input, just like #16

[sorccu]

Please provide the same details as in that issue. Including minitouch output and the getevent command output.

Also, check your settings very carefully, perhaps you need to enable it separately like on Xiaomi.

[rockywhisper]

@sorccu Hi, thanks for your reply. :-)

• I'm pretty sure the required settings are checked.

• I used minitouch operate code to tap on [100, 100], and Meizu Pro7 Plus just don't response. (Other devices are OK, including Xiaomi.)

  

D:\dev-local\airtest>adb shell getevent -p
add device 1: /dev/input/event5
  name:     "sub_touch"
  events:
    KEY (0001): 00c4  0145  014a  0270  0271  0272  0280  0281
                0282  0283  0290  0291  0292  0293  0294  0295
                0296  0297  0298  0299  029a
    ABS (0003): 002f  : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                0030  : value 0, min 0, max 15, fuzz 0, flat 0, resolution 0
                0031  : value 0, min 0, max 15, fuzz 0, flat 0, resolution 0
                0035  : value 0, min 0, max 240, fuzz 0, flat 0, resolution 0
                0036  : value 0, min 0, max 536, fuzz 0, flat 0, resolution 0
                0039  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
  input props:
    INPUT_PROP_DIRECT
add device 2: /dev/input/event2
  name:     "mtk-kpd"
  events:
    KEY (0001): 0066  0072  0073  0074  0198
    SW  (0005): 0000
  input props:
    <none>
add device 3: /dev/input/event6
  name:     "main_touch"
  events:
    KEY (0001): 008f  00c3  0145  014a  0270  0272  0280  0281
                0282  0283  0290  0291  0292  0293  0294  0295
                0296  0297  0298  0299  029a
    ABS (0003): 0000  : value 0, min 0, max 1439, fuzz 0, flat 0, resolution 0
                0001  : value 0, min 0, max 2559, fuzz 0, flat 0, resolution 0
                002f  : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                0030  : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                0031  : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                0035  : value 0, min 0, max 1439, fuzz 0, flat 0, resolution 0
                0036  : value 0, min 0, max 2559, fuzz 0, flat 0, resolution 0
                0039  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
  input props:
    INPUT_PROP_DIRECT
add device 4: /dev/input/event7
  name:     "msensor"
  events:
    ABS (0003): 0000  : value 74, min -32767, max 32767, fuzz 0, flat 0, resolution 0
                0001  : value -83, min -32767, max 32767, fuzz 0, flat 0, resolution 0
                0002  : value -77, min -32767, max 32767, fuzz 0, flat 0, resolution 0
  input props:
    <none>
add device 5: /dev/input/event4
  name:     "bh1745"
  events:
    ABS (0003): 0028  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                0029  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                002a  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                002b  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
  input props:
    <none>
add device 6: /dev/input/event3
  name:     "input_prx_stk3311"
  events:
    ABS (0003): 0019  : value 1, min 0, max 1, fuzz 0, flat 0, resolution 0
  input props:
    <none>
add device 7: /dev/input/event1
  name:     "fp-keys"
  events:
    KEY (0001): 0067  0069  006a  006c  0074  008b  009e  00ac
                00d4
  input props:
    <none>
add device 8: /dev/input/event0
  name:     "ACCDET"
  events:
    KEY (0001): 0072  0073  00a4  0246
  input props:
    <none>

[sorccu]

Oh. It's choosing the wrong device. This is a fairly simple case, the autodetection method needs to handle this case.

[rockywhisper]

@sorccu Glad to hear that. So is there any hint? What should I do to specify the autodetection method?

Or I can just wait for your fix. :-)

[sorccu]

Check out the issue-28 branch. Let me know whether it works for you. You should also test any other devices you have to make sure it didn't break anything.

[rockywhisper]

@sorccu Hi, buddy. Sorry, I didn't reply to you in time. The issue-28 branch works fine for the Meizu Pro7 Plus, as well as 10+ devices in my hand. Thank you very much.

Maybe you can merge into master later.