• zecg@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    15 days ago

    Why not just install Graphene? That’s the only reason I’d spring for Google’s hardware.

    • witten@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      15 days ago

      How would that help in this case? If the Google battery-nerfing update is legitimate, then it’s preventing Pixel 4a phones from catching on fire or whatever.

      To be clear, I’m not trying to justify Google’s handling of this situation created by their own defective hardware fuckup.

      Sent from my Pixel 4a.

      • Vanilla_PuddinFudge@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        People are literally playing with fire.

        On one hand, it could be more Google bullshit like their RCS requirements that lock out custom Roms just so users will buy a new phone or play their cat and mouse game with Magisk modules.

        On the other, it could legitimately be a problem with the battery and it needs to be taken seriously.

        If those are my options, and there’s no way to know the real truth, I’d swap to a different phone just to be on the safe side.

        • witten@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          2 days ago

          Totally, but why couldn’t Google just be straight with people on this? All the corporate speak and hedging just serves to fuel speculation—and doesn’t instill a lot of confidence in them or their products.