Aura CBR not recognized?

[Mercador]

Hello, I got another question, folks in here are quite helpful so maybe you'll be able to sort this out for me. I got 3 Kobos at my home, a Mini, an Aura and an Aura One. I tried ultimate manga reader on the Aura One and some CBR for my daughter, it works perfectly fine. However, when I want to put the same CBR on the "normal" Aura (not One), some are recognized, other not. I can see them on the device (I see the files), but I don't see them in the library (or book browser or whatever it is called). Do you have any idea why some of them doesn't show? Thanks a lot!

[davidfor]

All the Kobo devices and all firmware should support comic books. And adding a CBR or CBZ should be enough for them to be imported and read.

The reasons that I can think of for this not to happen are:

• The database is corrupt. This can mean the imported books are not saved to the database and hence not shown when the database is reread. But, if this is the case, I would expect other problems such as losing the reading status of recently opened books.
• A bad book blocking the import. The import can fail reading the books. When it does, it blocks processing any other new books. And it will continue to do this while it is there. The only fix is to find the bad book, remove it and fix it. This is a much less common problem than it was. I don't know if that means that Kobo has improved the handling, or if book creation has gotten better. Probably a bit of both.
• The books are put in a location that isn't being processed. In older firmware, the import process ignored any directory or file whose name started with a dot. The current firmware looks in them, but, it is possible to add a config file entry to ignore directories. If you have done this, it might be the problem.
• Sort or filtering being used isn't showing the book. It's sounds stupid, but, I have added books couldn't find them, added them again, still couldn't find them. Then I realised I'd changed the sort. Or, that the name wasn't what I was thinking it was. And if the clock on the device is wrong...

If the above doesn't answer it, then one question is whether the importing screen is shown when you eject the device. Try connecting to the PC and then ejecting without adding a new book. If the importing screen is shown, then it is finding books.

You can also turn on some logging. In the search on the device, enter "devmodeon". This enables developer mode and the "Developer options" on the "Device information" screen of the settings. There are various options including logging options, but, the base level should include logging of import errors. The log is in the ".kobo" directory with the name "syslog" and the time when it was created. If you do what I suggest above and connect again, this should be created and hopefully will show an error. Some are obvious, some need some interpretation. If there is an error, post it here and hopefully the brains trust here will have an idea of what is wrong.

[Mercador]

The transfer from Calibre is alright, it takes one minute for 200mb. But the Kobo is trying to process new content, it goes at 6% then it stops. And I got the front page without the cbr. Is works on my Aura One so I'm pretty sure it's the Kobo loading that got the issue. Is it possible to log the import feature of the Kobo?

[Mercador]

It looks like the Calibre and the Kobo were out of sync, now everything is working fine... I just wonder why it was working on my Aura One but oh well At least, now I know how to enable logging and seeing what's going on under the carpet, thank you!

[davidfor]

Originally Posted by Mercador

The transfer from Calibre is alright, it takes one minute for 200mb. But the Kobo is trying to process new content, it goes at 6% then it stops. And I got the front page without the cbr. Is works on my Aura One so I'm pretty sure it's the Kobo loading that got the issue. Is it possible to log the import feature of the Kobo?

That says the books were being found and processed. The 6% is pretty much the first book being processed. And it usually means something is wrong with it as I mentioned above.

Originally Posted by Mercador

It looks like the Calibre and the Kobo were out of sync, now everything is working fine... I just wonder why it was working on my Aura One but oh well At least, now I know how to enable logging and seeing what's going on under the carpet, thank you!

The most likely thing is that there was a book that was not on the Aura ONE causing the problem. You probably cleaned that up and that let the rest through. If it happens again, and you work out what the book it was, I'd be interested in seeing it. I would love to work out what is actually triggering this error.

Another possibility is the memory in these devices. The Aura ONE has 512MB of RAM and I'm pretty sure the Aura has only 256MB. It is possible that the combination of books it was importing hit some memory limit. For that matter, it could have been the order they were processed in.

[m-p{3}]

I think I had this issue once where the filenames inside the CBR/CBZ file were actually not valid, with the Em_dash character (—) being used in the image filenames. Renaming all those files inside the CBR/CBZ fixed the problem for me in this case.