12-31-2012, 01:08 PM | #991 |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Thank you. And the "FIX" could simply be putting in the documentation: Unfortunately on the PW you have to reapply the margins after opening a book. IMO, if that is too much work, then just leave it at the default settings.
|
12-31-2012, 01:17 PM | #992 | |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Quote:
Theoretically you could change the margins to 0, but that does not work for me - that results in the words touching the bezel. Not really good looking. Remember that on the PW you also have to go to the aA menu, and select a different margin setting and back to the one you had for the changes to be active. That has to be done EVERY time you open the book. At least until ixtab can fix it (if it is fixable). |
|
Advert | |
|
12-31-2012, 01:38 PM | #993 |
Evangelist
Posts: 413
Karma: 650430
Join Date: Apr 2010
Device: Kindle paperwhite2, Ipad Air, Kobo Aura H2o
|
Thanks! Ixtab, it works fine...
Happy new year for all ;-D |
12-31-2012, 01:42 PM | #994 |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Sorry to interrupt your scheduled programming again. The Margins DO NOT work on the PW as is. Even a page turn will destroy the margins back to default. Not useable the way it is.
|
12-31-2012, 01:46 PM | #995 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Correct again. And an invaluable hint, because it will hopefully make finding the missing link much easier - thanks! I'll delete the posted file until then.
|
Advert | |
|
12-31-2012, 01:59 PM | #996 | |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Quote:
That might be something to check out. Works flawless for my margins of 100, 150, 250. Remembers from one book to next, on page turns, closing and opening everything. *sigh* |
|
12-31-2012, 02:13 PM | #997 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
PS: No, it's not the "reader.content.[(left)|(right)]Margin" settings which determine the PDF margins, I just tried that. And there doesn't seem to be any other related number with the value of "50" in the settings either. *sigh*. PPS: The only place where the "font.wordsperline.margin.list" setting of the com.amazon.ebook.booklet.reader.resources.ReaderRe sources file is (seemingly) read is inside the com.amazon.ebook.booklet.reader.impl.ui.yd class (the FontDialog class), which is already patched by this patch. So that value of "50" is most probably hardcoded somewhere, but I simply don't know how to find out where. Last edited by ixtab; 12-31-2012 at 03:05 PM. |
|
01-01-2013, 01:03 PM | #998 |
Addict
Posts: 392
Karma: 1008414
Join Date: Jun 2011
Device: Kindle
|
Could JBPatch be used to:
a) totally turn off the PW light and b) remove the "Personal" tag at the bottom of book covers for books you emailed to yourself? |
01-01-2013, 02:33 PM | #999 | |
Connoisseur
Posts: 56
Karma: 5502
Join Date: Oct 2012
Device: none
|
Quote:
Something like: grep -PHn '>=\s*?50|<\s*?50' *.java That searches all Java files and displays filename and line number where "< 50" or ">= 50" is found (whitespace is accounted for). There will probably be some false positive, but it's certainly better than searching with eyeball. |
|
01-01-2013, 03:30 PM | #1000 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Because Amazon did not ship us the source code. All that is there is the *.class files. |
|
01-01-2013, 03:44 PM | #1001 |
Pest
Posts: 204
Karma: 239254
Join Date: Jan 2012
Location: Italy
Device: KT, PW3
|
1000th reply to this post: mine!
|
01-02-2013, 09:28 AM | #1002 | ||
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
Quote:
To get an idea of what the code to be deciphered looks like, here is the method in question. This is already the "easy" part of it, as this method decompiles almost correctly - still, the disassembly has to be looked at to really understand what's going on (but other classes are far, far worse): Spoiler:
So much for now. I now have to get my Paperwhite out of "your Kindle needs repair" mode. |
||
01-02-2013, 09:48 AM | #1003 |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
@ixtab: good job on making headway. 50, 40, 60 - close enough. The reason I initially said 50 (shoot me now) is because to my eyes it looked exactly as the default 50 setting - no visible difference.
As for your repair mode. That can be fixed by several restarts and/or plugging in usb, taking out, plugging in, taking out, push button, wait, plug in, take out. That is how I fixed mine before. The most common culprit is - if you fail to sucessfully reboot so many times it will display the message, even if nothing is wrong with the device itself. That also means, (possibly), that sucessfully booting into the "needs repair" screen might be enough for the PW to get over it. |
01-02-2013, 09:56 AM | #1004 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
@DuckieTigger: I know how to get out of that dreaded repair mode - I was the one who originally released the "rescue pack" for the PW ...
The correct and working way to do it is described near the end of this document. Still, it's a PITA, because the Kindle gives up way too fast, and then one has to go through the entire procedure to get it back to life, which takes about 5 minutes every time... Last edited by ixtab; 01-02-2013 at 10:32 AM. |
01-02-2013, 10:03 AM | #1005 |
Wizard
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
|
Sorry about that. Just saying that you don't always need the rescue procedure. But of course it will be more reliable as it undepends (is that a word? well it is now) on luck.
To prevent getting it stuck in repair mode, maybe you can try to restart it a few times every time it crashed on you. I finally found my logs, or part of them - and it was ALWAYS running out of memory that crashed it. Edit: what readme? your link is broke Last edited by DuckieTigger; 01-02-2013 at 10:06 AM. |