VERY URGENT : The app not working fine on 1.5G emulator (target name: Google APIs) which is working fine on 1.0 emulator

by manoj » Sat, 23 May 2009 13:12:33 GMT


Sponsored Links
 Hi I have written a location based app.

The app finds a route between two coordinates. Its working fine on 1.0
emulator as well as on 1.0 supported devices.

Now I tried to run the same app on 1.5G (Google APIs ) emulator. Its
not working. It is not showing the route. and got the following log
messages:

D/GpsLocationProvider(  568): setMinTime 0
I/Maps.MyLocationOverlay(  655): Request updates from gps
E/LocationManagerService(  568): isProviderEnabled got exception:
E/LocationManagerService(  568): java.lang.IllegalArgumentException:
provider=network
E/LocationManagerService(  568):        at
com.android.server.LocationManagerService._isProviderEnabledLocked
(LocationManagerService.java:1514)
E/LocationManagerService(  568):        at
com.android.server.LocationManagerService.isProviderEnabled
(LocationManagerService.java:1499)
E/LocationManagerService(  568):        at android.location.ILocationManager
$Stub.onTransact(ILocationManager.java:245)
E/LocationManagerService(  568):        at android.os.Binder.execTransact
(Binder.java:287)
E/LocationManagerService(  568):        at dalvik.system.NativeStart.run
(Native Method)


and I tested the maps app on 1.5G emulator. When I tried to get my
current location,
I got the alert "Your location cannot be determined. We will keep
trying, but you can also try moving your position".

and the log says:
D/GpsLocationProvider(  568): setMinTime 0
I/Maps.MyLocationOverlay(  655): Request updates from gps
E/LocationManagerService(  568): isProviderEnabled got exception:
E/LocationManagerService(  568): java.lang.IllegalArgumentException:
provider=network
E/LocationManagerService(  568):        at
com.android.server.LocationManagerService._isProviderEnabledLocked
(LocationManagerService.java:1514)
E/LocationManagerService(  568):        at
com.android.server.LocationManagerService.isProviderEnabled
(LocationManagerService.java:1499)
E/LocationManagerService(  568):        at android.location.ILocationManager
$Stub.onTransact(ILocationManager.java:245)
E/LocationManagerService(  568):        at android.os.Binder.execTransact
(Binder.java:287)
E/LocationManagerService(  568):        at
com.android.server.SystemServer.init1(Native Method)
E/LocationManagerService(  568):        at
com.android.server.SystemServer.main(SystemServer.java:412)
E/LocationManagerService(  568):        at
java.lang.reflect.Method.invokeNative(Native Method)
E/LocationManagerService(  568):        at java.lang.reflect.Method.invoke
(Method.java:521)
E/LocationManagerService(  568):        at com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:782)
E/LocationManagerService(  568):        at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
E/LocationManagerService(  568):        at dalvik.system.NativeStart.main
(Native Method)
W/I


I am not understanding why I am not getting the current location.

Can any one please help me to solve this problem?

Thanks,
Manoj.
--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Button.setTextColor, how to make it work? Options

If you want to permanently change the color scheme of the button,
please consider using a custom style:
http://d.android.com/guide/topics/ui/themes.html
R/




--~--~---------~--~----~------------~-------~--~----~

2. How to start debugger on ADP1 device rather than AVD

What is the minSdkVersion for your app? Which android does the avd
that starts run?

For example if you have minSdkVersion=4 in your app's manifest, ADT
will want to locate a system for android-4, but your device only runs
android-3 (aka 1.5).

One workaround is to edit your launch configuration in eclipse to use
the manual target mode: menu Run > Run/Debug Configuration > select
config > Target tab > Manual.

R/





--~--~---------~--~----~------------~-------~--~----~

3. Application closes when I try to convert String to Integer

4. Is Service capable of showing Error Messages in the form of transient notices?

5. sendBroadcast compile error

6. InputMethodService problem

7. Build Problem