As we know, Tungsten T3 provides a bluetooth dialog (invoked by the bluetooth icon at the status bar), which shows either a "Connect" or "Disconnect" button, depending on whether it is connected to a bluetooth device. I found that T3 maintains incorrect bluetooth connection states.
I tested the scenario on a Tungsten T3 with a bluetooth GPRS phone. The idle timeout is set to "Never".
My application begins a socket connection, by SysLibFind() NetLibOpen() ...etc
After the socket connection is made, the bluetooth dialog shows the "Disconnect" button. This is correct, as the GRPS via bluetooth connection is now active.
However, when the application closes the socket and then calls NetLibClose(libRefNum, false), the Bluetooth dialog shows the "Connect" button. This is NOT correct, because the GRPS via bluetooth connection is still active, only the socket connection is closed. Now, if the user presses the "Connect" button, nothing happens and the "Connect" button quickly changes to the "Disconnect" button.
Does anyone aware of this problem? I think it is a bug in the Tungsten T3. But is there any workaround?
Thank you!
Best Regards, Tony Cheung
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
