Ok... for the record, the ipod does NOT send audio through usb.
Just as I told y'all last March.
The iPod connector has many signals on it. Among these (depending on model) are USB, analog audio out, power, remote control, video, and Firewire (on older models). People may think of the iPod connector as "just USB", but it's not.
As well, a very small number of cellphones, such as the Motorola RAZR, multiplexed analog audio I/O on the USB connector. Basically, the phone detected USB, and if it didn't see the USB connection (probably by sensing the USB power), it would switch the headset signals in place of the USB signals.
USB is and always was a digital-only signal. And on most phones, you only have the USB Target interface -- the phone cannot initiate a USB transaction, only respond to one. So you can even have the phone push digital audio out to something else on its own, over USB. Some devices, like my Pioneer GPS, have USB host interfaces that can read data from a phone (or other USB device, such as a memory dongle or hard drive) and play it.. but that's the other device doing most of the work.
For digital playback on another device, with a modern smart phone, Bluetooth is your best bet.
While the connection to the pc may be usb, the audio signal is sent through different 3 different conductors of that same cable. When the ipod is connected to an aftermarket radio that will actually control the ipod, it is doing so through usb mass storage.
Actually, there are more signals there than you think.. the iPod connector has 30 signals, as well as a shield ground around the whole thing. There is a +5V power input, a +3.3V power output (allows the iPod to power small add-ons), and a bunch of ground signals. USB adds the two USB signals, plus a separate ground return for USB. Audio comes out on two pins, but there's only one audio return (ground), which is also shared with video. There are also audio input pins, which are line-level (-12dBV I would assume)... this is how add-in microphone devices get the audio into an iPod. For video, there are actually separate chroma and luma pins, like on an S-Video cable.
Remote units don't use USB just to control the iPod.. there's a 2-way UART, running at 19,200 baud.. more or less like the LANC connector on some camcorders... simple microcontrollers can talk to the iPod this way and give it commands, without the need to be a USB host, which is far more complex.
There's also an add-on sensing input... adding a resistor on this pin (pin 21, in fact), tells the iPod something about the device that's been attached.... different values indicate different devices.
The micro usb connector used to charge the DROID does have more conductors, but not enough to do audio without actually using the 3.5mm at the top of the phone.
The MicroB connector used on the Droid is essentially a thinner, rugged version of the Mini-B connector, which has 5 pins. These are used for power, ground, and the two USB clock/data pins. The fifth is technically to enable USB "on-the-go" devices, though this isn't supported on the Droid, despite the fact that it actually can support "on-the-go".
When USB was invented, there was a strict split between Target devices (keyboard, mouse, memory dongle, hard drive) and Host devices (your PC). This is different than, say, Firewire, in which every device is technically a peer... host USB devices are much more complex than target devices.
What they didn't consider was a device, like a PDA or Smartphone, that might want to do both... I might want it to be a target when connected to a PC, or a host when connected to some other device.... I have a camcorder, for example, that hooks to my PC like a storage device, but when hooked to a USB storage device, can do its own offloading of data to that device. This 5th pin is used for that.
The Mini-B connector enabled this, and was fine for the early days. But more recently, they've changed the specs. Today, an on-the-go device is only supposed to have the Micro-AB connector... that's the one that's about as thin as the Micro-B, but not as wide, and more square. When you have an on-the-go device (OTG), the cable you plug in tells the device, via this extra pin, that it's supposed to be a host... if it can be. That's why they change the connector spec... all devices with Micro-AB connectors are supposed to be on-the-go.
Of course, no cellphone will use this connector, even if it does add on-the-go, since the Micro-B is not the standard for phones, and it's also far more rugged than other USB connectors.
It would appear that the best way to get an audio signal to an aftermarket stereo, or any other device for that matter, would be through bluetooth.
Just as I wrote here back in March.
A friend of mine has one of the newer Kenwood in-dash nav/tv's and synced his DROID to it. VOILA!!!... not only did he have hands free calling AND get the audio from his DROID through his head unit, but he could actually access some (not all) of his apps from his head unit without ever having to touch his phone. The main app of interest to me was Pandora. And YES... full control over Pandora via the kenwood head unit.
Yup. Bluetooth is the right answer here, mainly because there are a whole bunch of standard protocols supported by it. USB devices may perform a few tricks... your USB device could present itself as storage, or maybe a sound card, but that's about all... and it would be hard pressed to do both.
Bluetooth has a large number of protocols. Not every device supports every protocol, but most GPS/Handsfree device and smartphones have some area of agreement. There's the "Handsfree" protocol, which actually combines the "remote control" and "Headset" protocols... you can push buttons on a foreign device that get sent, in standard ways, to your phone, and you can talk to it and hear back from it. There's also a hi-fi audio protocol... my GPS doesn't have this, but my Altec Lansing "Sound Blade" does, and sounds just dandy playing music back from the Droid. There's also the "Object Exchance" protocol, which lets data move back and forth -- so my phone sent my whole address book to my GPS using this. There's also a plain serial protocol, which replaces RS-232... my old PDA used this to talk to GPS dongles, for example. There's also a cordless phone protocol... most cellphone makers don't implement this, but if they did, you could hook into your home cordless phone system over Bluetooth and make calls from your cell over your landline. Curiously, I have a cordless phone that works the opposite way... I can make and answer calls from/to my Droid via that cordless phone.
My reasoning for wanting a one cable audio/charging connector is that I no longer want a head unit clogging up my dash board. I was running a pc in car for all multimedia and nav purposes. My mobo died and since then have been using my DROID coupled with an Audiocontrol Three.1. Still trying to fine tune the sound b4 I finish all the fab work. But one of my hang ups have been ease of connection. I may try to wire something through the micro usb, or just eventually give up and go with a blue tooth audio adapter.
You ought to use Bluetooth for the audio connection, and fix one of those Droid desktop cradles (or something like it) in the car to hold and power the Droid. Then you're virtually "zero" cable. And if a PC's in charge, Bluetooth is a done-deal, assuming you have a free USB port and $15 or so for the USB dongle. Linux and Windows support most Bluetooth protocols.