Symptoms
Tapping a footnote returns to a nearby but incorrect paragraph only after the book font size has been changed.
The useful clue here is what still works: Tapping a footnote returns to a nearby but incorrect paragraph only after the book font size has been changed. That narrows the test to the point where the two paths diverge.
- The failing path: Tapping a footnote returns to a nearby but incorrect paragraph only after the book font size has been changed.
- Control test: Tap the same footnote at default font size and enlarged font size while recording the return location.
- A successful outcome: The footnote returns to the originating sentence after multiple font-size changes.
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.
- Reflow cache offsets stale. This explanation predicts a different result in the comparison test or the more advanced inspection.
- EPUB backlink anchor incorrect. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Reader back stack replaced by chapter navigation. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Keep the original book file and reading-position data before attempting a corrected EPUB conversion.
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 |
|---|---|---|
| Tap the same footnote at default font size and enlarged font size while recording the return location. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Close the note using the reader back action rather than reopening the chapter from the table of contents. | 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. |
| Check EPUB internal anchor identifiers, reader reflow cache and whether the document is fixed layout or reflowable. | Does this separate EPUB backlink anchor incorrect from reader back stack replaced by chapter navigation? | Use documented diagnostic views rather than blind replacement. |
| The footnote returns to the originating sentence after multiple font-size changes. | 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: Tapping a footnote returns to a nearby but incorrect paragraph only after the book font size has been changed. Note the affected account, file, connection or physical control and record the current settings. Keep the original book file and reading-position data before attempting a corrected EPUB conversion.
Run the passing comparison
Tap the same footnote at default font size and enlarged font size while recording the return location. 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
Close the note using the reader back action rather than reopening the chapter from the table of contents. 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 footnote returns to the originating sentence after multiple font-size changes. 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: reflow cache offsets stale; EPUB backlink anchor incorrect; reader back stack replaced by chapter navigation. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Check EPUB internal anchor identifiers, reader reflow cache and whether the document is fixed layout or reflowable. 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 “Tap the same footnote at default font size and enlarged font size while recording the return location.” 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 footnote returns to the originating sentence after multiple font-size changes. Keep the original book file and reading-position data before attempting a corrected EPUB conversion.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating reflow cache offsets stale as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Keep the original book file and reading-position data before attempting a corrected EPUB conversion.
- 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 footnote returns to the originating sentence after multiple font-size changes.
Use the same baseline case: Tap the same footnote at default font size and enlarged font size while recording the return location. 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: Check EPUB internal anchor identifiers, reader reflow cache and whether the document is fixed layout or reflowable. 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 reflow cache offsets stale. 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 reflow cache offsets stale definitely the reason this happens?
No. The same symptom can come from EPUB backlink anchor incorrect or reader back stack replaced by chapter navigation. First compare the affected and unaffected paths: Tap the same footnote at default font size and enlarged font size while recording the return location. Do not assume any cause without a different outcome.
How can I safely rule out EPUB backlink anchor incorrect?
Try the reversible correction only after documenting the control: Close the note using the reader back action rather than reopening the chapter from the table of contents. If the behavior does not change, restore the old value and use the deeper observation: Check EPUB internal anchor identifiers, reader reflow cache and whether the document is fixed layout or reflowable.
What if reader back stack replaced by chapter navigation 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 footnote returns to the originating sentence after multiple font-size changes.