I’m tired of collecting phones, and frankly I’m a little money strapped and kind of want to coast by on older phones for a while. But I’m wanting to de-google as much as possible.

Of the last few phones I’ve had, all are working well. Most have been able to be kept relatively up to date with LineageOS, and a couple have /e/os/ versions available for them (one official, one community)

  • Essential Phone (Community Build e/os/…not sure if still being updated or not though.)

  • Moto One Hyper (No e/os/ build. Sadly not a popular enough phone)

  • Moto One 5G Ace (Has an e/os/ build. Currently being used as a DIY game emulator on LineageOS)

  • Motorola Edge 2023 (Current Phone. No e/os/ build. It’s essentially a canadian variant of the Motorola Edge 40 Neo…which are the only two newest phones to use the Dimensity 7030 chip, making it incompatible with the regular Edge 40 or 40 Pro e/os/ builds.

I’m using /e/os/ on my Essential phone (though not daily driver) to get a feel for the software and the Murena app/account. I’m willing to give up my game emulator to put it on the newer phone if I like it (though it would suck to lose my FFVII and Chrono Trigger playthroughs)

Ideally my Edge 2023 would have a build. But I’m not going to expect a chipset used by only two phones total to garner that much development focus (and rightly so)

Anyone have more long term experience with /e/os/ and Graphene and tell me what Graphene has stronger?

Thanks

  • monnier@lemmy.ca
    1·
    5 days ago

    So AFAICT, in practice a locked bootloader makes no difference to the most common attacks I’ve seen on my devices and that of friends&family. Seems like a far cry from your original claim that “This means that the most essential feature for your safety, the metaphorical lock on the front door of your house, is left broken and loose.”

      • monnier@lemmy.ca
        1·
        10 hours ago

        I don’t think it’s a question of willingness to understand, but one of disagreement about the seriousness of the problem. Not to mention the implict idea that a “verified boot” is the only way to get that result. E.g. it’s very easy to get to a “safe factory state” without that kind of locking, for example with an immutable boot loader, as is typically present in many ARM SoCs (Allwinner, Rockchip, …). In that case you can revert to a safe state by downloading a known good OS image (using a trusted machine) and installing that image using only the immutable bootloader.