ObsidianAndroidAppiumTransportOptions.layoutReadyTimeoutInMilliseconds?

ObsidianAndroidAppiumTransportOptions › layoutReadyTimeoutInMilliseconds?

Type: number

Timeout in milliseconds for waiting for app.workspace.layoutReady, counted from the moment appStartTimeoutInMilliseconds is satisfied — not from the reload.

The second of the two budgets the transport spends after location.reload(). It covers only Obsidian's own work — opening the vault and loading every plugin — once the app itself is up, which is why it can stay tight: measured at ~1s, and ≤8.4s under 12-core + disk + memory stress.

Blowing it therefore means Obsidian genuinely stalled, **or** that each probe round-trip is being inflated by a busy guest. The timeout error names which, by reporting the probe count and slowest round-trip alongside the furthest startup milestone reached: a handful of probes each taking tens of seconds is a contended guest, and the knob for that is deviceIdleTimeoutInMilliseconds, not this one.