feat: implement RCS support with Constellation and Asterism services#3669
Open
waterWang wants to merge 1 commit into
Open
feat: implement RCS support with Constellation and Asterism services#3669waterWang wants to merge 1 commit into
waterWang wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What changed: Implemented the RCS (Rich Communication Services) support for microG by adding the Constellation and Asterism service modules. These services provide the phone number verification and consent management APIs that Google Messages requires for RCS functionality.
Why it is correct: The implementation follows the existing microG service patterns and provides the AIDL interfaces that Google Messages expects. The Constellation service handles phone number verification (including TS.43 EAP-AKA carrier entitlement), IID token generation, and PNV capabilities. The Asterism service handles user consent management for RCS.
Risk: Low — new modules added without modifying existing functionality. The services are only activated when Google Messages requests them.
Changes
New modules:
Build system:
Verification
Checklist
LLM Disclosure