Don't quote me guys...but a little birdie told me Audiovox is going to release the bluetooth patch this Friday, the 4th. Let's see if it really happens. I sure hope so.
Originally posted by acepero Audiovox Bluetooth patch coming 2/4!!!!!!!
Don't quote me guys...but a little birdie told me Audiovox is going to release the bluetooth patch this Friday, the 4th. Let's see if it really happens. I sure hope so.
But will it be released to the public? Or will it be released to to the phone companies (i.e. Verizon) so they can test it for the next 8 months before releasing it to the public?
I just got off the phone with Audiovox, and they expect to release the Bluetooth patch by the end of this week (Friday, the 4th) or sometime next week at the latest. The tech I spoke with told me that it will only be available for download on the Audiovox website, not through Verizon. The link is: http://www.audiovox.com/webapp/wcs/s...ductId=&brand=
This one will have an Audiovox name in it, and maybe a logo on the Setup.EXE file.
Undoubtedly they're hard at work downloading MSWLOGO's patch and slapping "Made by Audiovox" all over it
Smilies for the humor impaired:
On topic: I just got my Logitech Mobile Freedom. HOWEVER, the bluetooth manager from the system tray couldn't find it. The bluetooth manager from the Start-Menu->Programs could. I was always under the impression these were both links to the same file... but can't figure out how to verify/dispute this.
Originally posted by dmizock I just got off the phone with Audiovox, and they expect to release the Bluetooth patch by the end of this week (Friday, the 4th) or sometime next week at the latest. The tech I spoke with told me that it will only be available for download on the Audiovox website, not through Verizon. The link is: http://www.audiovox.com/webapp/wcs/s...ductId=&brand=
I loaded the 3500C on my XV6600 Rambo style. Got the memory error and used mswlogos' technique and it worked.
However my Jabra BT250 still sounded bad. I decided to return the headset and wait for my HBH-660.
Strangest thing... I turn the bluetooth off for 3 days and when I turned it on, I got the memory. THE PROBLEM IS NOW IT WON"T GO AWAY... no matter what I do. Turn phone off, reset, and turn on bluetooth. All sorts of combindation of reseting and turning phone off. Nothing will fix it.
Now I am really stuck.. basically my HBH-660 arrived today and I can't turn on my bluetooth.
First, BT is off from what I understand & you can't turn it on. No matter what you do, you get the memory error. So...
Turn ON flight mode. Then soft reset. Once back, turn on BT. Then turn off flight mode.
Basically, here's how I think about it:
- I am starting with a stack/heap space wherein neither the cell radio nor BT is on.
- I then turn on BT, so it gets it's stack/heap space allocated first, i.e., the BT memory space is allocated first thing after reboot. Allocating that BT space first is the trick.
- Then I can turn on the cell radio (i.e., turn off flight mode).
Thank you for the suggestion but I have already tried that combination and still mem error. It's really freaking me out now as it sounds like I may have to do a hard reset. I have a lot of software loaded and it will probably take me 3-4 hours to rebuild.
Wait..before you hard reset...if you haven't already...download a little prog called "check notifications"...it deletes duplicate instances of notifications and frees up mem. This seems to allow it enable bluetooth on my phone even though I have alot of programs.
DWIM... I activesynched my XV6600 and then went through the step again as you recommended (as a last ditched). It worked. I don't know why.. but wanted to let you know. Thank you very much.
I have check notification running already. What a great program.
This is a great forum.. thanks for your input.
====================================
Another question... I initially loaded the 3500C for my Jabra BT250. It didn't improve the static problem at all.
Now that i have the HBH-660. It is much clearer and much better. (The fit is problematic with my very large ear - I'll post later on how I plan to modify the hook). However, I would still like to have caller ID...so I am ready to "downgrade" to the 3500B version to get caller ID. Do I simply run the B cab file? Will that take care of install (Rambo style of course).
I think B can put it back (but I'm not 100% sure). Note that someone posted they had caller ID working consistently and learned they had to push a button or something to get it. You'll have to search for it.
Originally posted by acepero Audiovox Bluetooth patch coming 2/4!!!!!!!
Don't quote me guys...but a little birdie told me Audiovox is going to release the bluetooth patch this Friday, the 4th. Let's see if it really happens. I sure hope so.