Thanks for your help guys. I can see where I'm going wrong so should
be able to make some progress now.
Cheers.
On Nov 30, 10:23 am, Neilz wrote:
> Yes, the first attempt at grabbing a location is often null. You need
> to add a listener (onLocationChanged) and take it from there.
>
> On Nov 29,
Yes, the first attempt at grabbing a location is often null. You need
to add a listener (onLocationChanged) and take it from there.
On Nov 29, 7:03 pm, Lance Nanek wrote:
> If you use the Logcat view in Eclipse or the "adb logcat" command from
> the SDK on the command line you can see why your ap
If you use the Logcat view in Eclipse or the "adb logcat" command from
the SDK on the command line you can see why your app is crashing. In
this case it is probably that getLastKnownLocation is returning null,
which it can as per the documentation:
http://developer.android.com/intl/zh-CN/reference/
Thanks for the advice. I am still having trouble however.
When I add the debug line as advised, the app falls over and as far as
I can tell, 'location' is coming out as null.
If I comment out the log.i code then it works ok. So it seems to me
that there is something wrong with the way I am trying
Hi. As you are using Eclipse, you can use the Android plug in, and the
build in Emulator Control, to load up your KML file and manually send
location updates to the emulator. You find it at Window->Show View-
>Other->Android->Emulator Control. That should get you going.
To debug:
import android.u
5 matches
Mail list logo
