I am using a Cingular 650 running software update 1.17 and have good phone functionality with signal strength but no battery strength passed to the MID.

Has anyone succeeded in getting a connection to Acuralink using a similar set up -and if so what are the exact settings/tricks to use?

Thanks

 

I have the same setup and as far as I can tell, that is all you will get. The best situation would include the battery. This bluetooth is headset compatable so you will never get the phone's contact list to download. You need to program the car with the numbers you want to quick call. My last 2 bluetooth systems downloaded the contact list from the 650.

 

the acuralink I believe will not link up to our cell phones as long as the onStar system is active. The info will come through onStar until the year service is up and then our cell phones should work through acuralink. This is what I was told by the dealer and hope they are right. I also am unable to link through my Treo.

 

The treo does not have dial-up networking which is required to use acrualink. We with treo's are SOL.

 

Some software/firmware versions for GSM phones do include DUN, but I have not been able to figure out how to get it to support the outbound call feature. Also, my 650 will only do Bluetooth OR DUN, but not both at the same time.

 

I have a GSM Treo 650 and 2005 Acura RL. On every call, I have to request through my Acura bluetooth pairing for each call the number to be dialed twice. First time, changes the Bluetooth symbol on the Treo to a headset. The call never goes through. So, I have to place the call a second time and it goes through.

Has anyone else experienced this and do you know of a fix?

Thanks,

 

JCarey

Is your HF Link set up as a trusted device on the Treo? I has to clear and repair mine to get it to connect and stay connected automatically

I also highly recommend 1.17 software patch for Cingular.

 

Yes, I have it set as a Trusted Device on the Treo. I have deleted and re-paired it a couple of times in hopes of getting it to work.

I have an unlocked GSM Treo running Firmware 1.71 and Software Treo650-1.20-ENA.

Any thoughts? Is this an Acura issue or Treo?

Thanks, in advance.

 

Did you notice any functional differences with the 1.17 update as compared with your previous version?

 

Signal strength was added I think. Other then that all I know is my phone doesn't randomly reboot anymore and a few other little things. Mine has always worked flawlessly with the RL though.

 

I would not recommend the Cingular update for an unlocked GSM phone. I too found better stability with the new version - only tends to reboot on first outbound call about one time in 5.

 

I have to attempt every call twice, which can't be correct. This leaves me with 3 possible sources of the error: Acura RL, Treo 650, or the pilot.

When attempting to make a call from the car, I press the phone button on the steering wheel and say " Dial XXX-XXX-XXXX". The RL responds with "Dial XXX-XXX-XXXX. Say Call, Dial or Continue to add numbers." I say "Dial" or "Call". When I do this, the RL responds "Dialing" or "Calling" based upon which I said. Then, on the Treo, the Bluetooth symbol located next to the signal strength indicator changes to a blue headset.

The call doesn't go through, I hear silence until it times out. I can hit the cancel/end button on the steering wheel and repeat these steps and the call will go through. Only difference here is: the Treo doesn't change back from the blue headset to the Bluetooth symbol. It stays as a blue headset and the call starts through the RL.

Any help or suggestions woudl be greatly appreciated.

 

Sorry, you got me on that one. Haven't had any problems with my Treo 650 and the RL. You don't touch the phone during the attempted all I assume. The volume is turned up in the car? Have the dealer check that out. Shouldn't be any charge.

 

On my '06 RL with a Sprint Treo 650, the very first call i make when i start the car pairs up to the HFL but then drops. I have to say "Transfer" to get it back to the HFL. All subsequent calls work fine. Weird.

 

hello everyone.. I'm having a hard time linking up to Acuralink with my treo 650. Can anyone help.

I have my phone linked up to the bluetooth..but everytime I receive a phone..I can't pick up the phone thru my car..even though i see the phone number thru the MID. Is this a problem with my bluetooth.. or am I screwed. thanks.

d-

 

Thanks for advising people with a Treo 650 and Cingular to update the software. I have 1.b07 and it has improved the connection between the car and the phone. Also, the signal strength is showing for the first time.

Now for my dumb question of the day: how do you get call waiting to work? If another call comes in while you're talking, how do you switch over?

 

I have a Treo 650 [Sprint] and have experienced some of the same problems those above have had. When I purchased my '06 RL, I called Acura and was told that if I wanted to use a Treo with Bluetooth, I had to go with Sprint. I specifically went to the Verizon store and was told that their software wouldn't work, so I had to change services. The most irritating aspect is that the system never recognizes the first phone call [incoming or outgoing] after I get in the car. I have to hit handsfree and say "Transfer". I sometimes receive the response "No phones have been found" and have to start it all over again. I was also have great difficulty getting the handsfree link to add additional numbers [estensions] to the phone calls. I finally determined that after confirming the main phone number, and saying "Call", I then had to say "Send"; wait for the voice prompt, then say the extension number [10]. for some reason, if i didn't say "Send" first, the system wouldn't hear the number "one" and would only hear "zero". Regarding Call Waiting, I believe that I have done it by just pushing the "handsfree" link button, to toggle back and forth.

 

This is absolutely not true. Your dealer should be skewered for giving that sort of information. Call Acura Care and complain.

So, yes, you should be able to get -a- phone to pair and operate regardless of your OnStar subscription status. Visit handsfreelink.com for officially supported phones.

 

I beg to differ. The acuralink has nothing to do with pairing with the hands free bluetooth. My phone pairs just fine even though it is not on their list of accepted phones. However it does not work with acuralink as many others have complained.

 

Acuralink requires BT pairing, since it is the only way the RL computer can send a mesage to the Acuralink server. However, not all BT phones have the capability for Acuralink outbound messages, which seems to be related to a phone's capability to support DUN (dialup networking) and HFL at the same time. I have tried all sorts of things to get my Treo 650 to call out, but to no avail. Howeer, my SE T637 worked great for HFL and made a call to the Acuralink server on the first try-go figure.

 

Acurafox is right.

Acura Link has two fundamental ways in which it either receives and/or sends data. I believe the owners manual probably also describes this, but I apologize if I'm in error on this point (It SHOULD if it doesn't already).

1. Broadcast data by XM (general messages, tips and the like) (one-way broadcast TO car)
2. Contact to Acura server by data connection USING the Handsfreelink Bluetooth phone (two-way data)

And ralteredstates you're right, specifically voice *handsfree* functionality has little to do with Acura Link. But Handsfreelink and Acura Link are co-dependent systems in other ways.

Generally:
-First, a phone must be paired with Handsfreelink in order for Acura Link to be able to even try to connect using the Bluetooth phone.
-Secondly, that paired phone must be able to support Bluetooth Dialup Networking (DUN). See further recent posts on this topic (https://acurazine.com/forums/showthread.php?t=1486) If the phone does not support DUN (or at least DUN doesn't work with HFL for whatever reason) you will see the message "does not support offboard diagnosis" next to the phone on the Handsfreelink site.

ralteredstates and others with Treo 650:As shipped, the Sprint's Treo 650 is the only Treo 650 supported by Handsfreelink
(http://www.handsfreelink.com/dev/fin...nu&mid=PalmOne). And, as theHandfreelink site shows, "does not support offboard diagnosis" (aka Acura Link).

Hope this helps and if you need assistance picking out a phone that does what you want both in the RL and in the OUTSIDE world, feel free ...

 

Acurafox is right.

Acura Link has two fundamental ways in which it either receives and/or sends data. I believe the owners manual probably also describes this, but I apologize if I'm in error on this point (It SHOULD if it doesn't already).

1. Broadcast data by XM (general messages, tips and the like) (one-way broadcast TO car)
2. Contact to Acura server by data connection USING the Handsfreelink Bluetooth phone (two-way data)

And ralteredstates you're right, specifically *handsfree* voice functionality has little to do with Acura Link. But Handsfreelink and Acura Link systems in the car share a lot of functionality and depend upon one another.

However:
-First, a phone must be paired with Handsfreelink in order for Acura Link to be able to even try to connect using the Bluetooth phone.
-Secondly, that paired phone must be able to support Bluetooth Dialup Networking (DUN). See further recent posts on this topic (https://acurazine.com/forums/showthread.php?t=1486) If the phone does not support DUN (or at least DUN doesn't work with HFL for whatever reason) you will see the message "does not support offboard diagnosis" next to the phone on the Handsfreelink site.

ralteredstates and others with Treo 650:
As shipped, the Sprint's Treo 650 is the only Treo 650 supported by Handsfreelink (http://www.handsfreelink.com/dev/fin...nu&mid=PalmOne).

And, as the Handfreelink site shows, "does not support offboard diagnosis" (aka Acura Link).

Hope this helps and if you need assistance picking out a phone that does what you want both in the RL and in the OUTSIDE world, feel free...

 

Just as an additional data point, the Cingular and ROW unlocked versions also support the Acura HFL-I have a Cingular-branded 650 and am running a debug version of the unlocked firmware on it, and it works great for HFL. I have been looking for a f/w version that will support DUN and BT at the same time, but I have not found one yet.

 

You bring up a good point. So, Acurafox, my understanding is: the Treo 650 connecting to Acura Link requires you to manually switch the phone to allow DUN and then back to handsfree. Is that correct?

My understanding is this is one of the reasons for Handsfreelink not officially supporting Acura Link/DUN ("offboard diagnosis") with the Treo 650 -- the lack of seamless transition from Bluetooth Handsfree to DUN and back to handsfree without the user having to manually intervene.

Apparently, like you mentioned, there are versions of the software in which DUN has been made to work.

Also, at least PalmOne/Sprint have made available an official ROM update for the Sprint Treo 650: http://www.palm.com/us/support/downl...er/sprint.html that enables DUN to work among other changes/fixes/enhancements but reportedly also has that same usability quirk and thus is also not officially supported for AcuraLink.

 

The 650 can only support either DUN OR BT, but not both at the same time, which I believe is the fundamental reason the Treo cannot transmit an outbound message to the Acuralink server. I use PDAnet with my laptop when I am out of the office, and it works the same way: when I switch to DUN to support PDANet, BT is disabled by default (I tether the Treo with a USB cable). A hack that solves this problem would be very well received by the Treo user community just for the PDANet app itself, since everyone that uses PDANet could then use their Treo as a modem without having to tether the phone to the computer. I have not yet found a firmware version (official or otherwise) that will allow the Treo to do both at the same time.

 

It is worth mentioning that DUN itself was disabled in the early versions of the Cingular and Sprint firmware, until someone discovered that the GSM ROW f/w had it enabled and that a locked GSM phone could be flashed with the ROW f/w. The theory at that time was that DUN was a potential competitor to the more lucrative MEdianet-type EDGE services that the SPs were (and are) selling for $25 per month and up, so they required that Palm disable that function in the firmware. I guess Cingular and Sprint decided not to fight it any longer after the cat was out of the bag, so to speak.

 

One minor clarification in all of this.

DUN = Bluetooth Dialup Networking Profile
HFP = Bluetooth Handsfree Profile

Handsfreelink uses both of these profiles. When you are doing handsfree voice calling etc you are using Bluetooth HFP. When you connect to Acura Link you are using Bluetooth DUN.

Consistent with what you mentioned, many if not most of today's Bluetooth handsets and phones do not support multiple simultaneous Bluetooth connections. The exception is mostly USB dongles and PCs.

Which is why most (if not all -- I don't know any that DO support multiple simultaneous Bluetooth connections) handsets must switch out of HFP and into DUN. The thing about the Treo, I understand (haven't used it myself) is that the user must intervene to cause that switch to happen rather than, say, on my Cingular RAZR where it occurs seamlessly without user intervention.

Hope that better explains what I was getting at.

 

Yes, you've hit the core of the issue regarding the enablement of Bluetooth DUN by the carriers in the phones they sell.

The astute observer or data user will see that most of the major carriers have recently worked out this billing loophole where the DUN user could get by with, say, the basic WAP data settings by which data is a lower-cost add-on to the account. This is about where my knowledge gets a little thin as I have not had much experience as of late using different data settings for different types of data accounts.

I do know that Sprint's new "Phone-as-Modem" plan(s) is the one that allows the user to connect using Bluetooth DUN or tethered connection (e.g., the type of data call that dials #777, e.g., for a 1xRTT or 1xEvDO connection) and I believe their billing systems are now robust in the sense that you cannot connect using the phone as a "modem" without being on that plan (can't authenticate/get through carrier gateway unless that phone-as-modem plan is what they call "attached" to the account).

Anyhow, I digress. Thanks for your input, acurafox.