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

[Frenzie]

Originally Posted by NiLuJe

I am also eagerly awaiting a kernel that doesn't implement eink processing as two kernel threads busy-looping (!!).

You mean busy looping while in "idle"? >_>

[frailtyy]

This isn’t specific to Kobo but is Zsync no longer a feature? I keep seeing references to it in the docs but nothing on device.

[Frenzie]

Oh, indeed. It's been deprecated for at least a few months now.

[Name28]

Hi! Thanks a lot for Koreader. I have been using it for a long time on Kobo Glo and Glo HD. It is not very convenient to connect e-reader to PC every time I want to copy new fb2, so I tried to set my Dropbox account on Koreader. I did as it is explained here, it works but not for a long time. For example, yesterday I generated token and pasted it to the correspondent field in the "cloudstorage.lua". It worked and I successfully downloaded books to my Kobo glo. However, when I tried to open my dropbox folder from Koreader today, it returns: "Cannot fetch list of folder contents. Please check your configuration or network connection". From the beginning I made changes as suggested in the thread i mentioned above, i.e. removed slash: ["url"] = "" and made permission changes before generating token.
I am pretty sure, It would work again If I generate new token and paste it to Koreader, but it does not make sense to change and connect Koreader to PC every time...
Could you please advise any solution on that?

Thank you.

[Frenzie]

If anybody should come across the above by search, it was resolved in https://github.com/koreader/koreader...ent-1072974014

Indeed! I hope it does not break tomorrow https://www.dropboxforum.com/t5/Drop...le/td-p/425269

[Name28]

Originally Posted by Frenzie

If anybody should come across the above by search, it was resolved in https://github.com/koreader/koreader...ent-1072974014

So, no it is not working either. I tried that permanent token method yesterday, and when checked today had the same issue.
Looks like Dropbox depreciated long time tokens at all.
As far as I understood, it does not make sense to set Dropbox account on Koreader anymore. As access works only for 4hrs. What a pity! Have to find another way to wirelessly send my books to Koreader...

For reference, while the creation of new long-lived access tokens is now deprecated, we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s) without interruption, if you have any. Also, note though that after the change you won't be able to create new long-lived access tokens.

[CyberPaul]

Hi,
I found the on GitHub:
https://github.com/koreader/koreader/pull/8815
I have latest stable release (2002.03.01) and I can't find the Autostandby timeout parameter. I see Autosuspend timeout (in minutes) and Autoshutdown (hours).
Should I install a nightly build to have that Autostandby option?

[pazos]

Originally Posted by CyberPaul

Hi,
I found the on GitHub:
https://github.com/koreader/koreader/pull/8815

[...]

Should I install a nightly build to have that Autostandby option?

Yes. In the same link you posted you'll see the milestone 2022.04. That's the first release that will have this feature. In the mean time nightlies are an option to test the feature before it gets released.

[jasius]

The latest nightly xxxxxxx38 really caused a ton of issues for me, I had to revert to STABLE, when I tried to use dictionary it crashed the ereader, some UI elements were replaced with a ! with a triangle around it. The first one I really ever had issues with, so odd.

I'm on a Kobo Libra 2 newest firmware.

[NiLuJe]

(Those were caused by file transfer issues).

[jasius]

Originally Posted by NiLuJe

(Those were caused by file transfer issues).

Is it fixed in the newest nightly? Or are you saying it's in the way I installed KOReader?

[NiLuJe]

Wasn't clear, sorry. I meant to say that the Libra 2-induced hangs probably screwed something up, the nightly version doesn't really have anything to do with it, what "fixed" it was simply reinstalling *something* without the device crapping out on you .

[pickyaxe]

Since upgrading my Kobo Elipsa to 4.32.19501, I keep having issues connecting to WiFi on KOReader. For example, highlighting a word and choosing "Wikipedia" sometimes fails to turn on WiFi. Even if it does work, trying to save the Wikipedia article as ePub always fails due to connection issues. I'm on the most recent nightlies.

Any idea what could be wrong?

[NiLuJe]

Actual spotty network issues? ;o).

Haven't noticed anything over here, but I did recently reinstall my Wi-Fi AP with openwrt, so it's been working much better than before (i.e., I'm not a good example for cross-testing) .

[jasius]

Since updating to firmware 4.32 when I use the nightly build the dictionary searches lock up my Libra 2 but going back to stable channel and downgrading makes it work again. Sometimes the dictionary portion of the screen goes all black, sometimes the Libra 2 just fully locks up.

I too was having issues with the Wifi not working when in the nightly build, I had to repeatedly reenable wifi to downgrade and it was a struggle to do so, it kept turning itself off, again in Stable channel the wifi is solid.

I’ve never had this issue with any development nightlies before.

I’ve had the issue on the xxx38 nightly and also xxxx40 nightly.

The fact that the stable build runs great, suggests to me that there’s something in the nightly causing these issues.

Could you look into this?