Applies to: Roku or comparable documented streaming device; distinguish television power/standby from an actual device system restart.
The useful distinctions
- Roku says a TV power-button action is not necessarily a system restart.
- Its system restart is a distinct device operation.
- Diagnostic inference to test: A resume-only symptom narrows a state-transition report without identifying its cause.
Define the starting state
Turning a screen off does not establish what happened to the external player. Record which device entered standby and whether its startup sequence was observed later. A fresh app session and a complete device restart are also different states. Use the exact manufacturer terminology so a support engineer can reproduce the same transition.
Keep one reference across states
Choose a lawful item with a reliable visible and audible section. Compare it after normal resume and after the separately documented fresh state. Note if the player renegotiates an output format or selects another audio destination. Those changes can explain why the two starts behave differently, so they belong in the result rather than being treated as invisible background details.
Use the pattern for escalation
If the complaint occurs only after resume and disappears in the fresh comparison, report that state dependency. It does not establish a firmware regression or identify which component mishandled the transition. Keep the model/software version and exact steps compact. Avoid a factory reset that erases settings before the repeatable resume sequence and its differences have been recorded.
A focused way to proceed
- Record whether the device truly restarted or only the display/TV power changed.
- After normal standby/resume, retry the same lawful reference and record the outcome.
- Use the manufacturer-supported fresh-session/restart method separately if needed.
- Keep account, network, output route and reference unchanged.
- Compare the two start states and preserve any changed format or audio destination.
Worked example · synthetic
Hypothetical example: the same reference is silent after an observed standby return but audible after a documented device restart, with the audio destination changing between states. The user reports both the resume dependency and the routing change instead of asserting an unexplained service fault.
When to stop or ask for help
Fresh state, app reopen and device restart must be named accurately. This comparison does not prove a firmware bug or guarantee a permanent fix.