Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
What a weird dig coming from Google. Who is Google to complain about outdated messenger tech when they don't even built RCS into Android? The RCS Google wants you to use (the one with encryption) is part of their messenger, not part of the operating system itself. It's not even standardised.
The iMessage/SMS situation is stupid, but Google isn't exactly doing much better here.
Give google a break, its hard for them to keep track of what message backend is in which app. They have created and killed 5 messaging apps in the time I wrote out this comment, how can you expect them to know whats going on?
Google is taking the "monkeys with typewriters" approach to messaging apps, if they release enough of them they'll eventually stumble across a messaging app that's compatible with iMessage.
And then cancel it two weeks later.
I miss Hangouts π₯²
I miss shouting and whispering with Allo
Wheres my Google circle crowd at? Y'all move over to Wave?
I miss Messenger with XMPP
This kind of shit is why I've been working on replacing things, and leaving their ecosystem. There are 57 ways to do everything, and nothing ever works properly.
I am all about tweaking and changing things, or adopting something new, but that's all under the assumption that it works. One of the reason why people like iMessage is because they don't have to fuck with thirdparty apps, half of which can't even receive a text message without issues
I'm not using RCS until it is available with no vendor lock-in. Call me when third-party apps like Textra can use it, and I don't need to use Google's relay.
Google's relay is a requirement for carriers who don't host their own RCS infrastructure. Google set up a fallback server because outside of a few specific carriers, nobody bothered implementing RCS in their networks. In theory your carrier could set up a server and you wouldn't need Google at all.
In theory apps could build an RCS implementation and take control of your RCS account.
I trust my carrier even less than Google, which is saying something.
The nice thing about E2EE is that you don't need to trust your carrier. You could write your messages on a billboard along the highway if you can keep the message's secret key to yourself and the recipient(s).
Annoyingly, that does require someone to actually implement Google's RCS encryption protocol (which is really just Signal + MLS but over RCS) and publish the source code (and provide reproducible builds to prove nothing's been messed with).
When RCS first came out, my carrier provided their own app to use it lol
Canadian carriers did, but they since have started moving towards Google's RCS servers instead. Probably realized it wasn't worth hosting a server, and then maintaining it. I remember some carriers wouldn't update their servers, so not all RCS features would be available to them.
It should just be an API that any text messaging app can use on Android, with the ability to define your own relay if desired.