You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This patch removes com.google.android.gms.rcs.START and com.google.android.gms.carrierauth.service.START from DummyService and routes them to dedicated services.
Why
For this issue, the current DummyService path always returns API_DISABLED, which blocks the RCS path immediately and gives no useful runtime signal for further implementation.
What changed
Added org.microg.gms.rcs.RcsService and org.microg.gms.rcs.CarrierAuthService.
Added a small binder shim that:
returns SUCCESS at service bind time,
records incoming transaction metadata (caller, code, flags, interface token),
can dump recent traces through binder dump transaction.
Updated AndroidManifest.xml:
registered both dedicated services,
removed the two corresponding actions from DummyService.
Scope
This is a focused infrastructure step. It does not claim full end-to-end RCS messaging support yet.
Did you run microG on a microG-enabled ROM on a physical phone with SIM card and tried to use RCS with Google Messages app before attempting to solve this issue? If so, what device, ROM and Android version did you use?
Did you run microG with this patchset applied on the same environment as in 1 to test that it passes the verification steps you outlined yourself?
Thanks for the clear questions. Direct answers first:
No, I have not yet validated this on a physical SIM-equipped device running a microG-capable custom ROM.
this patchset has not yet been end-to-end validated in that exact physical carrier environment.
The current scope of this PR is Phase 1: protocol-layer isolation and deterministic binder-contract analysis.
Phase 2 is now in progress: physical-device validation with SIM and carrier-backed conditions.
To keep this transparent and reproducible, I have added a concrete Phase 2 validation matrix and a structured reporting template to this branch under docs/juzi/.
I will update this PR with structured carrier-backed logs and results as soon as field telemetry is available. Please keep this PR active as the implementation hub while Phase 2 validation is running.
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
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
This patch removes
com.google.android.gms.rcs.STARTandcom.google.android.gms.carrierauth.service.STARTfromDummyServiceand routes them to dedicated services.Why
For this issue, the current
DummyServicepath always returnsAPI_DISABLED, which blocks the RCS path immediately and gives no useful runtime signal for further implementation.What changed
org.microg.gms.rcs.RcsServiceandorg.microg.gms.rcs.CarrierAuthService.SUCCESSat service bind time,AndroidManifest.xml:DummyService.Scope
This is a focused infrastructure step. It does not claim full end-to-end RCS messaging support yet.
Verification steps
adb logcat | grep -E "RcsApiService|CarrierAuthService"DummyServiceAPI_DISABLED.Rationale for this split