We've written a Symbian C++ application that constanlty keeps oppen several bluetooth connections (RFCOMM) to different medical sensors.
Since we switched to the Nokia 6600, we occasionally get the following Bluetooth server panic:
- This panic also occurs, if there is only one bt connection open
- This panic seems to be related to a low reception power
- The system seems to recover correctly from this crash: the BT server will be restarted, all open socket server sessions seem to remain valid as well.
- Does somebody have some more information about this issue. ?
- Is there a work-around on application level to prevent this bug?
My question the other way round:
- is there a way to prevent to display the panic dialog, which irritates the phone users quite much?
Probably some problems with an Active Objects in your app. But I can imagine that in BT based application it might be on several places and it is, without seeing the code, very difficult to say what is wrong. Maybe this bug is there all the time but it didn't occur on previous devices because of some different timing of events (maybe), etc...
You should go over all AO and see if you are not trying to set an object active when he already is...