Incoming call screen is shown underneath the fingerprint scanner

[mijorus]

Checklist

• [X] I can reproduce the bug with the latest version given here.
• [X] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• [X] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• [X] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• [X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [X] This issue contains only one bug.
• [X] I have read and understood the contribution guidelines.

Affected app version

1.1.1

Affected Android/Custom ROM version

Android 14

Affected device model

nothing phone 1

How did you install the app?

Google Play Store

Steps to reproduce the bug

Received a phone call with the screen locked

Expected behavior

The UI should be interactive

Actual behavior

The incoming call UI is shown underneath the FP scanner

Screenshots/Screen recordings

No response

Additional information

This is a long standing bug for this dialer app, I'm opening this hoping that will finally be fixed

[Guarmanda]

I have the same issue with lineageos. I have to unlock my screen before answearing

[piterq]

The same issue here on hyperos 2.0 (Xiaomi 13T). Fossify Phone version: 1.4.0. Sometimes I see the unlock screen when the phone is ringing, so I must unlock it first to answer or reject the call.

[da-anda]

same issue on a Moto Edge Neo 30 running their "stock" Android. On every incoming call one first has to unlock the screen using the default pin/pattern

[bugsbugsbux]

i have the same problem as #296 meaning the screen stays turned off (but it rings) and when i press the power button to wake the phone the call is terminated!

moto g 05, android 15

[eminfedar]

Same issue, pretty annoying, makes me lose couple of seconds while trying to answering the phone.

[naveensingh]

People on Xiaomi phones may try the following:

• Disabling battery restrictions for Fossify Phone in system settings (see this comment)
• Enabling Show on Lock screen in Other permissions
• Solutions available on https://dontkillmyapp.com/xiaomi

[GazaShaggy]

I also have this issue using Pixel 9 Pro and fdroid version

[da-anda]

I tried to find the cause for the issue and used AI to find possible root causes. After checking every suggestion by the AI, the last crucial requirement it gave for the fullscreen lock screen overlay to work was that the app HAS TO request the USE_FULL_SCREEN_INTENT intent for anything Android 12 and above. The current manifest does not seem to contain this.

Since this was suggested by AI, there is no guarantee it is true. But maybe a dev (@naveensingh ?) can verify or provide a test build?

Suggested code change by the AI:

<!-- 
CRITICAL: This permission is mandatory for Full-Screen Intents to work 
on devices running Android 12 (API 31) and higher.
Without this, the system ignores the setFullScreenIntent() call.
-->
<uses-permission android:name="android.permission.USE_FULL_SCREEN_INTENT" />

<!-- Example placement in the manifest: -->
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="org.fossify.phone">

    <!-- Add the USE_FULL_SCREEN_INTENT permission here -->
    <uses-permission android:name="android.permission.USE_FULL_SCREEN_INTENT" />

    <!-- ... existing permissions (e.g., READ_CONTACTS, CALL_PHONE) ... -->
    
    <application
        <!-- ... -->
    </application>
</manifest>

[naveensingh]

Yeah, that permission is needed. It could also be a faulty check in the code that decides when to show the activity (it currently does it manually instead of relying on the system to pick between activity vs notification).

I remember running into some complication when I was fixing it a while back. I'll send a test build as soon as I'm home.

[naveensingh]

A test build with a potential fix is available here. Please let me know if it works.

[da-anda]

@naveensingh thanks much. Installed it on the affected phone and from a very brief test it seems to be working. I'll use it for a couple days and report back if the issue popps up again.

[GazaShaggy]

@naveensingh Thanks installed on mine as well and appears to function.

[eminfedar]

According to my tests, it is working too. Nothing Phone (1). Thanks @naveensingh . We are waiting an official release for this.

[WebworkrNet]

A test build with a potential fix is available here. Please let me know if it works.

Just for your information: The link currently leads to a 404 error.

If the test build was only available temporarily, it doesn't need to be restored as far as I'm concerned. I just noticed it.

[da-anda]

A test build with a potential fix is available here. Please let me know if it works.

Just for your information: The link currently leads to a 404 error.

build artifacts are usually not kept for long on github

[tswistak]

Just for your information: The link currently leads to a 404 error.

It works on my end. Maybe you have a misconfigured adblocker or something like this? Or maybe you're downloading on the device where you aren't logged into GitHub? Downloading artifacts works only after being logged in.

[WebworkrNet]

A test build with a potential fix is available here. Please let me know if it works.

Just for your information: The link currently leads to a 404 error.

build artifacts are usually not kept for long on github

Thanks for the information! 👍

A ZIP file is now available for download again.

This fact is certainly not known to everyone and was also new to me.

@naveensingh I would find it helpful if a note to this effect were included when setting build links in the future. :-)

[da-anda]

build artifacts are usually not kept for long on github

Thanks for the information! 👍

A ZIP file is now available for download again.

This fact is certainly not known to everyone and was also new to me.

@naveensingh I would find it helpful if a note to this effect were included when setting build links in the future. :-)

AFAIK projects can specify for how long. But I could also be mixing things up with Gitlab. My brain is a bit foggy atm (too much stress)

[WebworkrNet]

Just for your information: The link currently leads to a 404 error.

It works on my end. Maybe you have a misconfigured adblocker or something like this? Or maybe you're downloading on the device where you aren't logged into GitHub? Downloading artifacts works only after being logged in.

I wasn't logged in before. That must have been the cause. 👍 Thanks

[naveensingh]

Thanks for testing!

[naveensingh]

We are waiting an official release for this.

It's up now: https://github.com/FossifyOrg/Phone/releases/tag/1.8.0

I would find it helpful if a note to this effect were included when setting build links in the future. :-)

@WebworkrNet You got it.

[da-anda]

thank you so much Naveen 👍. Much appreciated

[zanyshh]

We are waiting an official release for this.

It's up now: https://github.com/FossifyOrg/Phone/releases/tag/1.8.0

I would find it helpful if a note to this effect were included when setting build links in the future. :-)

@WebworkrNet You got it.

Thank got the api updated to 36 🥰🥰