View Single Post
Old 03-19-2026, 06:48 PM   #25
MrSilverstrike
Member
MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.MrSilverstrike is as sexy as a twisted cruller doughtnut.
 
Posts: 10
Karma: 15376
Join Date: Apr 2024
Location: Belgium
Device: Kobo Libra Color, Kobo Clara Color
@bluepeter: Thanks! I will definitely look into a configurator for NickelMenu at some point.

@JSWolf: I last updated the patches in the repo on the 15th, so I think I'm up-to-date? I see the "## Does not work" comments, I should indeed be able to use those.

Alternatively, I could also just try to apply each individual patch programmatically, and see if the patch succeeds. That would also give us a list of broken patches -- but that does not account for patches that may apply but don't actually work as intended on-device.

I tried to generate a quick script that does this and here's the results: https://gist.github.com/nicoverbrugg...c104768c1febe3

Anyway, great idea. I'll put it on the list -- the patch selection screen needs to be updated anyway for patches that are intended to be user configurable.

(Ah, I missed the post from geek1011, oops. That's even better. If that's all automated I could just source the patches in the Web UI from there.)

Last edited by MrSilverstrike; 03-19-2026 at 06:50 PM. Reason: addendum about other technical approach
MrSilverstrike is offline   Reply With Quote