A trial tool was used, but that would not cause that problem.

What phone did you install it on.

3100 seems to have way less issues than 3500.

Nope... it was definitely the driver. The 3500 build on my 6601 shot back after I tried installing it twice that my trial license had expired. And that was after a hard reset, so it's not associated with the 3100 build. Sorry, but it looks like anyone who loaded the 3500 build may be in for a surprise today.

Eric

Brider,

Which phone?

Not many of us are running 3500. 3100 is reasonbly ok.

Update on Voice Command with build 3100.

Turning on bluetooth with the headset still left at home did not fix the problem with Voice Command not able to wake up the phone. Bluetooth on or off does not fix.

Once I got home and the headset was in range. Voice Command worked perfectly again.

I think the new bluetooth stack is stopping the phone from going into a deep sleep or staying in a deep sleep. I think it partially wakes up every few seconds. And asks, is the headset still there.

This does not seem to drain the battery.

You can see something a little interesting going on watching the active bluetooth connections with the headset paired. The strength goes up and down on a cycle.

The 3100 is finally stable on my 6601 and it seems to be working much better. I'm still disappointed that the 3500 didn't work because I wanted to check some of the new features. Ah well...

Thanks!

I have just installed the 3100 on my ppc6601. So far headset seems to work better. Will try on GPS shortly.

Still cannot open bluetooth manager w/o a soft rest, just get a beep. I can toggle BT on an off but the manager or settings options do nothing.

Thanks

I have just installed the 3100 on my ppc6601. So far headset seems to work better. Will try on GPS shortly.

Still cannot open bluetooth manager w/o a soft rest, just get a beep. I can toggle BT on an off but the manager or settings options do nothing.

Thanks

Just out of curiosity, try closing all your open (running) programs from settings/memory. Then try to open Bluetooth Manager.

Bingo

I'm still having problems with the 3100 build and my Motorola 810. After waking from sleep on the 6601, my 810 won't work until I toggle BT on and off. Now I have a problem where when it wakes back up it attaches and pushes nothing but static and white noise back at me. I know there's a movie coming out with Michael Keaton about EVP (Electro-Magnetic Voice Phenomena) and it looks facinating, but I'd rather have a conversation on my phone than speak to the dead through static... Any thoughts?

Eric

I called both Verizon and Audiovox yesterday. Both companies said that they were unaware of the bluetooth problem. If they know nothing about a problem, then I am sure that they are not working on a solution. 3100 installed on my xv6600 but did not solve any of my issues.
3500 gave out of memory error.

What issues you having and which headset.

Some folks with some headsets are doing quite well.

Although my headset is found every time now the audio quality can be awful. If i have the device in my top let shirt pocket and my jabra in my right ear the audio sucks. I have been using the headset with the enhanced partnership. I am going to try standard partnership to see if that helps.

As for all my other issues with bt on my 6601, they are all fixed.

Nice work.

installed 3100

__________________
Cingular 8525

Which of us are you talking to? I'm using the 6601 and the Motorola 810. Funny observation. When I'm plugged in and power on all the time, and I let it sit for more than an hour or so, the pairing still goes south. The phone rings but not in the headset. The indicator still shows that the pairing exists on the taskbar, but in reality its belly up. I'm getting close to returning the phone with this, the screech-of-death, and the loose slider.

Eric

I was just making a general comment to inform other users of a possible issue with the jabra. Please let me know if someone else is using the jabra with no issues. I am starting to think I have a bad headset.

__________________
Cingular 8525

I guess I should have said issue not issues. I am refering to the issue of losing my bluetooth connection after the unit goes into sleep/idle mode or if I power the unit off. I have tested Jabra 200 and Motorola hs810 headsets both with 3100 patch with no success

OK, so I installed the 3100 patch. Two days of no problems, then today, I got the insufficient memory error twice when I tried to turn on bluetooth, two soft resets, same error each time.

Then, I opened Settings>Memory and realized that the memory bar was in the middle, so I slid the bar all the way to the left. Soft reset and NO ERROR message.

Maybe the cab file reset my memory settings. I don't know, but I thought I would share this info to anyone who gets the insufficient memory error, but doesn't want to do a hard reset / restore.

RFK

__________________
Chunk Style

I would agree with you if you were right, but the Palm OS is crap.

Fat,

Great observation. I never thought to look at that when testing build 3500. Especially when nothing else was install.

Yeah man, check it out again, maybe with the memory maxxed out, you wont run into problems.

RFK

__________________
Chunk Style

I would agree with you if you were right, but the Palm OS is crap.

I've reworked yet another release from i-mate

This is Build 3500 again.

I have not tested it a lot.

I was runn 3100 and was running pretty good. Only quarks I saw were Voice Command could not wake up phone when bluetooth of or headset out of range. This appears fixed.

I also on occasion, usually when fiddling with other BT devices would get voice over BT not as clear as it should. This happened rarely and I don't know if its fixed.

I don't know if hard reset is required or not. I did.

Good luck. I report later how stable I think it is if you want to wait.

It's attached to the first post of this thread.