Hi.
I've had a fr230 for a month now and the time to get a gps lock has always been above 15/20 minutes. As soon as I got it I took it for a run and after standing still like an idiot for >15 minutes without a GPS lock I just gave up and run without tracking. And we are talking about a city park...no tall buildings impeding the gps signal, pretty much just clear skies. So since then I reverted to my old polar+footpod for running and I've been taking the forerunner for walks around the city hoping to get a sense of the reason why this thing just doesn't seem to be able to work reliably.
-I tried with and without glonass
-I tried with and without an updated epo.bin file (the file containing the preloaded gps data for a, theoretically, fast lock)
-I've always started at the same point so as to make the FR's life easier, so to speak
-Obviously I've restarted the FR many times.
-The FW has always been up to date.
Through all of this the GPS lock time has always been 15/20 minutes and today the FR touched a new low (or high): 35 minutes...
I live in a large city but the buildings are old (or even ancient) and they are not very tall, so they do not impede the gps signal. And I've always kept on large roads, again just to make the FR's life easier. But it's all been to no avail.
And the worst aspect is that I don't even think that my FR is defective (we are talking about a large and renown manufacturer so the probability of a defective product should be pretty low). I'm beginning to think that this may be a design problem and therefore not fixable.
I think I tried everything to make it work reliably but if someone think I've missed something please do tell.