Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - kweckwor

Pages: [1] 2
eLibrary Manager / Re: Issue with adding books [duplication]
« on: January 05, 2020, 09:00:37 pm »
If a book file path changes as a result of the folder restructure (which I assume it would), then the progress will be lost. The book progress is associated with a specific book and changing a book file path effectively results in a new book.

I understand that you are using eLibrary Manager Basic, but just so you know, in the full version, book position for the last 20 books opened (configurable, so it can be set higher) is saved based on book title and author(s). In that case, if a book file path changes, then as long as the title and authors remain the same, the first time the new book is opened in the reader, it would open at the last reading position (and therefore restore the progress).

So I guess the bottom line is that, in the basic version, there is no way to easily carry over book position and progress if the book file is moved to a new folder in the device file system. In the full version, you could carry over the last 20 opened book positions (and progress) as long as each of those books is opened in the reader which would restore the last position.

eLibrary Manager / Re: Issue with adding books [duplication]
« on: January 05, 2020, 07:34:23 am »
On re-reading the original post, I wanted to mention a couple of extra things.

By "onboard file explorer", you might have meant an external file explorer from which you can launch the reader of your choice, as opposed to a "file explorer" view in the eLibrary Manager app itself. You're correct that an external file explorer will likely allow you to launch my reader. I don't know what file explorers are available in the Amazon App Store, but I would suspect there should be a number to choose from.

One more thing to mention is that, by removing a book entry from your eLibaray Manager library does not delete the underlying book file. It simply removes the app record for it. Performing a scan again will add the record back. So if you don't want a book to reappear on every scan, you would need to delete the underlying book file so a subsequent scan won't find it. You can do that with a file explorer on the device, if you have one installed, or if not, you should be able to do the same by connecting your device to a PC over USB so that you see the device shared storage as a drive on your PC.

One of the fundamental principles of my app is that it never touches book files on your device. It simply allows you to have access to files that have been externally copied to the device, but it never updates or deletes those files.

eLibrary Manager / Re: Issue with adding books [duplication]
« on: January 05, 2020, 07:22:15 am »
Each entry in the app library represents a separate file with a distinct file path. If you're seeing what looks like duplicate entries for the same book, then that probably means you have multiple files for the same book on your device. You can see the file path in the Book Information view, so check that for each of the duplicate entries to see if the File Path value is different for each duplicate. By default you should see File Path in the Book Info view, but if not, you can enable that in the eLibrary Settings "Book Info Properties" setting by adding "File Path" to the selected properties.

With respect to your mention of "an onboard file explorer", the full version of the app includes a Book Info Browser which allows you to browse your library based on different metadata/book info criteria. One browsing criteria available is File Path, so that gives you a way to navigate the file system to see the books loaded in your library. This feature isn't available in the Basic app though.

ePub Reader / Re: Letters in night mode are dark
« on: January 03, 2019, 03:31:46 pm »
Hi Peregrina and anyone else who might be interested in this topic,

Just a quick update. I've got a fix that I'm happy with and I'll be releasing it soon (version 4.1.1). I just need to test things out a little more thoroughly, and if that goes well, then I should be able to release within a week or so.


ePub Reader / Re: Letters in night mode are dark
« on: December 26, 2018, 02:59:37 pm »
Hi Peregrina,

I suspect the book file is explicitly setting the text colour, so you may not find the same issue with other books.

In general, I've taken the approach to apply styles only when those styles are not explicilty set in a book file. My rationale has been that, if a book author/provider is going out of his/her way to set styles explicilty, then I assume there is an esthetic reason for doing that and I don't try to override it. But as I find cases where the general rule may not work out for the best, I'm willing to see what I can do to force a specific style to override what is coded in the book. I'll see what I can do for this scenario.

You should know though that even if I can make this change (I'm assuming I should be able to - but I'll need to figure it out to be sure), there may always be cases where styles are applied at some level of nesting in the parent hierarchy for book content that can clash with whatever styles I apply. So it may not be foolproof. ePub book content is just HTML, so styling possibilities are almost endless, so without stripping all original styles and only applying my own, it can be tricky to ensure that any general book format works well with overrides that I apply.

As I mentioned above, my strategy has been to try and be as faithful to the original book format and styling as I can, so that books are rendered as intended by the author. I still want to keep to that philosophy as much as I can. But this sounds like a reasonable exception to the general rule.

Thanks for the feedback! I'll let you know if I can make this happen in a way that I'm happy with.

Karl Weckworth

Calibre Documents Provider / Version History
« on: September 09, 2018, 11:26:44 am »
VERSION 1.2.5 (2020-01-19):
  • Minor improvements.

VERSION 1.2.4 (2019-11-17):
  • Synchronize with system light/dark mode on Android 10+.
  • Internal optimizations.
  • Note: Due to issues on older versions of Android with the latest Android libraries required for Android 10 system dark/light mode integration, I've started producing separate builds for Android versions greater than or equal to version 8 and lower than 8. In the "About" box for the app, if the "Build" version number has a ".102" prefix, then the app does not support Android 10 system dark/light mode integration.

VERSION 1.2.3 (2019-09-09):
  • Update book cover image.
  • Minor fixes.

VERSION 1.2.2 (2019-06-28):
  • Migrate to Android 10 (Q).

VERSION 1.2.1 (2019-04-18):
  • Updates for Android Q.

VERSION 1.2.0 (2019-03-02):
  • NEW: Automatically detect when calibre book file data becomes stale.
  • NEW: Calibre Documents Provider home page.
  • NEW: Add support for provider file search.
  • Minor performance improvements.

VERSION 1.1.0 (2018-12-06):
  • NEW: Allow integrating applications like eLibrary Manager to update book information (metadata) in calibre libraries.

VERSION 1.0.3 (2018-11-04):
  • Update URL references to HTTPS.

VERSION 1.0.2 (2018-09-26):
  • Minor fixes.

VERSION 1.0.1 (2018-08-07):
  • Updates for Android 9 (Pie) and Chrome OS.

VERSION 1.0.0 (2018-05-28):
  • Initial release.


You can find comprehensive online documentation for this product at Calibre Documents Provider.

You can also watch the YouTube tutorials at

You can access all of the above from the Calibre Documents Provider About Box directly from the application on your device. Here's a screen capture of the About Box - just tap on the link for your area of interest:

For support/queries/comments, please feel free to start new topics, or contact

Hi Truss,

What kind of activity are you finding the stuttering/freezing occurring with? Is that when using the reader or when using the library manager? Maybe you can describe what you are doing and how things are behaving. If you can also let me know some more environment details like Android version and version of the app, that might help as well. Is this something that's degraded recently, or have you been having these issues from the start?

Hopefully we can figure something out.


I will be releasing version 3.1.4 of eLibrary Manager within the next couple of days. If you use the software on Android 7.x, you should be aware of the following:

Performance on Android 7.0+
Current performance on Android 7.0+ is less than optimal, especially if book files are large (e.g. graphic novels, for example). As of eLibrary Manager v3.0, the application is using the Android Storage Access Framework (SAF) for file access. Using this framework, accessing book files is slower, most noticeable for large files (the larger the file, the slower the performance). To address this, I need to add the requirement for WRITE_EXTERNAL_STORAGE permissions back (I had removed that with the move to SAF) in order to efficiently access book file. So on updating to 3.1.4, you will be prompted to give the app those permissions on first launch. Hopefully the Android platform will improve over time to fill in the functional gaps with SAF - then I will remove the permission requirement. With version 3.1.4, performance on Android 7.0+ is much better.

Launching External Apps
Since Android 7.0 (and SDK level 24), Android no longer allows file URIs (e.g. file:///folder/book.epub) to be used when invoking external applications. With version 3.1.4 I am targeting the latest SDK level (currently 25). That means the app now launches external apps (e.g. readers, image viewers) differently. Most likely your favourite reader and image apps have already been updated to handle this change in the Android platform and you won't notice any change in behaviour.

However, if you discover that those apps are no longer being launched, that probably means that they still expect file URIs to identify book files. In that case, download and install the new eLibrary File URI Launcher add-on app. Installing that app will allow eLibrary Manager to behave as before. See for more information and for download links.


eLibrary Manager / Re: Screen and Font Colors
« on: June 22, 2016, 06:00:03 pm »
A quick update on this topic...

I've just released version 2.2.3 that includes the ability to customize Night Mode colour scheme. You can read more about it at

eLibrary Manager / Re: Screen and Font Colors
« on: March 27, 2016, 05:41:41 pm »
There is a Night Mode option for the reader. You can see information about that in the online documentation at
The night mode presents book content with light text on a dark background. The above web site has screen captures demonstrating what it looks like. As described in the docs, you can toggle between day and night mode using the Reader Display Options dialog or through the ePub Reader Display Settings.

For the full version, that is available on Google Play and Amazon App Store. If you have access to Amazon Underground, the Underground version of the app is functionally equivalent to the full version, but it is not available in all geographies. Underground apps are free to download. You can find information about additional features in Full/Underground that you do not get in Basic in the online documentation as well, at
Let me know if you have any questions.



eLibrary Manager / Re: external application support
« on: February 04, 2016, 05:39:06 am »
I haven't heard anything back from the original poster on this, but I will report on what my investigation has uncovered:
  • With mimetypes cbr=application/x-cbr and cbz=application/x-cbz, I've been able to launch a variety of comic readers that I randomly downloaded and tried.
  • It may still be the case that the default Nook comic reader (or any individual specific comic reader) does not respond to external requests to launch through intents. If that is the case then this app cannot integrate with those readers.
  • I am adding the above mimetypes for comics into the default configuration, so it won't be necessary once that is released to define your own. That will be included int the next update.

eLibrary Manager / Re: external application support
« on: January 29, 2016, 07:55:18 pm »
One more thing you should try, I've just realized. In your mimetype.txt file, you should remove the leading slash from the mimetype values. So use
  • cbr=application/x-cbr
  • cbz=application/x-cbz
rather than
  • cbr=/application/x-cbr
  • cbz=/application/x-cbz
That might work.

eLibrary Manager / Re: external application support
« on: January 29, 2016, 05:00:07 pm »
In order to launch an external application, that application needs to respond to Android Intents to open resources for which it's declared a corresponding IntentFilter. It might be the case that the default Nook comic reader doesn't respond to these. Is the reader an application that you installed from an app store or did it come bundled with your Nook? If I can install the same app (I don't have a Nook), I can see if I can get it to work.

eLibrary Manager / Re: PDF book covers
« on: December 18, 2015, 05:57:20 pm »
Hi Reader101,

Right now, eLibrary Manager only really understands ePub books. It treats non-ePub books (like PDF) as "black box" and doesn't access the contents. I'll take look and see if I can do that without resorting to third-party libraries, which I've been mostly avoiding up to now. I can't promise anything until I have a chance to do my homework on the topic, but I'll see how possible it might be.

However, since you mention that you use calibre, there is another option available that will allow you to load PDF metadata (i.e. book information) from calibre into eLibrary Manager. If you configure calibre to "Save to disk" with separate cover and OPF files in addition to the PDF file, my app will read the metadata (including cover) and load that into the app library.

You can see instructions on how to do that in the online documentation at My video tutorial (Part 2) at also demonstrates this at around the 13:46 minute mark. I'll list some of the key points here:
  • In calibre, set the Saving books to disk preferences to enable the "Save cover separately" and "Save metadata in a separate OPF file" options.
  • Invoke the "Save to disk" action to export your PDF books to your device. That should create 3 files for each book, of types PDF, OPF and JPEG.
  • In eLibrary Manager, scan for books as normal, and book information and cover should get loaded into the app library based on the data contained in the extra files saved.
A couple of things I want to point out though:
  • Unfortunately, the "Save cover separately" and "Save metadata in a separate OPF file" options in calibre only apply to the "Save to disk" action and they have no effect on the regular "Send to device" action that you are probably used to using. Therefore, to produce the extra OPF and cover files, you need to use "Save to disk".
  • On one of my devices, the calibre "Save to disk" action does not seem to work when I target any drives on that device. So when loading books through "Save to disk" on this device, I need to save to my computer first, and then copy manually to the device as a separate step. I'm not sure why this happens - I assume its just something weird with how calibre and Android (5.1.1 is the version I'm running) interact with mounted drives through Windows. On my phone, the operation works just fine, so it doesn't seem to be a global problem. But I thought I'd mention it just in case you run across the same issue.
Please let me know if you have any questions.



Pages: [1] 2