<uses-native-library> missing in Android LLM Inference Guide

[bringert]

Description of issue (what needs changing)

Add manifest tags <uses-native-library> to Android LLM Inference Guide

Clear description

The Android LLM Inference Guide https://developers.google.com/mediapipe/solutions/genai/llm_inference/android doesn't mention the need to add <uses-native-library> to AndroidManifest.xml.

Those tags are present in the example code https://github.com/googlesamples/mediapipe/blob/main/examples/llm_inference/android/app/src/main/AndroidManifest.xml:

        <!-- Required to initialize the LlmInference -->
        <uses-native-library
            android:name="libOpenCL.so"
            android:required="false"/>
        <uses-native-library android:name="libOpenCL-car.so" android:required="false"/>
        <uses-native-library android:name="libOpenCL-pixel.so" android:required="false"/>

Without them, I get a SIGABRT with these messages:

E0000 00:00:1713429439.990396    7017 calculator_graph.cc:887] FAILED_PRECONDITION: CalculatorGraph::Run() failed: Calculator::Open() for node "LlmGpuCalculator" failed: Can not open OpenCL library on this device - undefined symbol: clSetPerfHintQCOM
F0000 00:00:1713429439.990602    7017 llm_engine.cc:126] Check failed: graph_->WaitUntilIdle() is OK (FAILED_PRECONDITION: CalculatorGraph::Run() failed: Calculator::Open() for node "LlmGpuCalculator" failed: Can not open OpenCL library on this device - undefined symbol: clSetPerfHintQCOM) 
terminating.
F0000 00:00:1713429439.990602    7017 llm_engine.cc:126] Check failed: graph_->WaitUntilIdle() is OK (FAILED_PRECONDITION: CalculatorGraph::Run() failed: Calculator::Open() for node "LlmGpuCalculator" failed: Can not open OpenCL library on this device - undefined symbol: clSetPerfHintQCOM) 
terminating. 

Correct links

No response

Parameters defined

No response

Returns defined

No response

Raises listed and defined

No response

Usage example

No response

Request visuals, if applicable

No response

Submit a pull request?

No response

[kuaashish]

Hi @bringert,

Thank you for bringing this to our attention. We are forwarding the issue internally and will work to include it in our documentation soon.

Thank you!!

[kuaashish]

Hi @schmidt-sebastian,

Could you please look into this issue?

Thank you!!

[schmidt-sebastian]

cc @ktonthat