search

chaseberry / little-fluffy-location-library

Automatically exported from code.google.com/p/little-fluffy-location-library
0 stars 0 forks source link

Last know location #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
More a question than an issue: 
why does little-fluffy-location-library use and save the last known location in 
the preferences and does not use something like LocationManager 
getLastKnownLocation or getLastLocation on LocationClient? I think this may 
also  remove the need of the PassiveLocationChangedReceiver, as these methods 
return the last known location, even if used by another application.

Thanks and regards

Original issue reported on code.google.com by hff...@googlemail.com on 25 Apr 2014 at 9:13

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It's because sometimes it wants to notify right at the point it gets the 
location via PassiveLocationChangedReceiver, if the time difference is greater 
than the minimum notification period. If not, it stores it and processes it at 
the next inexactrepeatingalarm period.

Original comment by ken...@kentonprice.com on 25 Apr 2014 at 2:36