ShizuStore

Nothing Modes

Dvorinka

0.19.21 · GitHub

Download APK
Automation Android 9+ 4 days ago GPL-3.0
580 ShizuStore
2k GitHub
11 Stars
57 MB Size

More about this app

Automation app for Nothing phones (modes, routines, Glyph) that also runs on other Android devices with optional Shizuku

Nothing Modes logo

Nothing Modes

nothing-modes.vercel.app

Open-source Android automation for Nothing phones — and every other Android device.

Built like a premium system app: OLED-black surfaces, monoline iconography, dot-matrix hero type, and a single red accent. The engine is pure Kotlin; the UI is Jetpack Compose. Shizuku and Nothing Glyph are supported, not required.

Nothing Modes

Automation list Mode detail Mode builder Action catalog

Beta testing (Google Play)

The Play Store build is in closed testing — new testers are welcome.

  1. Join the tester group: nothing-modes-testers — anyone can join, no approval needed.
  2. Become a tester: open the opt-in link and tap Become a tester.
  3. Install the app from the Play Store listing.

Use the same Google account for all three steps — the one on your phone. If the opt-in page says you're not a tester right after joining the group, wait a few minutes and retry; membership can take a moment to reach Play. Feedback goes straight from the app: Settings → Feedback → Send feedback.

What it does

  • Modes — persistent or event-based automations (Sleep, Work, Gaming, or event triggers) with optional conditions, actions, and automatic state restoration.
  • WHEN / ONLY IF / THEN builder — explicit, no confusion about what runs when.
  • Nothing Glyph / Glyph Matrix — light stripe and matrix on supported devices.
  • Shizuku — optional, graceful degradation everywhere else.
  • Bluetooth reconnect — an action that turns the radio on and keeps paging a paired device until it connects, plus a "Reconnect watch" template that runs it whenever the device drops.
  • Capability detection — the app asks what the device can do instead of guessing.
  • Priority + cooldown + conflict resolution — deterministic ordering, overlap suppression, and fire cooldown.
  • Import / export / share — JSON bundles with schema versioning.
  • Privacy-first diagnostics — no analytics SDKs; crash reports are opt-in, and after a crash the app shows the error and asks before anything is sent.

Glyph support

Device Glyph Stripe Glyph Matrix Glyph Toy
Nothing Phone (1) Yes No No
Nothing Phone (2) Yes No No
Nothing Phone (2a) / (2a)+ Yes No No
Nothing Phone (3a) / (3a) Pro Yes No No
Nothing Phone (3) Yes Yes (25x25) Yes
Nothing Phone (4a) Yes No No
Nothing Phone (4a) Pro Yes Yes (13x13) Yes
Nothing Phone (4b) Yes No No
Non-Nothing devices No No No

How Glyph output works — read this first

Nothing OS hands the Glyph interface to one selected toy at a time. Whoever owns the current Glyph Toy slot (or the Always-on toy slot) is the only app whose frames reach the lights. There is no API to switch that selection programmatically — Nothing controls it.

What this means in practice:

  • To see Nothing Modes output, select Nothing Modes in Settings → Glyph Interface → Glyph Toys (or as the Always-on toy). The Glyph Preview screen in the app has shortcut buttons to both pickers and shows a live "Matrix owner" status.
  • We cannot trigger other apps' Glyph Toys. Toy apps can be bound and sent lifecycle messages, but their frames never reach the lights while another toy owns the slot — we verified this on-device. Nothing Modes renders its own equivalents (battery ring, progress, text, marquee, icons) instead.
  • If another toy is selected, Glyph actions fail honestly with "matrix owned by another toy" instead of pretending to render. Check the "Matrix owner" row in Settings → Glyph Preview — it always shows who currently controls the lights.

This exclusivity is Nothing's platform rule, not a limitation we chose. If Nothing ever exposes a public toy-switching API, we will use it.

Build

./gradlew assembleDebug
./gradlew :engine-core:test
./gradlew :ui:lintDebug

Requires JDK 17+ and Android SDK API 36.

Architecture

app
├── ui                 — Compose screens, theme, design primitives
├── automation-android — services, receivers, scheduler
│   ├── engine-core    — pure Kotlin engine
│   ├── data           — Room stores
│   ├── capabilities   — action executors, capability resolver
│   ├── core-shizuku   — Shizuku gateway
│   ├── device-tools   — shell-based state readers
│   └── nothing-integrations — Glyph SDK wrapper

The engine resolves each action through: Public Android API → Nothing API → Shizuku → settings panel fallback.

Modules

Module Role
engine-core Pure Kotlin automation engine
device-tools Shell-based device state readers
automation-android Android lifecycle, services, receivers
ui Jetpack Compose screens and design system
core-shizuku Shizuku privileged shell transport
capabilities Action executors and resolver
nothing-integrations Nothing Glyph SDK wrapper
data Room persistence
app Entry point and nav host

Quick start

  1. Install on Android 9+.
  2. Follow the in-app onboarding for restricted settings and optional Shizuku.
  3. Create a mode from the builder, a template, or a shared JSON link.
  4. Automations fire on triggers, check conditions, then execute actions in order.

Templates and sharing

Community templates live in templates/ — browse them in-app via the grid icon on the Modes screen. To contribute one, see templates/README.md.

Share any mode from the detail screen as a JSON bundle. Bundles carry schemaVersion, appVersion, and requiredCapabilities, so imports across users and app versions show compatibility warnings before anything is written.

Shizuku

Optional. Without it, every action still resolves — silent where the platform allows, a jump to the right settings panel where it doesn't. Shizuku turns the panel fallback into a silent toggle.

Verified on Nothing Phone 3, Nothing OS 5.0 (C5.0-260924-2115), Android 16:

Action Without Shizuku With Shizuku
Wi-Fi, mobile data, hotspot connectivity panel silent toggle (cmd wifi, cmd phone)
Airplane mode airplane settings silent toggle (cmd connectivity)
Battery saver, data saver, auto-sync settings panel silent toggle
Always-On Display, extra dim display settings silent toggle
Location mode settings panel silent toggle (secure table)
Refresh rate display settings silent toggle (system.peak_refresh_rate, float e.g. 120.1)
Nothing OS feature flags (nt_*/led_*) settings app silent toggle
Arbitrary WriteSetting permission-required silent toggle
NFC NFC panel NFC panel — svc nfc is killed on Nothing OS even for shell; platform limitation
Screenshot per-capture consent (MediaProjection) same
Everything else — Glyph, volume, ringer, DND, brightness, dark mode, rotation, flashlight, notifications, media, clipboard, app/URL launch, lock screen, SMS runtime permissions only unchanged

Nothing OS 5.0 notes:

  • svc data is gone — it exits 0 without changing anything, so exit codes alone can't be trusted. Every shell-backed toggle now reads the real state back after writing; a command that "succeeded" but changed nothing degrades to the settings panel instead of reporting a fake success. For mobile data the real state is mIsDataEnabled in dumpsys telephony.registry — global.mobile_data is a vestigial key that stays 1 either way; the per-sub mirror mobile_data<subId> still tracks.
  • svc wifi/svc bluetooth still answer but are undocumented; the executor uses the documented cmd wifi/cmd bluetooth_manager interfaces.
  • secure.peak_refresh_rate no longer carries Hz — it's a static mode id. The live ceiling is system.peak_refresh_rate/min_refresh_rate as a float (120.1).
  • Disabling mobile data from the Quick Settings/internet panel shows a new confirmation modal — Nothing's own UI. The shell path (cmd phone data) bypasses it entirely.

Get Shizuku from GitHub or the Play Store, then grant it inside the app's settings sheet.

Testing

./gradlew :engine-core:test
./gradlew connectedCheck

Documentation

License

GPL-3.0


Authored By: TDvorak [email protected]

Close

How Shizuku is used

Can toggle radios, hotspot, sync, display, privacy, Glyph and run custom shell commands via Shizuku with `sh -c`, `settings put` and `screencap`.

This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.

How this app uses Shizuku

Shizuku provides a privileged shell that lets modes and routines change protected system state directly on the device.

  • Toggle WiFi: turn WiFi on or off in automations with the cmd wifi shell command through Shizuku.
  • Toggle Bluetooth: turn Bluetooth on or off in automations with the cmd bluetooth_manager shell command through Shizuku.
  • Manage Bluetooth devices: connect a chosen paired device, plus disconnect a paired device or forget its bond through Shizuku.
  • Switch mobile data and NFC: turn mobile data on or off with the cmd phone data command and switch NFC with the svc nfc command through Shizuku.
  • Control airplane mode and hotspot: switch airplane mode with the cmd connectivity airplane-mode command and turn the WiFi hotspot on or off through the system tethering service through Shizuku.
  • Control sync and savers: turn auto sync, battery saver, data saver and stay awake while charging on or off through Shizuku.
  • Write custom settings: write a chosen system, secure or global setting key and value with the settings put command through Shizuku for custom setting actions.
  • Adjust display and appearance: change refresh rate, always on display, extra dim, font scale, Night Light, color inversion, color correction and one handed mode with settings put writes through Shizuku.
  • Manage location and privacy: change location mode and block or unblock the microphone and camera with settings put and the cmd sensor_privacy command through Shizuku.
  • Control Glyph lights: turn the Nothing Glyph interface master switch on or off device wide with a global settings put write through Shizuku.
  • Capture screen: take a screenshot for screenshot actions with the screencap command through Shizuku.
  • Run custom commands: run a shell command typed in the action with sh -c through Shizuku, plus end the active call, force stop a chosen app and expand the notification shade with input keyevent, am force-stop and cmd statusbar commands.

Android APIs or commands used

  • cmd wifi set-wifi-enabled
  • svc wifi enable/disable
  • cmd bluetooth_manager enable/disable
  • svc bluetooth enable/disable
  • BluetoothDevice.connect
  • BluetoothDevice.disconnect
  • BluetoothDevice.removeBond
  • cmd phone data enable/disable
  • svc data enable/disable
  • svc nfc enable/disable
  • cmd connectivity airplane-mode
  • android.net.ITetheringConnector.startTethering
  • android.net.ITetheringConnector.stopTethering
  • WifiManager.startTetheredHotspot
  • WifiManager.stopSoftAp
  • ContentResolver.setMasterSyncAutomatically
  • settings put
  • settings get
  • cmd netpolicy set restrict-background
  • cmd netpolicy get restrict-background
  • cmd sensor_privacy
  • sh -c
  • screencap -p
  • dumpsys telephony.registry
  • input keyevent
  • am force-stop
  • cmd statusbar expand-notifications

Notable details

Many toggles try a normal Android API first and open the matching system settings page when Shizuku is unavailable, so the action can be finished manually. Custom setting writes accept any system, secure or global key that passes shape checks, with no fixed allowlist.

Close

Changelog

What's new for version 0.19.21

What's Changed

Full Changelog: https://github.com/Dvorinka/Nothing_Modes/compare/v0.19.20...v0.19.21

What's Changed

Full Changelog: https://github.com/Dvorinka/Nothing_Modes/compare/v0.19.20...v0.19.21

Close

Permissions

39 permissions requested

  • android.permission.REQUEST_INSTALL_PACKAGES
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.SCHEDULE_EXACT_ALARM
  • com.android.alarm.permission.SET_ALARM
  • android.permission.FOREGROUND_SERVICE
  • android.permission.FOREGROUND_SERVICE_SPECIAL_USE
  • android.permission.POST_NOTIFICATIONS
  • android.permission.WRITE_SETTINGS
  • android.permission.ACCESS_NOTIFICATION_POLICY
  • android.permission.CAMERA
  • android.permission.READ_CALENDAR
  • android.permission.READ_CONTACTS
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • android.permission.SET_WALLPAPER
  • android.permission.SYSTEM_ALERT_WINDOW
  • android.permission.INTERNET
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.RECORD_AUDIO
  • android.permission.MODIFY_AUDIO_SETTINGS
  • com.nothing.ketchum.permission.QUERY_GLYPH_STATE
  • com.nothing.ketchum.permission.CONTROL_GLYPH
  • com.nothing.ketchum.permission.ENABLE
  • android.permission.ACCESS_FINE_LOCATION
  • android.permission.ACCESS_COARSE_LOCATION
  • android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION
  • android.permission.USE_FULL_SCREEN_INTENT
  • android.permission.READ_PHONE_STATE
  • android.permission.READ_CALL_LOG
  • android.permission.RECEIVE_SMS
  • android.permission.ACCESS_WIFI_STATE
  • android.permission.BLUETOOTH
  • android.permission.BLUETOOTH_CONNECT
  • android.permission.BLUETOOTH_SCAN
  • android.permission.PACKAGE_USAGE_STATS
  • android.permission.ACCESS_BACKGROUND_LOCATION
  • android.permission.SEND_SMS
  • moe.shizuku.manager.permission.API_V23
  • com.tdvorak.nothingmodes.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
Close