Since I updated my fairphone 3, it’s been playing a really annoying sound ‘bleep bleep bloop’ about a second after I unlock it. I have vague memories of it doing this when I first got it, but it’s started again recently.
Going into sound settings and unchecking “screen locking sound” does not work. This just stops a different sound, a quiet ‘click’ which is much more tolerable anyway.
The only way I can get it to stop is by silencing “ring and notification volume”, but I actually would quite like to get notification sounds for texts and calls. Just not this infuriating unlock sound.
Anyone have any idea how to fix it, if not in sound settings?
Your link is to a Google Drive location that requires authentication with a Google account.
Would you consider providing a link that can be used anonymously? To do this, when sharing the file, use the “Get link” command and then, in the dialogue box, choose “Anyone with the link”.
However, be aware that your account name and identifier will be visible to those accessing the file.
For occasional use, consider creating an account that you don’t mind making public.
One can use a totally anonymous service, but those often carry a more or less undesirable payload.
If you want to take the time, you could run through the collection of sounds provided by the system to see if it’s any of those. Just go to Settings > Sound > Default notification sound and listen to each one. If you recognise one of them, we might be able to find it in the phone’s settings.
It’s not in the sounds offered on the FP4 for A12, I’ve just been through them …
That’s because they’re the same. Owlbreeze just changed the access rights.
Since it wasn’t mentioned yet … an internet search wants to tell me that some people could attribute an unlock sound to NFC getting unlocked.
I don’t use NFC, so I can’t point directly to anything, but perhaps you could disable NFC to see whether the sound survives.