Skip to main content

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 :-)


Post a Comment

Popular posts from this blog

Android Recipes and Snippets

I've put together a small collection of Android recipes. For each of these recipes, this is an instance of Context (more specifically, Activity or Service) unless otherwise noted. Enjoy :)

One of the coolest things about Android is Intents. The two most common uses of Intents are starting an Activity (open an email, contact, etc.) and starting an Activity for a result (scan a barcode, take a picture to attach to an email, etc.). Intents are specified primarily using action strings and URIs. Here are some things you can do with the android.intent.action.VIEW action and startActivity().Intent intent = new Intent(Intent.ACTION_VIEW);
// Choose a value for uri from the following.
// Search Google Maps: geo:0,0?q=query
// Show contacts: content://contacts/people
// Show a URL:
startActivity(intent);Other useful action/URI pairs include:Intent.ACTION_DIAL, tel://8675309Intent.ACTION_CALL…
Read more

Email Injection

Not so long ago, I ran a wiki called SecurePHP. On that wiki, there was one particular article about email injection that received a lot of attention. Naturally, with all the attention came lots of spam. As a result, I disabled editing of the wiki and content stagnated. Still, the email injection article remained popular. About a year later, the server that hosted SecurePHP died and I never had a chance to hook it all back up. I saved the article though and I'm reposting it now. It may be a bit old (I've been away from PHP for a long time), and I didn't write all of it, so feel free to leave comments about needed updates and corrections. Though this article focuses on PHP, it provides a lot of general information regarding email injection attacks.

The PHP mail() FunctionThere are a lot of ways to send anonymous emails, some use it to mass mail, some use it to spoof identity, and some (a few) use it to send email anonymously. Usually a web mailform using the mail() function …
Read more

XBee ZNet 2.5 Wireless Accelerometer

I managed to put together a wireless accelerometer the other night using my two new XBees, an Arduino XBee shield, an XBee Explorer USB, an ADXL330, and some Python. I struggled a bit with some of it, so here's what I learned:

First, a parts list.
XBee 2mW Series 2.5 Chip AntennaArduino XBee (with XBee Series 2.5 module)XBee Explorer USBADXL330I'm not sure exactly what the specs are on the XBee that comes with the Arduino shield. But, it is definitely a series 2.5.

The first thing to do is to configure and upgrade the firmware on your XBees. To do that, you'll need X-CTU (for the firmware upgrade at least, but it's also nice for configuration) which, unfortunately, is only available for Windows. But, it works fine from VMware. First up, the XBee we'll hook up to the computer to read incoming data from the accelerometer:
Plug one of the XBees into the Explorer (it's also possible to do this from the Arduino shield by shifting the two XBee/USB jumpers to USB and remo…
Read more