Originally Posted by csoldfield
I have the same issue with 8300/Curve v22.214.171.124 whilst running GoogleMaps (v1.6.1 #1616) or Nav4All (v8.0.3). Holux M-1200 puck.
Puck connects and stays connected flawlessly with Nokia N770/MaemoMapper. So I conclude the puck is good
However, with BlackBerry I get the bluetooth connection dropped. This can be after just a few minutes of launching the app, or maybe an hour. Pretty random intervals. Exiting (ie. Quit) then relaunching the app restores the BT connection. Deleting the pair and re-pairing is not necessary to restore the BT connection, nor does doing that help any.
Nav4All pops up a message: "The Nav4All application requires Bluetooth to be enabled. Enable Bluetooth? Yes/No" - select 'Yes' and after 45secs wait normal operation is always restored.
GoogleMaps simply stops flashing the little blue dot and pops up "Sorry, we can't determine your location at present". Sometimes it comes back by its self after a short while.
This issue seriously limits the usefulness of GPS on the Curve - on a recent roadtrip it naturally decided to fail at the most critical turn
Please, please, RIM can you fix this for us?
More results: I can remain connected with a Samsung WEP410 for what appears indefinately. If I connect to my Holux M1200 and run GoogleMaps or Nav4All, I experience a loss of connectivity to both the M1200 and the WEP410 after a short while. So it appears that whatever activity is associated with running GoogleMaps/Nav4All causes an otherwise reliable WEP410 connection to be lost. I've never
seen the WEP410 connection dropped unless I'm running GM/Nav4All.
My second observation is that it appears that a static map ie. where no network downloads are taking place due to GPS movement, then the M1200 appears to have a better reliability. Switching to 'Satellite View' appears to worsen the reliability, it appearing that the more data being downloaded the worse the problem of dropped connections. I did disable the network download, but still saw some dropped connections.
Final observation - a lost bluetooth connection can be restored from within the app being run. Nothing has to be done from outside the app. So why can't the app automatically reconnect when the connection is lost? Doesn't the Bluetooth SPP connection have this level of recovery?
I'm going to report the issue to RIM - has anyone else opened a bug report yet?