Callery’s bulk archive workflow requires recordings saved in shared internal storage, visible in your phone’s file manager. Copy the original files with their names intact. A dialer’s recording or Share button alone is not enough.
Check the OEM dialer route for your exact model, region, and software. Some routes use manufacturer settings; others are clearly scoped community reports. Installing another Phone app alone does not establish recording support.
You must be able to select and copy recordings together from a normal storage folder. If recordings are only available inside the dialer, that setup does not meet Callery’s archive requirements.
Preserve original filenames: Callery reads recognized caller and call-date details from them. Test a few supported audio files before copying years of recordings.
Check the current setup: original files accessible when the folder and metadata checks pass; OEM setup required when an applicable dialer route needs completing; or not established for this build when no working route is verified. A phone shipped with Google Phone may have an OEM setup path.
On supported Galaxy recording setups, open My Files → Internal storage → Recordings → Call. Copy that folder or select its original files together, including over USB. Keep every filename unchanged.
Copy Samsung’s recording folderGoogle’s individual sharing route does not meet the original-folder requirements. This describes the current recording setup, not permanent hardware incompatibility. On phones with an applicable OEM dialer route, check that setup for future recordings. Existing private Google Phone recordings do not migrate automatically.
Why Google Phone does not fitUse an available Xiaomi OEM dialer, or review the model-scoped community ADB reports when firmware packages need restoring. The guide separates restoration from Google-app and overlay removals, includes rollback, and requires calling, original-folder, and filename checks. Another region’s dialer does not prove your installed build contains it.
Check Xiaomi’s dialer and storageUse the built-in OEM dialer or official ODialer only where offered for your device. Recording support alone is insufficient: confirm the original folder is visible in File Manager, then check the unchanged filenames in Callery.
Check OPPO and ODialer setupSome firmware offers an OEM Phone & Contacts app. Verify that its recordings appear as original files in storage. Opening audio only in Recorder is insufficient, and automatic Vivo/iQOO filename recognition has not been verified.
Check Vivo and iQOO requirementsSources reviewed November 12, 2026: Samsung’s recording folders, Samsung’s USB copying instructions, Google’s individual-call sharing instructions, and Callery’s filename reference. The linked device guides give additional model and software limits. No hardware certification is implied.
Callery accepts these upload formats. Confirm the extension of your actual recording, then try a few files before transferring an entire archive.
AMR, standalone AAC, and OGG/Opus are not currently accepted. A recognized filename does not add support for an unsupported audio format.
These naming layouts describe files, not certified devices. The uploader can accept an unfamiliar filename, but the result has an unknown caller and upload time. That fallback does not provide the contact-and-date archive workflow described here.
| Recorder profile | Filename layout | Automatic metadata |
|---|---|---|
| Samsung-style call files | Call <caller>_YYMMDD_HHMMSSAlso recognizes the “Call recording” prefix. | Caller and local call date/time |
| Older MIUI call files | <call label>@<phone>_YYYYMMDDHHMMSSRecognized localized call labels are discarded. | Phone number and local call date/time |
| Huawei-style call files | <name>@<phone>_YYYYMMDDHHMMSSPhone number takes priority for contact matching. | Name, phone number, and local call date/time |
| ColorOS call files | <caller>-YYMMDDHHmmMinute precision. This is a filename profile, not certification of every Oppo model. | Caller and local call date/time |
| GrapheneOS call files | CallRecord_YYYYMMDD-HHMMSS_<phone>Recording availability depends on the installed system. | Phone number and local call date/time |
| LineageOS call files | <phone>_YYMMDD_HHMMSS[mmm]Optional milliseconds are recognized. | Phone number and local call date/time |
| BCR default filenames | YYYYMMDD_HHMMSS.mmm±HHMM…Custom filename templates need a separate check. | Timestamp with offset; optional caller details |
| ASUS sequence exports | Call recording <sequence>Recognized as a recording name only. | No caller or call date in the filename |
| Oppo voice recorder | RECYYYYMMDDHHMMSSIts timestamp describes recording end, not call start. | No inferred call start date |
Dates without a UTC offset do not identify the phone’s timezone. Review dates and contact matches after a small test import. Copying a file must preserve its original name; a changed filesystem modification date cannot restore missing call metadata.
Our backup guide walks through a careful first import.
Callery