Home Page » News » Tutorials » How to Add a Custom Notification Sound on Android Using ADB (No Root)

Add a Custom Notification Sound on Android Using ADB (No Root)

11 min read Step‑by‑step guide to copy a custom audio file to Android, set it as the notification tone via UI or ADB, and troubleshoot common issues – all without rooting. October 04, 2026 23:00

Before you start

Changing the default notification sound is a common way to personalize your device and make alerts more noticeable. Android stores user‑added tones in the /sdcard/Notifications folder. By using ADB you can copy a file there without opening the device’s UI, which is handy when you have many phones to configure or when the UI limits you to certain formats.

What you will need:

A PC (Windows, macOS or Linux) with platform‑tools (ADB) installed.
An Android phone with Developer options enabled and USB debugging turned on.
A custom sound file in .wav, .mp3 or .ogg format (max 5 MB is safe for most devices).
A USB‑C or micro‑USB cable that can transfer data.

Make sure the phone is charged above 30 % and that you are connected to a reliable Wi‑Fi network if you plan to download the sound directly on the device later.

1. Prepare the custom sound file

Choose a short, distinctive audio clip (e.g., 1–2 seconds). Long clips can be trimmed in any audio editor – Audacity, WavePad, or even an online tool.
Rename the file to something simple, such as my_alert.wav. Avoid spaces and special characters; Android may reject them.
Place the file in an easy‑to‑access folder on your PC, for example C:\Sounds\my_alert.wav (Windows) or ~/Sounds/my_alert.wav (macOS/Linux).

Why this matters: Android’s MediaStore scans the Notifications directory for files with supported extensions. A clean filename ensures the scan succeeds and the tone appears in the system picker.

2. Connect the device and verify ADB communication

Plug the phone into the PC via the data cable.
Open a terminal (Command Prompt, PowerShell, Terminal.app, etc.).
Run adb devices. You should see a line like RZ8M7XXXX device. If the status shows unauthorized, unlock the phone and tap Allow on the USB‑debugging prompt.
Once the device shows as device, you are ready to push files.

Tip: If the device does not appear, try switching the USB mode to “File Transfer (MTP)” or reinstalling the platform‑tools.

3. Transfer the sound file to the Notifications folder

First, ensure the target folder exists. Execute:
```
adb shell "mkdir -p /sdcard/Notifications"
```
Copy the file:
```
adb push "C:\Sounds\my_alert.wav" /sdcard/Notifications/
```
(Replace the Windows path with your actual location; on macOS/Linux omit the drive letter.)

Force Android to scan the new file so it appears in the media database:

adb shell am broadcast -a android.intent.action.MEDIA_SCANNER_SCAN_FILE -d file:///sdcard/Notifications/my_alert.wav

Verify the file is present:
```
adb shell ls -l /sdcard/Notifications/
```
You should see my_alert.wav listed.

If the ls output shows the file but it does not appear in the UI later, repeat step 3c to trigger the media scan.

4. Set the custom tone via the Android UI

On the phone, open Settings → Sound & vibration (the exact wording may differ on Samsung, OnePlus, etc.).
Tap Default notification sound or Notification tone.
Scroll to the bottom of the list – you should see my_alert (or the filename you chose). Select it.
Press OK or Save to confirm.

After confirming, Android will play the new tone for any standard notification (messages, system alerts, etc.).

5. Optional: Set the tone directly with ADB (useful for bulk deployments)

Some device manufacturers expose the system setting notification_sound as a writable key. You can try the following command; it works on many stock Android builds and on devices that accept a file‑URI.

adb shell settings put system notification_sound /sdcard/Notifications/my_alert.wav

If the command succeeds, you can verify the value:

adb shell settings get system notification_sound

The output should echo the same path. Some OEM skins (e.g., Samsung One UI) store the value in secure or global namespaces; you can try:

adb shell settings put secure notification_sound /sdcard/Notifications/my_alert.wav
adb shell settings get secure notification_sound

Why you might need this: When configuring many devices (e.g., in a small business) you can script the push and setting steps without touching each phone’s UI.

6. Verify the new tone works

Trigger a test notification. The simplest way is to send a message to yourself via a messaging app, or use the built‑in “Test notification” button if your device’s sound settings provide one.
If you prefer ADB, run:
```
adb shell am broadcast -a android.intent.action.TEST_NOTIFICATION
```
(Note: not all devices implement this broadcast; the UI test is more reliable.)
Listen for the custom sound. If you hear the expected clip, the process is complete.

7. Troubleshooting

7.1 The tone does not appear in the notification list

Make sure the file extension is supported (.wav, .mp3, .ogg).
Confirm the media scan broadcast succeeded. Re‑run step 3c and then check the UI again.
On some heavily customized OEM skins, the notification picker looks only in /system/media/audio/notifications. In that case you need root access; without root you must rely on the UI method.

7.2 ADB command to set the tone returns “SecurityException”

Some devices protect the notification_sound key. Use the UI method instead.
Alternatively, you can set the tone for a specific app using the app’s own settings (e.g., WhatsApp → Notifications → Custom tone).

7.3 The sound plays but is distorted or too loud

Android expects notification tones to be around 44 kHz, 16‑bit PCM. If your file is encoded at a higher bitrate, re‑encode it with an audio editor.
Reduce the volume of the file itself; Android adds its own volume control on playback.

8. Safety and best‑practice notes

Do not overwrite existing system files. Always copy to /sdcard/Notifications, never to /system unless you have a rooted device and know what you are doing.
Keep a backup of the original sound files you replace, in case you need to revert.
Avoid using copyrighted audio clips for system tones unless you have permission – personal use is fine, but redistribution may violate rights.
If you plan to deploy the same tone to many devices, script the ADB steps and test on a single device first.

9. Clean‑up (optional)

If you later decide to remove the custom tone, simply delete the file and clear the MediaStore cache:

adb shell rm /sdcard/Notifications/my_alert.wav
adb shell am broadcast -a android.intent.action.MEDIA_SCANNER_SCAN_FILE -d file:///sdcard/Notifications/

After deletion, the tone disappears from the picker. You can also revert to the default system tone via Settings → Sound → Default notification sound.

Wrap‑up

Adding a custom notification sound with ADB gives you precise control, works on any Android version that supports USB debugging, and requires no rooting. By following the steps above you can prepare the audio file, push it safely, make it selectable via the UI, or set it programmatically for bulk configurations. Should any hiccups arise, the troubleshooting section offers quick fixes, and the safety notes keep your device secure.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.