When using the timer, you cannot take a picture ahead of time, but only interrupt the process
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 30/100
Research direction
The payload names no files or tests. Start by reproducing the timer flow in the app: begin a countdown, then check that the shutter button turns into a cancel button. Decide whether a second press during the countdown should capture immediately, and confirm the maintainers agree before coding. Done means a press during the countdown takes the photo now, and the existing timer behaviour still works when nothing is pressed.
Written by the indexing model from the issue text.
Description
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 propose to discuss the feasibility of changing the current functionality of creating a photo using a timer.
Why do you want this feature?
I usually take pictures using a three-second delay. But I have situations when I have already started the countdown and I need to take a picture at that very moment, without waiting for the countdown to end (because then the right moment will be missed). At the moment, it is impossible to take a picture like that, because the camera shutter button changes to a cancel button after the countdown has started.
Additional information
Fossify Camera 1.1.0 (6) f-droid (Jul 28, 2025)
- Dominant language
- Kotlin
- Stars
- 473
- Forks
- 56
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Camera
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FossifyOrg/Camera#347 ·
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
FossifyOrg/Camera#346 · 1 comment ·
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Camera#339 · 1 comment ·
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 25/100
FossifyOrg/Camera#338 ·
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 30/100
FossifyOrg/Camera#335 ·
All issues in FossifyOrg/Camera
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
enorm-labs/event-junkie#3166 ·
Maintainers usually reply within 1 day
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
theopenconversationkit/tock#2113 ·
Maintainers usually reply within 1 day
-
Bayern feature:Application ready web
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
digitalfabrik/entitlementcard#3176 ·
Maintainers usually reply within 7 days