-
Notifications
You must be signed in to change notification settings - Fork 66
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel 5.10 strange behaviour (Pixel 6a) #43
Comments
Hi, I don't have any phone with kernel 5.1 (yet), so I can't test it. I might try this on a Pi. I don't have any clue - sorry. Tjado |
Okok I see, no problem.
Well I started with the official Google rom from this month (Jan. 2023, https://support.google.com/pixelphone/thread/195623748/google-pixel-update-january-2023?hl=en) Then I realized that usb-gadget tool didn't work, so I installed a custom rom (GrapheneOS) (https://grapheneos.org/releases#bluejay-stable) thinking that I might have better luck but the result was the same. I've also thought about downgrading the kernel to try, but I'm still not sure how to do this on Android and I need to do more research. |
This is a dummy USB controller and not the actual one. I guess this is the issue. |
|
Great, then use USB Gadget tool as usual. But if you want to activate the respective gadget, e.g. MouseKeyboard, please test the following:
So I guess I need to adjust the controller detection in USB Gadget tool. |
Hmm, every time I try to overwrite the
|
What about the other gadget, the default one? Does it still has 11110000.dwc3 in it? Can you also paste the kernel log (dmesg) if you are writing to UDC? Thanks. |
The file was too big for Pastebin (You have exceeded the maximum size of 512 kilobytes per Paste.), I uploaded it on controlc.com
|
Thank you - can't see anything in the log which relates to this. If you can find out why this is happeing, it would be great. |
Update, when I setprop
Another strange fact, if I load |
Okay, interessting. Thanks a lot for the information. I will hopefully get a device with such a Kernel in the next days, so I can look more into that. Under Windows, do you get the same error in the Device Manager as the following issue? #42 If you are using hid-gadget tool, I can't help you there as I'm not using it. Try Authorizer. |
Oh so cool, that's good to hear then!
No, there is no error message, the phone is just not recognized at all by the computer when
Yes, I know but my test script works perfectly on two other phones, so it should also work in theory with the Pixel 6. But thanks for the info, I'll try Authorizer. |
Hey, any news concerning this issue? |
Unfortunately not. I thought I'm going for the Pixel 7a instead of 6a. So will get it in the next days and then have a look into that issue. |
Having a similar issue on the Pixel 6 (oriole). I edited the props as mentioned in #43 (comment) but I couldn't get any devices to detect USB HID mode. EvolutionX 7.9.7 (Pinakbet) for Oriole Kernel:
|
I have been using usb-gadget tool for a while on my Xiaomi 11 Lite (Kernel 4.14) and no problem.
But I recently purchased a Pixel 6a (kernel 5.10), /dev/hidg0 and /dev/hidg1 are present and enabled.
The strange thing is that when I execute a command on /dev/hidg0
e.g.
The output is reflected on the mobile phone itself instead of the device that should be connected (PC or another device ..).
For /dev/hidg1 the output is "Success" but nothing happen, seems my PC does not recognize my phone as an HID device, unlike my other Xiaomi phone running under kernel 4.14
Do you have any idea why it behaves this way?
Logs
The text was updated successfully, but these errors were encountered: