Today I tried to do something non-trivial with #Android permissions: I have an app I don't really trust, which I need to give some images to. So I made a folder, and thought I could throw all the relevant images there, and give the app permissions to the folder only. As far as I could see, that's actually not an option. Android permissions to images are either the entire device, or one-by-one. No middle ground. (Samsung has "Secure Folder" which can sort-of do this, by essentially making a VM)
Similar posts
3 posts close in meaning, closest first
Interesting. The new glass effects are terrible, becsuse unlike iOS, they're not fluent throughout the Android experience. However, performance wise, Xiaomi have pulled off a noticeable uplift for sure. Animations aren't quite as smooth, but the underlying task you're doing (eg app launching or switching) is loaded before the animation finishes.
#TechIsShitDispatch my #Google #Pixel9 #Android phone has recently, within the past few days, started lying and claiming that the screen is being kept unlocked via Android's "extend unlock" feature while in fact it's _not_ being kept unlocked and when I try to open the phone it makes me enter my PIN (doesn't even accept my fingerprint). Restarting the phone makes the problem go away for a bit and then it comes back. Really amazing how Google breaks existing functionality on the regular.
woof, note this android 17 permissions change, hostile to LAN-only services: developer.android.com/privacy-… ... as of 17, you must allow "Nearby devices" or you can't get to your own stuff self-hosted on your LAN from mobile apps (e.g. firefox, firefox focus, chrome, ...)
