You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tried in Nokia android one, vivo funtouch & redmi os too
Affected device model
currently vivo iqoo z7s
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Launch the dialer app. Keep history tab as default tab.
Next time close the app & reopen. Call history wont be already there but loads from phone storage each time if you open the app. Visible 1 second or 2 second gap comes to load call history.
Expected behavior
When launched, the call history should be there already and not load after opening the app
Actual behavior
It takes time to load call history each time i open the app
changed the title [-]call history takes a short 2 seconds gap to load. while "emerald dialer" or system dialer is fast to load call history whenever app is clicked. but here contact, favorites takes a very less load time but call history shows 1-2 seconds gap[/-][+]Call history loading is slow on app launch[/+]on May 8, 2025
Me too. Up to 10 seconds to load, I deleted history a couple of weeks ago so it's not like there are thousands in there.
Moto g13, Android 14. Google play services disabled in case that's making a difference.
Incidentally, this phenomenon does not only occur when the app is launched, as described in the title of this issue, but every time the “call log” tab is reloaded, i.e., when switching tabs within the app and when the Phone app is brought back to the foreground from the background.
On app start, landing on call history lags. Loading takes time. But if I switch to contacts tab instead of waiting, and return back to call logs, it loads without lag.
The program has slowed down excessively. I'm opening the program, the last calls don't appear before 15 seconds. When the call comes in, the caller's name does not appear before 15 seconds. Sometimes the phone rings, but the call screen never comes. When the call ends, I go to recent calls and call back.
I have a working version that substantially improves call-history loading, tested on my Huawei LYA-L29 running Android 10 with 3,520 contacts containing phone numbers and 1,608 call-log entries. The benchmark builds are based on Fossify Phone 1.11.1 (built from source, foss debug).
I reproduced the original delays and verified the improvement on the same device. The modified app feels much faster and more responsive in everyday use.
Measured before and after
Measurement
Before
Working version
First 100 entries
3.3 to 3.8 s
160 to 170 ms
Full list of 1,608 entries
9 to 17 s (16.7 s typical)
110 to 130 ms
Overlapping refreshes at startup
3 to 4
1 at a time
Full contact loads per refresh
2 to 3
0 to 1, shared
Timings were measured with temporary SystemClock.elapsedRealtime() instrumentation around refreshCallLog(). The first-100 and full-list loading phases reuse shared work; the full-list figure is not an independent cold-start measurement. These are measurements on one device and address book, not a claim about total cold-launch time on every device.
The main causes I found were:
Repeated full contact loads in RecentsHelper, RecentsFragment.prepareCallLog, and MainActivity.cacheContacts, costing about 1.4 to 3.5 seconds each.
Overlapping refresh requests repeating the same work.
Matching each call against the contact list, making the work grow with calls multiplied by contacts.
The patch shares contact loads through a cache invalidated by a system contacts observer and relevant settings, builds number lookups once, and coalesces overlapping refresh requests. I have checked the working version on the device, including contact edits being reflected in the call history.
One remaining limitation to address before merge: changes to the app's private-contact storage do not directly invalidate the cache. Those changes currently become visible after a system-contact or relevant setting change. The other fragments' own contact loads are outside this focused patch.
I'd like to contribute this as a focused PR. Your contribution guidelines require the help wanted label before submission. Could a maintainer add it so I can open the PR?
Activity
Aga-C commentedon May 6, 2025
WebworkrNet commentedon May 6, 2025
Maybe related to FossifyOrg/General-Discussion#220.
naveensingh commentedon May 6, 2025
Both are about optimizing loading, but this one concerns call history items, and the general issue concerns contacts.
#345 is a similar issue that could be solved by optimizing loading, but it's better to do a direct database search in that case.
geesquer4u commentedon May 8, 2025
But it helps right. Ok. Short version would be "each time I open the app, call history or any other tab takes time to load data"
i mentioned latest version (from fdroid). Funtouch OS 15. But my other Nokia with android 12 also same issue. And redmi note 10 with android 13 also
This is a new device just 5 call logs were there
[-]call history takes a short 2 seconds gap to load. while "emerald dialer" or system dialer is fast to load call history whenever app is clicked. but here contact, favorites takes a very less load time but call history shows 1-2 seconds gap[/-][+]Call history loading is slow on app launch[/+]breggles commentedon Jul 13, 2025
Happens for me, as well. Version 1.6 on Fairphone 4 with Android 13. Same for contacts and favorites.
c-o-m-m-a-n-d-e-r-d-a-t-a commentedon Jul 22, 2025
Me too. Up to 10 seconds to load, I deleted history a couple of weeks ago so it's not like there are thousands in there.
Moto g13, Android 14. Google play services disabled in case that's making a difference.
21 remaining items
WebworkrNet commentedon Jan 9, 2026
breggles on Sep 17, 2025:
I can confirm this.
WebworkrNet commentedon Jan 9, 2026
Incidentally, this phenomenon does not only occur when the app is launched, as described in the title of this issue, but every time the “call log” tab is reloaded, i.e., when switching tabs within the app and when the Phone app is brought back to the foreground from the background.
archivesilver commentedon Jul 13, 2026
Hope this is helpful information.
On app start, landing on call history lags. Loading takes time. But if I switch to contacts tab instead of waiting, and return back to call logs, it loads without lag.
yusufsunetci commentedon Aug 15, 2026
The program has slowed down excessively. I'm opening the program, the last calls don't appear before 15 seconds. When the call comes in, the caller's name does not appear before 15 seconds. Sometimes the phone rings, but the call screen never comes. When the call ends, I go to recent calls and call back.
Softweb-SA commentedon Oct 12, 2026
I have a working version that substantially improves call-history loading, tested on my Huawei LYA-L29 running Android 10 with 3,520 contacts containing phone numbers and 1,608 call-log entries. The benchmark builds are based on Fossify Phone 1.11.1 (built from source, foss debug).
I reproduced the original delays and verified the improvement on the same device. The modified app feels much faster and more responsive in everyday use.
Measured before and after
Timings were measured with temporary
SystemClock.elapsedRealtime()instrumentation aroundrefreshCallLog(). The first-100 and full-list loading phases reuse shared work; the full-list figure is not an independent cold-start measurement. These are measurements on one device and address book, not a claim about total cold-launch time on every device.The main causes I found were:
RecentsHelper,RecentsFragment.prepareCallLog, andMainActivity.cacheContacts, costing about 1.4 to 3.5 seconds each.The patch shares contact loads through a cache invalidated by a system contacts observer and relevant settings, builds number lookups once, and coalesces overlapping refresh requests. I have checked the working version on the device, including contact edits being reflected in the call history.
One remaining limitation to address before merge: changes to the app's private-contact storage do not directly invalidate the cache. Those changes currently become visible after a system-contact or relevant setting change. The other fragments' own contact loads are outside this focused patch.
I'd like to contribute this as a focused PR. Your contribution guidelines require the
help wantedlabel before submission. Could a maintainer add it so I can open the PR?geesquer4u commentedon Oct 15, 2026
Novadial app is a fork of this but there is no delay in call history. Is it possible to compare these 2 apps and get any findings
Softweb-SA commentedon Oct 15, 2026
No need to compare as we have fixed that, thats what i am saying, i am waiting for access to make a pull request here by the maintainer
Softweb-SA commentedon Oct 15, 2026
App is very snappy right now,
Using it with ease every day making more than 50 calls!
Waqar144 commentedon Oct 15, 2026
@Softweb-SA are you a bot? You can just make a PR, I don't think labels are needed
EDIT: seems I am wrong. https://github.com/FossifyOrg/Phone/pull/918/changes
The project is on life support, hardly any changes in the last months and no fixes and no PRs accepted.
Softweb-SA commentedon Oct 15, 2026
No, real human, this is our official github
I am just trying to help the users of this OSS project, because we debugged these issues.