RILAnalyzer. A comprehensive cross-layer monitoring tool for mobile traffic.
RILAnalyzer is a set of android processes that provides cross-layer monitoring tools for user-app-cell net interactions. It can be used to identify app inefficiencies, debugging and also for monitoring apps for research purposes. It also maps traffic to processes.
Narseo Vallina-Rodriguez, ICSI-Berkeley and University of Cambridge
Andrius Aucinas, University of Cambridge
Yan Grunenberger, Telefonica Research
Collaborators: Jon Crowcroft (University of Cambridge) and Dina Papagiannaki (Telefonica Research). We would like to thank as well the help of Armando Garcia-Mendoza (Telefonica Research) on an earlier attempt.
Networklog was implemented by PRAGMA. This is a customised version to improve traffic accounting and to log data locally on the sdcard.
The current version only supports xgoldmon chipsets. It has been tested for Samsung Galaxy S2 and Samsung Galaxy S3 running Android 4. See our IMC'13 paper for more details about its goals, features and limitations. Paper. If the tool is used for academic purposes, we would appreciate if you cite it.
Current instalation process is tedious due to OS permissions. See instructions below. Please refer to the wiki for more detailed information on the rilAnalyzer architecture. See logger process and networklog to see the structure of the different logging files (we will update that on the wiki soon).
Android APK for monitoring RNC events. It directly polls the radio interface to collect RNC state. This APK has to run as a system service because of Android permissions.
Runs as a background service launched on boot by the OS. Data output is written on /sdcard/ril_log.txt by logger process (See below). The logging procedure be customized and quite improved.
Traffic monitor app exploiting iptables nflog feature. It collects mobile traffic at IP level.
This APK has to be launched by the user for the first time and then modify the app settings to launch it automatically on boot. Data output is written by itself on /sdcard/networklog.txt (can be customized).
It also makes sure that required processes (e.g. iptables flags) are set up correctly.
Binary (c) that runs in the background and reads UDP packets from RILAnalyzr and saves them on the SD Card.
Requires Android NDK for building it.
Rudimentary transparent proxy to collect data using a transparent tun interface. It is no longer needed if networklog is used but it can be of use for capturing mobile traffic without relying on iptables or tcpdump.
Requires Android NDK for building it. Use same process as logger binary to install it on the phone and follow the steps described in the wiki to set up a tun interface on android
Building and Instalation:
IMPORTANT: Requires rooted devices.
Install Android SDK and NDK.
Create and import projects separately on Eclipse.
Remove Samsung Service Mode:
$adb shell mount -o rw,remount /system $adb shell rm /system/app/SamsungServiceMode.apk $adb shell mount -o ro,remount /system
To build rilanalyzr.apk, you need to import android's framework.jar
Build logger process using Android NDK (with the right target). It is required for storing RNC events on /sdcard/. To install, move the binary to /system/ so it is automatically launched on boot:
$adb shell mount -o rw,remount /system $adb push SOURCE_LOGGER /system/bin/ $adb shell mount -o ro,remount /system
Use ADB to put send APKs to mobile handset:
$adb shell mount -o rw,remount /system $adb push source_rilanalyzer_apk /system/app/ $adb push source_networklog_apk /system/app/ $adb shell mount -o ro,remount /system
Launch Networklog manually. RILAnalyzer and logger binary should be automatically launched on boot. To stop and remove all the logging capabilities, remove the files manually (mount filesystem with the right permisions accordingly):
$adb shell rm PATH_TO_APK/BINARY
The logging processes are very CPU and memory intense. The battery life of the handset can be quickly drawn. The main reason for such inefficience is the lack of firmware and OS support to collect RNC states on the user space. As a consequence, we are forced to poll the firmware every second.
For further details, suggestions and collaborations, do not hesitate to contact us.