Weegie5

This has happened to me twice now. I installed the WIDCOMM stack so I can pair with my Garmin GPS. That works fine.

I then pair my Motorola HT820 headphones and they work fine- for about 2 hours. Then the sound cuts out of the headphones indefinitely (I only waited a few minutes). I turn the headphones off, and back on. Axim doesn't discover headphones. I delete the connection and try to re-pair them. Again, Axim can't discover the headphones.

I have to soft reset and then re-pair. Anyone else haveing a similar issue? Is there any fix for this? I can't imagine it's a driver issue since they work fine for the first 2 hours. WTF? Any insight would be helpful. Thanks.

~Weegie5

jhom

Originally Posted by Weegie5

This has happened to me twice now. I installed the WIDCOMM stack so I can pair with my Garmin GPS. That works fine. I then pair my Motorola HT820 headphones and they work fine- for about 2 hours. Then the sound cuts out of the headphones indefinitely (I only waited a few minutes). I turn the headphones off, and back on. Axim doesn't discover headphones. I delete the connection and try to re-pair them. Again, Axim can't discover the headphones. I have to soft reset and then re-pair. Anyone else haveing a similar issue? Is there any fix for this? I can't imagine it's a driver issue since they work fine for the first 2 hours. WTF? Any insight would be helpful. Thanks. ~Weegie5

I had the same issue with my HT820. There is a registry fix posted that solves the problem. Take a look at the Widcomm thread and you will find the fix.

Here is the fix:

UPDATE 10-23-2006: FLOWCONTROL FIX

A new solution for A2DP hangs has been found: Setting
[HKLM\SOFTWARE\WIDCOMM\BTConfig\SerialTransport]
FlowControl=0

seems to avoid the wrong behavior at 921600bps. So setting FlowControl=0 you can restore the original high speed configuration with BTSpeedSwitcher and listen to high quality audio without problems. Read the original post. You can also apply this fix importing this regfile by Menneisyys.

Weegie5

Thanks a bunch. I had searched for probably 20 minutes or so and didn't see anything that looked like it addressed this issue.

I made that change in the registry, though I've been wondering for a week or so now what HKLM means; now I know it's HKEY_LOCAL_MACHINE. Yeah, so I'm a newbie.

Anyway, so far so good! Thanks again.

~Weegie5