Nearest

Land on a frame near the requested one, before or after it, within the backend's own tolerance. Cheaper than Exact, and the right choice while a finger is moving.

The seek reports the slot of the frame it shows in PlaybackEvent.SeekCompleted.position, not the time it was asked for. That frame may sit either side of the request, as far as the backend's own tolerance allows.

Android does not reach it. media3's player takes no seek tolerance of any kind, so a relaxed seek there lands on the requested frame and costs what an exact one costs.

The desktop does not reach it either. Its frames arrive on a pipe that carries no timestamps, so a seek that landed anywhere but where it was asked has no way to say where, and both the completion and a read-back frame's presentation time would name a frame nobody rendered. It bounds the cost of a scrub by waiting for the finger to settle instead.