- cross-posted to:
- android@lemdro.id
- android@lemmy.world
- cross-posted to:
- android@lemdro.id
- android@lemmy.world
These are welcome changes but I hope they will address the elephant in the room sooner or later. They can’t go on depending on Pixels and hardware memory tagging. They need a roadmap for opening up the project to more phone models and they need it yesterday.
They’ve drummed up some publicity with the journalist debacle so it’s a good time to use that. But people who hear about Graphene will want to have some phone choices. “Get an old Pixel” is about to age like milk.
I don’t mind finding alternative apps for my gallery and etc but RCS would be amazing. And I’m not sure it’s feasible for a third party app right now so Graphene itself doing it will be awesome!
I agree but how does RCS actually work? My understanding is that it is particularly difficult to implement.
Yeah it probably will be pretty difficult. Google has a chokehold on it but I trust Graphene devs to find the minimum possible surface to j trace with Google while having functional RCS. And just not needing Google’s messenger app will be a huge plus for me.
The Mastodon thread linked in the most said they are planning to get an implementation that requires sandboxes Play Services first, then they should have a better idea of how to implement it solely with the carrier. It is an open standard in theory, just not in practice, since it is secretive.
The current messaging app doesn’t even have a search function. This is well overdue.


