Implement and review native C++ Binder services for AOSP using libbinder.
npx skills add https://github.com/Binh230199/ai --skill android-binder-native
Please help me install this Agent Skill. Skill: android-binder-native Source: https://github.com/Binh230199/ai/tree/main/.github/skills/android-binder-native Command: npx skills add https://github.com/Binh230199/ai --skill android-binder-native
Manually writing native Binder services is error-prone, and this Skill helps you design, review, and debug libbinder-based IPC code for AOSP without missing transaction, parcel, or threading details.
Ask for a native Binder service implementation or review plan for your AOSP service, including the interface, proxy, stub, service registration, and client-side usage.
High-intent search queries and answers about installing and using this skill.
To implement a native C++ Binder service in AOSP using libbinder, you must define IInterface, BnInterface, and BpInterface structures, handle Parcel marshaling, dispatch onTransact calls safely, and register with ServiceManager.
Handling Parcel transactions in libbinder requires serializing data correctly, validating interface tokens, and dispatching onTransact calls safely. You must ensure ordered parcel read and write operations to maintain data integrity.
Setting up a thread pool and death notifications for an AOSP native service involves configuring libbinder runtime behavior. This ensures robust concurrent state handling and allows clients to detect when a bound service process terminates unexpectedly.
Yes, you can review existing platform services and vendor native services for concurrency risks. The approach validates manual Bn/Bp interfaces, checks meta-interface macros, and ensures safe concurrent state handling within your Binder IPC code.
Native Binder service transaction delegation fails when delegated unknown transactions are not properly routed. You must ensure your onTransact implementation correctly delegates unknown transactions and validates interface tokens to prevent dispatch errors.
Yes, ServiceManager registration is required to expose a vendor native service via IPC. After defining your Bn/Bp interfaces and setting up the thread pool, you must register the service so clients can discover and connect to it.
Binh230199Define, review, and debug Android AIDL interface files for cross-process IPC.
jonaschenAlign Android HAL binder domains, VNDK boundaries, and service registration to verified AIDL definitions.
chendongqiDesign and evaluate Android system architectures with HAL integration and SELinux policy modeling.
yash-gargGenerate Dart FFI bindings from native headers using ffigen and verify with Dart analysis.
