I have exactly the same problem.
Only difference:

the app stops receiving location updats after 1-2 attemts.

Same here, my app only receives two locations, then my Listener isn't called again.
Sending Locations through DDMS doesnt work (rest of DDMS works fine). Sending geo fix
by telnet works, but only twice.

any solutions?

I have the same issue. Noticing that going via telnet and sending a geo fix negative 
values and some with high presicion don't get accepted. I couldn't get it running.

Same problem here. Only the first geo fix command works, the next one won't get updated.

Same experience.  Only one update hits my listener.  Worked fine in 1.1

Same here. I need that fuction for an application, so any suggestion?

One potential workaround is to try to use mock location providers instead: 

http://developer.android.com/reference/android/location/LocationManager.html#addTestProvider(java.lang.String,
boolean, boolean, boolean, boolean, boolean, boolean, boolean, int, int)

I have the same problem too.
Does anyone have a solution?

Thank you.

Hi, same problem too.

But wit works if you create some SDK 1.1 AVD (target=1) 

regards

I have problem that looks the same. Outputting the Location object shows that the
first one has mTime=1234567 (something real) the second one has mTime=-1000 and then
the updates stop.

Getting the last known location and outputting that one shows that all mTimes after
the second Location are mTime=-1000. 

I submitted a fix that solves the problem in the mTime situation.
https://review.source.android.com/10251

Same problem here.
This is really annoying, because it is actually almost impossible to work with the
emulator.
I hope the priority changes to something more serious.

Any other workaround besides addTestProvider?

I'm testing the listener on a HTC Magic (I/O 2009), and my location is only updated 
once. I installed my application and started driving, and I was never informed of a 
location changed (I set up 60 secs and 50 mts).
I'm using SDK 1.5 r2
Thanks

Same problem though I tried it on Ubuntu and still had the same issue of it stopping
after two location updates...????

Same problem here. The location is updated two times only, after that, the ddms keeps
sending mock locations but the emulator does not show them into the map. Is there a
problem with the ddms or in the emulator?. 
Somebody has a solution? I need this working for my university's project, it is very
important!

Thanks, and sorry for my English!

same here...

this is really embarassing... you'd think this would have been tested at this basic 
level...

I also get the same problem even on the real device (HTC Magic - Non Google), the
work around:

public class DeviceLocationListener implements LocationListener {
		public void onLocationChanged(Location location) {
			mLocationManager.removeUpdates(locationListener);
			mLocationManager.requestLocationUpdates(
                        LocationManager.GPS_PROVIDER,
                        3000,
                        1,
                        locationListener);
		}
}

Ah thanks a.wirayudha the work around is simple and works so I guess that will have
to do. This problem was driving me crazy for ages.

Tom

Hy,
I wrote a script that sends a "geo fix [coord1] [coord2]" command (every command
should give a new location at about a distance of 10-40 m from the last one)
The onLocationChanged() method triggers normally but it doesn't receive the correct
coords. The coords are received when the new location is at a distance of about 10-20
km from the last location update received.
Ex:

Example:
Sending: geo fix 26.446486 44.464973
Sending: geo fix 26.446745 44.465572
Sending: geo fix 26.447004 44.46617
Sending: geo fix 26.447264 44.46677
Sending: geo fix 26.447523 44.46737
Sending: geo fix 26.447783 44.467968

When i print the received coords i get this:
Loc changed: 44.457335816666664 26.43766885
Loc changed: 44.45733591666667 26.437668900000002
Loc changed: 44.45733601666667 26.43766893333333
Loc changed: 44.474000016666665 26.43766898333333
Loc changed: 44.474000116666666 26.43766901666667

Why do I get coords with this lack of precision ? (requestLocationUpdates() has
minTime = 0, minDist = 0)

I have experienced also those issues, both the missing position updates in 1.5
firmware (had to revert to 1.1 for my personal project to work) and the precision
issue in telnet, which, curiously enough, doesn't happen when the coordinates are
sent from eclipse (I would certainly have assumed that eclipse sent the coordinates
through a telnet connection!). 

I also tried sending mock locations (at a rate of about 1000 ms using another thread)
with sendTestProviderLocation(...) but that will not trigger onLocationChanged(). Is
it possible I forgot to do/set something ?

Same issue here, I can only receive 1 or 2 first location changes. Very annoying

I am seeing the same issue in the emulator. My onLocationChanged is not being called
more than once or twice from either geofix or DDMS. I setup a Toast to notify me of
location changes. If I send a new location to the application, I get no indication it
was received. If I close my Activity in the emulator and reopen it, I see the Toasts
from the previous session as if they were queued up. 

SDK 1.5_r2, Vista SP1
Eclipse Platform
Version: 3.4.1
Build id: M20080911-1700

Can someone test the issue with the 1.5r3 SDK/emulator.
(It includes a few related GPS-related fixes)

It's same with the 1.5r3.

In 1.5r3 the problem remains for me too, issue and solution as described in:
http://code.google.com/p/android/issues/detail?id=2545#c13 

Bug still remaining in 1.5r3...

One more detail : it seems to be linked to an application lifecycle : whenever I
relaunch an application, I can push GPS coordinates once again.

Same issue here, I can only receive first two location changes. Any fixes??

any one from google please give the solution and suggest how to proceed forward in
1.5 sdk...

I'm not sure this solved issue, or not.
Anyway, after I set correct Time zone & Time in setting of AVM, 
it works great. Someone try this and feedback plz.

ses1430 you are my hero..works!!!
but i see one side effect when I use location listerer...my onTap on the Itemized 
overlay keeps getting called even when I dont take ON the overlay but somewhere near 
it....it does not happen when i dont use location listener..
But thx a lot for sharing the info!

Thanks a lot ses1430, it works!! Though I don't really understand why...

Just to be precise:

In the emulator, on the Home Screen, press "Menu" -> "Settings" -> "Date & Time" ->
->Uncheck "Automatic" -> "Select Time Zone", and choose the right time zone (ie, yours).

And voila! Works great!!

Yes, ses1430, your workaround does the trick!

The workaround makes sense because a buggy timezone usage in the GPS-emulator driver
(gps_qemu) causes the problem. Setting the timezone avoid the driver problem!

Thank you ses1430 for the help!

Rene

(No comment was entered for this change.)

Finally it works, don't know why!!
Just follow the steps on Comment 38.
Thanks ses1430

This issue should be fixed in the recently released 1.6 SDK.
If this not the case, please update this bug.

hello,
ddms does not work on my mac. perhaps i make a stupid mistake.

please look at: 
http://groups.google.com/group/android-developers/browse_thread/thread/5360c665c92af02e/d1ee24b3377a47da#d1ee24b3377a47da

Thanks.

Well just adding the time zone correctly fixed it.
Thanks
Nirav