Developing Android Platform Tools
5 likes1,174 views
1. The document discusses tools for Android platform development and proposes a new architecture using Node.js, Express, and JavaScript for building lightweight monitoring tools. 2. It describes initial pain points such as looking up AIDL files and monitoring processes/filesystem, and demonstrates a tool called Raidl that returns AIDL interfaces. 3. The proposed architecture uses a Node.js backend with Express and a Backbone.js frontend, allowing tools to be built for process monitoring, file browsing, and analyzing Binder relationships between services.
![18
5.1. Example Output
root@generic:/data/local/tmp # ./raidl iface -n power
// Service: power, Interface: android.os.IPowerManager
package android.os;
interface IPowerManager {
void acquireWakeLock(IBinder p1, int n2, String s3, String s4, WorkSource p5, String
s6); // 1
void acquireWakeLockWithUid(IBinder p1, int n2, String s3, String s4, int n5); // 2
void releaseWakeLock(IBinder p1, int n2); // 3
void updateWakeLockUids(IBinder p1, int[] p2); // 4
void powerHint(int n1, int n2); // 5
void updateWakeLockWorkSource(IBinder p1, WorkSource p2, String s3); // 6
boolean isWakeLockLevelSupported(int n1); // 7
void userActivity(long n1, int n2, int n3); // 8
void wakeUp(long n1); // 9
void goToSleep(long n1, int n2, int n3); // 10
void nap(long n1); // 11
boolean isInteractive(); // 12
boolean isPowerSaveMode(); // 13
boolean setPowerSaveMode(boolean p1); // 14
void reboot(boolean p1, String s2, boolean p3); // 15
void shutdown(boolean p1, boolean p2); // 16
void crash(String s1); // 17
void setStayOnSetting(int n1); // 18
void setMaximumScreenOffTimeoutFromDeviceAdmin(int n1); // 19
void setTemporaryScreenBrightnessSettingOverride(int n1); // 20
void setTemporaryScreenAutoBrightnessAdjustmentSettingOverride(float p1); // 21
void setAttentionLight(boolean p1, int n2); // 22
}](https://image.slidesharecdn.com/platform-tools-150324-150428183019-conversion-gate01/85/Developing-Android-Platform-Tools-18-320.jpg)
![22
5.5. Raild - Running an .apk
● .apk == .jar (with some DEX code)
● DexClassLoader:“A class loader that loads
classes from .jar and .apk files [...]”
● Ergo:
export CLASSPATH=/system/app/raidl.apk:/system/app/raidl/raidl.apk
exec app_process /system/app com.opersys.raidl.Raidl "$@"](https://image.slidesharecdn.com/platform-tools-150324-150428183019-conversion-gate01/85/Developing-Android-Platform-Tools-22-320.jpg)
![36
9.1. Reaching Inside Android
● JSLibBinder – libbinder for Android
var Binder = require("jslibbinder"),
var sm = new Binder.ServiceManager();
var services = sm.list();
var i = 0;
console.log("Found " + services.length + " services:");
services.forEach(function (s) {
console.log((i++) + "t" + s
+ ": [" + sm.getService(s).getInterface() + "]");
});](https://image.slidesharecdn.com/platform-tools-150324-150428183019-conversion-gate01/85/Developing-Android-Platform-Tools-36-320.jpg)
Developing Android Platform Tools
- 1. Developing Android Platform Tools Android Builders Summit 2015 François-Denis Gonthier @fdgonthier
- 2. 2 AboutAbout ● Author and maintainer of: ● github.com/opersys/raidl
- 3. 3 Agenda ● What's out there? ● What's the problem? ● Our Objectives ● Initial Set of Pain Points ● raidl – AIDL file lookup ● Architecture for Creating Monitoring Tools ● Process Explorer ● File Explorer ● Binder Explorer ● The Road Ahead
- 4. 4 1. What's Out There Now? ● Official App Dev Tools ● Official Platform Dev Tools ● 3rd Party App Dev Tools ● 3rd Party Platform Dev Tools
- 5. 5 1.1. Official App Dev tools ● Eclipse Android Development Kit ● Android Studio (IntelliJ) ● DDMS ● Plenty of documentation
- 6. 6 1.2. Official Platform Dev Tools ● Tools on the previous pages ● gdb / gdbserver ● ftrace, systrace, atrace ● perf
- 7. 7 1.3. 3rd Party App Dev Tools ● CrossWalk / Cordova ● Delphi ● Xamarin.Android ● etc.
- 8. 8 1.4. 3rd Party Platform Dev Tools ● Qualcomm tools ● Intel tools, Nvidia tools, etc ● ARM Tools – DS-5 ● JTAG -- Lauterbach
- 9. 9 2. What's The Problem? ● Google obviously catering to app developers – App dev tools have nice finish – Platform dev tools ... ● Official tools heavily tied to app dev IDE – Requires IDE-specific knowledge to extend/customize – Assumes official IDE is being used and/or is present ● Platform is huge
- 10. 10 2. What's The Problem ● Documentation is often spartan ● Existing platform dev tools assume internals understanding – Do you truly know how to use “dumpsys procstats”, “dumpsys meminfo” or “vdc” ● Most platform tools can only be used on the command line ● Most 3rd party tools assume on-screen rendering of information
- 11. 11 3. Our Objectives ● Reduce barrier to entry for platform development ● Catter for unmet patform developer needs ● Easy to use platform dev tools ● Build on lightweight/mainstream technologies: – No IDE-specific tie-in – Extensible language – Large ecosystem of reusable packages/add-ons ● Avoid monopolizing device screen
- 12. 12 4. Initial Set of Pain Points ● Looking up AIDL interfaces ● Monitoring Processes ● Viewing / Manipulating the Filesystem ● Understanding Binder Relationships
- 13. 13 4.1. Getting AIDL files ● find -name “*File.aidl” ● godir ● Android documentation – Focused on app developers – Doesn't cover everything
- 14. 14 4.2. Process Monitoring ● ps / top ● htop (Cyanogenmod) ● Studio/Eclipse/DDMS/Monitor integrated ● On the Play Store... – ... hundreds of candidates – Few are aimed at developers
- 15. 15 4.3. Filesystem Monitoring/Browsing ● ls, find ● adb push/pull ● On the Play Store... – ... hundreds of candidates – Few are aimed at developers
- 17. 17 5. Raidl - Features ● Returns the AIDL interface of a service – AIDL based service – Best effort for other services (Activity service) – No interface for C++ service – No parameters names
- 18. 18 5.1. Example Output root@generic:/data/local/tmp # ./raidl iface -n power // Service: power, Interface: android.os.IPowerManager package android.os; interface IPowerManager { void acquireWakeLock(IBinder p1, int n2, String s3, String s4, WorkSource p5, String s6); // 1 void acquireWakeLockWithUid(IBinder p1, int n2, String s3, String s4, int n5); // 2 void releaseWakeLock(IBinder p1, int n2); // 3 void updateWakeLockUids(IBinder p1, int[] p2); // 4 void powerHint(int n1, int n2); // 5 void updateWakeLockWorkSource(IBinder p1, WorkSource p2, String s3); // 6 boolean isWakeLockLevelSupported(int n1); // 7 void userActivity(long n1, int n2, int n3); // 8 void wakeUp(long n1); // 9 void goToSleep(long n1, int n2, int n3); // 10 void nap(long n1); // 11 boolean isInteractive(); // 12 boolean isPowerSaveMode(); // 13 boolean setPowerSaveMode(boolean p1); // 14 void reboot(boolean p1, String s2, boolean p3); // 15 void shutdown(boolean p1, boolean p2); // 16 void crash(String s1); // 17 void setStayOnSetting(int n1); // 18 void setMaximumScreenOffTimeoutFromDeviceAdmin(int n1); // 19 void setTemporaryScreenBrightnessSettingOverride(int n1); // 20 void setTemporaryScreenAutoBrightnessAdjustmentSettingOverride(float p1); // 21 void setAttentionLight(boolean p1, int n2); // 22 }
- 19. 19 5.2. Raidl - Demo
- 20. 20 5.3. Raidl – How Does It Work? ServiceStubClass = Raidl.class.getClassLoader() .loadClass(serviceClass.getCanonicalName()+"$Stub"); for (Field serviceField : serviceStubClass.getDeclaredFields()) { // Get the fields that look like transaction code. } for (Method serviceMethod : serviceClass.getMethods()) serviceMethods.put(serviceMethod.getName(), serviceMethod); for (Integer serviceCode : serviceCodesMethods.keySet()) { // ... if (serviceMethod != null && isRemoteMethod(serviceMethod)) aidlService.addMethod(serviceCode, serviceMethod); }
- 21. 21 5.4. Raild - Integrate in AOSP Build LOCAL_PATH:= $(call mydir) include $(CLEAR_VARS) LOCAL_SRC_FILES := $(call alljavafilesunder, src) LOCAL_PACKAGE_NAME := raidl LOCAL_MODULE_TAGS := optional LOCAL_PROGUARD_ENABLED := disabled include $(BUILD_PACKAGE) include $(CLEAR_VARS) LOCAL_SRC_FILES := raidl LOCAL_MODULE_PATH := $(TARGET_OUT)/bin LOCAL_MODULE_CLASS := EXECUTABLES LOCAL_MODULE := raidl LOCAL_MODULE_TAGS := optional include $(BUILD_PREBUILT)
- 22. 22 5.5. Raild - Running an .apk ● .apk == .jar (with some DEX code) ● DexClassLoader:“A class loader that loads classes from .jar and .apk files [...]” ● Ergo: export CLASSPATH=/system/app/raidl.apk:/system/app/raidl/raidl.apk exec app_process /system/app com.opersys.raidl.Raidl "$@"
- 23. 23 6. Architecture for Creating Monitoring Tools
- 24. 24 6.1. Tool architecture ● Backend: Node.js + Express ● Frontend: Backbone.js + w2ui ● AJAX communication ● Websocket or Server-Sent events
- 25. 25 6.2. Node.js in Android – Why? ● One language to rule them all: Javascript ● 132 510 Node.js packages ● Ease of use ● Web 2.0 support (SSE, WebSockets) ● Speed – V8 – Binary modules ● Runtime independence ● Few actual alternatives: Go, C/C++, Python, etc.
- 26. 26 6.3. Node.js – It's easy! var express = require('express'); var app = express(); app.get('/home', function(req, res) { res.send('Hello World'); }); app.listen(process.env.PORT || 8080);
- 27. 27 6.4. Node.js in Android – Why not? ● Still pretty slow ● Runtime independence – Node is within its Linux bottle ● Difficult to package in Android ● It's Javascript – WAT! https://www.destroyallsoftware.com/talks/wat
- 28. 28 6.5. How to use Node.js on Android ● Older versions (0.8), binaries available – Too old for comfort ● Development version (0.11, now 0.12) was patched with Android support ● Backported to 0.10 ● V0.10 Binaries are avaible! ● Io.js and Node v0.12: TBD. ● https://github.com/fdgonthier/node
- 29. 29 6.6. Distribution ● Extracted in local files ● Multiple binary packages – ARM, ARM + PIE, ia32, ia32 + PIE ● Started by a simple Android application ● Able to start as root
- 30. 30 7. Process Explorer ● Browser based process manager ● Displays logcat (live!) ● Process statistics – /proc based ● Needs root access for better function ● Works on Chrome and Firefox
- 31. 31 7. Process Explorer - Demo
- 32. 32 8. File Explorer ● Browser based file manager for Android systems ● File upload/download ● File updates (live!) ● Needs root access for better function
- 33. 33 8. File Explorer - Demo
- 34. 34 9. Binder Explorer ● In development... ● Analysis of the links between Binder Services and Android applications ● Uses data from /sys/kernel/debug/binder ● Pushing further: JSLibBinder
- 35. 35 9. Binder Explorer - Demo
- 36. 36 9.1. Reaching Inside Android ● JSLibBinder – libbinder for Android var Binder = require("jslibbinder"), var sm = new Binder.ServiceManager(); var services = sm.list(); var i = 0; console.log("Found " + services.length + " services:"); services.forEach(function (s) { console.log((i++) + "t" + s + ": [" + sm.getService(s).getInterface() + "]"); });
- 37. 37 10. The Road Ahead ● New Features: – Raidl – service to JS Binder interfaces – Process Explorer new version has: ● More /proc data: memory, network, process maps, etc. – File Explorer ... – Binder explorer: ● Allow JS calls to Binder ● New Tools: – We've got our ideas ;D – We'd like to hear from you: What are you looking for?