On Monday, March 26, 2012 2:21:33 AM UTC-4, ramya mohan wrote: > > Hi, > > The following information is based on my understanding. > > Usually android update adb won't do that. > It actually updates the adb to the latest adb version. >
This comment in ~/.android/adb_usb.ini suggests otherwise: # ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT. # USE 'android update adb' TO GENERATE. # 1 USB VENDOR ID PER LINE. Certainly I can edit that by hand, but I'd rather our customers just install our USB driver package and have everything just work. Matt > on linux machine: > > modify the /etc/udev/rules.d/52-android.rules file to add the vendor id > to it. > > then restart adb,it should work. > I am not sure what happens with windows machine. > > Regards, > Ramya. > > On Fri, Mar 16, 2012 at 2:54 AM, Matt Reimer <mrei...@sdgsystems.com>wrote: > >> So I've made an INF file packaged up and signed, and I can install it >> using the Android SDK Manager. >> >> When I plug adb the device into a Windows computer and point Windows to >> the INF file, and edit ~/.android/adb_usb.ini by hand, adb works. >> >> My question is: how do I get the SDK manager to put the vendor id in >> ~/.android/adb_usb.ini itself? Running "android update adb" doesn't do it. >> >> Thanks for your help. >> >> Matt >> >> -- >> unsubscribe: >> android-porting+unsubscribe@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> website: >> http://groups.google.com/group/android-porting<http://groups.google.com/group/android-porting> >> > > > > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
