Hacker News new | past | comments | ask | show | jobs | submit login

Actually they don't use ADB but rather implemented their own USB protocol, which is why it doesn't work on current devices. See also this rant here: http://romfont.com/2011/05/11/a-closer-look-at-googles-open-...



Thanks for the link. I had wondered how multiple devices would work. (Plus, it's nice to see that I'm not the only one who came to the same conclusion - just add support for USB OTG.)

This whole ADK thing reeks of hardware-done-by-software guys. (Which is just as bad as software-done-by-hardware guys.) (I also hesitate to use the word engineer in this case.)

The AT90USB micro-controller has the same AVR core as the Ardunio which they're leveraging, and with LUFA, does fine in OTG or USB slave mode, and there are PICs that do USB if that's more your thing.

Electrically speaking, there is very little difference between a USB slave and a USB master, but unfortunately that's not something that's correctable in software.

Android is running Linux (specifically the kernel), which has drivers for a number of things, including USB card readers, printers, numerous USB-serial converters including FTDI, and other, more esoteric hardware too. Why re-invent the wheel, or in this case, drivers?


As a software engineer I object to that! At least software engineers would have thought their design through, instead this this whole thing looks thrown together by a bunch of amateurs over the weekend. I think it's more a testament of the 'there I fixed it!' attitude that's the cause of so much Android-related WTFs in general.

As for LUFA, I'm working on a port of MicroBridge to AT90USB. I'll get working on it as soon as I receive the dev board.


You're right, so I updated my comment. :p




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: