Symptoms
The page looks complete on the tablet, yet the exported PDF omits handwriting made on one imported template.
Do not start by resetting the device. The page looks complete on the tablet, yet the exported PDF omits handwriting made on one imported template. Use the passing comparison as a control while investigating the failing route.
- The failing path: The page looks complete on the tablet, yet the exported PDF omits handwriting made on one imported template.
- Control test: Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer.
- A successful outcome: A newly exported PDF shows every test stroke on another device.
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.
- Annotation layer excluded. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Export format does not embed strokes. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Imported template has protected or hidden overlay. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Preserve the editable original notebook and its cloud copy before changing template or export settings.
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 |
|---|---|---|
| Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Flatten or include the handwriting layer in the device's export options, then export a copy rather than overwriting the original. | 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. |
| Inspect layer visibility and whether the handwriting belongs to an annotation layer excluded by the chosen export format. | Does this separate export format does not embed strokes from imported template has protected or hidden overlay? | Use documented diagnostic views rather than blind replacement. |
| A newly exported PDF shows every test stroke on another device. | 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: The page looks complete on the tablet, yet the exported PDF omits handwriting made on one imported template. Note the affected account, file, connection or physical control and record the current settings. Preserve the editable original notebook and its cloud copy before changing template or export settings.
Run the passing comparison
Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer. 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
Flatten or include the handwriting layer in the device's export options, then export a copy rather than overwriting the original. 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
A newly exported PDF shows every test stroke on another device. 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: annotation layer excluded; export format does not embed strokes; imported template has protected or hidden overlay. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Inspect layer visibility and whether the handwriting belongs to an annotation layer excluded by the chosen export format. 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 “Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer.” 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: A newly exported PDF shows every test stroke on another device. Preserve the editable original notebook and its cloud copy before changing template or export settings.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating annotation layer excluded as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Preserve the editable original notebook and its cloud copy before changing template or export settings.
- 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
A newly exported PDF shows every test stroke on another device.
Use the same baseline case: Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer. 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: Inspect layer visibility and whether the handwriting belongs to an annotation layer excluded by the chosen export format. 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 annotation layer excluded. 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 annotation layer excluded definitely the reason this happens?
No. The same symptom can come from export format does not embed strokes or imported template has protected or hidden overlay. First compare the affected and unaffected paths: Export a newly created blank note and the imported template separately; compare the two PDFs on another viewer. Do not assume any cause without a different outcome.
How can I safely rule out export format does not embed strokes?
Try the reversible correction only after documenting the control: Flatten or include the handwriting layer in the device’s export options, then export a copy rather than overwriting the original. If the behavior does not change, restore the old value and use the deeper observation: Inspect layer visibility and whether the handwriting belongs to an annotation layer excluded by the chosen export format.
What if imported template has protected or hidden overlay 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: A newly exported PDF shows every test stroke on another device.