> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/faq/common-issues/why-cant-i-find-my-android-14-based-ndi-devices-on-my-network.md).

# Why can't I find my Android 14-based NDI devices on my network?

{% hint style="warning" %}
This issue has been resolved as of Android 14 and an update to the NDI HX App version 1.64
{% endhint %}

After updating your phone to Android 14 the Tricaster Camera, NDI HX Camera App, NDI HX capture App, and some other NDI apps will no longer appear as a source within your input. We've developed a workaround to solve the problem till the app is fixed. Please follow the below steps:

{% hint style="info" %}
**A new version of the NDI HX Camera app is now available which allows it to be discovered automatically. Ensure you're on the latest version of the software before trying the following steps:**
{% endhint %}

In the receiving PC or Mac, open NDI Access Manager and navigate to External Sources (NDI Access Manager is part of the freely available NDI Tools application)

1. Add a new source by selecting the External Sources tab, then pressing the + button beside IP Address
2. On the new window, select NDI as a type, and type in the Android 14's IP address
3. Press OK to close that Windows, then press OK to close the next Window
4. Restart your NDI application intended to receive the signal.

<figure><img src="https://ndi.video/wp-content/uploads/2023/10/Access-Manager-manual-source.gif" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ndi.video/all/faq/common-issues/why-cant-i-find-my-android-14-based-ndi-devices-on-my-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.