> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/apps/tracking/prepare-smartphone.md).

# Prepare smartphone

Prepare your smartphone befor live tracking with RACEMAP app.

Set location permission of RACEMAP app "allow all the time"

<figure><img src="https://1672210197-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSRNxaH2Ju9Flr7JhJD%2Fuploads%2F1zSoGZ58bVMMNZcB56jH%2FScreenshot_20251201_143859_Permission%20controller.jpg?alt=media&amp;token=f5be1155-2e5f-4c6a-bcb9-3fe1f2ffc11d" alt="" width="188"><figcaption></figcaption></figure>

* Test live tracking before your race, to get to know how tracking works well at the competition.
* Share the link of your tracking map in WhatsApp, Facebook. That way your family and friends keep track of your race easily.
* Stow smartphone: Fix your smartphone properly at the upper arm, in a tricot pocket or in the backpack lid pocket of your bag.

Use a powerbank for 15+ hours of live tracking with Racemap App. Tracking affects the battery life of your smartphone. Battery life depends on your device, the battery, your usage behavior and network coverage.

* Charge & restart your phone.
* Stop all apps you do not need.
* Use a powerbank for long events.


---

# 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.racemap.com/apps/tracking/prepare-smartphone.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.