Allow launching the application from the lockscreen shortcut without unlocking the phone
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests or entry points. It asks that the camera open from the lock screen without unlocking, while limiting access to previously captured media. Start by deciding how the app should behave on the lock screen and how gallery access is restricted, which is a design question for maintainers. Done means a maintainer-agreed approach, then an implementation that passes the existing test suite.
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
The builtin camera app from Samsung or Google can be opened without unlocking the phone, either by double-clicking on the power button or via a lockscreen app shortcut.
When using configuring those to open Fossify Camera instead, this require unlocking the phone.
Why do you want this feature?
It would be convenient to be able to take pictures without needing to enter the pin.
Additional information
This would require limiting the access to pictures/videos so that you cannot see them without unlocking the phone unless there were captured before closing the app.
- Dominant language
- Kotlin
- Stars
- 473
- Forks
- 56
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 8
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 3/5 1-2 days Newbie friendliness 45/100
FossifyOrg/Camera#358 ·
Maintainers usually reply within 1 day
-
Custom Shutter SoundOpenfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FossifyOrg/Camera#357 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FossifyOrg/Camera#347 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
FossifyOrg/Camera#346 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Camera#339 · 1 comment ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Camera
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-brownfield#492 · 1 comment ·
Maintainers usually reply within 4 days
-
fix: retain the best partial noise-correction solutionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
world-federation-of-advertisers/cross-media-measurement#4653 ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kabirvashisht4-glitch/Vet#22 ·
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
djazairdev/wilayas#23 ·
Maintainers usually reply within 1 day