ASE r23 Released

So, what's new?
  • Added support for adjusting and inspecting media volume. Also added inspecting the maximum volume for media and ringer. 
  • Added APIs for accessing the contacts database. 
  • pickPhone() API now returns the chosen phone number instead of the data URI. 
  • Added APIs for generating DTMF tones (see DTMF dialer example). 
Bug fixes:
  • Wake lock bugs fixed.
  • Perl error messages make more sense. 
  • SMS bugs fixed. 
  • Broken error responses fixed. 
Under the covers:
  • Usage tracking happens in a background thread pool which should make the application more responsive. 
  • Usage tracking now includes API use. Arguments are not logged, only that a particular API is used. This will help significantly with prioritizing bugs and feature development. So please, enable usage tracking! 
In the works:
  • Still working on distributing interpreters as APKs separately from ASE. This is an arduous task. 
  • More advanced triggers. 
  • A new slider input dialog.
  • A new spinner input dialog.
Visit the ASE project page to download the latest APK.


  1. Also, 2 new dialogs are being developed... :)

  2. You're absolutely right! Added that to the list.

  3. Great, can't wait for the new dialogs!

  4. This comment has been removed by the author.

  5. Hey Damon,

    I have some applications that the developers have created. And i need to test them using ASE. So since i cannot directly access the application contexts, i am trying to build ASE in my phone software testing release along with the applications. Will i be able to use ASE to test the applications then?

    I hope i have framed my question correctly. :-)

  6. Hi Roly,

    I'm using the ASE for phone automation test. My way is write the test code in Python and run in ASE to call the applications. But now, I block with the camera feature because the cameraTakePicture() function doesn't work.

  7. HI Alan,

    Yes. Thats the way to do it. Write a script in Python, and run in ASE to call applications. But the problem is when the application is standalone application, then we are unable to write new API's in ASE that can test the standalone application.
    So the question still we need to build the ASE with the application release so that we are able to write API's in ASE that can access the INTENTS, CONTEXTS for the standalone application? :-)))


  8. Sorry, Roly. I don't completely understand your question. It's possible to use ASE to craft Intents that could trigger functionality in your application. However, ASE can only test the publicly accessible parts of your application (i.e. accepted Intents, content providers, etc.). So, it can be useful for blackbox testing. If you want to test internal APIs of your application, I suggest you use the normal Android testing practices which you can find out more about online.

  9. Hey Damon,

    Thanks for your reply and explanation. I now understand it more clearly.

    Thanks again........and keep up the good work :-)