JBPatch

[knc1]

Originally Posted by geekmaster

Which reminds me, we need some way to identify the different 5.1.0 firmware versions -- any ideas?

If they change the kernel also, then uname might give something useful;
try: uname -a
to get the entire set of strings on one line.

Do they change the firmware version build number?
Should be in:
cat /etc/issue
or
cat /etc/issue.net
or
some such similar place.

(I still do not have my K3 re-assembled and working, so I can't try myself.)

Edit:
@GM - why not start a new thread on the firmware ID subject and ask a mod to move this stuff that is dirting up Ixtab's thread?

[ixtab]

Originally Posted by geekmaster

Could the noads hack somehow prevent screensaver powerdown mode from operating in certain conditions? The last thing I had run was the demo in the tcc package, and it pauses and resumes the framework. I tend to suspect the firmware, but it is worth considering other possible causes in any case.

Nope, definitely not the fault of any of the patches. They generally only minimally change the behavior here and there, by returning an unconditional "true" or "false" instead of performing some calculations, etc.

BTW, I fixed the noads patch. I gave up trying to be smart by intercepting screensaver module settings (which is horribly unstable... not because of my code, but the underlying native executable just seems to crash at times, for no particular reason), and went for the simple solution instead: just remove /var/local/adunits

[ixtab]

Here's another patch, inspired by popular demand.

This patch allows to change the margins around the book content. For the simplest use case, you can now influence what the Kindle understands as "fewest/fewer/default" words per line. You can also hide the progress bar, if you are so inclined. Finally, this patch also affects the PDF display, so in principle, PDFs can be made to display on the full screen.

I attached a few "before/after" screenshots (see below). The result is largely depending on your individual settings, though.

INSTALLATION: copy the attached file "ixtab_margins-5.1.0.zip" directly to your Kindle's opt/jbpatch folder (do NOT unzip the file!), and add the corresponding entry to CONFIG.TXT.

CONFIGURATION:
With the default configuration, this patch does not change anything at all. To change the behavior, you have to modify the file "ixtab-patch-margins.txt" inside the zipped file. After editing, make sure that you re-zip the patch correctly, then restart your Kindle.

SCREENSHOTS

Before:


After:


The PDF files are mostly for verification: The central box should always be square, and the borders are a visual indicator of the actual document dimensions.


Update: I attached the actual pdfs, and the code to produce them - maybe they are useful.

[diba]

Hey, you keep me busy with testing ;-)

THX for another patch !

[alaiksander]

I tried the margin hack. But dont quite understand this line

font.wordsperline.margin.list=120 80 40

Plus I still have the right&left margin default on azw/mobi files. The pdf(s) are good with the hack.

PS: In the future, would you update the first thread with every hack available in this thread? thus will be easier for many to try the hacks.

Thx

[ixtab]

Originally Posted by alaiksander

I tried the margin hack. But dont quite understand this line

font.wordsperline.margin.list=120 80 40

Plus I still have the right&left margin default on azw/mobi files. The pdf(s) are good with the hack.

"fewest" words per line=120px margins
"fewer"=80, "default"=40. These are the default settings, adjust them whichever way you want.

And read the comment in the file again. The margins are cached by the Kindle, so if you change the setting, you will not see the effect until you switch to another "mode", then back to the one you want.

Originally Posted by alaiksander

PS: In the future, would you update the first thread with every hack available in this thread? thus will be easier for many to try the hacks.

Thx

I'm already doing this, and yes, I will keep doing so.

[eureka]

I'm not asking for it personally, but displaying directories in /mnt/us/documents on Home screen as distinct items and showing directory content on tap (i.e. filtering items by locating in selected subdirectory of /mnt/us/documents) and so on recursively will certainly bring satisfaction to some part of KT users which prefer hierarchical structuring to "tagging" by using native collections.

Sorry for bothering anyway.

[ivar]

Originally Posted by ixtab

Here comes the revamped no-ads patch... essentially an overhauled version of this one.

This new version also removes the screen saver ads without requiring user intervention.

INSTALLATION: Unzip the attached file, copy ixtab_ksonoads-5.1.0.jbpatch to opt/jbpatch on the Kindle. Make sure that opt/jbpatch/CONFIG.TXT contains a line to activate "ixtab_ksonoads-5.1.0.jbpatch". Finally, restart the Kindle.

Upgrading: If you are already using the old version, just overwrite the jbpatch file, and restart.

Is this new ixtab_ksonoads-5.1.0 patch work with jbpatch_1.2.0 or needs it latest jbpatch_1.3.1?


Thanks for your (and others) work

[diba]

Updating these patches is always recommended. ixtab is doing things "under the hood" which always have been improvements!

[diba]

Maybee a dumb question, but what are these sample-pdf good for ??

[ixtab]

Originally Posted by ivar

Is this new ixtab_ksonoads-5.1.0 patch work with jbpatch_1.2.0 or needs it latest jbpatch_1.3.1?


Thanks for your (and others) work

It needs 1.3.1 because it now requires additional permissions (deleting files), which have been introduced in v1.3.0.

[ixtab]

Originally Posted by diba

Maybee a dumb question, but what are these sample-pdf good for ??

Quoting myself: "The PDF files are mostly for verification: The central box should always be square, and the borders are a visual indicator of the actual document dimensions."

[ixtab]

Originally Posted by eureka

I'm not asking for it personally, but displaying directories in /mnt/us/documents on Home screen as distinct items and showing directory content on tap (i.e. filtering items by locating in selected subdirectory of /mnt/us/documents) and so on recursively will certainly bring satisfaction to some part of KT users which prefer hierarchical structuring to "tagging" by using native collections.

Sorry for bothering anyway.

Now that is one SERIOUS request

It would certainly be possible "somehow" (tm), but actually it would require to rip out the home screen logic, and completely replace it. That's WAY over my head, sorry.

[diba]

Originally Posted by ixtab

Quoting myself: "The PDF files are mostly for verification: The central box should always be square, and the borders are a visual indicator of the actual document dimensions."

Even if I out myself as the most stupid guy in this forum, but I still do not understand.
I HAVE READ you txt file and the postings, but still. no clue. Are they something like an overlay?
Pls help me out of my misery.

[ixtab]

They are simply examples which I used for testing. For instance, when setting all margins to 0, with a "real" PDF, it is hard to determine whether the display is really "full screen", because you don't know how much white margin is INSIDE the document. This is why the samples have a black border: you can immediately check if the black border really reaches the left/right edges of the device. Finally, I produced multiple versions (A4 and letter), to see how it behaves with different page formats. And even more finally, the square in the center was used to verify that the aspect ratio is correctly kept.

In other words: they are not needed, and they are not magic in any way. They simply allow to visually verify the actual margins that are applied AROUND the document.