No thanks, I’d rather use a Google Pixel with GrapheneOS

Image transcription:

buy privacy-first community driven phone look inside closed source OS with no recovery image and outdated dependencies

  • macros@feddit.org
    link
    fedilink
    arrow-up
    154
    arrow-down
    9
    ·
    edit-2
    2 days ago

    Uh even this short stab is quite wrong. Here notes from Jolla itself for Sailfish OS 5.2

    • As promised, users can unlock the Jolla Phone bootloader. A corresponding menu item can now be found at the System Settings / Developer tools
    • Users can do factory reset from the System Settings
    • Users can enter the recovery mode with the volume up key + power key combination
    • Flashable images and fastboot will be provided (coming soon)
    • The initial version of the Privacy Switch was implemented. The function is end user configurable and to start with, the users can control e.g. Bluetooth, WLAN, Location and AppSupport status with the switch. Further implementations are coming and the framework is available for community contributions.

    The base of Sailfish OS is a full blown Linux, way more open than Android (more options for the user, less secure than Graphene, which has that as main goal) you can easily install/compile Linux software on it.

    Close source components are used. Parts of the UI (Jolla is open sourcing more and more), libhybris to run closed source Android drivers, Android App Support.

    So yes its not as open source as debian, but offers more freedom to modify the OS than Graphene and gives you near full control.

    • Hishiryo@scribe.disroot.org
      link
      fedilink
      arrow-up
      6
      ·
      1 day ago

      I do prefer a Fairphone, a Librem Phone or a PinePhone with postmarketOS though. Install Niri or MauiShell and Waydroid to it and you have pretty much it.

      • macros@feddit.org
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        1 day ago

        Yes thats pretty much the closest you can get to fully open source today. I have a number of devices I use:

        • A Pixel 5 with Graphene because the modern world relies to much on Android Apps, also used as hotspot,
        • A Nokia N9 for reading and light browsing, occasional navigation
        • A Nokia N900 with Maemo Leste for secure administrative work.

        We also have Sailfish devices in the house

        • Hishiryo@scribe.disroot.org
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          24 hours ago

          Pixel 5 are pretty good, I’d really like to have one of these because they’re the nearest-to-mainline-Linux Android phones.

        • pwalker@discuss.tchncs.de
          link
          fedilink
          arrow-up
          5
          ·
          2 days ago

          another batch two here. Maybe the longer we wait the more polished the OS will be, so maybe worth the wait. Especially waiting for camera app/driver update. The front cam seems really fucked right now.

      • macros@feddit.org
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        2 days ago

        No, not at all. Just check the things claimed by @pewpew quickly with a search engine or an AI of your choice (Always check the sources it finds!) and you will see that the overwhleming majority is wrong and the rest is blown way out of proportion. See also my answer to his retort below.

    • Fmstrat@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      4
      ·
      1 day ago

      The base of Sailfish OS is a full blown Linux, way more open than Android

      Sorry, but no. AOSP and Graphene do not use any proprietary blobs. They are 100% open.

      By your own post, SailfishOS uses closed source components.

      • HereIAm@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        13 hours ago

        And AOSP does not make a complete system. There are still plenty of binary blobs in both for drivers to get a working phone.

      • macros@feddit.org
        link
        fedilink
        arrow-up
        15
        ·
        1 day ago

        So does Graphene.

        Both ship: Firmware, the HAL components (which are way more critical in my eyes as they have low level hardware access and could hide anything from the OS) Example for these are: The Camera Stack, the Audio Stack, under Graphene the Widevine DRM components.

        Sailfish can run without these, e.g. on the Pinephone. Graphene OS can’t Graphene additionally comes with an eSIM binary, which is disabled by default Sailfish comes with proprietary UI components, a choice the company made because of their limited manpower as it allowed them to provide features where currently no open source solution exists or existed at the time of implementation) examples are swipe gestures for the keyboard, MS Exchange support, Android App support. That not great, but far from a closed source system where everything is closed source. There exist many patches for UI components because they are partly open source.

        The OS ist still Linux, that is true. It is even LInux+GNU which Android is not. It is Linux with closed source components, thats true too.

        • Fmstrat@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          1 day ago

          Both ship: Firmware, the HAL components (which are way more critical in my eyes as they have low level hardware access and could hide anything from the OS)

          Aren’t firmware and HAL in hardware/devices in the source tree for graphene? Also the camera stack/etc isn’t Google’s, it’s Graphene’s.

          The Widevine comment is fair, but Sailfish needs to support DRM, too, so they’re in the same boat, there.

          • AlfredoJohn@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            19 hours ago

            So graphene is also not open source then by your metrics? So some of the ui is closed source while on an os where you can trace and verify what is going on but an android derivative where you cant track whats going on in the os as freely with more critical closed source portions of its hardware is supposedly more open to you?

            Aren’t firmware and HAL in hardware/devices in the source tree for graphene?

            So either you know its there because you care so much to have verified the source code or you are just getting defensive about something you literally arent verifying…

            • Fmstrat@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              19 hours ago

              What? Are you arguing without comprehending?

              And what makes you think it’s easier to trace what is happening in SailfishOS? Tracing isn’t hard in Android.

    • pewpew@feddit.itOP
      link
      fedilink
      arrow-up
      29
      arrow-down
      13
      ·
      2 days ago

      It may be a private phone, but you don’t really know whats going on under those proprietary blobs.

      Sailfish OS is the definition of proprietary software. You need to buy a subscription if you even want to install it on third party devices.

      It’s like Windows but it claims to be private and commnunity driven while not providing the source code to the entire OS. It’s a little misleading to me

      • M137@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        19 hours ago

        You are so wrong about many things that it seems like you have some personal anger towards it and just don’t care about having a fact based based opinion. It all reads like a fanboy of something else just blurting out shit they’ve heard without even trying to find out if it’s correct.

      • macros@feddit.org
        link
        fedilink
        arrow-up
        37
        arrow-down
        3
        ·
        edit-2
        2 days ago

        It may be a private phone, but you don’t really know whats going on under those proprietary blobs.

        Yes thats not good, but also a problem of many common Linux distributions. If you have any linux-firmware-* packages installed on your system, they also contain similar binary blobs for the firmware. E.g. Intel or Qualcom wireless cards. But you can utilize all tools up to strace under Sailfish OS, to see what those drivers are accessing and check that they don’t do anything bad. Under Graphene OS, you can not do this. (But its resonable to trust the very privacy focused developer that they have checked and tested this and isolated them as far as possible on the OS level)

        Sailfish OS is the definition of proprietary software. You need to buy a subscription if you even want to install it on third party devices.

        Again this is not correct. If what you claim is true, how comes that the OS is available on all these devices?. Sailfish OS is open Source at its core and easily ported to new devices. What you can do is pay for the licensed content on official devices. That enables automatic updates and proprietary software as the MS Exchange support and the Android App Support. Though for the later you can also install Waydroid because, you know, its Linux! Paying Jolla however gives access to a more comfortable solution and support development of the platform.

        It’s like Windows

        Um… no. Can you port Windows to a new device? No, its source is closed. Does Microsoft support people hacking their OS? No, Jolla has community meetings for that. Do you have full Access udner Windows? No. Does Sailfish send your data to a third party? No. Does Sailfish show you adds? No, Does it force you to use AI? No and so on and so forth.

        Please don’t hate on the one European company trying to do things right. Support them in making things better.