Do not work on NUBIA z9mini

[scottchejin]

Hi,

I installed minitouch onNUBIA z9mini, then run 'adb shell /data/local/tmp/minitouch -h', but minitouch do not work. the response is: WARNING: linker: /data/local/tmp/minitouch: unused DT entry: type 0x6ffffffe arg 0xae0 WARNING: linker: /data/local/tmp/minitouch: unused DT entry: type 0x6fffffff arg 0x1 Usage: /data/local/tmp/minitouch [-h] [-d ] [-n ] -d : Use the given touch device. Otherwise autodetect. -n : Change the name of of the abtract unix domain socket. (minitouch) -h: Show help.

The device info:

[sorccu]

If it shows usage, then you're probably just calling it wrong somehow. Otherwise it would show an error. The warnings are OK and can be ignored.

Your command looks ok but maybe it's not what you're actually using? Try the run.sh script instead

On Fri, 2 Dec 2016 at 14:36 scottchejin notifications@github.com wrote:

Hi,

I installed minitouch onNUBIA z9mini, then run 'adb shell /data/local/tmp/minitouch -h', but minitouch do not work. the response is: WARNING: linker: /data/local/tmp/minitouch: unused DT entry: type 0x6ffffffe arg 0xae0 WARNING: linker: /data/local/tmp/minitouch: unused DT entry: type 0x6fffffff arg 0x1 Usage: /data/local/tmp/minitouch [-h] [-d ] [-n ] -d : Use the given touch device. Otherwise autodetect. -n : Change the name of of the abtract unix domain socket. (minitouch) -h: Show help.

The device info: [image: nubia] https://cloud.githubusercontent.com/assets/5362161/20824004/f91e1c92-b893-11e6-8dea-f12ad1003836.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openstf/minitouch/issues/9, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-_RUFQwupyMzgBG4-Qa-mGWf1v_TBks5rD65QgaJpZM4LCN24 .

[sorccu]

Please let us know if you managed to resolve the issue.

[scottchejin]

I’m terribly sorry for my late reply。I update Nubia UI from 3.1 to 3.8, it can work fine. So I think they fixed something.

2016-12-06

scottche

发件人：Simo Kinnunen notifications@github.com 发送时间：2016-12-05 23:46 主题：Re: [openstf/minitouch] Do not work on NUBIA z9mini (#9) 收件人："openstf/minitouch"minitouch@noreply.github.com 抄送："scottchejin"scottche@126.com,"Author"author@noreply.github.com

Please let us know if you managed to resolve the issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[codeskyblue]

Using the latest minitouch which publish in npm.

Phone nubia NX508J also called Z9 Android 5.0.2 not support minitouch

But the minitouch log looks good.

shell@NX508J:/ $ /data/local/tmp/minitouch
Note: device /dev/input/event0 was outscored by /dev/input/event1 (2109 >= 2109)
Note: device /dev/input/mice is not supported by libevdev
Type B touch device atmel_mxt_ts_T100_touchscreen_rim (1079x1919 with 10 contacts) detected on /dev/input/event1 (score 2109)
Connection established

[sorccu]

Did it work before?

Can you run adb shell getevent -ilp?

Reply with all the output.

On Wed, Jul 12, 2017 at 11:17 shengxiang notifications@github.com wrote:

Using the latest minitouch which publish in npm.

Phone nubia NX508J also called Z9 Android 5.0.2 not support minitouch

But the minitouch looks good.

shell@NX508J:/ $ /data/local/tmp/minitouch Note: device /dev/input/event0 was outscored by /dev/input/event1 (2109 >= 2109) Note: device /dev/input/mice is not supported by libevdev Type B touch device atmel_mxt_ts_T100_touchscreen_rim (1079x1919 with 10 contacts) detected on /dev/input/event1 (score 2109) Connection established

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/openstf/minitouch/issues/9#issuecomment-314633110, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-_U93IAxT8s-k7EIlxOcsYyDfbPlUks5sNDrVgaJpZM4LCN24 .

[codeskyblue]

It does not work before.

This is detailed output of adb shell getevnet -ilp

add device 1: /dev/input/event1
  bus:      0018
  vendor    0000
  product   0000
  version   0000
  name:     "atmel_mxt_ts_T100_touchscreen_rim"
  location: "i2c-2-004a/input0"
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): KEY_F10               KEY_MENU              KEY_BACK              KEY_HOMEPAGE         
    ABS (0003): ABS_X                 : value 1076, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_Y                 : value 38, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_PRESSURE          : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_SLOT           : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MAJOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_ORIENTATION    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_X     : value 0, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_Y     : value 0, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_MT_TRACKING_ID    : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                ABS_MT_PRESSURE       : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
  input props:
    INPUT_PROP_DIRECT
add device 2: /dev/input/event0
  bus:      0018
  vendor    0000
  product   0000
  version   0000
  name:     "atmel_mxt_ts_T100_touchscreen"
  location: "i2c-2-004a/input0"
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): KEY_F10               KEY_MENU              KEY_BACK              KEY_HOMEPAGE         
    ABS (0003): ABS_X                 : value 551, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_Y                 : value 349, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_PRESSURE          : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_SLOT           : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MAJOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_ORIENTATION    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_X     : value 0, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_Y     : value 0, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_MT_TRACKING_ID    : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                ABS_MT_PRESSURE       : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
  input props:
    INPUT_PROP_DIRECT
add device 3: /dev/input/event9
  bus:      0000
  vendor    0000
  product   0000
  version   0000
  name:     "msm8994-ak4961-snd-card Headset Jack"
  location: "ALSA"
  id:       ""
  version:  1.0.1
  events:
    SW  (0005): SW_HEADPHONE_INSERT   SW_MICROPHONE_INSERT  000e                  000f                 
                0010                 
  input props:
    <none>
add device 4: /dev/input/event8
  bus:      0000
  vendor    0000
  product   0000
  version   0000
  name:     "msm8994-ak4961-snd-card Button Jack"
  location: "ALSA"
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): BTN_0                 BTN_1                 BTN_2                 BTN_3                
                BTN_4                
  input props:
    <none>
add device 5: /dev/input/event7
  bus:      0000
  vendor    0001
  product   0001
  version   0001
  name:     "hs_detect"
  location: ""
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): KEY_VOLUMEDOWN        KEY_VOLUMEUP          KEY_MEDIA            
    MSC (0004): MSC_SCAN             
    SW  (0005): SW_HEADPHONE_INSERT   SW_MICROPHONE_INSERT 
  input props:
    <none>
add device 6: /dev/input/event5
  bus:      0000
  vendor    0000
  product   0000
  version   0000
  name:     "qpnp_pon"
  location: "qpnp_pon/input0"
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): KEY_VOLUMEDOWN        KEY_POWER            
  input props:
    0004
add device 7: /dev/input/event4
  bus:      0018
  vendor    0000
  product   0000
  version   0000
  name:     "hall_device"
  location: ""
  id:       ""
  version:  1.0.1
  events:
    REL (0002): REL_RX                REL_RY               
  input props:
    <none>
add device 8: /dev/input/event3
  bus:      0018
  vendor    0000
  product   0000
  version   0000
  name:     "light"
  location: ""
  id:       ""
  version:  1.0.1
  events:
    REL (0002): REL_X                 REL_Y                
  input props:
    <none>
add device 9: /dev/input/event2
  bus:      0018
  vendor    0000
  product   0000
  version   0000
  name:     "proximity"
  location: ""
  id:       ""
  version:  1.0.1
  events:
    REL (0002): REL_X                 REL_Y                 REL_Z                 REL_MISC             
  input props:
    <none>
add device 10: /dev/input/event6
  bus:      0019
  vendor    0001
  product   0001
  version   0100
  name:     "gpio-keys"
  location: "gpio-keys/input0"
  id:       ""
  version:  1.0.1
  events:
    KEY (0001): KEY_VOLUMEUP          KEY_CAMERA_FOCUS      02fe                 
  input props:
    <none>

[codeskyblue]

Just notice that message. I will try this way.

[sorccu]

It's weird but I think it shows the same touch device twice. They have the same bus and location. Everything's the same. Maybe a device bug. Probably only one of them works, and STF chooses the wrong one by chance.

On Wed, Jul 12, 2017 at 13:02 shengxiang notifications@github.com wrote:

Just notice that message. I will try this way. [image: image] https://user-images.githubusercontent.com/3281689/28102515-4fc300f4-6702-11e7-9a1f-34cb65de49c7.png

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/openstf/minitouch/issues/9#issuecomment-314644799, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-_bQ02Y6olw1rl-rhPHqk8Yi6tZFfks5sNFNVgaJpZM4LCN24 .

[mingyuan-xia]

This might be related. This is a getevent -lp dump for NUBIA z17mini. Very weird, NUBIA models always show two MT devices. But actually, when you touch on the screen, only one would output evdev data (nubia_synaptics_dsx, aka /dev/input/event1). The other, so-called wrapper, is just there for nothing. Seems that we need a stronger mechanism to detect the real evdev outputer. BTW, some Chinese OEM ROM makers also observe this, see http://bbs.zhiyoo.com/thread-8878087-1-1.html (you might need Google translate). And the case is, even different batches of a same NUBIA model might have hardware difference.

add device 1: /dev/input/event8
  name:     "msm8952-snd-card-mtp Headset Jack"
  events:
    SW  (0005): SW_HEADPHONE_INSERT   SW_MICROPHONE_INSERT  SW_LINEOUT_INSERT     SW_JACK_PHYSICAL_INS
                SW_MUTE_DEVICE        SW_MAX                0010                  0011
  input props:
    <none>
add device 2: /dev/input/event7
  name:     "msm8952-snd-card-mtp Button Jack"
  events:
    KEY (0001): KEY_VOLUMEDOWN        KEY_VOLUMEUP          KEY_MEDIA             BTN_4
                BTN_5                 BTN_6                 BTN_7                 KEY_VOICECOMMAND
  input props:
    INPUT_PROP_TOPBUTTONPAD
add device 3: /dev/input/event5
  name:     "qpnp_pon"
  events:
    KEY (0001): KEY_VOLUMEDOWN        KEY_POWER
  input props:
    INPUT_PROP_TOPBUTTONPAD
add device 4: /dev/input/event4
  name:     "proximity"
  events:
    REL (0002): REL_RZ                REL_MISC
  input props:
    <none>
add device 5: /dev/input/event3
  name:     "light"
  events:
    REL (0002): REL_X
  input props:
    <none>
add device 6: /dev/input/event2
  name:     "gf3208"
  events:
    KEY (0001): KEY_F3                KEY_F9                KEY_HOME              KEY_UP
                KEY_LEFT              KEY_RIGHT             KEY_DOWN              KEY_POWER
                KEY_MENU              KEY_BACK
  input props:
    <none>
add device 7: /dev/input/event0
  name:     "input_mt_wrapper"
  events:
    ABS (0003): ABS_MT_TOUCH_MAJOR    : value 0, min 0, max 1, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_X     : value 0, min 0, max 1080, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_Y     : value 0, min 0, max 1920, fuzz 0, flat 0, resolution 0
                ABS_MT_TRACKING_ID    : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                ABS_MT_PRESSURE       : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
  input props:
    <none>
could not get driver version for /dev/input/mice, Not a typewriter
add device 8: /dev/input/event6
  name:     "gpio-keys"
  events:
    KEY (0001): KEY_VOLUMEUP
  input props:
    <none>
could not get driver version for /dev/input/mouse0, Not a typewriter
add device 9: /dev/input/event1
  name:     "nubia_synaptics_dsx"
  events:
    KEY (0001): KEY_F9                KEY_F10               KEY_MENU              KEY_BACK
                KEY_HOMEPAGE          BTN_TOOL_FINGER       BTN_TOUCH             02f0
    ABS (0003): ABS_X                 : value 0, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_Y                 : value 0, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_PRESSURE          : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_SLOT           : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MAJOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MINOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_X     : value 0, min 0, max 1079, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_Y     : value 0, min 0, max 1919, fuzz 0, flat 0, resolution 0
                ABS_MT_TRACKING_ID    : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                ABS_MT_PRESSURE       : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
  input props:
    INPUT_PROP_DIRECT

[sorccu]

Which one gets selected?

[mingyuan-xia]

the wrapper (event0), but should be nubia_synaptics_dsx (event1)

[sorccu]

The Synaptics device should get selected because it has INPUT_PROP_DIRECT. What does the minitouch log output look like?

[mingyuan-xia]

Problem solved, my bad. INPUT_PROP_DIRECT lets nubia_synaptics_dsx selected.

[sorccu]

It sounds like this device is prob fixed now thanks to INPUT_PROP_DIRECT handling which was added for some other device earlier.