🚀 Bounty Alert!

💰 A bounty of $5000.00 has been created by unpluggederan on BountyHub for this issue.

🔗 Claim this bounty by submitting a pull request that solves this issue!

You can also increase the amount of the bounty if you think the issue is worth more.

Good luck, and happy coding! 💻

Nice, but I would wait a bit as Google Messages started showing users with custom ROMs that they aren't secured. Let's the leaked keybox thing run its course, then we can expect some alternatives solutions. If people with regular Gapps can't get RCS, then how are we gonna get it.

Best alternative would be open API or using Apple's RCS server, just like how people used mac mini for iMessage on Android.

But I can confirm(#2063) like Huawei users that RCS push messaging works with MicorG, the issue is Play Store certification that Companion fails at. Getting Strong or going naked with no spoofing doesn't help.

$5000???????

$5000???????

yes I'm the founder of bountyhub and I can confirm that this has been paid in advance

$5000???????

yes I'm the founder of bountyhub and I can confirm that this has been paid in advance

Fair play. Ive just downloaded google messaging cause of this bounty and can confirm getting the same error. Since Google will slow foss rcs apps down as much as possible, GMessaging seems the only option so I hope someone can get this going!

Hi @unpluggederan Implemented RCS service with SMS permissions and TelephonyManager integration to provide the service interface Google Messages expects, enabling RCS connectivity without root access.

Looking forward for the review

Hi @unpluggederan Implemented RCS service with SMS permissions and TelephonyManager integration to provide the service interface Google Messages expects, enabling RCS connectivity without root access.

Looking forward for the review

Did you test it on a real Device with GMS core instead of google play services?

Hi @unpluggederan Implemented RCS service with SMS permissions and TelephonyManager integration to provide the service interface Google Messages expects, enabling RCS connectivity without root access.

Looking forward for the review

Very nice! Can you confirm it was tested on a real device and you can send/receive RCS messages?

@omarsoufiane @unpluggederan

This PR adds an initial RCS service implementation. It's currently a basic stub that provides the service interface structure. I'm working on improving the implementation with proper AIDL interface, comprehensive logging, and testing utilities. Will update with improvements soon.

@omarsoufiane @unpluggederan

This PR adds an initial RCS service implementation. It's currently a basic stub that provides the service interface structure. I'm working on improving the implementation with proper AIDL interface, comprehensive logging, and testing utilities. Will update with improvements soon.

Hi and good job. But does your approach confirm that Carrier Services and Play Protect certification isnt necessary for RCS instant messaging?

What about the RCS rust APK that appeared some years ago? Will IMS have a role in this or can be use Apple or the Carriers RCS servers?

@omarsoufiane @unpluggederan
This PR adds an initial RCS service implementation. It's currently a basic stub that provides the service interface structure. I'm working on improving the implementation with proper AIDL interface, comprehensive logging, and testing utilities. Will update with improvements soon.

Hi and good job. But does your approach confirm that Carrier Services and Play Protect certification isnt necessary for RCS instant messaging?

What about the RCS rust APK that appeared some years ago? Will IMS have a role in this or can be use Apple or the Carriers RCS servers?

Your questions highlight that we need to move beyond the interface layer to actual RCS protocol implementation.
Our current implementation is a stub that provides the RCS service interface Google Messages expects, but we haven't tested if it works without Play Protect certification, Carrier Services, or actual RCS protocol implementation (SIP/MSRP/IMS) - we need real device testing to determine what Google Messages actually requires for RCS functionality. The RCS Rust APK you mentioned could be very valuable for understanding how to implement RCS without Google's infrastructure.

@omarsoufiane @unpluggederan
This PR adds an initial RCS service implementation. It's currently a basic stub that provides the service interface structure. I'm working on improving the implementation with proper AIDL interface, comprehensive logging, and testing utilities. Will update with improvements soon.

Hi and good job. But does your approach confirm that Carrier Services and Play Protect certification isnt necessary for RCS instant messaging?
What about the RCS rust APK that appeared some years ago? Will IMS have a role in this or can be use Apple or the Carriers RCS servers?

Your questions highlight that we need to move beyond the interface layer to actual RCS protocol implementation. Our current implementation is a stub that provides the RCS service interface Google Messages expects, but we haven't tested if it works without Play Protect certification, Carrier Services, or actual RCS protocol implementation (SIP/MSRP/IMS) - we need real device testing to determine what Google Messages actually requires for RCS functionality. The RCS Rust APK you mentioned could be very valuable for understanding how to implement RCS without Google's infrastructure.

Recent versions of Google Messages appear to work with Jibe across all carriers (though there may be exceptions). Using a stub seems to be a good direction, as Google Messages uses GMS in the provisioning process for something. However, the purpose of other methods related to actual RCS messaging (such as connectRcs, sendRcsMessage, etc.) remains unclear and may exist purely for legacy reasons while Google Messages handles everything else

Carrier Services may or may not be required, it doesn't matter as long as RCS works, I guess someone will figure it out eventually. Based on the thread in the original post, there is a strong indication that RCS is working without device attestation (either Device Integrity or Strong Integrity) which is very good.

I don't believe the RCS Rust implementation is relevant as there is no corresponding RCS server you can connect it to. Google clearly took over RCS and now controlling the gates. Apple are allowed because it's aligned with Google's strategy. Therefore, making RCS work on Google Message is probably the only feasible way to go.

@Dev-in-the-BM if you wanna go that route going with EU Digital Services Act would more promising, they are the reason big tech has to conform in eu. And then sometimes big tech outside of eu follows. Thats why we have usb c for iphones outside of eu and stuff like windows bloat having to be removable in eu.

I tried it and not that much was possible, aasked for a GDPR like reporting system:

Dear Mr,

Thank you for contacting the Europe Direct Contact Centre.

We have consulted the Directorate-General for Communications Networks, Content and Technology. Please find below the answer to your question.

"Thank you for reaching out to us with your concerns regarding Alphabet’s compliance with the Digital Markets Act (DMA), specifically in relation to its Android operating system and its messaging service. We greatly appreciate your input as it is valuable for our ongoing assessment of gatekeepers' compliance with the DMA obligations.

As of 7 March 2024, designated gatekeepers are required to ensure compliance with the DMA. In this regard, it is important to note that any measures proposed by Alphabet or other gatekeepers are currently under review and are not yet endorsed by the Commission.

The DMA mandates that gatekeepers submit a compliance report detailing their measures to meet the DMA's requirements. You can access a non-confidential summary of Alphabet’s compliance report here: https://digitalmarkets-act-cases.ec.europa.eu/reports/compliance-reports

We are actively monitoring Alphabet’s compliance through regular dialogue and by carefully evaluating their proposals as detailed in their report. As part of this process, we continue to welcome feedback from all stakeholders such as yours.

Should there be any non-compliance, the Commission will take all necessary actions to ensure adherence to the DMA. At this stage, we are unable to disclose specifics regarding the assessment of Alphabet’s compliance measures.

Nonetheless, your feedback is crucial, and we thank you once again for sharing your concerns.

We hope this information helps."

We hope you find this information useful. Please contact us again if you have other questions about the European Union, its activities or institutions.

Created on: 2024-07-18 15:20:20

Hi, I have a question about the Digital Markets Act that was presented by the European Union against gatekeepers. As listed on the official document, you name gatekeepers as Apple, Alphabet, Microsoft and etc. iMessage was mentioned as an instant messaging app that created a walled garden that made Apple users a little bit special in quotation marks.But I wonder if it's possible for the public to report about potential gatekeepers that break the DMA very publicly, it's like GDPR. For now, Apple has been losing its fight to protect its walled garden, for example USB-C, RCS and default apps. But I would like to look at Alphabet's policy to ban users that don't comply to their own standards of security. As you know, RCS or Rich Communication Services is a GSMA source available technology from 2007 that Google has been pushing to make everyone adopt, especially Apple. When the news about Apple supporting RCS add-on, Google being ironic and sarcastic started to act like Apple about RCS. Google adds a DRM on this chat feature that is meant to connect people, yet they close it off from modders of their phones that like to reuse their phone for future use. It's ridiculous as Google has been trying to make RCS a thing, yet other instant messaging apps like Signal, Telegram, Facebook Messenger just works without any kind of DRM or security add-on.TLDR Google who is banning rooted Android users from RCS is breaking the DMA. Is there anyway in the European Union to escalate this issue so it becomes more public for the politicians to actually demand Google to stop with this policy. RCS used to work without any demands or mods.

I guess we'd need a more "professional" message from a lawyer to get their attention, otherwise they'll just say whatever and hope you forget about it, as too little people complain about it for them to care. They probably dont even know and care what a rooted phone is and why rcs doesnt work for rooted/gappless phones.

@Dev-in-the-BM
if you want more people complaining/attention you could email Louis Rossmann. Complaining about big tech is one of the things he does for a living.
He has a page (fulu) for such bounties too.

I guess we'd need a more "professional" message from a lawyer to get their attention, otherwise they'll just say whatever and hope you forget about it, as too little people complain about it for them to care. They probably dont even know and care what a rooted phone is and why rcs doesnt work for rooted/gappless phones.

@Dev-in-the-BM
if you want more people complaining/attention you could email Louis Rossmann. Complaining about big tech is one of the things he does for a living.
He has a page (fulu) for such bounties too.

Louise Rossmann isn't ideal for DMA, he himself said he doesn't get how government works in Europe. He did invite the chairman of the right to repair committee to his old store but it didn't work. But FUTO does sponsor so why not make a big media thing, programmers defy Google walled garden project and if people compare RCS closed off as iMessage, then it could make carrier start servers or Google F off with its bad policy.

You could always contact your Parliamentarian, I did for the article 13 and 15 issue and I got the best response from the greens but the copyright law passed.

As this 150K dollarydoo bounty was only mentioned on XDA, Reddit and hackernews, making noise on other influencers can make a difference, it would still increase halfarsed AI commits. Sure, make a shoutout on LTT forums or any big Linux channel as this is a open source project. I mentioned one that RCS isn't open and I got a jerk showing the whitepaper that it's open to anyone to spend cash on server that can't even allow rooted users.

At this point I might start a bounty to touch up the UI of the LOS SMS app so it doesn't look like an Android 5.0 app. And add Signal support with SMS fallback to the default messaging app. Should be doable since the client is open source. Forks like Molly and Signal-Foss can still communicate and message the official build. Shouldn't be impossible using the client source as a reference.

Well it'd be better as a standalone app so that anyone can use it.

Well, the idea would be that you would have a secure messenger with SMS support built into the OS. It would also probably trickle down to all the other ROMs based on Lineage. And if you really just wanted the app you could just grab the APK. Like you currently can with their apps.

i don't know anything about the EU, I'm in the US.

But the fact is that right now Google has a monopoly on SMS messaging apps.

And duh, one person filing a complaint won't do anything.

But if enough of us complain to our governments, then maybe something will change.

Has anyone tried activating RCS when on the typical Google stack, upgrading to microG and seeing if RCS stays?

If so, is it possible to spoof the Android ID with the Android ID from the pre-microG activation to ensure continuity?

Starting work on this bounty now. Plan: reproduce on-device/emulator, identify the missing Play Services/microG component blocking RCS activation, implement with tests, then submit a PR with verification steps + demo evidence.

PR is up: #3234

This adds an initial RCS service implementation that:

• Allows Google Messages to bind to the RCS service
• Returns SUCCESS instead of API_DISABLED
• Includes logging for debugging

Test steps and verification included in the PR description. Happy to adjust based on feedback!

What does initial RCS do from a functional perspective? Is it the first step in getting full RCS?

What does initial RCS do from a functional perspective? Is it the first step in getting full RCS?

just another one ai slop

Has anyone tried activating RCS when on the typical Google stack, upgrading to microG and seeing if RCS stays?

If so, is it possible to spoof the Android ID with the Android ID from the pre-microG activation to ensure continuity?

I have used the LZPlay method on my Huawei device to install a pseudo-GMS and that allowed me to get RCS working even without device attestation.

So it seems like device attestation and the actual hardware is not what is keeping RCS as a gatekeeper.

When I installed microG, on the Huawei, I just get perma stuck on code 3000.

On my Google Pixel 6, which is rooted and does not have device integrity, I have RCS working. So it seems like device integrity isn't the blocker for RCS either.

Not sure exactly which factor it is, but hopefully this is useful for folks to help narrow down some paths.