Better "generic" icons for numbers in call history
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- mobile-dev
Research direction
This is a feature request for call-history icons in an Android dialer, and the body shows no code paths or files. Design is still open: landline versus mobile detection, or new versus seen-before numbers, and both need a decision and a number-classification approach first. The one comment has gone 232 days without a reply. Before writing code, get a maintainer to pick one direction and say where the icon logic lives.
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
A basic implementation - differentiate landline calls from mobile calls. Artist's impression:
Another idea could be to have the icon show for numbers that are "new" vs have been seen before (in call history). This could also be expanded to indicate spam numbers in future:
Why do you want this feature?
Currently, most of the numbers in my call history begin with '0' (or '+' for country code)
The icon doesn't show much useful info:
Additional information
Cheers
- 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
-
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