This article is intended for users of Debenu Quick PDF Library for Android.

The Android Virtual Device (AVD) is an emulator configuration that lets you model an actual device by defining hardware and software options to be emulated by the Android Emulator. It comes as an optional download when you install Android Studio.

Please note: Android Emulator’s can be quite slow to load and performance is lower than what you get if you test directly on a physical device. However, it gives you the opportunity to test a variety of different device form factors and phone/tablet models.

  1. In Android Studio go to “Tools (Menu Bar) >Android > AVD Manager.
  2. Click on the “Create Virtual Device” button.avd_step2
  3. Select “Phone” or “Tablet” as Category and select the device which you want to use to make a Virtual Device. Then click on the “Next” button. Note: select a small screen device for better emulator performance. Devices with a large screen will have a longer launch time (Nexus 4, Nexus 5 etc).avd_step3
  4. Select the System Image i.e. the API level of Android OS (KitKat, Lollipop etc). Debenu Quick PDF Library for Android requires an API level of 15 or higher.avd_step4
  5. Now you will see options to verify the Emulator Settings otherwise you may change the settings according to your requirement from this dialog as well and then click on the “Finish” button.avd_step5
  6. Now you will see the newly created Emulator in the list of available Android Virtual Devices.avd_step6
  7. After launching the Emulator (by double-click on the Emulator option that you want to use as show in the screenshot above), wait for the “Home Screen” to load on the Android Virtual Device and then run the application. It’s important that the Virtual Device has finished loading before you try to run the application otherwise it won’t be recognized by Android Studio and you will be prompted to launch the Emulator again which can cause issues. Once the Virtual Device has loaded and you have run the application the dialog below will appear and you can select the Android device that you wish to use.avd_step7
  8. Finally you should now see your application running in the Android Emulator.


  1. Android Studio can be a bit sensitive with the Emulators. If you find the Emulator isn’t working (when it has previously worked) check the task manager and remove any loaded Emulator processes. If that doesn’t work try rebooting. This can be an issue in step 7 if you try loading the same Emulator twice you will find that it a) doesn’t let you and b) causes ongoing issues until you have resolved the conflict (as already mentioned, rebooting helps but is not the most efficient).
  2. We suggest launching the Emulator first from the ADV Manager and waiting for the Emulator to fully load the device (i.e. homescreen is shown) before trying to run the app on the Emulator. If the Emulator has not fully loaded then it will not be shown in the Choose Device screenshot shown in step 7 when you try running the app and then it will give you the option to launch the Emulator again and this will just result in frustrating Emulator conflict issues. Refer to note #1.