android

mmashaghi

Has anyone successfully built depthai-core v2.32.0 or v3.x for Android in 2025/2026, and if so, which commit, NDK version, and build procedure did they use?
thanks

Oskar-Luxonis

Hey mmashaghi - for v3.x, Android is not officially supported. For v2, there have been community-successful Android builds, but they are unofficial and not actively tested by us. Is there no way to use linux?

Thanks,
Oskar

mmashaghi

Hi Oskar,
thanks for the swift reply.

I need to integrate the camera in a Unity project, and Unity requires special license for Linux. So I am bound to use it in Android.
I have tried to use the git repositories of Luxonis regarding and android implementation, but I wasn't able to compile or run any of them.

Oskar-Luxonis

mmashaghi - the only Android build report I found that worked recently is this customer/community setup:

luxonis/depthai-core1001

It is not an officially supported Android/Unity path, but it includes the NDK version and CMake procedure that worked for that user.

Sorry, but beyond that community-provided setup we currently can’t help much with Android/Unity integration or debugging the older Android repositories.

mmashaghi

So now I'm working on bringing an OAK-D-PRO-W up directly from an Android application using the Android USB Host API, without using the official DepthAI Android stack. I've confirmed that Android can enumerate the device, obtain USB permission, open the device, claim the interface, and communicate with the bulk endpoints. The camera appears as a Movidius MyriadX device (VID 0x03E7, PID 0x2485) with a single vendor-specific interface and bulk IN/OUT endpoints.

Could you clarify the expected host-side boot sequence for a device in this state? Specifically, is PID 0x2485 the MyriadX ROM bootloader waiting for a firmware upload, and is the firmware upload protocol documented anywhere? We're interested in understanding the minimum sequence required to transition the device from the unbooted MyriadX state into a running DepthAI/XLink state. Any documentation, protocol references, firmware-loading details, or pointers to the relevant source files in the DepthAI/XLink stack would be extremely helpful.

Thank you Oskar.

Oskar-Luxonis

Hey mmashaghi - yes, 03e7:2485 is the Myriad X unbooted/ROM state. In our stack it maps to X_LINK_UNBOOTED. After boot, the USB PID changes, e.g. 03e7:f63b for X_LINK_BOOTED.

At a high level, the supported host flow is:

Discover device in X_LINK_UNBOOTED
Load the DepthAI .mvcmd firmware binary
Send it with XLink’s boot path, internally XLinkBootMemory(...)
Wait for USB re-enumeration into the booted XLink state
Connect/open XLink streams normally

Relevant source pointers:

depthai-core/src/device/DeviceBase.cpp - handles unbooted / bootloader / booted device states
depthai-core/src/xlink/XLinkConnection.cpp - calls XLinkBootMemory(...)
depthai-core/src/utility/Resources.cpp - loads embedded MyriadX firmware / bootloader firmware
XLink source:
- src/pc/protocols/usb_host.cpp maps 03e7:2485 to X_LINK_UNBOOTED
- src/pc/protocols/usb_host.cpp contains the USB boot bulk-write path
- src/shared/XLinkDevice.c exposes XLinkBootMemory(...)

The firmware upload protocol itself is not documented as a supported public Android USB Host API protocol. It is an internal implementation detail of XLink/libusb, and we do not currently support bypassing the DepthAI/XLink stack or reimplementing the boot flow directly on Android.

So unfortunately this is outside what we can support/debug. The best reference is the XLink implementation, but we can’t provide a stable packet-level protocol contract for custom Android USB Host API integration.

mmashaghi

Thanks for the clarification Oskar, It's much more clear now.

I've also heared there is another binary that can be flashed into the camera to turn in to a normal usb camera (or 3 cameras) without any depth or IMU output. is that so?
can you also guide me through that process?

Actually through this link https://docs.luxonis.com/software-v3/depthai/ we can view 3 separate cameras asa normal usb-camera, but again implementing the same exact thing in android has the same challenge that we hade before.
so even if we could make the camera to act as a normal usb camera with a firmware update (which is stored in memory and wount be lost by cutting the power) it could help us at this stage.

Oskar-Luxonis

mmashaghi - there is a UVC mode, but it still uses DepthAI. It is not a separate firmware that permanently turns the OAK-D-PRO-W into a normal USB webcam.

The way it works is that a DepthAI pipeline with a UVC node is loaded onto the device. Once that pipeline is running, the host can see the output as a standard UVC camera stream. But the device still needs to be initialized through DepthAI first.

So for your Android/Unity case, this likely does not avoid the original issue. Android would still need some way to boot/load the DepthAI pipeline before the OAK can expose the UVC stream.

As far as I know, we do not currently have a supported firmware update that makes OAK-D-PRO-W permanently enumerate as one or more standard USB cameras after power-up, independent of DepthAI.