Smartphone depth functions can use different hardware and software routes. When checking a phone with a ToF sensor, identify the exact model, region and function first. A rear focusing sensor, front authentication system and application-accessible scene-depth stream are separate capabilities.
List bounded manufacturer-confirmed examples
The examples below were checked against the named manufacturers' pages on 19 October 2026. They identify documented configurations rather than a complete current-market or purchasing list.
| Documented example | Manufacturer-described ToF use | Scope to retain |
|---|---|---|
| Sony Xperia 1 IV, 512 GB, United States support specification | 3D iToF sensor listed among rear-camera features | The named model and regional specification |
| HUAWEI Mate 40 Pro, applicable single/dual SIM 8 GB + 256 GB configurations, EMUI 13.0 | ToF 3D imaging used for 3D face recognition | The configurations and system stated on the support page |
Sony's Xperia 1 IV 512 GB specification provides the hardware identification. HUAWEI's Mate 40 Pro face-recognition guidance describes the ToF-based authentication function for its listed configurations. Neither example, by itself, establishes a public raw-depth API.
Separate rear focus, scene depth and front authentication
A rear ToF sensor may support camera functions such as focusing. Scene-depth software can estimate distances for effects, measurements or AR, using the inputs available to it. A front authentication system uses its selected imaging and processing pipeline to compare a face with enrolled information.
Check the actual function rather than inferring it from a depth-related marketing name. A portrait effect, facial unlock or an AR depth image does not identify the physical ranging technology on its own. See ToF in face-recognition systems for the distinction between capture and authentication.
Check regional model and generation
Record the full product name, regional model code, operating-system version and camera configuration. Related phone generations or similarly named regional variants can have different cameras and software access. Use the specific manufacturer's specification or support document for the device being evaluated.
Phone integration also involves optical placement, thermal limits, battery states and proprietary processing. Passive stereo, structured light and ToF have different optical arrangements and input requirements. An external development camera and an embedded phone module therefore need separate integration assessments.
Separate Camera2 hardware depth from ARCore depth and API access
Android defines DEPTH16 as a dense depth format containing range and confidence information; camera-produced ranges use millimetres. A format definition does not mean every phone exposes it. Inspect the camera's advertised capabilities and supported stream configurations, then test access with the required permissions and camera mode.
Google's ARCore Depth API derives depth from motion, uses machine-learning processing and combines additional hardware depth where available. An app receiving ARCore depth therefore should not label that result as a raw ToF stream without device-specific evidence. Hardware depth availability, Camera2 access and ARCore support should be recorded separately.
Explain developer evaluation limits
Test the intended API on the exact device and software version. Record output size, format, timestamp behavior, supported simultaneous streams, latency, battery use and thermal changes. Evaluate motion, textureless surfaces, dark objects and the intended lighting, retaining confidence or validity information where supplied.
For a product that needs a separately integrated depth camera, define the host platform and input requirements independently of the phone examples. The AR/VR integration guide covers geometry, pose and timing questions for that development path.
Discuss your evaluation with DOMI.
FAQs
Which verified phone examples are listed here?
The bounded examples are the United States Sony Xperia 1 IV 512 GB specification and the listed HUAWEI Mate 40 Pro configurations under EMUI 13.0. Check the exact model and region before extending those descriptions.
Does a ToF sensor guarantee an app can read its depth data?
Application access depends on the device's software, camera capabilities, permissions and exposed modes. Verify the required streams on the exact hardware and software combination.
Does ARCore depth require a physical ToF sensor?
ARCore can derive depth from device motion and use available hardware depth as an additional input. Its depth output alone does not identify the phone's physical sensing configuration.
What should a developer log during evaluation?
Log the model code, operating system, API, stream configuration, timestamps, validity, latency and resource use. Keep results tied to representative scenes and the tested software version.
