this post was submitted on 15 Dec 2025
133 points (97.8% liked)

Games

22701 readers
235 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 2 years ago
MODERATORS
nanoUFO@sh.itjust.works
133
Yep, Xbox Is Bleeding Out (gizmodo.com)
submitted 3 weeks ago by hypertruck@feddit.org to c/games@sh.itjust.works
49 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Moltz@lemmy.ml 6 points 3 weeks ago (4 children)

Neglected Pixels? Lol, truth is they were always poorly made midrange phones sold at high end prices. Google has never made good hardware, not even accidentally.

[–] baggachipz@sh.itjust.works 6 points 3 weeks ago (1 children)

Don’t worry, they’ll kill off and abandon the pixel line soon enough. Remember Nexus? Pepperidge Farm remembers.

[–] specialseaweed@sh.itjust.works 4 points 3 weeks ago

Nexus line had some real quality mid range phones at great prices.

[–] Rekorse@sh.itjust.works 4 points 3 weeks ago

Literally never heard this opinion before. Why are they bad?

[–] steeznson@lemmy.world 3 points 3 weeks ago

My pixel 1 phone was fine. Went back to Samsung after that though.

[–] fruitycoder@sh.itjust.works 1 points 3 weeks ago

They are basically the exclusive target for GrapheneOS for their feature set:

Non-exhaustive list of requirements for future devices, which are standards met or exceeded by current Pixel devices:

    Support for using alternate operating systems including full hardware security functionality
    Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)
    At least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tablets
    Device support code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they're released)
    Linux 6.1, 6.6 or 6.12 Generic Kernel Image (GKI) support
    Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM to match Pixels but another usable implementation may be acceptable)
    Hardware memory tagging (ARM MTE or equivalent)
    Hardware-based coarse grained Control Flow Integrity (CFI) for baseline coverage where type-based CFI isn't used or can't be deployed (BTI/PAC, CET IBT or equivalent)
    PXN, SMEP or equivalent
    PAN, SMAP or equivalent
    Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode / decode, image processor and other components
    Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
    Verified boot with rollback protection for firmware
    Verified boot with rollback protection for the OS (Android Verified Boot)
    Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
    StrongBox keystore provided by secure element
    Hardware key attestation support for the StrongBox keystore
    Attest key support for hardware key attestation to provide pinning support
    Weaver disk encryption key derivation throttling provided by secure element
    Insider attack resistance for updates to the secure element (Owner user authentication required before updates are accepted)
    Inline disk encryption acceleration with wrapped key support
    64-bit-only device support code
    Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
    Support for disabling USB data and also USB as a whole at a hardware level in the USB controller
    Reset attack mitigation for firmware-based boot modes such as fastboot mode zeroing memory left over from the OS and delaying opening up attack surface such as USB functionality until that's completed
    Debugging features such as JTAG or serial debugging must be inaccessible while the device is locked

From https://grapheneos.org/faq#device-support