android getlastknownlocation always null in emulator

Question

It seems a common issue, but i really can\'t understand why is it happening even though i read ton of simialr issues.

I am playing with a basic location class on a e

Answer 1

getLastKnownLocation() will return null in general, if no app has requested a location fix from your desired provider recently.

On the emulator, it seems to take it one step further: you do not get a location unless one has been delivered to the emulator since your app has called requestLocationUpdates().

The general pattern for using getLastKnownLocation(), if you want decent odds of getting an actual Location, is to use requestLocationUpdates() and removeLocationUpdates() to ensure that LocationManager is actively seeking locations via your chosen provider. Of course, you could also use LocationListener and onLocationChanged(), rather than getLastKnownLocation(), if you so chose.

Answer 2

There is another option, to create your own provider using locationManager.addTestProvider(); so you can make your own tests.

Answer 3

@CommonsWare's answer is clear. To get not-null on emulator go to Google Maps application and after that you get some location