An Android profile isn’t a browser’s mobile mode — it’s a real Android image running in an emulator on your computer. One profile is one device with its own identifiers, and its state syncs just like a regular profile.
Model and identifiers
The model is picked from real-world data: screen, system, build, memory and device fingerprint are filled in automatically. Each profile gets its own IMEI, Android ID and serial number — they are created on first launch and can be regenerated with one click.
Geo, carrier and network
Carrier, language and time zone follow the proxy’s country and IP. GPS coordinates come from the proxy or you set your own on a map. Network type ranges from 5G down to GPRS, with signal strength.
Camera, sensors and battery
- The rear and front cameras show the emulator’s room, an image or video from a file, or your computer’s webcam.
- Device posture — on a table, in hand, upright or custom; sensors include accelerometer, gyroscope, light, proximity and shake.
- Battery level and charging — over USB or wireless.
- APKs install just like on a regular phone.
A proxy for the whole device
The proxy applies to the whole device, not to a single app. The emulator’s internal network is 10.0.2.x and the external IP is the proxy’s address. Time zone, language and geolocation follow that IP.
How much to download
The first download is 181–213 MB, later ones are 52 MB: profiles on the same image version share a common base, so each new one loads faster and takes less space.
Where emulation hits its limits
Play Integrity and SafetyNet don’t pass, and attestation is not faked. That means banking apps, Google Pay and some marketplaces don’t work on Android profiles. These profiles are labeled as emulated in the interface — keep that in mind before choosing a use case.