View Single Post
Old 07-01-2018, 08:38 PM   #54
downeaster59
Wizard
downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.
 
downeaster59's Avatar
 
Posts: 1,251
Karma: 2957301
Join Date: Apr 2014
Location: Rochester, NY
Device: Boox Go 10.3, Kobo Libra 2
Quote:
Originally Posted by NiLuJe View Post
Be aware that the "no framework" mode (besides being of dubious usefulness there) is severely hampered on FW 5.x, preventing basically anything low-level but framework-related (buttons, suspend, screensavers if SO, among other things) from working properly and/or at all.

It's main use-case was for the DX/DXg and its combo of limited RAM and larger screen, making it a tight fit in terms of availmable memory.

That doesn't really apply to anything w/ 512MB of RAM, a switch which happened, err, a while ago .
When I use the "regular" mode, KOReader freezes constantly. That's why I went to "no framework".

Should I send you the crash log?

Edit: Just tried it again in "regular" mode. I try to open one book and another menu opens. Then it freezes.

Edit #2: Here's the crash.log, if it helps.
Attached Files
File Type: zip crash.log.zip (4.7 KB, 140 views)

Last edited by downeaster59; 07-01-2018 at 08:44 PM.
downeaster59 is offline   Reply With Quote