The primary mechanism for xref in large open-source projects is the LSP (Language Server Protocol) for local development and Web-based Indexers for remote browsing.

AOSP generates IDE project files natively.

# From your AOSP root
source build/envsetup.sh
lunch aosp_cf_x86_64_phone-userdebug
make idegen && development/tools/idegen/idegen.sh

This creates android.ipr and android.iml. Opening this in Android Studio gives you:

Location in AOSP: frameworks/base/services/core/java/com/android/server/usage and frameworks/base/core/java/android/app/usage

The Problem: Currently, Android's battery usage screen (Settings > Battery) tells you how much battery an app used, but not why or how efficiently it used it. An app might use 1% battery, but if it did so by waking the device up 500 times in the background for no reason, it is behaving poorly. Users and developers lack a quick "efficiency" metric.

The Feature: An "App Health Score" assigned to every installed application. This is a weighted metric (0-100) calculated by the UsageStatsManager that reflects how efficiently an application behaves on the specific device.

Calculation Logic (Internal): The score would be derived from existing data points already collected by UsageStatsService:

User Experience (Settings UI): In Settings > Apps > [App Name] > Battery, display a badge next to the usage graph:

Developer Value: This creates a passive incentive for app developers to optimize their background processing logic to maintain a "green" score, similar to how developers optimize for Android Vitals, but visible directly on the user's device.