Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'Summary
Google Messages is currently the primary RCS client available for Android. While microG provides compatibility with many Google Play Services APIs, Google Messages still cannot successfully activate RCS on devices using microG.
Users commonly encounter one of the following issues:
"RCS chats aren't available for this device."
An endless "Setting up..." state where phone number verification never completes.
Recent reports indicate that Google Messages no longer strictly relies on Play Integrity or device attestation for RCS activation. Devices running sandboxed Google Play Services (such as GrapheneOS) have successfully enabled RCS after applying specific permission changes, suggesting that the remaining obstacle is API compatibility rather than device certification.
Problem
Google Messages appears to depend on several Google Play Services components that microG may not fully implement or expose.
Possible missing components include:
Google authentication services
Device Check-In
Firebase Cloud Messaging registration
Google Identity APIs
Phenotype (Flags) API
Carrier Services integration
Modern Play Services registration APIs
Without complete compatibility, Google Messages is unable to finish the RCS provisioning process.
Proposed Solution
Improve microG compatibility so that Google Messages can successfully register and activate RCS on supported carriers.
Potential implementation areas include:
Complete implementation of the required Google Play Services APIs used during RCS provisioning.
Ensure proper authentication token generation and device registration.
Improve compatibility with Carrier Services.
Support the APIs required by recent versions of Google Messages.
Investigate Binder communication between Google Messages and official Google Play Services to identify missing services or incorrect responses.
Requirements
The solution should:
Work with current Google Messages releases.
Support locked bootloader devices.
Not require root, Magisk, LSPosed, or similar modifications.
Be compatible with recent Android versions whenever possible.
Expected Result
Users should be able to:
Install microG.
Install Google Messages.
Complete phone number verification.
Successfully enable RCS without using official Google Play Services.
Why This Matters
Although RCS is a GSMA standard intended to replace SMS, Google's implementation has become the de facto messaging platform on Android. Supporting Google Messages RCS in microG would significantly improve compatibility for users who choose privacy-focused or de-Googled Android distributions while still allowing them to communicate using the modern messaging standard.
With Apple now supporting RCS as well, interoperability has become increasingly important.
References
GrapheneOS discussions on sandboxed Google Play Services and RCS
Google Messages RCS provisioning behavior
microG compatibility documentation
2. Click on '....'
3. Scroll down to '....'
4. See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System
Android Version: [e.g. 10]
Custom ROM: [e.g. LineageOS 17.1]
Additional context
Add any other context about the problem here.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Google Messages is currently the primary RCS client available for Android. While microG provides compatibility with many Google Play Services APIs, Google Messages still cannot successfully activate RCS on devices using microG.
Users commonly encounter one of the following issues:
"RCS chats aren't available for this device."
An endless "Setting up..." state where phone number verification never completes.
Recent reports indicate that Google Messages no longer strictly relies on Play Integrity or device attestation for RCS activation. Devices running sandboxed Google Play Services (such as GrapheneOS) have successfully enabled RCS after applying specific permission changes, suggesting that the remaining obstacle is API compatibility rather than device certification.
Problem
Google Messages appears to depend on several Google Play Services components that microG may not fully implement or expose.
Possible missing components include:
Google authentication services
Device Check-In
Firebase Cloud Messaging registration
Google Identity APIs
Phenotype (Flags) API
Carrier Services integration
Modern Play Services registration APIs
Without complete compatibility, Google Messages is unable to finish the RCS provisioning process.
Proposed Solution
Improve microG compatibility so that Google Messages can successfully register and activate RCS on supported carriers.
Potential implementation areas include:
Complete implementation of the required Google Play Services APIs used during RCS provisioning.
Ensure proper authentication token generation and device registration.
Improve compatibility with Carrier Services.
Support the APIs required by recent versions of Google Messages.
Investigate Binder communication between Google Messages and official Google Play Services to identify missing services or incorrect responses.
Requirements
The solution should:
Work with current Google Messages releases.
Support locked bootloader devices.
Not require root, Magisk, LSPosed, or similar modifications.
Be compatible with recent Android versions whenever possible.
Expected Result
Users should be able to:
Install microG.
Install Google Messages.
Complete phone number verification.
Successfully enable RCS without using official Google Play Services.
Why This Matters
Although RCS is a GSMA standard intended to replace SMS, Google's implementation has become the de facto messaging platform on Android. Supporting Google Messages RCS in microG would significantly improve compatibility for users who choose privacy-focused or de-Googled Android distributions while still allowing them to communicate using the modern messaging standard.
With Apple now supporting RCS as well, interoperability has become increasingly important.
References
GrapheneOS discussions on sandboxed Google Play Services and RCS
Google Messages RCS provisioning behavior
microG compatibility documentation
2. Click on '....'
3. Scroll down to '....'
4. See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System
Android Version: [e.g. 10]
Custom ROM: [e.g. LineageOS 17.1]
Additional context
Add any other context about the problem here.