|
Latest Bug Reports
Updated 4/2/05
|
|
| 04/2/05 |
BTA12 - Bug in
PANDisconnect
Affected Models:
all models, starting with Widcomm stack v1.4.
Symptoms: Call to PANDisconnect would fail after PANConnect if you also
do any other type of connection (e.g. SPPConnect).
Fix: Bug resolved
Status:
FIXED
|
|
| 01/12/05 |
BTA11 - Bug using
SetSvcSecurityOptions and SetGeneralSecurityOptions
Affected Models:
all models, starting with Widcomm stack v1.5.
Symptoms: Call to either routine would disable any subsequent bluetooth
operations (device-search, connect, etc).
Fix: Corrected way in which stack was informed about security
settings.
Status:
FIXED
|
|
| 01/02/05 |
BTA10 - Memory leak in .Net
GetActiveConnections
Affected Models:
all models .Net usage only
Symptoms: Call to BT_GetActiveConnections in the flat API used from C# (BTAccess.cs)
results in a memory leak. This was due to the fact that the underlying
CBtStack.GetActiveConnections C++ method creates an MFC CPtrList to hold the
connection info, but was not correctly cleaning up after using it.
Note this same error was found and fixed in the C++ StackDemo sample
application as well.
Fix: Objects in the CPtrList were deleted first, then the list itself
was deleted.
Status:
FIXED
|
|
| 9/16/04 |
BTA9 - Did not show
non-English device names correctly
Affected Models:
all models
Symptoms: Device names containing special characters would show garbage
characters.
Fix: Bug resolved
Status:
FIXED
|
|
| 9/13/04 |
BTA8 - Unable to do PANDisconnect
or LANDisconnect
Affected Models:
all models
Symptoms: Disconnect functions would fail nearly every time after a
recent change.
Fix: Bug corrected
Status:
FIXED
|
|
| 9/1/04 |
BTA7 - Unable to connect on
Dell Axim X30
Affected Models:
Dell Axim X30 or any new devices using the Widcomm v1.5 bluetooth stack
Symptoms: SPPConnect would succeed but would be followed by an event
message indicating the connection was not completed.
Fix: Build error corrected
Status:
FIXED
|
|
| 9/1/04 |
BTA6 - Unable to cancel
SPPConnect
Affected Models: all
models
Symptoms: When doing an SPPConnect to a desktop, if you reject the
connection request at the desktop the BTAccess program would crash.
Fix: Build error corrected
Status:
FIXED
|
|
| 9/1/04 |
STD1 - StackDemo would not
compile
Affected Models: all
models
Symptoms: We inadvertently forgot to ship the StackDemo.vcw file with
the project. Also due to a build error related to precompiled header
files certain functions were not compiling correctly.
Fix: Build error corrected.
Status: FIXED
|
|
| 9/1/04 |
BTA5 - Unable to set
Security Options for DUN or PAN
Affected Models: all
models
Symptoms: Attempting to call SetSvcSecurityOptions with the
BTSVC_DIALUP or BTSVC_LAN or BTSVC_PAN values would crash the program.
Fix: Added code to support these services which had been
inadvertently omitted.
Status:
FIXED
|
|
| 9/1/04 |
BTA4 - Unable to set
pDevice->m_strDeviceName
Affected Models: all
models
Symptoms: When creating your own new CBtDevice and trying to set an
initial value for the m_strDeviceName member variable the program would get
a First Chance Exception.
Fix: Build error corrected
Status: FIXED
|
|
| 9/1/04 |
BTA3 - Unable to set
pDevice->m_strDeviceName
Affected Models: most
Spanish, French, German, Italian iPAQs
Symptoms: When creating your own new CBtDevice and trying to set an
initial value for the m_strDeviceName member variable the program would get
a First Chance Exception.
Fix: Build error corrected
Status: FIXED
|
|
| 4/15/04 |
BTA2- SPPConnect fails
on non-English iPAQs only
Affected Models: most
Spanish, French, German, Italian iPAQs
Symptoms: A call to
SPPConnect succeeds but the ConnectionStatus event received later
always indicates BT_CONNECTION_FAILED.
Fix: Most non-English iPAQs are shipped from HP with an error in the
registry whereby the text name of the inbound service is in English and the
outbound service is in the native language (or vice-versa). This
caused problems in our code which we now deal with.
Status:
FIXED
|
|
| 3/10/04 |
BTA1- system hang on
SPPConnect with 54xx models
Affected Models: 54xx and later
Symptoms: When you do an
SPPConnect and the connection is lost for any reason (device moves out of range,
device is turned off), and then do a SPPDisconnect followed by a second
SPPConnect, the system will hang.
Fix: We discovered a
memory corruption in our code which on some models had no impact except a memory
leak. On other models it causes a system hang.
Status: FIXED
|
|