Add "double-tap to exit" when on the call screen.
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the call-screen entry point and how it handles Android's back button. Implement the requested double-tap behavior so a single tap does not exit the full-screen call view, and verify that a double tap exits the view without ending the call.
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
While on a call, add the feature of having to double-tap Android's "back" button to exit the call's full-screen.
Why do you want this feature?
I have noticed that in many occasions, elderly people mistakenly hit the Android's "back" button to end the call, instead of the correct, default red button. Then they exit the call screen, but the call is not ended, and it is very complex for them to finally hang up the phone when it is on the background.
Additional information
At first I thought of requesting adding an option to completely disable the "back" button's functionality when on call's full-screen, but having to double or triple tap it should do the job.
I recently have chosen the app because of some features that make it friendly for elderly people, like the confirmation dialogue before making the call, choosing bigger letters, and having an all-time visible alphabetic index at the contacts, so the feature I request should complement perfectly the accessibility for the elderly. (These are actually, exactly all the things that caused problems in my case)
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 213
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 14
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/Phone
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FossifyOrg/Phone#922 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Phone#914 · 2 comments ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Phone#889 ·
Maintainers usually reply within 4 days
-
feature request needs triage
Difficulty 2/5 Half a day Newbie friendliness 60/100
FossifyOrg/Phone#822 ·
Maintainers usually reply within 4 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FossifyOrg/Phone#921 ·
Maintainers usually reply within 4 days
All issues in FossifyOrg/Phone
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
enorm-labs/event-junkie#3301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1017 ·
Maintainers usually reply within 1 day
-
enhancement impact:U1 later P3 reach:R2 size:S
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100