So... Another guy who is unable to see any statement disputed without taking it as a personal attack, and responding in such kind...|
I'm sorry I replied to you in the first place, which I did in the hope that we might together find a different approach for a solution to the problem with devices that do not give any response at all with our current Android setups. But that hope was obviously in vain...
Since you apparently took my criticism of those specific Android apps as personal criticism of yourself, causing you to launch a new "no regard" attack at me in response, I suspect that no sensible cooperation is possible.
I will proceed with my reply anyway, as we do have some interests in common, but if it results in another 'flame' I'm out of here...
I will start with this, because to me, it's a glaring flaw in your argument. "USB Device Info" gives you just what it says: USB device info. Its only job is to tell you who the vendor is, what the product is, and what corresponding codes go with each. That's it.
ryjyd Posted at 2014-8-26 09:33
Yes, that's it. That's exactly what it's intended to do. And exactly what it fails to do with many of the USB devices I've connected to a BananaPi running the current Android 4.2 release (in any of its image file 'flavours', as they all lack required driver compatibility).
When testing those devices, pressing keys and pushing buttons has no effect whatever.
Every post I see, with something I don't know about, gets me on Google in a second to go find out what it is and what it does. You may benefit from a similar practice.
Which is exactly what I do as well. But no information from google overrides contrary information seen first hand.
That said, when the XBox 360 wireless receiver is plugged in and USBDI is running, it will see the device and tell details.
Yes, I assume this would be the case, since that was the specific USB device you described having tested.
And it was references like that to generic files and their functionality that led me to believe you were speaking of a more generic use than just for one specific gamepad brand. My description of USB device response failures did not concern any XBox device (which I've never had any and have no interest in getting).
From that you can make a generic keyboard file with "Vendor_####_Product_####.kl" as your format, and USB BT Joystick Center will read the bits pushed from the dongle to the system.
And that's exactly where I think your assumption is wrong. If the underlying Linux system completely disregards a connected unit, because it's not accepted by the low-level USB drivers, then there's nothing any app can do to change that, unless they're able to replace, extend, or otherwise modify existing low-level device drivers.
I would imagine if this app were modified, it could read bits from any USB input, but I'm not that good... yet. If you know of ANY app that reads the data from any USB device bit by bit, tell me what it is because I've scoured the net looking for it. You could hand-craft a .kl file by the next day that will read the data and output a desired effect on the system.
That is exactly what I did to get my F710 running, a few copy-pastes aside. If this means I'm learning how to write USB drivers, then I'm smarter than I thought, I guess.
I think what this ".kl" file editing achieves is merely to make the existing high-level drivers make better sense of the incoming data packets from low-level drivers that they would otherwise fail to handle correctly. But those files do not affect the low-level drivers at all, in their choice of whether to accept or ignore a specific connected device.
Here then is a challenge that requires no bucket of ice water. I know you have a K400r in your possession. I have the same one. Help me find a USB bit reader besides USB BT Joystick that takes any USB device and reads the bits pushed from it. Your file will be named Vendor_046d_Product_c52b.kl. You find a bit reader, and I will hand-craft the file myself. Look over it, scour it for malice, and when you are satisfied it won't hurt anything, plug it in and see if it works. No donation but time, no 24 hour limit. Either we both benefit or we both learn something.
I'd be willing to try this, though I doubt that any app is able to access what low-level drivers fail to pass on to the high-level system.
Sure. And the same methods can probably solve it for any device whose data packets give any response in these test apps. But it is the other group of devices, who trigger no response at all, that I am more interested in.
As for the XBox 360 receiver, which is the original subject of this thread you might notice, I'm quite certain that the info I've already provided, researched, and practiced will get full functionality out of it. It's simply a matter of translating the 1's and 0's to something the system understands. Nothing more. But, that's all of computing, isn't it?
And there we have the final insult making future cooperation unlikely.
A slap in the face at the end of a conversation effectively invalidates all that was said before it.
You could have done what I'll do now, which is simply to end the post without a personal comment (either way).