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: [email protected]
💡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: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
📰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 [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
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
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
I wish Apple hadn't abandoned so many devices to rot on an old version for no good reason and then made their "One" service only work on the latest version as a blatant push to make people buy a new iDevice when the one they have would work just fine otherwise.
What he means is that typically after 5v years your iPhone won't get a system update. Lets say you're on iOS 10. Then next year Apple will tell all Devs that their apps may not longer support iOS 10 and below and all apps must use the ios 11 SDK.
Immediately all those folks stuck on iOS 10 cannot upgrade their apps and eventually they may stop functioning.
Whereas on the Android Play Store most apps require Android 5 and above. We're about to get Android 14. That means that an 11 year old Android can still install the very latest apps and games.
if you bind the web browser to the system update you can have as long updates on Android as iOS. Considering how old devices get a washed down version of "updates" and everyone claiming that's the holy grail of system support when google can push browser and security updates through Google Play Services. But keep repeating the only talking points you've ever known. You don't have to wait for a system update for a browser vulnerability like a caveman on Google supported Android. And if Apple has to release the patch for the same vulnerability, it has to push a "system update".
woo hoo, I had to use the Apple system update, Apple is the GOAT.
jeezus. 🤦♂️
Android by no means is perfect, is fragmented beyond control and Google is shit but these "consistent major updates" is apple fed bs. but you do you
Indeed this is a strength of Android and something most tech websites don't understand: on iOS to get a bug fix the entire OS needs to be updated. On Android this is not the case. Google can just push out the update via the Play Store.
Security updates have to come from the vendor, which is exactly the same on iOS. Apple has to update the entire OS to issue a security update. Whereas on Android the OEM can just send out a small security fix
In both cases the OEM is the weak point because they need time to push it out. Whether ios or Android.
One nice thing on Android is that you don't need to wait for an os update to add features to your device. You can just install an app.
For example, my LG V30 running Android 9 did not have gestures. So I downloaded an app called NG Gestures (needs an adb command for permission) and I had full gestures as if I were running Android 10 or higher.
Same thing with Dynamic Island. iPhone 14 user's have to buy the iPhone 15 is they want dynamic island whereas on Android you can just install one of the many dynamic island apps and instantly have that functionality,. And that typically includes phones running Android 5 and higher.
And they do, quickly, and at worst it takes me 5 more minutes to reboot my phone. Meanwhile on the Pixel 6 Pro, my phone maybe couldn't have called 911 for a week.
huh? my Pixel 6 update yesterday took 2 minutes
I was talking about iOS updates for things Apple doesn’t have de bundled from os updates. Since iOS updates are controlled by Apple and not carriers, it’s not similar to Android.
@phillaholic @ink if it takes a week for an update to get to you, you can blame your carrier for that. Google pushes updates very quickly to unlocked phones.
It’s a phone Google makes, with Software they make, a security vulnerability that Google discovered, which they alerted Google to 90 days before going public, a deadline they set, and I should blame AT&T for being responsible for this situation? Uh huh.
Meanwhile the carrier has nothing to do with anything iPhone related other than carrier settings.
@phillaholic carriers have to "approve" updates; Google, Samsung, or whoever is your vendor can't actually push an update because the carrier must sign it with their key. Was it Google's fault for the vuln? Yeah. Was it AT&T's fault for your update to take 1 week longer to roll out to you? Yeah.
You see that as the carrier waiting too long, I see it as Google having 90 days and waiting until the last minute. Regardless, Google allowing a third party to handle is a defective design.
This seems to be a US only issue. I've lived in several countries and my Android phone got updates direct from the OEM. Nothing at all to do with the carrier.
My old iPhone 7 (manufactured Sep 2016-2019) received a security update last month. Meanwhile, I bought a Samsung Android tablet new a few years ago only to find that the currently selling model wouldn't upgrade to the current very of Android.
I'm not an iPhone user, but they have better long-term updates than the vast majority of other vendors. Five years of support, I don't disagree with them wanting to push their newest device - they are a business and want to make money. Most features work except for things where there are hardware limitations.
I gave an example that has absolutely nothing to do with hardware limitations.
Your example didn't really make any sense, as you can use Apple One on iOS 14 or newer. So the oldest supported iPhone would be the 6s from 2015, which at the point iOS 14 came out was already 5 years old.
Tell that to my iPod Touch 7 on iOS 15 that refuses to then.
It claims to be unable to connect. Support is full of people with the same complaint, Apple doesn't care to fix it.
Yep
It is a tough decision…. On one hand you screw older devices; relegated them to second tier status and leave them abandoned and at risk
On the other hand you have a more consistent install base and better support and the ability to drop older systems and their bugs.
Someone gets screwed either way
Yeah, but not the same amount or scope of "someone", though.
You're saying you either make several hundred million devices into ewaste overnight versus "had to wait for a bit for the latest update to propagate".
Not the same scale of problem right there.