錯誤回報 |
Cannot block number |
| ID: 560Status: 待處理Version: 0.2.8Report Date: 31/03/2017Product: 小鴨幹線 | |
| Reporter | Tom |
| Assignee | |
Description Nexus 5X Android 7.1.1 with March security patch Cannot block number in database |
|
錯誤回報 |
Cannot block number |
| ID: 560Status: 待處理Version: 0.2.8Report Date: 31/03/2017Product: 小鴨幹線 | |
| Reporter | Tom |
| Assignee | |
Description Nexus 5X Android 7.1.1 with March security patch Cannot block number in database |
|
在〈Cannot block number〉中有 8 則留言
Did those calls have any block records in the app? (Under history tab)?
No block records is shown in the app.
Number remain in call log (“Erase call record on phone” checked)
The number can be found using the search function in the database.
Seems the background service was not started or killed. Was it OK before the March path? Do you have apps that kill background jobs eg clean master?
It was okay before March.
Auto-update of database is running fine, even call blocking currently has problems
I don’t have any apps that kill background jobs, e.g. clean master
Have you tried re-installing the app? I have googled comments on the update but have not find any clue on the problem so far.
Seems problem is fixed on android 7.1.2.
Thanks for your help.
Hi again.
Seems the problem appears back in android 7.1.2, particularly when the phone is using or in doze mode.
I suspect the telephony API may have changed in this new version of android, causing blocking failure,
Can you please check that? Thanks a lot.
If the failure is due to internal api changes in telephony the app should have never worked regardless of doze, and you should see the call logged by the app in history. From your observations it is more likely that the new ROM or the particular build places more severe restrictions on background service in doze mode, such that it was forbidden from running at all in doze mode for some reasons. If so you may try turning off the battery optimization for the app to see if the situation improves.