What I'm wondering is just what compatibility issues is the company
going to resolve when they come out with the Treo version.
As I've tried and discarded a bunch of BT headsets, one thing I've
noticed is "not compatible with" seems to be a euphemism for "we
advertise a lot of things this headset can do, but probably not with
your phone."
For instance, the Treo650 doesn't support caller ID to the headset;
you can't voice dial through the headset, etc. etc. -- but some of them
were just dandy as long as you didn't care those things didn't work.
I was about to buy a Jabra JX-10, which boasted some pretty cool
noise reduction capability, but fell into the "not compatible with" trap
and didn't. But the time I learned the code, I'd gone through a few and
finally settled on a Cardo -- which is giving me fits (I think mostly it
needs a new battery but I haven't tried the company to supply one) so
I'm back in the market.
And the Jawbone is getting mostly good reviews, except it does not
physically fit some users, and I'm maybe going to try one, but if I buy
one now, what changes will the company make just after my 30-day return
runs out.
Sam Kamens wrote:
> Dan wrote:
>
>> On Wed, 11 Jul 2007 22:48:33 -0400, Allen P wrote:
>>
>>
>>
>>> I have been using mine with the 680 since Father's Day with no problem.
>>>
>>>
>> That's odd. I called them a few weeks ago and they said that they were
>> aware of the compatibility issues and they were working on a new model
>> for the Treo to come out at the end of the summer.
>>
>>
>>
>
> I seem to recall hearing that there were issues with certain networks -
> i.e. they might work for GSM and not CDMA or something like that.
>
> But I don't have one of these, so I can't really speak to it.
>
> sam
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
--
/"Thirty-five million deaths leave an empty place at only one family
table." /
(News commentator Eric Severied in a radio essay on the 25th
anniversary of the start of World War Two. 8/31/64)
[Non-text portions of this message have been removed]
