Skip to content

Advanced & System ​

For power users, LinkSheet provides deep system integration and developer tools.

Shizuku Integration ​

LinkSheet uses Shizuku to perform system-level operations without root access.

  • Manage App Links:
    • Allows you to batch enable or disable the "Open supported links" setting for multiple apps at once.
    • This is much faster than manually navigating to each app's system settings page to revoke link handling permissions.
  • Auto-disable link handling: Automatically disable link handling for an app right after it is selected, streaming the takeover of every link.
  • Verification Reset:
    • Purpose: Forces Android to re-verify app links (Intent Filters).
    • Use Case: Useful when app associations get stuck, corrupted, or when you've installed a new app that isn't capturing its links correctly.
  • Requirements: Shizuku app installed and service running (via Root or Wireless Debugging).

NOTE: A rewritten Shizuku integration is available behind the experimental Enable Shizuku flag. When enabled, Shizuku gains its own entry in the main settings screen.

Multi-User & Profiles ​

LinkSheet supports Android's multi-user and work profile features.

  • Profile Switcher: Show a control in the bottom sheet to selectively open links in a different user or work profile.
  • Send Target: Send a link to a different profile directly, without opening the sheet first.
  • App Detection: Automatically detects apps installed in different profiles and presents them in the selection sheet.

Backup & Restore ​

Back up your configuration or transfer it to another device from Advanced → Backup.

  • Backup: Writes your settings to a file.
    • Options: Include history (link click and app history), Include log hash key (the key used to redact your logs).
  • Restore: Reads a previous backup from a file. You choose how existing data is handled:
    • Replace: Keep existing data, overwrite on conflict.
    • Merge: Keep existing data, ignore on conflict.
    • Erase & restore: Erase current data and restore the backup.
  • A backup bundles Preferences, Experiments, App state, Selection history, and Cached URLs.

Logging & Debugging ​

  • Log Viewer: View internal app logs to diagnose issues, grouped by capture time.
  • Redaction: Exported logs are automatically redacted using a hash key to remove sensitive info like exact URLs and package names before sharing. You can choose to include the hash key in a backup.
  • Crash Logs: Option to include stack traces for crash reporting.

Experiments & Feature Flags ​

Advanced → Experiments lets you try bleeding-edge features that are still in development. Experiments are grouped as follows:

Improved Bottom Sheet ​

  • Ignore accidental taps while sheet is animating: Prevents accidental clicks while the bottom sheet is animating.
  • Disable bottom sheet state save: Prevents the bottom sheet from remembering its state between opens.

Logging ​

  • Disable log persistence: Stops saving internal logs to device storage to save IO and space.
  • Use LinkEngine: A new core engine for matching and processing links.
  • Enable new VLH page: A redesigned interface for managing verified link handlers.

LibRedirect ​

  • QuickJS engine: Uses the QuickJS JavaScript engine to execute LibRedirect rules. The default uses a Native Kotlin implementation, which is lighter and faster but may not support all complex redirection rules that require actual JavaScript execution.
  • Custom instances: Add your own LibRedirect frontend instances.

Shizuku ​

  • Enable Shizuku: Enables the rewritten Shizuku integration.

In addition to the Experiments screen, LinkSheet has a small set of feature flags (exposed under Advanced → Debug) that gate larger, unfinished parts of the UI, such as the new bottom sheet, URL decluttering, the switch-profile UI, and the LinkSheet Compat menu.

Note: Experimental features may be unstable, change frequently, or be moved to stable settings once they are fully tested. The Experiments screen includes a reset button to restore all experiments to their defaults.

Developer Menu ​

Enabling Developer mode (in the About screen) adds a Dev entry to the settings, exposing development tools such as scenario dumps and internal state inspection.