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

[pickyaxe]

Thank you jasius for the heads up.

After rolling back to the most recent stable, the WiFi connection on my Kobo Elipsa is working again. That said, I only a did a short test.

Seems like something broke it since March 24th.

[NiLuJe]

The only Wi-Fi related commit is https://github.com/koreader/koreader/pull/8942, and that landed *in* 2022.03.1 . (So I'm going to need clarification on what "the latest stable" exactly means for you, and whether your experience differs between 2022.03 and 2022.03.1 ).

The only major change is the autostandby feature, but that is opt-in (and a terrible idea anywhere else than on an Elipsa or a Sage), so did either of you happen to enable it?

There's even *less* changes between -37 and -38 (as the number implies, only one, actually ^^).

As usual, can't tell you much more without verbose debug logs.

[jasius]

Originally Posted by NiLuJe

The only Wi-Fi related commit is https://github.com/koreader/koreader/pull/8942, and that landed *in* 2022.03.1 . (So I'm going to need clarification on what "the latest stable" exactly means for you, and whether your experience differs between 2022.03 and 2022.03.1 ).

The only major change is the autostandby feature, but that is opt-in (and a terrible idea anywhere else than on an Elipsa or a Sage), so did either of you happen to enable it?

There's even *less* changes between -37 and -38 (as the number implies, only one, actually ^^).

As usual, can't tell you much more without verbose debug logs.

The version on the STABLE server that works perfectly is 202203010000

When I tried -38 and -40 I got the hangs on opening dictionary then crashes issue.

With my Libra 2 with the latest firmware of 4.32.19501

With -41 I was able to successfully look up ONE word with no issue, when I tried the 2nd word I got a black dictionary window and the ereader reset itself. After the Libra 2 reboots itself and I launch back into KOReader, I can't even use the dictionary once, after highlighting a word, the dictionary doesn't even pop up anymore, it just crashes back to Nickel. When I go to downgrade by switching back to Stable the screen doesn't render properly but I can still press the Downgrade button.

Again on the 202203010000 build I have ZERO issues with anything. So I'll have to use that for now, hopefully these bugs don't make it into the stable channel build.

[NiLuJe]

That looks more like the usual Libra 2 shenanigans than anything else, unfortunately ;o).

Do you remember using earlier (i.e., between 2022.03.1 and -38) nightlies without issues?

And wouldn't you say that the issues curiously started occurring right after you updated your device to 4.32?

[jasius]

Originally Posted by NiLuJe

That looks more like the usual Libra 2 shenanigans than anything else, unfortunately ;o).

Do you remember using earlier (i.e., between 2022.03.1 and -38) nightlies without issues?

And wouldn't you say that the issues curiously started occurring right after you updated your device to 4.32?

I had stable usage with the nightlies before -38 yes.

This did start with the new 4.32 firmware, but this is feedback, these issues are real.

[NiLuJe]

See https://github.com/koreader/koreader/issues/9038 for an eerily similar report that was pinpointed to the auto standby feature, which I think is what I started asking you about .

(As in, double-check that you really don't have it enabled, please ).

(Incidentally, that report perfectly shot down my 4.32 theory, so, progress!).

[jasius]

Originally Posted by NiLuJe

See https://github.com/koreader/koreader/issues/9038 for an eerily similar report that was pinpointed to the auto standby feature, which I think is what I started asking you about .

(As in, double-check that you really don't have it enabled, please ).

(Incidentally, that report perfectly shot down my 4.32 theory, so, progress!).

Going into Plugins and unchecking Auto Power Save fixed the crashing when using the dictionary.

Strangely either it's this newest -41 build or something the Auto Power Save plugin did, but when I go into Screen>Rotation the options for all the different rotations are no longer there, luckily the rotation options on the bottom bar still work. What a weird quirk.

[pazos]

Originally Posted by jasius

Strangely either it's this newest -41 build or something the Auto Power Save plugin did, but when I go into Screen>Rotation the options for all the different rotations are no longer there, luckily the rotation options on the bottom bar still work. What a weird quirk.

None of them. When you have a document opened you're expected to change the rotation in the bottom menu.

The Settings->Screen->Rotation will only include "keep current rotation across views".

[NiLuJe]

Okay, that's interesting. Disabling the whole plugin is a bit drastic, especially given that autostandby/shutdown shouldn't have changed behavior.

What's a tad strange is that the only addition to this plugin is auto standby, and it should be *disabled* (and completely inert) by default.

So, could you check if things behave with the "Auto power save" *plugin* enabled, but Auto *standby* disabled (it's in [Gear] > Device, IIRC), and Auto *suspend* & *shutdown* enabled at their default values?

[NiLuJe]

(The other good news is that enabling auto standby is mostly an user experience downgrade on your device, unless you have extremely specific needs for power savings (and even then, I'd have to put actual numbers on it, as I've never been convinced it was a good idea on i.MX SoCs)).

It's designed very specifically for the boards using a sunxi SoC (currently, Elipsa & Sage).

[jasius]

Originally Posted by NiLuJe

Okay, that's interesting. Disabling the whole plugin is a bit drastic, especially given that autostandby/shutdown shouldn't have changed behavior.

What's a tad strange is that the only addition to this plugin is auto standby, and it should be *disabled* (and completely inert) by default.

So, could you check if things behave with the "Auto power save" *plugin* enabled, but Auto *standby* disabled (it's in [Gear] > Device, IIRC), and Auto *suspend* & *shutdown* enabled at their default values?

What you're describing I tried first, and it didn't work, I had to disable the plugin.

I use the sleep cover so I don't really care about auto power.

What about the Rotation options missing from the Screen>Rotation menu? Is that intentional? As I stated, I still have access to that from the bottom menu, but I'd still like to know.

[JSWolf]

Originally Posted by jasius

What you're describing I tried first, and it didn't work, I had to disable the plugin.

I use the sleep cover so I don't really care about auto power.

What about the Rotation options missing from the Screen>Rotation menu? Is that intentional? As I stated, I still have access to that from the bottom menu, but I'd still like to know.

Try installing the latest daily update and see if this fixes the problem.

[pickyaxe]

Just wanted to confirm that the WiFi issues I've been having are gone after NiLuJe's enormous pull request.

Thanks as always, the amount of work you have done to improve Kobo device compatibility is amazing. I don't even know what to say at this point.

[niki11784]

I am a complete Koreader newbie and I have a few questions:

I'm trying to organize my books by publishing date- do either of those allow that?

Also, right now Koreader is showing my books as a list of folders with the authors names and the books are inside the folders. I want one list with all my books and cover images like the original kobo list. How do I fix that?

How do I access the Calibre library from Koreader on the device?

[mbrisco]

Got myself identical KOReader installations running on the two current most-recommended e-readers: Kobo Libra 2 and Kindle Paperwhite 5. I'm thinking of doing a full comparison later this week. Trying to decide between them myself to see which one I should keep.

Some initial impressions:

* Instinctively, I like the Libra 2 more because the white color and shape and design are a lot nicer than the Paperwhite's boring black design with the chin.
* The Paperwhite has MUCH better battery life on KOReader than the Libra 2, and also has that cool, special-hardware-integrated page-turn animation, which I ended up liking a lot.
* The Libra 2 has more unstable kernel (apparently a hopeless situation), from what I hear, so the entire device occasionally crashes and reboots, especially when adjusting frontlight settings and sometimes just randomly. The Paperwhite also has some idiosyncratic bugs on KOReader that I noticed, but no crashes yet.
* The Libra 2 screen is a lot nicer than the Paperwhite's. Blacks are more black on the Libra 2 as opposed to more grayish on the Paperwhite. The Libra 2 screen itself is larger than the Paperwhite's (those 0.2" between 6.8" and 7" seem to make a huge difference somehow).
* There is an upgradable (to 256GB) SD card in the Libra 2 but not the Paperwhite.