[1514599514]

All changes in this update were generated by GitHub Copilot. Since I lack the relevant Android low-level knowledge, I'm unable to review the code itself. However, I manually tested all use cases and parameter combinations in the minicap example's README.md, and they all worked successfully on my test device.

If there are any issues with the code, such as it not conforming to the project's conventions, feel free to close the PR directly.

Below is a summary generated by GitHub Copilot.

Summary

• Add an allocator@3.0 descriptor-v30 allocation path for the tested device when the API 29 Qualcomm allocator@2.0 service is unavailable.
• Validate the observed Mali/Bifrost native handle and linear RGBA plane layout before reading pixels from the DMA-BUF.
• Preserve the existing Qualcomm and Pixel graphics paths; reject unsupported or compressed layouts rather than interpreting them as RGBA.
• Document the supported device ABI and minicap usage.

Device and architecture

• Tested on a device reporting ro.board.platform=rk3588, Android 10 (API 29).
• Built and run as a 64-bit ARM Android executable (GOOS=linux GOARCH=arm64 CGO_ENABLED=0).
• The device exposes allocator/mapper HIDL 3.0 with Bifrost graphics libraries; the tested allocation is a CPU-readable, linear RGBA DMA-BUF.
• The device's model/build properties do not consistently identify it as an RK3588 device. Support is therefore limited to the allocator ABI verified on this device and is not a claim of compatibility with all RK3588 or Mali devices.

Validation

• Cross-compiled the minicap package tests for ARM64 and ran them on the device.
• Verified display info, capture test, and JPEG screenshot modes on-device.
• Verified continuous minicap socket delivery, JPEG frame decoding, and client reconnection.
• Verified raw RGBA output contains fixed-size frames.
• go vet, formatting checks, and git diff --check passed.