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

help-circle




  • 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 30nyears 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.


  • 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.





  • “It doesn’t exist if it isn’t written down”. Someone said that to me long ago, and it really changed my perspective.

    I recently came across the PARA concept - everything we deal with falls into one of these 4 categories: Projects, Area of Responsibility, Resource, Archive.

    I restructured my OneNote notebooks to use it, and it’s been a game changer. Now when an idea comes my way, I can immediately categorize it so I know what to do with it (even if just on my head). I added a final R to my notebooks - Reference, because I save a lot of info that I need access to.

    It surprised me that at any one time I have about 30 ongoing personal projects. Seeing them laid out as tabs in my notebook makes them more apparent, instead of just floating around in the back of my head. I’ve even Archived a few after seeing them languish, and realizing they were fleeting ideas I really don’t need or have time for.







  • Changes by shitty apps wanting to start with windows and register for context menus.

    I’ve had windows machines run fine for 10 years, and some having trouble at 6 months. The difference being the problematic machines I’ve made tons of changes, installed tons of risky apps.

    I’ve also run registry cleaners as a test, and it’s made a world of difference.

    In short: crappy apps make windows run poorly.



  • Well before.

    And “refuse to change their ways” - are you going to underwrite the project to implement a transition and hold all the liability for the risks?

    Its not like changing systems is just a click of a button, this is an extensive project, that you better get right or you’re dealing with records going the wrong way, potentially having serious life and safety implications.

    Plus, you have to maintain this legacy fax system because not everyone else has migrated to something new. So for the remainder of your career, it still doesn’t go away, and you’ll have to continue to pay for its maintenance.

    Companies have systems they’ve built up over years, that works. They’ll move forward as it makes fiscal sense.


  • “embedded in many workflows”

    Key statement right there.

    And once people see what that really means, and what it would take to move past it (including time, cost, and risk), they may start to understand. You’re dealing with it first hand, so you know what’s involved.

    It became the de facto way to send stuff with high confidence it went to the right place. Then tech addressed the paper-to-paper over one phone line issue with modem banks into a fax server. So all the same fundamental comm tech (so fully backwards-compatible), but a better solution for the company with that infrastructure. Such a company has little motivation to completely change to something new, since they’d have to retain this for anyone that hasn’t switched. Chicken-and-egg problem, that’s slowly moving forward.

    It’ll be a long time before it’s gone completely. Perhaps in 20 years, but I suspect fax will still be around as a fallback/compatibility.