> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-07-bluetooth-works-for.md).

# Bluetooth works on Android but not iOS

Identify when Android access uses NFC rather than Bluetooth and verify reader Bluetooth support.

### Explanation

Assigning a Bluetooth credential to an Android phone also assigns an NFC credential, which works on any HBUS-connected T-series reader that has MIFARE capability, not just Multitech Bluetooth readers.

This makes it appear that Bluetooth is working on Android when it is not. The Android device is using the NFC component of the reader.

**To confirm:** open the Mobile Connect app on the Android phone. If no doors are listed in the app but the user can still gain access, the NFC component of the phone is granting access, not Bluetooth.

### When Android works but iOS does not

* The readers are likely not Bluetooth-capable readers at all.
* Verify using the reader identification steps in [03. Mobile Credential not working on Readers](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-03-mobile-credential-no.md).

> **Note:** this does not affect all Android devices. Many Android devices do not have NFC capability, and not all that do will support this functionality.

***

🔗 **Related**

* [03. Mobile Credential not working on Readers](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-03-mobile-credential-no.md). Reader identification and Bluetooth checks.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-07-bluetooth-works-for.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.