GwenAEther
I don't know the exact figures, but the pattern has way more possible combinations than a pin.
Absolutely not. It's the complete opposite. Pattern lock is a similar to a PIN but unnecessarily restricted and strongly encourages highly insecure patterns.
Then, I can input a pattern without looking. As long as I know where I started, I can input the whole thing with my phone in my pocket or something. So that eliminates anyone looking at it as I input the pattern. The same is not true of a pin/password. You HAVE to look, as that's the nature of them.
Doesn't make sense, PIN is a similar grid without scrambling enabled. You're essentially just saying that you did the usual thing and chose a manually selected pattern you believe is great but is really quite awful and doesn't provide secure encryption.
As long as you can skip over dots (Say top left connects to top right, but top middle is still unused for later) the amount of complexity offered by a pattern is incredibly high. So I don't think a pattern is inherently less secure than any other unlocking method.
It's far worse than the other methods and not practical to support for random lock method generation. The whole point is users believe they're choosing a secure lock method but they aren't and pattern lock makes this problem much worse. You're demonstrating the problem and why it was removed.
You're essentially just reinforcing the reasons it was removed. It was removed because people shouldn't be a given a completely false sense of security. We tell people to use a random 6-digit PIN as the bare minimum secure lock method. What would be the equivalent for a pattern and how are you supposed to generate it randomly? Humans are not good at choosing things randomly themselves and it's not a good way to do things. The OS will be offering random PIN and passphrase generation which is in the process of being implemented. Aside from that, we don't want to implement more complexity for our other features to deal with pattern lock such as supporting for duress PIN/password, 2-factor fingerprint unlock and elsewhere. It's not a feature we want to have let alone implementing a bunch of code to support it. Android having it doesn't justify GrapheneOS having it. It was a mistake and they'd almost certainly remove it if it wouldn't cause outcry against it.