-
Notifications
You must be signed in to change notification settings - Fork 9
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
App doesn't work #25
Comments
working on some improvements right now that'll make it easier to debug some issues like this. After I get those finished I'll follow up on this. |
Try this debug build out. I encountered a very similar problem (#29) and was able to clarify the issue a bit better. You might be in luck. |
i was actually wondering if this was the same issue, thanks for linking the build! If it works then we have our answer, but if not then I'm working on improved debugging right now. |
haven't made as many improvements to debugging as I planned to since I've been pretty busy but can you uninstall the app (if you still have it installed), install the latest one from the Github releases page, try it, and if it's still broken, export logs from the bottom of the settings page and attach them here. |
(In reference to #29) Doesn't work. I don't see any HID fallback option in the settings. Before I first boot the app, I already have had added Thank you once again for the help! |
yea i havent added that option yet, my reply was meant for the author of this issue |
I've improved the ability to troubleshoot issues like this in the latest release (v2.3.0). Do you mind trying that out and exporting a log file for me to check out? You would just have to:
|
Same issue, just complains about not being connected. Used 2.3.0. Below logs and screenshot of the troubleshooting page. |
thanks for the logs! unfortunately I was a little bit conservative on how large I allowed the log buffer to be, so it dropped the earlier logs which contained the actual character device creation script output. I'll fix that soon, but from what I could see, everything looks like it should work. the "device unplugged" error says that, because in my experience, the underlying error is generally caused by the device being unplugged, but the error itself could indicate other problems. so basically (as I've previously seen mentioned in tejado/android-usb-gadget issues), this seems like a very weird issue thats gonna take some more troubleshooting. I'll do some thinking and research soon probably |
Describe the bug
Hello, the app always says "device not connected" (even tho it is) and when exporting debug log it says "error getting logs". The app didn't manage to make the phone a HID device so I used "USB gadget tool" (which I like to use more). No keys are being sent to the pc
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app should work as intended; be a keyboard app
Screenshots
It's only showing the built in error messages
Device details (please complete the following information):
Additional context
Keyboard emulation works on "Rucky" (a app for running ducky scripts)
I love the idea and I'm so happy someone did it because the old app "USB keyboard" doesn't work (Pixel 8 Pro has no 32bit support)
The text was updated successfully, but these errors were encountered: