×

Discussion Board

Results 1 to 4 of 4
  1. #1
    Registered User
    Join Date
    Nov 2003
    Posts
    4

    Symbian OS Error = -6305

    Anybody know where I can check the long description of this error message. I am writing a sending a btl2cap servicel url using bluetooth

  2. #2
    Registered User
    Join Date
    Nov 2003
    Posts
    5
    Hi!

    Check out http://newlc.com/article.php3?id_article=117

    L2CAP:
    KErrHCILinkDisconnection -6305

    I don't know if this is much more informative than just the number... :-)

    Jarkko

  3. #3
    Registered User
    Join Date
    Dec 2006
    Posts
    1

    Re: Symbian OS Error = -6305

    http://forum.nokia.com/Technical_Lib...error_6305.htm

    Library contents

    Bluetooth L2CAP error -6305 KIS000381

    Overview

    Reported against S60 2nd Edition, Feature Pack 1 and Feature Pack 2

    Date identified July 7, 2006

    Symptoms -

    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.

    Hope it may help you.

  4. #4
    Registered User
    Join Date
    Oct 2009
    Posts
    4

    Re: Symbian OS Error = -6305

    Hi rachel9,

    you wrote: "Solution This problem is corrected in S60 3rd Edition and no workarounds are needed."

    Well, I'm using the S60 3rd FP1 and I'm still getting this Exception:

    javax.bluetooth.BluetoothConnectionException: SymbianOS error = -6305 : General:
    System error (-6305)
    Handle exception


    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.

    Thanks and best greets, Micha

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×