Koreader running on Kobos (all of them, hopefully!)

[ywq111]

Thank you very much.

Originally Posted by chrox

This fallback is for the UI only, if there is no Tibeten translation of Koreader it will be of no use. EPUB document has a fallback font of "Droid Sans Fallback" which can display Chinese chars you only need to select "Tibetfont" on the "Choose font" menu entry. If it does not help, you may need to disable embedded style of your EPUB document.

[pazos]

Originally Posted by embryo

With versions 630 - 634 I get a message saying that after a restart Koreader will be updated, and I also get an extra koreader.updated.tar file inside the OTA folder, with the same size as the other two.
After the restart I have the original (not updated) version.
I change the servers but I got identical results.

You need to update KSM, look in tshering thread

[embryo]

Originally Posted by pazos

You need to update KSM, look in tshering thread

I can't find anything newer than the compination of:
KBStartMenu_04.zip
KBStartMenu_04_update01a.zip
KBStartMenu_04_update01a_preventfreeze.zip

Do I miss something obvious?

[embryo]

Using version 634, I can't make Koreader start (with or without defaults.persistent.lua)
I get this crash.log:

./luajit: frontend/ui/device.lua:79: bad argument #1 to 'sub' (string expected, got nil)
stack traceback:
	[C]: in function 'sub'
	frontend/ui/device.lua:79: in function 'getModel'
	frontend/ui/device/screen.lua:145: in function 'getDPI'
	frontend/ui/gesturedetector.lua:53: in main chunk
	[C]: in function 'require'
	frontend/ui/input.lua:2: in main chunk
	[C]: in function 'require'
	frontend/ui/uimanager.lua:3: in main chunk
	[C]: in function 'require'
	frontend/ui/widget/button.lua:9: in main chunk
	[C]: in function 'require'
	...
	frontend/ui/widget/buttondialog.lua:1: in main chunk
	[C]: in function 'require'
	frontend/apps/filemanager/filemanagerhistory.lua:3: in main chunk
	[C]: in function 'require'
	frontend/apps/filemanager/filemanager.lua:1: in main chunk
	[C]: in function 'require'
	./reader.lua:22: in main chunk
	[C]: in function 'dofile'
	./koreader-base:22: in main chunk
	[C]: at 0x0000bd85

Any hint?

Update: The problem was crated because I had copied an extra Koreader Folder to the root.
After deleting this folder all versions (including 634) are working OK.

Sorry for the false alarm...

[pazos]

Originally Posted by embryo

I can't find anything newer than the compination of:
KBStartMenu_04.zip
KBStartMenu_04_update01a.zip
KBStartMenu_04_update01a_preventfreeze.zip

Do I miss something obvious?

Not really obvious but here is it

https://www.mobileread.com/forums/sho....php?p=2900766

[embryo]

Originally Posted by pazos

Not really obvious but here is it

https://www.mobileread.com/forums/sho....php?p=2900766

Thank you.
.. and at last!
the first OTA update is version 636!

[Ken Maltby]

Version 665 is really lagging on my AuraHD.
Will try 661. It seems much more normal.

Version 665 working normally again, but that first suspend to book cover, is really slow (after being used to its normal quick response). See WS64's post below.

Luck;
Ken

[WS64]

What exactly is lagging?
For sure slower are the screen covers (both screen saver and in the search window, and i guess it will stay like this), and the first search will also be slower since I changed the format of the database so this has to be rebuilt once, but for the rest there should not be any difference.

[Ken Maltby]

Originally Posted by WS64

What exactly is lagging?
For sure slower are the screen covers (both screen saver and in the search window, and i guess it will stay like this), and the first search will also be slower since I changed the format of the database so this has to be rebuilt once, but for the rest there should not be any difference.

It was going to suspend in a book, with bookcover, that I first noticed it. Right after that there was a very slow response to a number of selections. I'll try it again, keeping what you said in mind.

It is working, for the most part, but still getting some slow responses and even had it crash out to the Start Menu once when I just did a normal page turn. It seems normal most of the time but a random problem seems to popup out of the blue. I know this is no help, but I still am thinking this 665 build is not as stable as previous builds.

Luck;
Ken


Luck;
Ken

[embryo]

Originally Posted by WS64

What exactly is lagging?

Its not just the lagging.

With 663, 665 I had some crashes back to KSM when trying to browse Tags or Series and once getting out of suspend.
With 665 it had also changed the Margin values of the book I was reading although the button was at the right setting (small).

Version 661 works OK

[Ken Maltby]

Originally Posted by embryo

Its not just the lagging.

With 663, 665 I had some crashes back to KSM when trying to browse Tags or Series and once getting out of suspend.
With 665 it had also changed the Margin values of the book I was reading although the button was at the right setting (small).

Version 661 works OK

I guess I will go back to 661. While we don't have the greatest diagnostic data, The postings should narrow down what changes might have caused these issues.

Luck;
Ken

[WS64]

if you go back AND use the search please delete the temp folder within Koreader. At one point I changed the format of the cache metadata file, and the older version will not like it. From now on this is safe against new versions, just this one time it is not.

[embryo]

Originally Posted by WS64

if you go back AND use the search please delete the temp folder within Koreader. At one point I changed the format of the cache metadata file, and the older version will not like it. From now on this is safe against new versions, just this one time it is not.

I had the temp folder cleared for the 663 and 665 tests, but did not help.
661 didn't have any problems with that.

[Ken Maltby]

Originally Posted by embryo

I had the temp folder cleared for the 663 and 665 tests, but did not help.
661 didn't have any problems with that.

673 is out and, from the comments it looks like the issues are being addressed.
It seems to function better, the screensave to cover looks normal.

Luck;
Ken

[WS64]

Originally Posted by embryo

I had the temp folder cleared for the 663 and 665 tests, but did not help.
661 didn't have any problems with that.

No, I meant you need to clear it if you want to go back to an older version.
The newer versions take care of that by themselves.