Quote:
Originally Posted by davidfor
It's just you? 
I have tested a few, including one that is 130MB with lots of images, with no problems. This is with my Glo HD.
Were these books that were on the device before the update? If so, can you try removing one of PDFs and adding it back? This shouldn't change anything, but, it is something to check.
If it is sickel doing the reboot, the device should hang for about a minute, then restart. The light will probably go off before go off a few seconds before the screen changes for the reboot. If something has crashed, there might be a stack log in the .kobo directory. If there is, it can give the Kobo developers a very good idea of what went wrong. |
Lovely.
The majority of pdfs were ones that were there prior to the firmware upgrade, but I only noticed this behaviour when I initially tried to read one I had just loaded on so I don't think it matters.
That light thing does happen the way you say each time, so it probably is sickel.
I can't find anything like a log in .kobo, though. The only things in there are folders labeled certificates, dict, guide, kepub and Kobo (and no log files inside them either), as well as the affiliate.conf, BookReader.sqlite, device.salt.conf, KoboReader.sqlite and version files. Is there a specific directory where these log files would exist? I am open to pulling out the card and looking at rootfs if needed (I have access to a Linux machine too, although I just checked and /var/log is empty).
That said, my 64GB card is close to being full and my device database is just over 1GB. It could be that it just takes longer for pdfs to load now, but it can't finish before sickel kills it. Should I risk disabling sickel using
one of the mods that were posted here a while back to see if that works?