I tried to use the deprecated functions Device.Location.wait() and
Device.Location.last() with the same result. I do not get a GPS
location while the Google Maps application does. Can anyone else
confirm this behaviour (or not, in which case it might be my phone
that is the problem)? If so, it should be reported as a bug. I was
relying on Big5 for an application that needs to be working by the
beginning of May and this problem is a bit of a show stopper.
Is LiquidGear likely to be available for download from the app store
any time soon? The whole point of these apps is to provide a platform
for strictly web-based solutions that can be downloaded readily by
anyone. If I have to build my own custom version of Big5 or
LiquidGear, then I might as well just use PhoneGap and post my own app
to the app store.
On Mar 21, 3:48 pm, Giraldo Rosales <
nitr...@gmail.com> wrote:
> The location manager in Big5 uses the default accuracy, which is Best
> Accuracy. It should get you the best possible location in your current
> location. The weird part is that Google Maps is getting it so it can't be a
> bad location.
> I've just updated LiquidGear, adding the option of accuracy to the location.
> The JS gives an example of using a default of 3 meters but you can specify
> anything from 1-100 meters.
>
> -Giraldo
>
liquidgear.net
>