ticky

im in ur web site

  • she/her

web dracat

made:
internet-ti.me, @Watch, Wayback Classic, etc.

avatars appearing:

in 2D by nox lucent
in 3D by Zcythe

"If it were me, I'd have [changed] her design to make [her species] more visually clear" - some internet rando

I post embeds of other peoples' things at @ticky-reposts


You must log in to comment.

in reply to @ticky's post:

might not work (the perm in question is restricted to system apps usually), but: pm grant your.package.name android.permission.SHUTDOWN from adb, and then use intent: android.intent.action.ACTION_SHUTDOWN within your app.

A second option: You could turn on wifi debugging, pair it to a server or something in your house running cron, and/or have that server listen for device activity (e.g., a background app pinging it from the device) and dispatch the intent to your device remotely through adb shell am broadcast -a android.intent.action.ACTION_SHUTDOWN...

though at that point, adb shell reboot -p likely works too

everything I’m reading about that permission seems to suggest that it can’t be done from userspace at all

it appears that Wi-Fi debugging is killed each reboot, which would break this being anywhere near seamless sadly

ah, damn. I'd still give the permission/intent one a shot. this is a heavily vendorized Android after all, perhaps Meta made changes to the usual AOSP permissions?

and yeah, wifi debug being non-persistent is a bummer, in this case.