Troubleshooting
Record the exact message and the point where the update stopped: connection, preparation, upload, or refresh. Keep the device model and app version available.
The phone cannot identify the display
Check that the phone and app are supported for your exact product, that NFC is enabled where required, and that the phone is aligned with the device's NFC area. Follow the product's power instructions.
For devices relying only on the NFC field, the app must enable energy harvesting again whenever that field is removed and reapplied. An NFC tag detection alone does not prove that the display is ready.
If Metadata is missing, unsupported, or identifies an unexpected panel, stop. Do not choose a similar size to bypass the problem. Check display selection or contact support.
Preparation appears stuck
The initial receiving response is followed by a separate ready event. The app must not send the first chunk before it receives that event. Its documented Begin-to-ready window is 20 seconds.
On timeout, use the app's recovery flow: it should clear any stale response, check status, and restart a complete transfer if required. Do not repeatedly press update or use a generic NFC writer.
The NFC connection was lost during upload
Keep or restore a stable position and follow the app's bounded recovery flow. Transient tag-loss or busy responses can be retried by the app, but a reported reupload_required state always means a complete new upload. Do not resume from an old progress percentage.
Missing, corrupt, or out-of-order chunks do not produce individual chunk error responses. The final status check detects the failed transfer.
Upload reached the end, but the screen is not finished
Finishing data transfer is different from finishing refresh. The app first verifies loaded, then commits the image, consumes the response, and waits through the preparation interval and physical refresh.
NFC commands must remain quiet during this period. Wait for the automatic completion event; a status recovery request belongs after the expected refresh window, not in a tight polling loop.
The app reports a display error
| Result | What to do |
|---|---|
| REFRESH_START_FAILED + refresh_retryable | Let the app retry the same Commit within the retained-image window. Do not manually start repeated refreshes. |
| REFRESH_BUSY_TIMEOUT + reupload_required | The refresh timed out. Follow a complete new upload; seek support if the fault repeats. |
| POWER_CYCLE or SESSION_RESET + reupload_required | The device restarted and the loaded image is no longer trusted. Restore the required connection/power and upload the entire image again. |
| REUPLOAD_REQUIRED + reupload_required | Restart the complete image transfer; partial resume is unsupported. |
| DISPLAY_CLEANUP_FAILED + complete | The visible update succeeded. Report the cleanup fault and do not repeat the refresh. |
| UNSUPPORTED_OPERATION | The app may be using an unsupported operation. Display Text is unsupported; Display Fill is not a production update path. Confirm the app version with support. |
Do not erase, flash, or change hardware as a routine recovery step.
Colors or text look wrong
Check the preview and Metadata together. The two 2.9-inch panels have different palettes despite matching pixel dimensions. The 7.5-inch SE0750NW26-TNG-A0 is three-color, including red.
Check orientation, clipping, and missing glyphs before sending a new image. See text and images.
Prepare a support request
Include the model, panel identity reported by the app, app/phone/operating-system versions, firmware version if available, exact error, and whether connection or power was interrupted. Describe what the screen shows and whether the app reported complete. Remove personal content from any screenshot.
Contact support if the same failure repeats after the documented recovery.