Custom Shutter Sound
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
The issue names no files or tests, so start by finding where the app currently plays its shutter sound and where its settings screens are defined in the Kotlin Android code. The work needs a way to pick an audio file, persist its location, and fall back to the default sound when that file is missing. It is done when a chosen sound plays on capture and a missing file silently uses the system default. Agree the settings design with maintainers before writing code.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
I would like to be able to change the shutter sound using an audio file on my device. If the custom file goes missing, gets deleted, or is moved, the app should automatically replace it and fall back to the default system sound.
Why do you want this feature?
I feel like this feature could bring some quality of life and give users the ability to add their own charm to the app, and including a fallback in case something happens to the audio file
Additional information
No response
- Lenguaje dominante
- Kotlin
- Estrellas
- 473
- Forks
- 56
- Merge medio
- 1 d 12 h
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Camera
-
Moveable Recording TimerAbiertofeature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
FossifyOrg/Camera#358 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
FossifyOrg/Camera#347 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
FossifyOrg/Camera#346 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Camera#339 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
FossifyOrg/Camera#338 ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Camera
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
SLNE-Development/surf-chat#134 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100