I've been trying to reduce my reliance on all things Google, and one of the big ones is password management. I've tried several times to make the jump, but every time I start researching options I'm overwhelmed by the selection. There are a lot of popular options out there, and I really don't have the time/energy to endure a misstep. So without a clear idea of which manager will check all of my boxes, I end up bailing on the process and keep using chrome's built in option.

So to start, here's what I like about Chrome:

• Automatically offers to store passwords without extra clicks
• Autofills automatically where it can, and gives me an easy choice when it can't
• Works everywhere I need passwords. (basically everywhere I browse the internet since chrome works everywhere)
• Minimal overhead. This is hard to beat since Chrome just includes it, so I'm fine with a little extra setup if necessary.

I used to use keepass portable on a thumb drive (I want to say circa ~2009ish), but it became really inconvenient as my usage shifted more to mobile devices.

I see this as a first step to also reducing my reliance on Chrome so I can start to consider other browsers. Right now I feel locked in to Google's ecosystem, but I know I can break it up if I don't get too bogged down by choice. Much appreciate any help. :)

I am and have been on a bit of a quest to make my computing devices suck less.

Over the last few years I have migrated all of my laptops and desktops over to various Linux flavors. My experience with this process is that each flavor has their own quirks that need to be ironed out, but after getting things running there is little in the way of maintenance. Things kind of just work nowadays.

I have been looking into getting something like (but not necessarily) LineageOS on my phone. As I am looking into this and reading forums on the subject, it seems like a perpetual arms race between application developers and application users. One puts in a way to check for root, then there are root hiders, then there are root hider checkers, then there are root hiders that you build with custom names, etc.

I want my device to not suck.

I don’t want to be going in and fighting with my banking applications every time there is an update. I am totally willing to fight a painful setup once.

Is a custom phone OS something that is essentially only viable to use if you are driven by spite? Am I reading too much into the struggles that are posted in various forums? I am looking for any input for anyone that has used a custom OS short or long term.

I doubt I'll find any new ideas, but maybe someone here has one. I'm running out of places to turn, with no solution.

I have been in a fight with Fitbit support for a few weeks now over their push to migrate everyone to a Google-linked Fitbit account. I'm pretty sure what I've found is a rare edge case of a bug, or rather, an unaccounted for set of conditions when trying to migrate.

A long time ago, 2017 I think, I created a Google-linked Fitbit Account (via oauth, "Login with Google"). I used it briefly and then stopped, and completely forgot about its existence.

In 2022, I got a Pixel Watch and created a new/second Fitbit Account with a different email address, as I did not remember I had a Fitbit account already and I wanted to use a masked email address through my personal domain.

With the push to migrate all Fitbit accounts to Google accounts, I decided to try to do so last month. When I attempted to migrate my second account to a Google account, I got an error that I already had an account registered under my Google account. So I logged in to that old 2017 Google account and initiated its deletion. It told it me would take 30 days to delete it, so I waited 31 days.

31 days later, I tried to migrate my second account to a Google account. When I try to do so, I get an error:

Can't use Fitbit with this Google Account
This could be because you're using a Google Workspace account, or because your account is supervised.

My account is neither a child account, nor a Workspace account, it's a standard (adult) account I've had for something like 16 years.

So I tried to see if my old Google account was perhaps not deleted after all. I tried to log in to my old account via oauth (Sign In > Continue with Google), and I get a different error:

Sign in again to continue
Since you deleted Fitbit from your Google Account, you’ll need to sign in again as a new user.

I suspect that what happens when I deleted my old/original Google account is that it wasn't actually deleted, but made inactive with some "deleted" flag, but the account hasn't been purged. As a result, I'm unable to migrate my new account to the same email address I used for my old Google account.

Reaching out to Fitbit, they continually put the blame on Google for reporting my account as a workspace/supervised account, and the only solution they'll offer me is "You should create a new Google account". Google has also been unable to help, but that doesn't surprise me, as I don't think it's an issue on their end. Requests to Fitbit to escalate my case to a higher tier of support and/or someone from some type of database team have been stonewalled, and I think that Fitbit support has now just stopped responding to me entirely.

Does anyone have any idea where I could turn?