Page 2 of 2 FirstFirst 12
Results 21 to 33 of 33
  1. #21  
    The Acura HFL does not work with the Treo correctly and it is listed as not (http://www.handsfreelink.com). I have Acura TL and every few days I get in HFL booting up loop which disable all my audio functions (XM, CD, Radio...). The easier way to fix this is disconnect the battery (negative lead) for a moment. This is with latest SprintPCS patch.
    -Flash123
  2. #22  
    Quote Originally Posted by flash123
    The easier way to fix this is disconnect the battery (negative lead) for a moment. This is with latest SprintPCS patch.
    You are kidding right? Disconnecting your battery is the workaround?
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  3. #23  
    Nope. I ask the technicians if they knew the fuse(s) that could allow the same function of disconnecting the battery. They indicated the Radio and ACC fuses should but this did not work. At least, my settings for my audio were still available after the battery was disconnected and reconnected. HFL was still showed booting after I got back my audio until I somehow get HFL to talk to the Treo after each incident.
    Last edited by flash123; 06/19/2005 at 10:06 AM.
    -Flash123
  4.    #24  
    Welllllll my MDX works "OK" - reliable and clear exceot for the first call issue I noted - which is consistent and has a simple workaround - call, wait for it to drop BT, then hang up and all calls after that are fine...
  5. #25  
    Well, bad news fellow Acura owners. I just applied the latest PalmOne firmware patch (1.12 http://www.palmone.com/us/support/do...er/sprint.html ) and I am STILL getting the "first call no connect" issue. I was hoping the patch would solve that problem....no such luck.

    Oh well, it could be worse AND the new P1 patch solved a lot of other problems. Let me know if anyone has any success because it did not work for me.
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  6. #26  
    Well, the patch 1.12 Treo does not seem to effect my HFL before the patch 1.08 (HFL says BOOTING UP and audio system is out to lunch after period of use). Also, patch 1.12 does show the signal bars with this update on the HFL. I am unable to transfer numbers via bluetooth if that is even possible. I am still trying to figure out if I have to have discovery on or off in order for the phone to be noticed by HFL. For some reason, I do not know if it is the phone or HFL that needs help to have the devices to notice each other first time in the morning or long periods in between using the car.
    -Flash123
  7. #27  
    Having exactly the same problem. Will play with it to see if there is any improvement. Thanks for the update.
  8. #28  
    The HFL in my 05 Acura MDX worked perfectly for 4 months. All of a sudden, I'm getting the problem where making an outgoing call never dials the first time - but goes through the second time. I can't figure out what changed. I tried to repair, but that didn't help. Has anyone solved this problem? I have the latest 1.31 Cingular update and have not had a problem until a few days ago. Thanks.
  9.    #29  
    Quote Originally Posted by horatio8
    The HFL in my 05 Acura MDX worked perfectly for 4 months. All of a sudden, I'm getting the problem where making an outgoing call never dials the first time - but goes through the second time. I can't figure out what changed. I tried to repair, but that didn't help. Has anyone solved this problem? I have the latest 1.31 Cingular update and have not had a problem until a few days ago. Thanks.
    Wow mine has never worked without the first call issue. First call goes through if I initiate from HFL but first call from Treo always goes back to phone..then second call works ok.

    I am at latest firmware = 1.12 Sprint. Anyone got HFL without first call issue on SPrint?
  10. #30  
    My problem sounds a little different then what I'm hearing from others.

    1. Push HFL on the Acura MDX
    2. Call Home - the system responds "would you like to call home"
    3. Yes - the system responds "calling"
    4. The bluetooth symbol on the Treo's phone screen turns from "B" to the headphones symbol - but the phone never dials
    5. The only work-around is to push the HFL rocker switch towards back (cancel) - the car system stays in HFL and won't exit - next I repeat the "call home" sequence and the phone finally dials
    6. Trying again doesn't work - to initiate a call from HFL I always have to try twice

    Incoming calls work fine. It's really frustrating because the problem only arose after 4 months of no problems. Another work around is to initiate the call on the Treo and use the transfer command on HFL.

    Does anyone else have the same problem? Thanks for reading through this.
  11. Jasper2k's Avatar
    Posts
    15 Posts
    Global Posts
    16 Global Posts
    #31  
    Quote Originally Posted by horatio8
    My problem sounds a little different then what I'm hearing from others.

    1. Push HFL on the Acura MDX
    2. Call Home - the system responds "would you like to call home"
    3. Yes - the system responds "calling"
    4. The bluetooth symbol on the Treo's phone screen turns from "B" to the headphones symbol - but the phone never dials
    5. The only work-around is to push the HFL rocker switch towards back (cancel) - the car system stays in HFL and won't exit - next I repeat the "call home" sequence and the phone finally dials
    6. Trying again doesn't work - to initiate a call from HFL I always have to try twice

    Incoming calls work fine. It's really frustrating because the problem only arose after 4 months of no problems. Another work around is to initiate the call on the Treo and use the transfer command on HFL.

    Does anyone else have the same problem? Thanks for reading through this.
    I had EXACTLY the same situation as yours with my 650 and the Chrysler UConnect (made by Johnson Controls, same as the Acura?). What I discovered is that my 650, updated with the Unlocked GSM 1.13 Updater direct from PALM did NOT update the Bluetooth with the Car Kit Updater - in fact, this 1.13 Updater actually REMOVED the updater; i.e. flashed it back to a previous version without the update!

    You can verify this, as per the Palm Support website, by checking the SIZE of the Bluetooth library - if it reads 223K then you do NOT have the Car Kit Updater in ROM, if it reads 543K then you do. My fresh 1.13ROW did not have the updater. What I ended up doing is hacking a custom ROM by pulling the CIngular 1.15 updater files, substituting them for the BT files in the 1.13ROW, and then flashing the custom ROM.

    Now, my 1.13ROW with custom BT / 1.31FW Treo 650 works perfectly with the UConnect system.

    I can give you more gory details if you'd like, but first check to make sure you actually have what Palm says they gave you in the 1.13ROW updater...

    Hope this helps someone else!!
  12. #32  
    My first call connect problem is gone now that I did a hard reset and did not reload Ringo. Is anyone using another ringtone manager that works with HFL (Mring, CallFilter, etc.) Thanks.
  13. #33  
    Quote Originally Posted by horatio8
    My problem sounds a little different then what I'm hearing from others.

    1. Push HFL on the Acura MDX
    2. Call Home - the system responds "would you like to call home"
    3. Yes - the system responds "calling"
    4. The bluetooth symbol on the Treo's phone screen turns from "B" to the headphones symbol - but the phone never dials
    5. The only work-around is to push the HFL rocker switch towards back (cancel) - the car system stays in HFL and won't exit - next I repeat the "call home" sequence and the phone finally dials
    6. Trying again doesn't work - to initiate a call from HFL I always have to try twice

    Incoming calls work fine. It's really frustrating because the problem only arose after 4 months of no problems. Another work around is to initiate the call on the Treo and use the transfer command on HFL.

    Does anyone else have the same problem? Thanks for reading through this.

    Resurrecting this thread

    Just bought a 06 MDX. Seeing exactly the problem described above.

    Has there been a resolution to this issue ? Any updates since ?

    -Kuntal
Page 2 of 2 FirstFirst 12

Posting Permissions