What is a reasonable timeout for acquiring a GPS fix?

Question

I am creating a BREW application that requests a user position.

If the phone cannot get the position, I would like to show an error.

How long should I wait for my callback to be called before I determine that the phone is unlikely to receive a GPS fix?

Answer 1

When a cold start is required, the receiver must download a complete set of ephemeris data that is broadcast from the GPS satellite for a 30 second cycle and retransmitted every 30 seconds.

So, I would say that 60-90 seconds (two or three Ephemeris cycles) would be a suitable waiting time before declaring a failure.

http://www.navigadget.com/index.php/gps-knowledge/ttff-time-to-first-fix

, , ( 12,5-15 ). Factory TTFF ( ).

Answer 2

45-90 .

. .

, , , , , , , , .

Answer 3

(, 20 30 ) , , . , , (, 5 - 10 ).

Answer 4

- , Motorola, GPS-, - 5 , , Bluetooth- .

Why are you reporting an error after a specific timeout? Why not, after a reasonable time has passed (say, a minute), display a message on the melody "GPS correction is still not available, but I'm still trying" with the ability to cancel at any time if the user loads up? What do you expect the user to do with the error message that you suggest giving him?