-
Notifications
You must be signed in to change notification settings - Fork 333
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
Should match with IOUSBInterface, not IOUSBDevice #2
Comments
Hi Rob. Here's a link to the USB prober tool (you can also get it in Apple's USB debug kits) for OS X. Can you launch that, attempt to tether your phone, and then click "Save Output" and attach the file here? I think what's going on is that HoRNDIS is not matching against your device because the descriptors may be slightly different than what it's expecting; if that be the case, then I should have a quick fix for you. Thanks, |
Hey Joshua, I tried the USB Prober app and it crashes. I tried looking for a debug kit and none of them are for 10.7.5. Thanks |
Gee, that's no good! What's the crash signature -- is there some particular library that's missing? I may be able to provide the missing dylib. Unfortunately, if it's not on Apple's site, I'm not sure where to find it, but in case something went wrong when I was zipping it, you can try [http://touch-base.com/documentation/USBMacProber.htm](one of the versions from this guy's site), too. |
I just now found USB Prober and got it running. It's in the Hardware IO Tools for February. Running the capture now. |
Is this what you're looking for? The USB Port status? Hub (EHCI Root Hub Simulation) @ 0xfa000000 with 6 ports |
I'm looking for the results in the 'bus probe' tab (importantly, the device and configuration descriptors). A "Save Output" in the bus probe tab should get the right thing. |
Ah, OK. I think it's only the XT912 section but here's all of it just in case: High Speed device @ 1 (0xFA000000): ............................................. Hub device: "EHCI Root Hub Simulation" |
Ok, I understand what's happening there. Yes, the descriptors are slightly different than that for the Galaxy Nexus. It will require a little more doing than I expected, but I think I see how to make that work. (The solution is, arguably, what I should have done in the first place.) Bed time now, but I'll try to do that tomorrow. |
I'm seeing the same thing with a Samsung Galaxy S3 (Android 4.0.4) on Tmobile on Mac 10.8.2.
|
Tristan, This looks like the same syndrome - the interface descriptor is okay, but the device is composite class. I'll have this fixed tonight. Thanks for the input. joshua |
Awesome! Thanks for your work on this On Thu, Nov 15, 2012 at 11:50 AM, Joshua Wise notifications@github.comwrote:
|
Tristan and Rob, can you test with rel1? |
It works for me - thanks Joshua! |
I'm still unable to get it to work although I'm seeing progress because I'm seeing HoRNDIS logs now. Let me know if you'd like for me to create a new issue. Thanks
|
Okay, that's new and exciting ... sigh. Yeah, let's create a new issue for this one. I wonder why it's sending an INDICATE, when no other devices do that. |
Devices like Droid RAZR, which have a device class of 0/0/0 (rather than 224/0/0), will not work, since currently we match on a device class of 224/0/0. We should match on an interface class to make sure we get what we want; if we do that, then we can match on the more specific interface class, as well, to avoid picking up CDC devices.
Original:
Subj: Tethering error with Mac 10.7.5 and Android 4.0.4
Steps:
Via kextstat I saw it wasn't loaded so I manually loaded it:
Tried to tether again and noticed these errors in kernel.log:
The text was updated successfully, but these errors were encountered: