Yeah sorry I was mixing what I was trying to retrieve mixed with the actual API call. But yea that is correct.
It's not a phone I have either :( We can't reproduce it consistently. And a lot of the Galaxy S phones do have defects in their GPS software but I never thought it would just block. I have a few logs from clients but it seems to feel like their locking inside of their libgps code is not releasing it's global lock. We have a few other theories but since the LocationManager class isn't documented too well (it seems to be somewhat of a port of J2ME's but not completely) we are just shooting in the dark. I noticed a pattern in our application which registers the same LocationListener multiple times without deregistering it. The registration does not fail and we don't get updates after we unregister once so we assumed it was fine and made the code more readable because we didn't have to worry about side effects. However now I am not so sure. But even if that was the problem it should be something that is completely reproducible on the same OS/firmware version. To be clear we saw the same phone, Samsung Galaxy S Epic, install the app and each one may or may not get stuck in this really nasty state. Basically the overall GPS system for the OS gets frozen, even maps can't get a fix after it gets in this state. Enabled providers don't seem to be the issue as they have both GPS and network locations providers enabled on each phone. On Dec 7, 10:54 am, Mark Murphy <[email protected]> wrote: > On Tue, Dec 7, 2010 at 1:49 PM, Greg Giacovelli <[email protected]> wrote: > > After which we > > call on the UI thread LocationManager.getBestLastKnownLocation() for > > the provider we were interested in. > > There is no getBestLastKnownLocation() in LocationManager in Android. > I am assuming you are referring to getLastKnownLocation(). > > > However on certain phones, the > > Epic in particular sometimes this call never returns. > > Seriously? That's a Galaxy S phone, which is pretty popular, though it > is not one I have in my stable. > > It certainly feels like a compatibility bug. Do you have any info on > criteria for when this will block (e.g., only if no providers are > enabled)? > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
