FIELD GUIDESource-led reference

P161 / Charging and power / Guide

Read a charger’s port-sharing table

Source output, occupied ports, requested power and cable evidence are separate.

The useful distinction

Read the exact adapter model, port labels and cable markings.

Claim inspection dates: 2026-10-03 · Independent review pending

Guide note · not an individual product specification

The useful distinction

Understand the requirement.

One headline wattage does not describe every occupied-port combination. [C161A]

A published per-port ceiling is not an optimizer. Subtracting one device’s target from the total does not authorize giving the remainder to another port. Use an explicitly documented allocation case. [C161B]

Bounded facts, visible unknowns

Specifications and limits

Read a charger’s port-sharing table facts and limitations
Workflow boundaryOne documented source, direct outputs, anonymous target assumptions. [C161A] [C161B]
Verified device listNot included. Check exact device and accessory documentation.
A boundary, not an omission to guess around.

Start with the occupied-port combination. The Apple dual-port cases additionally depend on the connected device categories. An omitted device or attached cable can make the selected scenario inapplicable.

Before you connect

What to check

  1. Identify the source model and each connected port.
  2. Keep wattage and fixed-voltage requests separate.
  3. Keep unknown cable and occupancy evidence visible.
Trace a supported connection class →

Do not redistribute the remainder

A published per-port ceiling is not an optimizer. Subtracting one device’s target from the total does not authorize giving the remainder to another port. Use an explicitly documented allocation case.

Use the worksheet

Choose the charger and ports, then compare anonymous target assumptions against the documented ceilings. Unknown allocations stay unknown; the result does not establish charging speed or safety.

Your next step

Move from the form to the requirement.

The source trail

Evidence for this page

AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.

C161ASource checked · pending review

One headline wattage does not describe every occupied-port combination.

Apple · How to use the 35W Dual USB-C Port Power Adapter ↗

Locator: Charge a single device; Charge two devices; charging troubleshooting
Access: public page. Device-dependent examples, not a universal equal split. Fixed voltage/current profiles are not listed. Extra unused cables must not be assumed absent.

S160: full source recordInspect review dependencies → (private workspace)

Claim scope: Source-scoped charging reference and worksheet boundary; no electrical approval, forced mode or battery-speed prediction.. Next review due 2027-01-01.

C161BSource checked · pending review

A published per-port ceiling is not an optimizer. Subtracting one device’s target from the total does not authorize giving the remainder to another port. Use an explicitly documented allocation case.

Apple · How to use the 35W Dual USB-C Port Power Adapter ↗

Locator: Charge a single device; Charge two devices; charging troubleshooting
Access: public page. Device-dependent examples, not a universal equal split. Fixed voltage/current profiles are not listed. Extra unused cables must not be assumed absent.

S160: full source recordAnker · 735 Charger (Nano II 65W), A2667 — output specifications ↗

Locator: Output; A2667 user manual label
Access: public page. A2667 Nano II only, not A2668 GaNPrime. PPS is named, but PPS ranges and fixed PD profiles are not supplied on this inspected page.

S161: full source recordInspect review dependencies → (private workspace)

Claim scope: Source-scoped charging reference and worksheet boundary; no electrical approval, forced mode or battery-speed prediction.. Next review due 2027-01-01.

Suggest a correction to this field note →

Charging and power

Keep the power path separate.

Source ceilings, occupied ports, voltage-specific requirements and cable observations need distinct evidence.

Evidence behind this page

Scope first. Source second. Approval separate.

2 linked sources · 2 scoped claims · 0 sources with inspection/access flags.

Page scope: consumer_reference_expansion

Assessment 2026-10-22 · earliest scheduled source review 2027-01-01. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 2 source scopes, access limits and dates

S160 · How to use the 35W Dual USB-C Port Power Adapter

Apple · Manufacturer / product-owner domain · inspected 2026-10-03 · due 2027-01-01

Within inspection window

Scoped support: Two ports share a 35W maximum. Listed Mac/iPhone/iPad pairings have 17.5W per device; specified Mac-or-iPhone plus Watch-or-AirPods pairings have 27.5W and 7.5W ceilings.

Not established / limitations: Device-dependent examples, not a universal equal split. Fixed voltage/current profiles are not listed. Extra unused cables must not be assumed absent.

Locator: Charge a single device; Charge two devices; charging troubleshooting

S161 · 735 Charger (Nano II 65W), A2667 — output specifications

Anker · Manufacturer / product-owner domain · inspected 2026-10-03 · due 2027-01-01

Within inspection window

Scoped support: The A2667 output table distinguishes both USB-C ports and USB-A. Individual, paired and three-port limits are separate documented cases.

Not established / limitations: A2667 Nano II only, not A2668 GaNPrime. PPS is named, but PPS ranges and fixed PD profiles are not supplied on this inspected page.

Locator: Output; A2667 user manual label

Trace 2 claims to their source records

C161A · P161

One headline wattage does not describe every occupied-port combination.

Claim scope: Source-scoped charging reference and worksheet boundary; no electrical approval, forced mode or battery-speed prediction.

Source links: S160 · Evidence trail → (private workspace)

C161B · P161

A published per-port ceiling is not an optimizer. Subtracting one device’s target from the total does not authorize giving the remainder to another port. Use an explicitly documented allocation case.

Claim scope: Source-scoped charging reference and worksheet boundary; no electrical approval, forced mode or battery-speed prediction.

Source links: S160 · S161 · Evidence trail → (private workspace)

Prepare this page for review → (private workspace)Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.