Reduced-form identity with stock-style structure
User-Agent uses a reduced form, following stock browser behavior. Client Hints can define model, platformVersion, Google Chrome brands, and fullVersionList as a coordinated identity.
DCBrowser
DCBrowser combines original Chromium 159 with native engine-level configuration for browser identity, graphics, network behavior, and profile isolation. Browser settings are managed from Device Changer and applied without JavaScript injections. Profiles support cookie import and export, including conversion of desktop cookies for mobile use.
Latest APK: DCBrowser-159.0.8154.8-dc63-release.apk
DCBrowser is based on original Chromium 159. Its behavior is controlled at the C++ engine level across Blink, the network stack, and GPU interfaces. Instead of overwriting browser objects after a page loads, DCBrowser applies configuration through switches and native interception at the point where a value is created.
This keeps browser behavior aligned across page APIs, request headers, graphics adapters, and storage. The profile is configured in Device Changer, so browser settings remain connected to the same controlled environment used for Android testing.
User-Agent uses a reduced form, following stock browser behavior. Client Hints can define model, platformVersion, Google Chrome brands, and fullVersionList as a coordinated identity.
The Accept-Language request header is aligned with navigator.languages. The relationship is controlled in the network stack instead of being patched separately in page JavaScript.
Configure hardwareConcurrency, deviceMemory, languages, platform, and webdriver from the same browser profile.
The Intl locale follows the first language in the profile. Timezone behavior uses a triple binding across Intl.DateTimeFormat, Date.getTimezoneOffset, and ICU so all three paths describe the same zone.
WebGL vendor and renderer can represent the selected device, for example ANGLE (ARM, Mali-G715, OpenGL ES 3.2). Parameters such as MAX_TEXTURE_SIZE and the extension allowlist can follow the same GPU legend.
WebGPU adapterInfo is controlled to match the device legend instead of exposing an unrelated adapter from the host system.
The screen resolution mechanism lets the browser present the dimensions assigned to the active device profile.
Canvas and audio noise are available as part of the browser profile, alongside its other identity and graphics settings.
WebRTC IP handling uses default_public_interface_only, preventing local or internal interface addresses from being exposed through the default WebRTC path.
Every DCBrowser profile can use its own SOCKS5 proxy. Network selection belongs to the browser profile rather than being shared globally.
Export cookies from a browser profile or import them into another profile. DCBrowser can convert cookies exported on a PC into a mobile-compatible format while keeping cookies and cache isolated per fingerprint.
History also belongs to the individual fingerprint. Identity, storage, and network settings remain attached to the same profile.
| Area | Controlled values | Application point |
|---|---|---|
| Chromium engine | Original Chromium 159 behavior | C++ across Blink, net, and GPU |
| User-Agent | Reduced-form, stock-style UA | Native browser configuration |
| Client Hints | Model, platformVersion, Google Chrome brands, fullVersionList | Coordinated browser identity |
| Languages | Accept-Language and navigator.languages | Single relationship in the network stack |
| Navigator | hardwareConcurrency, deviceMemory, languages, platform, webdriver | Active profile |
| Locale and time | Intl locale, Intl.DateTimeFormat, Date.getTimezoneOffset, ICU | First language plus triple timezone binding |
| WebGL | Vendor, renderer, MAX_TEXTURE_SIZE and other parameters, extension allowlist | GPU legend |
| WebGPU | adapterInfo | Profile-matched adapter |
| Display | Screen resolution | Profile resolution mechanism |
| Media surfaces | Canvas and audio noise | Browser profile |
| WebRTC | default_public_interface_only | Public-interface-only IP handling |
| Proxy | Independent SOCKS5 per browser profile | Separate from Device Changer app proxy |
| Storage + cookie portability | Cookies, cache, history, cookie import/export, PC-to-mobile conversion | Isolated per fingerprint |
Use DChecker Web to inspect what the browser reports after the profile is applied. The goal is a consistent result across page APIs, network headers, graphics interfaces, and stored state, rather than isolated values that contradict each other.
Open DChecker Web Download DCBrowser APK