maemo.org Bugzilla – Bug 5761
Bluetooth GPS reconnect dialog refuses to go away after clicking "No"
Last modified: 2010-01-14 12:23:01 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
Establish a GPS connection with a bluetooth GPS device and open Ovi Maps (so
that it actually gets used).
Then move out of range of the bluetooth GPS. The dialog asking if a bluetooth
reconnected should be attempted pops up and the users thumbs no.
The dialog goes away.
The dialog pops up repeatedly, until the application wanting location is closed
or until the user goes into settings and selects the internal GPS.
Thanks for reporting this!
(In reply to comment #0)
> Establish a GPS connection with a bluetooth GPS device
Which exact device? Probably unrelated but can't hurt to know...
> Then move out of range of the bluetooth GPS. The dialog asking
What is the *exact* text of that dialog?
Makes it easier to find a ticket when searching...
Confirming. The text of the message is "The connection to the Bluetooth GPS has
been lost. Try to reconnect? (Yes/No)".
You may normally use a Bluetooth GPS for better fix times but may not always
have it with you when you want to casually browse a map (nor should you be
expected to have the GPS connected at all times when Maps is running). This
seems to be somewhat related to bug 5905 in that Maps assumes you must always
have an internet connection and a GPS active.
It's a Holux M1000.
(In reply to comment #3)
> It's a Holux M1000.
I have this device as well, but the bug is unrelated to the make of the
Bluetooth GPS; it's simply the fact that the location framework doesn't
remember that you pressed "No" when you dismissed the dialog.
On a side note, Ian, would you mind having a go at bug 5586 and see if you can
confirm it? I think it may in fact be specific to the Holux M1000.
Yes, this MIGHT be a duplicate of bug 5905. Good catch!
So I currently expect bug 5368, bug 5905 and bug 5761 to have the same
underlying root issue in location-proxy having a broken passing of the user
decision to click "No". This is just my uneducated guess though.
This has been fixed in the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update