Mobyx Devices & browsers

#Three kinds of device, one page

Device Center holds everything mobyx can drive. Phones are your real devices over USB, Wi-Fi or the internet. Mobyx Devices are full Android virtual machines that live inside mobyx. Browsers are just a browser, for work that never needs a phone.

#Mobyx Devices

A Mobyx Device is a complete Android phone running on your PC: its own apps, files, settings and a Virtual SIM that can receive SMS and calls. Create one with + New Device.

Lite is the preset to use. It runs Android 12 without Google services and, measured while idle, uses about 2.6 GB of memory and 1% of the processor. The Google Play presets run the newest Android, which reserves at least 4 GB however low you set it, and whose Play Store and Google services keep working in the background -- on an ordinary PC that is enough to make everything feel slow.

The first Lite device asks to download its Android image (about 626 MB, from Google's own repository, checked against Google's published checksum). You do not need Android Studio, and mobyx never touches emulators you made there.

Stopping a device saves its state, so starting it again takes about half a minute instead of a couple of minutes. Devices run at below-normal priority, so a busy phone cannot freeze your desktop.

#How many Mobyx Devices fit

Android needs at least 2 GB of memory per device, and a device that has been running a while holds about 3 GB (measured). That is a limit of Android's emulator, not of mobyx: it refuses a smaller setting. As a guide, a 16 GB PC runs 2 to 3 devices comfortably, 32 GB about 8, 64 GB about 18.

mobyx checks free memory before it starts a device and says plainly when there is not enough, instead of letting Windows slow to a crawl. Start All starts as many as fit and names the rest. For many more identities on a small PC, use browser profiles: they cost about 350 MB each.

#Browsers, and where they run

On this PC gives an isolated browser profile: its own cookies, storage, cache and history, ready in about a second. Two of them can be signed into the same site as different people at the same time. Choose an Android phone in the Screen list and it presents itself as that phone -- user agent, client hints, platform, touch, screen, graphics chip and memory all say Android.

On a device drives the Chrome already installed on a phone or Mobyx Device, over the same cable as everything else. Nothing is emulated, so a fingerprint test reads an ordinary phone: measured on an independent fingerprint test, 100%, no masking and no automation detected. The PC browser dressed as a Pixel 8 scores 90% on the same page, because a disguise is still a disguise.

The trade is isolation. Android runs one Chrome with one profile, so a browser on a device shares that device's cookies, logins and history, and cannot be cloned into a second identity. When identities must stay apart: browsers on this PC, or one Mobyx Device each.

#Browser profiles in detail

Engine. Pick Mobyx Chrome (no download, the best default), Mobyx Firefox (a different engine), or Camoufox (Firefox with its fingerprint changed inside the browser).

Identity. Leave it as this computer for a browser that tests clean, or build one: choose Windows, Mac, Linux, Android or iPhone and everything follows -- user agent, platform, screen, processor, graphics. On Firefox these are set through the browser's own preferences, so a Mac profile reports a Mac in navigator.platform, oscpu and WebGL, not just in the user agent. Fonts are the one thing that stays this PC's on Firefox; Camoufox covers those.

Version and screen. The version box offers the installed browser's version and a few before it; empty means match the browser that really runs, which a site cannot contradict. The screen size is a drop-down you can also type into.

Location. Match location, language and clock asks where the profile's proxy comes out and sets the timezone, languages and coordinates from that, so they agree with the IP.

#Proxies

Paste a proxy in any of the usual layouts into the Proxy tab and mobyx fills in the fields:
ip:port · user:pass@host:port · host:port:user:pass · user:pass:host:port · socks5://user:pass@host:port

Test quality goes through the proxy and reports the address, country, network, whether it is residential, mobile or a data centre, how fast it answers, and a score out of 100. Reset clears the proxy completely. In a workflow, the Profile node's Create Profile action takes the same formats, and Test The Proxy First fails the step on a dead or low quality proxy so a loop can skip it.

#Which one should I use?

A real phone when the app checks hardware, or when the browser has to be genuinely Android.
A Mobyx Device when you need many phones, or a clean one per account, and nobody is watching the hardware that closely.
A Browser on this PC when the job is a website and you want a dozen separate identities cheaply.