MisakaX features—matched to the device, not the checkbox.

MisakaX can change selected capability values used by iOS or iPadOS on a release-supported build. The owner lists flags for interface, device behavior, developer surfaces and narrow installer paths. The exact result still depends on the product track, build, model, hardware, region and service prerequisites.

This ledger contains 26 published capability claims checked against the current owner pages on August 31, 2026: 22 listed by MisakaX and carried into misaka26, plus four misaka26-only additions. Upcoming items are not counted as released features.

No. A supported release range only says which builds the product claims to address. Each flag can have a narrower iOS family, model, hardware, region or service boundary, and a successful restore can still end with no visible or functional result.

No. The minimum shown in the owner’s feature list is an entry condition, not a complete compatibility statement. Match ProductVersion, BuildVersion, product release and platform first, then evaluate the feature-specific dependency.

No. That label describes the feature’s minimum family inside misaka26; it does not override the product’s write-path boundary. The current owner range stops at iOS/iPadOS 26.1 plus 26.2 beta 1, so 26.2 final and later builds must not be inferred as supported.

The current owner lists the same 22 core capability claims in both product branches. misaka26 additionally lists TrollPad, PWM, SRD Mode and an App Store eligibility flag for M/Pro-chip games. That overlap does not make the products interchangeable; their supported builds, release channels and reload instructions differ.

The current misaka26 README places those two names under “upcoming features,” not “supported features.” We therefore exclude them from the released ledger until the owner publishes them as available in a specific release.

No. A capability value can influence a software decision or reveal a settings surface. It cannot add a display cutout, LTPO-like panel behavior, Action button, Camera Control, Pencil digitizer, crash-detection sensor, RAM or GPU.

It can expose Apple Intelligence-related eligibility or settings values on the owner’s stated beta-era path, but that is not the same as functional Apple Intelligence. Apple’s supported path also depends on compatible hardware, system version, storage, matching language, region and downloaded on-device models.

The setting, model download and service function are separate stages. A public misaka26 issue also reports Siri, dictation and other voice behavior failing after capability changes. Record the selected flags and every affected service, then stop adding changes and use the matching revert route.

The flag can expose Dynamic Island UI, but it cannot reshape the physical cutout. Verify real Live Activities, expansion, touch targets and portrait/landscape placement; notch overlap, spacing or animation faults mean the outcome is partial.

No. The setting can appear while panel behavior, refresh strategy, power use and screen-off conditions differ from a supported device. Test locked, face-down or covered, and under Low Power Mode rather than accepting the toggle as proof.

Return to the baseline rather than waiting for a checkbox to become safe. Record the feature, brightness, charging state and elapsed time; stop the test, use the matching revert route and let the device return to a normal temperature. Apple notes that charging itself can be paused when an iPhone becomes too hot or cold.

No. Apple documents charge limits for its supported iPhone models, but an exposed setting on another model is not evidence of reliable battery control. Observe a complete charging cycle and remember that even Apple’s supported implementation can occasionally charge to 100 percent for calibration.

No. These flags may expose configuration UI. They cannot replace the Ring/Silent switch or add Camera Control hardware, pressure sensing or capacitive gestures.

No. A settings row or capability answer cannot add the digitizer and pairing hardware required for actual Pencil input. Treat the result as UI-only unless pairing and drawing input both work.

No. Never test an emergency feature by simulating a collision. A visible setting does not validate the sensors, algorithms, connectivity or emergency-service chain required for the real feature.

No. It cannot add supported Apple Watch sensing, regional clearance or medical validity. Apple states that its own notification feature is not a medical device or a replacement for diagnosis, treatment or monitoring by a clinician.

The current misaka26 1.6 release page is internally inconsistent: its feature line says TrollPad requires macOS, while the same changelog says version 1.3 added Windows and Intel Mac support. We label the platform scope unresolved and do not turn either sentence into a universal rule.

No. They can expose multitasking or iPad-style interface behavior. Product identity changes are a different and more dangerous action; do not borrow an iPad MobileGestalt or infer safe identity spoofing from a windowing UI.

No published feature claim says Find My must remain off as a permanent dependency. If your matched Apply workflow temporarily required it off, turn Find My back on as soon as that workflow is complete and verify the device appears in Find My; Apple requires Find My to be enabled before a lost device can be located.

No. The owner describes an SRD-related flag. It does not make a consumer device part of Apple’s Security Research Device program or grant special entitlements, hardware, documentation or support.

Not necessarily. App Store visibility, download, launch and stable gameplay are four different outcomes. An eligibility value cannot add the GPU, memory, controls or thermal capacity expected by the game.

The primary TrollRestore project publishes iOS/iPadOS 15.2 through 16.7 RC build 20H18 and the four iOS 17.0 builds 21A326, 21A327, 21A329 and 21A331. This narrow installer range is separate from general MisakaX feature compatibility.

No. Use one feature or the smallest practical set. A minimal change makes no-effect, side effects and rollback attributable; a large bundle makes it difficult to know which value caused the result.

Record restore, reload, setting and functional result separately. Success can describe an earlier process stage; issue #115 records a success message and reboot followed by missing Apple Intelligence and Always-On Display settings. Do not spam Apply.

Record when it disappeared and whether only the setting, only the function or both changed. The owner does not publish one permanence contract for every flag and build. Re-check the exact release and reload instruction, preserve the log and baseline, and do not automatically add repeated writes.

Use the reset or original-file route documented for the same product and release, perform the required reboot or respring, then verify both the setting and the actual function against your baseline. Deleting the computer app does not revert the device.

There is no documented universal selective-rollback contract. The attributable baseline route restores the matched original state; re-adding selected flags afterward is a new change set with a new test. Do not guess which plist key is safe to remove manually.

There is no universal persistence rule. Treat the destination as a new build: preserve the original file and a current backup, use the matching revert route while the device is reachable, verify the baseline, update, then re-check compatibility before another Apply.

Do not substitute a similarly named toggle, paste unknown MobileGestalt keys or assume an “upcoming” item is released. Preserve your current state and wait for a product owner to publish the feature and its release boundary.

Confirm the exact product and release file first. A repository-wide feature list does not prove that every historical binary, platform build or device state presents the same control. Do not switch tracks or edit the plist to imitate the missing checkbox; capture the app version, platform and screenshot, then use the owner’s support route.