• 3 Posts
  • 4.31K Comments
Joined 1 year ago
cake
Cake day: September 21st, 2023

help-circle
  • but as far as comparability goes, sandboxed services is always better.

    Pretty sure you meant “compatibility”, which I agree with, since you’re running the actual Google software just isolated in user profile.

    I think you’ve covered it all pretty well. Moving away from Google Services comes with tradeoffs that we have to decide how to address, individually.

    For me, I’ve found there’s stuff I was used to having that I really don’t need anymore, things that can be accessed through a browser such as Hermit or Native Alpha (like my bank, The Free Dictionary and Etymonline).

    Other stuff I’ll have to address through some self-hosting, like location sharing which was through Google Maps.













  • Lineage and a fork, DivestOS are very close to Graphene, and run on far more devices.

    The search for perfection is the enemy of good.

    I’ve run Lineage for years on some spare devices. Battery life is so much better without Google Services.

    My most recent device (Pixel 5 with DivestOS) is averaging 1.1% battery consumption per hour over the last day. That included an hour of navigation, using Google maps with microG services.

    One old device runs longer with DivestOS than it ever did with stock, and the battery has lost 40% capacity. That’s how bad Google Services eat battery.

    Plus Lineage permits you to use a number of old devices, unlike Graphene. It’s good, it gives you far more control than Google.

    My final thought on Graphene - it needs to be taken over and lead by some professionals. Those folks act like stereotypical geeks of 30 years ago, arrogant, condescending (I worked with their type 30 years ago, and was a little like them then). They also denigrate anything less than what they deem “perfect”. The very definition of hubris.

    Their attitude is “if you have a problem you must’ve done something wrong, why did you do something wrong”. Having that experience with them has put me off Graphene permanently.

    Edit: I can re-lock the bootloader with Divest, so the condescending Graphene folks are just plain wrong about being the only OS that can do this. I don’t lock it, because my threat model doesn’t require it. The odds of my phone being grabbed by someone with state-actor-level skills being after me is non-existent, and there are easier ways to get the same data from me.



  • First, don’t buy new phones. You’re paying a massive premium to be first. Especially since you’re going to flash a rom, which has a little risk anyway (I’ve bricked phones by flashing, though not for years).

    I just upgraded from a 2017 flagship to a Pixel 5 (only because my cell company decided to stop it working on their network, when I can throw a different Sim in and it works fine). I was able to buy 3 Pixel 5’s for less than you paid for your new phone. Which means I have a daily driver, a hot spare, and a test device for a little over $400.

    If my daily breaks, I pickup my spare and swap the SIM, since I keep both phones synced with Syncthing. I don’t even have to login to anything because that’s all done. (I had 4 functional devices of my 2017 phone, they had become so cheap).

    So pick a 1-2 year old model that you like the features, and pay far less for it.

    Before (finally) coming to the pixel, I would look at the Lineage device list, then check those phones out at gsmarena.com and phonearena.com to see which I’d prefer, because Lineage has the broadest device support that I’ve seen.

    Today I run DivestOS, a fork of Lineage with some changes to a few things. I forget now exactly what I preferred (I’d have to pull up my comparison spreadsheet), but average battery consumption is a staggering 0.5% per hour, with microg services installed and a couple apps using it. Consumption average increases to about 4% per hour when I’m doing a lot of intensive stuff - copying files over the network, using nav, watching a video, etc.