I have not any prior experience with installing custom ROMs, but after trying it out (and getting stuck, and googling and finding answers) I successfully did it. Below is my home screen if anybody is curious:

I use OpenBoard for my keyboard. Unfortunately I am still dependent on Play Store since some of the apps I need can only be found there. Sometimes it feels meaningless committing to this whole thing because I’m not perfectly private; then I think this is better than using a regular iPhone or Android phone.

So far I’m liking it. I am naturally inclined to feel hesitant about using this as my main phone and plugging in a SIM since it’s custom, but I’m slowly making the transition.

Feel free to share any beginners advice or your own experience using GOS for the first time. Cheers!

  • EveryMuffinIsNowEncrypted@lemmy.blahaj.zoneEnglish
    131·
    4 months ago

    I’d love to try out GrapheneOS (or another OS), but I can’t afford a second phone, and there’s no way I’m gonna dive head-first into something entirely unfamiliar to me when it’s my only method for telephony.

    • IDew@lemm.ee
      16·
      4 months ago

      It does function just like any other phone so far I’ve tested. No app that simply doesn’t work. And if it doesn’t, you can simply exploit the GOS hardening in settings to improve compatibility. You overall have more control over any app, which I like

      • K4mpfie@feddit.de
        3·
        4 months ago

        One of my biggest concern is banking apps not working. Is that still an issue with Custom ROMs? Edit: Nevermind, answerd below

    • 𝙻𝚘𝚗𝚐𝙼𝚊𝚌𝚃𝚘𝚙𝚙𝚎𝚍𝚄𝚙@aussie.zone
      5·
      4 months ago

      Ironically it was when the stock android upgrade on my pixel 7 completely bricked my phone (due to the multiple user profiles bug) that I decided to jump in to Graphene head first.

      Compared to my experience running random ROMs on Samsungs back in the era of galaxy note 1 to 4, Graphene installer was so easy!

    • Mike D.@lemm.ee
      4·
      4 months ago

      I feel the same. If I try to install a different ROM and it falls I could be without a phone for a bit.

    • communism@lemmy.ml
      3·
      4 months ago

      It is really similar to stock android in terms of functionality. It’s just degoogled and hardened. It’s designed to be user-friendly and not for tech-savvy people (though tech-savvy-friendly—which is part of being user-friendly imo). I promise you you can use it out of the box once installed just like a stock android install. The only thing to be aware of is to install some kind of package manager like fdroid or aurora store, or even grapheneos’s unprivileged google play store, to get apps, unless you just want to use the stock apps it comes with i guess in which case you probably shouldn’t waste money on a smartphone.

        • communism@lemmy.ml
          3·
          4 months ago

          Yes, only Pixels are officially supported. If you want to add support for other devices, it’s a foss project and you’re welcome to write the code yourself. For other devices there are other degoogled OSes you can use. Graphene is generally considered the most secure but if you have another phone you can install one of the other AOSP forks or turn it into a linux phone or something

          • The Cuuuuube@beehaw.orgEnglish
            3·
            4 months ago

            Its also worth noting Graphene’s focus on pixel devices stems from those devices having more easily secured hardware. Which android fork you decide to use will depend on your particular use case. I wound up going with a Pixel and Graphene for android auto. But if you’re someone with existing hardware that you want to set up with a degoogled os, there’s e/os, lineageos, CalyxOS, iodé, and, if you wanna get really weird, postmarket os. Having done a deep dive into this I can honestly day there’s no single OSFA answer to this.