Finally got my Prime to work with my HTC!

[Rami98]

Hi Laurel,

At least on my part, I wouldn't like to return my jawbone - I really think it's very good (Aside from the fact it doesn't work...).

So I would very much like to help and solve the problem (In any case, I got it as a gift from a NY store - don't know which, so I can't realy return it).

More details:

a. Plantronics Voyager 520, works fine with htc.

b. Jawbone Prime works fine with NOKIA 6120.

After pairing the htc touch hd (WM6.5) with the 520,repairing with the Jawbone and viewing the BT related registry of my phone (didn't change anything, just compared the settings for the jawbone and the 520) it didn't disconnect for a couple of hours.

Did you already identified the root cause of the problem?

Thanks,

Rami

[Existentialism]

I'm in a similar situation. I can't return the item, because the item technically "works". The item isn't broken or defective, as far as I can consistently prove, it's a design flaw on YOUR part that causes it to not work with MY phone, or more specifically, HTC Phones. I would very much like it to work. The original Jawbone had no problems for me, and the 2 was a bit more problematic but worked fine. The prime however, has been nothing but problems. Have you at least been able to duplicate the issue? You should have access to a Diamond, or Touch Pro or some HTC Phone there. Although I would have hoped you'd have tested before releasing the device, the least you can do now is fix the issue.

[JawboneLaurel]

I can assure you that all our headsets go through very rigorous testing before we release them to the market. However, there is no way for us to tell every handset manufacturer how to configure the Bluetooth functionality in their devlices. As I have already said, we are aware of the problem, are working on solving it, but do not have a solution for you at this time.  I wish we did, but aside from getting a new phone or returning your Jawbone, there is no fix I can recommend. My apologies.

[Rami98]

The obvious question here, is what kind of time table to solve the problems we are looking at ?

[davsug]

just to reiterate, I've confirmed these same problems on a TMobile Dasg 3g(HTC Snap), Tmobile Touch Pro 2, HTC Diamond 2 and HTC Diamond 1.  I think that pretty much confirms the issue is mainly with HTC phones, which are the majority of Windows Mobile phones worldwide, so I would think you guys have tested agains HTC phones.  This problem has been known and documented for months.  It shouldn't take this long to either come up with a fix or admit that the Jawbone 2/Prime isn't compatible with HTC phones.

[Injurious]

 I was unaware this was a problem with the Jawbone II thought it was only the prime.....wow. Fail.

[davsug]

so are we to assume we're not getting any help on this problem?  I see compeitors, like BlueAnt, releasing firmware updates for their top of the line headsets like the Q1, but no support for our Jawbone Primes. This is obviously a major problem experienced by many people, so it's not a "faulty headset".  Will there ever be a fix?

[Existentialism]

Know that we are still waiting for a fix or at least an update.

[JawboneLaurel]

Unfortunately at this time we do not have an available fix.

[Rami98]

Did you at least mange to see and identify the problem?