AOSP Core Services Architect Required

@jagratip3

Hi, I’m interested in helping architect and implement these deep AOSP framework changes. I can work at the AMS/WMS/PMS framework layer with a security-first approach, translating product requirements into reviewable architecture, hooks, patches, and testable implementation plans. My approach would be to first map existing framework call flows and dependencies, then define minimal, maintainable extension points for System UI, Launcher, and permissions without introducing unnecessary framework coupling. I’ll document security/permission implications, lifecycle and concurrency risks, and CTS compatibility. For maintainability, I’ll structure changes as focused Gerrit CLs with clear commit boundaries, documentation, and a rebase strategy that minimizes conflicts across Android releases. I’ll use repo/Git, Gerrit, AOSP build tooling, clang tooling, logcat/dumpsys, emulator/reference-device testing, and CTS-focused validation. I can deliver the architecture document, PoC patches, build/setup instructions, and comprehensive test plan with clear rationale for every framework-level change.

@GobindSawarn

As an Android App developer with a specialized focus on the core AOSP services, I bring a unique mix of technical expertise and broad industry experience to your project. I am deeply familiar with the inner workings of Activity Manager Service, Window Manager Service and Package Manager Service – three key areas you seek assistance with in your project. During my six-year career, I have consistently delivered high-quality work that aligns with client expectations while maintaining clear communication throughout the process. To structure the AMS/WMS/PMS modifications efficiently, I would follow a systematic approach that begins with a thorough understanding of your project's objectives before exploring various design options. I'd then employ my extensive knowledge of Java, Android App and Mobile App Development to propose pragmatic yet innovative solutions that consider security implications. My familiarity using tools like repo, Gerrit and clang-tidy will facilitate smooth workflow and ease in reviewing codes.

@hxptechnologies

Hi there ?, I’ve carefully reviewed your project titled "AOSP Core Services Architect Required" and can confidently deliver a production-ready solution with clean UI and smooth performance. Let's discuss your specific requirements — I can start right away!

@VutomiM1

INTRO Recently helped a similar business solve the challenge of streamlining core Android services, turning a complex architecture into a more manageable and efficient system that aligned perfectly with their project goals. I can help you create a practical, professional solution built around what you actually need to achieve, not simply complete the project. MIDDLE I noticed you specifically mentioned the need for detailed architecture and clear documentation for modifying AMS, WMS, and PMS. That is important because the right approach here is not just about making changes, it’s about ensuring a seamless integration with existing systems and maintaining security standards. I bring experience in AOSP architecture, having successfully contributed to multiple upstream merges and commits. My background in using tools like repo, Gerrit, and clang-tidy has resulted in 75+ 5-star reviews on similar projects, ranking in the top 1% among 75 million users! OUTRO If you message me, I can share how I would approach this and where I see the biggest opportunity to solve the challenge effectively. Regards, VutomiM1

@eugabrielmaximo

Hello, I think the key challenge here is not simply modifying AMS, WMS, and PMS independently it is designing clean framework hooks so System UI, Launcher, and permission/security changes remain predictable across Android releases and CTS. I would structure the work around clear ownership boundaries between activity/task lifecycle, window policy, package/permission state, and the System UI/Launcher integration points. I’d first map the existing call paths and Binder interfaces, then identify the minimum framework changes required, with particular attention to permission enforcement, identity propagation, race conditions, and backward-compatible behavior. For implementation, I would * Produce an architecture document covering AMS/WMS/PMS interactions, affected System UI and Launcher flows, security implications, and alternative designs. * Develop incremental PoC patches that can be reviewed and rebased independently. * Use repo, Git, Gerrit, format-patch, Soong/Ninja, adb, dumpsys, logcat, CTS/VTS where applicable, and static analysis such as clang-tidy. * Validate lifecycle, windowing, package/permission flows and regression cases on an AOSP reference emulator/device. I can also provide a commit-by-commit implementation roadmap. One useful starting point would be the target Android release and the specific System UI/Launcher behavior you want to introduce.

@Wonitaf

Hi there, I totally get what you're looking for. With a solid background in AOSP and experience with refactoring core services like Activity Manager, Window Manager, and Package Manager, I'm confident I can help you translate your high-level vision into actionable patches and documentation. I noticed you want to ensure that new behavior in System UI and the Launcher integrates seamlessly while managing the Android permissions model. I can definitely structure the modifications to keep everything clean and professional and ensure that we don't break CTS in the process. I specialize in AOSP architecture and have used tools like repo and Gerrit extensively in my previous projects. My approach focuses on pragmatic solutions and clear documentation to guide implementation teams effectively. I’m committed to speedy communication and a fast turnaround. Let me know if you are available for a quick chat! Regards, Wonita