View Single Post
Old 02-18-2015, 12:14 AM   #2
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
I haven't heard of issues with processing CBR and CBZ files. I don't read mangas or comics, but the few I have tested had no issues. As such, the following are some thoughts and questions that hopefully will lead to a fix or workaround.

I'm not sure what you mean by "the reader struggles to read a file". Are you meaning during the initial processing or when you open the manga to read it?

Assuming it is during the processing, how many manga are you processing at a time and how big are they? When CBR/CBZ are processed, the names of the files inside them are extracted and put into the database. As the format is a lot simpler than an epub, the only things I can think to go wrong is if the manga was very big with lots of images, or the internal file names were something that the firmware couldn't handle.

After the factory reset, how are you putting the manga back on the device? Are you adding a few and then adding more later. And then it goes into the loop? Or are you putting them all back on and it works OK, but later does the processing loop?

The factory reset is probably a built-in safety feature. Each time the device restarts, it checks to see if nickel (the UI) has started before. If several reboots have been done without nickel starting successfully, it will prompt to do a factory reset. With the continual restart you describe, this has probably happened a few times.

And something missing from your report, what firmware version are you running? Did this ever work and if so, which firmware was that?
davidfor is offline   Reply With Quote