Set up the Android phone, step by step

The one-time part: turn on Developer options, switch on Wireless debugging and type a six-digit code into iTell's notification. About five minutes, with pictures.

Before you start

  • iTell installed on the Android phone (see Download).
  • The phone connected to Wi-Fi, not only mobile data.
  • Your screen lock PIN or pattern, in case Android asks for it.

iTell walks you there

In iTell's setup, the “Developer options” step has an Open button and the “Pair with Wireless debugging” step has a Start button. They open the right Settings page for you. This page is for when you want to see what's coming, or you're stuck.

Screens are from an Android 13 phone. Colors and some names differ on yours; the order is the same.

Part 1 · Developer options

Hidden by default. Android shows them after you tap one line seven times. You do this once.

1

Open Settings, then About phone

Scroll to the bottom of Settings and tap About phone. On some phones it's called About device.

Open Settings, then About phone
2

Tap Build number seven times

Scroll to the very bottom and tap Build number quickly, seven times. Android may ask for your screen lock. A short message says you're now a developer.

Can't find it? On Samsung and Xiaomi it sits one level deeper. See the table below.
Tap Build number seven times
3

Open Developer options

Go back to Settings, tap System, then Developer options. The switch at the top, “Use developer options”, must be on.

Some phones keep it elsewhere (Samsung: right in the main Settings list). The table below has the common ones.
Open Developer options
Open Developer options

Part 2 · Wireless debugging and the code

This is the tricky part, so we've cut it into small steps. Take them one at a time and don't close the code window.

4

Switch on Wireless debugging

Make sure you're on Wi-Fi. Scroll down to the Debugging section and switch on Wireless debugging. If Android asks “Allow wireless debugging on this network?”, tick “Always allow on this network” and tap Allow.

That question only appears on a new Wi-Fi network. USB debugging can stay off. iTell's Start button opens this page with the Wireless debugging row highlighted.
Switch on Wireless debugging
5

Tap the words “Wireless debugging”

Tap the name, not the switch. A page opens with the device name and a few options.

Tapping the switch only turns it off and on.
Tap the words “Wireless debugging”
6

Tap “Pair device with pairing code”

Not the QR code one. It's right below.

Tap “Pair device with pairing code”
7

Read the six-digit code and leave the window open

A window shows a Wi-Fi pairing code. Don't tap Cancel and don't press Back: it has to stay open for the next step. The code works only while the window is open.

Every time the window opens, the code is new.
Read the six-digit code and leave the window open
8

Type the code into iTell's notification

Swipe down from the top of the screen. iTell's notification “Type the pairing code” has a field: type the six digits and tap Pair. The code window stays open underneath.

No notification? Allow notifications for iTell in Settings → Apps → iTell → Notifications.
Illustration of the notification, not a screenshot.
9

Wait for “Paired”

In a few seconds the notification changes to “Paired” and iTell starts the call-audio helper. You can close Settings. Leave Wireless debugging on.

After a restart, iTell switches it on again by itself as soon as the phone reaches Wi-Fi.
Illustration of the notification, not a screenshot.

Where things are on your phone

Names move around between makers. If you get lost, search Settings for “Build number” or “Developer options”.

PhoneBuild numberDeveloper options
Pixel, Motorola, Nothing, most stock AndroidSettings → About phone → Build numberSettings → System → Developer options
SamsungSettings → About phone → Software information → Build numberSettings → Developer options (bottom of the main list)
Xiaomi, Redmi, POCOSettings → About phone → tap OS version (or MIUI version)Settings → Additional settings → Developer options
OnePlus, OPPO, RealmeSettings → About device → Version → Build numberSettings → Additional settings (or System & updates) → Developer options

Why does iTell need this?

Android doesn't let ordinary apps near the sound of a phone call. Wireless debugging is Android's own way to hand a small helper that permission, and only after you type a code shown on your own screen. You do it once. No computer, no cable, and the pairing never leaves the phone.

If something's off

I can't find Developer options

Tap Build number seven times first (steps 1 and 2). Then look for Developer options under System, Additional settings, or at the bottom of the main list. Searching Settings for “Developer” is quicker.

Wireless debugging is greyed out or switches itself off

It needs Wi-Fi. Connect to a Wi-Fi network (mobile data alone isn't enough) and try again. Turning Wi-Fi off and on once often fixes it.

iTell says the pairing window isn't open

Tap “Pair device with pairing code” again and type the new code. You can't pair with a closed window, and every window has its own code.

It says the code was wrong

Type the six digits from the window that's open right now. If you opened it twice, the older code is dead. Digits from any keyboard work.

The notification has nowhere to type

Pull the notification all the way down and tap Pair; the field opens. If there's no iTell notification at all, allow notifications for iTell in Settings → Apps.

Should I turn Wireless debugging off afterwards?

No, leave it on. Turning it off can stop the call-audio helper. After a restart, iTell switches it on by itself once the phone is on Wi-Fi.

Will I have to do this again?

Not after a restart or an update. Only if you uninstall iTell, remove its entry under Paired devices, or reset the phone.

All paired?

Back in the app, setup shows a tick and then the QR code for your iPhone.

Back to download