kobopatch request thread - Page 58

davidfor · 07-18-2022, 03:43 AM

Quote:

Originally Posted by Deobulakenyo

Are these books from kobo store? I only have sideloaded books and the "Nonfiction | 190k words" are not shown on my kobo.

That line is the subtitle. @allanahk is using the driver to set the subtitle to something they think is useful.

allanahk · 07-18-2022, 04:03 AM

Quote:

Originally Posted by Deobulakenyo

Are these books from kobo store? I only have sideloaded books and the "Nonfiction | 190k words" are not shown on my kobo.

Can i make them appear via calibre?

These are all sideloaded books, and the subtitle info is generated in Calibre. It requires the Kobo Touch Extended driver to put the info of your choice into the subtitle metadata when sending books to your device.

If you want the same setup as I have, you will need the Count Pages plugin which puts the word count into a custom column usually called #words (instructions are in the linked thread). Then in the Kobo touch extended driver configuration, go to "Metadata, on device & advanced", tick "Subtitle", and paste the following into the template editor:

Spoiler:

Note that I have a separate genre column that I use, but you could also use tags - just replace field('#genre') with field('tags') (without the # symbol). You can put any column info that you like! The Calibre template language is quite powerful.

davidfor · 07-18-2022, 04:54 AM

Quote:

Originally Posted by allanahk

These are all sideloaded books, and the subtitle info is generated in Calibre. It requires the Kobo Touch Extended driver to put the info of your choice into the subtitle metadata when sending books to your device.

It does not need the extended driver. The subtitle, and all other metadata updating, is part of the built-in KoboTouch driver. The only functions that the extended driver supplies are those configured on the "Extended" tab of the driver configuration. Anything else is part of the KoboTouch driver, or base calibre function.

jackie_w · 07-18-2022, 04:30 PM

Quote:

Originally Posted by BiliBug

I would love to see this patch for the Sage.

I've updated post #844 to add beta patch which can be used on your Sage
beta Increase width available for book Title in Booklists - Daylight only

@alanahk, @Deobulakenyo & anyone else who already installed the initial Libra beta patch,

I've made the following changes to the original patch in post #844

Added new option (Part 2) to customise font-size of both Author and Subtitle lines in the Booklist. Same font-size is used for both. Cosmetic only, won't affect width available for long book Titles.
Changed Series option (Part 3) so only a single Find/Replace is needed to customise font-sizes for Series and (time remaining, filetype, filesize). These 2 values can be different.

BiliBug · 07-18-2022, 06:55 PM

Quote:

Originally Posted by jackie_w

I've updated post #844 to add beta patch which can be used on your Sage
beta Increase width available for book Title in Booklists - Daylight only...

Fantastic! Thank you so much!

Deobulakenyo · 07-18-2022, 10:21 PM

Quote:

Originally Posted by jackie_w

I've updated post #844 to add beta patch which can be used on your Sage
beta Increase width available for book Title in Booklists - Daylight only

@alanahk, @Deobulakenyo & anyone else who already installed the initial Libra beta patch,

I've made the following changes to the original patch in post #844

Added new option (Part 2) to customise font-size of both Author and Subtitle lines in the Booklist. Same font-size is used for both. Cosmetic only, won't affect width available for long book Titles.
Changed Series option (Part 3) so only a single Find/Replace is needed to customise font-sizes for Series and (time remaining, filetype, filesize). These 2 values can be different.

Thanks.

Just a note to others who may overlook the first time. The patch title changed (At least for the Libra devices) from:

beta Increase width available for book Title in Booklists - Libra only:

to

beta Increase width available for book Title in Booklists - Storm only:

if using overrides in kobopatch.yaml, you need to change it there as well.

Patch working good.

Deobulakenyo · 07-18-2022, 10:32 PM

Quote:

Originally Posted by allanahk

These are all sideloaded books, and the subtitle info is generated in Calibre. It requires the Kobo Touch Extended driver to put the info of your choice into the subtitle metadata when sending books to your device.

If you want the same setup as I have, you will need the Count Pages plugin which puts the word count into a custom column usually called #words (instructions are in the linked thread). Then in the Kobo touch extended driver configuration, go to "Metadata, on device & advanced", tick "Subtitle", and paste the following into the template editor:

Spoiler:

Note that I have a separate genre column that I use, but you could also use tags - just replace field('#genre') with field('tags') (without the # symbol). You can put any column info that you like! The Calibre template language is quite powerful.

I tried using your settings and this is what i got:

Plugboard Template error

Now I can't remove the error displaying

Edit: Got it working now.

Raemchoi · 07-25-2022, 10:23 AM

Hey there!

Lately I've lost all my reading stats and I'm trying to get them up where they were (manually). I've found a patch from geek1011 which could help out:

Code:

Manipulate reading stats:
  - Enabled: yes
  - Description: Always add 10 hours to the reading time every time you close a book.
  # in EventEngine::endReadingSession(*Volume) when recording end of reading session stats, change QDateTime::secsTo calls to a fixed value
  - ReplaceBytes: {Offset: 0x4D53A0, FindBLX: 0x425270, ReplaceH: 4F F6 FF 70} # MOV  r0, #65535
  - ReplaceBytes: {Offset: 0x4D53C0, FindBLX: 0x425270, ReplaceH: 4F F6 FF 70} # MOV  r0, #65535

If I had this patch in a 1h and 0.1h version as well, it would be possible to get the values up to where they were exactly (I'd written down the total reading times per book somewhere else before the reset and Geek kindly explained me how to get the right HEX code for these other variants) but when I try to enable this (original) patch, I get the following error:

Code:

          |   Patch("Manipulate reading stats") enabled=true
          |     ResetBaseAddress()
          |     applying
          |     looping over instructions
          |       kobopatch.ReplaceBytes index=3 line=14
          |         ReplaceBytes(kobopatch.ReplaceBytes{Base:(*kobopatch.FlexAbsOffset)(nil), Offset:5067680, Find:[]uint8(nil), Replace:[]uint8(nil), FindH:(*string)(nil), ReplaceH:(*string)(0x126df260), FindInstBLX:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstBLX:(*kobopatch.FlexAbsOffset)(nil), FindInstBW:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstBW:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstNOP:(*bool)(nil), FindBLX:(*uint32)(0x126931f8), CheckOnly:(*bool)(nil)})
          |         ReplaceH.Expand("4F F6 FF 70")
          |           -> Replace = []byte{0x4f, 0xf6, 0xff, 0x70}
          |         FindBLX(0x425270)
          |           -> FindInstBLX = FindBLX = 0x425270
          |         FindInstBLX.Expand(kobopatch.FlexAbsOffset{Offset:(*int32)(0x131942d4), Sym:(*string)(nil), SymPLT:(*string)(nil), SymPLTTail:(*string)(nil), Inline:false, Rel:(*int32)(nil)})
          |           FindInstBLX.Resolve(kobopatch.FlexAbsOffset{Offset:(*int32)(0x131942d4), Sym:(*string)(nil), SymPLT:(*string)(nil), SymPLTTail:(*string)(nil), Inline:false, Rel:(*int32)(nil)})
          |             -> Target: 0x425270
          |           AsmBLX(0x4D53A0, 0x425270)
          |             -> Find = []byte{0x4f, 0xf7, 0x66, 0xef}
          |         ReplaceBytes(5067680, []byte{0x4f, 0xf7, 0x66, 0xef}, []byte{0x4f, 0xf6, 0xff, 0x70}) [cur:0x0 + off:5067680 -> abs:0x4D53A0]
          |         could not apply patch "Manipulate reading stats": line 14: inst 3: ReplaceBytes: could not find specified bytes
        --> could not apply patch "Manipulate reading stats": line 14: inst 3: ReplaceBytes: could not find specified bytes

Probably 'cause newer firmware in which the offset bytes has changed? I'm on 4.33.19759. Is there someone willing to update this patch for me? Or help me out if it isn't due firmware version...

(a lot!)

JSWolf · 07-25-2022, 12:45 PM

Quote:

Originally Posted by Raemchoi

Hey there!

Lately I've lost all my reading stats and I'm trying to get them up where they were (manually). I've found a patch from geek1011 which could help out:

Code:

Manipulate reading stats:
  - Enabled: yes
  - Description: Always add 10 hours to the reading time every time you close a book.
  # in EventEngine::endReadingSession(*Volume) when recording end of reading session stats, change QDateTime::secsTo calls to a fixed value
  - ReplaceBytes: {Offset: 0x4D53A0, FindBLX: 0x425270, ReplaceH: 4F F6 FF 70} # MOV  r0, #65535
  - ReplaceBytes: {Offset: 0x4D53C0, FindBLX: 0x425270, ReplaceH: 4F F6 FF 70} # MOV  r0, #65535

If I had this patch in a 1h and 0.1h version as well, it would be possible to get the values up to where they were exactly (I'd written down the total reading times per book somewhere else before the reset and Geek kindly explained me how to get the right HEX code for these other variants) but when I try to enable this (original) patch, I get the following error:

Code:

          |   Patch("Manipulate reading stats") enabled=true
          |     ResetBaseAddress()
          |     applying
          |     looping over instructions
          |       kobopatch.ReplaceBytes index=3 line=14
          |         ReplaceBytes(kobopatch.ReplaceBytes{Base:(*kobopatch.FlexAbsOffset)(nil), Offset:5067680, Find:[]uint8(nil), Replace:[]uint8(nil), FindH:(*string)(nil), ReplaceH:(*string)(0x126df260), FindInstBLX:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstBLX:(*kobopatch.FlexAbsOffset)(nil), FindInstBW:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstBW:(*kobopatch.FlexAbsOffset)(nil), ReplaceInstNOP:(*bool)(nil), FindBLX:(*uint32)(0x126931f8), CheckOnly:(*bool)(nil)})
          |         ReplaceH.Expand("4F F6 FF 70")
          |           -> Replace = []byte{0x4f, 0xf6, 0xff, 0x70}
          |         FindBLX(0x425270)
          |           -> FindInstBLX = FindBLX = 0x425270
          |         FindInstBLX.Expand(kobopatch.FlexAbsOffset{Offset:(*int32)(0x131942d4), Sym:(*string)(nil), SymPLT:(*string)(nil), SymPLTTail:(*string)(nil), Inline:false, Rel:(*int32)(nil)})
          |           FindInstBLX.Resolve(kobopatch.FlexAbsOffset{Offset:(*int32)(0x131942d4), Sym:(*string)(nil), SymPLT:(*string)(nil), SymPLTTail:(*string)(nil), Inline:false, Rel:(*int32)(nil)})
          |             -> Target: 0x425270
          |           AsmBLX(0x4D53A0, 0x425270)
          |             -> Find = []byte{0x4f, 0xf7, 0x66, 0xef}
          |         ReplaceBytes(5067680, []byte{0x4f, 0xf7, 0x66, 0xef}, []byte{0x4f, 0xf6, 0xff, 0x70}) [cur:0x0 + off:5067680 -> abs:0x4D53A0]
          |         could not apply patch "Manipulate reading stats": line 14: inst 3: ReplaceBytes: could not find specified bytes
        --> could not apply patch "Manipulate reading stats": line 14: inst 3: ReplaceBytes: could not find specified bytes

Probably 'cause newer firmware in which the offset bytes has changed? I'm on 4.33.19759. Is there someone willing to update this patch for me? Or help me out if it isn't due firmware version...

(a lot!)

If you use Calibre, what you can do is keep track of where you are on the books you are reading and you can also backup the database for cases like this where you need to reset it. This is done with Calibre and the Kobo Utilities plugin.

Raemchoi · 07-25-2022, 01:28 PM

Quote:

Originally Posted by JSWolf

If you use Calibre, what you can do is keep track of where you are on the books you are reading and you can also backup the database for cases like this where you need to reset it. This is done with Calibre and the Kobo Utilities plugin.

Thanks for the info, I'll look into that (I should've make a back-up before updating anyway but well...)! Calibre won't be able to help restore the values at the moment, right?

JSWolf · 07-25-2022, 01:35 PM

Quote:

Originally Posted by Raemchoi

Thanks for the info, I'll look into that (I should've make a back-up before updating anyway but well...)! Calibre won't be able to help restore the values at the moment, right?

Right. You'll have to start over. But you can keep backups from then on.

JSWolf · 08-12-2022, 02:24 PM

I have a request for a KePub specific patch.

When doing a strikeout using <del>text to be struck</del>, the line is a singe pixel wide. It's barely noticeable. Also, underlines are also not thick enough. Can a patch be made to fix these lines? Thank you.

ownedbycats · 08-13-2022, 02:54 AM

Patch request: An option to disable the 'mark as finished?' prompt that comes up if a book is over 95% finished and has a last-read date of over a month ago. It sometimes comes up for recently-updated fanfics.

davidfor · 08-13-2022, 09:41 AM

Quote:

Originally Posted by ownedbycats

Patch request: An option to disable the 'mark as finished?' prompt that comes up if a book is over 95% finished and has a last-read date of over a month ago. It sometimes comes up for recently-updated fanfics.

This controlled by an entry in the config file. The last time it was checked is stored. You can set it to a date in the future, as has been suggested for "LastAffiliateSyncTime". The two lines, with a date that is now about eight years in the future, are:

Quote:

MarkAsFinishedLastShown=@Variant(\0\0\0\x10\0%\x94 h\x3!>i\x2)
MarkAsUnreadLastShown=@Variant(\0\0\0\x10\0%\x94h\ x3!>i\x2)

SusanReads · 08-17-2022, 05:12 AM

Quote:

Originally Posted by codychan

Hi there, as we know, there are three types of info about the reading progress can be displayed in the header/footer:
1. Pages left in chapter/book
2. Percent of chapter/book read
3. Time remaining in chapter/book

I'm wondering is it possible to show more than one type in the header/footer such as:
ChapterName 10 mins to go, 10 / 100 or ChapterName 10 % read, 10 / 100
or even three types in it at the same time?

This is the patch I would be most happy with. I would LOVE to have time remaining in book and percentage displayed at the same time.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

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

08-12-2022, 02:24 PM	#867
JSWolf Resident Curmudgeon Posts: 73,841 Karma: 128597114 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	I have a request for a KePub specific patch. When doing a strikeout using <del>text to be struck</del>, the line is a singe pixel wide. It's barely noticeable. Also, underlines are also not thick enough. Can a patch be made to fix these lines? Thank you.

08-13-2022, 02:54 AM	#868
ownedbycats Custom User Title Posts: 8,534 Karma: 61120499 Join Date: Oct 2018 Location: Canada Device: Kobo Libra H2O, formerly Aura HD	Patch request: An option to disable the 'mark as finished?' prompt that comes up if a book is over 95% finished and has a last-read date of over a month ago. It sometimes comes up for recently-updated fanfics.