Databases
StackOverflow2013
Postsdbo
POcamera and map crashes when launched from my custom home screen
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POcamera and map crashes when launched from my custom home screen
    primarykey
    data
    text
    <p>I've created a custom home screen. This is my code to launch an application when clicked:</p> <pre><code>mainIntent = packageManager.getLaunchIntentForPackage(strPackageName); if(mainIntent!=null) { mainIntent = mainIntent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET) .addFlags(Intent.FLAG_ACTIVITY_RESET_TASK_IF_NEEDED); startActivity(mainIntent); } </code></pre> <p>Everything works fine except that while launching Camera or Google Maps i get an exception:</p> <pre><code>E/AndroidRuntime(845): FATAL EXCEPTION: main E/AndroidRuntime(845): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.camera/com.android.internal.app.ResolverActivity}; have you declared this activity in your AndroidManifest.xml? E/AndroidRuntime(845): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1536) E/AndroidRuntime(845): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1510) E/AndroidRuntime(845): at android.app.Activity.startActivityForResult(Activity.java:2858) E/AndroidRuntime(845): at android.app.Activity.startActivity(Activity.java:2964) E/AndroidRuntime(845): at com.gears42.surelock.ApplicationLauncher.onItemClick(ApplicationLauncher.java:34) E/AndroidRuntime(845): at android.widget.AdapterView.performItemClick(AdapterView.java:284) E/AndroidRuntime(845): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1696) E/AndroidRuntime(845): at android.os.Handler.handleCallback(Handler.java:587) E/AndroidRuntime(845): at android.os.Handler.dispatchMessage(Handler.java:92) E/AndroidRuntime(845): at android.os.Looper.loop(Looper.java:143) E/AndroidRuntime(845): at android.app.ActivityThread.main(ActivityThread.java:4914) E/AndroidRuntime(845): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(845): at java.lang.reflect.Method.invoke(Method.java:521) E/AndroidRuntime(845): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858) E/AndroidRuntime(845): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) E/AndroidRuntime(845): at dalvik.system.NativeStart.main(Native Method) E/AndroidRuntime(872): FATAL EXCEPTION: main E/AndroidRuntime(872): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.google.android.apps.maps/com.android.internal.app.ResolverActivity}; have you declared this activity in your AndroidManifest.xml? E/AndroidRuntime(872): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1536) E/AndroidRuntime(872): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1510) E/AndroidRuntime(872): at android.app.Activity.startActivityForResult(Activity.java:2858) E/AndroidRuntime(872): at android.app.Activity.startActivity(Activity.java:2964) E/AndroidRuntime(872): at com.gears42.surelock.ApplicationLauncher.onItemClick(ApplicationLauncher.java:34) E/AndroidRuntime(872): at android.widget.AdapterView.performItemClick(AdapterView.java:284) E/AndroidRuntime(872): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1696) E/AndroidRuntime(872): at android.os.Handler.handleCallback(Handler.java:587) E/AndroidRuntime(872): at android.os.Handler.dispatchMessage(Handler.java:92) E/AndroidRuntime(872): at android.os.Looper.loop(Looper.java:143) E/AndroidRuntime(872): at android.app.ActivityThread.main(ActivityThread.java:4914) E/AndroidRuntime(872): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(872): at java.lang.reflect.Method.invoke(Method.java:521) E/AndroidRuntime(872): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858) E/AndroidRuntime(872): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) E/AndroidRuntime(872): at dalvik.system.NativeStart.main(Native Method) </code></pre> <p>I'm using 2.2.1 HTC Wildfire (The same works perfectly on Android 3.1 Samsung Galaxy Tab)</p> <p>Any suggestions / workarounds ??</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPC.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POcamera and map crashes when launched from my custom home screen
      1. USingsaurabh
      1. VTFavorite
    2. VO
      singulars
      1. POcamera and map crashes when launched from my custom home screen
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POcamera and map crashes when launched from my custom home screen
      1. This table or related slice is empty.
      1. VTUpMod
    1. COtried cleaning ur project? this often happens with eclipse
      singulars
      1. POcamera and map crashes when launched from my custom home screen
      1. USPratik Bhat
    2. COthanks for the tip. Clean Project did not help. How can I find out how existing Home Screens (eg HTC Sense) has fixed this issue.
      singulars
      1. POcamera and map crashes when launched from my custom home screen
      1. USPC.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload