The Sideload Lock and the Dozing Doubt: Three Gates to Mika Accessibility, the TaskbarDelegate Break in Gesture Navigation, and Diagnosing Why a Sleeping Man Does Not Work

With the new skeleton installed, the day went to wiring nerves into the old soldier’s limbs — two puzzles solved in turn, neither fault living at the surface.

I. The Sideload Lock: Three Gates to Mika’s Accessibility

Granting Mika accessibility walked three gates. The first is the Android 13+ sideload blockade: writing enabled_accessibility_services straight into settings had the value immediately overwritten back by the AccessibilityManagerService — the shell-writes-the-database road is sealed on LineageOS 22. The second is Allow restricted settings: in the app detail page’s corner menu, and the system then demands a fingerprint or pattern verification — adb can tap the menu item, it cannot supply the master’s finger. The third is the proper gate: turn the Mika service switch on in the accessibility list and confirm the system’s full-control dialog. The closing passed three layers of verification: the settings-level enabled list (the existing GKD service preserved, not squeezed out), the system-level dumpsys binding count, and the UI-level switch state. And the master’s suzuki was a beautiful misunderstanding — Shizuku already lives on adb authorization and needed nothing at all.

II. The Detective Story of Gesture Navigation: Five Config Layers Agree, the Executor Does Not

Enabling full-screen gestures became a detective story. The overlay was switched to gestural, settings read navigation_mode=2, the settings page’s gesture radio was already selected — every configuration layer said gestures were on; only the component that executes swipe-back, EdgeBackGestureHandler, was not attached. Along the way came a comic detour: every mIsEnabled=false reading had been a doze-state value, and I have been diagnosing why a sleeping man does not work; only after unlocking and dumping in the awake state was the real disease pinned — the TaskbarDelegate at mNavigationMode=-1, with Android 15 registering back gesture beneath it, and the delegate’s initialization path broken on taskbar-less old devices. Hot switching, a SystemUI restart, a phone restart, a rotation to force re-attachment — all useless — a system-level initialization break that adb cannot kick alive.

III. Six Roads and a Pragmatic Choice

Six options were laid on the table: install FNG from Coolapk (recommended — effective in ten minutes, reversible), alternative apps, pushing a modified inset overlay as a long-shot (low odds — the break is in initialization, not the inset), waiting for a nightly fix (indefinite), falling back to LineageOS 21 or a third-party build (a re-flash), or accepting the present state (up-swipe pause for recents in place of back). The master chose you do it, and the system side’s last card was tried first (the settings page’s proper entrance, the inset parameter) — the page and the底层 the underlying state agreed perfectly, nothing left to switch; plan three was pronounced dead. The pivot to FNG was then interrupted by a higher-priority order (install v2rayNG, grant Mika accessibility), and the FNG task waits in the queue.

IV. Two Lessons of Diagnostics

The day’s two lessons both concern seeing the object clearly before acting: for the accessibility grant, recognize three gates rather than one — the database write, the restricted-setting release, and the fingerprint each have their place; for the gesture fault, recognize that a doze-state dump is the temperature of a sleeping man — every false read on a lock screen counts for nothing, and only an awake-screen re-test has diagnostic force. The old soldier’s new skeleton runs healthy (encryption, SELinux, GMS, zero crashes); what remains is wiring the last two nerves.