[GH-ISSUE #1027] feature request: support Rich Communication Services (RCS) #821

New issue

Open

opened 2026-02-26 01:32:00 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 01:32:00 +03:00

Owner

Originally created by @kurahaupo on GitHub (Jul 8, 2020).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1027

Originally assigned to: @jberkel, @kurahaupo on GitHub.

This feature-request ticket consolidates numerous requests to add support for "Rich Communication Services" (aka "RCS", "Advanced Messaging", or "AM").

The heart of the issue is that there is no public API for accessing (sending, receiving, storing, or retrieving) RCS messages.

The Google API for retrieving SMS & MMS messages from a SIM does not handle RCS messaging at all, not even to give an indication that they exist, so it hasn't been feasible to implement RCS support in 3rd-party apps such as SMS Backup+.

Google added an entirely new API for RCS, but the new API was still "OEM only" as of July 2019 with the Android Q release, or even October 2019 according to Google Support. (Reading between the lines, that was mostly due to intransigence by device vendors, rather than by Google.)

Google now offer an RCS gateway service as a paid service to businesses, but it's still not clear when or whether there will be an on-device API.

And to complicate matters further, RCS service has only been deployed in limited cellular markets, and without having some means of testing it's going to be nigh on impossible to write the new code required to implement this feature.

Originally created by @kurahaupo on GitHub (Jul 8, 2020). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1027 Originally assigned to: @jberkel, @kurahaupo on GitHub. This feature-request ticket consolidates numerous requests to add support for "Rich Communication Services" (aka "RCS", "Advanced Messaging", or "AM"). The heart of the issue is that there is **no public API** for accessing (sending, receiving, storing, or retrieving) RCS messages. The Google API for retrieving SMS & MMS messages from a SIM does not handle RCS messaging at all, not even to give an indication that they exist, so it hasn't been feasible to implement RCS support in 3rd-party apps such as _SMS Backup+_. Google added an entirely new API for RCS, but the new API was _still_ "OEM only" as of [July 2019 with the Android Q release](https://www.androidpolice.com/2019/07/30/google-rcs-third-party-messenger-apps/), or even [October 2019 according to Google Support](https://support.google.com/messages/thread/22367378?hl=en). (Reading between the lines, that was mostly due to intransigence by device vendors, rather than by Google.) Google now offer [an RCS gateway service](https://developers.google.com/business-communications/rcs-business-messaging) as a paid service to businesses, but it's still not clear when or whether there will be an on-device API. And to complicate matters further, RCS service has only been deployed in limited cellular markets, and without having some means of testing it's going to be nigh on impossible to write the new code required to implement this feature.

kerem added the

feature-request

AM+RCS

FAQ

labels

2026-02-26 01:32:00 +03:00

kerem commented

2026-02-26 01:32:00 +03:00

Author

Owner

@kurahaupo commented on GitHub (Jul 8, 2020):

Update 1: there's a good background explanation in this Reddit thread.

Update 2: a public RCS API was still non-existent as of March 2020.

(Side note: there's now a new MmsManager API)

@kurahaupo commented on GitHub (Jul 8, 2020): Update 1: there's a good background explanation in this [Reddit thread](https://www.reddit.com/r/UniversalProfile/comments/dysikj/android_11_rcs_api/). Update 2: a public RCS API was still non-existent [as of March 2020](https://www.reddit.com/r/UniversalProfile/comments/fktq5q/android_11r_developer_preview_2_today_still_no/). (Side note: there's now a new `MmsManager` API)