Hey all, I was one of the lucky folks to get one of the ADK's at Google I/O but I am unable to use it on my HTC EVO for lack of an official Google update to 2.3.4. I've loaded the latest version of Cyanogenmod which is sporting 2.3.4 code but the AOSP version is missing the critical framework files for the USB accessory. I recompiled the kernel with all of the relevant USB accessory flags enabled and placed the permission XML and framework JAR on my phone but whenever I insert the ADK the log from the ADK spams out that it can't get the protocol number and the phone lags.
I've tried looking at dmesg and logcat but logcat is silent during the entire process and the only thing close to relevant in the dmesg logs is the following: http://dumpz.org/55759/ The accessory driver doesn't seem to be attaching to the device. The backtrace above is coming from the f_mass_storage driver instead. I'm not terribly familiar with kernel code but I can't seem to find a discrepancy between the code in f_accessory in my kernel tree (cm- kernel) and the trees available at Google's repos (msm/samsung trees contain f_accessory). An early boot dmesg shows that the accessory function is being initialized but that's the last message that it ever sends. Hopefully someone from the ADK team will catch a glimpse of this and shed some light :) -Ryan Loebs -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
