Unanswered call SIM information on the notification 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
The payload names no files, so start by finding where the missed-call notification is built in the Kotlin Android code and whether the call's SIM information is already available at that point. Check how the app identifies the SIM for a call elsewhere, such as the call log. Done when a missed-call notification shows which SIM received the call, for a device with two SIMs.
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
In the missed call notification, the notification screen does not show which SIM card the call was from. For example, they call from SIM 2, and since I can't see it, I press call back and call from SIM 1. There's confusion.
Why do you want this feature?
To quickly see which SIM card they called us from.
Additional information
No response
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
openclaw/openclaw#172218 · 1 comment ·
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