| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| I am working at the CENS laboratory at UCLA, and we have developed an appli= cation that continuously polls a bluetooth gps device for location informat= ion at given intervals. We have noticed that the bluetooth connection will= fail and the gps unit unpairs while the application is still running. The= time between the beginning of collection until failure seems to be arbitra= ry. To fix the problem we have tried updating the firmware as mention here, [ht= tp://wiki.forum.nokia.com/index.php/KIS000562_-_Bluetooth_serial_connection= _problems_in_S60_Nseries_devices] We also though about the watchdog solution posted here, [http://discussion.= forum.nokia.com/forum/showthread.php?t=3D76928] but our connection does not time out, instead the location api returns the = last acquired location (we know this from comparison of acquisition timesta= mps). We have also attempted to destroy the CLbsPositionRequestor and recreate it= when we see stale data returned, but this does not appear to solve the pro= blem. The only way to reconnect the gps device appears to be turn the phone= off and then back on. Any advice would be greatly appreciated.=20 Thank you, Steve Edited by: soakley on 13-Jan-2008 16:03 |
|
#2
| |||
| |||
| Hi Steve Where is CLbsPositionRequestor documented? I don't think its a Symbian API. Without knowing the cause of the problem its hard to offer useful advice. T= wo options occur to me: 1. Try L2CAP protocol instead of RFCOMM. If the problem is in the higher le= vel RFCOMM layer you may be able to bypass it. 2. Purchase some API partnering support with Forum Nokia to get them to res= olve the issue - at very least you could get them to verify that this is a = defect and the cause - which is the first part of resolving the issue. Regards Hamish Willee Symbian Ltd. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.