> For the complete documentation index, see [llms.txt](https://docs.helix.voodoo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helix.voodoo.io/monetization/integrate-the-sdk/unity-levelplay-adapter/android-levelplay-adapter.md).

# Android

This guide covers integrating Helix with Unity LevelPlay on **Android** using Gradle.

{% hint style="info" %}

* **Minimum supported Android version:** Android 7.0 (API level 24)
* **Latest adapter version:** 5.9.0
* **Latest Helix SDK version:** 4.29.3
  {% endhint %}

{% hint style="info" %}
**Before you start:** complete the mediation setup first — activate Helix and set up your instances in the Unity LevelPlay dashboard. See [Unity LevelPlay Integration](/monetization/configure-mediations/unity-levelplay-integration.md).
{% endhint %}

## Add custom Maven repository

Add the Helix Maven repository to your Gradle configuration.

Use **one** of the following options, depending on where your project declares repositories.

{% tabs %}
{% tab title="Groovy DSL (`build.gradle`)" %}

```groovy
allprojects { 
	repositories { 
		google() 
		mavenCentral()
		maven { 
			url "https://framework.voodoo-adn.com/android/release/apps" 
		} 
	} 
}
```

{% endtab %}

{% tab title="Kotlin DSL (`settings.gradle.kts`)" %}

```kotlin
dependencyResolutionManagement { 
	repositories { 
		google() 
		mavenCentral() 
		maven { 
			url = uri("https://framework.voodoo-adn.com/android/release/apps") 
		} 
	} 
}
```

{% endtab %}
{% endtabs %}

## Add dependencies

Add the Helix LevelPlay adapter and SDK dependencies to your **app module** (or ads module if applicable).

```groovy
dependencies { 
	implementation "com.unity3d.ads-mediation:voodoo-adapter:5.9.0"
	implementation "io.adn:adn-sdk:4.29.3"
}
```

## Sync and build

After updating Gradle configuration:

* Sync the project.
* Build the app.
* Confirm that:
  * Dependencies are resolved successfully.
  * No Gradle or dependency resolution errors occur.
  * The Helix SDK and the LevelPlay adapter are included in the final APK or AAB.
* Verify at runtime with LevelPlay's [integration validator](https://docs.unity.com/en-us/grow/levelplay/sdk/android/integration-helper) — the log shows <mark style="color:red;">`Voodoo - VERIFIED`</mark>, as Helix appears under **Voodoo** in LevelPlay's network list.

## Testing

Use [LevelPlay’s Integration Test Suite](https://docs.unity.com/en-us/grow/levelplay/sdk/android/integration-test-suite) to validate that the adapter is installed and the integration is working as expected.

After completing these steps, Helix will be enabled for this ad unit and ready to receive bid requests.

## Troubleshooting tips

If dependency resolution fails:

* Confirm the repository is added at the correct level
* Ensure <mark style="color:red;">`mavenCentral()`</mark> is present
* Perform a clean sync, then rebuild
* If the build fails with "Build was configured to prefer settings repositories over project repositories", your project uses <mark style="color:red;">`FAIL_ON_PROJECT_REPOS`</mark>, the default for projects created by recent versions of Android Studio. Declare the repository in your settings file instead of <mark style="color:red;">`build.gradle`</mark>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helix.voodoo.io/monetization/integrate-the-sdk/unity-levelplay-adapter/android-levelplay-adapter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.