this post was submitted on 22 Aug 2023
118 points (97.6% liked)

Android

17682 readers
3 users here now

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

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
 

Project Mainline delivers key OS updates through Google Play β€” here's how it's changing

you are viewing a single comment's thread
view the rest of the comments
[–] atocci@kbin.social 28 points 1 year ago (2 children)

I'll never understand why typical android updates are tied to your carrier and reliant on them for distribution.

[–] crow@beehaw.org 6 points 1 year ago (1 children)
[–] atocci@kbin.social 3 points 1 year ago (2 children)

But where's the money in that? How does AT&T holding back a major update for months at a time help them make money? It makes me never want to buy a phone from them again more than anything.

[–] Cris_Color@lemm.ee 7 points 1 year ago

I think the point they're making is that updates don't help sell more phones, and selling new phones with contracts is how they make money

[–] crow@beehaw.org 6 points 1 year ago (1 children)

Carriers likely pay google under the table to implement it that way so they can hold out updates on people and make them buy new phones. They also likely want to make sure all their crap spyware they force on your phone is working the best it can on the latest version so they can get as much of your data as well. Sometimes that might mean holding off a security patch until they themselves have wormed their way around it.

Yes this is all hypothetical, but the money there is real.

That and also pay the manufacturers under the table to not support bootloader unlocking, ensuring that the phone is ewaste after you're done with it And forcing you to get a new one

[–] avidamoeba@lemmy.ca 3 points 1 year ago* (last edited 1 year ago)

It's a combination of historical, technical and liability reasons. Even though wireless is built on standards (GSM, etc) implementations by vendors don't always conform, have defects, or need additional configuration to make it work well on a particular network comprised from particular base equipment. Does Qualcomm test every one of their their modems with every firmware version on every base station from every vendor? Does MediaTek? They don't and so many issues only show up once you encounter those combinations at the carrier end. When a carrier sells a phone with service on their network, they want to be damn sure it works or they'll be getting a volume of angry calls or worse (think implications of failed 911 calls). In order to ensure that doesn't happen, carriers test every device and every firmware version for it on their network. A lot of vendor hardware/software defects are found precisely during this stage. That's because these days the software/firmware is just as important for the proper functioning of the device-network combination. Therefore carriers want to keep tight control over device/software/firmware combos and only sell what they've tested and certified as working correctly. Ultimately carriers hold the keys to their network and they can block any device/group of devices that might cause problems for the network, others subscribers or expose them to liability. This is why updates that can affect any of the above are gated by carriers. This used to be extraordinarily strict prior to 2010. We made specific device software versions for Verizon, AT&T, etc. Remember when every phone had a carrier logo on it? That's when that was. After 2010, manufacturers and software vendors gradually began decoupling the carrier-related pieces like modem firmware and services, telephony, emergency, etc from the higher level software like calculator apps and through.. arduous lobbying and discussions with carriers vendors proved to carriers that they don't need to vet every little thing that changes in a phone from one version to the next. And so gradually we had more and more things not having to pass carrier testing. That said, OS updates which change the aforementioned critical components are still gated by carrier testing and Google can't do shit to get past them. They have no leverage as they wouldn't be liable if something goes horribly wrong.

When I say carriers, think large North American carriers and large European ones. Verizon, AT&T, T-Mobile, etc. Small carriers that don't have much resources don't do as much testing and rely more on the diligence of the vendors on the phone and base station ends to have things work well. They also benefit from fixes of defects found during carrier testing conducted by the big ones.

Source: Am a software guy that used to work at BlackBerry during the BBOS, BB10 and Android days.