title: Appium: Should not start App or Activity on startup / Testing unlock passcodes
body: <p>I have to test some Android devices for there security policies.
  So when an update or the policies comes out for one of the secured apps we can run our test to ensure the update/policies are not going to open new security issues.</p>
  
  <p>We decided to use Appium to automate our test cases.</p>
  
  <p>I'm stucking now on running the launcher app.
  I preferred not to open an App on startup, because there is no app that should be tested. But Appium reqiered an declared activity and package.
  I decided to specify the launcher app as entry point, that's working fine but, if the device is locked, appium cannot launch the launcher app and it is stucking.</p>
  
  <p>I tried to use "unlockType" and "unlockKey" to unlock the device, this is also working, it unlocks the device once at the beginning but i have to test several unlocking scenarios (e.g. device wipe after entering 10 wrong passcodes).</p>
  
  <p>Does some one have a idea how to test this scenario properly?
  Or is Appium generally not usable to test whole devices?</p>
  
  <p>Thank you for your ideas and opinions!</p>