framework-services-expert

Map Android SystemServer service changes to lifecycle, API surface, and Watchdog safeguards.

40|7|Updated Mar 14, 2026

Search Tags:#watchdog #api-surface #systemserver #android-framework #binder-ipc #system-service #android-15

Ready to run

npx skills add https://github.com/jonaschen/Android-Software --skill framework-services-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: framework-services-expert
Source: https://github.com/jonaschen/Android-Software/tree/main/skills/L2-framework-services-expert
Command: npx skills add https://github.com/jonaschen/Android-Software --skill framework-services-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill maps SystemServer service changes to the right code paths, API surface updates, and runtime constraints so that agents avoid accidental deadlocks, service misregistration, and Watchdog-triggered crashes.

Core Features & Use Cases

Path scope intelligence: Focuses on frameworks/base, frameworks/native, libcore, and libnativehelper and highlights where each service lives, registers, and exposes permissions.
Lifecycle & safety playbooks: Details boot phases, service boot and phase callbacks, Watchdog monitoring patterns, and binder permission requirements to keep system_server stable.
Tooling & handoffs: Provides grep-based commands to locate implementations, API surface references, and Watchdog registrations plus handoff rules to SELinux, init, HAL, multimedia, and build experts when responsibilities cross domains.

Quick Start

Ask the framework-services-expert to map your SystemServer service change to its startup phase, API surface, and Watchdog guardrails before editing.

Frequently Asked Questions about framework-services-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a SystemServer service on Android 15 without crashing the Watchdog?▼

To add a SystemServer service on Android 15 without crashing the Watchdog, map your changes to the correct boot phase and register Watchdog monitoring patterns. This ensures your service follows the framework lifecycle and avoids deadlocks.

What's the best way to update system service APIs in frameworks/base?▼

Updating system service APIs in frameworks/base requires following binder IPC contracts and documenting permission checks. Map API surface updates to the correct code paths to prevent service misregistration and maintain system_server stability.

Why does my Android SystemServer service modification cause a deadlock?▼

Android SystemServer service modifications cause deadlocks when they violate binder IPC contracts or skip lifecycle callbacks. Ensure your changes align with boot phase callbacks and Watchdog safeguards to keep system_server stable.

Can I use this to locate Watchdog registrations across frameworks/native and libcore?▼

Yes, this provides grep-based commands to locate Watchdog registrations and API surface references across frameworks/native, libcore, and libnativehelper. It helps identify where each service lives and exposes permissions.

When should I hand off SystemServer changes to SELinux or HAL experts?▼

You should hand off SystemServer changes to SELinux, init, or HAL experts when responsibilities cross domains and extend beyond the framework lifecycle. This ensures binder permission requirements and forbidden action guards are correctly applied.