Just want to close out this thread with results/fixes. Please see url - http://www.google.com/support/forum/p/android/thread?tid=08945730bbd7b22b&hl=en
This will give some information on how to fix these issues on Linux. But in general, the correct udev settings are necessary and this help URL indicated the tools you can use to discover that information with USB. All my problems mentioned here were fixed and I can use ADB and Fastboot on linux without having to setup TCP as was mentioned here in this thread. The most importent changes are made inside the udev rules files to match your device VID. Also, no evidance that fastboot breaks ADB in anyway, as was mentioned in this thread. Hope this will help the next person that falls into this hole. /mpd On Wed, Mar 2, 2011 at 3:45 PM, mike digioia <mpd...@gmail.com> wrote: > Hi steve, > > This makes some sense. But the id is the usb product id. They have asked to > alter the product id on my linux ubuntu system to match what is in my device > kernel for usb product code. I have not done this yet, since the product > code should only change if the usb hw changes. It makes some sense to take > the adb source code and find where it has this code set and change it to > match the qualcomm device. I have not looked at the adb code yet. > > From an usb standpoint, I do not believe it cares about the product id of > the connecting device. Do you? Last I worked on the usb protocol was 2006. > > I still need to suspect this is an adb problem. Something is not working on > my device correctly that causes adb to malfunction. > > Did you get it to work by changing anything in udev? I will need to look at > the adb code and see why this happens. The pc vendors all have posted new > usb drivers for windows xp/7 for use with adb. Nothing for linux usb > drivers. So that seems to indicate that the usb driver needs to think it has > that unique product id. Turns out to be 0x5c6. > On Mar 2, 2011 1:36 PM, "Steve Modica" <mod...@small-tree.com> wrote: > > > > On Mar 2, 2011, at 4:20 PM, mike digioia wrote: > > > >> Yes this is the normal stuff everyone needs to do when it does not work > well. But my problem has been identified by Qualcomm engineers as a product > id mismatch. First they said it was caused by the pid (misunderstood to be > process id). But in the platform boards file USB has its product ID number > inside the usb struct. This id need to match the one used by the target > platform. > > > > I was fiddling with this in the udev files since fastbooting a phone > makes the id come out different. Maybe ADB has a hard coded value it's > looking for? Can you check that and just rebuild it when you build the > kernel? > > > > > > > > -- > > Steve Modica > > CTO - Small Tree Communications > > www.small-tree.com > > phone: 651-209-6509 ext 301 > > mobile: 651-261-3201 > > > > > > > > > > > > > > -- > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > website: http://groups.google.com/group/android-kernel > -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
