Archived:Bluetooth L2CAP error -6305 (Known Issue)

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 2nd Edition, Feature Pack 1 and Feature Pack 2

---

Article

Created: User:Technical writer 1 (07 Jul 2006)

Last edited: hamishwillee (15 Jun 2012)

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.

Solution

This problem is corrected in S60 3rd Edition and no workarounds are needed.