Symptoms
Erased strokes vanish immediately, then return on another device after synchronization.
The useful clue here is what still works: Erased strokes vanish immediately, then return on another device after synchronization. That narrows the test to the point where the two paths diverge.
- The failing path: Erased strokes vanish immediately, then return on another device after synchronization.
- Control test: Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits.
- A successful outcome: The deleted test stroke stays absent on both devices after reopening.
Why It Happens
For e-ink products, response speed and export behavior vary widely between native notebooks, EPUB files and PDFs. Confirm the file type and the feature the manufacturer actually supports.
There are three genuinely different layers worth checking; use the observation in the table to decide which one is implicated. None of these is proven merely by the symptoms.
- Competing offline revisions. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Stale cloud version. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Eraser action not committed to editable layer. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Never overwrite the only copy of handwritten notes during conflict resolution.
Save the current configuration or capture screenshots of the exact option values; where a file or recording is involved, work on a disposable duplicate. If this is shared equipment, ask the owner or administrator before changing it. Prefer a safe test item over real customers, medical decisions, paid transactions or irreplaceable data.
Write down the device model, platform, observed time of failure, and which action still works. These details will distinguish an unsupported feature from a malfunction and will be useful if escalation is required.
Problem-Specific Diagnosis
Use the following route rather than guessing based on a product name. The expected differences are designed for this particular failure.
| Action or observation | Meaning of the result | Decision |
|---|---|---|
| Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Allow the notebook to finish syncing on the original device and check the correct account and notebook. | Does the low-impact correction restore the exact failure without altering the control case? | Re-test; reverse the change if the original symptom is unchanged. |
| Compare revision timestamps and resolve the conflict by exporting both versions before selecting an authoritative copy. | Does this separate stale cloud version from eraser action not committed to editable layer? | Use documented diagnostic views rather than blind replacement. |
| The deleted test stroke stays absent on both devices after reopening. | Is the same original symptom gone after a normal repeat? | Record the pass condition and preserve the working settings. |
If the control case fails as well, the fault may be broader than this guide. Stop at that point and check the shared power, account, access or media path before applying the narrow fix.
Beginner and Advanced Paths
Start with the reversible Beginner path. The Advanced path examines a different layer when the first route fails; it is not a repetition of the same restart or setting.
Step-by-Step Troubleshooting
Choose the simple reversible checks first, then investigate the deeper system layer only if necessary.
Record the exact failure
Confirm the behavior without guessing: Erased strokes vanish immediately, then return on another device after synchronization. Note the affected account, file, connection or physical control and record the current settings. Never overwrite the only copy of handwritten notes during conflict resolution.
Run the passing comparison
Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits. Keep the working and failing cases separate. If both fail, stop and investigate the common path instead of forcing a narrow repair.
Apply the least disruptive correction
Allow the notebook to finish syncing on the original device and check the correct account and notebook. Change only this setting or route; do not reset unrelated profiles, storage or pairing records. Save the previous value so it can be restored.
Retest and keep the result
The deleted test stroke stays absent on both devices after reopening. Repeat after a normal reopening or reconnect. If the control case gets worse, undo the last change and write down the difference.
Separate the three underlying layers
Test the hypotheses independently: competing offline revisions; stale cloud version; eraser action not committed to editable layer. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Compare revision timestamps and resolve the conflict by exporting both versions before selecting an authoritative copy. Use only read-only diagnostics or documented configuration screens first. Capture logs and timestamps rather than removing the component or reinstalling software blindly.
Cross-check with an independent path
Where possible, repeat “Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits.” using a second supported account, safe sample file, physical input, known-good cable or alternate compatible application. Change only one variable and note which outcome follows it.
Choose a reversible targeted escalation
If the deeper check isolates a fault, use a vendor-supported fix or authorized service for that layer; otherwise restore original values. Finish only when: The deleted test stroke stays absent on both devices after reopening. Never overwrite the only copy of handwritten notes during conflict resolution.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating competing offline revisions as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Never overwrite the only copy of handwritten notes during conflict resolution.
- Calling the issue fixed after one status indicator changes but before repeating the original operation.
- Discarding the working configuration or the only original file before a replacement has been verified.
How to Verify the Fix
The deleted test stroke stays absent on both devices after reopening.
Use the same baseline case: Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits. Then repeat the previously failing operation after a normal close-and-open, reconnect or next scheduled cycle, whichever matches the scenario. Confirm the part of the system that was already working is still unaffected.
Where a result can be measured, retain the test timestamp, file name, screenshot or device state. A temporary success that cannot be repeated is not yet a confirmed repair.
If the Problem Continues
Escalate from the surface symptom to the narrower mechanism: Compare revision timestamps and resolve the conflict by exporting both versions before selecting an authoritative copy. If this identifies a hardware, account-policy or service limitation, use the manufacturer’s authorized support route rather than bypassing controls.
When opening a support case, supply the model, software/firmware version actually installed, the failing operation, the successful comparison, the three possible explanations checked, and the final observed result. Redact account identifiers, access codes, serial-number photos and personal information from public posts.
Prevent Recurrence
Keep a short note of the confirmed working configuration, particularly the setting implicated by competing offline revisions. Repeat the disposable comparison after an app update, device replacement, major account change or new connection only when that change plausibly affects this issue.
Retain a recovery path: spare test material, a saved profile, a restore point, a backup copy or official service information, as appropriate for the device. Do not schedule risky resets as routine maintenance.
FAQ
Is competing offline revisions definitely the reason this happens?
No. The same symptom can come from stale cloud version or eraser action not committed to editable layer. First compare the affected and unaffected paths: Erase one disposable stroke, wait for confirmed sync, and compare both devices before making further edits. Do not assume any cause without a different outcome.
How can I safely rule out stale cloud version?
Try the reversible correction only after documenting the control: Allow the notebook to finish syncing on the original device and check the correct account and notebook. If the behavior does not change, restore the old value and use the deeper observation: Compare revision timestamps and resolve the conflict by exporting both versions before selecting an authoritative copy.
What if eraser action not committed to editable layer turns out to be responsible?
Do not force an unsupported setting or a factory reset. Keep the evidence and ask the manufacturer or responsible administrator to investigate the isolated layer. The measurable pass condition remains: The deleted test stroke stays absent on both devices after reopening.