What is the directory structure of android AOSP root tree?



 

This is short version of what you will find when you download the Android source. I will leave out some minor directories and dig deeper into a couple of the important ones. Basically what you will get (based on the (Kit Kat - 4.4.4), in alphabetical order:
  • Bionic - the C-runtime for Android. Note that Android is not using glibc like most Linux distributions. Instead the c-library is called bionic and is based mostly on BSD-derived sources. In this folder you will find the source for the c-library, math and other core runtime libraries.
  • Bootable - boot and startup related code. Some of it is legacy, the fastboot protocol info could be interesting since it is implemented by boot loaders in a number of devices such as the Nexus ones.
  • Build - the build system implementation including all the core make file templates. An important file here is the envsetup.sh script that will help you a lot when working with the platform source. Running this script in a shell will enable commands to setup environment variables, build specific modules and grep in source code files.
  • Cts - the compatability tests. The test suite to ensure that a build complies with the Android specification.
  • Dalvik - the source code for the implementation of the Dalvik Virtual Machine
  • Development - projects related to development such as the source code for the sdk and ndk tools. Normally not a folder you touch when working with the platform for a target.
  • Device - product specific code for different devices. This is the place to find hardware modules for the different Nexus devices, build configurations and more.
  • External - contains source code for all external open source projects such as SQLite, Freetype and webkit.
  • Frameworks - this folder is essential to Android since it contains the sources for the framework. Here you will find the implementation of key services such as the System Server with the Package- and Activity managers. A lot of the mapping between the java application APIs and the native libraries is also done here.
  • Hardware - hardware related source code such as the Android hardware abstraction layer specification and implementation. This folder also contains the reference radio interface layer (to communicate with the modem side) implementation.
  • Kernel - not part of the default source download but you can get access to this code either by downloading it manually or by adding the repository to the repo tool. Contains the sources for the Android version of the Linux kernel.
  • Out - the build output will be placed here after you run make. The folder structure is out/target/product/. In the default build for the emulator the output will be placed in out/target/product/generic. This is where you will find the images used by the emulator to start (or to be downloaded and flashed to a device if you are building for a hardware target).
  • Packages - contains the source code for the default applications such as contacts, calendar, browser.
  • Prebuilt - contains files that are distributed in binary form for convenience. Examples include the cross compilations toolchains for different development machines.
  • System - source code files for the core Android system. That is the minimal Linux system that is started before the Dalvik VM and any java based services are enabled. This includes the source code for the init process and the default init.rc script that provide the dynamic configuration of the platform

Comments

Post a Comment

Popular posts from this blog

How To Run Compatibility Test Suite (CTS) ?

Image
How does the CTS work? The CTS is an automated testing harness that includes two major software components: The CTS test harness runs on your desktop machine and manages test execution. Individual test cases are executed on attached mobile devices or on an emulator. The test cases are written in Java as JUnit tests and packaged as Android .apk files to run on the actual device target. Pre-Requirements : Linux System  Mobile or Emulator with User Build. Download   latest CTS. Download   CTS Media files. Download   Android SDK for Linux and keep it ready.  Setup the System for CTS: 1.Create 3 folders in your system root directory.  CTS CTS_Media ADT 2. Extract and  Copy   downloaded CTS files into the   CTS   folder which you have created now . It will have below folder structure             android-cts                 repository           plans                        results           testcases                        host_confi
Read more

NFC : Reading a MiFare Classic 1K from Android Devices

Image
Ever since Near Field Communication was embedded on mobile phones, loads of new ideas and business proposals made people very busy. So does the Android platform with its API's supporting NFC. Nexus S looks like a state of the art - good starting point if one wants to get past the monotonic Nokia's piece of the cake. I just want to share with you my experience on reading a MiFare Classic tag using the Nexus S..and the Android platform.  You need to have : A MiFare Classic 1k Tag - ( hopefully you know the keys for its Blocks :=) ) Android SDK and IDE Preferable a Nexus S (Make sure if the Android version is 2.3.3 and above). Some Basics about the card: MiFare classic cards store data in its Sectors. In MiFare classic 1k card there are 16 of them. Each Sector contains 4 blocks.  You can store 16 bytes in each block. Making about 1024 bytes of storage space..that explains the 1K part of the card. You can perform common tasks like reading, writing data on these blocks, authent
Read more

Dalvik Virtual machine VS Java Virtual Machine:

Dalvik Virtual machine :          (DVM) is Register Architecture, designed to run on low memory, uses its own byte code and runs .Dex file (Dalvik Executable File) Java Virtual Machine :         (JVM) is Stack Architecture, uses java byte code and runs .class file having JIT. Java  source code is compiled by the Java compiler into .class files. Then the dx (dexer) tool, part of the Android SDK processes the .class files into a proprietary file format called DEX that contains Dalvik bytecode. Difference between .class and .dex file format           ● In DEX all the classes of the application are packed into one file.           ● All th e classes in the same DEX file share field, method, etc if they are same.           ● Classes from the same DEX file are loaded by the same class loader instance. Click on the link below to view in graphic the difference between the two:  Difference between .class and .dex file:               1) The dx tool eliminate all the re
Read more