Here is the sound on YouTube: https://www.youtube.com/watch?v=-H5ZOVelLEw *The sound video was uploaded by a person who has the same problem as me, though he has a smartphone of another model. In general, there are not few people asking the question but the solution still has not been found. I would like to place the links to the people's questions but I don't have enough reputation to put more than 2 links here.* I checked the /system folder and **/system/media/audio/ui** folder particularly and found the sound fallbackring.ogg only in the latter. But this is not the sound produced by the volume buttons (as I have learnt it is an input call sound playing when the Bluetooth is turned on and used). Then I have found the page http://forum.xda-developers.com/showthread.php?t=2378177 where the screen unlock system sound is replaced. The sound is situated in **/system/framework/framework-res.apk**. So I copied the framework-res.apk file and all the .apk files from /system/priv-app (as in the folder there are .apk files whose names sound like system: SystemUI.apk, Settings.apk, IputDevices.apk and etc. on my smartphone) to my PC, converted them to ZIP and searched there for any .ogg, .mp3 and .wav files. I have found some .ogg and .mp3 system sounds but not the volume button system sound and I have also found files like open.wav, open_bluetooth.wav, success.wav and failure.wav but I managed to play them with VLC media player neither on Windows nor on Linux and, still, their names have nothing in common with the volume button. So here is my small investigation. Could someone, please, give me a tip where the annoying beep sound can be kept? Or, maybe, is it produced with hardware of the smartphone? I will appreciate any help.

It is possible to customize the notification sounds for Google calendar for Android cellphones. For example, a ***task***-notification can sound like a windchime playing and and a ***calendar*** notification can could sound like a car horn. Are ***task*** notifications a subset of of ***calendar*** notifications? Are ***task*** notifications mutually exclusive from ***calendar*** notifications? Suppose that there is a Google Calendar ***event*** at 1:00PM on Monday. Will the ***event*** notification play the ***task*** sound or will the ***event*** notification play the ***calendar*** notification sound?

Suppose I am connected to my Bluetooth speaker. I want to play my Youtube Music/Music Player on the speaker. Now, if I turn on Instagram reels, what happens is the Music Player gets paused and the audio output happens through the Bluetooth speaker. What I want is for my Insta sound output should be through my phone's speaker. **Is there any way by which this can be achieved?** There can be many more use cases for this but this is just a small example.

How can I go about obtaining the default Android keyboard button press sound file? If it is not readily obtainable, how can I obtain a similar 'click' sound effect? -Thanks

I just purchased a Samsung Galaxy S22. It runs Android 12 and One UI 4.1. What I am trying to do is use a custom notification sound for my text messages (Google Messages). I want a custom sound for one specific person and another for everyone else. I had this previously on my Galaxy S8. Unfortunately this does not work for me. I have added the sounds I wish to use to my phone's storage. This includes custom ringtones. Those do work as I am able to select them when choosing a ringtone. I can see them in my list of available ringtones. But the sounds I have added for notifications do not appear in the list of available notification sounds. I have tried placing them in the following locations: - /root/sdcard/Notifications - /root/sdcard/Ringtones - /root/sdcard/Android/media - /root/sdcard/Android/media/Notifications It's this still possible to do? If so, what am I missing?

I am using Android on a Realme 6 phone. When reading interface elements out with TalkBack, it wastes a lot of time reading out what is on the screen as I explore by touch or use linear navigation. It would be nice if TalkBack had a feature where you could switch back and forth between normal mode and another "quick cue" mode. In this quick cue mode, when TalkBack encounters an element, it plays a very brief sound corresponding to the type of widget encountered. The user learns to recognize these sounds and can browse quickly through the interface without being distracted, closer to how a seeing user of the interface would. When the user wants to know what type of element the sound corresponds to, the user swipes left then up then right, to be reminded. Otherwise scrolls quickly till they get to what they want, quickly building a mental idea of what's there. To read out the text of a button, since the sound cue alone is played out, the user swipes right then up the left. The button text, which takes longer to be read out, is then read aloud. Or the user can switch back to normal mode and proceed. The sound cues may correspond to things like "time", "share button", "tool button", "add button", "modify button", "delete button", "done button", "submit button", "text widget", "caption", "text entry widget", and so on. Markup, following a given markup XML prefix for the standard set of standardized sounds included, would be supplied, and available in the source code to support this, for the benefit of these very blind users so that they may be able to hear these standard assigned cues for faster less stressful browsing in TalkBack than I'd text would have to be read out everywhere. Many times when we view a time widget we don't read the time out. Similarly, when viewing a share button, we don't read out "share" to ourselves, we simply recognize the button. With a sound cue, the non-seeing users experience corresponds more closely to a seeing user's experience. This would thus enhance the blind user's ability to use a variety of apps, including apps that were designed primarily for seeing users, but that included blind user support. Perhaps, in many cases, a separate interface should be designed and made accessible to blind users in apps. However, it is not guaranteed that developers would do this, although it would only be right if they were pushed to do this through development tools, and, in this case, how would a blind user access the separate blind user-specific interface to the given apps supporting this feature. There could be a special swipe gesture in TalkBack to switch between normal mode and quick cue mode. For instance, up then right then down, or up then left then down. Does TalkBack currently support such a behavior, or does anyone know whether Google and Android have plans to support this behavior for blind users in the future? Thanks.

I would like to know what Android does to support blind Android users with sort attention span. One of the problems with these users, is, that while the user interface talks, the sound of the reading voice itself distracts them to the point where they focus on the sounds and not on the letters that make up the words. In this manner, they can never understand the words, that are being spoken out. The words are just spoken out too fast, and everything just goes too fast for them to keep track of everything. What these users need, besides linear navigation in TalkBack, is a way to control the speed at which words and pauses are pronounced. They need to be able to drag out the pronunciation of the words over a long length of time. This slows everything down. Never mind. The point is that they must understand. Not only, they must be able to memorize and keep track of what goes by while it is being spoken. Ideally these users should be able to control, not only swiping forward and backward between one word and another to navigate, but also, the length of time for each letter to be pronounced. They should have access to quadruple tap and drag a slider to control the speed, which they need to change as needed while everything is read. Because, at any given point in time, their ability to focus on longer pronunciations or shorter pronountiations as reading speed changes, and there is always, at any given point of time, matching their awareness and awakeness, a right, optimal, speed, with which to read the words out aloud. The same goes for sound clues. These, just like the words, should also be sounded out longer or shorter, to allow the blind user with attention problems to have the time they need, in their slowness, to focus on them, and say to themselves, "yes, I've heard the sound i recognize as being such and such", and this must take place before the sounds finishes. The user must be able to talk to themselves during the sound, not after, when the sound had finished and the user has forgotten about it before they were able to say anything to themselves, about it. So, my question is, does Android have anything to support this feature, which would be indispensably necessary to make the device accessible to blind users with sort attention span? Thanks.

I installed some custom notifications sounds on my BLU Advance 5.5 running Android 6.0 a few months ago and they've worked fine for a really long time until when recently all my notification sounds went back to default, so I try to change back to any of the old custom sounds that I'd been using, but they won't show up in the options. My custom ringtone sounds didn't change and still work fine, but my notification sounds just won't show up. I've tried rebooting, renaming, changing the location of the file(s), and clearing the cache, but nothing works. I don't know what to do anymore.

I noticed several years ago after getting a new phone that newer versions of the Android software seem to play my notification sound three times. Prior to this phone it only ever played once. It gets pretty annoying and I was wondering if there's any way to configure this so the sound only plays once? Or is this hard-coded? It has happened with my last three phones, so it's likely a feature of newer versions of the Android software. I have a Samsung Galaxy J7 running Android 7.1.1. Whenever I get a notification sound (custom WAV sound that is just the door chime from Star Trek TNG playing once) for an email, app, etc, instead of just playing once, it plays three times in a row. I have not been able to locate any settings that would allow me to configure how many times it plays.

In the clock app (bedtime tab, sleep sounds) I can choose a device sound Deep space. I would love to use it as my alarm sound. Every file-exploring app that I have used hasn't found this file. How can I?

I have a Samsung Galaxy Tab A with S pen. I am trying to add additional alarm sounds to the list used by the native alarm clock app provided by Samsung, as these lack personality and often fail to wake me. I copied all the ringtones from my phone to Dropbox, and then exported them to the Ringtones folder with the Dropbox export feature. Of the sixty-odd ringtones so exported, exactly four appeared in the alarm clock list of available sounds. I can discern no pattern in the ringtones so appearing. All 60 are all of the same file type, .mp3s. They are not especially long or short, nor large or small. They are neither clustered together under any file sort view nor evenly spaced. I have played all the files with six different player apps, all such apps that I have installed. With one exception, every app played all the files without difficulty. The exception is the Sound Picker, invoked via the plus sign at the top of the clock's list of alarm sounds. The Sound Picker shows the four ringtones the clock sees, and four more, again with no obvious pattern; also a bunch of short snippets of some lecture that I do not recognize. The sound picker allows me to add exactly one of these new sounds to the clock's list. Adding another removes the one previously added. I am completely befuddled by this and have no idea how to proceed further. Any insight or diagnostic suggestions welcome.

I have many calendars on Google Calendar: 1. Hospital appointment (blue) 2. Birthday calendar (yellow) 3. Payday calendar 4. My career's calendar They are separated by the colours to make it easy for identification, but **I would like to separate the notification sound to go with the colours**. Some more urgent like an alarm, some less aggravating but still just a buzz or something. It's confusing that they all use the same tone, and although via some apps I can differentiate these between text, voicemail, and Facebook, etc, it's not quite ideal. I have been looking through all calendar apps I can find for this thing.

This question is basically the same as [this one](https://android.stackexchange.com/questions/89/how-do-i-disable-the-click-sound-on-the-camera-app) but the canonical answer for that post is not compatible with my particular device for which a discussion and a solution can be found below. I would often like to use the [Samsung Galaxy SIII Neo](http://www.gsmarena.com/samsung_i9300i_galaxy_s3_neo-6289.php) stock Camera app but would like to keep the sound it makes while pictures are shot on silent (so that when I take a shot people are not distracted by the sound so that the resulting pictures taken look more natural). However, I've figured out that to turn such sound off, out of the volume settings Ringtone, Notifications, Media, and System, it is the Ringtone volume setting which must be turned off for this to take place (click on any of the volume hardware buttons and then on the volume settings cogwheel to see these). Unfortunately, setting the Ringtone to silent means no sound will be made when a phone call is received. So, I would like to know whether newer phones have a Camera setting menu list entry for enabling or disabling the sound specifically for the Camera application. And, if not, then I would like to know where to place a feature request width Samsung for this to be implemented in future releases of the stock Camera software. Anyways, I think, as a hack, if one knew where the mp3 sound file for the camera app is stored, one could just deleted (or perhaps replaced it with an mp3 file producing no sound to resolve the problem). Anyone know where I could find such a file? --- **UPDATE**: I've tried [rooting my device](https://android.stackexchange.com/questions/102430/what-are-the-advantages-of-enabling-or-disabling-samsung-knox) and then following [this solution](https://android.stackexchange.com/questions/89/how-do-i-disable-the-click-sound-on-the-camera-app) but I still get an error message saying the filesystem is read-only. Not sure if [Samsung KNOX](https://android.stackexchange.com/questions/102430/what-are-the-advantages-of-enabling-or-disabling-samsung-knox) is causing this. Thank you for your replies. --- **UPDATE**: Remounting the system with the following command as root: mount -o remount,rw /system Allowed me to rename the file, but it seems it's the wrong file as the stock Camera app still produces a snap sound when taking a picture after the rename. Candidate files related to the stock Camera app under /system/media/audio/ui could be the following: - Cam_Start.ogg - Cam_Stop.ogg - Camera_click_short.ogg - Camera_click.ogg - Camera_empty.ogg - camera_focus.ogg - Camera_Timer_2sec.ogg - Camera_Timer.ogg I've tried renaming both Camera_click.ogg and Camera_click_short.ogg to Camera_click.ogg.bak and Camera_click_short.ogg.bak but no luck! Even after rebooting the phone, the stock Camera application still produces a sound when a picture is taken with the Ringtone Volume enabled. The Camera_empty.ogg sound file produces no sound; ideally I would like this one to play when the camera takes a picture. Anyone know where the problem may be and how to fix it? --- UPDATE: After installing the BusyBox app in order to have the Unix find tool and then running: find / -name '*.ogg' > out.txt the contents of out.txt were the following: /storage/emulated/legacy/Ringtones/hangouts_message.ogg /storage/emulated/legacy/Ringtones/hangouts_incoming_call.ogg /storage/emulated/legacy/Notifications/Calendar Notification.ogg /storage/emulated/0/Ringtones/hangouts_message.ogg /storage/emulated/0/Ringtones/hangouts_incoming_call.ogg /storage/emulated/0/Notifications/Calendar Notification.ogg /mnt/shell/emulated/0/Ringtones/hangouts_message.ogg /mnt/shell/emulated/0/Ringtones/hangouts_incoming_call.ogg /mnt/shell/emulated/0/Notifications/Calendar Notification.ogg /system/media/audio/alarms/Alarm_Day_by_day.ogg /system/media/audio/alarms/Alarm_Morning_flower.ogg /system/media/audio/alarms/Dawn_chorus.ogg /system/media/audio/alarms/Daybreak.ogg /system/media/audio/alarms/Sea_breeze.ogg /system/media/audio/alarms/Serene_morning.ogg /system/media/audio/alarms/Springtime_memories.ogg /system/media/audio/alarms/Ticktac.ogg /system/media/audio/alarms/Walk_in_the_forest.ogg /system/media/audio/notifications/Beep_once.ogg /system/media/audio/notifications/Hang_drum.ogg /system/media/audio/notifications/Harp_glissando.ogg /system/media/audio/notifications/S_Bubbles.ogg /system/media/audio/notifications/S_Charming_bell.ogg /system/media/audio/notifications/S_Chirps.ogg /system/media/audio/notifications/S_Dew_drops.ogg /system/media/audio/notifications/S_Flowers.ogg /system/media/audio/notifications/S_Good_News.ogg /system/media/audio/notifications/S_Harmonics.ogg /system/media/audio/notifications/S_Knock.ogg /system/media/audio/notifications/S_On_time.ogg /system/media/audio/notifications/S_Opener.ogg /system/media/audio/notifications/S_Postman.ogg /system/media/audio/notifications/S_Pure_Bell.ogg /system/media/audio/notifications/S_Temple_bell.ogg /system/media/audio/notifications/S_Tickety_tock.ogg /system/media/audio/notifications/S_Whistle.ogg /system/media/audio/notifications/Sweet_favour.ogg /system/media/audio/notifications/Whisper.ogg /system/media/audio/ringtones/A_rustling_in_the_trees.ogg /system/media/audio/ringtones/Basic_bell.ogg /system/media/audio/ringtones/Basic_tone.ogg /system/media/audio/ringtones/Beep-beep.ogg /system/media/audio/ringtones/Beep_once.ogg /system/media/audio/ringtones/Blowing_dandelion_seeds.ogg /system/media/audio/ringtones/Break_of_day.ogg /system/media/audio/ringtones/Breeze.ogg /system/media/audio/ringtones/Bugs_story.ogg /system/media/audio/ringtones/Chime.ogg /system/media/audio/ringtones/Drifting_downstream.ogg /system/media/audio/ringtones/Ecliptic.ogg /system/media/audio/ringtones/Flying_in_the_sky.ogg /system/media/audio/ringtones/Fog_on_the_water.ogg /system/media/audio/ringtones/Glissando_tone.ogg /system/media/audio/ringtones/Ice_blue_tone.ogg /system/media/audio/ringtones/In_your_mind.ogg /system/media/audio/ringtones/Journey.ogg /system/media/audio/ringtones/Leisure_time.ogg /system/media/audio/ringtones/Over_the_horizon.ogg /system/media/audio/ringtones/Popcorn_tone.ogg /system/media/audio/ringtones/Quantum_bell.ogg /system/media/audio/ringtones/Rainbow.ogg /system/media/audio/ringtones/Rainy_day.ogg /system/media/audio/ringtones/Rays_of_the_sun.ogg /system/media/audio/ringtones/Rolling_tone.ogg /system/media/audio/ringtones/Scampering_tone.ogg /system/media/audio/ringtones/Writing_adventure.ogg /system/media/audio/ui/Alert_on_call.ogg /system/media/audio/ui/Auto_focus.ogg /system/media/audio/ui/Auto_focus_error.ogg /system/media/audio/ui/Birdsong_by_the_lake.ogg /system/media/audio/ui/Call_Connect.ogg /system/media/audio/ui/Cam_Start.ogg /system/media/audio/ui/Cam_Stop.ogg /system/media/audio/ui/Camera_Timer.ogg /system/media/audio/ui/Camera_Timer_2sec.ogg /system/media/audio/ui/Camera_empty.ogg /system/media/audio/ui/Charger_Connection.ogg /system/media/audio/ui/Dialer_new.ogg /system/media/audio/ui/Dock.ogg /system/media/audio/ui/Effect_Tick.ogg /system/media/audio/ui/Fairy_fountain.ogg /system/media/audio/ui/Highlight.ogg /system/media/audio/ui/HoverPointer.ogg /system/media/audio/ui/KeypressDelete.ogg /system/media/audio/ui/KeypressInvalid.ogg /system/media/audio/ui/KeypressReturn.ogg /system/media/audio/ui/KeypressSpacebar.ogg /system/media/audio/ui/KeypressStandard.ogg /system/media/audio/ui/Lock.ogg /system/media/audio/ui/Lock_none_effect.ogg /system/media/audio/ui/LowBattery.ogg /system/media/audio/ui/New_chat.ogg /system/media/audio/ui/Pen_att_noti.ogg /system/media/audio/ui/Pen_att_noti1.ogg /system/media/audio/ui/Pen_att_noti2.ogg /system/media/audio/ui/Pen_att_noti3.ogg /system/media/audio/ui/Pen_det_alert.ogg /system/media/audio/ui/Pen_det_beep1.ogg /system/media/audio/ui/Pen_det_beep2.ogg /system/media/audio/ui/Pen_det_beep3.ogg /system/media/audio/ui/Pen_det_beep4.ogg /system/media/audio/ui/Pen_det_beep5.ogg /system/media/audio/ui/Pen_det_noti.ogg /system/media/audio/ui/Pen_det_noti1.ogg /system/media/audio/ui/Pen_det_noti2.ogg /system/media/audio/ui/Pen_det_noti3.ogg /system/media/audio/ui/PowerOn.ogg /system/media/audio/ui/S_Beam_end.ogg /system/media/audio/ui/S_Beam_error.ogg /system/media/audio/ui/S_Beam_start.ogg /system/media/audio/ui/S_HW_Touch.ogg /system/media/audio/ui/S_SIP_Backspace.ogg /system/media/audio/ui/Sent_chat.ogg /system/media/audio/ui/Serenity.ogg /system/media/audio/ui/Shutter.ogg /system/media/audio/ui/Shutter_multiple.ogg /system/media/audio/ui/Sparkling_mist.ogg /system/media/audio/ui/TW_Battery_caution.ogg /system/media/audio/ui/TW_Battery_swelling_warning.ogg /system/media/audio/ui/TW_Call_Disconnect.ogg /system/media/audio/ui/TW_SIP.ogg /system/media/audio/ui/TW_Silent_mode_off.ogg /system/media/audio/ui/TW_Touch.ogg /system/media/audio/ui/TW_Volume_control.ogg /system/media/audio/ui/The_secret_forest.ogg /system/media/audio/ui/Undock.ogg /system/media/audio/ui/Unlock.ogg /system/media/audio/ui/Unlock_none_effect.ogg /system/media/audio/ui/VideoRecord.ogg /system/media/audio/ui/Voice_processing.ogg /system/media/audio/ui/Voice_start.ogg /system/media/audio/ui/Voice_stop.ogg /system/media/audio/ui/WirelessChargingStarted.ogg /system/media/audio/ui/Zero_Clickr_Ready.ogg /system/media/audio/ui/airbutton_close.ogg /system/media/audio/ui/airbutton_open.ogg /system/media/audio/ui/camera_focus.ogg /system/media/audio/ui/lens_flare_lock.ogg /system/media/audio/ui/lens_flare_unlock_silence.ogg /data/media/0/Ringtones/hangouts_message.ogg /data/media/0/Ringtones/hangouts_incoming_call.ogg /data/media/0/Notifications/Calendar Notification.ogg At this stage I'm not sure whether the stock Camera app is really taking the shutter sound from one of these .ogg files or whether the actual .ogg file is hardcoded into the stock Camera app's binary file.

I have a brand new Galaxy S10. I would like to keep the phone in mute mode but want the phone to vibrate if there is any Call, SMS or any WhatsApp notification. How to do this? I do not wish to root the phone as of now.

I am running Android KitKat 4.4.2 on a Samsung Galaxy SIII Neo. I have installed the [Screen Lock Pro](https://play.google.com/store/apps/details?id=com.iglint.android.screenlockpro) app which allows you to log off by clicking a home screen icon or tapping on a notification drawer entry. Now I would like to know whether I can leave the sound volume on, but disable the sound that is emitted when the user logs out / logs in. I presume this can be done by renaming a sound file somewhere [using a similar trick as can be done with the camera app](https://android.stackexchange.com/questions/102420/how-to-make-stock-camera-app-silent-when-shot-is-taken-without-preventing-phone/102469#102469) . Thank you for your replies. --- NOTE: This question I am asking is the same as [this one for Windows 7 PCs](https://superuser.com/questions/988399/how-to-disable-the-sound-when-logging-off-locking-switching-users) , but relates to Android devices instead.

I upgraded to Oreo about a week ago and I've noticed that all my apps' alerts now sound like my SMS alert. This means that I either get constantly bothered by unimportant notifications (It's your turn in a game!, etc.), or I miss important notifications like most SMSs, because now now unimportant and important notifications sound the same. With the new notification channels I can set a custom sound manually, but the last thing I want to do is customise every single notification on my phone, and I also don't know where the sound files are for the original sounds. It's just too much work. How can I get Oreo to behave like Nougat in this regard?

You know that annoying beeping you hear when you call someone, waiting them to pick up? I am completely sick of it and want to customise it on my Huawei Android phone. The question is: how do I do that? Thank you

I have an LG g5 running Android 7.0. every now and then, several times per day, my phone makes a sound that belongs to no alert (that can be seen on screen at least). As best as I can describe it - it's like a mailbox opening and mail being taken out and the door being closed. It began a week ago and I cannot think what is causing it. What can I do? Thanks

I have two very basic questions about my Samsung Galaxy S3 phone. In its default configuration: 1. Every now and then the phone whistles. (a) What does this mean? (b) How do I change this or turn it off permanently? 2. A few months ago the operating system did an OTA (over-the-air) update. Now every now and then, besides this whistling, I also hear a bicycle bell ringing. (a) What does this mean and how does this differ from the whistling, that is, how is the information conveyed by the whistling different by the information conveyed by the bicycle bell ringing? (b) How do I change this sound or turn it off altogether permanently? Thanks.

Last year I bought an RCA Voyager (tablet) running android 6.0.1 (marshmallow), and between now and then I have added custom tunes to my 'Alarms' folder to spice things up a bit. My problem is that I accidentally added an alarm that I do not wish to use. I searched the whole clock app for a remove or delete option, but could not find one. I deleted the tone directly from the 'Alarms' folder, but it is still registered in the list (only it now uses the default sound). I attempted clearing the application's data, that didn't work either. I downloaded an app for removing ringtones and alarm tones, but it would not even run. I went as far as installing an app that can access the /system directory, but it was too complex in there and I did not want to break anything. My device is not rooted. So this really boils down to: is it at all possible to remove custom alarm tones?