As above. The documentation does not state in what unit this timeout is, and I have found by empirical means that the unit is in "seconds".
However, also, there is a maximum value you can pass to this API - if the value is too big, the function simply errs out with LOCATIONS_ERROR_INVALID_PARAMETER. It is not documented what the maximum value is, though. I can find that value by empirical tests as well, but I have a few questions:
a) Can someone official (e.g. from Samsung) please confirm what it the official maximum timeout value?
b) Will (a) vary from device to device? (as in in different model of Gear devices)?
c) Can someone official confirm that the value stated in (a) is indeed sufficient to get a GPS reading when transitioning from best to worst case scenario (e.g. device was previously inside a building, and location_manager_request_single_location is triggered at the same time the device is put outside under clear sky).
d) If answer to (c) is NO, then what is your suggestion? location_manager_get_position doesn't seem to have a timeout. What's gonna happen if we trigger this when the device can't get a GPS location at all?
Basically I need a function that can guarantee to deliver an accurate GPS reading, given a timeout, if possible. "location_manager_request_single_location" seems to be the correct function except that the maximum timeout value seems to be too small (from experience) to be able to do that, when GPS has to start from scratch (e.g. just after power-on, for example).
Thank you.
Platform: Tizen 2.3.2, Device: Gear S3