Calls are automatically rejected

[Glitchy-Tozier]

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.5.1 & 1.6.0

Affected Android/Custom ROM version

14 & 15

Affected device model

Fairphone 5

How did you install the app?

Google Play Store

Steps to reproduce the bug

1. Install app
2. Try to have someone call me
3. See bug: No call ever gets patched through. (This isn't the same thing as "i can hear a call but can't accept it." Calls go straight to voice mail, without ringing a single time)

Expected behavior

A notification/full screen option to pick up should appear.

Actual behavior

• The caller doesn't hear the call ringing but immediately is directed to voice mail, as if I had immediately hung up or had no service
• I only get an SMS after the fact, telling me I had been called.

Screenshots/Screen recordings

No response

Additional information

• I have a dual-SIM setup. Calling the first (physical) SIM fails, as described above. Calling the second (e)SIM works as expected.
• The issue persists even when disabling the second (e)SIM.
• The app has all permissions enabled and is allowed to run in the background, ect.
• Other phone apps such as the "Amadz" phone dialer or the default phone app (from google) are able to patch through calls to SIM1. Only Fossify Phone (and the Simpletools-Phone app) fails.
• Reinstalling / deleting all data / rebooting the phone / going to flight-mode / resetting network connections doesn't help.

[chesio]

I have the same setup (Fairphone 5 with physical SIM and e-SIM, the same app version), but I don't have the issue. The only difference is that I have installed the Phone app via F-Droid.

~~What network operator is your physical SIM using? Could it be an operator related setting?~~

EDIT: Ignore my question - it wouldn't work with other apps as you have mentioned.

[Glitchy-Tozier]

EDIT: Ignore my question - it wouldn't work with other apps as you have mentioned.

Yep, that's why I decided to post this bug, since receiving calls seems to be working perfectly fine with other apps.

That being said, during the last few days, I noticed that "Right Dialer" – an app also based on Simple Phone – also seems to be having this issue. On the other hand, the default (google) phone app and a fairly basic open source phone dialer app called "Amadz" seem to be working perfectly fine.

I suspect the bug consists of something all these Simple-Phone-based apps have in common, making them different from other alternatives.

[naveensingh]

@Glitchy-Tozier

• Do you have Block calls from unknown/hidden numbers enabled? Does the issue go away if you disable it?
• Do you use pattern blocking? If yes, please check if there's any wide-ranging pattern like +*. Currently, blocked numbers and patterns are stored in the system, so they survive reinstallations.

This seems like a bug in the call screening service.

[Glitchy-Tozier]

@naveensingh I don't block any numbers, and I don't even use a call-screening service on my device.

[antodc]

Out of curiosity, what happens if you disable voicemail?

[Glitchy-Tozier]

@antodc I don't know how to do that...however, after installing the open spource "Amadz- Calling App" dialer, and using that as my primary app for a couple of days, I was able to switch back to Fossify Phone and consistently receive calls 🎉

[naveensingh]

Thanks for the update. I couldn't find anything that could cause this in Fossify Phone. Will reopen if this is reported again.

[Glitchy-Tozier]

Aaaaand after updating to Android 15 the bug is back.

[chesio]

@Glitchy-Tozier Do you have 5G enabled? I do recall having strange connectivity issues when I had 5G enabled on my Fairphone 5, so I've disabled it. It might be related to the area I live in, but perhaps you could give it a try.

[Glitchy-Tozier]

@chesio Let me answer in a couple of bullet-points:

• Before the recent update, I'm pretty certain I had 5G disabled
• After the update, it seems to have been magically re-enabled
• I switched it off (changing the setting back to "4G/3G/2G", see screenshot). This enabled me to receive one phone call
• However, in the five days since, all phone have gotten automatically rejected, identical to the original bugged state

[naveensingh]

Since you mentioned that other phone apps are working fine, this is likely not a network issue.

[Glitchy-Tozier]

Are there any things you want me to try out before I attempt to fix things again by installing a non-Simple-Phone-based dialer app?

[naveensingh]

Nope. You could try switching between Fossify Phone and the other phone app back to back to rule out any network issues.

My initial theory was that this might be a drop-all-calls bug in the call screening service provided with Fossify Phone, but that requires Fossify Phone to be set as the default caller ID app (which you likely haven't).

[Glitchy-Tozier]

I didn't change anything and now it works again. Sorry for the chaotic reporting, I've got no idea what's causing this issue.

[naveensingh]

I didn't change anything and now it works again.

It wouldn't be so intermittent if it were a simple logic issue. Something else is triggering this.

You could try switching between Fossify Phone and the other phone app back to back to rule out any network issues.

I don't know if you have tried that exactly, so... have you tried that? That's the only way we can confirm if this is a Fossify issue or something else:

1. Wait for the magical moment when calls start failing
2. Set Fossify Phone as the default phone app and receive a call ➜ note the result
3. Switch to another phone app immediately and call your number again -> note the result
4. Back to 2

If the call never fails on the other app, something must be broken in Fossify Phone.

[WebworkrNet]

For me, the error only occurs recently when the device is locked. Incoming calls when unlocked are reported correctly and can be answered.

Motorola moto g34 5G XT2363-3 Android 15 (stock ROM) FossifyPhone 1.7.0

SIM 1 (physical): Data SIM 2 (eSIM): Phone calls, SMS, data (during phone calls and as failover)

Unrestricted battery usage is granted by default and cannot be manually disabled.

[Glitchy-Tozier]

I can tell you that in my case it happened even when the device was locked.

[naveensingh]

Calling the first (physical) SIM fails, as described above. Calling the second (e)SIM works as expected.

@WebworkrNet which SIM is failing in your case? Physical or eSIM?

[WebworkrNet]

Calling the first (physical) SIM fails, as described above. Calling the second (e)SIM works as expected.

@WebworkrNet which SIM is failing in your case? Physical or eSIM?

I only use SIM 2 for making calls. That's the eSIM, as already mentioned in the comment.

[WebworkrNet]

I received a call today. My smartphone was locked. The device rang, but the screen to accept the call did not appear. I did not see any other options for accepting the call.

[naveensingh]

I received a call today. My smartphone was locked. The device rang, but the screen to accept the call did not appear. I did not see any other options for accepting the call.

That could be https://github.com/FossifyOrg/Phone/issues/165 or https://github.com/FossifyOrg/General-Discussion/issues/268

[ksz16]

I have a similar problem on OnePlus 6 and OnePlus 6T. Both phones run LineageOS 22.2 (Fossify Phone version 1.9.0 installed via F-Droid).

Incoming calls sometimes appear under the locked screen (the changes in version 1.8.0 did not fix this). Sometimes someone called me: the ringtone last very briefly and then cut off, the notification appeared on the screen and disappear. Only after a moment a second call came through, this time correctly. It also happened that someone called me and got a message saying that the user was unavailable (as if my phone was turned off).

I started to look into the problem. It seems that this is related to killing applications or services running in the background. I should add that from the very beginning I had the system dialer (com.android.dialer) disabled, while Fossify Phone was the default phone app with App battery usage set to Unrestricted. It seems that these settings are not enough. Today I added the following apps to Unrestricted:

• com.android.dialer
• com.android.phone
• com.android.providers.telephony

I hope this helps.

I noticed one more thing. If I call someone using Fossify Phone and end the call, I can still see the app in Recent Apps. However, if I receive a call from someone (on locked screen), end it, and check Recent Apps, Fossify Phone is not there. Isn't that strange?