Yes, AOSP and AOS are parts of Android Google open source project and AOSP is developing application like mobile and TV and some of automobile component but AOS is we are developing application only automobile purpose and whenever we have we go through any document AOSP development we go to documentation review we just check that documentation and we go to update community update we can we just checking our compatibility we that we check that our testing component like that is a visible that AOSP and AOS project that is a visible to our application or not that we use that compliance that compliance is equally a fit and requirement is fit in our eco Android ecosystem and as per our module our module architecture we use that framework library API integration we just used to version control system CICD system we integrating our hardware abstract layer to customize our component AOS so we just can system integration testing we check to our application compatibility like in instrument testing unit testing we automate our application in tools through unit test or instrument test and our pipeline like a devops devops thing and we check our application mostly in optimize our application that UI component CPU memory battery we can minimize and we consume we focus in our application performance and memory related power management thing battery how much that battery consume our application and that our that AOSP feature we can that different different as a vendor we can call vendor that first party vendor OEM based what their requirement we can flash that AOSP and customize as per our requirement and as per customize our information system we just focus focus on mostly in compatibility testing that is a fit of our compatibility testing and is our communication like hair layer and framework layer that communication is going is good and we focus on vehicle diagnostic the diagnostic going to right way that that thing we follow in our best practice in AOSP side and AOS side that is a we currently follow
