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. top ListActivity destroyed just after a Search has been initiated from it - was: Back key after Search doesn't return to list in 2.0 as it did in all earlier versions

Hi again,

Hmm, it seems even more strange to me: the onDestroy() method of the top 
ListActivity is actually called very shortly after the search has 
triggered the onCreate()+onResume() methods that creates the second 
level ListActivity (note that this is the actual same class as the top 
one, just producing a different result due to the SEARCH action).
Call Sequence:

top onCreate()
top onResume()
-- I press search and enter some text.
top onPause()
2nd onCreate()
2nd onResume()
top onDestroy()
-- This is before the second ListActivity is even displayed

So obviously, by the time I press back in the 2nd ListActivity, there is 
no top ListActivity to show. So the problem is not the Back key, but 
that some unknown force has destroyed the top activity...

Note: the code is still compiled with android:minSdkVersion="2" and the 
very same package executes as expected on previous versions. So perhaps 
I've always done something incorrectly, but up until now the result was 
what I expected. In some special cases I do in fact explicitly call 
finish() to force this very effect, but that does not happen in this 
situation.

I didn't notice anything explicitly related to this in the release 
notes, but perhaps there is something between the lines that I have not 
yet realized.

                Advice appreciated / Jonas





-- 

2. sending mock location data to emulator?

I follow guidelines here to provide mock data for emulator (http://
developer.android.com/guide/topics/location/index.html)
This line suggest that I must connect to emulator first:

"Launch your application in the Android emulator and open a terminal/
console in your SDK's /tools directory. Connect to the emulator
console. Now you can use:..."

Since I'm on Windows, I did it by using putty and telnet to localhost,
port 5554 (of the emulator). However I could never succeed.

Did I understand the instruction properly? (connect by telnet before
using "geo fix" to send mock data)
If yes, why couldn't I connect to the emu?

Thanks.




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

3. Have you ever has a experience with JSP

4. How to use external library in Android project

5. SOAP on Android

6. Quick contact

7. RGB from bitmap