Koreader running on Kobos (all of them, hopefully!)

[Ken Maltby]

Originally Posted by ectoplasm

Zsync doesn't add involve adding code to the server, the code is client side and pulls from the server via http and byte ranges. There must be logic in the koreader implementation to seek out other clients. I looked at the code, but didn't feel inclined to undertake to work out a way to imitate a client (maybe simple, maybe not).

I found a fairly simple alternative (at least one I know how to implement), and that is serving up a bare-bones ODPS file from Lighttpd. I got the idea from Calibre's ODPS server. I can script a file change monitor, which generates the ODPS file list, without all the extraneous tags Calibre uses which I don't care about.

This gets me where I wanted, which is to drop epubs in a folder (step 1), and then pull them later from the reader (step 2). I do this now with nickel and kobo's browser (and could still do that from KSM if I load up nickel). I prefer this to the standard approach, where both steps must be done at the same time. Note that my "server" is always on, so this wouldn't work for folks without a server.

I also prefer to do such things with OPDS, if you can do it with a browser you should be able to add the URL to Koreaders OPDS listings of catalogs. It can't handle authentication yet, though. (zsync would not be good for an epub, unless you were writing it and wanted to sync to your drafts as you work on the story. Or if you were editing it.)

Luck;
Ken

[ectoplasm]

Originally Posted by Ken Maltby

..if you can do it with a browser you should be able to add the URL to Koreaders OPDS listings of catalogs. It can't handle authentication yet, though. (zsync would not be good for an epub, unless you were writing it and wanted to sync to your drafts as you work on the story. Or if you were editing it.)

ODPS via Lighttpd and Calibre both work from koreader in my tests. I haven't decided which one to settle on.

I never actually tested zsync successfully. My aim was not to update existing files, but rather to pull new ones from a central location. Does koreader+zsync only sync pre-existing files? If so, not what I was looking for.

[Ken Maltby]

Originally Posted by ectoplasm

ODPS via Lighttpd and Calibre both work from koreader in my tests. I haven't decided which one to settle on.

I never actually tested zsync successfully. My aim was not to update existing files, but rather to pull new ones from a central location. Does koreader+zsync only sync pre-existing files? If so, not what I was looking for.

Zsync is also used for the "Over The Air" (OTA) update process. If you can get to one of the OTA servers (http://vislab.bjmu.edu.cn/apps/koreader/ota/ is back now.) you can see how it is setup, and the "koreader-kobo-latest-nightly.zsync" file that the plugin uses to get the right download for the OTA process. Zsync's main feature is that it will only download the new or changed parts/the delta, of a file it is syncing. The Koreader device to Koreader device transferring is the menu item in Koreader.

Koreader integrates with calibre in a number of ways. If you are using calibre to organize your ebooks, you might want to let calibre see a hidden folder on your device as a device in calibre. You can then have caliber send selected books to that device. Calibre will create its own file structure on your device, that way.

I prefer to use my own hidden file structure and only use calibre's built-in "Content Server" and Koreaders OPDS function to wirelessly transfer ebooks, that I have cleaned up in calibre, to folders of my choosing.

Luck;
Ken

[roger64]

About Zsync OTA process (Kobo).

I would like to implement this feature. I read that, from last April, we can use it with KSM and the .adds folder.

I know that, on Ubuntu, they can use zsync for OTA update of iso files, entering a command like this:
zsync http:// (and the complete path of the iso file)

However, my zsync menu on koreader offer me two choices: Publier (publish) and S'abonner aux documents, (subscribe to..) which gives me access to my files. I see no place where I could enter an url address.

Could I get some practical information about this? How old can be the updated file?

EDIT: success

I opened the wifi using the KSM 07 menu.

I found the right OTA menu on koreader (this is recommended...) , selected the develop channel (since no update was proposed for me on the stable channel), confirmed the Chinese server - among three -, was offered to update to the version below, accepted the proposed update, was warned it would take some time, was informed after one minute that the update would take place after reboot, the update was done after reboot (one minute) and I am now with the latest version:

v2014.11-322-g0293816 dated 8 September 2015

Wow !... Really impressed and how convenient!

[roger64]

Charging.

With Nickel, I can use the charger of my camera to charge directly my Kobo Glo. I may be wrong, but I am not sure I can do this with Koreader. This would be the last item missing to be totaly independent from Nickel (since we already can start usb and wifi using KSM).

[NiLuJe]

AFAIK, whether you're running nickel or not shouldn't have any impact whatsoever on how the system behaves on such a low-level. (Unless nickel does some weird magic).

[Ken Maltby]

The charging of the battery takes place if a charging cable is plugged in, while Koreader is running as well, but it doesn't look like the charge % indicators get updated while charging (just while discharging, I guess).

Personally, I think the KSM battery monitor scripts are the way to go, if you want to watch it charge. I sometimes check with them to get the charging started then start Koreader, to read while it is charging.

Luck;
Ken

[tshering]

Originally Posted by roger64

Charging.

With Nickel, I can use the charger of my camera to charge directly my Kobo Glo. I may be wrong, but I am not sure I can do this with Koreader. This would be the last item missing to be totaly independent from Nickel (since we already can start usb and wifi using KSM).

I guess you can charge your Kobo Glo without nickel. The only difference is that the device is not informing you about it. Try to select (KSM home) tools > checkbatteryautorefresh.sh, and see whether your device is charging.

[roger64]

@tshering

Thanks or the tip. I'll try this next day, for the time being the capacity of my battery is 100, so charging would not be really relevant.

What means "current now 50000 / charge now 500000"?

[NiLuJe]

@Ken Maltby: I can't remember how KOReader behaves now, so, stupid question: I imagine instead of showing something percentage-based, you just get a specific 'charging' icon/text with no %? If that's it, that should be trivial to change.

[roger64]

Originally Posted by NiLuJe

AFAIK, whether you're running nickel or not shouldn't have any impact whatsoever on how the system behaves on such a low-level. (Unless nickel does some weird magic).

Nickel shows a percentage written in small characters when you are on the home screen. If not on this screen, at least you get a charging icon on the top right. You know something happens.

[Ken Maltby]

Koreader's Reader Menu top dropdown has the time @ nn% in the bottom right corner.
The "Mini" progress bar can also provide a battery charge percentage display (B:nn%).

The top menu display updates when you bring it up, I think. The mini-progress bar updates after a certain number of page turns, I think. (Going by how it appears, not looking at the code.)

Adding a lightning bolt when charging would be a nice touch, though.

Luck;
Ken

[NiLuJe]

@Ken Maltby: that's how I vaguely remembered it, too, thanks. [And how I remember the refresh behavior being implemented].

@roger64: So, basically, you were expecting an always-on battery status *somewhere*, is that right? Or at the very least *something* always visible when the battery is charging? Because as Ken just confirmed, KOReader handles battery status refreshes the exact same way whether it's charging or not, so I'm a tiny bit confused, and not quite 'getting' what behavior you were expecting .

[roger64]

Hi

I use a Kobo Glo. (Nickel 2.8.1. and latest Koreader).

mini-bar battery test

This morning I had a little test:
on Koreader my mini-bar battery reported a 97% level.
I put it to charge (wall charger) during over one hour: the battery report stayed stuck to 97%.
I unplugged, used a little Koreader. Still 97%.
(From there a casual user may think the battery has not been charged and may start Nickel).

Only when I rebooted Koreader did I get a fresh battery report: 100%.

What I take from this:
- one can charge directly its battery with Koreader
- he will get information on the real (I mean new and updated) battery status after rebooting Koreader.
During a Koreader session, the mini-bar seems to notice and report instantly only battery decreases but not increases (at least when they come from a wall charger).

This behaviour could be improved.

Note: I will also test KSM refresh a.s.a.p.

[tshering]

Originally Posted by roger64

Note: I will also test KSM refresh a.s.a.p.

If your battery is charged around 97% you will not notice much change. In order to get convinced that the device is actually charging. Call checkbattery.sh or checkbatteryautrorefresh, before you plug the device in. You will see "status Discharging". Then plug the device in and press "refresh". Now you should see "status Charging." (Note:autorefresh updates the information only once a minute or so.)
As I understand it, none of nickel, Koreader, KSM contribute actively to charging the device. (This is done at a lower level. Otherwise you could not charge the battery once the charge level is so low that you cannot start nickel.) Nickel and so on only forward the charging information to the user..