Yep. The Android Bluetooth issues are pretty huge. I've written quite a few posts about my BT HFL problems on multiple forums.
One BIG issue may never get solved (or, may be quite a while if it can be solved): Voice dialing via the Bluetooth connection.
From what I've read, Google's architecture is different from all other phones out there: Google does real-time Universal Search voice recognition very frequently (and, even moreso with 2.1). Whenever you issue a voice command to your Droid ("Call Yoda at Work", "Navigate to Nearest Starbucks"), the analysis of that command does not occur directly on your phone. Instead, the audio is digitized/processed and sent up to Google's Voice Recognition servers. Then, Google sends the results back down to your phone.
When you have used the Voice Universal Search in the past, there has probably been a lot of times that Google will come up with wrong answers - especially when you are trying to do something dealing with the Contacts stored on your phone/GMail. I personally have had tons of problems.
An underlying problem with Universal Search is this: It's "universal" - many times with no basis for context of the voice request. Your Droid knows that you're asking for something, but it doesn't know why you are asking (or what you are really asking for).
So, if I try to issue a voice command to "Navigate to Joan Sellner" (who is stored as a Contact), Google seems to frequently search businesses before it investigates Contacts. As a result, I get directions to the nearest Long John Silver's. Google found lots of "hits" with similar sounding restaurants, and so it assumes it found the match for what I was looking for.
No other phone that I know of does voice searches in this manner. When you issue a "Call Joe Schmoe at Home" request on other phones, the audio is processed on the phone itself when trying to find a match.
Since Google searches everything, they had to come up with a priority scheme of what they would search for first when someone initiates a Voice Universal Search. It seems to me that Google selected businesses for the top of the pile.
If Google selected Contact Names to be first in the search order, then tons of people would be complaining about how their Android phones would be falsely matching to entries in their Contacts list instead of listing a restaurant they were trying to find.
I'm not saying that this particular issue is insurmountable (it's not), but I wanted to give y'all a heads-up on one of the reasons why this issue isn't being solved as quickly as we would like. This may only be fully solved when Google's Voice Recognition servers get much, much better at voice analysis.