Many developers new to AOSP try to grep -r through a local checkout. While possible, this approach has fatal flaws when working with AOSP:
Simply put: If you do any AOSP development or analysis, xref AOSP is your most essential daily tool.
One of the most common AOSP debugging tasks is solving SELinux "avc: denied" errors. Using xref AOSP:
xref generates a browsable, hyperlinked view of your source code. It parses symbols (functions, classes, variables, macros) and lets you:
Unlike grep, it understands scope — so you don’t get false positives from comments or string literals.
Would you like a specific BibTeX entry for any of these, or a deeper summary of one paper?
Now that you know the basics, let's move to advanced workflows that separate casual browsers from power users.
Paper: “An Analysis of Power Consumption in a Smartphone” (Carroll & Heiser, USENIX ATC 2010)
The Android Open Source Project (AOSP) is a colossal beast. As of the latest Android releases, the codebase contains over 600 GB of source history and tens of millions of lines of code spread across C++, Java, Kotlin, Go, Python, and Makefiles. From the Linux Kernel drivers to the System Server and the Launcher UI, the sheer scale is daunting.
For developers, finding the definition of a specific function—say, AudioFlinger::openOutput()—by manually grepping through a local repo can take minutes. For reviewers trying to understand a patch's impact across subsystems, it’s a nightmare.
Enter Cross-Referencing (xref). In the AOSP community, xref AOSP refers to the practice of using code indexing and navigation tools to instantly jump between definitions, references, and call hierarchies. This article is your definitive guide to setting up, using, and mastering source code cross-referencing for AOSP.
It’s important to understand where xref AOSP stands compared to other tools.
| Tool | Strengths | Weaknesses | | :--- | :--- | :--- | | Xref AOSP (cs.android.com) | Official, always up-to-date, cross-repo, semantic, blame integration | Requires internet, no local editing | | Local AOSP checkout + ctags | Offline, integrates with vim/emacs | Huge disk space, slow initial build of tags, no cross-repo easily | | OpenGrok (hosted privately) | Powerful for internal forks | Outdated for main AOSP, complex to set up | | GitHub search (mirrors) | Familiar UI, easy to share links | Incomplete mirrors, no symbol-level xref, rate-limited | | Android Studio | Best for editing and running code | Requires full sync and build, heavy IDE |
For pure exploration and understanding of the public AOSP, xref AOSP is unmatched.
Many developers new to AOSP try to grep -r through a local checkout. While possible, this approach has fatal flaws when working with AOSP:
Simply put: If you do any AOSP development or analysis, xref AOSP is your most essential daily tool.
One of the most common AOSP debugging tasks is solving SELinux "avc: denied" errors. Using xref AOSP:
xref generates a browsable, hyperlinked view of your source code. It parses symbols (functions, classes, variables, macros) and lets you: xref aosp
Unlike grep, it understands scope — so you don’t get false positives from comments or string literals.
Would you like a specific BibTeX entry for any of these, or a deeper summary of one paper?
Now that you know the basics, let's move to advanced workflows that separate casual browsers from power users. Many developers new to AOSP try to grep
Paper: “An Analysis of Power Consumption in a Smartphone” (Carroll & Heiser, USENIX ATC 2010)
The Android Open Source Project (AOSP) is a colossal beast. As of the latest Android releases, the codebase contains over 600 GB of source history and tens of millions of lines of code spread across C++, Java, Kotlin, Go, Python, and Makefiles. From the Linux Kernel drivers to the System Server and the Launcher UI, the sheer scale is daunting.
For developers, finding the definition of a specific function—say, AudioFlinger::openOutput()—by manually grepping through a local repo can take minutes. For reviewers trying to understand a patch's impact across subsystems, it’s a nightmare. Simply put: If you do any AOSP development
Enter Cross-Referencing (xref). In the AOSP community, xref AOSP refers to the practice of using code indexing and navigation tools to instantly jump between definitions, references, and call hierarchies. This article is your definitive guide to setting up, using, and mastering source code cross-referencing for AOSP.
It’s important to understand where xref AOSP stands compared to other tools.
| Tool | Strengths | Weaknesses | | :--- | :--- | :--- | | Xref AOSP (cs.android.com) | Official, always up-to-date, cross-repo, semantic, blame integration | Requires internet, no local editing | | Local AOSP checkout + ctags | Offline, integrates with vim/emacs | Huge disk space, slow initial build of tags, no cross-repo easily | | OpenGrok (hosted privately) | Powerful for internal forks | Outdated for main AOSP, complex to set up | | GitHub search (mirrors) | Familiar UI, easy to share links | Incomplete mirrors, no symbol-level xref, rate-limited | | Android Studio | Best for editing and running code | Requires full sync and build, heavy IDE |
For pure exploration and understanding of the public AOSP, xref AOSP is unmatched.
