trying to execute that requires the caller (so user shell
from using adb most likely) to have the same uid as Google Play which should never be the case
afair
trying to execute that requires the caller (so user shell
from using adb most likely) to have the same uid as Google Play which should never be the case
afair
why I prefer firefox over chrome/edge / other chromium forks
idk tbh, SafetyNet / Play Integrity have existed for a while
honse
Kinda makes sense. A paid app on Google Play is a license to download the .apk file(s). Then a user could make copies, and without DRM, it'd be the same situation as with copyrighted movies and whatnot.
I'm not saying I support them, it's just that they are like this for a reason
Maybe everyone was just OK with mobile devices being locked down heavily from the start, and now it's more or less the same level for most
mac and chrome + safari, seems about right
no, for cross-language interoperability. ok I just noticed that this breaks other calendar systems but well
every date MUST be in RFC 3339 format. e.g. 2024-09-08, with optionally the time: 21:41:24+02:00
and hell no not ISO 8601 cause then people would use stuff like 2024W154
huh I never click on the driver and still pass lol
maybe cause I started doing them slowly and adding unnecessary but humane touches / mouse movements
Is the bootloader unlocking requirement that FRP is not triggered a hard one or just because the settings screen isn't (or shouldn't) be reachable? Now that OEM unlocking and FRP aren't tied together anymore, it doesn't seem like a hard one
maybe thats related to your ad blocker(s) lol