I am currently an IOS user, however, as the title suggests, I wish to switch to android. This is because I would prefer to use free software and not be locked into the apple ecosystem. That being said I am already locked into apple and would like to know how anyone else here has managed the switch.

I for one know I will face problems regarding group chats with friends and family on IOS, I will lose out on iCloud+ features, I will have to buy a replacement for my HomePod, I will need to replace apple home, etc.

How did anyone else here who has made such a switch replace or solve these issues?

  • Jumper775@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Loooking at the wiki for those doesn’t list modern devices, or even older ones like the pixel 4 through 7. The phone I was looking at buying was a pixel 7 pro as people here seemed to recommend the pixels. Will droidian or others run on this?

    As for operating system, manjaro is obv a no go. I also will avoid UBports as I don’t really like snaps or Ubuntu. This leaves droidian and I was looking at postmarketOS, but that doesn’t seem ready. Ideally as I’ve said phosh or gnome shell mobile distros would be best but I can’t find any that support modern devices that run these and I don’t really want to spin my own. Are there any you can think of or perhaps some privacy respecting androids that still let me use google apps I may need or stuff of the like?

    • Refurbished Refurbisher@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Droidian would be more to try out and less to use as a daily driver. It runs atop Halium, so it should work on most modern Android devices that support Treble. Hardware support is a bit hit or miss.

      I’d stick to Graphene OS for now.

      EDIT: Halium only supports up to Android 11 for now. You will have to wait for support for Android 13 for the Pixel 7 Pro.

      If you want to try Linux sooner, the OnePlus 6 can be gotten for relatively cheap nowadays.

      • Jumper775@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I think grapheneOS will probably be fine. There are however a few google apps I absolutely need for work, namely google docs and sheets. From what I could read on their website the google services aren’t included at all, even microg and require extra setup. Can this be made to let me run all my apps that need them?

        • notenoughbutter
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I’m using grapheneos and docs works just fine

          sheets should also work, I don’t see any reason why it shouldn’t

          and you probably haven’t read the website in a long while, grapheneos doesn’t support/recommend microg as it is an insecure/partial implementation of google services

          grapheneos has developed their own sandboxed play services, which act as a regular android app, it doesn’t get any special privileged access to imei or whatever stock oem android gives

          after installing this through the “apps” app, you can use grapheneos like regular oem android, but with better privacy and security features

        • Refurbished Refurbisher@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          You can still install Google services on GrapheneOS. It is sandboxed as user apps, so you can deny it permissions.

          https://grapheneos.org/usage#sandboxed-google-play

          DivestOS can use MicroG, which is a FOSS replacenent for Google services.

          Neither ROM includes it by default.

          Although if you can use the apps inside of a web browser, that would be better for privacy/avoiding Google.

          Also not sure if you use it, but Android Auto is proprietary as well and requires Google Apps. Not compatible in Graphene due to it requiring very invasive permissions.