ilBanker,
- to your point, "...that some headset work for some people, but not others...", this is something that has intrigued me from the beginning. As a recovering engineer I have tried to connect all the dots that are known in this anomaly ("that some headset work for some people, but not others"). For me:
1. this cannot be explained by variations in iPhone or BT headset hardware (antenna, RF circuits, etc). Such variations would only have impact if Apple's quality control were truly crap. (ok maybe it is but humor me for a bit in thinking it is not)
2. nor do I think this anamoly could be explained in variations in iPhone OS software (DSP, multitask algorithms, etc) since code is code is code, and we're all pretty much using the same iOS, 5.01 unfortunately.
3. what I think--and have thought for some time--is this problem is caused by some combination of installed and/or running apps, some additional combination of iPhone Settings, or, Apple's alleged 'echo-control mods' they instituted with iOS 4.
I am about 90% certain that Apple knows the root cause of this anomaly. My sense is that Apple is not correcting this problem because their Apple brand headsets work precisely because the echo control was tweaked, and 'un-tweaking' it would **** off those users. Conversely, if my assumptions above are reasonably correct, they obviously cannot acknowledging this huge freaking screwup, because they would expose themselves to substantial damages.
- to your thought, "...I wonder if somebody could contact C/Net or some media outlet like that who would publish this...", I think that idea is spot on.