The touch device cannot be awakened.

[swety2003]

          Same problem.

Device: Redmi Note11 Pro+ (pissarropro) System logs:

2023-10-21 10:25:58.074  1646-2024  InputReader             pid-1646                             I  Disabling goodix_ts (device 6) because the associated viewport is not active
2023-10-21 10:25:58.074  1646-2024  InputReader             pid-1646                             I  Device reconfigured: id=6, name='goodix_ts', size 8641x19201, orientation 0, mode 0, display id 0
2023-10-21 10:26:00.051  1646-2024  InputReader             pid-1646                             I  Device reconfigured: id=6, name='goodix_ts', size 1080x2400, orientation 0, mode 1, display id 0
2023-10-21 10:26:10.511  1646-2024  InputReader             pid-1646                             I  Disabling goodix_ts (device 6) because the associated viewport is not active
2023-10-21 10:26:10.511  1646-2024  InputReader             pid-1646                             I  Device reconfigured: id=6, name='goodix_ts', size 8641x19201, orientation 0, mode 0, display id 0
2023-10-21 10:26:12.744  1061-1068  android.sy....0-service pid-1061                             E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:26:13.053  1646-2024  InputReader             pid-1646                             I  Device reconfigured: id=6, name='goodix_ts', size 1080x2400, orientation 0, mode 1, display id 0
2023-10-21 10:26:13.081  1061-1068  android.sy....0-service pid-1061                             E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:26:23.521  1061-7638  android.sy....0-service android.system.suspend@1.0-service   E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:26:23.533  1646-2024  InputReader             system_server                        I  Disabling goodix_ts (device 6) because the associated viewport is not active
2023-10-21 10:26:23.533  1646-2024  InputReader             system_server                        I  Device reconfigured: id=6, name='goodix_ts', size 8641x19201, orientation 0, mode 0, display id 0
2023-10-21 10:28:34.526  1646-4227  ActivityManager         system_server                        I  Killing 6047:com.goodix.gftest/u0a102 (adj 999): empty #40
2023-10-21 10:28:35.850  1061-1922  android.sy....0-service android.system.suspend@1.0-service   E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:28:35.858  1646-2024  InputReader             system_server                        I  Device reconfigured: id=6, name='goodix_ts', size 1080x2400, orientation 0, mode 1, display id 0
2023-10-21 10:28:41.046  1061-7638  android.sy....0-service android.system.suspend@1.0-service   E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:28:41.057  1646-2024  InputReader             system_server                        I  Disabling goodix_ts (device 6) because the associated viewport is not active
2023-10-21 10:28:41.057  1646-2024  InputReader             system_server                        I  Device reconfigured: id=6, name='goodix_ts', size 8641x19201, orientation 0, mode 0, display id 0
2023-10-21 10:28:46.208  1061-1922  android.sy....0-service android.system.suspend@1.0-service   E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:28:46.223  1646-2024  InputReader             system_server                        I  Device reconfigured: id=6, name='goodix_ts', size 1080x2400, orientation 0, mode 1, display id 0
2023-10-21 10:28:56.719  1061-1922  android.sy....0-service android.system.suspend@1.0-service   E  Error opening kernel wakelock stats for: wakeup38 (../../devices/platform/goodix_ts.0/wakeup/wakeup38): Permission denied
2023-10-21 10:28:56.734  1646-2024  InputReader             system_server                        I  Disabling goodix_ts (device 6) because the associated viewport is not active
2023-10-21 10:28:56.734  1646-2024  InputReader             system_server                        I  Device reconfigured: id=6, name='goodix_ts', size 8641x19201, orientation 0, mode 0, display id 0

_Originally posted by @swety2003 in https://github.com/phhusson/treble_experimentations/issues/2460#issuecomment-1783095722_

[phhusson]

Why do you think this log is relevant? I can't see how it is relevant

[swety2003]

Why do you think this log is relevant? I can't see how it is relevant

The touch chip of this device comes from goodix_ts, when I lock the screen and reopen it, the touch won't work unless I restart my phone.（Every gsi I tested has this problem） It seems that this is the only thing in the system log that seems to be related to it. If the log I provided is not helpful, I will provide a complete log later.

[phhusson]

Unless it's the resolution change (but then it wouldn't be "doesn't work" it would be "is scaled"), those logs doesn't give any information.

Run getevent do you really see no event coming out after resume? Get logs with adb logcat -b all. I'm pretty sure there'll be other goodix references (maybe indirect, like just saying touchscreen idk) in it.

[swety2003]

Unless it's the resolution change (but then it wouldn't be "doesn't work" it would be "is scaled"), those logs doesn't give any information.

Run getevent do you really see no event coming out after resume? Get logs with adb logcat -b all. I'm pretty sure there'll be other goodix references (maybe indirect, like just saying touchscreen idk) in it.

Run getevent: before suspend:

arm64_bgN:/ $ getevent
add device 1: /dev/input/event6
  name:     "uinput_nav"
add device 2: /dev/input/event5
  name:     "goodix_ts"
add device 3: /dev/input/event0
  name:     "ACCDET"
add device 4: /dev/input/event3
  name:     "mt6877-mt6359 USB_3_5 Jack"
add device 5: /dev/input/event4
  name:     "uinput-goodix"
add device 6: /dev/input/event2
  name:     "awinic_haptic"
add device 7: /dev/input/event1
  name:     "mtk-kpd"
/dev/input/event5: 0003 0039 0000017c
/dev/input/event5: 0003 0035 0000169d
/dev/input/event5: 0003 0036 0000206b
/dev/input/event5: 0001 014a 00000001
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0039 ffffffff
/dev/input/event5: 0001 014a 00000000
/dev/input/event5: 0000 0000 00000000

after

30|arm64_bgN:/ $ getevent
add device 1: /dev/input/event6
  name:     "uinput_nav"
add device 2: /dev/input/event5
  name:     "goodix_ts"
add device 3: /dev/input/event0
  name:     "ACCDET"
add device 4: /dev/input/event3
  name:     "mt6877-mt6359 USB_3_5 Jack"
add device 5: /dev/input/event4
  name:     "uinput-goodix"
add device 6: /dev/input/event2
  name:     "awinic_haptic"
add device 7: /dev/input/event1
  name:     "mtk-kpd"
/dev/input/event1: 0001 0074 00000001
/dev/input/event1: 0000 0000 00000000
/dev/input/event1: 0001 0074 00000000
/dev/input/event1: 0000 0000 00000000

Run adb logcat -b all: adb.txt

I also found that running the GSI, the device could not be connected to the computer via USB, and the device manager showed the USB device that was not recognized

[swety2003]

Fixed by flashing a specific kernel.

[NewUserHa]

Fixed by flashing a specific kernel.

can you share the specific kernel or the way to get it