commit | 8fcc233baf2af351501ddf67f933aa8c6ca5e1d7 | [log] [tgz] |
---|---|---|
author | Karsten Tausche <karsten@fairphone.com> | Wed Mar 15 16:16:44 2023 +0100 |
committer | Karsten Tausche <karsten@fairphone.com> | Wed Mar 15 16:16:44 2023 +0100 |
tree | ff8f205cc61b979d30cb928ece6af0bf08656e73 | |
parent | 385654deb31efcaee1b82dabed3a0e9a20dad59c [diff] | |
parent | 27ec3912b32ad3c939bcbac25a90b6e5f1d3ad5e [diff] |
Merge tag 'android-13.0.0_r32' into int/13/fp3 Android 13.0.0 release 32 * tag 'android-13.0.0_r32': Added API to trigger PIN/PUK commands for specific subscription. Make this not fail if test passed an address that doesn't exist. Add rahulsabnis@ as an owner Listen for bond state changes in bonding SL4A APIs and adds SL4A interface to reconnect over GATT Update oob bonding interface to use oob data's address type Change-Id: I585f3d85cf98f1d6af19fefd9c227bff63ff85f0
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>/testcases/sl4a/arm64/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.