Treo 650 & 2004 Prius

Yep, mine works great too! And I am able to send my contacts to the Prius with minimal problems. The only problem I run into is if I have a name that has two numbers. The Prius only accepts the first one. So I believe that is a limitation of the OBEX Profile for the Prius and not the phone.

 

Yep, sent my 150+ at one time.

 

<div class='quotetop'>QUOTE(bmodell\";p=\"92389)</div>

Yes. From the contacts app, make sure you're viewing "All" as oppossed to a particular category. Then just choose send CATEGORY instead of send CONTACT.

First though, you might want to make sure your phone numbers are parenthesis & space free (dashes seem to be OK).

I also used excel to edit my contacts (exported from Outlook) & created a new contact for each extra phone number. If you do care about this, then make sure you give each contact only *one* phone number, or you may end up with the wrong one sent to the prius phone book.

*Finally* I also edited all the phone numbers to be prefixed with "*70" because that is the sprint code for disabling call waiting. This avoids call waiting hanging up your current call when a new one comes in.

 

Ah, good call on the *70. I didn't think about that. I have sprint as well and hate it when call waiting happends. Then both callers try calling me and all I end up doing is hanging up on them.

So what kinda of a programmer are you Delrey? I'm a J2EE Java Developer

<div class='quotetop'>QUOTE(delrey\";p=\"92726)</div>

Yes. From the contacts app, make sure you're viewing "All" as oppossed to a particular category. Then just choose send CATEGORY instead of send CONTACT.

First though, you might want to make sure your phone numbers are parenthesis & space free (dashes seem to be OK).

I also used excel to edit my contacts (exported from Outlook) & created a new contact for each extra phone number. If you do care about this, then make sure you give each contact only *one* phone number, or you may end up with the wrong one sent to the prius phone book.

*Finally* I also edited all the phone numbers to be prefixed with "*70" because that is the sprint code for disabling call waiting. This avoids call waiting hanging up your current call when a new one comes in.[/b][/quote]

 

Just wondering if anyone has a Treo 650 from Verizon? They just started offering the Treo and I was wondering if you can send the phonebook with the Verizon 650, or if they have disabled it as on their Motorola V710?

 

<div class='quotetop'>QUOTE(BitShifter01\";p=\"92751)</div>

Heh. That obvious huh? C++ and now C#

I think I got the disable call waiting prefix idea from a priuschat post, though it was some other prefix (must have been another provider). Of course this only helps if *we* call out. If we receive a call & then a 2nd call, then the first one will still be dropped. It's still well worth the trouble, fixes more than half the problem for me!

I'm wondering what my next career should be though. I like my job (and gadgets & figuring things out, as you can tell) but I don't *love* programming either. Part of our next project is being outsourced, and we've got development offices in Singapore and Shanghai ... maybe I'll post over in Fred's and get Prius people career advice.

 

Is anyone successfully using a GSM Treo 650? I've tried installing the Car Kit Update to no avail, and have even upgraded my firmware to the beta v 1.23 floating around to no avail. I've followed the various instructions from the various Treo-related sites that talk about this and still can't get the Prius to recognize that the Treo has paired with it.

FWIW, I have a Cingular Blue (AT&T) GSM phone.

 

Who is the carrier phone company for your Treo 650? Is it Verizon, Sprint, or others? Treo 650 will soon be made available from Verizon but there are concerns that the Bluetooth function may be partially restricted.

 

<div class='quotetop'>QUOTE(michalopoulosgk\";p=\"93194)</div>

I have Sprint. It appears from the early reports that the VZW treo 650 has the same capabilities as the sprint one - but I haven't seen a really strongly worded post with thorough test descriptions yet. Just "seems to work", etc.