Top-end clip-on jacked headsets?

[vbuggy]

So the Samsung HS3000 I was using in the main does pretty much everything I want out of it. Properly pairs to two phones at once (HSP and A2DP), apt-x, decent mic, decent volume with anything I use.

http://www.samsung.com/my/consumer/...BHS3000UBECXME?subsubtype=bluetooth-solutions

The problem is that it's (like so many things Samsung) a usability nightmare when it comes to the UI. The side controls are overly fiddly, and to add insult to injury the front call button is way too easily pressable, leading to mis-dials of previous numbers - with disastrous results in a particular case, leading me to abandon it altogether.

The flat form factor Nokia BH series are a lot more usable and have positive controls that don't lend themselves to accidental activation. The problem is that they don't do multi pairing and don't have apt-x.

Why jacked headsets? I use both custom and generic fit multi-driver balanced armatures for commutes and I don't want to trade down.

Have I missed any other better designed, full featured jacked headsets?

 

[paperwastage]

nope.

I have the Sony MW1 which has the same front-button mis-click problems, and UI problems... guess Samsung and Sony hired the same designers (you get a screen with the sony though)

the newer version of MW1 is the SBH20 and SBH52 (and yet, they removed microSD functionality, and SBH20 doesn't have FM radio). both have 2-devices connect, SBH52 has HD voice. neither has APT-X though



EDIT1:
someone has MW1 and HS3000.. he says stick with the HS3000 if you have your own IEMs


maybe get a MW1 + put your music on a 64GB microSDXC, see how the quality is like directly on the device

http://www.inearmatters.net/2012/10/review-sony-mw1-smart-wireless-headset.html

http://www.head-fi.org/t/633873/review-sony-mw1-smart-wireless-headset-pro

For the second part, I did some basic RMAA measurements. Using MH1 as load, the result is actually pretty good. The frequency response is absolutely flat from 15Hz to 20kHz. In comparison, my Nokia BH-111 BT headset, which is decent sounding, has a big -6dB roll-off at above and below 10Khz and 100Hz. While everything seems good, the only result that doesn’t look particularly great is the stereo crosstalk – it matches the performance ofGT7+ headphone-out, but comes out 10dB higher than Clip+ or Fuze under similar load.

From what I have been told, MW1 actually pack a Wolfson DAC inside and the output circuit has been optimized for the MH1 to perform at its best – and I can really agree. As far as actual SQ of the BT unit itself, I’ll say it is pretty much on par with Sansa Fuze (or Clip+) and the new iPod Nano 7G when used with MH1. In direct comparison, both Fuze and Nano 7G have a slightly bigger soundstage, but otherwise all three are extremely similar sounding. If I have to make up a number to explain the difference in soundstage, I’ll say MW1’s soundstage is, maybe 10~20% smaller than the other two – and I don’t consider this a deal breaker at all.

So MW1 might not be an actual ‘audiophile level’ BT headset if you were to compare it to top-end audiophile digital audio player, but it is by far the best sounding BT headset I ever heard with performance matching the ever popular Clip+. While it might not appeal to those who already carry around a Clip+ (or Fuze) as part of their day-to-day listening gears, its true usefulness lies on turning any Android smartphone into a competent source, or just creating a wireless setup that actually sounds good. In my case, I have my MW1 connected to both GT7+ and Nano 7G for a true minimum cable rig.

 

[vbuggy]

Thanks. Anyone who tests with RMAA I'm leery of, especially someone who obviously considers himself a bit of an authority - so we'll skip the sound stuff.

It's a shame that no-one else apart from Samsung appears to have true dual-pair: I really find it useful to be able to take calls from and listen to two phones. Where it's advertised as multi pair (e.g. in Sony's BT headsets) it means HSP and A2DP can be bound to two different handsets - but it's usually far more unreliable than even the Samsung's occasionally squirrely controls, even assuming your phone doesn't grab both profiles and lock out other handsets (i.e. pretty much every non-Android handset).

It looks like Sony have a replacement for the M, in the form of the NW-M505 - it does support apt-x but it looks like Japan only right now. and again, I really don't need an MP3 player on the headset itself: Unless it's 'smart' (i.e. can go fetch podcast episodes by itself, etc) it's useless to me.

So I guess... out of options then?

 

[paperwastage]

It's a shame that no-one else apart from Samsung appears to have true dual-pair: I really find it useful to be able to take calls from and listen to two phones. Where it's advertised as multi pair (e.g. in Sony's BT headsets) it means HSP and A2DP can be bound to two different handsets - but it's usually far more unreliable than even the Samsung's occasionally squirrely controls, even assuming your phone doesn't grab both profiles and lock out other handsets (i.e. pretty much every non-Android handset).

hmm... on my MW1, I have to manually select the A2DP profile for the phone I want (i.e. multiconnect only grabs HSP for both phones, but doesn't grab A2DP from the phones). WHen I want A2DP from the other phone, I have to manually select it on the MW1. From your wording, I guess your Samsung device seamlesslf switches b/w A2DP from both devices?

I guess this is too much of a niche... find someone to kickstart a perfect dongle?

 

[vbuggy]

Hmmm. I guess I'll have to look at some sort of mod to make the call button less pressable in that case. Thanks for the comments anyway, if anyone else has any better ideas I'd appreciate it.