# Druid USB Camera 1.0.0 (versionCode 2) — third-party source and notices

This package identifies the original signed AAB by SHA-256 in CODE2_BINARY_INVENTORY.json and its nine exact native-library hashes. It contains no APK/AAB, proprietary Druid application source, private key, password or media. App binaries are not licensed as open source merely by inclusion of these libraries.

libusb 1.0.30, commit 87a55632db62c9bdc58cd31d3ccfa673f1bb017f, is LGPL-2.1-or-later, unmodified and dynamically linked as libusb-1.0.so. The complete original archive, Android configuration/headers and original build scripts are in source/libusb.tar.gz. Original copyrights/license are preserved. The new library-only build/replacement helpers are provided under LGPL-2.1-or-later; that grant applies only to those helpers, not proprietary app source. Full license text: licenses/libusb/COPYING.

libuvc (BSD) and libjpeg-turbo 3.1.4 (BSD/IJG/zlib) are statically included in libdruid_uvc.so. Their original upstream sources and full original notices are included. libuvc has app-specific integration changes described in licenses/NOTICE.txt; this archive does NOT claim its original source alone reconstructs the proprietary combined libdruid_uvc.so. Permissive licenses do not require disclosure of that proprietary integration. JPEG has upstream acb5ce780c78194e99656798aba7cac4126a7513 destination tracking backport in src/jdatadst-tj.c: the added condition is `&& dest->alloc` after `&& alloc` on the destination-buffer reuse condition. The exact original/patched hashes and upstream link are in UPSTREAM_PINS.json. This is not an OSV-2026-1068 resolution claim. This software is based in part on the work of the Independent JPEG Group.

AndroidX graphics-path 1.0.1 (Apache-2.0): official AAR, POM and published source JAR are under third-party/. The source JAR is not represented as complete native source. The native hashes match the official AAR. Apache/BSD/IJG/zlib/NDK and resolved AndroidX/Kotlin component notices are retained under licenses/; the corresponding notices embedded in app binaries are unchanged. See the inventory for exact component scope.

## Library rebuild

Install Python 3.12+ (tarfile data filter), the Android SDK with NDK 29.0.14206865, CMake 3.31.6/Ninja, and Android build-tools 36.0.0. These are external standard tool prerequisites, not supplied here. From this folder, run once per ABI, choosing new output directories:

    python build_libusb.py --sdk <ANDROID_SDK> --abi arm64-v8a --output <new-arm64-dir>

Repeat for armeabi-v7a and x86_64. The helper validates the source digest and compiles for Android API24. It does not download code, sign, install, overwrite an existing output directory or access a signing key. Build instructions and the library-only CMake input use the same source file list, Android configuration, visibility/O2 options and linked log dependency as the code2 build. Bit-for-bit reproduction is not promised (build paths/debug/build IDs can differ). Interface/export/dependency and package replacement checks are documented separately.

## Replacement/relinking rights and practical limits

DruidApps permits modification of the application for the customer's own use and reverse engineering for debugging modifications to the LGPL-covered library, and copying/repackaging application object code to relink with an interface-compatible modified libusb. No proprietary application source is granted or needed for this dynamic-library replacement method. Preserve all component notices. Conflicting application terms must not restrict these LGPL rights.

Obtain the complete APK set for your own installed copy using Android's supported package/ADB tools (`adb shell pm path com.druidapps.usbcamera`, then pull each returned APK). Keep base and all configuration APKs. On the ABI-containing APK:

    python replace_libusb.py original-abi.apk arm64-v8a <rebuilt-libusb-1.0.so> modified-abi.apk
    zipalign -P 16 -f 4 modified-abi.apk aligned-abi.apk

Use apksigner with YOUR OWN key to sign all APKs in the installation set consistently, then verify each. No upload signing key is included or needed; do not ask for DruidApps' key. Android does not allow a differently signed in-place update; installation can require uninstalling first, which can lose app-private media catalog/settings. Preserve/export data before making changes. This kit performs no signing, uninstall, installation or user-data operations.

IMPORTANT: these steps describe unprotected local application objects. Google Play automatic protection may reject modified/repackaged apps or redirect to Play. This kit does not remove, bypass or certify that protection. Do not assume that a modified Play-protected installation will run. DruidApps must settle recipient replacement/relinking compatibility and any conflicting terms/protection before distribution. The original in-app claim about absence of integrity restrictions describes the supplied unprotected AAB, not verified Play-transformed delivery. Actual Play-split installation has not been tested in this preparation.

The proposed source-access method is direct no-charge download, not a three-year written-offer substitution. Publish the download alongside clear recipient access instructions and retain its exact version. Final LGPL distribution interpretation, equivalent recipient access, product terms and Play protection compatibility require owner/legal review. Contact support@druidapps.com for source/license questions. Preparation alone is not a certification that all distribution obligations are fulfilled.
