Closed chnlzh2 closed 1 year ago
pastaq
commented
2 years ago Can you elaborate? Gyro support should work already. You need to press and release LC and RC at the same time. The console will provide 1 buzz for enable and 2 buzz for disable.
alphonsez1
commented
2 years ago I have the same issue. Also the rumble/haptic is not working either. I find that the Steam UI still shows the Xbox controller logo when the service is running.
I tried to run the python script manually. It runs fine, with the original devices moved to the hidden folder. The log says the Gryo is successfully captured. It seems to be the issue with Steam that didn't recognize the Handheld controller.
When I got it running, there is always a popup says that Xbox 360 controller is connected. If I look at the js devices, there is always a new js device created when I run this application. So my guess is that something else is trying to recover the device.
alphonsez1
commented
2 years ago I did some further testing. First of all, I got wrong about what LC and RC are. I thought it was clicking both joysticks. @chnlzh2 Would you try pressing both LC+RC (buttons next to LB and RB) and check whether it works to you?
It still doesn't work for me, although I do hear the 1 buzz when enabling gyro and 2 buzz for disable. I printed the gyro events and the handycon.py is working as expected. It can also rumble properly. However it appears the games are not using this controller somehow.
alphonsez1
commented
2 years ago I got the gyro worked once when the UI says detected steam controller rather than xbox 360 controller. However I can't reproduce it.
I'll also try SDL_JOYSTICK_DEVICE env var this weekend.
alphonsez1
commented
2 years ago Update: Somehow my controller gyro suddenly starts to work. It still shows the Xbox button.
Now I can't figure out how to make it not work any more. Even if I use a controller layout that says not supporting motion control, it still works on my Ayaneo Air.
EricFL1998
commented
2 years ago my gyro on the air is not working either it shows the xbox button and detect the controller as xbox-360, pressing lc, rc and release does not do anything, no buzz either.
pastaq
commented
2 years ago What OS are you both using?
ghost
commented
2 years ago What OS are you both using?
Arch linux with kernel 6.0.6-arch1-1. Gyro doesn't seem to work for me either, not a big deal right now so just contributing.
EricFL1998
commented
2 years ago holoiso> What OS are you both using?
pastaq
commented
1 year ago I found the issue. The AUR package wasn't properly installing the gyro config. Fixed in the latest. package.
ghost
commented
1 year ago Sorry if this sounds dumb but is there a trick to activating gyro? Been trying to get it to work with Little Witch Nobeta and no luck. Am I meant to remap the controls or make a .conf for the game?
pastaq
commented
1 year ago should just be holding the LC & RC buttons until the device does a little buzz, one for on and two for off.
ghost
commented
1 year ago Strange, it doesn't seem working for me, already updated the AUR package. Is there a program I can run to help debug this?
pastaq
commented
1 year ago If you disable the handycon.service and run it manually you should get some debug output. running the evtest program should tell you if the gyro is sending events or not.
ghost
commented
1 year ago Here's my results.
Event: time 1669187582.208484, type 1 (EV_KEY), code 316 (BTN_MODE), value 1
Event: time 1669187582.208484, -------------- SYN_REPORT ------------
Event: time 1669187582.298663, type 1 (EV_KEY), code 311 (BTN_TR), value 1
Event: time 1669187582.298663, -------------- SYN_REPORT ------------
Event: time 1669187582.388847, type 1 (EV_KEY), code 316 (BTN_MODE), value 0
Event: time 1669187582.388847, -------------- SYN_REPORT ------------
Event: time 1669187582.479018, type 1 (EV_KEY), code 311 (BTN_TR), value 0
Event: time 1669187582.479018, -------------- SYN_REPORT ------------Here's my results.
Event: time 1669187582.208484, type 1 (EV_KEY), code 316 (BTN_MODE), value 1 Event: time 1669187582.208484, -------------- SYN_REPORT ------------ Event: time 1669187582.298663, type 1 (EV_KEY), code 311 (BTN_TR), value 1 Event: time 1669187582.298663, -------------- SYN_REPORT ------------ Event: time 1669187582.388847, type 1 (EV_KEY), code 316 (BTN_MODE), value 0 Event: time 1669187582.388847, -------------- SYN_REPORT ------------ Event: time 1669187582.479018, type 1 (EV_KEY), code 311 (BTN_TR), value 0 Event: time 1669187582.479018, -------------- SYN_REPORT ------------This would seem to indicate only the LC button is detecting a press. What output do you get when you press just RC?
If nothing happens with RC only and only LC shows up when you press both, there could be an issue with the key map on some of these. Stop handycon.service with systemctl and run sudo evtest to capture the raw data for the RC button under the AT translated keyboard device. If you still get nothing then you might have a hardware issue.
ghost
commented
1 year ago Event: time 1669190910.441148, type 1 (EV_KEY), code 316 (BTN_MODE), value 1
Event: time 1669190910.441148, -------------- SYN_REPORT ------------
Event: time 1669190910.531484, type 1 (EV_KEY), code 307 (BTN_NORTH), value 1
Event: time 1669190910.531484, -------------- SYN_REPORT ------------
Event: time 1669190910.622459, type 1 (EV_KEY), code 316 (BTN_MODE), value 0
Event: time 1669190910.622459, -------------- SYN_REPORT ------------
Event: time 1669190910.713144, type 1 (EV_KEY), code 307 (BTN_NORTH), value 0
Event: time 1669190910.713144, -------------- SYN_REPORT ------------
Event: time 1669190916.049937, type 1 (EV_KEY), code 316 (BTN_MODE), value 1
Event: time 1669190916.049937, -------------- SYN_REPORT ------------
Event: time 1669190916.140666, type 1 (EV_KEY), code 307 (BTN_NORTH), value 1
Event: time 1669190916.140666, -------------- SYN_REPORT ------------
Event: time 1669190916.231511, type 1 (EV_KEY), code 316 (BTN_MODE), value 0
Event: time 1669190916.231511, -------------- SYN_REPORT ------------
Event: time 1669190916.321958, type 1 (EV_KEY), code 307 (BTN_NORTH), value 0
Event: time 1669190916.321958, -------------- SYN_REPORT ------------
Event: time 1669190925.063344, type 1 (EV_KEY), code 316 (BTN_MODE), value 1
Event: time 1669190925.063344, -------------- SYN_REPORT ------------
Event: time 1669190925.153710, type 1 (EV_KEY), code 311 (BTN_TR), value 1
Event: time 1669190925.153710, -------------- SYN_REPORT ------------
Event: time 1669190925.244272, type 1 (EV_KEY), code 316 (BTN_MODE), value 0
Event: time 1669190925.244272, -------------- SYN_REPORT ------------
Event: time 1669190925.334615, type 1 (EV_KEY), code 311 (BTN_TR), value 0
Event: time 1669190925.334615, -------------- SYN_REPORT ------------
I hit LC first, then RC, then both together. I know the button works because I mapped it before.
pastaq
commented
1 year ago Strange, it appears to be detecting the same butotn for LC and RC. You remapped in windows with the AyaSpace app? What did you map it to?
I'll need to see what buttons the system is detecting from the raw input. Can you get an evtest capture of the AT Translated Keyboard with handycon.service sopped?
ghost
commented
1 year ago Strange, it appears to be detecting the same butotn for LC and RC. You remapped in windows with the AyaSpace app? What did you map it to?
Nah, I remapped it by modifying constants.py.
I'll need to see what buttons the system is detecting from the raw input. Can you get an evtest capture of the AT Translated Keyboard with handycon.service sopped?
Sure thing.
Event: time 1669250140.165896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.165896, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 1
Event: time 1669250140.165896, -------------- SYN_REPORT ------------
Event: time 1669250140.172655, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.172655, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 1
Event: time 1669250140.172655, -------------- SYN_REPORT ------------
Event: time 1669250140.175659, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.175659, type 1 (EV_KEY), code 87 (KEY_F11), value 1
Event: time 1669250140.175659, -------------- SYN_REPORT ------------
^[[23;5~Event: time 1669250140.272314, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.272314, type 1 (EV_KEY), code 87 (KEY_F11), value 0
Event: time 1669250140.272314, -------------- SYN_REPORT ------------
Event: time 1669250140.281356, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.281356, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0
Event: time 1669250140.281356, -------------- SYN_REPORT ------------
Event: time 1669250140.290369, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.290369, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 0
Event: time 1669250140.290369, -------------- SYN_REPORT ------------
Event: time 1669250140.296241, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.296241, -------------- SYN_REPORT ------------
Event: time 1669250140.306339, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.306339, -------------- SYN_REPORT ------------
Event: time 1669250140.315381, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.315381, -------------- SYN_REPORT ------------
Event: time 1669250140.321974, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.321974, -------------- SYN_REPORT ------------
Event: time 1669250140.331189, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.331189, -------------- SYN_REPORT ------------
Event: time 1669250140.343226, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.343226, -------------- SYN_REPORT ------------
Event: time 1669250140.349176, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.349176, -------------- SYN_REPORT ------------
Event: time 1669250140.358117, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.358117, -------------- SYN_REPORT ------------
Event: time 1669250140.367243, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.367243, -------------- SYN_REPORT ------------
Event: time 1669250140.373107, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.373107, -------------- SYN_REPORT ------------
Event: time 1669250140.386072, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.386072, -------------- SYN_REPORT ------------
Event: time 1669250140.394986, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.394986, -------------- SYN_REPORT ------------
Event: time 1669250140.401001, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.401001, -------------- SYN_REPORT ------------
Event: time 1669250140.409973, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.409973, -------------- SYN_REPORT ------------
Event: time 1669250140.418961, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.418961, -------------- SYN_REPORT ------------
Event: time 1669250140.424932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.424932, -------------- SYN_REPORT ------------
Event: time 1669250140.433928, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.433928, -------------- SYN_REPORT ------------
Event: time 1669250140.442944, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.442944, -------------- SYN_REPORT ------------
Event: time 1669250140.448846, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.448846, -------------- SYN_REPORT ------------
Event: time 1669250140.457917, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.457917, -------------- SYN_REPORT ------------
Event: time 1669250140.466758, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.466758, -------------- SYN_REPORT ------------
Event: time 1669250140.473585, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250140.473585, -------------- SYN_REPORT ------------
Event: time 1669250140.482757, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250140.482757, -------------- SYN_REPORT ------------
Event: time 1669250140.491700, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250140.491700, -------------- SYN_REPORT ------------
Event: time 1669250143.652396, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.652396, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 1
Event: time 1669250143.652396, -------------- SYN_REPORT ------------
Event: time 1669250143.659352, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.659352, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 1
Event: time 1669250143.659352, -------------- SYN_REPORT ------------
Event: time 1669250143.662318, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.662318, type 1 (EV_KEY), code 68 (KEY_F10), value 1
Event: time 1669250143.662318, -------------- SYN_REPORT ------------
^[[21;5~Event: time 1669250143.773992, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.773992, type 1 (EV_KEY), code 68 (KEY_F10), value 0
Event: time 1669250143.773992, -------------- SYN_REPORT ------------
Event: time 1669250143.782899, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.782899, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0
Event: time 1669250143.782899, -------------- SYN_REPORT ------------
Event: time 1669250143.793004, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.793004, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 0
Event: time 1669250143.793004, -------------- SYN_REPORT ------------
Event: time 1669250143.798867, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.798867, -------------- SYN_REPORT ------------
Event: time 1669250143.809642, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.809642, -------------- SYN_REPORT ------------
Event: time 1669250143.818843, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.818843, -------------- SYN_REPORT ------------
Event: time 1669250143.824889, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.824889, -------------- SYN_REPORT ------------
Event: time 1669250143.833879, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.833879, -------------- SYN_REPORT ------------
Event: time 1669250143.842725, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.842725, -------------- SYN_REPORT ------------
Event: time 1669250143.848826, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.848826, -------------- SYN_REPORT ------------
Event: time 1669250143.857642, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.857642, -------------- SYN_REPORT ------------
Event: time 1669250143.866629, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.866629, -------------- SYN_REPORT ------------
Event: time 1669250143.876608, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.876608, -------------- SYN_REPORT ------------
Event: time 1669250143.885804, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.885804, -------------- SYN_REPORT ------------
Event: time 1669250143.894661, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.894661, -------------- SYN_REPORT ------------
Event: time 1669250143.900816, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.900816, -------------- SYN_REPORT ------------
Event: time 1669250143.912558, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.912558, -------------- SYN_REPORT ------------
Event: time 1669250143.921557, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.921557, -------------- SYN_REPORT ------------
Event: time 1669250143.927529, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.927529, -------------- SYN_REPORT ------------
Event: time 1669250143.936503, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.936503, -------------- SYN_REPORT ------------
Event: time 1669250143.945579, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.945579, -------------- SYN_REPORT ------------
Event: time 1669250143.951509, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.951509, -------------- SYN_REPORT ------------
Event: time 1669250143.961242, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.961242, -------------- SYN_REPORT ------------
Event: time 1669250143.970400, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.970400, -------------- SYN_REPORT ------------
Event: time 1669250143.976488, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250143.976488, -------------- SYN_REPORT ------------
Event: time 1669250143.985348, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250143.985348, -------------- SYN_REPORT ------------
Event: time 1669250143.994348, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250143.994348, -------------- SYN_REPORT ------------
Event: time 1669250146.203459, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.203459, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 1
Event: time 1669250146.203459, -------------- SYN_REPORT ------------
Event: time 1669250146.209370, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.209370, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 1
Event: time 1669250146.209370, -------------- SYN_REPORT ------------
Event: time 1669250146.212366, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.212366, type 1 (EV_KEY), code 68 (KEY_F10), value 1
Event: time 1669250146.212366, -------------- SYN_REPORT ------------
^[[21;5~Event: time 1669250146.234092, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.234092, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1669250146.234092, -------------- SYN_REPORT ------------
Event: time 1669250146.240244, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.240244, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 2
Event: time 1669250146.240244, -------------- SYN_REPORT ------------
Event: time 1669250146.243261, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.243261, type 1 (EV_KEY), code 87 (KEY_F11), value 1
Event: time 1669250146.243261, -------------- SYN_REPORT ------------
^[[23;5~Event: time 1669250146.701098, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.701098, type 1 (EV_KEY), code 68 (KEY_F10), value 0
Event: time 1669250146.701098, -------------- SYN_REPORT ------------
Event: time 1669250146.710134, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.710134, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0
Event: time 1669250146.710134, -------------- SYN_REPORT ------------
Event: time 1669250146.720412, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.720412, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 0
Event: time 1669250146.720412, -------------- SYN_REPORT ------------
Event: time 1669250146.726030, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.726030, -------------- SYN_REPORT ------------
Event: time 1669250146.736111, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.736111, -------------- SYN_REPORT ------------
Event: time 1669250146.745375, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.745375, -------------- SYN_REPORT ------------
Event: time 1669250146.752027, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.752027, type 1 (EV_KEY), code 87 (KEY_F11), value 0
Event: time 1669250146.752027, -------------- SYN_REPORT ------------
Event: time 1669250146.761260, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.761260, -------------- SYN_REPORT ------------
Event: time 1669250146.769852, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.769852, -------------- SYN_REPORT ------------
Event: time 1669250146.776235, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.776235, -------------- SYN_REPORT ------------
Event: time 1669250146.787823, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.787823, -------------- SYN_REPORT ------------
Event: time 1669250146.796885, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.796885, -------------- SYN_REPORT ------------
Event: time 1669250146.802784, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.802784, -------------- SYN_REPORT ------------
Event: time 1669250146.811780, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.811780, -------------- SYN_REPORT ------------
Event: time 1669250146.821688, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.821688, -------------- SYN_REPORT ------------
Event: time 1669250146.827834, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.827834, -------------- SYN_REPORT ------------
Event: time 1669250146.836745, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.836745, -------------- SYN_REPORT ------------
Event: time 1669250146.846666, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.846666, -------------- SYN_REPORT ------------
Event: time 1669250146.852623, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.852623, -------------- SYN_REPORT ------------
Event: time 1669250146.861598, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.861598, -------------- SYN_REPORT ------------
Event: time 1669250146.870631, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.870631, -------------- SYN_REPORT ------------
Event: time 1669250146.876577, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.876577, -------------- SYN_REPORT ------------
Event: time 1669250146.885505, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.885505, -------------- SYN_REPORT ------------
Event: time 1669250146.894497, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.894497, -------------- SYN_REPORT ------------
Event: time 1669250146.900515, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.900515, -------------- SYN_REPORT ------------
Event: time 1669250146.913760, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.913760, -------------- SYN_REPORT ------------
Event: time 1669250146.922393, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.922393, -------------- SYN_REPORT ------------
Event: time 1669250146.928351, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.928351, -------------- SYN_REPORT ------------
Event: time 1669250146.937368, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.937368, -------------- SYN_REPORT ------------
Event: time 1669250146.946324, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.946324, -------------- SYN_REPORT ------------
Event: time 1669250146.952297, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250146.952297, -------------- SYN_REPORT ------------
Event: time 1669250146.961281, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.961281, -------------- SYN_REPORT ------------
Event: time 1669250146.970285, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.970285, -------------- SYN_REPORT ------------
Event: time 1669250146.976227, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250146.976227, -------------- SYN_REPORT ------------
Event: time 1669250146.985245, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250146.985245, -------------- SYN_REPORT ------------
Event: time 1669250146.994965, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250146.994965, -------------- SYN_REPORT ------------
Event: time 1669250147.001155, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250147.001155, -------------- SYN_REPORT ------------
Event: time 1669250147.010442, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.010442, -------------- SYN_REPORT ------------
Event: time 1669250147.022247, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.022247, -------------- SYN_REPORT ------------
Event: time 1669250147.028176, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250147.028176, -------------- SYN_REPORT ------------
Event: time 1669250147.037163, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.037163, -------------- SYN_REPORT ------------
Event: time 1669250147.046150, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.046150, -------------- SYN_REPORT ------------
Event: time 1669250147.052153, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250147.052153, -------------- SYN_REPORT ------------
Event: time 1669250147.065081, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.065081, -------------- SYN_REPORT ------------
Event: time 1669250147.074031, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.074031, -------------- SYN_REPORT ------------
Event: time 1669250147.080019, type 4 (EV_MSC), code 4 (MSC_SCAN), value 44
Event: time 1669250147.080019, -------------- SYN_REPORT ------------
Event: time 1669250147.088988, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.088988, -------------- SYN_REPORT ------------
Event: time 1669250147.098020, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.098020, -------------- SYN_REPORT ------------
Event: time 1669250147.103926, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250147.103926, -------------- SYN_REPORT ------------
Event: time 1669250147.112964, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.112964, -------------- SYN_REPORT ------------
Event: time 1669250147.121891, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.121891, -------------- SYN_REPORT ------------
Event: time 1669250147.127879, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
Event: time 1669250147.127879, -------------- SYN_REPORT ------------
Event: time 1669250147.136856, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1669250147.136856, -------------- SYN_REPORT ------------
Event: time 1669250147.146638, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9d
Event: time 1669250147.146638, -------------- SYN_REPORT ------------LC first, then RC, then both LC and RC.
pastaq
commented
1 year ago Nah, I remapped it by modifying constants.py.
Uh, don't do that. There should be a file, $HOME/.config/handygccs.conf where you can change the assignments of each button. If you mess with the expected constants then its going to behave differently.
pastaq
commented
1 year ago I also haven't tested the results of having two buttons mapped to the same thing, but I'm pretty sure that will cause issues.
ghost
commented
1 year ago Uh, don't do that. There should be a file, $HOME/.config/handygccs.conf where you can change the assignments of each button. If you mess with the expected constants then its going to behave differently.
Already reinstalled and restored it back to how it was before testing.
pastaq
commented
1 year ago Can you provide the console output from manually starting handycon.py
ghost
commented
1 year ago Can you provide the console output from manually starting handycon.py
Sure thing.
Identified host system as AIR Pro and configured defaults for AYA_GEN2
Attempting to grab controller device...
Attempting to grab keyboard device...
Keyboard device not yet found. Restarting scan.
Attempting to grab power device...
Power Button device not yet found. Restarting scan.
Gyro device not initialized. Ensure bmi160_i2c and i2c_dev modules are loaded, and all python dependencies are met. Skipping gyro device setup.
[Errno 13] Permission denied: '/dev/i2c-1'
Attempting to grab keyboard device...
Keyboard device not yet found. Restarting scan.Last two lines loop, so it keeps going, not going to add that to make reading easier.
pastaq
commented
1 year ago Run it as sudo
ghost
commented
1 year ago Sure thing. Sorry about that.
Identified host system as AIR Pro and configured defaults for AYA_GEN2
Attempting to grab controller device...
Found Microsoft X-Box 360 pad. Capturing input data.
Attempting to grab keyboard device...
Found AT Translated Set 2 keyboard. Capturing input data.
Attempting to grab power device...
Found Power Button. Capturing input data.
Gyro device not initialized. Ensure bmi160_i2c and i2c_dev modules are loaded, and all python dependencies are met. Skipping gyro device setup.
[Errno 108] Cannot send after transport endpoint shutdown
Hmm, I'll need to research that error some.
Can you run
sudo i2cdetect -l and sudo i2cdetect -y -r 1
ghost
commented
1 year ago sudo i2cdetect -l
i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-2 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
i2c-3 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
i2c-4 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter
i2c-5 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-6 i2c AMDGPU DM i2c hw bus 1 I2C adapter
i2c-7 i2c AMDGPU DM i2c hw bus 2 I2C adapter
i2c-8 i2c AMDGPU DM aux hw bus 0 I2C adapter
i2c-9 i2c AMDGPU DM aux hw bus 1 I2C adapter
i2c-10 i2c AMDGPU DM aux hw bus 2 I2C adaptersudo i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- I hope the gyro isn't faulty on my device, would be annoying to send it in for a replacement. :smile:
pastaq
commented
1 year ago Hmmm, it's not on the same bus as normal. In that last command replace the 1 with 0.
ghost
commented
1 year ago sudo i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- try this
lsmod | grep i2c
ghost
commented
1 year ago lsmod | grep i2c
bmi160_i2c 16384 0
bmi160_core 20480 2 bmi160_i2c,bmi160_spi
i2c_piix4 36864 0
i2c_dev 24576 0Drivers appear to be loading but for some reason its not available at bus 1 address 68. I wonder if they connected it differently?
Can you post the output of that command for the busses 2-7 please?
For reference, this is what my Non pro AIR shows for the two you provided already.
[gamer@chimeraos ~]$ sudo i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
[gamer@chimeraos ~]$ sudo i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- 2b 2c -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 4
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- 41 -- -- -- 45 -- -- -- -- -- -- -- -- -- --
50: -- -- -- 53 -- -- -- 57 -- -- 5a -- -- -- 5e --
60: -- -- -- -- 64 65 -- -- 68 -- -- 6b 6c -- 6e 6f
70: 70 -- 72 73 74 -- 76 77 sudo i2cdetect -y -r 5
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 6
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 7
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- You might want to test in windows if your device is fully working. They have use 1x68 for all their other devices, including the non pro version of the air. I'll leave this open for now in the hopes we can get another pro user to test it.
ghost
commented
1 year ago @pastaq just spent the past hour disassembling and putting the stock SSD back in with Windows on it, installed handheld companion and gyro is working perfectly so I don't know what's going on in linux.
pastaq
commented
1 year ago At least we know your hardware is working. I'll need to do some digging to figure out that error. Thanks for everything so far.
pastaq
commented
1 year ago Updated the name for this issue. It seems to affect the following devices:
I also briefly had this issue on my Aya Neo 2021 Pro but a reboot resolved it.
I looked at the DSDT for the Mini Pro and the AOK ZOE and they both have the address 0x68 as expected configured in the firmware.
@ghost573 can you upload your DSDT as well? I'd like to confirm the same for the AIR Pro.
Instructions:
sudo pacman -Sy acpica
cd ~/
sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
iasl -d dsdt.datThen upload dsdt.dsl here If I can confirm the i2c address then it will have to be an issue with the driver in some way. I'll put together a gyro test script to see if we can't get it to initiate in a more simple environment.
ghost
commented
1 year ago @pastaq no problem.
pastaq
commented
1 year ago @pastaq no problem.
Awesome, thanks. It appears to be the same as the other devices I've seen. I'll whip up a test script in the next few days.
pastaq
commented
1 year ago journalctl from AOEZOE A1 revealed this interesting error:
Nov 29 12:28:00 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: supply vdd not found, using dummy regulator
Nov 29 12:28:00 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: supply vddio not found, using dummy regulator
Nov 29 12:28:00 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: mounting matrix not found: using identity...
Nov 29 12:28:00 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: Error reading chip id
Nov 29 12:28:00 chimeraos kernel: bmi160_i2c: probe of i2c-BMI0160:00 failed with error -121An AOKZOE user noted that in windows the BMI160 returns a device ID of 27 vice 0xD1 as specified in the kernel driver. If anyone else tracking this issue is able to probe the device ID and post the value that would be great. I'd like to confirm if this is the same issue across all devices.
The GPD WIN4 uses a BMI260 which currently is not supported by the kernel driver.
Both of these issues will require a kernel patch.
ghost
commented
1 year ago Not sure how to do this in windows but I'll be happy to open my Air Pro to reinstall the stock windows SSD again tomorrow.
pastaq
commented
1 year ago Not sure how to do this in windows but I'll be happy to open my Air Pro to reinstall the stock windows SSD again tomorrow.
Sorry, I misspoke. Seems the user gets the ID in dmesg on Linux, not in windows.
Nik123456789010
commented
1 year ago Hi! I came from HoloISO to Chimera OS, at HoloISO Gyro works (with stutter), i have a buzz by activating. Now at Chimera there where no buzz, may i can help you with with some logs from my Aya Neo Air? A question, how get HandyGCCS updates (in Chimera OS) Thank you!
pastaq
commented
1 year ago Hi! I came from HoloISO to Chimera OS, at HoloISO Gyro works (with stutter), i have a buzz by activating. Now at Chimera there where no buzz, may i can help you with with some logs from my Aya Neo Air? A question, how get HandyGCCS updates (in Chimera OS) Thank you!
Sure. I'll need the output of the following commands:
lsmod | grep i2c
journalctl -u handycon
journalctl -b | grep i2c
sudo i2cdetect -y -r 1
Nik123456789010
commented
1 year ago [gamer@chimeraos ~]$ lsmod | grep i2c bmi160_i2c 16384 0 bmi160_core 20480 2 bmi160_i2c,bmi160_spi i2c_piix4 36864 0
[gamer@chimeraos ~]$ journalctl -u handycon Dec 23 21:46:37 chimeraos systemd[1]: Started Handheld Game Console Controller >
[gamer@chimeraos ~]$ journalctl -b | grep i2c Dec 23 21:46:36 chimeraos kernel: Goodix-TS i2c-GDIX1002:00: supply AVDD28 not found, using dummy regulator Dec 23 21:46:36 chimeraos kernel: Goodix-TS i2c-GDIX1002:00: supply VDDIO not found, using dummy regulator Dec 23 21:46:36 chimeraos kernel: Goodix-TS i2c-GDIX1002:00: Unexpected ACPI resources: gpio_count 1, gpio_int_idx 0 Dec 23 21:46:36 chimeraos kernel: Goodix-TS i2c-GDIX1002:00: ID 927, version: 0040 Dec 23 21:46:36 chimeraos kernel: Goodix-TS i2c-GDIX1002:00: Invalid config (0, 0, 0), using defaults Dec 23 21:46:36 chimeraos kernel: input: Goodix Capacitive TouchScreen as /devices/platform/AMDI0010:00/i2c-0/i2c-GDIX1002:00/input/input5 Dec 23 21:46:36 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: supply vdd not found, using dummy regulator Dec 23 21:46:36 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: supply vddio not found, using dummy regulator Dec 23 21:46:36 chimeraos kernel: bmi160_i2c i2c-BMI0160:00: mounting matrix not found: using identity... Dec 23 21:46:37 chimeraos iio-sensor-prox[512]: Could not find trigger name associated with /sys/devices/platform/AMDI0010:03/i2c-1/i2c-BMI0160:00/iio:device0 Dec 23 21:52:44 chimeraos dbus-daemon[453]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.92' (uid=0 pid=9995 comm="sudo i2cdetect -y -r 1") Dec 23 21:52:44 chimeraos sudo[9995]: gamer : TTY=pts/0 ; PWD=/home/gamer ; USER=root ; COMMAND=/usr/bin/i2cdetect -y -r 1 Dec 23 21:56:50 chimeraos dbus-daemon[453]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.94' (uid=0 pid=10066 comm="sudo i2cdetect -y -r 1") Dec 23 21:56:55 chimeraos sudo[10066]: gamer : TTY=pts/0 ; PWD=/home/gamer ; USER=root ; COMMAND=/usr/bin/i2cdetect -y -r 1
[gamer@chimeraos ~]$ sudo i2cdetect -y -r 1
[sudo] password for gamer:
Error: Could not open file /dev/i2c-1' or/dev/i2c/1': No such file or directory
pastaq
commented
1 year ago @Nik123456789010 seems the i2c_dev driver isn't loading
sudo vim /etc/modules-load.d/handycon.conf
add a single line to that file i2c_dev
Reboot
pastaq
commented
1 year ago I think these devices may have a BMI260. The WIN4 has a BMI260. I found a driver in ChromiumOS we might be able to modify. It correlates to the device ID in the AOKZOE.
https://chromium.googlesource.com/chromiumos/platform/ec/+/master/driver/accelgyro_bmi260.h
https://chromium.googlesource.com/chromiumos/platform/ec/+/master/driver/accelgyro_bmi_common.h
https://chromium.googlesource.com/chromiumos/platform/ec/+/master/driver/accelgyro_bmi_common.c
Nik123456789010
commented
1 year ago @Nik123456789010 seems the i2c_dev driver isn't loading
sudo vim /etc/modules-load.d/handycon.confadd a single line to that filei2c_devReboot
Yes, and there was the buzz, thank you! I testet it at Aperture Desk Job, there was also gyro stutters.
Aya neo air pro (5825) gyroscope support? THANK you