KPV: a PDF reader for Kindle, based on muPDF, GPLv3

[reprep]

Bug report:

If you start kindle pdf viewer with shift p k (kill framework) after a stand-by period "going into screensaver" message pops and it never goes away. I mean the screen saver is never displayed. Though the kindle goes to sleep and you have to wake it to continue reading by slider.

If you start kindle pdf viewer without killing framework, the screen saver is displayed fine.

[dracodoc]

Anybody noticed battery issue?
If I let the kindle dx go to screensaver in file browser mode, the battery level didn't change overnight.
However, if it go to screensaver in reading mode, the battery level dropped from 49% to 39% in 8 hours. This is definitely not right.

Update: it dropped to 7% after 5 mins. I have to recharge it immediately.
It seemed that I have to restore to previous version.

[hawhill]

Would you mind trying the same version again, after a full device reboot? Just to make sure it's not another process running havoc.

@reprep: Yep, the screensaver is a function of the Java framework. When you say the message ain't going away, does that mean that even after triggering the power switch again it won't go away?

[knc1]

Originally Posted by hawhill

Would you mind trying the same version again, after a full device reboot? Just to make sure it's not another process running havoc.

@reprep: Yep, the screensaver is a function of the Java framework. When you say the message ain't going away, does that mean that even after triggering the power switch again it won't go away?

Is "top" installed on these machines?
Is there an easy way that a user could view it?

Or would this require one of the terminal emulators to be installed?

Hmm... "ps aux" would give more information, but would probably require the posting of a screen capture so we could translate for the end user.

Edit:
If available -
ps aux >/mnt/us/ps.txt
or
top -bn1 >/mnt/us/top.txt
would generate a text file the end user could post for us to read.

[dracodoc]

OK, I'll install new version again. See what will happens with full reboot.

Another question, it seemed that the last reading position is not kept after update. I thought the last reading position is saved in the book.lua file, which should be recognized by newer version.

I checked the book.lua file, it said "last page"=125, which is correct, but the newer version opened the book at page 101.

[dracodoc]

The recent 1 hour seemed OK. My last installation didn't use the shift shift space to reload launchpad, will that cause problem I met?

Update: after 2 hours, I woke up the kindle, it stopped at the kindle home screen with a circle at top. I pushed the slider, there was some messed up display, then it lost response.

I read for 15 mins, put it into screen saver. Then I woke it up, it displayed some messed up screen again. After several moves of the slider, I guess it is in kindle home screen actually but with messed up display. I used shift P R to restart amazon framework, it did restart and back to normal.

I'm using rcount=0 to force global refresh, and some customized pic for screen saver (but in kindle resolution). I guess it's a bug related to memory usage, maybe there is not enough memory.

Actually the new features in file processing is of little use to me, I decided to turn back to older version. But I'm afraid I'll have to upgrade when there are more new features available...

[reprep]

@hawhill:

nope, after triggering the switch, it goes away. Just the screensaver is not shown. Not a big deal though.

[NuPogodi]

Originally Posted by dracodoc

Another question, it seemed that the last reading position is not kept after update. I thought the last reading position is saved in the book.lua file, which should be recognized by newer version.

I checked the book.lua file, it said "last page"=125, which is correct, but the newer version opened the book at page 101.

Well, in contrast to older versions, the new kpdf no longer saves the history files (like book.lua) in the folder with the book, but in the fixed folder mnt/us/kindlepdfviewer/history/ Thus, to some extent it is incompatible with older kpdf-versions (unless you manually move & rename book.lua following the pattern '[#path] filename.lua'). It might be a reason of what you have reported. If you kept in mind something else, please, be more specific - what is the filetype? if the file is opened by crereader (epub, mobi, etc), did you change the fontface, fontsize?

[EDIT] Mea culpa... cre-documents are usually saved with 'last_percent', rather than 'page'. So, your book is definitely not cre-document.

[xueyou2]

Great work. I just install it and it runs smoothly.
Well this is a big problem maybe you do not care : it can not show chinese word.
I try to replace the font in \kindlepdfviewer\fonts\droid and it still does not work.
Just show 口口 instead of chinese words or other asia words.
I think it is a small case for you expert.
Thank you very much.

[NuPogodi]

Originally Posted by xueyou2

Well this is a big problem maybe you do not care : it can not show chinese word.
I try to replace the font in \kindlepdfviewer\fonts\droid and it still does not work.
Just show 口口 instead of chinese words or other asia words.

@xueyou2: it was a problem for me to test whether chinese glyphs are present in the default font or not. I guess that dave2008 may help you with a competent advice what should be changed to solve this problem.

@devs: I've just obtained some feedback from a lucky owner of K2. kpdf runs smoothly also in his device. The only problem was that the left_page_forward button was not activated. So i've sent him a bit modified version to define the keycode of this button. He has done it, then added the line KEY_LPGFWD = 104 (i.e. the same keycode as in K3) to default keys in keys.lua and wrote me that now it works properly.

[Tanga]

Wow dude - I just got my Kindle back (long story) and so had my first attempt using this software. It sure is gorgeous! I really love the shortcut help being accessible in the software. I actually have tried reading other books using this software too, and it worked beautifully. I must now get around to doing a right up for it - in a fortnight I'll have some spare time.

Thanks so much. I love it!

[dave2008]

Originally Posted by xueyou2

Great work. I just install it and it runs smoothly.
Well this is a big problem maybe you do not care : it can not show chinese word.
I try to replace the font in \kindlepdfviewer\fonts\droid and it still does not work.
Just show 口口 instead of chinese words or other asia words.
I think it is a small case for you expert.
Thank you very much.

hi xueyou2,

Chinese words are rendered properly here in my K3. You can try with the DroidSansFallback or AR PL Sungtil GB font. Both of them supports Chinese Characters.

[Tanga]

I've just updated the Introduction section of the wiki and added an Installation Guide. Is that all that needs to be done? Have I got it right?

Cheers!

[xueyou2]

Originally Posted by dave2008

hi xueyou2,

Chinese words are rendered properly here in my K3. You can try with the DroidSansFallback or AR PL Sungtil GB font. Both of them supports Chinese Characters.

Good news.
well i do not know how to do this.
Can you give me detai steps?I just repalce \kindlepdfviewer\fonts\droid\DroidSans.ttf with the DroidSansFallback.ttf and other chinese font like 方正宋体，it does not work.

[dracodoc]

That explains the problem I had. The file I read is a pdf (thus have page number).

Originally Posted by NuPogodi

Well, in contrast to older versions, the new kpdf no longer saves the history files (like book.lua) in the folder with the book, but in the fixed folder mnt/us/kindlepdfviewer/history/ Thus, to some extent it is incompatible with older kpdf-versions (unless you manually move & rename book.lua following the pattern '[#path] filename.lua'). It might be a reason of what you have reported. If you kept in mind something else, please, be more specific - what is the filetype? if the file is opened by crereader (epub, mobi, etc), did you change the fontface, fontsize?

[EDIT] Mea culpa... cre-documents are usually saved with 'last_percent', rather than 'page'. So, your book is definitely not cre-document.