Use Geocoder, the newly class introduced in 1.0 SDK. Its helps in reverse geocodeing( i.e getting address from lat/lon)
http://code.google.com/android/reference/android/location/Geocoder.html Thanks, Shibbs On Oct 17, 2:12 pm, Matthias <[EMAIL PROTECTED]> wrote: > Well, in other words, this whole location manager thing is pretty > broken in Android 1.0? > > From what I've read and experienced myself so far, it's pretty much > like this: > > 1) LocationManager cannot be subclassed anymore, instead you use the > debug bridge to send location fixes. Unfortunately, this thing is > broken in two ways: Firstly, it only works on systems with a US locale > (?? sounds odd, but I can definitely tell it does not work for me...), > and secondly, the proclaimed "geo" command from the tools/ folder > isn't even there...! > > 2) In order for LocationManager.getLastKnownLocation() to actually > work, one has to register a listener, although this may not even what > the programmer needs -- I surely don't want it, I want to poll for > updates only on well-defined occasions. In fact, I believe this whole > location listener thing is a bad idea, because it will result in each > and every location-aware Android app running its own > ListenForLocationUpdatesService, in order to always have access to the > latest known location... yuck. > > Is that correct so far? If so, I have to say I am pretty much > disappointed with the progress Android makes. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
