Well, in the end I couldn't get Google Maps to run on 1.5 no matter how hard I tried. Now I'm happily using OpenStreetMap, which was up and running in 15 minutes, but needed one or two days of tweeking until it met my needs. See http://www.anddev.org/openstreetmap_mapview_for_android-t2967.html
Anyway, that's nothing compared to the many days I spend trying to get Google Maps working along with a Widget. The thread http://groups.google.com/group/android-developers/browse_thread/thread/7ce1902505bba25a/f915dcb6d1ee6f19?lnk=gst&q=maps+widget#f915dcb6d1ee6f19 states that this is currently impossible anyway. Anyway, some of you might acutally need to use Google Maps, and I hope that there will be some clarification for everyone who still experiences difficulties and a bugfix in the next SDK version. On 30 Jul., 08:50, "jagtap.jj" <[email protected]> wrote: > Refer this > http://www.anddev.org/viewtopic.php?p=24902#24902 > > On Jul 21, 10:12 pm, Spiral <[email protected]> wrote: > > > Same here. > > > On Jul 6, 8:45 pm, Georgy <[email protected]> wrote: > > > > Hello Brian, > > > > I am having your same issue. Were you able to solve it? > > > > thanks > > > > On May 25, 8:48 am, "brian.schimmel" <[email protected]> > > > wrote: > > > > > Hi everybody, > > > > > I'm getting the same problems. Of course I have read this thread and > > > > tried everything that was suggested (and some more), but it does not > > > > work. Here are the facts: > > > > * Using SDK 1.5_r1 > > > > * Project target in Eclipse is "Google APIs 1.5" > > > > * AndroidManifest.xml contains <uses-sdk android:minSdkVersion="3" /> > > > > inside the manifest element > > > > * AndroidManifest.xml contains <uses-library > > > > android:name="com.google.android.maps" /> inside the application > > > > element > > > > * maps.jar is NOT added manually to the buildpath, but is shown under > > > > Project -> Google APIs -> maps.jar > > > > * The maps key is setup properly (that is, worked before switching to > > > > 1.5) > > > > * code works when compiled againt the 1.1 API, but I need to compile > > > > for 1.5 because I want to provide a Widget. > > > > > On the emulator (Firmware 1.5, google_sdk_eng 1.5 CUPCAKE 147336 test- > > > > keys, the one that comes with DSK 1.5_r1) I get this: > > > > > 05-25 12:33:40.554: INFO/ActivityManager(568): Starting > > > > activity:Intent{ comp={com.webxells.ourapp/.OurMapview} } > > > > 05-25 12:33:40.564: DEBUG/AndroidRuntime(819): Shutting down VM > > > > 05-25 12:33:40.564: WARN/dalvikvm(819): threadid=3: thread exiting > > > > with uncaught exception (group=0x4000fe70) > > > > 05-25 12:33:40.564: ERROR/AndroidRuntime(819): Uncaught handler: > > > > thread main exiting due to uncaught exception > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): > > > > android.content.ActivityNotFoundException:Unableto find explicit > > > > activity class {com.webxells.ourapp/.OurMapview}; have you declared > > > > this activity in your AndroidManifest.xml? > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > android.app.Instrumentation.checkStartActivityResult > > > > (Instrumentation.java:1480) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > android.app.Instrumentation.execStartActivity(Instrumentation.java: > > > > 1454) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > android.app.Activity.startActivityForResult(Activity.java:2656) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > android.app.Activity.startActivity(Activity.java:2700) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > com.webxells.ourapp.CommonUi.onOptionsItemSelected(CommonUi.java:64) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > com.webxells.ourapp.OurAppStart.onOptionsItemSelected(OurAppStart.java: > > > > 22) > > > > 05-25 12:33:40.584: ERROR/AndroidRuntime(819): at > > > > android.app.Activity.onMenuItemSelected(Activity.java:2085) > > > > ... some more... > > > > > Of course, the activity is declared in the AndroidManifest.xml, and > > > > this declaration worked when compiling against the 1.1 API. > > > > > And on a real device (HTC Dev Phone 1, Firmware 1.5, dream_devphone- > > > > userdebug 1.5 CRB21 147201 test-keys) I get another error, instead of > > > > the one above: > > > > > 05-25 12:17:34.764: WARN/dalvikvm(691):Unabletoresolvesuperclass > > > > of Lcom/webxells/ourapp/OurMapview; (100) > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): Link of class 'Lcom/webxells/ > > > > ourapp/OurMapview;' failed > > > > 05-25 12:17:34.764: ERROR/dalvikvm(691): Could not find class > > > > 'com.webxells.ourapp.OurMapview', referenced from method > > > > com.webxells.ourapp.CommonUi.onOptionsItemSelected > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): VFY:unabletoresolveconst- > > > > class 114 (Lcom/webxells/ourapp/OurMapview;) in Lcom/webxells/ourapp/ > > > > CommonUi; > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): VFY: rejecting opcode 0x1c at > > > > 0x0045 > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): VFY: rejected Lcom/webxells/ > > > > ourapp/CommonUi;.onOptionsItemSelected (Landroid/view/ > > > > MenuItem;Landroid/app/Activity;)Z > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): Verifier rejected class Lcom/ > > > > webxells/ourapp/CommonUi; > > > > 05-25 12:17:34.764: DEBUG/AndroidRuntime(691): Shutting down VM > > > > 05-25 12:17:34.764: WARN/dalvikvm(691): threadid=3: thread exiting > > > > with uncaught exception (group=0x4000fe70) > > > > 05-25 12:17:34.764: ERROR/AndroidRuntime(691): Uncaught handler: > > > > thread main exiting due to uncaught exception > > > > 05-25 12:17:34.784: ERROR/AndroidRuntime(691): java.lang.VerifyError: > > > > com.webxells.ourapp.CommonUi > > > > 05-25 12:17:34.784: ERROR/AndroidRuntime(691): at > > > > com.webxells.ourapp.ourappMain.onOptionsItemSelected(ourappMain.java: > > > > 36) > > > > 05-25 12:17:34.784: ERROR/AndroidRuntime(691): at > > > > android.app.Activity.onMenuItemSelected(Activity.java:2085) > > > > ... some more ... > > > > > of course, the unknownsuperclassof OurMapview is > > > > com.google.android.maps.MapActivity. Don't get confused by the name > > > > "OurMapview", it's an activity, not a view. > > > > > While trying different targets and small changes in the manifest, I > > > > somehow managed to get it working on the emulator, but it never worked > > > > on the device. When I compiled for 1.1, it worked on the emulator and > > > > the device, though they were already running the 1.5 firmware. Any > > > > idea what else could be wrong? > > > > > thanks, > > > > Brian > > > > > On 21 Apr., 19:29, André Charles Legendre <[email protected]> > > > > wrote: > > > > > > Hi > > > > > > Finally, my error was to leftmaps.jar in the classpath > > > > > > Now, this very simple Map app with 1.5 SDK launch good > > > > > > Thank for all the responses. It helps a lot. > > > > > > Andre > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
