• 0 Posts
  • 154 Comments
Joined 2 years ago
Cake day: June 15th, 2023
  • GenderNeutralBro@lemmy.sdf.orgtoAndroid@lemmy.world•GrapheneOS is finally ready to break free from Pixels, and it may never look backEnglish
    22·
    7 days ago

    I’ll speculate.

    My money’s on Asus. Asus is a bit more mainstream than Nothing but still enough of an underdog that I think they should see the value in a partnership. They already target an enthusiast niche with the ROG line.

    The Nothing Phone 3 uses an SD 8s Gen 4, which is not Qualcomm’s “flagship” SOC, and it would be stretching the definition of “major” OEM, but who knows? This seems the most likely after Asus.

    Moto’s only flagship Snapdragon phone is the Razr Ultra, which I guess is possible. It’d be weird, but hey, I’d buy one.

    OnePlus has been moving in the opposite direction for years now, locking things down more and more. I think they’re too big for their britches at this point.

    Sony’s flagships are crazy expensive, well beyond the price of Pixels. They also don’t cover the US market, though I’m not sure how important that is to the Graphene devs.

    HMD doesn’t make any phones with flagship SOCs. I think their best is the Skyline, with a 7s gen 2, Qualcomm’s fourth-tier SOC line (the “s” stands for shitty).

    Fairphone doesn’t use flagship Snapdragons and GOS has had some pretty nasty things to say about them in the past.

    Samsung is a pipe dream. They’d have no motivation. The entire GOS user base would be a rounding error to them.

    On a global scale, Xiaomi would be a huge get. Not sure I see any of the Chinese OEMs focusing on this though.

    Lenovo and Blackberry…might still exist? I think?

  • GenderNeutralBro@lemmy.sdf.orgtoLinux@lemmy.ml•[Solved] Ran fdupes -rd /home without -A, now flatpak is dead, any help?English
    6·
    16 days ago

    Thanks for posting the solution!

    If you happen to be using a BTRFS or XFS file system, you might want to try duperemove. It will help you reclaim usable disk space without deleting any files, by using those filesystems’ built-in support for data deduplication and copy-on-write. In other words, it will make duplicate files point to the same data on disk, but still work as individual files. Files will appear and function exactly the same, and editing one copy will not change another (unlike with hard links, for example). That way it won’t interfere with cases like Flatpak or Python virtual environments where you really need multiple copies of the same files.

  • GenderNeutralBro@lemmy.sdf.orgtoAndroid@lemdro.id•Snapdragon 8 Elite Gen 5 benchmarks: Just how badly does it beat its rivals?English
    4·
    26 days ago

    Still good if you want ROM support or are willing to wait a few months to pick one up for dirt cheap.

    GrapheneOS only supports pixels, and LineageOS only officially supports a few more models. If you filter the official LineageOS devices list to 2024/2025 models, you’ll see Pixels, Moto G 5G, and OnePlus 12R. That’s it. Options are similarly limited for Calyx, e/OS, and others. So with most other recent phones, you’re stuck with all the stock bloat and spyware, or unofficial community builds.

    Also, they’re dirt cheap in practice in the US. MSRP is a joke. For most of the year, you could get an unlocked, brand new Pixel 9 for less than the MSRP of the low-end 9a. If memory serves, it dropped under $400 at times.

    Aside from that, they kind of suck. I wouldn’t even compare them to high-end phones. They are mid-range phones masquerading as high-end. Credit to Google’s marketing department, I guess.

  • GenderNeutralBro@lemmy.sdf.orgtoLinux@lemmy.ml•Which of the 3 standard compression algorithms on Unix (gz, xz, or bz2) is best for long term data archival at their highest compression?English
    8·
    28 days ago

    Generally speaking, xz provides higher compression.

    None of these are well optimized for images. Depending on your image format, you might be better off leaving those files alone or converting them to a more modern format like JPEG-XL. Supposedly JPEG-XL can further compress JPEG files with no additional loss of quality, and it also has an efficient lossless mode.

    Do any of them have the ability to recover from a bit flip or at the very least detect with certainty whether the data is corrupted or not when extracting?

    As far as I know, no common compression algorithms feature built-in error correction, nor does tar. This is something you can do with external tools, instead.

    For validation, you can save a hash of the compressed output. md5 is a bad hashing algorithm but it’s still generally fine (and widely used) for this purpose. SHA256 is much more robust if you are worried about dedicated malicious forgery, and not just random corruption.

    Usually, you’d just put hash files alongside your archive files with appropriate names, so you can manually check them later. Note that this will not provide you with information about which parts of the archive are corrupt, only that it is corrupt.

    For error correction, consider par2. Same idea: you give it a file, and it creates a secondary file that can be used alongside the original for error correction later.

    I also want the files to be extractable with just the Linux/Unix standard binutils

    That is a key advantage of this method. Adding a hash file or par file does not change the basic archive, so you don’t need any special tools to work with it.

    You should also consider your file system and media. Some file systems offer built-in error correction. And some media types are less susceptible to corruption than others, either due to physical durability or to baked-in error correction.