Treo 650

Well folks, I got a call from my local Toyota dealership today. They had received a call from Toyota Corporate after I placed a call to 1800-GOTOYOTA last week. They offered to have me come in this Wednesday with my Prius and phone and said they will call the internal Toyota Tech number live, while I'm there, to see if we can figure out how to get the devices working together! Now, I honestly doubt they'll be able to figure it out, but hey, at least they'll know there's a problem and hopefully help us identify who is responsible (i.e. PalmOne?).

I'll let you know how things go after the appointment.

EDIT: They moved my appt. to 12/6! DOH!

 

thanks for the update! i'm in the same boat, though i am having some fun with my treo650 working on my ringtones... (shameless plug - aaron's ringtones for the treo at handango)

anyway, since i suppose 650 owners will be checking this thread, here's a freebie i am playing with - make your treo say 'scotty, beam me up' in capt. kirk's real voice!

just navigate to this link on your phone

www.aaronstein.com/beammeup.wav

save it as a sound file. set as a ringtone in prefs. there seems to be a problem setting it as a tone for one of the one-touch buttons on the phone screen, but it works fine from prefs...

 

Made another attempt today at lunch to get things working. As reported peviously, the T650 thinks it's paired, but the Prius doesn't and just hangs on the discovery screen. Interesting thing though is that now, everytime I turn on the car, the first call from my phone is picked up by the Prius and it goes hands free. From then on though, nothing works until I turn the car off and on again. How frustrating. I'm going to call Sprint this afternoon.

 

pshady,

You are not alone. Here is a discussion of a similar problem experienced by an owner of an Acura TL.

Treo 650's Bluetooth inability to work with Acura TL.

As for me, I am waiting for the release of the new LG-PM325.

 

Some good news - though who knows how long we'll wait ...

Well Toyota & Sprint can't / won't be fixing this problem. It's PalmOne that will have to update their phone & make it work with the Prius (and other autos that have builtin bluetooth handsfree). I read on another forum that even the Audi (demoed as part of the t650 launch) has similar problems. Of course what Sprint *can* do is let PalmOne know the number of calls they've received on the problem. I'm not sure if they do this or how best to state the problem to them so they log it in a way that will count later. I do know that # of customer complaints certainly plays a big part in whether we fix a problem & when we fix it, where I work.

I did get some encouraging words from my contact at PalmOne finally. I had emailed him back at 11/21 and he answered right away saying he'd look into it. Now yesterday I got this message:

"FYI, I did talk to the bluetooth SW QA person...We are working on the Prius solution and while I can't comment on dates upon which we will resolve this (and the channel: carrier or patch), we have identified this as something we will address. Cheers"

 

The folks over at Treocentral claim to have found a patch.

http://discussion.treocentral.com/showthre...ead.php?t=63250

Haven't tried it, so don't know if it works, but it sounds really complicated for a non-techie.

 

Yeah, I think all of us should contact PalmOne about this problem. It seems that there are a few car models out there that have had the same problem with the Treo. I think PalmOne is probably the best way to get this problem fixed. I bought my car with Bluetooth hooked up just for the purpose of syncing my phone with it. And to not be able to use it dampers my spirits. It seems nowadays all I buy are Bluetooth products, and would really hope that someday all the products can work together. So lets all start telling PalmOne to fix this problem or else we'll go somewhere else to buy Bluetooth products.

 

Re: Treo 650 - From Palm 1 Website

Bluetooth® Car Kit Compatibility for Treo™ 650 smartphones


The application used to interoperate with Bluetooth® wireless car kits is called hands-free profile. The Treo 650 smartphone supports this profile, as defined by the Bluetooth Special Interest Group (SIG).

However, at this stage of Bluetooth technology adoption by automakers, each implementation differs based on the interpretation of the profile by the manufacturer. In addition, some automakers have added features beyond those defined by the SIG to enhance their users’ experience. At this time, palmOne is testing with select car kits in order to identify any interoperability issues and to provide a software update to users of these kits as soon as possible. Users will be able to install the update for the select kits and exploit the convenience of hands-free calling.

The update may work with other car kits as well, but palmOne cannot ensure compatibility with unsupported kits or that all features will be supported.

http://www.palmone.com/us/support/bluetoot...o650carkit.html

I hope they post a patch shortly.

Philipp Djang
New Mexico

 

The Treo survey wasn't working when I just tried it

 

Uploading the phone book to the Prius.

Since I am unable to upload my phone book from my LG PM-325 (due to its lack of OBEX) to the Prius, I am planning to borrow a friend's Treo 650 to perform the task.

Has anyone had luck uploading their phone contacts from the Treo to the Prius?

 

<div class='quotetop'>QUOTE(IsrAmeriPrius\";p=\"58501)</div>

Nope... you've got to be able to have the car recognize the treo before this can happen, and that is not presently possible until they fix the BlueTooth problem on the 650.

 

I had the 2004 Prius and it paired with the Sony Ericson, but would not fully connect with the Treo 650. Was hoping that there might be new software in the 2005 Prius that would fix the problem, but just got my 2005 Prius and it doesn't pair with the Treo 650either.

 

It's not a problem with the Prius, but with the Treo... lots of people are having the same issue.

 

Mine didn't work. I got an "incompatible device" error when installing it on my treo. it happened when I launched the installer.

any help?