SYSTEM ONLINE CHROMIUM 159 · BLINK · NET · GPU
← Back to home

DCBrowser

A Chromium browser controlled by Device Changer profiles

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 native Chromium profile hologram Configuration and switches flow into a native Chromium engine window, with isolated browser profiles and per-profile network settings. 01 / INPUTCONFIG 02 / RULESSWITCHES 03 / ORIGINC++ NATIVE profile://pixel-a16 BLINK / NET / GPU NO JS INJECTIONS PROFILE ACOOKIES / CACHE PROFILE BHISTORY / STORAGE NETWORKSOCKS5 / PROFILE

Engine-level control, not JavaScript patches

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.

01ConfigProfile values in Device Changer
02SwitchesBrowser-level configuration
03InterceptionNative Blink, net, and GPU paths
04Value originNo JavaScript injection layer

Identity, language, and navigator

User-Agent + Client Hints

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.

Accept-Language

One language source across page and network

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.

Navigator

Hardware and platform values for the active profile

Configure hardwareConcurrency, deviceMemory, languages, platform, and webdriver from the same browser profile.

Intl + timezone

Locale and time stay internally consistent

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.

Graphics, display, and media

WebGL

GPU identity, capabilities, and extensions

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

Adapter information aligned with the profile

WebGPU adapterInfo is controlled to match the device legend instead of exposing an unrelated adapter from the host system.

Screen

Profile-specific resolution spoofing

The screen resolution mechanism lets the browser present the dimensions assigned to the active device profile.

Canvas + audio

Controlled noise for graphics and audio surfaces

Canvas and audio noise are available as part of the browser profile, alongside its other identity and graphics settings.

Network behavior and isolated profiles

WebRTC

Internal interface protection

WebRTC IP handling uses default_public_interface_only, preventing local or internal interface addresses from being exposed through the default WebRTC path.

SOCKS5

A separate proxy for each browser profile

Every DCBrowser profile can use its own SOCKS5 proxy. Network selection belongs to the browser profile rather than being shared globally.

Cookies + portability

Import, export, and convert cookies between desktop and mobile

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

Independent browsing history

History also belongs to the individual fingerprint. Identity, storage, and network settings remain attached to the same profile.

From Device Changer configuration to a running browser

  1. Create or select a profile in Device Changer. Define the device identity, language, timezone, graphics, display, and network values.
  2. Assign a browser-only SOCKS5 proxy if needed. Keep it separate from the proxy used by the Device Changer app.
  3. Launch the profile in DCBrowser. Configuration is passed through native switches and engine-level interception without a JavaScript injection layer.
  4. Verify the result with DChecker Web. Compare navigator, locale, timezone, WebGL, WebRTC, screen, canvas, audio, and network behavior against the intended profile.

DCBrowser capability map

AreaControlled valuesApplication point
Chromium engineOriginal Chromium 159 behaviorC++ across Blink, net, and GPU
User-AgentReduced-form, stock-style UANative browser configuration
Client HintsModel, platformVersion, Google Chrome brands, fullVersionListCoordinated browser identity
LanguagesAccept-Language and navigator.languagesSingle relationship in the network stack
NavigatorhardwareConcurrency, deviceMemory, languages, platform, webdriverActive profile
Locale and timeIntl locale, Intl.DateTimeFormat, Date.getTimezoneOffset, ICUFirst language plus triple timezone binding
WebGLVendor, renderer, MAX_TEXTURE_SIZE and other parameters, extension allowlistGPU legend
WebGPUadapterInfoProfile-matched adapter
DisplayScreen resolutionProfile resolution mechanism
Media surfacesCanvas and audio noiseBrowser profile
WebRTCdefault_public_interface_onlyPublic-interface-only IP handling
ProxyIndependent SOCKS5 per browser profileSeparate from Device Changer app proxy
Storage + cookie portabilityCookies, cache, history, cookie import/export, PC-to-mobile conversionIsolated per fingerprint

Verify the active browser profile

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

Related pages