When open app it is not rotate alignment with the book open.
Steps to reproduce
crash.log (if applicable)
crash.log is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:
/mnt/private/koreader for Cervantes
koreader/ directory for Kindle
.adds/koreader/ directory for Kobo
applications/koreader/ directory for Pocketbook
Android logs are kept in memory. Please go to [Menu] → Help → Bug Report to save these logs to a file.
Please try to include the relevant sections in your issue description.
You can upload the whole crash.log file (zipped if necessary) on GitHub by dragging and dropping it onto this textbox.
If your issue doesn't directly concern a Lua crash, we'll quite likely need you to reproduce the issue with verbose debug logging enabled before providing the logs to us.
To do so, go to Top menu → Hamburger menu → Help → Report a bug and tap Enable verbose logging. Restart as requested, then repeat the steps for your issue.
If you instead opt to inline it, please do so behind a spoiler tag:
The rotation is saved per book and overrides your device's general rotation orientation. To change the book's orientation, use the bottom menu (1st tab) or program a gesture of your choice.
When open app it is not rotate alignment with the book open.
Steps to reproduce
crash.log
(if applicable)crash.log
is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:/mnt/private/koreader
for Cervanteskoreader/
directory for Kindle.adds/koreader/
directory for Koboapplications/koreader/
directory for PocketbookAndroid logs are kept in memory. Please go to [Menu] → Help → Bug Report to save these logs to a file.
Please try to include the relevant sections in your issue description. You can upload the whole
crash.log
file (zipped if necessary) on GitHub by dragging and dropping it onto this textbox.If your issue doesn't directly concern a Lua crash, we'll quite likely need you to reproduce the issue with verbose debug logging enabled before providing the logs to us. To do so, go to
Top menu → Hamburger menu → Help → Report a bug
and tapEnable verbose logging
. Restart as requested, then repeat the steps for your issue.If you instead opt to inline it, please do so behind a spoiler tag:
crash.log
```