Mike-

Sorry, I didn't mean that it just "hangs".. My bad, incorrect
terminology... I have a loader Activity that first acquires their
location then sends that to my Web API and waits for response data. It
shows a nice graphic and displays a spinning loader accompanied with
relevant text based on the current action "Acquiring your
location...", "Download data...", etc. So it's not that the app hangs
or that it appears to be broken or anything.. It just waits on the
loader screen for a bit while obtaining a location.

I have definitely noticed severe lags with GPS and Network locations,
especially when inside [as you addressed].. Basically I'm looking for
the best and most efficient way to write a custom Location manager
class [not a sub-class, just a custom class that handles all the
Location ish for me, cause the built-in Android LocationManager is a
little too low-level to use directly in my main Activities [basically
I'm working on writing my own Location manager that is similar to the
iPhone's version in usability (meaning that my main activities don't
really care/distinguish between GPS/network, the Location manager
class will take care of all that requesting bestProvider and getting
updates from it and what-not).]

It seems the Maps app acquires the user's location much quicker than
my app.. Why is this? Well, I suppose the simple answer is: "Because
it was made by Google." hahah... But really, it all must be
replicable...

Thanks!
Nick



On Mar 31, 2:02 pm, mike <[email protected]> wrote:
> On 03/31/2010 01:50 PM, patbenatar wrote:
>
> > Hey all-
>
> > I am working on an app that fetches localized data from the Web based
> > on the user's long/lat. Currently I am querying the system for the
> > best enabled provider [my criteria defines best basically as most
> > precise--not sure if this is the best idea for my application, as at
> > the point where I fetch data it really doesn't matter if the user is
> > here or 3 miles from here.].. But anyhow, I'm curious as to what is
> > most reliably the fastest Location provider? Network or GPS? My app
> > hangs a bit "Acquiring your location" on my loading screen and I'd
> > like to cut this wait time down as much as possible.
>
>  From experience, you're setting yourself up for trouble if
> you hang until you get location information. For GPS, it can
> take quite a while -- if ever if you're indoors -- before you get
> a fix. I've also seen far too many times where glitches in firmware
> and other phase-of-moon kinds of problems severely lengthen
> the first point acquired. As far as network based location, you
> may not have any to get anything from for one. Even in places
> where you'd expect it, like oh say, San Francisco.
>
> My advise would be to find something else to entertain your
> users until you get a fix. Hanging would look to me like a broken
> app.
>
> Mike

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to