12-13-2019, 11:54 PM | #406 | |
Evangelist
Posts: 496
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
|
Quote:
Last edited by rtiangha; 12-14-2019 at 12:00 AM. |
|
12-24-2019, 05:56 AM | #407 | ||
Connoisseur
Posts: 55
Karma: 8430
Join Date: Mar 2016
Device: PW3, Clara HD, PB740
|
Quote:
Quote:
Is the LD_PRELOAD trick the way you found to achieve that? It has the additional advantage you don't even have to write everything in assembly but also plain C. OTOH, user code is only executed while hooking existing symbols, but there should be a workaround for that. My other question, since we're in developer's corner, what is the usual workflow when you create a new/custom patch? It has the risk of loop-crashing the nickel process, am I correct? Are there provisions to put back the device in workable state in such occurrences? Can you for instance:
Last edited by Marco77; 12-24-2019 at 06:08 AM. Reason: fmt |
||
Advert | |
|
12-24-2019, 09:03 AM | #408 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Once you have shell access (whatever method you're using, f.g., SSH (preferably over USBNet) or serial), you can also simply kill nickel, patch it manually, start it manually, and watch it harmlessly crash and burn since you're already in a shell.
|
12-24-2019, 06:35 PM | #409 | |||
Wizard
Posts: 2,733
Karma: 6987557
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Quote:
Quote:
This isn't what you're asking, but since we're discussing this, I'll also mention the other two things I'm considering. First, I'm considering expanding the assembler built in to kobopatch to more than BLX instructions (currently, I'm not working on this as it isn't worth the time for the current patches). Second, I'm looking (whenever I have the time/interest) into live patching libnickel using strace pokes. I'm also looking into live patching nickel CSS using a LD_PRELOAD hack on the qUncompress function (I'd check the address passed and patch it if necessary) or by directly modifying the GUI (I'd rather not do it this way, though). Quote:
Yes. Although, I've had quite a bit of trouble getting the environment set up right ... nickel is quite finicky to launch. You can also patch the memory directly using GCC. |
|||
12-24-2019, 07:07 PM | #410 | |
Wizard
Posts: 2,733
Karma: 6987557
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Quote:
And, see here: https://temp.s3.geek1011.net/kp-2019-12-24_19.04.23.mp4. |
|
Advert | |
|
12-27-2019, 04:34 AM | #411 | |
Junior Member
Posts: 4
Karma: 10
Join Date: Dec 2019
Location: Medan, Indonesia
Device: Kobo Clara HD, Onyx Boox Max 3
|
Quote:
|
|
01-05-2020, 04:36 PM | #412 |
Zealot
Posts: 120
Karma: 33696
Join Date: Dec 2016
Location: Germany
Device: Kobo: Libra 2, Aura One, Glo HD, Clara 2E
|
Wish: Bring back "advanced font control" for all fonts. In older versions of the firmware I could use this for ALL fonts. Now it appears only for some font-families and that's a pity. It was one of the settings that is unique for Kobo.
|
01-05-2020, 04:41 PM | #413 |
Resident Curmudgeon
Posts: 73,954
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
The patches for Advanced Font Control was for side loaded fonts was always for TTF and not OTF. So if any of your fonts are OTF, you'll have to convert them to TTF.
|
01-05-2020, 04:43 PM | #414 |
Zealot
Posts: 120
Karma: 33696
Join Date: Dec 2016
Location: Germany
Device: Kobo: Libra 2, Aura One, Glo HD, Clara 2E
|
|
01-07-2020, 02:20 PM | #415 |
Banned
Posts: 12
Karma: 10
Join Date: Jan 2020
Location: Westeros
Device: Kobo Clara
|
Who wants me to do a overdrive enablement patch?
|
01-07-2020, 02:46 PM | #416 |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
No-one with any long-term common sense wants you to do that. It would royally p*ss-off Kobo because you'd be depriving them of potential sales of high-end devices. It's a short step from there to them deciding to devote their efforts to locking down the firmware. Everybody would lose.
If you have these technical skills why don't you do something more productive with them than you've managed in the last couple of days? Perhaps geek1011 has some backburner projects he could send your way. |
01-07-2020, 03:22 PM | #417 | |
Resident Curmudgeon
Posts: 73,954
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
01-07-2020, 03:31 PM | #418 | ||
Wizard
Posts: 2,733
Karma: 6987557
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Quote:
Quote:
Although, if skldmf/anyone else knows how to write Go, kobopatch.patchlib does need quite a bit of refactoring, especially the zlib css minification and the unit tests (they're a gigantic mess because they were written as I was learning how the whole patching process works and as I was still working on the design of kobopatch). It's not currently a priority for me, as it works well enough as it is, it won't need much future updates (there's only so many different ways you can modify a binary), and it has enough test coverage. |
||
01-07-2020, 04:05 PM | #419 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
Isn't the main reason we like Kobos that they're so open, can be easily customised and made to work well with things like calibre? Why punish Kobo for allowing us to do this? |
|
01-07-2020, 04:10 PM | #420 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
FWIW, this is why mentions of tethering or Special Offers removal are a hard "no" rule in the Kindle Dev forum (and offenses are dealt with swiftly & harshly).
So, yeah, nope, not happening ;p. (And, on a technical level, this is why, on the K4, where I haven't found a way to detect if the device is SO, KOReader will *NOT* override the system's screensaver. On newer devices, it will on non-SO devices, but will let the Kindle deal with it on its own (i.e., show SO screensavers) on SO devices). TL;DR: Don't Be A Dick (TM), or everybody loses. Last edited by NiLuJe; 01-07-2020 at 04:13 PM. |
Tags |
kobopatch, patches, patching, request, requests |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Request for PW3 kernel [posted in another thread] | mustdie | Kindle Developer's Corner | 5 | 10-21-2015 04:28 PM |
Kobobooks.com future feature request thread | Mrs_Often | Kobo Reader | 47 | 11-08-2012 11:59 AM |
[Old Thread] Calibre 'feature request' thread | Waba | Calibre | 2 | 02-10-2010 07:52 PM |
Feature request thread? | Dahak | Calibre | 1 | 08-02-2009 12:51 AM |
3rd party software request thread | Adam B. | iRex | 23 | 11-28-2008 01:08 PM |