Archived:Calling LocationProvider.getLocation() periodically may result in device lock-ups with Nokia 6110 Navigator (Known Issue)
Calling getLocation(int timeout) regularly may result in device lock-up in the Nokia 6110 Navigator.
Calling LocationProvider.getLocation(int timeout)] periodically may result in the method to block forever regardless of the timeout value, which in turn results in a lock-up behavior in form of slow overall device performance even when the MIDlet has been exited. Attempts to access GPS by using another MIDlet or a native GPS application, such as GPS data, result in the device to hang. The device must be power cycled to resume normal operations.
How to reproduce
- Implement a test MIDlet using source code from http://www.developer.nokia.com/Community/Discussion/showthread.php?127120-JSR-179-serious-bug-in-getLocation-implementation&s=4f0d07e55ff730bd87626acfdf1609ca&p=387632
- After installing the test MIDlet, use App. Manager to change Settings for Positioning to Ask first time.
- Start the MIDlet and set the timing parameters. For example, set the timeout to 1 second.
- Select "Start Sync" to begin sampling using getLocation().
- Get a GPS fix and wait.
- Reproducing this problem may take time, for example, with 1 second as the initial timeout value, this may take up to 900 seconds to appear. The display will stop updating when the MIDlet eventually hangs, signaling the result lock-up state.
- Try launching "GPS Data" and other applications on the device. In the lock-up state, the device will launch applications sluggishly and GPS applications will hang.
No known solution.