My #Pixel7Pro basically on its way, just waiting for ebay to give me a tracking link/info, but I'm now debating weither I should keep the stock, google-infested rom and have no issues, or have a big chance of facing issues with CalyxOS or GrapheneOS?

The main reason being, I'm not sure if some of my apps like banking and carrier apps, along with another app or two will work, plus the fact that I'm paying for YouTube Premium, and so on.

I don't want to have to deal with incompatibility issues, but I'm also extremely uncomfortable (paranoid maybe?) with using the stock rom, so I don't know how it'll go...

#privacy #phoneprivacy #google #googlepixel #googlephone #android #android16 #android15 #Android14 #calyxos #calyxinstitute #grapheneos #graphene_os

Keep the stock ROM
1.6%
Flash GrapheneOS
87.3%
Flash CalyxOS
11.1%
Poll ended at .
@LisaKalayji I've spent a lot of time thinking about this topic. I'll try to give my take,
1. Install and maintain Linux.
This is getting easier by the day, even for non technical folks. You can buy a computer from a company like #system76, that comes pre loaded with Linux and it's as easy to keep updated as a MacBook. I've been using their laptop for the last 3 years and I'm very satisfied.
2. Installing graphene os is a lot of work for a non technical person and i think there are better options. You can order a privacy focused phone from calyx.com that runs #calyxos. The #calyxinstitute is a privacy focused non profit and for a non technical person that might be the better approach.
3. More general thoughts: from my research on this topic my main takeaway is that fighting this battle on an individual level is meaningless. Collective action and strong regulation are the only things that can bring back real privacy. Reduce your personal use as much as you can and use aliases as frequently as possible.

We have updated screenshots on our website showcasing our major features. There are more updates in the pipeline as well. Oh, there are some easter eggs too if you can spot them.

Go on, take a look: https://calyxos.org/

#calyxos #calyxinstitute #androiddev

CalyxOS

Got my membership items in from @calyxinstitute today. Put the stickers on my laptop and phone and will wear the t-shirt with pride. I didn't actually buy any hardware from them, but all four phones in the house including my kids' devices all run #CalyxOS, so I figure the least I can do is kick them a few dollars for making something we benefit from.

#privacy #Android #calyxinstitute

Looking for a new cell service for my de-Googled Pixal 7 in US. I’m aware of several new privacy centric service, but Im questioning the vetting of these self marketed offerings for real world use. What’s on your hot list? What’s your experience been like with these services? #mobile #privacy #degoogled #grapheneos #calyxinstitute #calyxos #esim #SIMHacked

I've unplugged my DSL, after a particularly flaky afternoon. I'll be testing whether #CalyxInstitute (with SQM-based QoS) alone is sufficient for the household's dozen-or-so devices. It certainly is vastly more stable, according to the pings that have run every 15 seconds for the last two weeks.

I should do a more thorough analysis, but that will require scraping my mailbox and parsing email. Not difficult, but one extra step.

#CalyxInstitute update:

As part of the multi-wan project, I am running fault_tolerant_router, which sends pings out every 15 seconds to see which connections are up. I have it configured to email me whenever a connection goes down or comes back.

CenturyLink goes down every 2-3 hours. Usually only for a minute or two. Calyx, though, typically only goes down once a day, for a similar period.

I'm almost ready to cancel CenturyLink, though having the extra bandwidth has been nice.

After some success with #retroshare, I invited a couple friends to try it. We immediately discovered:

- it is amazingly unstable on linux, or at least the version of linux mint it was tested on.
- it isn't compatible with the highest tier of #calyxinstitute hotspots, which are inexplicably #ipv6-only. I'm not sure which is more wtf-worthy - retroshare is #ipv4-only, or an internet uplink that is ipv6-only.

fault_tolerant_router has been working great for me, but the uplinks it has been routing between are both a little more flaky than I'd like.

So I added code to run arbitrary user-specified commands when a link goes out or comes back up (or when they all do):
https://github.com/drsound/fault_tolerant_router/pull/25

This makes it pretty good at automatically reconnecting to #CalyxInstitute and my DSL. The latter is probably more flaky; still collecting data.