On Wed, 08 Nov 2006 19:52:48 GMT, John Navas
<spamfilter0@navasgroup.com> wrote:
>On Wed, 08 Nov 2006 11:29:41 -0800, Jeff Liebermann
><jeffl@comix.santa-cruz.ca.us> wrote in
><7bb4l25tkvakom4t9p01vh02iqg0vausrd@4ax.com>:
>
>>There are also proximity and sharing issues. My XV6700 PDA phone has
>>both Bluetooth and Wi-Fi. I can see why Verizon disabled using
>>Bluetooth for listening to music. If I try to stream music from the
>>internet via Wi-Fi and listen to it via Bluetooth (after hacking the
>>registry), the music sounds like gargling ball bearings.
>Crappy implementation.
Worse. I forgot to mention that the XV6700 has Bluetooth 1.2 which
should have AFH (adaptive frequency hopping) which should prevent the
problem. However, I'm not sure if it's RF self-interference or the
CPU running out of horsepower that's causing the problem. It could
also be my Plantronics BT-3000 headset. Oops, the BT-3000 is only
Bluetooth 1.1. I'll try it with a BT 1.2 or 2.0 headset.
>My notebook computer has no problem doing that.
>And Wi-Fi shouldn't be an issue when playing stored music.
Your notebook also doesn't try to share the same antenna with
Bluetooth and Wi-Fi. I think (not sure) the XV6700 does. Checking:
| <https://gullfoss2.fcc.gov/prod/oet/cf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout =500&calledFromFrame=N&application_id=609145&fcc_i d='NM8PA10A'>
Sigh. The internal photos PDF appears to be fatally damaged.
However, there are some internal photos mixed in with the external
photos. Looks like 3 separate antennas for CDMA, BT, and WiFi.
| <https://gullfoss2.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=557710&native_or_pdf=pd f>
See page 6 of 9.
However, it appears that they changed to a different antenna in a
later version:
| <https://gullfoss2.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=576542&native_or_pdf=pd f>
I can't see the WiFi antenna so I'll guess(tm) that it's a common BT
and WiFi antenna.
>"Oops! Another feature doesn't work!"
Features and functions get added faster than bugs get fixed. The
inevitable result is a bloated buggy mess.
>"We don't have time to fix that too!"
Customer tested quality?
>"Should I just cripple it also?"
Of course. Call it an undocumented feature or "wireless streaming
media ready".
>"Yep -- documentation is so bad our dummies, er customers, won't know
>how to use it anyway!"
I think you saw the web page I scribbled just for setting up the
XV6700. It was a messy ordeal, even with the documentation. The
supplied documentation was tolerable, but for the previous firmware
version. I had to update from bits and pieces from all over the
internet. I don't think a non-geek could do it successfully.
If it were too easy, it would be no fun.
If the product were any good, it wouldn't need documentation.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
jeffl@comix.santa-cruz.ca.us
#
http://802.11junk.com jeffl@cruzio.com
#
http://www.LearnByDestroying.com AE6KS