> 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-11-mobile-credential-st.md).

# Mobile credential stops working after locking a device

Restore Mobile Connect access when a device suspends Bluetooth or NFC after locking.

### Background

* iPhones use only Bluetooth for credentials (not NFC).
* Android phones can use both NFC and Bluetooth.
* When a device is locked, in theory both the app and Bluetooth services will still work, and the credential should still function.
* Some cases may require the user to re-trigger the device's Bluetooth/NFC from idle by activating the screen (pressing the volume button, waking the device).
* The phone's OS may kill or suspend idle apps to reallocate memory, which causes Mobile Connect to stop working.
* Calibration, connection sensitivity, and Bluetooth background access settings can be adjusted in the app under **Settings**.

### iOS workarounds

> **Note:** these are workarounds only and should not be treated as a standard operating method.

### Option 1a: Siri Shortcuts

> **Cons:** the phone must be unlocked to run Mobile Connect.

1. Open Mobile Connect, tap the three dots (top right), tap **Settings**, tap **Register Siri Shortcut**.
2. Open the **Shortcuts** app.
3. Tap **+** (top right) to create a new shortcut.
4. Tap **New Shortcut**, then **Rename**, and give it a sensible name such as "Unlock Door".
5. Tap **Search Actions**, search "Gallagher MC", tap **Open Next Door**, tap **Done**.
6. The shortcut can now be launched with "Hey Siri Unlock Door."

> **Caution:** the 'Open door' Siri Shortcut uses the **manual connect range** for auto-connect and attempts to open the nearest door when the shortcut is run.

### Option 1a-i: Siri Shortcuts Automation (location-triggered)

1. Open the **Shortcuts** app.
2. Tap **Automation** (middle tab at the bottom).
3. Tap **+** to add a new Automation.
4. **When:** tap **Arrive**, then **Location**, then type the address or use Current Location. Drag the blue dot to set the area size. Choose a time range if needed. Tap **Run Immediately**.
5. **Do:** tap **Choose...**, tap **My Shortcuts**, select the shortcut you created.

### Option 1a-ii: Accessibility Back Tap

1. Open **Settings > Accessibility > Touch**.
2. Scroll to the bottom and select **Back Tap**.
3. Tap **Double Tap** or **Triple Tap**.
4. Scroll to **Shortcuts** and tap the Mobile Connect Siri Shortcut.
5. Mobile Connect will now open when the back of the phone is double-tapped.

### Option 1a-iii: Action Button (iPhone 15 or later)

1. Open **Settings > Action Button**.
2. Scroll across to **Shortcut**.
3. Select the Mobile Connect Shortcut.

### Option 1b: Launch Centre Pro

> **Cons:** this is a paid third-party app. It will run Mobile Connect while the phone is locked.

[Launch Centre Pro](https://contrast.co/launch-center-pro/) is an automation tool supporting scheduled, NFC tag, and location triggers.

URL options for Launch Centre Pro actions:

* Shortcut URL: `//run-short?name={{Unlock door}}`
* Mobile Connect app URL: `gglcredential:// xxxx`
* x-callback-url: `gglcredential://x-callback-url/launch`

> **Caution:** Gallagher does not support Launch Centre Pro or Siri Shortcuts as products. These are community workarounds that may improve Mobile Connect background access reliability.

***

🔗 **Related**

* [10. Mobile Credentials Disappearing from App](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-10-mobile-credentials-d.md). Another "credential seems gone" symptom.


---

# 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-11-mobile-credential-st.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.