Skip to content

Setup troubleshooting

Problems when setting up a Test Node or connecting phones, and what to check. For problems when a test suite starts, see Troubleshooting Test Suite Startup.

The installer command does not work

  • The command expired or was already used. A command works once and expires 30 minutes after it was created. Open Agent Installer for the Test Node again and click Regenerate.
  • The installation stopped at a step. Run a new command in the same directory: the installer shows the step that failed and offers a fresh installation. See Running the installer again.
  • Linux: the prerequisites check fails. The installer needs a 64-bit Intel/AMD PC with a Debian or Ubuntu based Linux, because it uses apt-get. See the requirements.

The Test Node is not online

  1. Check that the computer is awake and connected to the internet. On a Mac, sleep must be turned off (see Configure Sleep Settings).
  2. An Admin user can restart the agent from the Web UI: Test Nodes → select the node → ⋮ → Restart Agent.
  3. On Linux you can also restart the service with sudo systemctl restart tmsagent. On a Mac, restart the computer.
  4. Was an installer command of this Test Node run on another computer, or run again with the -c option? Each command gives the node a new credential, so the agent that was already running loses its connection. Run a new installer command on the node's own computer.
  5. Do not delete or edit node-identity.json in the QuadATFAgent folder: it is the node's credential.

If the node still does not come online, send the log files quadatflog-*.log from the QuadATFAgent folder to support@quadified.com.

The phone does not appear in Mobile ID's

  • The Test Node is not online. See above.
  • The cable or hub. Use a data-capable cable (not a charge-only cable) and a hub with its own power supply. Try another cable or port.
  • Android: USB debugging. Check that Developer options and USB debugging are on, then unplug and reconnect the phone. When Allow USB debugging appears, select Always allow from this computer and tap OK. If you tapped Cancel, reconnect the cable to see the prompt again.
  • Xiaomi: an active SIM card must be inserted and the phone signed in with a Xiaomi account, otherwise USB debugging (Security settings) cannot be turned on.
  • iPhone: tap Trust in the Trust This Computer? alert and turn on Developer Mode (see iOS). iPhones are supported on Mac Test Nodes, and only when iPhone support is not turned off on the node (ATF_IOS_MODE, see Advanced node settings).
  • The model or OS version is not supported. A phone is registered only when its brand and major OS version are listed in Supported devices; otherwise nothing is created and no message is shown. See Why doesn't my phone appear?
  • It is an MCM modem. Modems are never discovered automatically: add the Mobile ID by hand (see MCM modem setup).

Developer Mode is missing on the iPhone

Developer Mode appears in Settings > Privacy & Security only after the iPhone has been paired with the Mac. Connect it by cable, unlock it and tap Trust. If you tapped Don't Trust earlier, go to Settings > General > Transfer or Reset iPhone > Reset > Reset Location & Privacy and reconnect the cable.

Prepare reports failed steps

The result email lists every step with OK or Failed. Do the failed steps by hand on the brand page (Samsung, Xiaomi, Pixel); What Prepare does tells which step each name in the email stands for. On Samsung, Prepare cannot change the screen lock while a PIN, pattern or password is set: remove it by hand first.

Tests fail on a newly connected phone

  • The Mobile ID still has placeholder values. IMSI and IMEI start with random values, and the MSISDN may be a +00000… placeholder. Enter the real values and the National Format (see Edit a Mobile ID).
  • Xiaomi: the automation cannot control the phone. Turn on Install via USB and USB debugging (Security settings) in Developer options: without them the automation cannot install its helper apps or send input to the phone.
  • The screen locks during the test. Turn on Stay awake (Xiaomi: Keep screen on) and remove the screen lock. On Xiaomi and Pixel, Prepare does not change the screen lock. On an iPhone, turn the passcode off and set Auto-Lock to Never (see iOS).
  • The Test Node lost access to the phone after some days. Turn on Disable adb authorization timeout in Developer options; otherwise Android revokes the USB debugging authorization after 7 days without a connection.
  • SMS or MMS tests fail. Check the messages settings on the brand page: RCS chats off and MMS download on (Android); iMessage and RCS Messaging off, MMS Messaging on (iPhone).
  • Incoming calls or messages are not seen on iOS 26 and later. Set Screen Unknown Callers to Never and turn off Screen Unknown Senders (see iOS).
  • Call forwarding tests fail. Remove old call forwarding with ##002#; Prepare erases only unconditional forwarding.