Feasibility probe for Google-free carrier-native RCS support on /e/OS

/e/OS Smartphone Operating System
, , ,
1

I would like to request a focused feasibility step toward Google-free, carrier-native RCS support on /e/OS.
This is not a generic request to “just add RCS.” Existing related items include:

  • GitLab #7543: RCS doesn’t work
  • GitLab #8608: Group Messages are not working due to RCS
  • Several forum discussions about RCS, Google Messages, and failed group messages
    Those discussions show the user need, but the missing next step seems to be a technical feasibility probe.
    Requested feature:
    Add or support a small open-source privileged/system diagnostic component for /e/OS that can determine whether a device and carrier combination can support native RCS without Google Play Services or Google Jibe on-device.
    Initial target:
  • Fairphone 6
  • /e/OS official A15 build
  • T-Mobile US SIM
  • Carrier-native RCS/IMS path if available
    The probe should collect only non-secret diagnostics, such as:
  • IMS registration state
  • RCS feature availability
  • VoLTE/VoWiFi/SMS-over-IMS state where available
  • ISIM presence, without exposing secrets
  • P-CSCF discovery visibility
  • carrier config values relevant to IMS/RCS/UCE
  • whether Android exposes the needed privileged telephony/IMS APIs
  • whether vendor IMS services expose RCS/UCE/SIP delegate functionality
    The probe should not collect:
  • message contents
  • contacts
  • SIM secrets
  • authentication keys
  • private identifiers beyond what is strictly needed for local diagnosis
    Longer-term goal:
    If the feasibility probe shows the platform and carrier path are viable, the next step would be an open-source RCS client or service for /e/OS implementing GSMA RCS Universal Profile without relying on Google services. The eventual scope could include SIP/IMS integration, carrier provisioning, capability discovery, 1:1 and group chat, IMDN receipts, HTTP/MSRP file transfer, and MLS E2EE according to the GSMA RCS E2EE specification.
    Questions for the /e/OS team:
  1. Would /e/OS consider shipping or allowlisting a privileged open-source RCS feasibility probe?
  2. What requirements would apply for privileged permissions, platform signing, SELinux policy, reproducible builds, and privacy review?
  3. Can /e/OS expose enough Android IMS/RCS APIs for a system component to test this properly?
  4. Does the Fairphone 6 /e/OS build include the vendor IMS components needed for carrier IMS/RCS testing?
  5. If the probe is successful, would /e/OS consider a carrier-native, Google-free RCS system service as a future optional component?
    This would help determine whether RCS on /e/OS is blocked by Android APIs, device/vendor IMS support, carrier provisioning, Google/Jibe dependency, or a combination of those factors.
6 Likes