GETTING STARTED
Start with a log. Build a history.
Start with one recent analytics log. An in-app tutorial helps you along the way.
- 01
Find an analytics log
Go to Settings → Privacy & Security → Analytics & Improvements → Analytics Data. Look for a file starting with Analytics-.
- 02
Open it in MochiLog
Use the log’s share button and choose MochiLog. If it isn’t listed, save the log to Files, then import it from the app.
- 03
Explore your records
Review and save capacity, cycles, and other available values. Add logs from different dates to see trends in the charts.
A new way to use your paired computer.
The Mac or Windows companion collects daily Analytics files for your mobile app to receive when opened. Complete initial trust and QR pairing, then let mobile handle parsing and recording. Manual import remains available without a computer.
Enable Settings → Advanced Settings → Live Battery (off by default) to see a table of understood readings such as cycle count, charging and voltage, using existing computer pairings. Uncertain capacity fields remain in details. Open Show detailed information to inspect uncertain internal fields and channel metadata. Desktop Live Battery also has its own tab, with paired devices first in Overview. Mobile shows friendly model names, combines identical values from multiple computers reading the same device, and compares only differing fields. Each source keeps its acquisition time and state. Values refresh while open; only changed values are transferred, encrypted. Values are not saved to history, records or iCloud. Missing fields and outdated values are shown separately.
Use mobile 4.0.0 with MochiLog Mac or Windows 1.0.0. Mobile 4.0.0 is being prepared for App Store review and is currently available through TestFlight. Windows 11 is required; initial USB trust uses Apple Devices or classic iTunes from Apple. Daily-log collection requires an unlocked device. Current-value acquisition can also fail depending on OS and connectivity, and is separate from daily logs or official Apple diagnosis.
Choose how to collect your logs.
Settings → Automatic Log Collection contains independent PC and on-device options. On-device acquisition is experimental and off by default. It connects to your own diagnostic service through a compatible local VPN/reflector route. Explicitly reuse your own OS pairing from an updated authenticated computer, or import an RPPairing file. Initial OS trust and a compatible route are required. On-device collection supports iOS/iPadOS 17 or later. Initial pairing entirely on the device requires 27 or later and Developer Mode. From 4.0.0 beta 1050, an unlocked device with its VPN connected can also attempt collection while the app is not displayed, when iOS allows it. Complete files are analyzed and recorded the next time you open the app. Timing and intervals are not guaranteed. Daily diagnostics record OS wakes, starts, completion and interruptions; feature-file headers identify the log format and app version.
From 4.0.0 beta 1051, Settings → Debug → Activity logs groups daily device logs, received computer logs, and retention settings. Saved logs remain available when on-device or PC collection is disabled. On iPad, they open in the settings detail pane.
From 4.0.0 beta 1054, error logs are grouped by date and searchable by message. Wider iPad screens show the list and details side by side. Activity logs can be browsed by date, device and feature. Page controls above the text let you move through large logs or jump directly to their first and last pages; copying or sharing still includes the full text. Opening or refreshing the viewer does not start collection or transfer. Mac 0.2.26 and Windows 0.1.24 also improve loading of large logs.
Beta 1055 recognizes fully saved on-device reports and recovers them for import, preventing unnecessary downloads of the same file. Mac 0.2.27 and Windows 0.1.25 prioritize newer reports and retry unreadable files individually. Activity logs record failure reasons, retry times and progress from saving to import. Existing pairings remain valid.
Beta 1058 adds multiple selection and deletion of battery records from Home. Tap Select, check records and confirm the count before deleting; select all and deselect all are available. Records changed on another device during confirmation are skipped. With iCloud sync enabled, deletion also applies to synced devices.
Beta 1057 and later with Mac 0.2.29 or Windows 0.1.27 sends current mobile LAN endpoints inside encrypted requests. Companions verify those candidates using existing OS trust when VPN routing makes the transfer peer different from the diagnostic endpoint. No re-pairing is needed. Failed downloads and retry waiting remain visibly incomplete, while multi-PC history exchange and older-version communication are retained.
The VPN is provided by a separate app. A MochiLog QR alone cannot establish Apple OS trust. Fully wireless initial setup, Developer Mode-off operation and background acquisition are not guaranteed. Both paths use the same import queue to avoid duplicates.
Confirmed iCloud sync on both devices and the same Apple Account also allow current battery readings from other devices paired with the same PC. PC automatic update checks are off by default and can be enabled in the initial prompt or settings. These additions require MochiLog 4.0.0 (1041), Mac 0.2.20 or Windows 0.1.17 or later.
Logs from other devices, with their original identity.
In the multi-device sharing feature under development, iPhone and iPad paired with the same computer can receive each other’s logs encrypted only when both have iCloud sync enabled and the same Apple Account is confirmed. The rule applies per recipient with three or four devices too. Sync off, different accounts or unconfirmed settings prevent sharing. If the source app has not been opened recently, sharing waits for confirmation. Logs already deleted on the computer cannot be recovered.
Source device identities are preserved, and duplicate transfers and records are avoided. Another recipient’s acknowledgement protects the source’s pending queue. Log collection and current battery acquisition run independently.
For multi-device sharing, update to MochiLog 4.0.0 beta 1052 or later and Mac 0.2.25 or Windows 0.1.23 or later. When a log omits its model, the authenticated source device supplies it. Verified older records with the wrong model are corrected while preserving dates, record IDs and measurements. Existing pairing is retained.
Capacity is a value recorded in your log.
mAh measures electric charge capacity. MochiLog shows logged capacity values and ratios to reference capacities. These estimates can fluctuate with temperature, usage, and OS corrections. They are not an official diagnosis that is more accurate than Settings.
One cycle means 100% of use, in total.
Using 50% on each of two days amounts to one cycle. It is not the number of times you plug in a charger. Cycle count alone does not determine replacement timing; consider real battery life and Apple’s diagnostics too.
Build a history for the same device.
Logs from different dates help you see longer-term trends rather than focus on daily fluctuations. Some values may be unavailable depending on the log format and the information it contains.
Choose how to sync and share.
Enabling iCloud sync stores records in your private database. Your paired iPhone transfers records to Watch. Before sending a log to support, check for identifiers or other information and share only what is necessary.