You will need to choose an activity to launch, but seeing that you cannot inherently know where the launchable activities are or what they're called, I thought I'd include the process of finding a launchable activity in this recipe.

Here's an example you can try out:

dz> run app.activity.start –-action android.intent.action.MAIN –-category android.intent.category.LAUNCHER –-component com.android.browser com.android.browser.BrowserActivity

Let's take a look at the drozer source code to find out exactly how it manages to launch some activities.

.... #some code has been omitted for brevity
def execute(self,arguments)
  intent = android.Intent.fromParser(arguments)

  if len(intent.flags) == 0:
    intent.flags.append('ACTIVITY_NEW_TASK')

  if intent.isValid():
    self.getContext().startActivity(intent.buildIn(self))
  else:
    self.stderr.write('invlaid intent: one of action or component must be set')
...#some code has been omitted for brevity

So, what we see here is that drozer simply bundles user-supplied arguments into an intent after pulling it through the argument parser; it then sends over this intent after checking if the intent is valid. This works the same way an intent would from an Android application.

You can go about finding activities to launch using the app.activity.forintent module.

This nifty module lets you search for activities based on a given intent action and category; here's how to do that:

dz> run app.activity.forintent –-action [intent action] –category [intent category]

Here's an example:

dz> run app.activity.forintent –-action android.intent.action.VIEW –-category android.intent.category.DEFAULT