If you can afford it, I personally highly recommend just buying two USB-C hardware Yubikeys and storing it on there. Built in back up and if you put it on your keyring, it’s always nearby. You can still use your phone to access the code as well.

Not exactly super helpful for solving this problem but since you’re already going to have to reset or get new accounts, it’s a good time to switch over if you’re interested.

I can’t speak for Canada but at least here in the US, I’ve used every Pixel on any carrier I wanted. And most of them were small ones. Straight Talk, Ting, T-Mobile, and one more I can’t even remember the name of.

IIRC, the “allowlist” stuff was just “known carriers that use towers that are compatible with this phone.” As in, different carriers use different “bands”, or frequency ranges, for their transmissions. Your phone has to have hardware support for those bands. So the “allowlist” is really just “we know these work.” I’m pretty sure neither Samsung nor Google will stop you from using an unlocked phone bought from them with any carrier that’ll accept it. These days, I just stick a SIM (or eSIM) into my phone and just go.

Hmmm…I smell a massacre. Seems to be the only way to back these bastards up.

Make sure you’re on 1.19.0 of F-Droid, which needs to be installed manually for now.

https://f-droid.org/de/2024/02/01/twif.html

You’re not wrong but it feels disingenuous to say this. The entire repo with all of its dependencies checked out for a large website can easily clock at half a gig but there’s no popular website now that’s asking any users to download half a gig worth of stuff before they can use it.

There ARE websites where, if you keep them open long enough, they’ll constantly pull more and more data (usually for ads) but even that is measured more so in tens of megabytes.

And none of this is to say that websites haven’t gotten too big, just that comparing a downloaded app’s size to the size of a website’s unbuilt unbundled source with all of its dependencies is an unfair comparison.

Even if you turned it back at this point, it still wouldn’t work.

This is pretty infuriating though; Google works just fine with any device that doesn’t run Android so why would they care that you’re running a custom ROM?

My guess is something less evil and more mundane: something about your number changed in their system and now they can’t send codes to it, which is why it’s grayed out. Maybe it was previously classified as a mobile number but now is classified as a landline.

Your only option, if you don’t have any backup codes, is to use that “Get Help” option they have that takes a few days and then either start carrying around backup codes, a Yubikey, or De-Google.

Hey, maybe all 3!

A Travel Roku is the real pro tip.

It’s terrifying that the only way to win these days is to just never have been born. Even if you don’t play, someone you interact with online is and you get taken in that way.

All to sell you ads for things you don’t need or care about.

I’ve never dealt with this using a hypersonic speaker but I’m very familiar with attempting to record lyrics while hearing my own voice on a delay and it’s impossible. Thinking about just trying to read text while hearing myself on a delay sounds similarly difficult.

My guess is that some of us, musicians especially, are more reliant on internal timing in all things.

What’s probably happening here is your adapter is signaling some button press when you connect it that’s popping up the Assistant. Only way to fix that is to get a new adapter since you can’t manually disable that input from triggering the Assistant without root.

However, you can completely disable the Google Assistant from appearing at all via:

Settings > Apps > Default Apps > Digital Assistant App > Default Digital Assistant App > None

That should fully disable it in all regards and it’ll never pop up again.