1 / 5

An Application Profiler for Android

An Application Profiler for Android. CSC 714 - FALL 2011 Arash Rezaei , Gopikannan Venugopalsamy. Problem statement. Application profiling in Android, for the purpose of finding behavior patterns of applications

zandra
Download Presentation

An Application Profiler for Android

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Application Profiler for Android CSC 714 - FALL 2011 ArashRezaei, GopikannanVenugopalsamy

  2. Problem statement • Application profiling in Android, for the purpose offinding behavior patterns of applications • The identified behavior patterns helps to differentiate the applications that consume suspicious level/patterns of resources • Android assigns each application a • UID: unique number at install time • PID (Process ID)

  3. Resources Monitoring • Two monitoring service • Time based • Memory usage • CPU usage • Sensor usage • Network usage • Event Based • File System Monitoring

  4. Resources Monitoring(cont.) • Memory usage: The ActivityManager is used to get all the running process information and also the memory usage of each application given their pids. • Includes Pss, PrivateDirty and sharedDirty • Sensor Usage: Sensor manager is the service that handles all kinds of sensors in device. Batterystats.Uid.sensor is a package that is used to obtain statistics of sensor usage of an application. • CPU Usage: The package "android.os.BatteryStats.proc" is used along the Uid of the process to get the • user time • system time • foreground time The sum of these is multiplied along the power factor which gives us the CPU usage of that  application.

  5. Resources Monitoring(cont.) • Network usage: (TrafficStats) for each App. • No. of TCP/UDP payload bytes sent/received • No. of TCP/UDP packets sent/received • No. of TCP segments sent/received • File System Monitoring: (Event driven) • File X is created • File X is opened • File X is closed • File X is modified • File X written and closed

More Related