‹ BackHN Continuity

Thread

GrapheneOS has fixed the Android 17 QPR1 kernel performance regression

142 points · 102 comments · Cider9986

  1. mmooss · · focus · HN ↗

    [dead]

    1. Dezvous · · focus · HN ↗
      >Just zip it, be professional, focus on what you are doing and not on others.

      How do you propose they "focus on what [they're] doing and not on others" when their entire project is dependent on other's (Google's) work that directly impacts their own users? There's nothing about this blog post that is unprofessional. GrapheneOS released a patch for a rather severe performance bug, which is outside the scope of their normal work, so they provided context into why they made the decision to do so.

      1. andrewaylett · · focus · HN ↗
        Look to "HugOps" as inspiration: when someone else is having a bad day, offer them a hug rather than running them down.

        The article uses phrases like "completely broken", "awful", and "<delay> wouldn't be a surprise". Which might be true but it's not helping.

        1. microtonal · · focus · HN ↗
          We can hug the engineers that have to fix this while at the same time criticizing the process that led to this.

          Google has betas for QPRs and yet this was not caught. It makes you wonder if Google is dogfooding the devices themselves or at least the devices that are not the latest gen and have 16GB memory.

          The other issue is that it often takes weeks or months to fix show-stopping issues. Compare to e.g. Apple who rolled out a fix for Apple Watch 12/Ultra reboots or the iPhone 18 Pro Face ID issues within a week.

          There are seriously things wrong in their process if they don’t catch these bugs and/or fix them quickly. (Or the other possibility is that they are understaffed.)

          1. grapheneos · · focus · HN ↗
            Google caused many of these problems with mass layoffs, buyouts and ending remote work which drove away many of their best engineers. The hostility of Google's business side towards projects based on AOSP has also led to many additional issues for the Pixel OS which could have been avoided. If they hadn't made it nearly impossible to contribute and been so hostile towards many projects including GrapheneOS then they could have a lot of help with these issues and could get them fixed far easier. The Beta releases aren't released as open source and there's no way to contribute.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.