01-30-2013, 04:21 PM | #1171 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
So I used my Touch, downgraded it to (stock) 5.1.2, and removed the production keys. BTW, the Touch is really a bliss in that regard, because with USB downloader mode available now, it's almost impossible to permanently brick the device, or to lock yourself out... While I'm still treating my Paperwhite much like a raw egg. Anyway, here are the results, trying to install the official 5.3.2 update on a stock 5.1.2 firmware with only the pubprodkey*.pem files removed:
The conclusion is... well, it's that there is no conclusion. Removing those keys might work for preventing updates (at least for the update that I tested, it seemed to work), or it might not (because there are other update types which might still be installed because the kernel can verify them). I'm not adventurous enough to risk bricking my Paperwhite. So... use eureka's method to disable OTA updates, or use iptables, or simply keep your device in airplane mode and/or unregistered. We didn't find the "golden" solution to unwanted updates yet. |
|
01-30-2013, 04:47 PM | #1172 | |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
Quote:
On PW without Amazon's keys update will fail when "Update your Kindle" will be selected, but it should work on reboot, because PW update bundles are recovery updates recognized by in-kernel-image-updater. kindletool convert -i helps to distinct recovery updates. BTW, I guess, in-kernel-image-updater also have a strict filename pattern, so, I think, that's why updates with PW_ prefix didn't work. |
|
Advert | |
|
01-31-2013, 08:47 AM | #1173 |
Junior Member
Posts: 4
Karma: 10
Join Date: Jan 2013
Device: Kindle PW
|
At first, thank you all and especially ixtab for his troublesome work!
I already had the current jailbreak and previous JBPatch version on my Kindle PW with firmware 5.3.1 and because new JBPatch was released I updated to firmware 5.3.3 and JBPatch 3.2. After 'refreshing' kindlet-jailbreak and localization files, all was well and functional again, even all my font, margin, etc. settings were restored. Now trying the new justification setting in hyphenation patch. Changing to 'ragged justification' in my mobi-files (floating text) does not make a difference, the text stays 'fully-justified'. After changing the option I did a 'System/Restart Framework' in JBPatch, also a 'Menu/System/Restart' effects nothing. Any ideas? |
01-31-2013, 09:06 AM | #1174 | |
Wizard
Posts: 4,744
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Quote:
|
|
01-31-2013, 09:07 AM | #1175 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
If you carefully read the description, it's about *occasionally* allowing left-aligned lines, not about having all lines left-aligned.
The text still is fully justified, except for lines where full justification would lead to huge gaps. This is actually the same as the Kindle does without the hyphenation patch - except that in that case, it's much more pronounced (i.e., happens more often, and more "visibly" - exactly *because* there is no hyphenation). Anyway, quickly go forward through the pages, and you *will* find that some lines are ragged. It is most likely to affect the last line on a page. Last edited by ixtab; 01-31-2013 at 09:40 AM. Reason: typos |
Advert | |
|
01-31-2013, 09:12 AM | #1176 |
Wizard
Posts: 4,744
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
^ Hehe echo someone?
MARCO ... |
01-31-2013, 09:27 AM | #1177 |
Junior Member
Posts: 4
Karma: 10
Join Date: Jan 2013
Device: Kindle PW
|
Thanks for the quick reply, question answered at best ... twice.
I see. I have to read this forum not only occasionally careful ;-) |
01-31-2013, 11:30 AM | #1178 |
Wizard
Posts: 4,744
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
@qrti: No, you don't have to read it very careful. Just subscribe to this thread, read the last page, and then check every now and then what is new. This way you never miss if anything changes. Sometimes you will see the same question asked almost back to back.
@ixtab: maybe you should put that in the instructions as part of installation - to subscribe here so you know when a new feature is introduced. |
01-31-2013, 03:59 PM | #1179 |
SQUIRREL!!
Posts: 1,636
Karma: 8400000
Join Date: Nov 2010
Location: California
Device: K-Fire, PW2, PW3
|
|
02-01-2013, 09:18 AM | #1180 |
Enthusiast
Posts: 38
Karma: 1000
Join Date: Jul 2012
Device: Kindle Touch
|
|
02-01-2013, 12:40 PM | #1181 |
Enthusiast
Posts: 26
Karma: 26512
Join Date: Apr 2009
Device: Kindle PaperWhite
|
Right & Left Margins for PDF files are not working
@ixtab
The Top and Footer margins work perfect on ebooks and PDF whenever I modify them. Left & Right Margins didn't work with any PDF file. I set the value 0 and sometimes 5 for them but still the same result with some margins on the sides. As you can see in the attached PDF, I trimmed the sides so I get no margin. Kindle Paperwhite 5.3.3 Last edited by alfarhan; 02-01-2013 at 12:42 PM. |
02-01-2013, 12:53 PM | #1182 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
|
02-01-2013, 12:57 PM | #1183 |
Enthusiast
Posts: 26
Karma: 26512
Join Date: Apr 2009
Device: Kindle PaperWhite
|
Yes, most of Arabic books available online are scanned images combined in a PDF. Is there a way to force the PDF to take 0 margin on both sides and I control the margin by trimming the PDF pages?
|
02-01-2013, 01:38 PM | #1184 |
BLAM!
Posts: 13,478
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@DuckieTigger: You probably were on IRC the last time it wa smentionned .
@ixtab/eureka: I'm with eureka on that one, the updater run at boot, from the recovery shell in the initramfs, has stricter pattern-matching checks ('^update*.bin$', lowercase), and embeds its own set of keys, so we'd need a patched Kernel to run custom updates, as Yifan did for the whole "3.x-on-DX" thingy, and documented on his blog. It deletes anything that it doesn't like (wrong device code, wrong key, etc). Can't remember if the status of the auto-pilot updater is logged somewhere, but at the very least there's some stuff shown over a serial console . Last edited by NiLuJe; 02-01-2013 at 01:40 PM. |
02-01-2013, 01:42 PM | #1185 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
|
|