Idle high → press low
Source reference: approximately 1.8 V idle and 0 V when pressed. Confirm flex switch, connector, pull-up and PMU-side line separately.
Separate always-on power, sensor buses, physical keys, Taptic Engine drive, motion sensors, proximity/ALS, barometer and watchdog telemetry before replacing a flex, sensor IC or haptic driver.
A dead button, frozen orientation or 180-second restart is a symptom family. The correct repair follows the first electrical, bus or telemetry stage that cannot be confirmed.
Select the subsystem first because buttons, haptics, motion and environmental sensors use different rails and buses.
Each case keeps the flex, connector, rail, bus and IC domains open until bench evidence narrows them.
Button input and haptic confirmation are separate electrical paths.
Do not map a token directly to one flex or IC across every iPhone generation.
| Token / Symptom | Source Domain | Possible Physical Domain | Required Confirmation | Do Not Assume |
|---|---|---|---|---|
| prs0 | Pressure / barometer telemetry | Barometer, flex/connector, I²C line, board trace | Exact model mapping + full panic + I²C/power test | Do not automatically replace the charging/dock flex |
| Proximity fails during call | Prox / ALS / optical path | Optical window, flex, 3V rail, I²C, sensor alignment | Functional test + rail + bus + known-good assembly | Do not assume sensor IC is bad |
| Auto-rotate frozen | IMU / motion | IMU power, SPI/I²C, sensor, AP-side bus, software state | Known-good software state + power + bus evidence | Do not jump directly to IMU BGA reball |
| 180s restart | Watchdog / missing telemetry | Depends on token and model | Full panic log + exact model + functional isolation | Do not treat “3-minute reboot” as one universal flex fault |
Values are retained as uploaded-source references. Exact-model schematic/boardview and known-good measurements take priority.
| Subsystem | Rail / Signal | Source Voltage | Source GR | Resistance | Signal / State | What abnormal supports |
|---|
A passing line reading does not prove active bus traffic, sensor calibration or mechanical input integrity.
V2 deliberately removes several one-to-one conclusions from the uploaded V1.
It only proves the board can boot through that path. The original key/flex/connector line is still the primary branch, but PMU-side issues are not mathematically excluded.
An open can be filter/series part, trace, pad, connector or IC-side. Locate the actual discontinuity first.
Start with known-good engine, connector, boost rail, differential output and command state.
Optical obstruction, alignment, display glass, rail, I²C and sensor/flex faults can produce the same call symptom.
`prs0`, `mic1` and other tokens are domain clues; physical placement and repair route can vary by generation.
SPI/I²C timing, interrupt behavior, calibration, intermittent solder and mechanical faults can pass static GR/voltage tests.
Preserve exact model, panic token, button waveform, flex substitution and sensor behavior.