70
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jun 2023
70 points (100.0% liked)
Technology
37750 readers
291 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Corporate bullshit 101
No surprise from a company that announce to their employee they are fired by disabling their pass.
It is up to the device manufacturer. Google develops Android Open Source Project (AOSP) and the Google apps and services (Google Play Store for example). This feature (afaik) is in AOSP.
Google developed the version in AOSP, which is open source. Device manufacturers are then able to change the code as needed. If a device manufacturer uses base AOSP with (nearly) no changes, the fix Google made will be applied when the AOSP update goes through the manufacturers build pipeline and to the device (on Google Pixel phones for example). For manufacturers that have a lot of changes compared to AOSP (Xiaomi, Samsung, and many more), they might have to create their own fix that works on their own version of Android, which takes a lot longer.
One of the reasons people run "Custom ROMs" on their Android phone is to be responsible themselves for updates and fixes instead of the device manufacturer.
Yes, Google messed up and now abdicates all responsibility because of how fixes are pushed downstream to users.