commit | e8de2ddb30a52e2920c53a3f840977a262d91775 | [log] [tgz] |
---|---|---|
author | Girish Moturu <gmoturu@google.com> | Mon Jul 02 12:27:14 2018 -0700 |
committer | Girish Moturu <gmoturu@google.com> | Mon Jul 23 13:37:46 2018 -0700 |
tree | 067d53a9918c9390997f2b3c7be61dde90a7ddd0 | |
parent | 6f4e7c816372444f74d4715963db6ed22dd6b695 [diff] |
[ConnectivityManagerFacade] Changes to Natt Keepalive APIs CHERRY PICKED FROM AOSP connectivityStartNattKeepalive() returns a key which allows us to listen for a 'Started' event using connectivityNattKeepaliveStartListeningForEvent(). Similarly, to listen to a 'Stopped' event we use connectivityNattKeepaliveStopListeningForEvent(). However, connectivityStopNattKeepalive() deletes the key, which makes the API useless. Added a new API to delete the key. Bug: 72420688 Test: Verified the changes Change-Id: Ia7a43e5d03ee55a92b367035d7152901ec907df3 Merged-In: I762ad5e0f8e7346d09d2c2904d7cbd65a25e58e8
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.