I'm not making a judgement on it either way. These are things that are available to change in source. I'm just pointing it out, since others aren't aware of how things can be done.

But there are things locked out in the US I cannot get to. One of the things I've wanted to do for some years is turn on BeiDou reception, but it has a firmware geofence while inside CONUS. For Qualcomm devices there's no way that I've been able to find a way around this, it's not an opensource component. Just to preempt anyone saying it's because it's Chinese spywhere, Qualcomm/Tomtom engineers don't feel receive-only reception is a security risk (there's a report somewhere where military said the same, it's strictly a political prohibition): https://www.uscc.gov/sites/default/files/Research/Staff%20Re...

One of the reasons I build my own LineageOS builds is because of terrible one-party consent recording laws (in places like California) there’s no geographic way in Android to check it on a state-by-state way. It just goes off country code and disables it for the US since quite a few states it’s illegal to do. For my state it isn’t illegal so I modified my builds to allow it.

There are other things like this too in Android disabled on per-country. Japan has a camera shutter noise that cannot be disabled but this was a request by their carriers, apparently not a law, big discussion under this review: https://review.lineageos.org/c/LineageOS/android_frameworks_...

The sheer arrogance that you think someone manipulated successfully will just re-think the situation and ask their friends/family. The naivety to assume all scammers are impulsive fools and don't do this for a living, as their primary line of work.

So Google's going to add some nonsense abstraction layer and when this fails to curb the problem after a 24 hour wait, it will be extended more maybe a week, and more information must be collected to release it. We all know how this goes.