Skip to main content

⚙️ System - Detailed

Displays a list of hardware and software information for the running device. When issues occur, you can immediately determine whether problems are dependent on specific OS versions or CPU architectures.

📋 Display Item List

The System tab displays the following information organized by category.

1. Device & OS (Basic Information)

Used for device identification and OS-dependent issue investigation.

ItemDescription
Operating SystemOS type and version
Device NameDevice identifier
Device IDDevice-unique ID (copyable)
Device TypeDevice category such as Desktop, Handheld
Device ModelSpecific model name (e.g., iPhone15,3)
System LanguageDevice system language setting
PlatformRunning platform

2. Hardware (CPU/Memory)

Verify processing power and memory capacity.

ItemDescription
CPU TypeProcessor name/architecture
CPU CountNumber of logical processors (cores)
System MemoryTotal physical memory capacity
Battery StatusCharging state (AC connected, discharging, etc.)
Battery LevelBattery remaining (%)

3. Graphics & Display

Used to verify rendering load, graphics performance, and resolution.

ItemDescription
Graphics NameGPU name
Graphics VendorGPU vendor
Graphics VersionGraphics API version
Graphics MemoryVRAM (video memory) capacity
Gfx TypeGraphics API (Vulkan, Metal, Direct3D11, etc.)
Max Tex SizeSupported maximum texture size
Screen ResCurrent resolution and refresh rate (Hz)
DPIScreen pixel density
Instancing SupportGPU instancing availability
Compute ShaderCompute shader availability
HDR DisplayHDR display (RGBAHalf) support availability

4. Application & Unity

Verify build version and Unity runtime environment.

ItemDescription
Bundle IDApplication identifier (com.company.product)
App VersionApplication version
Build NumberMobile build number (retrieved from LogifySettings)
Unity VersionUnity Editor version being used
IL2CPPWhether scripting backend is IL2CPP
Install ModeDistinguishes store installation vs. development installation
Target FPSApplication.targetFrameRate setting value
VSyncVertical sync setting state

💡 Usage Scenarios

Practical Examples
  • Shader Bug Investigation: Check Graphics Name and Gfx Type to distinguish between GPU-specific (Adreno/Mali, etc.) rendering errors and API-dependent (Vulkan/OpenGL ES) issues.
  • QA Cost Reduction: If testers include System screen in their screenshots, it immediately identifies "which build" and "which device specs" the problem occurred on.
  • Release Decision Criteria: Verify that IL2CPP is True and Build Number is current to prevent confusion between debug and release candidate builds.