Android developer switches, on the phone.

Mock a location, walk a route, keep the screen on, flip developer options, inspect any installed app, fire a deep link, read the device. Every tool runs on the device itself.

Get it on Google Play See what it does
  • No account
  • No analytics
  • No backend
  • No ads

Features

Each tool has its own screen, most have a Quick Settings tile, and the long-running ones keep working after you switch to the app you are testing.

Keep screen awake

The display stays on after you switch to the app under test. Auto-off timer, only while charging, stop with the power button, and a notification with Stop and +30 min.

Mock location

Drop a pin, search a place, or reuse a saved one, and every app on the phone sees that position. Survives a reboot.

Route mode

Walk a test position between two points at a chosen speed, with live heading. Pause and resume from a floating control.

App inspector

Every installed package, user or system. Version, SDK targets, signing fingerprints, permissions, exported entry points you can launch, and a paste-ready summary.

Deep link tester

Type any link, see which app claims it, fire it. A searchable history keeps every attempt and its result.

Device

Twenty-six live fields across system, screen, hardware and battery. Copy or share as text. No permission needed.

Developer mode

Twenty-one switches from Developer options, grouped and searchable: show taps, pointer location, don't keep activities, wireless debugging, animation scale, and more.

needs adb setup

Display tuning

System text size from 50% to 200% with a live preview, from the screen, a Quick Settings tile, or a floating control over any app.

needs adb setup

Locale tester

Run one app in another language, right-to-left languages included, without changing the phone. Android 13 and up.

needs adb setup

The one-time adb setup

Two tools need a permission that Android only hands out over adb. Each one has its own permission and its own command, and they are independent: set up only the tool you use. Everything else in the app works straight after install.

Before either command

  1. Install adb on your computer. It ships with Android Studio, or on its own as Android SDK Platform Tools for Windows, macOS and Linux.
  2. Turn on Developer options on the phone. Settings, About phone, tap Build number seven times. Then in Developer options turn on USB debugging.
  3. Connect the phone by USB. The phone asks "Allow USB debugging?". Tap Allow. Wireless debugging works too, once paired.

Developer switches and Display tuning

Permission WRITE_SECURE_SETTINGS. Lets the app change developer options and the system text size. Without it, the switches still show their live state; only changing them needs it. Run adb devices to confirm the phone is connected, then the grant command.

Developer switches and Display tuning
$ adb devices
List of devices attached
R58N30XXXXX    device
# your phone is listed with "device" next to it: connected and allowed

$ adb shell pm grant com.kodeelite.devswitch android.permission.WRITE_SECURE_SETTINGS
# no output means it worked
# more than one device listed? add -s and its serial: adb -s R58N30XXXXX shell pm grant ...

Locale tester

Permission CHANGE_CONFIGURATION. Lets the app set another language for one app you pick. Only needed if you use the locale tester. Same two steps: confirm the phone, then the grant command.

Locale tester
$ adb devices
List of devices attached
R58N30XXXXX    device
# your phone is listed with "device" next to it: connected and allowed

$ adb shell pm grant com.kodeelite.devswitch android.permission.CHANGE_CONFIGURATION
# no output means it worked
# more than one device listed? add -s and its serial: adb -s R58N30XXXXX shell pm grant ...

After running a command

  1. Check in the app. The permission row on that tool's screen shows Granted, and the switches work with a tap.
  2. It stays. The permission survives app updates. It is removed by uninstalling, or by running the same command with revoke in place of grant.

The app shows these same commands on the screen that needs them, so you can copy them from the phone. It never asks for these permissions silently.

Nothing leaves the phone. No account, no analytics, no server. The only network requests are map tiles and place names while you use the map. Read the privacy policy.