A review by fenibook examines the North Korean “People’s Pixel,” a Google Pixel 8 Pro clone with weaker performance but generous memory, capable cameras, and a cooler-running MediaTek chip. Despite a spoofed 120Hz display claim, its eye-friendly dimming, strong telephoto macro performance, and unlocked bootloader make it an unusually competitive imitation.
  • 𝕸𝖔𝖘𝖘@infosec.pubEnglish
    2·
    14時間前

    unusually competitive imitation

    North Korean clone

    Yeah… nothing about this is competitive at this point. I wouldn’t trust any of my information with this device, unlocked bootloader or not.

    • SpookyBogMonster@lemmy.mlEnglish
      5·
      15時間前

      North Korea has its own intranet, essentially. About a decade ago, it got leaked on Reddit. Pretty mundane stuff. A news website, a recipe forum, etc.

      And I imagine they can access the Chinese internet fairly easily

  • Turret3857@infosec.pubEnglish
    22·
    2日前

    Despite a spoofed 120Hz display claim, its eye-friendly dimming, strong telephoto macro performance, and unlocked bootloader make it an unusually competitive imitation

    GET LINEAGE ON THIS SHIT ASAP!!!

    • Nebby@lemmy.blahaj.zoneEnglish
      2·
      1日前

      Was gonna say no graphene but id imagine it doesnt have the requirements for graphene. IMO lineage or stock aosp none of the other roms afaik (especially calyx and /e/) are worth installing due to lack of security updates.

      • Turret3857@infosec.pubEnglish
        2·
        17時間前

        Graphene is only leading in security updates if you choose to run their closed source builds. Otherwise the difference in security updates between open source Graphene, Calyx and Lineage (can’t speak to other Roms, have no experience with them) is usually days.

          • Turret3857@infosec.pubEnglish
            2·
            10時間前

            Google made changes to the AOSP release cycle last year. This change took AOSP from an open source project where every commit was visible, to more of a source available “here is a tar ball with squished commits so you can’t say we violated the license” once every 6 months sort of deal.

            Due to those changes, AOSP forks are faced with 2 options. Stay fully FOSS, reverse engineer each tarball drop for figuring out what each new commit was for and adapting that into your codebase, or the Graphene approach of partnering with an OEM (Motorola) to gain access to embargoed AOSP code, and maintaining 2 codebases (Graphene FOSS, and the Graphene embargoed version).

            Graphene is trying to maintain their security goals even if it means the end user can not completely compile the most secure version of their OS on their hardware.

            Lineage, Calyx, and Lineage forks l4mg, /e/OS and iodeOS are (whether by choice or by the fact collaborating with an OEM is a difficult pain in the ass) taking the first route.

            You can use GrapheneOS’s open source update channel, but you miss out on some security updates.

            Ive always felt every android fork has its place, just the same way every linux distro does. They all serve a different purpose.