Having trouble? Got questions? Check the FAQ or try the SL4A discussion group.
SL4A makes it possible to quickly prototype applications for Android on the device itself using high-level scripting languages. These scripts have access to many of the APIs available to full-fledged Android applications, but with a greatly simplified interface. Have a look at some of the example scripts to see for yourself.
That's very true. Android's development environment does make life pretty easy. But, you're tied to a computer to do your work. SL4A lets you try out an idea now, in the situation where you need it, quickly. After that, you can take what you learned and turn it into a real application!
SL4A provides Android facades which make APIs available via JSON RPC calls. Only the parts of Android's APIs which has been wrapped by facades are available to interpreters.
Does SL4A compile the supported languages to Dex bytecode or is there an additional layer of interpretation?
It depends on the language a bit. BeanShell is run in the JVM and has an additional layer of interpretation. Lua, Python, and Perl are actually the C versions running natively.
All interaction with Android is over RPC channels. Still, the RPC API is compiled to dex so there's no additional interpretation in Java (other than reflection).
With respect to the interpreters SL4A provides, Lua and Python are both cross compiled C binaries that run in their own process. CPython is significantly more performant than Jython (especially since Android does not currently support JIT).
As for the Android facades, the API is primarily focused on making it easier to write scripts than on the performance of those scripts. That said, remember the adage "measure first, then optimize." SL4A is about rapid development after all.
If you have performance concerns for your application, it's probably better to use the standard Android SDK (or NDK) where you'll have more control over the system.
Yes, mostly. You can invoke arbitrary intents and there are also plans to support broadcast receiver scripts. That is, you could write an app that consumes photos and shows up in the list of apps when the user presses Share in the Camera app.
It is not currently possible to write a script that will exit with a result (e.g. another Android activity starts your activity for result).
BeanShell, JRuby, and Rhino basically give you a complete API bridge (you can invoke Java calls directly). See the documentation for those interpreters for instruction on how to accomplish this. Cross compiled languages like Lua are more restricted. They only have access to the APIs exposed through the RPC layer. See the API reference for a list of currently supported APIs. The RPC layer is easy to extend.
Barcodes are a easy way to access a web link on your phone (e.g. to download SL4A). To read the barcodes, you'll need to install the barcode scanner application.
First, if you're running Cupcake or another older version of Android, make sure you've installed TTS support. If you have it installed, run the TTS activity and try playing the sample sound. If you can't hear it, try turning up the volume. Once that works, try your script again in SL4A.
If you have Donut or beyond, TTS comes with the phone. Check your phone's speech synthesis settings.
As of release 0.8 alpha, interpreters and sample scripts are distributed separately. Please read InstallingInterpreters for directions on how to add them.
All SL4A languages share the same common set of APIs. These are documented online and in the API browser within SL4A itself.
If you have a rooted phone, you may be interested in doing so. At the moment, SL4A does not support this directly. However, issue 184 is tracking this feature request.
- Enable "Unknown Sources" under Application settings.
- Install Barcode Scanner.
- Scan the barcode on the home page to download the APK.
- Tap on the downloaded APK to install SL4A.
Yes! You can embed your script in a (mostly) stand alone APK.
Not yet. We're working on it. See issue 271.
Yes. Use adb install sl4a_rnn.apk to install it to the emulator.
Yes and no. All cross compiled interpreters are compiled for ARM. Java based interpreters like JRuby, BeanShell, and Rhino will work.
Yes. See IntentBuilders.java.
Yes. Many pure Python modules will work if you simply add them to
/sdcard/com.googlecode.pythonforandroid/extras/python as long as they don't
depend on any C Python modules that aren't included with SL4A. You can, of
course, cross compile your own C Python modules. It's not for the faint of
heart, but see
here for
more detail,
Python eggs are supported, to a degree. The egg will have to have been
compiled using these instructions.
Then, download the egg into your downloads folder (this will typically be
/sdcard/Download, and is the default used by your browser) then use
the Install Module button on the Python Installer.
This will only work on release 4 or above. See python-for-android for more detail.
Your phone turns the screen off, among other things, when it goes to sleep. If an application doesn't request that it keep running when the phone is asleep, it will stop running until the phone wakes up again (i.e. you turn the screen back on). Requesting that the device remain on while your application is running is called a wake lock.
SL4A provides APIs for acquiring and releasing wake locks. It is important to note that wake locks significantly impact battery life. You should always release a wake lock as soon as possible.
Instead of using a wake lock, you can also enable the "Stay awake" system setting. From your home screen tap Menu, Applications, Development, and check Stay awake. With that enabled, your phone will never sleep while charging. This does affect the amount of time it takes to charge your phone, however.
Take a look at the remote control wiki page.
No. For security reasons, it is only possible for the shell user to inject UI
events into arbitrary applications. See UI/Application
Excersier in
the Android documentation.
If you enable "Usage Tracking", the application will collect anonymous usage information through Google Analytics.
JavaScript is implemented using the Mozilla Rhino project and V8. Look for "Rhino" in the interpreter downloads. Or, write an HTML script to use V8.
There is a PHP interpreter, which is a separate project. The PHP installer and interpreter can be found there.
Logcat is a rotating log of messages that Android produces. It's a very useful tool for programmers to work out what exactly is going on if someone reports and error. It's a requirement in our Issues reporting to attach a logcat wherever possible. See LogcatDump for several different ways to produce.
In fact, SL4A works fine on emulators, having been to a large degree developed on them. But these interpreters require a bit of room, and the default AVD size for a sdcard is on 16Mb. This is inadequate. I would allocate a minimum of 128Mb, and in fact commonly set mine to 512Mb. Bear in mind that it's unusual to get an Android device with less than 2Gb these days.
See this page: RunPythonAsScript
Please file an issue.