feat(rcs): implement Asterism and Constellation stubs to bypass RCS provisioning HTTP 400#3645
Open
Ahavahdev1 wants to merge 1 commit into
Open
feat(rcs): implement Asterism and Constellation stubs to bypass RCS provisioning HTTP 400#3645Ahavahdev1 wants to merge 1 commit into
Ahavahdev1 wants to merge 1 commit into
Conversation
…isioning HTTP 400 (microg#2994)
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
1 participant
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.
Fixes #2994
Description
This PR introduces the missing baseline components required for Google Messages to provision RCS successfully over microG.
AsterismServicestub to mock Jibe TOS consent (consent_status: 1).ConstellationServicestub to simulate successful GPNV (Google Phone Number Verification).DroidGuardChimeraServiceto bypass hardware attestation blocking checks specifically for the Google Messages package (com.google.android.apps.messaging).Motivation
To resolve the persistent "RCS chats aren't available for this device" and HTTP 400 errors during the ACS server provisioning phase by satisfying the undocumented IPC Binder requests.