The player closes unexpectedly: diagnostic checklist for Enigma2 Receiver
The player closes unexpectedly on Enigma2 Receiver: isolate the device, player, network and source with a clear test sequence and support checklist.
What this symptom means on Enigma2 Receiver
The app exits to the home screen or restarts while importing data or playing an item. This runbook applies when you are already using a player or viewing method supported by the actual device. Begin with one reproducible example; the symptom by itself does not prove that a service, application or network is at fault.
Check the Enigma2 Receiver environment
Receiver and portal workflows may use device assignment rather than a general player login. The portal address, device identity and account policy must match.
- Record the receiver model and firmware version before testing a portal or playlist change.
- Confirm whether the operator expects a device binding, a playlist, or ordinary account fields.
- Keep MAC assignments and complete portal credentials in private support notes, and use supported firmware only.
Identify the full playback chain before testing: device, operating system, player, login format, local connection and destination display or audio route. For an external box, a television may be only the display. In that case, the app version and network measurements belong to the box.
Run a controlled diagnostic sequence
- Record whether the crash follows one item, an import, or every launch.
- Check free storage and the installed application build.
- Restart the device and repeat one reproducible action.
- Test another compatible format or supported player without resetting the device.
Carry out the steps in order while keeping other settings unchanged. Write down the initial result and the result after each change. If a test has no measurable benefit, restore its original setting before continuing. This gives support a history it can interpret and avoids ending with several unexplained adjustments.
Possible explanations to compare
- Low resources or temporary application state
- An application build conflict
- A specific source format that triggers a decoder failure
These are hypotheses to test, not a diagnosis. A problem that follows an account across two otherwise working devices points to a different layer than a problem limited to one app. A failure seen only over one local connection needs a network comparison before an account reset.
What to record for support
| Evidence | Record | Keep private |
|---|---|---|
| Device | Enigma2 Receiver, exact model and operating system build | Serial numbers and account-linked identifiers |
| Player | Publisher, version and selected login type | Password, full playlist URL or portal token |
| Failure | The player closes unexpectedly, exact message and local timestamp | Customer or payment details |
| Comparison | Which single change improved or reproduced the result | Credentials for the comparison account |
A useful report includes what still works. For example, say whether menus respond, another item plays, or a second connection produces the same result. Avoid a screenshot of the full account page when a cropped error message is enough.
Work through the checklist
The checklist on this page is a temporary working aid. Record your final results in your own notes if you need to keep them or send them to support.
When to stop and escalate
A factory reset removes substantial setup information and rarely serves as the first controlled test. Escalate a repeatable crash with the app build and triggering action.
Stop changing settings when you can reproduce the failure and explain the controlled comparison. Send the evidence privately to the relevant app publisher or service operator. If the feature is unsupported on this model, document that finding and use a supported alternative rather than repeating the same reset.
Related Enigma2 Receiver reference
Read the Enigma2 Receiver device guide for setup context, and use the community discussion area to share a redacted description of your test.