4 ms·

Only available on Pixel phones and a single Xiaomi phone.

dcow 5y ago
Got to start somewhere.
SubzeroCarnage 5y ago
Unlike GrapheneOS (which I recommend you use if you can) and CalyxOS, my project https://divestos.org https://divestos.org is tested working on 30+ devices.
- atatatat 5y ago
  Very cool! Few quips: Silence was last updated (on F-Droid) a year ago — is this project secure//being maintained? & Mozilla-cousin browser: you're going to lose the security clout these days unfortunately.
  - SubzeroCarnage 5y ago
    Silence is sadly no longer maintained, but it still seems to work for now. I will eventually replace it. Re Mozilla: I do state on my browser comparison page that Chromium browsers are more secure. Also the Bromite repository is included in F-Droid by default on DivestOS.
    - atatatat 5y ago
      Very cool! Thanks for stopping in here!
- atatatat 5y ago
  Props on bringing verified boot to those devices Lineage can//will not, and doesn't tell users clearly that they could have it with other options.
  - SubzeroCarnage 5y ago
    That is a limitation of Lineage only because they choose to cater to users who want root (which usually modifies /system) and to support flashing Google Apps.
    - summm 5y ago
      Why would having root itself rule out secure boot? It's just that they refuse to offer root themselves, and only as a result of that refusal one has to use system modifications to gain root. In a sense this is the opposite of your claim: they do explicitly not cater to root users.
      - SubzeroCarnage 5y ago
        Verified boot is only enforcing on -user builds. Lineage ships -userdebug builds. Furthermore Lineage's official root addon writes to /system. You can't have any additional changes to system or else verified boot won't boot. You can't have it both ways as it stands. That isn't to say they are incompatible, you can compile-in root support before the system hashes are generated and then you can have a locked bootloader with verified boot with root support. But you cannot make any additional changes to /system with that root power afterwards.
        zozbot234 5y ago
        > But you cannot make any additional changes to /system with that root power afterwards. Not a showstopper, as modern root solutions like Magisk support "systemless" root, via file system overlays.
        SubzeroCarnage 5y ago
        I am not sure how systemless root interacts with verified boot. I've never tried it myself.
        5y ago
cdesai 5y ago
We do want to support more devices, however not all of them meet our requirements https://calyxos.org/about/faq/device-support/#requirements-for-supporting-a-new-device https://calyxos.org/about/faq/device-support/#requirements-f... We're trying to find devices which do, and if not see if the requirements can be relaxed. The most important part that's missing from many phones is being able to relock the bootloader with a custom OS installed.
- Krasnol 5y ago
  It would help if you'd put the supported devices right up on the front page. It saves much time for most visitors and doesn't end up in frustration if people get them on the second step.
crudbug 5y ago
That is the irony. Only pixel hardware provides one step OEM unlocking in US. All other devices are carrier locked and have restrictive unlocking process. Samsung/Motorola/ etc. should release OEM unlocked devices not just carrier unlocked that can be purchased directly from their online stores. This will make adoption easy for these open Android projects.

dcow 5y ago

Got to start somewhere.

Unlike GrapheneOS (which I recommend you use if you can) and CalyxOS, my project https://divestos.org https://divestos.org is tested working on 30+ devices.

atatatat 5y ago
Very cool! Few quips: Silence was last updated (on F-Droid) a year ago — is this project secure//being maintained? & Mozilla-cousin browser: you're going to lose the security clout these days unfortunately.
- SubzeroCarnage 5y ago
  Silence is sadly no longer maintained, but it still seems to work for now. I will eventually replace it. Re Mozilla: I do state on my browser comparison page that Chromium browsers are more secure. Also the Bromite repository is included in F-Droid by default on DivestOS.
  - atatatat 5y ago
    Very cool! Thanks for stopping in here!
atatatat 5y ago
Props on bringing verified boot to those devices Lineage can//will not, and doesn't tell users clearly that they could have it with other options.
- SubzeroCarnage 5y ago
  That is a limitation of Lineage only because they choose to cater to users who want root (which usually modifies /system) and to support flashing Google Apps.
  - summm 5y ago
    Why would having root itself rule out secure boot? It's just that they refuse to offer root themselves, and only as a result of that refusal one has to use system modifications to gain root. In a sense this is the opposite of your claim: they do explicitly not cater to root users.
    - SubzeroCarnage 5y ago
      Verified boot is only enforcing on -user builds. Lineage ships -userdebug builds. Furthermore Lineage's official root addon writes to /system. You can't have any additional changes to system or else verified boot won't boot. You can't have it both ways as it stands. That isn't to say they are incompatible, you can compile-in root support before the system hashes are generated and then you can have a locked bootloader with verified boot with root support. But you cannot make any additional changes to /system with that root power afterwards.
      - zozbot234 5y ago
        > But you cannot make any additional changes to /system with that root power afterwards. Not a showstopper, as modern root solutions like Magisk support "systemless" root, via file system overlays.
        SubzeroCarnage 5y ago
        I am not sure how systemless root interacts with verified boot. I've never tried it myself.
        5y ago

cdesai 5y ago

We do want to support more devices, however not all of them meet our requirements https://calyxos.org/about/faq/device-support/#requirements-for-supporting-a-new-device https://calyxos.org/about/faq/device-support/#requirements-f... We're trying to find devices which do, and if not see if the requirements can be relaxed. The most important part that's missing from many phones is being able to relock the bootloader with a custom OS installed.

Krasnol 5y ago
It would help if you'd put the supported devices right up on the front page. It saves much time for most visitors and doesn't end up in frustration if people get them on the second step.

crudbug 5y ago

That is the irony. Only pixel hardware provides one step OEM unlocking in US. All other devices are carrier locked and have restrictive unlocking process. Samsung/Motorola/ etc. should release OEM unlocked devices not just carrier unlocked that can be purchased directly from their online stores. This will make adoption easy for these open Android projects.