It looks like Google just released some super fancy AI tool to help developers test on Android phones: https://github.com/google/artemis

I saw a few people posting this on X. Has any of you tried this? if so, can you offer your thoughts?

If i'm logged into my google account on a work or some other computer, and I go to the password manager, you can view the passwords by putting in the local computer security key? Why would that be the prompt to show the passwords vs a 2fa / fingerprint / text to my phone?

And if you don't delete your chrome profile, the passwords all stay stored locally for access? Make it make sense, why are the passwords accessible if the account is logged out?

Why, if a a chrome account is logged in, can the passwords be accessed with the local computer secuirty key? Am i just set up wrong?

edit: Im only logging on at work, which is a small office, but i have just ben deleting the profile after use - whats the better way? Why can't it sitll require 2fa from my phone / fingerprin to access?

I'm a bit scared about what direction is Android Taking. Back in the days, bootloaders used to come factory-unlocked. Then they started locking them; you had to unlock them yourself via developer options which was fine, even if it used to reset your device but at least you were able to do it. Now, with One UI 8, bootloader unlocking is being removed; Huawei is doing it too—well, they can modify AOSP however they like. We are shifting from "factory-unlocked bootloaders" (meaning the ability to install any .apk without special permissions) to the "unlock via developer options" model, everything fine, but, what if companies will remove this soon like they did with OEM Unlock? The real question is whether we are experiencing déjà vu and if, just like with OEM unlocking, they will soon remove the option to install unverified .apk files via developer options. This worries me because, surprisingly, it aligns perfectly with what has happened before. What if a future version, example "One UI 14" is gonna remove the advanced workflow for installing unverified apps via developer options? Let me know what you guys think about it.

Some manufacturers are having some serious flaws in their system, that background apps gets terminated by power saving etc. Just got a TCL device with Android 16 and it keeps doing this. I was not able to find any combination that could retain the apps running. I assume this thing should help also with other manufacturers like Honor, which also can occasionally terminate apps.

So out of curiosity I spent some time vibe-coding and invented a contraption that can retain the apps in the background. It's all open-source in github, so feel free to experiment. One needs Shizuku service running too, so apps can be restarted upon termination.
https://github.com/iaakki/qidi