A master volume control on Android OS, or at least a master mute toggle, would have prevented this morning's situation where my alarm volume was zero after having to drill down through 2 levels of interface to twiddle 5 separate volume sliders for last night's Eucharist + ashes service, and then hope I untwiddled them all correctly when we left. Evidently I didn't untwiddle the alarm slider.

Proton's Lumo blenderized usage notes from two different Shizuku platform apps (ShizuTools and Volume Manager) to hallucinate a nonexistent route to a single, unified, system-wide Android volume control. Also TIL mismatched Android version numbers vs. API numbering will totally screw up searches for obscure apps, dev channels or features - e.g. Android 4.1 "Jellybean" is API number 16, but if you want to find apps supported on Android 16 then you better specify codename "Baklava" or risk getting garbage info from 2011.

Also, the Android method to unlock dev options is absolutely stupid:
Settings ~ About Phone ~ Device Details ~ Android Version ~ Kernel Version ~ tap 7 times wtflol
peak "security through obscurity", which we learned in "intro to computers 101" is fail and bad.

What you CAN do in the absence of a unified master volume/mute toggle, is configure and toggle "Do Not Disturb" mode, or a create a comparable "mode" toggle that disallows all audio including notifications (or, less severely, all but call/texts from select or "starred" contacts). Assisted searches also failed to suggest that approach. I experimented a little and you can prevent music/media and alarm from breaking through DND, but the calibration dings for phone ring and SMS audio notification volume changes still dinged normally. So if you want to fiddle with your phone polite-quietly, even in DND mode you're on thin ice touching those sliders.

TIL an emergent idiom: "phubbing", portmanteau of "phone snubbing", for connection bids foiled by habitual device distractions.

11:30? protein drink and powder supplements brekarito
fried rice