Call log is only recording 502 calls. More than that is getting deleted.

Randomperson

As the title says, if there are more than 502 call logs, the oldest call log will be deleted.

I used sms backup to restore the call, after some time past 502 call logs are stored. Rest are deleted.

Any way to solve this? I have lost more than year worth of call history!

Tried third party app but they are showing past 502 calls only.

Tigga

Randomperson did you figured out? Solved the problem?

de0u

Tigga

I think this is the case for many Android variants, inherited from AOSP. I think the code for this as of Android 16 QPR1 is here: https://github.com/GrapheneOS/platform_frameworks_base/blob/c4a46d2dd2bf289848efd5c8a03af478e46116c4/core/java/android/provider/CallLog.java#L1647

It looks as if the code was reorganized for A16 QPR2, but I don't have time right now to hunt for it.

Tigga

de0u I'm kinda new to custom ROM development. I can correct this piece of code, but the next steps: how to build the ROM for my device from this code, is where I am stuck. Any simple step-by-step guide how to make own build?

Tigga

de0u https://github.com/GrapheneOS/platform_frameworks_base/blob/c4a46d2dd2bf289848efd5c8a03af478e46116c4/core/java/android/provider/CallLog.java#L1647

It looks as if the code was reorganized for A16 QPR2, but I don't have time right now to hunt for it.

I synced the repo for the Pixel 10 by the tag 2026050900 and CallLog.java file contains only 1300 lines, whilst in the piece you provided the DEFAULT_MAX_CALL_LOG_SIZE variable is on the line 1647. So, basically, in my sources this line non-existent. Is it the A16 QPR2 reorganization you were talking about?
Could you please help me identify the needed piece of code for the latest release?

de0u

Tigga Any simple step-by-step guide how to make own build?

https://grapheneos.org/build

Note that installing a custom build will require wiping the device, and also getting updates will require building and installing each new release. Be careful not to lose the signing keys!

Andromxda

de0u Tigga You can build GrapheneOS on your machine and run it in the Android emulator.

Here are the official instructions for testing phone calls in the emulator: https://developer.android.com/studio/run/emulator-networking-voice

Tigga

de0u ok, seems like I found it. It's now on the 101th line of the file CallLogUtils.java
https://github.com/GrapheneOS/platform_packages_services_Telecomm/blob/309695ff9b303dc2649873e8d2274b699e71899c/src/com/android/server/telecom/util/CallLogUtils.java#L101
Could you confirm changing this property is enough?

Tigga

Andromxda thank you

de0u

Tigga Could you confirm changing this property is enough?

That is what I would try changing, and I would expect to succeed (70%), but I am absolutely not in a position to test the change at present, let alone extensively.

Tigga

thanks everybody for the help, I successfully built the code and ran it in emulator, which is a big progress for me given the fact that I was never into the mobile development, wow!
Now is the next step. I'm trying to verify the behavior and check if the above mentioned line I corrected made any impact to the call log. I connected to the emulator via console, and I am able to make an inbound call like gsm call XXXXXXXXXX, and now the question is how to automate it? I need to fake 500+ calls, ideally 10000 and see what is happening with the call log, if it is being wiped after 500 limit or no. Can anybody help me how to achieve that? The AVD console works via telnet on localhost, which prevents me from doing any bash scripting. Any idea how to push console commands in batches, via script, in a loop?
@Andromxda can you please give some hint?