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
{{ message }}
Repository navigation
Commit 9755cef
Browse filesBrowse the repository at this point in the historyBrowse files
Adds four ZCALLRECORD columns that newer iOS (26) stores carry, selected
only when present so older CallHistory.storedata schemas keep parsing:
Auto-Answered Reason and Communication Trust Score (both as stored), and
Originating Device Name and Blocked By Extension Name. The old call_history.db
path reports them as NULL. The existing twelve columns are unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: scripts/artifacts/callHistory.py
+35-10Lines changed: 35 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@
4
4
"description": "Extract Call History",
5
5
"author": "@AlexisBrignoni - @JohnHyla",
6
6
"creation_date": "2020-04-30",
7
-
"last_update_date": "2026-07-31",
7
+
"last_update_date": "2026-09-23",
8
8
"requirements": "none",
9
9
"category": "Call History",
10
-
"notes": 'Call type and disconnected-cause value mappings are community-established decodes reported as observed; unrecognized values are reported as stored. When both CallHistory.storedata and CallHistoryTemp.storedata hold records, rows from both are reported with a Source File path column and the report names both stores. On none of the nine registered corpora run did both stores hold records, so that path was exercised on a constructed tree with the same records under both names.',
10
+
"notes": 'Call type and disconnected-cause value mappings are community-established decodes reported as observed; unrecognized values are reported as stored. When both CallHistory.storedata and CallHistoryTemp.storedata hold records, rows from both are reported with a Source File path column and the report names both stores. On none of the nine registered corpora run did both stores hold records, so that path was exercised on a constructed tree with the same records under both names. Newer iOS (26) adds columns to ZCALLRECORD that are read here when present and left blank on older stores that lack them: Auto-Answered Reason and Communication Trust Score are reported as stored, and Originating Device Name and Blocked By Extension Name are reported as stored. iOS 26 introduced call screening and hold assist, which auto-answer calls; the meaning of the Auto-Answered Reason integer is reported as stored and not otherwise interpreted. On a tested iOS 26.5 sample the auto-answered reason and communication trust score were set on every call, with one call carrying a non-zero auto-answered reason, while the originating device name and blocked-by-extension name columns were present in the schema but empty, so those two are code-present and unexercised on that sample.',
# The Call Ending Timestamp provides an "at-a-glance" review of call lengths during analysis and review
39
39
# Additional details published within "Maximizing iOS Call Log Timestamps and Call Duration Effectiveness: Will You Answer the Call?" at https://sqlmcgee.wordpress.com/2022/11/30/maximizing-ios-call-log-timestamps-and-call-duration-effectiveness-will-you-answer-the-call/
0 commit comments