With the default settings, the latest versions of PayPal only require disabling secure app spawning.
It may also require dynamic code loading via storage, dynamic code loading via memory and native debugging being permitted but those aren't blocked for user installed apps by default. People can opt-in to those being enabled by default for user installed apps similarly to memory tagging, but memory tagging has the biggest positive impact.
What Pixel do you have? Modem quality varies and signal strength could play a role. My 9a gets hot in areas with poor reception but is fine at work where I get over a gigabit down.
I haven't been updating AUR packages since the initial incident. Thankfully hadn't updated for a week prior to it. Tonight I'll be uninstalling all the AUR packages I possibly can.
I'm a GrapheneOS user. The duress passcode feature will reboot the phone to a "corrupted data" screen, so it's pretty obvious that it's been used to render data inaccessible.
They've been available natively on Nightly with some basic UI support since they were first implemented a decade ago. Some other pre-release builds have them too but it's been too long and I cannot remember which ones did or didn't.
I don't use Nightly and I've been using containers for I think that long without any extension for it.
Edit: looks like I enabled them manually and couldn't remember/find it, it's in about:config under the name "privacy.userContext" instead of "containers".
as far as i remember, the low level container functionality was always in the core browser. what the extension adds is the UI to manage containers. with this change it appears the UI is merged back into the core browser.
It's been there just as long, turn it on with "privacy.userContext.ui.enabled" and manage them at "about:preferences#containers"
The addons added extra functionality but everything they've listed in this announcement is already there. Sounds like they're just flipping these two flags by default.