kobopatch request thread

[JSWolf]

Originally Posted by mxbndr

Got it, thanks for saving me the trouble. I wonder, is it instead possible to restore the older screensaver screen? The one with "Sleeping" etc at the top of the screen, and "X% read • Expires in Y days" etc at the bottom.

But if you are going to setup this Kobo to be as easy to use as possible, you'll need a sleep cover and with a sleep cover, you hardly ever see the sleep screen. (it's not a screensaver as there is no screen that needs saving)

[davidfor]

Originally Posted by JSWolf

But if you are going to setup this Kobo to be as easy to use as possible, you'll need a sleep cover and with a sleep cover, you hardly ever see the sleep screen. (it's not a screensaver as there is no screen that needs saving)

It would not be hard to argue that having a cover on a device doesn't make it "as easy to use as possible". The button to wake a Libra H2O when it isn't in a cover is easy to access, so there is no real advantage.

Of course, as your usual argument is that an ereader not in a case is a broken ereader, it's refreshing to see you coming up with different dogmatic advice. Though the "not a screensaver" argument is pretty pointless as it has been a general term for anything shown in this way for a long time.

[JSWolf]

Originally Posted by davidfor

It would not be hard to argue that having a cover on a device doesn't make it "as easy to use as possible". The button to wake a Libra H2O when it isn't in a cover is easy to access, so there is no real advantage.

Of course, as your usual argument is that an ereader not in a case is a broken ereader, it's refreshing to see you coming up with different dogmatic advice. Though the "not a screensaver" argument is pretty pointless as it has been a general term for anything shown in this way for a long time.

The term screensaver for eInk has been wrong since the first use. And yes, a sleep cover is easier to use then the button.

[davidfor]

Originally Posted by JSWolf

The term screensaver for eInk has been wrong since the first use.

It doesn't matter. "screensaver" is now a generic term for this sort function. It hasn't been accurate in any place it is used for a long time, but, people know what it means.

And yes, a sleep cover is easier to use then the button.

Really? You find it harder to use the button on your Libra H2O to wake the device than a cover? I didn't know you had a Libra H2O as you haven't mentioned it. You should probably update your profile to show the purchase.

Of course, if you do not have a cover, it is a significantly easier to use the button than to use a cover. And some people don't use them as they don't like them. And honestly, on my Aura H2O (as that is the only Kobo ereader you list), yes, I think waking it with the button is easier that closing the cover and opening the cover again as I don't always close cover when I put my ereaders down. And I frequently push the button on my ereaders to see the cover and status and then push it again to wake it. I prefer to display the page numbers when reading and that is an easy way to see the percent read and time-to-read for kepubs. It might seem silly, but, it works for me. And I also lift the corner of the cover on the Libra H2O so I can see the info panel.

And even when I use a device cover, I do see the book cover when I open the device cover. I like being able to see the book covers.

Configuring these things might not be useful to you, but it is to other people. And experimenting with different options helps to know what can and can't be done, what is and isn't useful and what is best for an individual.

Jon: The real point here is that @mxbndr wants to know if they can customise a function. Sharing your experience is one thing, but, far to many of your posts are really telling people that as you don't don't do something, no-one else should do it either. Yes, that IS what you far to frequently do. And it is definitely what you did this time.

[mxbndr]

Originally Posted by jackie_w

Do you mean the 'not-fullscreen screensaver'? If so, that's just a standard checkbox in Settings>Energy saving and privacy

Ah, I should have been more specific. I am using custom screensavers, which I think force the UI to have the infopanel (I believe that is what the little "Sleeping" or "Powered off" tab-looking thing is called) instead of the header and footer (at least with the requisite patch enabled, which AFAIK is necessary to show anything at all while using a custom image). I'm looking to have a custom screensaver while retaining the way it typically looks on top and bottom.

Originally Posted by davidfor

Jon: The real point here is that @mxbndr wants to know if they can customise a function. Sharing your experience is one thing, but, far to many of your posts are really telling people that as you don't don't do something, no-one else should do it either. Yes, that IS what you far to frequently do. And it is definitely what you did this time.

Thanks, @davidfor.

[jackie_w]

Originally Posted by mxbndr

Ah, I should have been more specific. I am using custom screensavers, which I think force the UI to have the infopanel (I believe that is what the little "Sleeping" or "Powered off" tab-looking thing is called) instead of the header and footer (at least with the requisite patch enabled, which AFAIK is necessary to show anything at all while using a custom image). I'm looking to have a custom screensaver while retaining the way it typically looks on top and bottom.

If you're talking about using the Kobo feature of storing custom screensavers in a screensavers directory for random display then I'm afraid I can't help. I've never used it so don't know the ins and outs. Maybe someone else will chime in.

ETA: I thought the infopanel didn't appear by default if you're using this option because there's a kobopatch Allow showing info panel on random screensaver in libnickel.so.1.0.0.yaml which will display the infopanel.

[mxbndr]

Originally Posted by jackie_w

If you're talking about using the Kobo feature of storing custom screensavers in a screensavers directory for random display then I'm afraid I can't help. I've never used it so don't know the ins and outs. Maybe someone else will chime in.

ETA: I thought the infopanel didn't appear by default if you're using this option because there's a kobopatch Allow showing info panel on random screensaver in libnickel.so.1.0.0.yaml which will display the infopanel.

AFAICT, this is what it normally looks like, without a custom screensaver, with the information shown as a header and footer:
https://i.imgur.com/7rKFBRg.jpg

and this is how it is shown with a custom screensaver (using the official "screensaver" folder method), and the aforementioned "Allow showing info panel on random screensaver" patch in libnickel.so.1.0.0.yaml:
https://i.imgur.com/PalRVfJ.jpg

What I'm hoping to achieve is a combination: custom screensaver, but information in the header and footer rather than the infopanel.

[jackie_w]

Originally Posted by mxbndr

What I'm hoping to achieve is a combination: custom screensaver, but information in the header and footer rather than the infopanel.

You're confusing me now. All our original conversation (and patch code) was related to the standard Kobo fullscreen screensaver feature. [In technical nickel terms, resource FullScreenDragonPowerView.qss]

Your first image is the standard Kobo non-fullscreen screensaver feature. [In technical nickel terms, resource FramedDragonPowerView.qss]

No discussion you and I have had so far relates to patching the latter CSS. Neither are there any existing kobopatches which do target this CSS.

I can post the CSS from FramedDragonPowerView.qss if you want to do some kobopatch experiments with that, but if custom random screensavers (your 2nd image) is what you really want then, as far as I know, they are always fullscreen, i.e not "framed".

[DNSB]

Originally Posted by jackie_w

I can post the CSS from FramedDragonPowerView.qss if you want to do some kobopatch experiments with that, but if custom random screensavers (your 2nd image) is what you really want then, as far as I know, they are always fullscreen, i.e not "framed".

Currently, to get the custom random screensavers, you need to select "Show book covers full screen" in the Energy saving and privacy settings.

[mxbndr]

Originally Posted by jackie_w

You're confusing me now. All our original conversation (and patch code) was related to the standard Kobo fullscreen screensaver feature. [In technical nickel terms, resource FullScreenDragonPowerView.qss]

Your first image is the standard Kobo non-fullscreen screensaver feature. [In technical nickel terms, resource FramedDragonPowerView.qss]

No discussion you and I have had so far relates to patching the latter CSS. Neither are there any existing kobopatches which do target this CSS.

I can post the CSS from FramedDragonPowerView.qss if you want to do some kobopatch experiments with that, but if custom random screensavers (your 2nd image) is what you really want then, as far as I know, they are always fullscreen, i.e not "framed".

Apologies! I was originally trying to move the infopanel, yes. As that isn't possible, I am now trying to find out if I can use the header/footer setup that appears when not in fullscreen (and when not using a custom image).

Originally Posted by DNSB

Currently, to get the custom random screensavers, you need to select "Show book covers full screen" in the Energy saving and privacy settings.

Yes. So, my understanding is that in order to get custom images to show, it needs to be fullscreen, and if it's fullscreen, it disables the header and footer info on the screensaver. I want to enable a custom image, but still leverage the top and bottom for information.

[mxbndr]

Separate, completely unrelated question:

Is it possible to make a Kobo sleep on a timer, even when in use? I have a friend who asked if this is possible to help them limit their reading sessions. For example, they find themselves reading late into the night and then losing sleep because they lost track of the time. Sure, they could just set a timer, but they often forget, and are hoping that Kobo can automate some of this digital hygiene.

[geek1011]

Originally Posted by mxbndr

Separate, completely unrelated question:

Is it possible to make a Kobo sleep on a timer, even when in use? I have a friend who asked if this is possible to help them limit their reading sessions. For example, they find themselves reading late into the night and then losing sleep because they lost track of the time. Sure, they could just set a timer, but they often forget, and are hoping that Kobo can automate some of this digital hygiene.

NickelMenu + NickelDBus can easily do this.

[mxbndr]

Originally Posted by geek1011

NickelMenu + NickelDBus can easily do this.

Thanks! I have successfully installed both NickelMenu and NickelDBus. However, I'm not sure of the command to run for auto-sleep nor where to run it. With NickelMenu, I can successfully create menu items via the "config" file I created, per the "doc" file that exists already. Is this where NickelDBus items should live, too? Or am I meant to run commands in a terminal window?

I read this, but it's a little sparse for a n00b like me.
https://shermp.github.io/NickelDBus/

[Vorath]

Is it technically possible to add a "transparent screensaver" (as talked about here https://blog.the-ebook-reader.com/20...o-screensaver/) that shows you last read page when you turn off your Kobo?

[geek1011]

Originally Posted by mxbndr

Thanks! I have successfully installed both NickelMenu and NickelDBus. However, I'm not sure of the command to run for auto-sleep nor where to run it. With NickelMenu, I can successfully create menu items via the "config" file I created, per the "doc" file that exists already. Is this where NickelDBus items should live, too? Or am I meant to run commands in a terminal window?

I read this, but it's a little sparse for a n00b like me.
https://shermp.github.io/NickelDBus/

It should be as simple as something like 'menu_item:reader:Power-off in 30m:cmd_spawn:sleep 1800;qndb -m pwrShutdown'.