← back to blog

Setting Up A Cloud Phone From First Boot

The device shows up in the dashboard, you click connect, and a home screen appears in a browser tab. It’s a real Android phone sitting in a rack somewhere, and for the next hour almost everything you do to it will stick. The language you pick, the account you sign in first, the permissions you grant on the first app launch, the device name it broadcasts. Most of those are easy to get right and tedious to fix later, and a few of them can’t really be undone at all from the platform’s side.

So this is the first hour, in order. It assumes you’ve already decided a cloud phone is the right tool for the account, which is its own question with its own trade-offs. This piece starts after that decision, at the moment the screen lights up.

Decide what this phone is before you touch it

Before the first tap, write down what the device is for. One line is enough, but it has to exist somewhere other than your head.

Which account or identity will live on this phone. Which platform. Which country and city the account claims. Which language it uses. Which phone number it’s verified with, if any. Whether it needs a Google account at all.

This sounds like paperwork. It’s the thing that stops you from making a quiet contradiction twenty minutes in, when you’re in the settings menu and have to choose a region and your hand picks the one you always pick. It also becomes the record you’ll need later, when a platform asks a verification question or when a teammate needs to know which phone holds which account.

The core rule is one phone, one identity. Not one phone per platform with several identities spread across the apps. The device, its network, its system settings and the account on it should all describe one person. If you catch yourself planning to put a second identity on the same device because it has spare capacity, stop and rent another device. Spare capacity is the most expensive thing a fleet ever uses, because it’s how two accounts end up sharing a device fingerprint, an IP history and a notification log.

Keep the sheet next to the session. You’ll check it at least five times before the hour is out.

Check what you’ve been handed

A rented phone should arrive clean. Check anyway, before you install or sign in to anything, because the cost of looking is a couple of minutes and the cost of not looking is inheriting someone else’s history.

Open Settings and look at Accounts. There should be nothing signed in, or only what the provider documents. Open the contacts app, the gallery, the downloads folder and the messages app. All empty. Look at the installed apps list and compare it with what a stock phone of that model ships with. A leftover platform app from a previous renter, still logged in, is exactly the kind of thing you want to catch now.

Check the Android version and security patch date under About phone. You’re not looking for the newest possible version. You’re looking for something plausible for that model and not years out of date, because an ancient patch level on a popular app’s user base is a little unusual, and it also means real security exposure.

Look at the device name, also under About phone. Some phones default to the model name, some to a name a previous owner set. That name is broadcast over Bluetooth and sometimes shown to other devices on the same network, so it’s worth making neutral before anything else.

If anything looks wrong, don’t fix it yourself by factory resetting. Tell the provider. A reset on hosted hardware can break the provider’s remote control or management setup, and a good provider will want to know their wipe process missed something.

Network first, before any account

The single most important thing to get right before any account touches the phone is where its traffic exits. Accounts remember the first IP they saw, and so do the risk systems behind them.

Find out how the phone reaches the internet. On a real hosted handset it’s usually one of three setups: its own SIM on mobile data, a Wi-Fi connection through the provider’s network, or a proxy configured on the device or upstream of it. Each gives a different exit address, and you need to know which one your account will see.

Then check it from the phone itself. Open the browser and load an IP lookup page. Note the address, the network that owns it and the location it reports. It should match the sheet: a mobile carrier in the right country if you’re relying on a mobile exit, and a location consistent with the account’s claimed home.

Do the check twice, a few minutes apart. On a mobile connection the address may change, which is normal for carrier networks, but the owning network and country shouldn’t jump around.

If a proxy is involved, test for leaks while you’re in the browser. A leak check page will show whether any request, including WebRTC, reveals a different address. If the phone exits one way for the browser and another way for apps, you’ll find out later in the worst possible way. Our proxy leaks guide goes through the checks in detail.

Don’t open the platform app until this matches. If you open it once on the wrong network, that first contact is already on record.

The settings that say where the phone lives

Next, the system settings that describe where the phone lives. These get read by apps constantly and quietly, and they need to agree with the network you just checked.

Set the system language to what the account’s person would use. Set the region or country to match. If the phone lets you add secondary languages, add only ones that fit the persona. A Singapore persona with English and Chinese is ordinary. A Singapore persona with English, Portuguese and Turkish needs a story.

Time zone is the one people get wrong most. On a real SIM with mobile data, automatic time zone from the network usually works and is the most natural setting. If the phone has no SIM and exits through a proxy, automatic may pick up the data centre’s zone or stay on whatever it was set to. In that case set it manually to the account’s zone and confirm the clock is right.

The keyboard matters more than it looks. The default keyboard app records which languages are enabled, and some keyboards sync learned words and settings to a cloud account. Enable only the persona’s languages. If the keyboard offers to sign in or sync, decline. A keyboard synced across ten phones shares a dictionary, and a shared dictionary is a strange thing for ten strangers to have.

Date and number formats usually follow the region. Leave them on the default for that region rather than tweaking them. Unusual choices are distinctive, and distinctive is what you’re trying to avoid.

When you’re done, the system should describe one place. Network, language, region, time zone and keyboard all telling the same story.

The Google account question

Most Android work eventually runs into the Google account. The Play Store needs one to install apps, several platforms offer Google sign-in, and many system features assume one exists.

First ask whether this phone needs one. If the platform app can be installed another way that the provider supports, and the account doesn’t use Google sign-in, running without a Google account is a legitimate choice. Plenty of people use phones that way. You lose convenience, mainly automatic app updates through the Play Store, and you gain one fewer account linking things together.

If it does need one, the Google account belongs to this phone’s identity and nothing else. Never your personal Google account, not even for five minutes to install an app. Never a Google account shared across the fleet to save time. Signing one account into many phones is one of the fastest ways to tie them together, because that account syncs contacts, app lists, backups and more across every device it touches.

When you sign it in, go straight to the sync settings. Turn off contacts sync unless the work needs it. Think about backup. A backup of this phone restored onto another device later would carry this identity’s data across, so for most fleet phones I’d leave device backup off and keep the record of what’s installed on the sheet instead.

Look at location history and web activity settings too. They exist to build a profile of where the device goes and what it does. For a hosted phone that never moves, they have little value and add one more store of data tied to the account.

Permissions baseline before the first app

Before installing the platform app, set the phone’s defaults so that the first app launch doesn’t quietly open things up.

Location is the big one. If the account doesn’t need location for its work, turn location services off at the system level, or at least set it so apps must ask. If it does need location, make sure it reports a place consistent with the network and the time zone. Don’t use mock location tools to fake it. Mock location is a developer setting, apps can see when it’s in use, and it’s one of the signals platforms treat as a tell.

Turn off Wi-Fi scanning and Bluetooth scanning in the location settings unless you need them. These let the phone look for nearby networks and devices even when Wi-Fi or Bluetooth are switched off, which is useful for location accuracy and also a way for apps with location permission to see what’s physically around the phone.

Contacts should stay empty and denied. Nearby devices permission should be denied for anything that doesn’t need it. Notifications can be allowed for the platform app, since a real user would usually have them on.

Check the default apps too. The default browser, keyboard and launcher shape what the phone looks like from inside. Leave them on the stock options for the model rather than installing replacements. A stock phone is the most common kind of phone there is.

Install only what the job needs

This is where hosted phones most often go wrong: people treat them like a personal device and fill them up.

Install the platform app the account needs, from the official store or the channel the provider supports. Then, mostly, stop. Every extra app is another thing reading device information, requesting permissions, sending analytics and building its own profile of the phone. Some of those SDKs are shared across many apps and report to the same third parties, so an extra app can connect the phone to more data than you’d guess.

Some categories deserve a hard no. Cleaner and booster apps, which often want broad permissions and do little. VPN apps on a phone that’s supposed to exit through its carrier or a configured proxy, because a VPN changes the network story in ways that contradict everything you checked. Automation and accessibility tools, which platforms can often detect and which don’t belong on a phone meant to look like an ordinary person’s. Any app that promises to change the device ID, model or other identifiers. And any APK from a forum or a file-sharing link.

A few small ordinary apps are fine if they fit the persona and you’ll actually use them, like a weather app or a note app. The goal is a phone that looks lived in by one person, not a phone that looks like a testing bench.

Never install another identity’s platform app on this device. If a teammate needs a second account on the same platform, that’s a second phone.

First launch of the platform app

Now open the app. Take it slowly.

If you’re creating a new account, go through sign-up with the details from the sheet, nothing improvised. The name, the date of birth, the number, the email. Anything you type now becomes part of the account’s permanent record, and inventing it on the spot is how accounts end up with a birth year that doesn’t match a later ID check.

If you’re moving an existing account onto the phone, expect a security check. A login from a new device is normal and platforms handle it all the time, but they’ll often ask for a code, a password confirmation or a selfie check. Have the recovery details ready before you start. Our guide to moving an account to a new setup covers the migration side, including why you shouldn’t log in from the old and new devices in the same hour.

Read every onboarding screen. Find-your-friends screens, contact import, location prompts, notification prompts and cross-app offers to connect other accounts. Decline anything that uploads data you’d rather not hand over, especially contacts. Accept notifications. Skip anything that links this account to another service you haven’t planned for.

Then leave the app alone for a bit. Scroll, look at a few things, close it. The first session of a new device on an account should look like a person getting familiar with a new phone, which is exactly what it is.

Two-factor and recovery, set up once and written down

Once the account is working on the phone, set up its security, because a cloud phone introduces one extra risk. You don’t physically hold it.

If the platform supports an authenticator app, decide where the authenticator lives. Putting it on the same cloud phone is convenient, but it means losing access to the device also locks you out of the second factor. Keeping it in a separate, secured place that you control is usually safer. Many operators use a password manager or a dedicated authenticator device and store the setup key there.

If the platform uses SMS for two-factor, the number matters. If the phone has its own SIM, codes arrive on the device. If it doesn’t, they arrive wherever the number lives, and you need to be sure that number stays active for as long as the account does. A lapsed number is one of the most common ways operators lose an account they otherwise did everything right with.

Save the recovery codes the platform offers. Store them against the account in your records, not in a note on the phone.

Write down what you set up: which two-factor method, where the backup is, which email is the recovery address. When something goes wrong in six months, the person fixing it will need that record more than anything else, and that person may be you, half-asleep, having forgotten everything about this particular phone.

Things to leave alone

Some settings and tools look useful and should stay untouched on a fleet phone.

Developer options. Enabling them is harmless in itself, but apps can check whether they’re on, and several of the settings inside them, USB debugging and mock location above all, are signals platforms associate with automation and tampering. On a hosted device, the provider may need some of these for remote control, so leave their configuration to the provider and don’t add to it.

Rooting and framework mods, along with custom recoveries. These break integrity checks that many apps now rely on, and they’re hard to hide. The whole value of a real hosted handset is that it passes as a normal phone because it is one.

Factory reset. On hosted hardware it can wipe the provider’s management setup and leave the device unreachable, and it doesn’t remove whatever the platform already recorded about the device on its side. If you think a phone is compromised or dirty, talk to the provider.

Device identifier changers. Apps that promise a new Android ID, a new model name or a new IMEI are either doing nothing or doing something that looks like tampering. An identity that’s supposed to be stable shouldn’t have its device identity shifting under it.

System update postponement is a judgement call. Take updates when they come on a normal schedule, the way a real user would. A phone that stays on a years-old patch indefinitely is unusual.

Screen lock, notifications and the lived-in look

A real phone has habits. It’s worth giving a hosted one a few of them, lightly, because blank defaults on every setting can look like a device nobody uses.

Set a screen lock PIN. Real phones have one, and some platform features, like secure payments or certain verification flows, expect a locked device. Record the PIN on the sheet, since you’re not the only person who might need to open this device.

Leave notifications on for the platform app. Let the phone receive them. If the account gets messages and the phone never shows them as delivered or read for weeks, that’s a small oddity.

Set a wallpaper if you like. It doesn’t matter much to detection, but it helps you and your team tell phones apart at a glance in a dashboard full of identical home screens, which cuts down on the far more serious mistake of doing something to the wrong device.

Keep storage modest and tidy. A few photos taken or saved as part of normal use are fine. A gallery full of downloaded images that also appear on other fleet phones is a content link between them.

Don’t overthink the lived-in look. The goal is ordinary, which usually means leaving defaults alone and letting normal use accumulate. A phone doesn’t need a fabricated history. It needs to avoid looking like a freshly unboxed test device on every single visit.

Setting up ten phones without making them identical

Most operators don’t set up one phone. They set up a batch, and batching creates its own pattern.

If you run the same checklist on ten phones in the same afternoon, the risk is that the phones come out identical in ways real phones never are. Same wallpaper, same handful of extra apps installed in the same order, same keyboard settings, same notification choices, the platform app installed within the same fifteen minutes on every device. Each phone looks ordinary on its own. Side by side, they look like a production line.

The checklist should be identical. The results shouldn’t be. Where a choice is about consistency with the persona, like language, region and time zone, follow the sheet, and the sheets will differ because the personas differ. Where a choice is cosmetic or optional, let it vary naturally. One phone gets a weather app, another doesn’t. Wallpapers differ. Some personas keep the stock launcher layout, some move a few icons.

Timing matters as much as content. Installing the platform app and creating accounts on ten devices within minutes of each other puts ten new account events close together, often through exits in the same area. Spread the account step out across days where you can. Do the device preparation in a batch if that’s efficient, then bring accounts onto the phones one or two at a time.

Don’t copy settings between phones with a backup or a cloning tool to save time. That’s the fastest way to produce identical devices, and it can carry across data you didn’t mean to move.

The honest trade-off is speed. Staggering a batch of phones over a week is slower than doing them all at once. It’s also the difference between ten accounts and one account wearing ten devices.

When the provider manages part of the stack

On a hosted phone, you don’t control everything, and it’s worth knowing where the line sits before you start changing things.

Most providers manage the physical layer: power, cabling, cooling, the connection that lets you see and control the screen remotely. Many also manage the network path, whether that’s a SIM plan, a Wi-Fi network or an upstream proxy. Some lock certain system settings so renters can’t break remote access, and some run a management app on the device for that purpose.

Read what the provider documents about this before the first session. If a management app is present, don’t try to remove it. If developer settings are needed for the remote connection, don’t turn them off to look cleaner, because you may lose the device. If the provider controls the network, ask how the exit is assigned and whether it can change without notice, since a surprise change in the exit country is the kind of thing that triggers a security check on the account.

Ask, too, what happens between renters. How the device is wiped, whether Google accounts are removed, whether the device keeps the same hardware identity. A careful provider will answer plainly.

The division is healthy. The provider keeps the device reachable and clean, and you keep the identity on it consistent. Problems start when either side quietly does the other’s job, like a renter factory resetting a device or a provider changing a network setting without telling anyone.

Record the device before you close the tab

Before you end the first session, update your records. This is the step people skip when they’re tired, and it’s the one that pays back most.

For each phone, keep one row with the device identifier the provider uses, the account on it, the platform, the phone number, the Google account if any, the network setup and exit you verified, the language, region and time zone, the two-factor method and where its backup is, the screen PIN, the date of setup and who did it.

That row is how you avoid the mistakes that actually kill fleets. Logging into the wrong account on the wrong phone. Reusing a number because nobody remembered it was taken. Moving an account and forgetting where its two-factor lives. Assigning a device to a new person without knowing what was on it.

Keep the records outside the phones and outside the accounts, in a system your team can reach. A spreadsheet is enough for a small fleet. Just make sure it’s not the kind of single document that would link every identity together if it leaked, which means access control and some thought about who can see what.

The record also lets you do a quick consistency check. If two rows share a Google account, a number or an exit IP that they shouldn’t, the spreadsheet will show you before a platform does.

The first week, not just the first hour

The setup is done. The account now has a device, a network, a consistent set of system settings and a clean install. What it doesn’t have is a history.

The first week on a new device should be quiet. Short sessions, ordinary browsing inside the app, nothing that looks like work at volume. If the account is new, this is the start of its warm-up, and the warm-up playbook covers the pace in detail. If the account is existing and just moved, the platform is watching to see whether the new device behaves like the old one’s owner. Keep your habits consistent with how the account was used before.

Watch for friction. Extra verification prompts, captchas, features that suddenly need confirmation, or a login that asks for a code every time. A little is normal after a move. A lot, or friction that grows over the week, means something in the setup contradicts itself. Go back to the sheet and check each layer again: exit IP and its owner, then time zone and language, then signed-in accounts and permissions.

Resist changes during this week. If you change the network, the language and an app setting all at once because something felt off, you won’t know which change helped or hurt. Change one thing, wait, look.

What a good setup can and can’t do

A careful first hour gives the account the best starting position a device can give it. The phone is real, it describes one person in one place, it isn’t sharing anything with other accounts and it isn’t carrying anyone else’s leftovers. That removes the device and network layers as reasons for the platform to doubt the account.

It doesn’t make the account safe by itself. Platforms also judge behaviour and content, plus relationships and history. An account that posts the same thing as ten others, messages strangers at volume or shares recovery details with its siblings will get linked or limited no matter how clean the phone is. And platforms change what they check. Anything you set up today is a starting position, not a guarantee.

What I’d say with confidence is that the mistakes of the first hour are the most avoidable ones in the whole stack, and they tend to be permanent. An account that first touched the platform through the wrong IP, or signed in alongside a shared Google account, carries that into its history. Spending an unhurried hour here is cheap. Fixing it later mostly isn’t possible.

I run cloud phone farms on real handsets in Singapore myself, and this is close to the checklist our own devices go through before an account ever touches them. For the rest of the stack, from choosing a phone over a browser profile to warming accounts up afterwards, head to the Multi Account Ops home page.

Get new guides and videos first — join the Telegram channel.

need infra for this today?