Compare wireless charging tests without confusing input watts with phone power
A simple repeatable observation is more useful than a precise-looking number measured in the wrong place. This method organizes your tests; it does not turn them into certified laboratory results.
Open the private test logKeep three evidence levels separate
| Evidence | What it establishes | What it does not establish |
|---|---|---|
| Manufacturer reference | A stated model capability or requirement under specified conditions. | That your exact retail unit, case and firmware have been independently tested here. |
| User observation | What the user recorded for an identified configuration and interval. | A calibrated phone-side power measurement or independently verified outcome. |
| Independent test | Would require an identified procedure, instruments, measurement point, conditions and review. | This module does not currently publish or claim such tests. |
Before each observation
Record the exact phone, charger model/SKU, case or “none,” power adapter, cable or integrated-cable arrangement, phone OS and charger firmware if known. Write “unknown” rather than guessing. Note the starting battery percentage, screen use, room conditions and anything that may affect the comparison.
Keep the starting battery range and conditions similar between runs. Change one component at a time. Use the same elapsed interval, and repeat a surprising observation before attributing it to that component. Never keep testing unsafe-feeling or damaged equipment.
What the notebook calculates
Percentage points per 30 minutes = (end percentage − start percentage) ÷ elapsed minutes × 30.
For a hypothetical change from 25% to 39% in 15 minutes, the interval-normalized value is 28 percentage points per 30 minutes. This is an arithmetic example, not a device benchmark and not a prediction that a later 30-minute interval will add 28 points. Battery percentage reporting is coarse and charging is not necessarily linear.
Zero or negative change can be recorded. It describes net battery change during that interval, not by itself a broken charger. Workload and other uncontrolled conditions can confound the observation.
Label optional watt readings by measurement point
USB input into the puck
This is upstream power. The puck’s own consumption and conversion losses intervene before energy reaches the phone. Do not label it as watts delivered to the phone or battery.
Battery / OS telemetry estimate
This is an estimate reported by the device, with its own sampling and system boundaries. Do not equate it with a calibrated wireless input measurement.
External receiver or test equipment
A receiver used in place of the phone can behave differently from the actual phone. Record the instrument and method in notes. A number alone does not establish the phone’s received power.
Storage, export and sharing
Only pressing “Save privately on this browser” stores a test under the key devicefitcheck.wireless.tests.v1. The module does not send the log to a server. Up to 30 records are retained until deleted or browser storage is cleared. In private browsing or when storage is blocked, keep a CSV export before leaving.
The CSV includes model labels, software, conditions and a user-reported/unverified status. Do not add private information that you would not want in a file you later share. The setup-link feature uses a URL fragment for the selected form inputs and deliberately omits readings, free-text notes and hardware labels. It does not publish your test log.
Updating the evidence
A source-review date is not a lab-test date or a guarantee that a manufacturer’s page never changes. A new SKU or firmware claim requires a new source review. When an exact pairing is not supported by the reviewed references, the checker returns an unresolved result.
Charging requirements are linked in each result to the relevant Apple, Google or Samsung reference. The comparison method and notebook calculation are our own.
Back to the wireless charging checker · Troubleshoot slow charging