Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unanswered call time information on the notification screen.

Open
#838 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
android, kotlin
Domain
mobile

Research direction

The issue asks that the missed-call notification show when the call came in. Find where the app builds the missed-call notification and check whether it sets a timestamp, and read the three comments first to see whether the maintainers already agreed on an approach. Done means a missed-call notification on a device or emulator shows the call time, with no change to other notifications.

Written by the indexing model from the issue text.

Description

feature request needs triage
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 unanswered call notification does not display the time of the call on the notification screen. However, it would be very practical if it were visible.

Why do you want this feature?

To quickly see when they called us.

Additional information

No response

Dominant language
Kotlin
Stars
1.4k
Forks
213
Avg merge
5d 10h
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FossifyOrg/Phone

All issues in FossifyOrg/Phone

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.