Android 2.2 umass -> da failure

[Adam Vande More]

I'm having some trouble get my android phone's usb storage to work.  It did
work at first and I was able to mount the SD card and transfer files.
Something has changed however and I'm not sure what.  Here's a dmesg from a
failed attempt to assign the device:

 ugen1.4: <LG Electronics Inc.> at usbus1
umass0: <LG Electronics Inc. LG Android USB Device, class 0/0, rev
2.00/1.00, addr 4> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:8:0:-1: Attached to scbus8
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid
field in CDB)
(da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): SCSI sense: Error code 0x72
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
(da0:umass-sim0:0:0:0): lost device
(da0:umass-sim0:0:0:0): removing device entry

FreeBSD 8.2-PRERELEASE #5: Thu Nov 25 19:14:00 CST 2010
adam at galacticdominator.com:/usr/obj/usr/src/sys/GENERIC  amd64

So as you can see no /dev/da0 is created, although a /dev/passX is.  I've
got two micro SD cards and both result in the same current symptoms.

Perhaps a quirk is needed?  I can handle the quirks file well enough to add
one, but I don't have the knowledge to know if that is the problem or what
particular quirk can resolve it.

My usb device is as follows:

galacticdominator# usbconfig -u 1 -a 4 dump_device_desc
ugen1.4: <LG Android USB Device LG Electronics Inc.> at usbus1, cfg=0
md=HOST spd=HIGH (480Mbps) pwr=ON

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0000
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x1004
  idProduct = 0x61cc
  bcdDevice = 0x0100
  iManufacturer = 0x0003  <LG Electronics Inc.>
  iProduct = 0x0002  <LG Android USB Device>
  iSerialNumber = 0x0001  <A000002872E308>
  bNumConfigurations = 0x0001

-----------------------------------------------------------------------------------------------------------------------------------

Additional info

It seems have something to do with how fast your at pressing the "Turn on
USB Storage" on the Android interface.  After connecting the usb device, if
you wait a couple of seconds before pressing "Turn on USB Storage" button
you won't be able to get a /dev/daX.  camcontrol functions don't seem to
work to get a /dev/daX either, a physical unplug, plug-in, quickly press the
button is the only way I've found to mount the device.

-- 
Adam Vande More