No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
bojie Merge pull request #2 from chirayudesai/patch-1
README: update links and contacts
Latest commit d23b0e4 Mar 15, 2013
Failed to load latest commit information.
apkanalyser first commit Apr 13, 2012
apktool first commit Apr 13, 2012
smali first commit Apr 13, 2012
README README: update links and contacts Feb 18, 2013


 Copyright (C) 2012 Sony Mobile Communications AB

 This file is part of ApkAnalyser.

 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 See the License for the specific language governing permissions and
 limitations under the License.


ApkAnalyser is a static, virtual analysis tool for examining and validating 
the development work of your Android app. It's a complete tool chain which supports 
modification of the binary application with more printouts. You are then able to 
repack, install, run and verify the result from logcat. ApkAnalyser also supports 
resource analysis, and you can decode XML, look up resource references and detect 
potential issues in your app.

It��s a stand-alone J2SE application, released under Apache 2.0 license, 100% written in Java.

Open Source Projects

Some code of following OSS projects are imported and modified:
1. smali, dalvik assembler/disassembler,
2. apktool, reengineering binary Android apps,
3. Android4ME, J2ME port of Google's Android,
4. Android Open Source Project

Following OSS projects are used as jar library:
1. ASM, Java bytecode manipulation and analysis framework, 
2. Jgraphx, Java Graph Visualization Library,
3. Xpp3, a streaming pull XML parser,
4. L2fprod, extended swing components,

Build Infomation

Firstly, the latest ApkAnalyser is available at:

ApkAnalyser includes two open source projects, smali and apktool.
The projects must be built in sequence of:

1. smali
2. apktool
3. apkanalyser

All of the projects are managed by Maven2 build system.

The project could be built on JDK1.5, 1.6 or 1.7.

Build Steps

1. Get the latest code 
git clone git://

2. Build smali project
cd smali
mvn install

3. Build apktool project
cd ../apktool
mvn install

4. Install jgraphx into local Maven repository
cd ../apkanalyser
mvn install:install-file -Dfile=lib/jgraphx.jar -DgroupId=com.mxgraph -DartifactId=jgraphx -Dversion= -Dpackaging=jar -DgeneratePom=true

5. Build and package ApkAnalyser
mvn assembly:assembly

6. The executable jar file should be at 

Optionally, Eclipse project could also be generated by "mvn eclipse:eclipse" command.

Launch ApkAnalyser

To launch it, just execute: 

java -jar ApkAnalyser.jar

Sometimes, ApkAnalyser consumes lots of memory for analysing the dalvik bytecodes. 
It may run out of memory expecially for loading more than one big odexed APK files.
In that case, the max heap size should be explicitly incrased by "-Xmx1024m" parameter: 

java -Xmx1024m -jar ApkAnalyser.jar


Zhang Bojie, Sony Mobile Communications