Koreader not able to read fb2 within zip on Hisense A5 Pro

kandwo · 04-23-2021, 02:35 AM

I use Koreader on both my Hisense A5 Pro and Nova 3 and sync the progress between them. I recently started reading a book (zip compressed fb2) on my Nova 3. When I tried opening the same file on my A5 Pro Koreader shows the message "(no book information: not readable by engine)" in the file browser. When clicking on the file it displays "No reader engine for this file or invalid file."

Some of the zipped fb2 files show up just fine on the A5. All of the files work perfectly on the Nova 3.

I tried unzipping the file on the A5 and the resulting fb2 opened up just fine. But it wouldn't sync the progress with the still zipped fb2 file on my Nova 3, of course.

What could the reason for this be? I'm confused since I use the latest Koreader from F-droid on both devices and the same files.

EDIT: I thought the files might have corrupted somehow when being transferred to the A5, but they opened up just fine in Alreader X, so that doesn't seem to be it either..

Frenzie · 04-23-2021, 03:09 PM

Could it be that you previously used "open with" on the device where it's working to force a specific engine?

kandwo · 04-23-2021, 04:21 PM

Quote:

Originally Posted by Frenzie

Could it be that you previously used "open with" on the device where it's working to force a specific engine?

Do you mean from a file browser? Certainly not for these files, and I don't recall having done that in general either. I tend to open my files directly through the reader apps, Koreader, Alreader X, etc. And these files had not been opened through any other app than Koreader before - I successfully tried opening one of the files in Alreader X only after having it refusing to work in Koreader.

I tried opening a file browser now and choosing Koreader from the "open with" menu only to get the same error message.

Did I understand your message correctly? Otherwise, please, clarify

Frenzie · 04-23-2021, 04:43 PM

If you had forced MuPDF instead of crengine or vice versa it could explain different behavior. Other files do open? There is no reason the program itself should behave any differently.

kandwo · 04-24-2021, 02:11 AM

Quote:

Originally Posted by Frenzie

If you had forced MuPDF instead of crengine or vice versa it could explain different behavior. Other files do open? There is no reason the program itself should behave any differently.

Do you mean within Koreader itself? If so, I have no idea how to do that and haven't done it manually. Is it possible to check which engine is in use?

I would say that about a third of the files show these errors in the file browser within Koreader. All of those files are zipped fb2, which at first I thought was the problem; but the files that do open are in the same format... And there doesn't seem to be anything wrong with the files since unzipping them manually and then reading the resulting fb2 works in Koreader. They work without unzipping on Alreader X on the same device, and also open just fine on Koreader on my Nova 3.

Could there have been a problem when indexing the files or something? Is there a way to tell Koreader to refresh the database or is this something that is done automatically?

NiLuJe · 04-24-2021, 12:57 PM

Check the engine in use: Long-press on the file, Open with.

There's absolutely no indexing involved in any of this (or, much of anything, actually ^^).

You could check the logcat after switching to verbose debug mode, that might shed some light on why it's failing to load (fair warning: or not ^^).

kandwo · 04-24-2021, 03:40 PM

Quote:

Originally Posted by NiLuJe

Check the engine in use: Long-press on the file, Open with.

There's absolutely no indexing involved in any of this (or, much of anything, actually ^^).

You could check the logcat after switching to verbose debug mode, that might shed some light on why it's failing to load (fair warning: or not ^^).

That's it! Thank you! Now it finally works again. For some reason it did try to open it with the MuPDF engine (altough I haven't changed it to that manually). I chose the Cool reader one and everything opened just fine

My goodness, all these long presses and hidden features of this app.. I hope I learn to fully use it someday!

anarcat · 07-20-2021, 10:06 PM

i'm having the same problem here and a long press does not work. sometimes it even crashes koreader (!), not sure what's up with that.

i tried with "Cool reader" and "mupdf", neither work.

This is a regression in the 2021.07 release too, i downgraded to 2021.05 and the books load fine.

nevermind that: reinstalling 2021.07 fixes the issue completely, probably a fluke in the original install, see also https://github.com/koreader/koreader/issues/7998

04-23-2021, 02:35 AM	#1
kandwo Evangelist Posts: 458 Karma: 11708254 Join Date: Dec 2020 Device: Kindle Paperwhite 3	Koreader not able to read fb2 within zip on Hisense A5 Pro I use Koreader on both my Hisense A5 Pro and Nova 3 and sync the progress between them. I recently started reading a book (zip compressed fb2) on my Nova 3. When I tried opening the same file on my A5 Pro Koreader shows the message "(no book information: not readable by engine)" in the file browser. When clicking on the file it displays "No reader engine for this file or invalid file." Some of the zipped fb2 files show up just fine on the A5. All of the files work perfectly on the Nova 3. I tried unzipping the file on the A5 and the resulting fb2 opened up just fine. But it wouldn't sync the progress with the still zipped fb2 file on my Nova 3, of course. What could the reason for this be? I'm confused since I use the latest Koreader from F-droid on both devices and the same files. EDIT: I thought the files might have corrupted somehow when being transferred to the A5, but they opened up just fine in Alreader X, so that doesn't seem to be it either.. Last edited by kandwo; 04-23-2021 at 06:23 AM.

07-20-2021, 10:06 PM	#8
anarcat Connoisseur Posts: 83 Karma: 192 Join Date: Jul 2013 Location: Planet Ocean Device: Kobo Glo HD, Onyx Boox Note Pro 2, Samsung Galaxy Tab S5e, Pixel 4a	i'm having the same problem here and a long press does not work. sometimes it even crashes koreader (!), not sure what's up with that. i tried with "Cool reader" and "mupdf", neither work. This is a regression in the 2021.07 release too, i downgraded to 2021.05 and the books load fine. nevermind that: reinstalling 2021.07 fixes the issue completely, probably a fluke in the original install, see also https://github.com/koreader/koreader/issues/7998 Last edited by anarcat; 07-20-2021 at 10:25 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Hisense A5 CC Pro	Markismus	Android Devices	12	12-04-2020 07:28 AM
Sell Hisense A5 Pro CC	dennisdd	Flea Market	0	09-14-2020 08:02 AM
Raccoon Reader - reads ePub, fb2, fb2.zip, txt on WP7 for free	Andrei_Shvydryk	Reading and Management	0	10-31-2011 03:17 PM
huge oversize zip-fb2??	rbruce1314	Conversion	4	02-10-2011 04:40 PM
Failure converting zip to fb2	rbruce1314	Calibre	2	11-17-2010 05:39 PM

04-23-2021, 03:09 PM	#2
Frenzie Wizard Posts: 1,742 Karma: 730681 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Could it be that you previously used "open with" on the device where it's working to force a specific engine?

04-23-2021, 04:43 PM	#4
Frenzie Wizard Posts: 1,742 Karma: 730681 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	If you had forced MuPDF instead of crengine or vice versa it could explain different behavior. Other files do open? There is no reason the program itself should behave any differently.

04-24-2021, 12:57 PM	#6
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Check the engine in use: Long-press on the file, Open with. There's absolutely no indexing involved in any of this (or, much of anything, actually ^^). You could check the logcat after switching to verbose debug mode, that might shed some light on why it's failing to load (fair warning: or not ^^).

Advert

Advert