Skip to content

Call history loading is slow on app launch #385

Open

Description

@geesquer4u

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

latest 1.4.0

(edited by naveensingh)

Affected Android/Custom ROM version

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

Screenshots/Screen recordings

No response

Additional information

No response

Activity

  1. added
    bugSomething is not working
    needs triageIssue is not yet ready for PR authors to take up
    on May 6, 2025
  2. Aga-C commented on May 6, 2025

    @Aga-C
    Contributor
    1. Please shorten the title - it should briefly describe the issue, not to be a long description.
    2. Also, please properly fill out the bug report. Which exact app version are you using (version number)? Which Android version do you have?
    3. How many call history entries do you have? You can check it by long-pressing any entry.
  3. added
    waiting for authorIf the author does not respond, the issue will be closed. Otherwise, the label will be removed.
    on May 6, 2025
  4. WebworkrNet commented on May 6, 2025

    @WebworkrNet
  5. naveensingh commented on May 6, 2025

    @naveensingh
    Member

    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.

  6. geesquer4u commented on May 8, 2025

    @geesquer4u
    Author
    1. Please shorten the title - it should briefly describe the issue, not to be a long description.

    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"

    1. Also, please properly fill out the bug report. Which exact app version are you using (version number)? Which Android version do you have?

    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

    1. How many call history entries do you have? You can check it by long-pressing any entry.

    This is a new device just 5 call logs were there

  7. 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
  8. removed
    waiting for authorIf the author does not respond, the issue will be closed. Otherwise, the label will be removed.
    needs triageIssue is not yet ready for PR authors to take up
    on May 8, 2025
  9. breggles commented on Jul 13, 2025

    @breggles

    Happens for me, as well. Version 1.6 on Fairphone 4 with Android 13. Same for contacts and favorites.

  10. c-o-m-m-a-n-d-e-r-d-a-t-a commented on Jul 22, 2025

    @c-o-m-m-a-n-d-e-r-d-a-t-a

    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.

  11. 21 remaining items

  12. WebworkrNet commented on Jan 9, 2026

    @WebworkrNet

    breggles on Sep 17, 2025:

    Having said that, the stock Google Phone/Contacts app doesn't seem to have any performance issue with this setup.

    I can confirm this.

  13. WebworkrNet commented on Jan 9, 2026

    @WebworkrNet

    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.

  14. archivesilver commented on Jul 13, 2026

    @archivesilver

    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.

  15. yusufsunetci commented on Aug 15, 2026

    @yusufsunetci

    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.

  16. Softweb-SA commented on Oct 12, 2026

    @Softweb-SA

    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:

    1. Repeated full contact loads in RecentsHelper, RecentsFragment.prepareCallLog, and MainActivity.cacheContacts, costing about 1.4 to 3.5 seconds each.
    2. Overlapping refresh requests repeating the same work.
    3. 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?

  17. geesquer4u commented on Oct 15, 2026

    @geesquer4u
    Author

    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

  18. Softweb-SA commented on Oct 15, 2026

    @Softweb-SA

    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

  19. Softweb-SA commented on Oct 15, 2026

    @Softweb-SA

    App is very snappy right now,
    Using it with ease every day making more than 50 calls!

  20. Waqar144 commented on Oct 15, 2026

    @Waqar144

    @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.

  21. Softweb-SA commented on Oct 15, 2026

    @Softweb-SA

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething is not working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions