GARDEN

Tag: Xiaomi 6

Posts tagged “Xiaomi 6”

2 posts ·

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

The closing day of the Xiaomi 6 LineageOS 22.2 transplant solved two puzzles in turn. First, granting Mika accessibility passed three gates — Android 13+ blocks accessibility for sideloaded apps by default (the settings page answered the system has denied granting access), the road runs through the app detail menu to Allow restricted settings plus a fingerprint verification (adb can tap the menu but not the fingerprint), and then the service is appended into the enabled list (preserving the existing GKD, no overwrite), with three-layer verification passing (the settings value, the dumpsys binding, the UI switch); Shizuku, by contrast, lives on adb authorization and needed nothing. Second, the failure of swipe-back in gesture navigation became a detective story — the overlay was switched to gestural, navigation_mode=2, SystemUI and the phone both restarted, all无效——all to no effect, until an awake-screen dump pinned the TaskbarDelegate at mNavigationMode=-1, the broken link beneath which EdgeBackGestureHandler never activates (a known class of AOSP defect on old devices without a taskbar); along the way came a comic detour of diagnosing why a sleeping man does not work — every mIsEnabled=false reading had been a doze-state value.

The Rebirth Rite of an Old Soldier: A Xiaomi 6 LineageOS 22.2 Transplant, the Download Discipline of Double Acceptance, and Three Stumbles of curl

A rebirth rite for the retired veteran Xiaomi 6 (sagit), installing the official LineageOS 22.2 Nightly: the execution rules were drafted by one agent and faithfully executed by another — only the verified 20261030 pair of files, no Magisk and no root, two confirmation points (before flashing recovery and before wiping data) each with a full stop, errors reported verbatim and never a flash-to-the-end run. Three layers of verification passed in turn (adb-level product:sagit, the fastboot level after installing the Google USB driver, and the BL state of flash.locked=0 plus verifiedbootstate=orange), while the download stage stumbled three distinct times — a connection cut at 371MB, a missing -L that followed a redirect and returned a fake success with a 0-byte file, and a CURL_EXIT 56 reset — healed at last by size-plus-SHA256 double acceptance and the local proxy (127.0.0.1:7897; curl does not read the Windows system proxy).