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

App does not remember fullscreen notification permission

Open
#907 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

Start by reading the app's call notification and fullscreen-permission handling, then reproduce the reported flow on the affected Android/MIUI setup: grant permission, wait for the next 24-hour period, and receive a call. Check whether permission state is being retained and whether the first call appears fullscreen without another prompt; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

bug needs triage
Checklist
  • I can reproduce the bug with the latest version given here.
  • 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 bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.
Affected app version

1.11.1

Affected Android/Custom ROM version

MIUI 2.0.16.0

Affected device model

Xiaomi Redmi Note 12 Pro

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Open app for the first time of the day/24 hour period.
Get asked to give fullscreen notification permission.
Give permission.
Repeat.

Expected behavior

First call of the day appears in fullscreen.
Am not asked to grant the same permission again.

Actual behavior

First call of the day does not show up on the screen, have to unlock phone and then click on app. This happens every fucking day.

Screenshots/Screen recordings

No response

Additional information

No response

Dominant language
Kotlin
Stars
1.4k
Forks
213
Avg merge
6d 21h
Merged PRs (30d)
11

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.