It's because A2DP is terrible. It's at a level acceptable for voice conversations, but it's designation for music is way off. The sound quality puts Bluetooth to shame.
I just laughed a bit a the sheer daftness of your comment. Do you even know what the hell you're talking about? Two-channel stereo audio is what A2DP was designed for, specifically for the sound quality required for streaming playback of MP3s or other digital media from a mobile phone or DAP to bluetooth headsets or speakers.
Don't confuse headset Bluetooth audio with A2DP which is _more_ than acceptable for music.
I absolutely do know what I'm talking about. I've used A2DP on two occasions, and on both, the sound was equally awful. One was on a dedicated Bluetooth receiver which I promptly returned, and the other was with a friend's Bluetooth headphones. I have a regular Bluetooth headset, and I know the difference; While A2DP is a big improvement, it's just not good enough.
More likely than not, there was something wrong with either the Bluetooth profiles, or you paired the device but didn't properly get to use A2DP services over the standard headset/wireless audio gateway. I've seen it happen before and seen people start whining about it. A2DP support is, right now, pretty buggy at best in most devices.
Honestly, I think this is something specific to what your particular application is. I've got a pair of logitech Bluetooth A2DP headsets I routinely pair with my notebook and HTC Mogul. Sound quality is equally as good as a traditional pair of noise canceling MDR-NC60s.
“An engineer explained to us that hundreds of ear impressions were gathered in the name of research, and while each one obviously boasted its own unique shape and size, one single characteristic remained uniform across the board: the entrance into the ear canal is not a perfect circle, it's an oval.”
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
#1 These aren't so bad - I've seen worse
#2 A2DP musta been forgotten by most DAP manufacturers. For apple and Microsoft to not have it in their newest DAP is a shame.
Why isn't any manufacturer making use of OBEX and A2DP?
Samsung
Motorola (sortof)...
It's because A2DP is terrible. It's at a level acceptable for voice conversations, but it's designation for music is way off. The sound quality puts Bluetooth to shame.
@Eli,
I just laughed a bit a the sheer daftness of your comment. Do you even know what the hell you're talking about? Two-channel stereo audio is what A2DP was designed for, specifically for the sound quality required for streaming playback of MP3s or other digital media from a mobile phone or DAP to bluetooth headsets or speakers.
Don't confuse headset Bluetooth audio with A2DP which is _more_ than acceptable for music.
Nokia
@nerdtalker
I absolutely do know what I'm talking about. I've used A2DP on two occasions, and on both, the sound was equally awful. One was on a dedicated Bluetooth receiver which I promptly returned, and the other was with a friend's Bluetooth headphones. I have a regular Bluetooth headset, and I know the difference; While A2DP is a big improvement, it's just not good enough.
@Eli,
More likely than not, there was something wrong with either the Bluetooth profiles, or you paired the device but didn't properly get to use A2DP services over the standard headset/wireless audio gateway. I've seen it happen before and seen people start whining about it. A2DP support is, right now, pretty buggy at best in most devices.
Honestly, I think this is something specific to what your particular application is. I've got a pair of logitech Bluetooth A2DP headsets I routinely pair with my notebook and HTC Mogul. Sound quality is equally as good as a traditional pair of noise canceling MDR-NC60s.