neosolipsism

Done deal. Works a lil better, but would still like to use a mouse and/or keyboard.

Just put in a F900BT and not particularly satisfied with alot of the features, but none the less curious about the modability of it using WinCE. Obviously there's alot of potential here. In any case my issue is the touchscreen when trying to screw around in testmode. I cannot close the initial "Copying" window. Touching the X doesn't close the window. I can only drag it out of the way. I have similar issues with the menus (File, Edit, etc) -- no matter how fine of a stylus I use I just cannot click on any of these options. Same issue with the on-screen keyboard: I can't use the Enter

Power is not an issue. Pretty much every car stereo puts out about 20W onboard per channel. Not that it matters, as I have the highs on an amp anyway. I'm just annoyed that what Pio considers a $1200 deck is really just a small Windows computer with a radio, GPS, and DVD playback. I could put a standalone GPS and a non-nav deck in for half that and have a whole lot more features. Don't get me wrong, I've been a huge fan of the AVICs since they were first released. Have sold and installed dozens of them, but never put one in my own car as I didn't really have a need for nav. But now

Well I just went from a DEH-P6900UB (older motorized OEL CD/USB 1DIN) to a F900BT and all I have to say is I am not impressed. Haven't spent a whole lot of time screwing with it, but so far I'm contemplating putting my old one back in. Nav is great and all, but this deck is missing a bunch of features for its price range and has plenty of annoyances. First off, a DVD receiver with no 5.1? I don't particularly care for watching movies, but I can definitely see the advantage of DVD capability simply to take advantage of true surround sound. Nothing sounds better than a good 5.1 or SACD re

Note that just because the phone supports a profile doesn't mean the service provider supports the profile. Most smartphones support a number of more advanced profiles for wireless internet, printing, file-sharing, etc., whereas basic flip-phones tend to only support mono HFP & HSP for using hands-free earpeices.

Did a little research and did came up with only this on the BTB-200: it REQUIRES "Object-Push-Pull" (OPP) Bluetooth profiles in order to move phonebook entries between the radio and phone, whereas most headsets only require "Hands-Free" and "Headset" profiles. For those of you using stock Verizon phones, you can forget it, as Verizon strips their phones of OPP (most likely to prevent software piracy between phones by sharing ringtones etc). To the point: Make sure your phone & service provider allow OPP on your phone or it won't pair with BTB-200.

If its Verizon don't expect it to work right at all. Check to see if there are any updates for the phone. Sometimes upgrading the software fixes the problem.

Think the Jetware only works for smartphones such as the Treo.

I've spent countless hours talking to Verizon reps. They did have an update for the Treo I was having issues with (don't remember the exact model). Did the update, still wouldn't pair with BTB-200.

Look in the manual on your phone under Bluetooth details. Most Bluetooth phones at least support GAP, HFP, and HSP. These are the profiles associated with your average headsets and hands-free applications. There are lots of others, many of which relate to computer functions (Fax, Dial-Up Networking, FTP, etc.). You should be able to find a listing of supported BT profiles in your phone's documentation. I'm not 100% positive that OPP is what allows phonebook transferring, but I do know the Pioneer CD-BTB-200 utilizes OPP, and the only phones I've seen that I've been able to transfer pho

From what I understand the phone has to support OPP to transfer the phone book. If OPP (Object Push-Pull) is supported, it should be listed as a Bluetooth profile on your phone. I've seen plenty of phones that will pair with the BTB-200, but not transfer phonebook entries.

Had same problem. Verizon by chance?

Have a customer who originally had a Palm Treo (Verizon). BTB-200 sees the phone, phone sees BTB-200, but won't properly pair. He just went out and bought a mil-spec Gzone phone in hopes that it would pair. No such luck, still the same problem. So why the hell won't BTB-200 cooperate with Verizon phones?

Installed a BTB200 on a customer's D3 to connect to his Verizon Palm Treo. Worked fine for about a month, but now there's static on the truck end (through the speakers). Its not a geographical thing. Tried resetting the BTB200. Tried re-pairing the BT connection. Tried the Echo control. Tried resetting the phone. Tried bypassing the IP-Bus past the XM module. Running out of ideas here. Everything works just as it should, and the static really isn't that bad, but it is annoying enough to piss my customer off. Anyone else had problems with BT static in the speakers?