• Markaos@lemmy.oneOPEnglish
        2·
        1 year ago

        GrapheneOS only supports phones that have official Google support - the reasoning is that there’s little point trying to make a phone secure if the closed source drivers no longer get security updates and might be full of vulnerabilities.

        Not sure if they’re gonna support newer Android versions on 6/7 series once they go into the security-updates-only support window.

  • ki77erb@lemmy.worldEnglish
    9·
    1 year ago

    Just reporting in. Pixel 7 on T-Mobile and nothing yet. I tried that trick by turning off the SIM and checked over Wi-Fi too and nothing. I’ll get it when I get it, no big deal.

    • MrGG@lemmy.caEnglish
      11·
      1 year ago

      Yep, Pixel 4 and Pixel 4a will not be getting anymore updates.

      • kungfuratte@feddit.deEnglish
        2·
        1 year ago

        With the 4a it’s close to a scam. But what do you expect from Goo “Don’t be evil” gle?

        • MrGG@lemmy.caEnglish
          1·
          1 year ago

          I agree entirely with that sentiment. With this absurd abandonment of the 4a, the constant reports of owners not being able to dial 911, and my 4a randomly deciding one day to go into “emergency mode” and begin calling 911 on its own (while the phone was in my hand, I was just checking email, finger was nowhere near the power button to activate “emergency mode”), and the fact that the feature gap between Android and iOS is becoming narrower and narrower, I am seriously considering going back to iPhone 🙄

  • Anonymousllama@lemmy.worldEnglish
    6·
    1 year ago

    Be super keen if a bit more effort was put into “themed icons” where it uses a monochrome icon for each of the apps to force them to use your selected theme pallet. I’ve got no idea why there isn’t an option on the app level to override the default icon so that every app, regardless of how stubborn the developers are will be consistent.

    • TheGreenGolem@lemm.eeEnglish
      1·
      1 year ago

      There were traces in the code about the forced solution I saw a couple of months ago in an article. Apparently it didn’t make it into the final version which is a shame.

    • wile_e8@lemmy.worldEnglish
      10·
      1 year ago

      Hasn’t Android had a thing for a while where it gives update priority to people who manually check for updates? Like, my phone (7a) didn’t say an update was available, but then I clicked the “Check for update” button, and now it said Android 14 is available.

      So I don’t think anyone who really wants the update soon needs to sideload the OTA, just check for an update and you’ll probably get it.

        • redrum@lemmy.mlEnglish
          41·
          1 year ago

          I’ve just checked now (Pixel 7a, Catalonia) and it’s upgrading to 14

      • TheGreenGolem@lemm.eeEnglish
        2·
        1 year ago

        I always do that. I think I only waited once, it notified me like 4 days later. But when I go into the settings and manually search for the update, it always gives me the update as soon as it’s announced.

    • deadcream@kbin.social
      2·
      1 year ago

      I always got updates on the day one. Is this american thing (because americans buy phones modified by their carrier)?

      • GenderNeutralBro@lemmy.sdf.orgEnglish
        3·
        1 year ago

        I got my phone unlocked directly from Google, but I think it might still get held back based on my network. I’m not sure what the current state of this is. Historically at least, yes, it’s been a clusterfuck with US networks.

  • russjr08@outpost.zeuslink.netEnglish
    3·
    1 year ago

    Anyone by chance have the build number for the stable version?

    I’m going to assume I didn’t get silently updated from the beta to stable (especially since it’s only now getting late over here, and OTAs normally only auto-install for me around 2AM), but I’d like to check just to be sure.