Maintenance & Troubleshooting 6 - 5
Can’t make my
Ericsson R520 phone
discoverable.
You attempte d to
bond with the
phone, and when
the phone
presented a
“pairing query,”
you entered No.
This prevents the
phone from being
discoverable until it
is reset.
Reset the phone by removing its battery.
There is a delay in
the Bluetooth st ack
re-initializing during a
resume from
suspend.
This is normal
behavior. No solution required.
Piconet (the
connection betwe en
a Bluetooth master
and one or more
Bluetooth slaves)
drops.
The EDA
suspends and the
Bluetooth radio
power turns off.
One of the devices
are out of range.
An application can register for no tification of an EDA resume by
creating a messag e queue using the CreateMsgQueue() API
and power notifications using the RequestPowerNotifications()
API (refer to the SMDK Help File). After an application receives
a resume notification it should close open Bluetooth sessions
and reopen them.This reestablishes the piconet lost dur ing th e
suspend.
My application
created a successful
RFCOMM session
with another
Bluetooth device but
the session was
dropped.
Device went out of
range or was shut
off.
Check the return value of APIs for errors. Look for a DCD state
change event in the Microsoft Bluetooth stack DCD window of
the Bluetooth connection.
After completing an
RFCOMM session
with another
Bluetooth device, I
was unable to create
a virtual COM port to
connect to another
Bluetooth device.
The Microsoft
Bluetooth stack
holds a baseban d
connection for ten
seconds after an
application closes
its session and
exits. This was
designed to allow
for speedy
connections to th e
same device if
other profiles were
to connect.
Either wait 10 seconds, choose a dif ferent COM port number for
the virtual COM port, or modify
HKLM\software\Microsoft\bluetooth\l2cap\IdlePhys (which
defines the nu m ber of se co nd s to ho ld the co nn ec tio n) .
Table 6-2
Troubleshooting Bluetooth Connection (Continued )
Problem Cause Solution