Reported against S60 2nd Edition, Feature Pack 1 and Feature Pack 2
Date identified July 7, 2006
Detailed description This error is due to physical link activation and closing events collision. Occasionally an application can use a sending interval that happens when the Physical Link and HCI are in the middel of a state transition. S60 2nd Edition, Feature Pack 3 implementation allows for a new activation while the link is actually being closed down - and therefore the -6305 error.
One workaround to this problem is to have constant traffic on the channel to avoid the physical link idle timer to go off and close the connection.
How to reproduce
Solution This problem is corrected in S60 3rd Edition and no workarounds are needed.
Im building an app, that uses a third party SDK for accessing a HeartRateMonitor via Bluetooth. Connection-Handling and Data-Transmission is encapsulated, so I have no chance
to add some code around the bluetooth-stuff.
Could you tell me please, what possible workarounds would be helpfull ?!
Actually, I even could not figure out where I can add some try catch or anything else.