New Treo 650 ROM released! Bluetooth fixed?

Interesting...I have also noticed the hang up on call waiting. Was funny when my friends kept on calling me back. One would call me and then the other friend would wonder why I hung up on him. This happened 3 or 4 times consecutively

I'll have to look into this update. I'm the kind of person who believes in, "if it ain't broke, don't fix it". I've been having problems with my device rebooting while using versa mail so I'll probably install the update.

Regards,
Bit

 

Unfortunately the problem has _not_ been fixed with the ROM update. Call waiting hangup is still there.

 

Does the existence of this thread imply that the Treo 650 is more or less useful in the 05 Prius and can be Bluetooth-connected? I have never seen it listed in any literature.

 

I just discovered this call waiting hang up problem today and I've been using my Treo 650 in my prius for a couple of weeks now. What are you guys doing about this problem? Are you taking the phone off bluetooth when this happens? I love my Prius and I love my Treo 650(just upgraded from the Treo 600) and don't want to have to give up either one.


ChubbCo... yes, you can use the Treo 650 in the 05 Prius. It can be bluetooth connected but you do have to deal with the call waiting hang up problem until it gets fixed.

 

<div class='quotetop'>QUOTE(herbielb\";p=\"78255)</div>

Sorry to seem a bonehead, but you're saying that (other than the c/w-h/u problem) the Treo 650 and Bluetooth interfaces correctly with the Prius? Uses the display in the cara? All functional? Sprint too, or some other service?

I just bought my Prius two weeks ago and the salesman said it did not. (Which is why I still have the Treo 600...)

 

I have a Treo 650 from Cingular and it works for me. I haven't tried loading all my numbers into the car... well, because I don't want to. I don't know if you know this but you can't use the touchscreen display on the prius when your car is moving. So you can't actually make calls when your vehical is moving from the screen. Since the Treo 650 is such a dandy device I haven't had any problems with just using my quick dial buttons to make my calls. The calls show up on the screen and come out of the speakers. Oh I do pick up and end my calls by pressing the buttons on the screen. I don't know if this helps you at all but I have to say the Treo 650 rocks!

 

I just upgraded my Treo 650 (Sprint) to the new update 1.08 from PalmOne and I regret it. I only did this because I was prompted by not one, but three text messages from Palm or Sprint. First, instead of 30 minutes as stated by Palm, it took 2 hours because their lousy software updater is broken. For some reason the first time I ran the software, it did not ask me for the user name - it just installed the software on my phone and did nothing after that. It took me a while to figure out what happened and it ended up re-writing my Rom three or four times.

Though Palm claims the update includes the carkit patch (so it is now in ROM), it fails to even see the Prius at all. I go to the Prius screen for setting up Bluetooth, I have the 650 search for devices and it does not show up at all. This is worse than before.

Does anyone else notice that Palm really doesn't want to talk to it's users? I would like to reset back to version 1.03 and I can't figure out how. Lousy support.

If anyone else has luck with this update, please let me know. I don't expect any help from Palm or Sprint.

 

I don't have a lot of use for bluetooth, but out of curiosity I tried setting up a connection with my Sprint v1.08 Treo 650 & Prius.

There was no problem seeing the devices, but I had to use the same workaround previously documented for the Prius & Treo650 combination; wait till the Treo says it's connected, then initiate a call. Then the Prius will say it's connected.

However... after shutting down the car, and going into a store to pick up something, it wasn't able to connect. I haven't investigated further; I remember from the previous Treo/Prius discussions there was one other setting that might be needed, but I haven't verified & tried it to see if that helps.

 

I'd like to take a quick second to point out that neither Toyota or palmOne say that the Treo 650 supports a handsfree bluetooth connection for the Toyota Prius.

Here's the official list from palmOne.

For those who have gotten it to work, you may want to post detailed instructions for others to use.

You should also know that the 1.08 ROM update also makes more of the memory on the device available for you to use, so you probably don't want to try and flash back.

Glenn

 

Just an update... I tried (under the menu in the Bluetooth application) "Allow Wakeup" to be on.

After that, the connection happened correctly. I didn't have to re-pair, etc. and was able to make a phone call using the Prius steering wheel & MFD buttons.

So at least for me, a v1.08 Treo 650 is working with a 2004 Prius.

 

I am posting to say that I finally got bluetooth working with the new 1.08 update. I had originally gone into the setting screen rather than the new phone screen on the Prius, however the 650 would list the device under trusted devices (not new devices) and then it would keep pinging me for the pass code. This was somewhat misleading. In any case, once I used the new phone screen on the Prius, it all worked just fine (following the original directions mentioned by previous users.

 

Folks,

I had my Treo working with my 04 Prius before with the 1.03 ROM and the previous software bluetooth update kit. However, now that I applied the 1.08 ROM update, it is not working for me. I get an initial connection when I make a call immediately upon pairing, but subsequent calls appear to lost the connection.

Clearly, some of you have had more luck than I have. For those of you who got this to work I wanted to know, when you did your 1.08 update, did you follow the instructions for the greater than or less than 11MB of available memory?

I wonder if some of the differences in results folks have had could be a result of the different upgrade options?

Dave

 

Houseofyin: I used the "with 11MB or more free" method, I had 12.9MB at the time. I also went directly from the stock 1.03 unpatched to the 1.08 update, I didn't apply any other updates in between. My provider is Sprint, and with Allow Wakeup and keyguard turned off, I've had no problems. Once in a great while I'll see 'Bluetooth connection failed' when I start up, but usually it will show success a minute or so later.

I haven't yet had a call-waiting scenario, but I won't be surprised if that turns out to not work - overall, I'm happy with the compatibility I'm getting from a "non-compatible" pair.

 

I tried the "more than 11MB free" option, but it didn't work, so I tried the version of the instructions with the hard reset. I am not sure if that accounts for the difference in behavior, but I did get mine working.

After not working at first, I noticed when I went to work today the message "Bluetooth Connection Successful." I retraced my steps, and this is what I discovered.

After doing the pairing and then making a call I needed to "reboot" the car :+) I.e. if I tried to make a second call right away after first call used as part of the pairing, it didn't work. But if I turned the car off after making the initial call as part of the pairing, and turned the car back on, it was able to restablish a connection with the phone. I was able to make and receive calls as I had before the 1.08 upgrade.