> For the complete documentation index, see [llms.txt](https://docs.realtwin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realtwin.org/cameratwin/troubleshooting/my-device-is-not-showing-up-in-the-livelink-sources-list.md). # My device is not showing up in the LiveLink sources list We've recently identifed an issue with NDI streaming, specifically on Android 14 devices, where the phone is not properly advertising the service and hence isn't being discovered within the UE plugin. If you are facing this issue, we've prepared a video tutorial with a workaround, which will allow you to use CameraTwin uninterrupted: {% embed url="" %} Unfortunately the issue is related to the NDI framework (which CameraTwin uses) and its compatibility with the latest Android update, so we cannot troubleshoot it directly. We are in close contact with NDI developers who have acknowledged the issue, and hope this will be resolved soon. In the meantime, make sure to utilise the workaround detailed above. If you are still facing issues, please reach out to us at [**cameratwin@realtwin.org**](mailto:cameratwin@realtwin.org)**.** --- # 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.realtwin.org/cameratwin/troubleshooting/my-device-is-not-showing-up-in-the-livelink-sources-list.md?ask=&goal= ``` `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.