OK, it took 3 minutes to get a cold start lock (its a couple of weeks since I last switched the Android XA2 on) from being ‘nowhere’ (just a map of the world shown in Google maps) to a zoomed in setting of my house, on my road on the South Coast of England instead of a few seconds. So definitely slower, but still in a different league to how long it takes Sailfish.
And what I don’t understand is
if that is the case then surely the lack of Mozilla online position lock availability in Sailfish would affect GPS performance on all Sailfish phones, not just the XA2?
Which then brings me back to the fact that it must be something to do with the way that Sailfish interfaces to the XA2 firmware, low level binaries or whatever, rather than a hardware design fault or individual hardware failure. And the problem is obviously more pronounced for ‘cold start’ locks as those who use GPS regularly, or keep GPSInfo loaded, don’t appear to have such severe problems.
Ij Jolla can’t fix this (and it doesn’t seem like they can, or not easily) could a solution, or workaround really, be for Sailfish to provide an selectable option to regularly, occasionally, ‘wake up’ GPS, get a lock, and then send it back to sleep again? OK, so there would be a hit on battery capacity I guess, but if it worked it might make GPS on XA2 more usable for occasional users when they need it?
