Hi Kostya, well, I checked the Google Mass Storage USB device by mounting the phone as a disk -- it shows up as an "L" drive. I can then successfully navigate folders on the phone from my PC. If I then go to Device Manager and "disable" the Google Mass Storage device, then the "L" drive disappears from my "Computer" window. If I enable it, the L drive reappears. So it seems that the "L" drive (listed under "Portable Devices" in the Device Manager) is dependent on the Google Mass Storage USB device -- it doesn't seem like it has anything to do with ADB. But, I don't know...
Thanks for the info on the semicolon in the .inf file -- I suppose I should've looked that up somewhere before I decided to iterate everything. BTW, the Hardware Ids for the Mass Storage device look nothing like the other entries in the Android .inf file -- it's 7 lines of text -- no PIDs or VIDs in sight. Were you possibly suggesting I try to use one of those lines in android_winwusb.inf? I went to your blog & saw the illustration of the USB modes you could choose from. I tried similar things on my Ally, but was given no choices -- either USB debug mode on or off. Again, maybe there's some secret menu I don't know about. But, thank you for your time. If you have any other ideas -- or elaboration on how I might use your idea that the Google Mass Storage is actually ADB... I of course would welcome them. Or, do you know any resource at Google I could go to? I can't seem to find any way to ask the Android folks a question directly... Or any other resource? Alan On Aug 26, 3:31 pm, Kostya Vasilyev <kmans...@gmail.com> wrote: > Alan, > > You are right - the modem device has nothing to do with adb. > > I think the Google disk drive device might be what you need, i.e. actually > adb. > > No sense in changing lines starting with a semicolon in the .inf file, as > those are just comments. Devices are matches based on their vendor and > device ID's. > > Also, if your phone has multiple USB connection modes, you might want to try > different ones. My Moto Milestone only shows up in adb when I select "Portal > & Tools" connection mode in the phone (see my blog for screenshots, this is > in case your phone has something similar). > > If phone settings are correct, you should get an adb device in the Windows > device manager, with a yellow question mark at first. This is the device > whose vendor and device ID's you should use in the .inf file. > > I wish there was an easier and more consistent way to enable adb in > Windows..... > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com > > 27.08.2010 0:54 пользователь "Alan" <alans_1...@yahoo.com> написал: > > Hello Kostya, thank you for your reply. I knew I'd forgotten to > mention something -- I had tried what you mentioned, and after seeing > your post, I was encouraged to try again, but I still can't get it to > work. Here's what I did (shortened version!) > > 1) Turned debugging on on the Ally > 2) Plugged the USB in > 3) Looked at device manager: when I plugged it in, these things > appeared: > a) Under "Disk drives": GOOGLE Mass storage USB device > b) Under "Other devices:"LG Mobile USB Modem" > There are 5 "LG Mobile USB Modem" entries. If I look at the first > one, the Hardware Ids entry says: > > USB\VID_1004&PID_618&REV_0100&MI_00 > USB\VID_1004&PID_618&MI_00 > > The next one is the same except it says "MI_01" and so on incremented > for each of the entries. > > The "Device description" for each of the entries is "LG Mobile USB > Modem". > > 4) I cut and pasted the entry for "; HTC Dream" (the first entry) and > changed the entry to > > ; LG Ally > %SingleAdbInterface% = USB_Install, USB\VID_1004&PID_618 > %CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_618&MI_00 > > 5) That didn't work. I tried "LGE Ally", LG Mobile Ally", "LG Mobile > USB Modem", "Ally", "LG", "LGE"... all to no avail > > 6) Iterating in with that I started changing the entry itself to match > the others more by changing PID to "PID_0618". I tried putting the > "REV_0100" in. > > 7) I tried many things like the above. Nothing worked. Windows always > would come back and say (quickly), "Windows was unable to install your > LG Mobile USB Modem". It seems like that's a clue, since I want ADB > and not a modem, but I'm at a loss as to what to try next. The folder > I always gave windows to look in was the "usb_driver" folder within my > Android SDK installation. > > It could well be that I'm missing the particular combination of things > that'll make it work, but I don't know what it is. Any further ideas > would be greatly appreciated. > > Thank you again, > > Alan > > On Aug 26, 12:10 pm, Kostya Vasilyev <kmans...@gmail.com> wrote: > > > Alan, > > > Apparently all "adb"... > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" g... -- 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
