Mjolnir is a Home button router built for multi-display Android devices.
With BOTH: Home, dual-screen frontends (iisu, cocoon, console launcher, etc.) can launch both screens with a single button press.
With FOCUS: Home, you can do the same but only for the selected screen.
Prefer mixing single-screen activities? BOTH: Auto and FOCUS: Auto are here.
TOP/BOTTOM options remain for full customization.

FAQ | Releases | Add to Obtanium | Discord

Mjolnir gives you precise control over what happens when you press the Home button — routing frontends or launchers to the top display, bottom display, or both.
Originally designed for the AYN Thor, it also works on single-screen devices as a powerful Home-button automation tool.

Device support note (0.2.7): AYN Thor is the primary supported target. RG-DS support is planned for 0.2.8 and is not officially supported in 0.2.7.

Mjolnir supports two onboarding modes:

• Android’s default launcher remains unchanged
• Mjolnir launches your selected top/bottom apps without Home interception
• Requires valid apps in both slots

• Requires Notification + Accessibility permissions
• May require setting Mjolnir or Quickstep as default home depending on configuration
• Supports gestures, presets, and full routing control

Advanced Mode is ideal for:

• Heavy customization
• Multi-frontend setups
• Using gestures to control both displays
• Start-on-boot behavior (Advanced only)

Mjolnir includes a Safety Net activity that prevents soft-lock when a screen would otherwise be left with an empty activity stack.
Protection status is visible in the persistent notification and in Settings/Onboarding.

Configs live at: /Android/data/xyz.blacksheep.mjolnir/

Get the latest release from the Releases page.
Use Add to Obtanium for auto-updates.

Open Mjolnir → select Initialize Mjolnir Home.

• Basic Mode → simpler, safer, does not replace your launcher
• Advanced Mode → full Home routing control

You’ll be prompted for:

• Notification (keeps the service alive)
• Accessibility (required to capture Home events)

Basic Mode requires valid apps in both slots.
Advanced Mode allows more flexible setups.

Configure actions for:

• Single Tap
• Double Tap
• Triple Tap
• Long Press

Gestures support FOCUS, TOP, BOTTOM, and BOTH routing options.

Add the Mjolnir Home tile to toggle behavior on/off instantly.
Add the SafetyNet Debug tile to surface SafetyNet activities if needed.

• Route Home presses to:
  • Top screen
  • Bottom screen
  • Both screens
  • Recents menu
  • Custom bindings via gestures
• Gesture presets (Type-A / Type-B / Type-C + custom)
• Start on boot (Advanced only): BOTH: Auto or BOTH: Home
• Separate Basic / Advanced onboarding flows
• Safety Net protection for empty-activity soft-lock prevention
• Multi-screen routing powered by Android 10+ display APIs
• Optional Quick Tiles
• Included utilities for gaming frontends

Main screen is intended to decide which display should receive focus after a dual‑app launch when focus is ambiguous.
Right now, it does not change behavior because of ongoing issues with simultaneous app launching.
In the future, it will be the user’s way of saying “this is where I expect focus to default to.”

A helper tool for frontends like ES-DE and Beacon:

• Generates .steam metadata files
• Accepts SteamDB links via Android’s Share menu
• Prevents duplicates
• Supports bulk deletion

This tool will be spun off into its own app in a future release.

Open in Android Studio → Sync Gradle → Run.

Open an issue for bugs, requests, or feedback.

Buy me a coffee: https://ko-fi.com/xyzblacksheep