> For the complete documentation index, see [llms.txt](https://docs.gkshop.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gkshop.org/gksphone-v2/configuration/custom-ringtones-and-notifications.md).

# Custom ringtones and notifications

## Step 1: Add Sound Files

#### For Ringtones:

Place your ringtone files in the following directory:\
`/html/sounds/ringtones/`

#### For Notification Sounds:

Place your notification sound files in the following directory:\
`/html/sounds/notifications/`

Ensure the files are in a supported audio format (e.g., `.ogg`, `.mp3`).

## Step 2: Add New Sound Config.json

#### Adding Ringtones:

1. Copy the relative path of the ringtone file from `/html/sounds/ringtones/`.
2. Add a new entry under the `Sounds` section in the `config.json` file.

**Example:** If you add a file named `chime.ogg`, the updated `Sounds` section may look like this:

```json
"Sounds": {
  "Default": "/html/sounds/ringtones/default.ogg",
  "Classic": "/html/sounds/ringtones/classic.ogg",
  "Bell": "/html/sounds/ringtones/bell.ogg",
  "Chime": "/html/sounds/ringtones/chime.ogg"
},

```

#### Adding Notification Sounds:

1. Copy the relative path of the notification sound file from `/html/sounds/notifications/`.
2. Add a new entry under the `Notifications` section in the `config.json` file.

**Example:** If you add a file named `alert.ogg`, the updated `Notifications` section may look like this:

```json
"Notifications": {
  "Arrived": "/html/sounds/notifications/arrived.ogg",
  "Crystal": "/html/sounds/notifications/crystal.ogg",
  "Ping": "/html/sounds/notifications/ping.ogg",
  "Alert": "/html/sounds/notifications/alert.ogg"
}
```

## Step 3: Restart the phone <a href="#restart-the-phone" id="restart-the-phone"></a>

After adding the audio files and updating the config, you need to restart the phone for the changes to take effect.


---

# 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.gkshop.org/gksphone-v2/configuration/custom-ringtones-and-notifications.md?ask=<question>&goal=<endgoal>
```

`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.