Excellent! Since Signal removed SMS support there’s no trusted app supporting old SMS and encrypted messaging on one UI
SMS is not to be trusted because it is plain text and full of vulnerabilities.
I know. But I still need it whether I want it or not.
I have a limited data plan, so the only way I can communicate when I’m not on WiFi is by good ol’ fashioned text and call.
If you’re only sending text messages (no voice memos, stickers, photos or videos), you’re data plan should never be an issue when using Signal.
Data plan: if you use 1MiB by accident (even if it’s your phone doing stuff by itself when “mobile data” is set to “off”), you have to pay for an entire 2GiB “emergency” pack.
Oh you’re using a prepaid SIM?
however SMS doesn’t need a data connection, just a mobile signal, so as an emergency backup type of communication it’s great
That old behavior of Signal confused what was encrypted and what isn’t.
It really didn’t. Blue messages encrypted, green not encrypted. There was nothing confusing there
I agree, it was a huge bummer that they removed it. Their reasoning didn’t quite make sense for me.
I think a huge selling point was that it wasn’t one more app to message with, you could just replace your SMS app and if your contacts also had Signal, your messages would be encrypted. Very simple proposition.
I hope it’s functionally installable on other versions of android
I read installable and instable, I was like 🫠
I hope it can finally bring this piece of shit messaging protocol to Linux phones so my friends and family know when I read a message
You can always use Waydroid
If you phone is X:
https://github.com/1999AZZAR/use-waydroid-on-x11#installing-a-nested-wayland-compositor
The waydroid devs said not to use way droid for anything security related. This is bad advice.
I’m not seeing that anywhere, got a link?
you do realise that rcs only works on unrooted stock google-certified android with a locked bootloader? that’t the whole reason grapheneos is making their own FOSS implementation
rcs only works on unrooted stock google-certified android with a locked bootloader
Uh no? It literally works on GrapheneOS. https://grapheneos.org/usage#rcs
I think you’re confusing this with Google Pay, which only works on Google-certified systems.
Just move them to signal :)
i can barely get them to move off of telegram 🥀️
My immediate family is on signal, and has been for a while, my parents and my sibling are now on signal which is nice!
I have a few others I communicate with often I wish I could get them over because I hate using sms, even rcs.
Everything they make is open source, so even if they don’t officially support it, someone else will probably fork it and upload it somewhere.
I’m sure it will install, but if it needs some system level thing it won’t actually work. It depends how they implement it.
Nah, it would be insecure (still more secure than defaults and way too secure for most users)
I like how the one comment on that article is a guy baselessly saying that RCS is an open standard.
Open standard doesn’t mean implementations are wide open to use.
It’s open as BGP. Public documentation, nobody will connect to you if you’re a nobody.
A quick search shows that it is technically true, though…?
Good. Everything Google touches needs to be forked.
Fork Google
We keep trying, but the courts are ok with monopolies.
They suddenly care about monopolies whenever a major competitor threatens to shift the balance of the market by providing alternatives…
fork it right out the ass
Go fork yourself
Goggle!
Lougle! If you get that reference lol
yooo! while i wait for mobile linux to be realistic for my device this is a win
Hopefully this work is able to be used to help further that as well
This project seems to be promising for providing a true mobile Linux experience: https://www.youtube.com/watch?v=otMoX0-PYp8
Wow. I had not heard of this device until now! Seems to have a passionate team behind it. I will definitely be watching this one. Thanks for sharing!
will it be usable on LineageOS? could it help with RCS support on linux?
I’ve had my GV number as my primary for ~16 years. I’ve been on grapheneos for about a year now. Maybe I should actually pull the trigger and migrate my number to my provider and finally get RCS. All the better if GrapheneOS provides native support.
I’m in this same boat… FOMO is hitting me hard.
I think GV is the heaviest anchor holding me to Google right now… :-\
Yep, I always laugh when I think that Google managed to successfully bully Apple into supporting RCS, yet Googles own service, Google Voice, doesn’t!
I’m not sure you’d have to? You should be able to just download the app and register your # and they’ll just start coming.
Honestly the best news I’ve seen in a while. It was RCS that drove me back to stock android. I’ll be switching back to Graphene as soon as this lands.
Patiently waiting for supported devices expansion and no i don’t want them to rush, i just don’t want to buy a new phone to be free of Google.
They’re working with Motorola to make a device
It’s supposed to be out next year but only the highest end devices will be supported because GrapheneOS requires certain security features in the firmware and hardware that Pixel 11, the lower end Motorola devices, and the other brands don’t/won’t have.
Seems like Pixel 11 has the hardware but they turned the Arm Memory Tagging Extension (MTE) off in firmware for ‘performance’ reasons. gOS has been able to turn it back on, but the jury’s still out on whether they’ll support it as I understand it.
Buying a Google phone in order to get rid of Google seems sort of counterproductive, doesn’t it?
Yes
Exactly why i would like to have on the phone i have now.
only if you can’t handle nuance
Pixel 4a is great and less than $100
I bought a second hand pixel 8 pro.
I get the vibe there’s not much intention to expand compatibility.
They require certain features that most phones don’t have in order to be willing to support them. They want phones with GrapheneOS to be impossible to break into even by sophisticated methods such as Cellbrite so it defeats the purpose if it can be circumvented by methods that don’t involve the OS.
Wait, is my GrapheneOS phone unlikely to be hackable by Cellbrite? That’s kind of amazing, I had no idea.
My current daily driver is an HMD Skyline and it’s been great thus far and repairability is good but it isn’t listed anywhere as being supported by alternative OSs.
The skyline has a locked bootloader that can’'t be unlocked by users.
Only phones that can have the bootloader relocked by Graphene will be supported. New Motorola phones are coming but they will be expensive. Get a Pixel (not 11).
Yeah but can you really trust pixels? Google hardware, ewww. I would rather pay more for proper hardware
Google put out a surprising amount of documentation that allowed graphene to build everything they needed from the ground up. It basically wasn’t possible to do anything as secure and independent of Google software on any other model.
Ironically, the phone Google makes is the only option right now to get fully away from Google. Motorola is working with graphene to release a model that meets the main criteria, but it’s not out yet.
That’s just one of the things required for graphene, there are a lot of hardware security features that are also required. Only Pixels (not Pixel 11) have these so far, but the Motorola phones will change that of course.
As of now, for clarification, Pixels 6-10 series, Tablet and Fold are supported by GrapheneOS. The new Motorola phones releasing next year will also support GrapheneOS.
For clarification, only some Motorola phones, likely expensive flagship models, for now.
For those who got too excited by the title: read the original messages from the GrapheneOS. RCS de-facto is not an open technology, there’s a massive amount of work and multiple steps are needed to get anywhere near the proper independent implementation. It’s gonna be amazing if the GrapheneOS team pulls it off, but don’t get too excited about the release dates and its availability for other systems (e.g. Linux).
To be honest, I’d rather they use the effort elsewhere (as a very happy gOS user). The number of people on gOS who wouldn’t prefer Signal (without phone number rego) / Threema etc. is probably vanishingly small, but that takes going up against the incumbents with heavy resistance.
There’s only so many irons you can keep in the fire. That said, gOS devs (sans drama) are freaking awesome, and seems to keep growing in number, if they can pull it off it will be a true coup.
That’s true on one hand, but on the other there are also family and friends with who we still want/need to communicate via the “normies” protocols, and it’s better to do it without explicit spyware on your phone (aka Play Services or Whatsapp). So yeah, it’s an absolutely ungrateful work what they’re doing, but huge thanks to them for that.
This would be great. Definitely one of the few missing features.
Is there a reason we can’t just all use Quik across the de-googled OSes? Vendor specific solutions only further the closed ecosystem problem.
QUIK handles bare SMS.
Oh shit. So, grapheneOS is reinventing the wheel, when we have one? Interesting.
We don’t.
Dude, go read a book or something.
While that is a good SMS app (in fact, it’s the one I’m currently using), it does not support RKS.
I don’t see any mention that Quik works with RCS. Am I mistaken about this?
It does work with both iPhone and Android users from my testing. I ended up putting it on when I got tired of getting “person reacted <emoji> to <full quote of what I wrote>”.
Odd it isn’t explicitly called out.
The parsed and properly displayed reactions are a QUIK feature, but it does not mean RCS is being used. You can try to install e.g. Fossify Messages and you will see the “A reacted to B” messages again.
Also, this reaction parsing does not work for all languages.
Meh, RCS is too little, too late, and archaic in design.
We moved away from hardware-based network identifiers in the 1980’s, and RCS requires a unique hardware ID. It’s fucking backwards.
I will never use the garbage that is RCS - it’s already dead, just needs to be buried.
You say that until you cant even text your family or friends because every messaging application requires RCS. In the US, almost everyone is using RCS or we are using Windows with Microsoft Teams because of work. We dont use WhatsApp, Signal, Telegram, etc, unless its about traveling out of the country. Apple and Google really want SMS and MMS to kick the bucket but if GOS can pull this through, Im 100% for it.
The US doesn’t matter.
Besides, almost everyone in the US has WhatsApp for their Latino friends. And if they manage not to have Latino friends, they’re almost in certainly a racist pos
What a terrible comment
What the hell does having Latino friends have anything to do with what type of messaging services they use? Your completely missing the point or your just trying to start drama.
Because >99% of people in Latin America has WhatsApp. And their family too. And their friends too.
As a basic sms user, is RCS the reason my conversations now sometimes get flooded with messages like, “so-and-so loved this”?
If you’re on Android, the Textra app handles most of the emojis on messages without needing RCS. Sadly it still doesn’t work with reactions to images yet.
Looks like scamware, only available on Play Store, and it doesn’t look like it’s open-source. I wouldn’t go near that.
Why? You aren’t confortable with a random guy developing an app having access to your conversations or to your 2FA codes from your bank?
TBF I used it for a couple of years, tho I don’t anymore. It’s a good app. Didn’t get robbed or murdered.
Yeah, yeah, yeah, yeah! I’ve been busy, ok?!? Now if you could stop moving, I can’t aim!!
Textra was the go-to SMS app for quite a while in the enthusiast community. I don’t know what happened to it in the last few years though.
Textra claims Google is the reason they don’t have RCS support, something along the lines of locked out of the protocol?
RCS is not an open protocol. Never was. Otherwise every other SMS app would have already implemented it.
As a rule, I don’t use proprietary software unless I have to. So from my perspective it may as well not exist.
Quik, an open source SMS app on FDroid, handles this already without needing a specific OSes RCS.
Unless there is something fundamental thats wrong with Quik and its development, I dont see why one would be excited about another vendor specific solution. Quik works on any degoogled android, not just Graphene.
I might try Quik again at some point, but to be honest I don’t care enough about sms messaging apps to go beyond the default one usually. I think I remember I stopped using Quik because at least at the time it didn’t have link previews, which is a hell of a lot more convenient to me than emoji react buttons.
Yup





























