यह पृष्ठ अभी आपकी भाषा में उपलब्ध नहीं है। आप अंग्रेज़ी पाठ पढ़ रहे हैं।
Fingerprint
A phone profile on a computer: what makes it a whole phone
ARMANOS टीम7 minUpdated

In short
A whole device. Screen, pixel density, graphics card and memory belong to one model.
A window sized to the screen. ARMANOS brings the window to the device size instead of leaving a desktop one.
A check in a minute. Five readings in the developer console show whether the profile adds up.
What a platform reads first
A page reads your machine with ordinary questions, and asks permission for none, and it is the platform that adds the answers up, not you.
The answers arrive separately and add up to one device.
Let any pair disagree, and the platform stops watching the account and starts watching the machine. A phone is the agreement of every answer, not one of them.
| What the platform asks | What a real handset answers |
|---|---|
| User agent | Android, with Mobile at the end |
| Client hints | Platform Android, architecture arm, model |
| Screen and available area | Equal: a handset has no menu bar |
| Pixel density | Fractional: 2.625, 2.75, 3 or 3.75 |
| Touch and pointer | Five touch points, coarse pointer, no hover |
| Graphics card | The ANGLE string Android itself writes |
| Cores and memory | Eight cores, 4 or 8 gigabytes |
| Fonts | The Android set plus the maker's face |
| Connection | Three fields a desktop lacks |
A handset arrives whole
On a desktop people assemble different machines, and one maker's screen beside another's graphics card surprises nobody. A handset is not like that: the model settles everything.
So your profile gets a whole handset, not a bag of values, and hand edits do not apply to separate parts of a handset.
The pool holds 22 handsets and 7 tablets, each a model that really shipped.
Screen and density
From 360 by 780 to 412 by 919 layout points, density 2.625 to 3.75. Eight distinct screens.
Graphics card
Vendor and renderer arrive as a pair, and the pool holds twelve pairs.
Cores and memory
Eight cores everywhere, memory 4 or 8: a browser never names more than eight.
Maker fonts
Google Sans on a Pixel, SamsungOne on a Samsung, MiSans on a Xiaomi. The profile names only its device’s fonts to the page.
Cameras and microphones are counted the phone way
A page that has been allowed to record reads the number of capture devices: how many microphones, how many speakers, how many cameras.
A handset has two or three cameras and more often one microphone and one speaker, and the profile answers the same way.
A desktop machine answers differently: one camera, while microphones and audio outputs come in twos and threes because of headsets and monitors.
A phone with one camera and three microphones is one more pair that does not exist.
A page gets device names and their number with the same permission, and before it only the kinds.
So the number is matched to the handset in advance rather than at the moment a platform asks.
What ARMANOS does for a phone profile
ARMANOS builds a phone profile from one line of the device set, so every part belongs to one model.
The window is brought to the screen size, touch turns on, the pointer becomes coarse and the connection gets phone numbers.
You pick the model from a list in the profile window, and tablet templates answer as tablets, not as phones.
The fingerprint auto-check reads values back from a page and adds lines about touch, orientation and window size.
A phone's heap limit is half as high
Besides the memory size a page reads the script heap limit, and on a phone it is figured differently: a quarter of the memory against a half on a desktop.
Eight gigabytes of memory give a phone two gigabytes of heap, and a desktop machine four.
ARMANOS figures it by one rule for every handset in the pool.
A phone with a desktop heap limit would give itself away the same way as a phone with a desktop window.
The phone's User agent is shortened
Chrome on Android stopped putting the model and system version in its signature, and hands the model out only on a site's request rather than in the first header: every handset says Android 10; K.
The real model lives only in the client hints.
So a signature reading Android 14; Pixel 7 gives the forgery away in the first header. Your profile puts the model where a live Chrome does, nowhere else.
Touch and pointer answer together
A platform asks three questions in a row: is there ontouchstart, does (pointer: coarse) match, does (hover: none) match. A handset says yes to all three, a desktop no to any.
A live machine never gives a mixed answer, and the check takes one line. The profile reports five touch points, like Chrome on Android.
The window comes out too wide
An ordinary desktop window does not shrink to phone width, so a profile with a 360 screen would get a window wider than its own screen. ARMANOS brings the window to the device size.
On a page that declared a phone size, a window wider than the screen reads in one comparison. ARMANOS sets the device size after launch, and a new tab receives it too.
Embedded frames see the same phone
A tablet answers differently
Chrome on a tablet leaves Mobile out of its signature and calls itself not mobile, so sites hand it the desktop layout.
A tablet carrying Mobile contradicts its own header.
A tablet screen lies long side across, and its density is one and a half or two, below any handset. The pool holds 7 tablets, never a handset density.
Connection adds three extra fields
Chrome on Android has three connection fields a desktop lacks: type, downlinkMax and ontypechange. A platform reads them in one line about navigator.connection.
Opening the fields is not enough: unreplaced, they hand over your own computer's numbers, and an endless speed ceiling stands out more than missing fields.
So the ceiling matches the speed and comes from the browser's own table: 11, 54 and 600 for Wi-Fi, 42 and 100 for fast cellular.
Forty-two is HSPA+, a hundred is LTE, and they are drawn where the browser declares a fourth generation link.
A whole device, not a patchwork
The device arrives whole: the screen, density, graphics card, cores, memory and fonts of each phone profile come from one line of the device set.
No part comes from a neighbouring model. Tablets are built the same way.
How to check your own profile
Open the developer console inside the profile and read four answers in a row, and there is no need to look further after the first mismatch. A live machine answers consistently, a forgery breaks on the first.
If any reading argues with the one beside it, the profile reads as a desktop calling itself a phone. Where your machine sits makes no difference.
- 1
Screen and window
screen.width and window.innerWidth: on a page that declares a handset viewport the window is not wider than the screen.
- 2
Touch and pointer
navigator.maxTouchPoints, ontouchstart, (pointer: coarse) and (hover: none): all four answer like a phone.
- 3
Signature and hints
Android 10; K in the signature, Android, arm and the model in the hints.
Common questions
- Can a platform tell the phone was opened on a computer?
- It sees the answers a page gets, not where the machine stands. What gets caught is disagreement: one handset's screen, another's graphics card, an oversized window.
- Why a handset sized window when my monitor is large?
- A phone window equals the phone screen. On a page that declares a handset viewport, a window wider than the screen gives a fake away; on a page without that declaration a real handset is wider too. Where it sits on your monitor stays your choice.
- Can I pick a specific model?
- Yes, the device is picked from a list in the profile's Fingerprint > Change values > Device, and it arrives whole. Screen, density, graphics card, cores, memory and fonts come with it.
- Is a tablet just a big phone?
- No. A tablet calls itself not mobile and leaves Mobile out of its signature, so sites hand it the desktop layout. The pool holds 7 tablets.
- Does a proxy change any of this?
- The address arrives from elsewhere, and every answer here is produced on the machine in front of you. A proxy fixes no screen, no touch, no graphics card.
- Do flows run the same on a phone profile?
- Yes. A tap on a phone is a touch, not a mouse click, and on a phone profile the flow’s steps press with a touch, like a finger on the screen.
Keep reading
The app and the page
What an app on the handset reads and what a page never sees.
Client hints
Where the handset model went once the User agent stopped carrying it.
A window wider than the screen
The same contradiction on a desktop profile, with smaller numbers.
Free fingerprint check
12 values read in your browser, with nothing sent anywhere.
Create a phone profile
Pick a model in the profile (Fingerprint > Change values > Device): the device arrives whole.