Minitouch does not work on LG lm-v350

[ghost]

I have a LG device, whose model is lm-v350, release version is 8.0, sdk version is 26, build is "judyp_lao_com-userdebug 8.0.0 opr1.170623.032 180921528041d.fgn test-keys".

I find that minitouch does not work on it, the error message is:

Note: device /dev/input/mice is not supported by libevdev Type B touch device touch_dev (1439x3119 with 10 contacts) detected on /dev/input/event1 (score 2109)

I can connect to its socket and can get output:

^ 10 1439 3119 255 $ 5862

However, when I input touch commands through the socket, nothing happens on the device screen.

I have another LG device which has the same issue.

minicap works normally on the device.

[sorccu]

Run adb shell getevent -ilp on both devices.

[ghost]

I only have one device at my hand now. Here is its output:

add device 1: /dev/input/event7 bus: 0006 vendor 0000 product 0000 version 0000 name: "uinput-fpc" location: "" id: "" version: 1.0.1 events: KEY (0001): KEY_UP KEY_LEFT KEY_RIGHT KEY_DOWN
KEY_PROG1 BTN_NORTH BTN_WEST
ABS (0003): ABS_Z : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0 input props:

add device 2: /dev/input/event6 bus: 0000 vendor 0000 product 0000 version 0000 name: "sdm845-tavil-snd-card Button Jack" location: "ALSA" id: "" version: 1.0.1 events: KEY (0001): KEY_VOLUMEDOWN KEY_VOLUMEUP KEY_MEDIA BTN_4 BTN_5 KEY_VOICECOMMAND input props: add device 3: /dev/input/event5 bus: 0000 vendor 0000 product 0000 version 0000 name: "sdm845-tavil-snd-card Headset Jack" location: "ALSA" id: "" version: 1.0.1 events: SW (0005): SW_HEADPHONE_INSERT SW_MICROPHONE_INSERT SW_LINEOUT_INSERT SW_JACK_PHYSICAL_INS 0010 0011 0012 0013 input props: add device 4: /dev/input/event3 bus: 0000 vendor 0000 product 0000 version 0000 name: "STM VL53L0 proximity sensor" location: "" id: "" version: 1.0.1 events: ABS (0003): ABS_WHEEL : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_GAS : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_BRAKE : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT0X : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT0Y : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT1X : value 0, min 0, max 765, fuzz 0, flat 0, resolution 0 ABS_HAT1Y : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0 ABS_HAT2X : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT2Y : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT3X : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_HAT3Y : value 0, min 0, max -1, fuzz 0, flat 0, resolution 0 ABS_DISTANCE : value 0, min 0, max 76, fuzz 0, flat 0, resolution 0 input props: add device 5: /dev/input/event2 bus: 0000 vendor 0000 product 0000 version 0000 name: "touch_dev" location: "" id: "" version: 1.0.1 events: KEY (0001): BTN_TOOL_FINGER BTN_TOUCH ABS (0003): ABS_MT_SLOT : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0 ABS_MT_WIDTH_MAJOR : value 0, min 0, max 2879, fuzz 0, flat 0, resolution 0 ABS_MT_WIDTH_MINOR : value 0, min 0, max 2879, fuzz 0, flat 0, resolution 0 ABS_MT_ORIENTATION : value 0, min 0, max 90, fuzz 0, flat 0, resolution 0 ABS_MT_POSITION_X : value 0, min 0, max 1439, fuzz 0, flat 0, resolution 0 ABS_MT_POSITION_Y : value 0, min 0, max 2879, 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 6: /dev/input/event1 bus: 0000 vendor 0000 product 0000 version 0000 name: "fingerprint" location: "" id: "" version: 1.0.1 events: input props: add device 7: /dev/input/event0 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: add device 8: /dev/input/event4 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 input props: could not get driver version for /dev/input/mice, Not a typewriter

[sorccu]

What is that device anyway? I can't find lm-v350 on google.

Also, it looks to me like it's running an unofficial ROM. Maybe that's why.

[ghost]

Hi Simo,

Which kind of "device type" do you want? (hardware.sku, build, or something else?) :) I can not touch the device physically and I can run adb commands on the device. I can also find some other people who can touch the device physically, so please feel free to tell me how to get the information you need.

abi: arm64-v8a brand: lge build: judyp_lao_com-userdebug 8.0.0 opr1.170623.032 180921528041d.fgn test-keys gms_version: 12.5.29 (040400-192802242) gservices_android_id: 3773991283048375218 hardware: judyp id: LMV350ULA968a8833 imei: 356659090004139 incremental_build: 180921528041d.fgn mac_address: 00:3d:e8:b6:66:54 model: lm-v350 product_board: sdm845 release_version: 8.0.0 rooted: true screen_density: 560 screen_size: 1440x2880 sdk_version: 26 serial: lmv350ula968a8833 sign: test-keys type: judyp_lao_com

[sorccu]

Give me a link that shows a picture of the device and perhaps some details of it.

I still think using a stock ROM would work. Since you're using a rooted device with custom ROM, it's very difficult to say anything. It could be that there's a custom option somewhere you need to enable. Or perhaps it's been permanently disabled.

[HenryNNN]

Hi Shianhou, how did you root it ? I got mine hard bricked in Qualcomm 9008 mode.