commit | 3a0e90f9c518f44288fbb5f5a7ab8a5ed8927a87 | [log] [tgz] |
---|---|---|
author | Betty Zhou <bettyzhou@google.com> | Mon May 22 23:50:01 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Mon May 22 23:50:01 2017 +0000 |
tree | 52a07c2c30deaab2d6114f2d96295cecd1c27e56 | |
parent | 8cd3985b54b2d946cca32ba84f0217c9c4582c22 [diff] | |
parent | ed7274232b21323474711c65e1da3e15db1f2890 [diff] |
Add support of set puk and pin for puk locked sim card. am: ed7274232b -s ours Change-Id: Ic748848ef4bc15edbc47c5a9c7db7b6621172e8c
Originally authored by Damon Kohler, Scripting Layer for Android, SL4A, is an automation toolset for calling Android APIs in a platform-independent manner. It supports both remote automation via ADB as well as execution of scripts from on-device via a series of lightweight translation layers.
Due to its inclusion in AOSP as a privileged app, building SL4A requires a system build.
For the initial build of Android:
cd <ANDROID_SOURCE_ROOT> source build/envsetup.sh lunch aosp_<TARGET> make [-j15]
where <ANDROID_SOURCE_ROOT>
is the root directory of the android tree and <TARGET>
is the lunch target name
Then Build SL4A:
cd <ANDROID_SOURCE_ROOT>/external/sl4a mm [-j15]
If you are not using a custom buildspec, create one as follows:
cp <ANDROID_SOURCE_ROOT>/build/buildspec.mk.default <ANDROID_SOURCE_ROOT>/buildspec.mk
Modify the buildspec to build SL4A as a custom module by editing the line ‘#CUSTOM_MODULES:=’ to ‘CUSTOM_MODULES:=sl4a’:
sed -i 's/#CUSTOM_MODULES:=/CUSTOM_MODULES:=sl4a/' <ANDROID_SOURCE_ROOT>/buildspec.mk
Run the following command:
adb install -r <ANDROID_SOURCE_ROOT>/out/target/product/<TARGET>/data/app/sl4a/sl4a.apk
a) SL4A may be launched from Android as a normal App; or
b) To enable RPC access from the command prompt:
adb forward tcp:<HOST_PORT_NUM> tcp:<DEVICE_PORT_NUM> adb shell "am start -a com.googlecode.android_scripting.action.LAUNCH_SERVER \ --ei com.googlecode.android_scripting.extra.USE_SERVICE_PORT <DEVICE_PORT_NUM> \ com.googlecode.android_scripting/.activity.ScriptingLayerServiceLauncher"
where <HOST_PORT_NUM>
and <DEVICE_PORT_NUM>
are the tcp ports on the host computer and device.
From SL4A source directory run this command:
python Docs/generate_api_reference_md.py
In the Docs directory there should now be an ApiReference.md file that contains which RPC functions are available in SL4A as well as documentation for the RPC functions.