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

[JimMcLaren]

Originally Posted by PeterT

The obvious answer to that question is YES..

lol

Originally Posted by WS64

defaults.lua:
-- default minimum screen height for reading with 2 pages in landscape mode
DCREREADER_TWO_PAGE_THRESHOLD = 7

I've tried values between 1 and 99 with no change. I'm currently on version 734. I've rolled back to 675 and the behavior is consistent. I'm wondering if I have a problem with my FW. I installed 3.8 shortly after it came out and have had a lot of problems since then. Nickel crashes consistently. About the only thing I use it for is the browser and Pocket client. Last night I was trying to read an epub in Nickel and could never open it without a crash. It wouldn't be a problem except a lot of the books I read have diagrams and they are more easily read in landscape than portrait.

I think I'm going to reload my firmware tonight and see if that fixes some of my problems.

[WS64]

Are you sure you don't have it set also in defaults.persistent.lua?

[JimMcLaren]

Originally Posted by WS64

Are you sure you don't have it set also in defaults.persistent.lua?

I'm sure. I opened them both at the same time to be sure. I'm not in a big hurry to reload this. If I can find another reason I will certainly jump at it.

[Vax]

Originally Posted by Vax

Is there a guide somewhere on how to configure the touch area? My problem is that the Aura has a very thin border and its not comfortable for me to hold it with the thumb on that small space. So what I want to do is resize the touch area to turn pages and call home menu overall to 70% less so I get 30% more border on all sides, so that I can actually touch the screen without anything happening. Of course this would disable the long press dictionary lookup but I don't need that functionality anyway.

Here is the solution:

Edit h=1/2 here: https://github.com/koreader/koreader...faults.lua#L69

Edit h=1/2 here: https://github.com/koreader/koreader...faults.lua#L70

Edit w=0 here: https://github.com/koreader/koreader...hlight.lua#L35

Edit h=0 here: https://github.com/koreader/koreader...hlight.lua#L36

Replace both files on your reader, reboot, done!

Bottom half of the screen will now be free to touch with your thumbs. Right in the middle will be the minibar touch area, forward and backward paging will start from half up. Hold is disabled. Everything else should work normally.

Enjoy!

[nglekhoi]

Is is possible for koreader to implement something like "automatically open next chapter/volume (if exists) when finished reading a manga/comic chapter/volume" ?

The old way: when i finished reading a comic chapter, i have to switch back to File Manager, navigate to the comic folder and open the next file.

The new way: when i finished reading a comic chapter, a prompt coming up and ask :

You have finished 'comic name - comic chapter.cbz'. Would you like to open the next 'comic name - comic chapter + 1'.cbz ?

If i touch 'Yes', koreader will open the next file automatically.
If i touch 'No', koreader will switch back to File Manager.

And this behavior affect to cbz format only.

Thanks for your attention

[hombretranquilo]

Hi WS64.

Each time i use Search Books function there is a crash. Device is Aura HD, and koreader version 2014.04-734.

The crash log message says:

error: cannot open
error: cannot load document ''
./luajit: frontend/apps/filemanager/filemanagersearch.lua:329: attempt to concatenate a nil value
stack traceback:
frontend/apps/filemanager/filemanagersearch.lua:329: in function 'find'
frontend/apps/filemanager/filemanagersearch.lua:228: in function 'close'
frontend/apps/filemanager/filemanagersearch.lua:199: in function 'callback'
frontend/ui/widget/button.lua:158: in function 'action'
frontend/ui/uimanager.lua:277: in function 'checkTasks'
frontend/ui/uimanager.lua:303: in function 'run'
./reader.lua:162: in main chunk
[C]: in function 'dofile'
./koreader-base:22: in main chunk
[C]: at 0x0000bd85

[WS64]

@hombretranquilo, sorry, can't help you.
I have heard of that error 3 times now, but never could find out anything. I can't reproduce it at all.
I suggest though that you delete the temp folder under Koreader and sync your Aura new with Calibre and then try a new search.

[JimMcLaren]

Originally Posted by JimMcLaren

I think I'm going to reload my firmware tonight and see if that fixes some of my problems.

I'm not sure what's causing my issue with landscape pages. I did a factory reset last night, loaded Kobo Start Menu and Koreader (version 688) and nothing else. I'm getting quite good at that, I've done it so many times. Anyway, the problem still existed. I'm going to have to poke around some more and see if I can resolve it.

[Ken Maltby]

Originally Posted by hombretranquilo

Hi WS64.

Each time i use Search Books function there is a crash. Device is Aura HD, and koreader version 2014.04-734.

The crash log message says:

error: cannot open
error: cannot load document ''
./luajit: frontend/apps/filemanager/filemanagersearch.lua:329: attempt to concatenate a nil value
stack traceback:
frontend/apps/filemanager/filemanagersearch.lua:329: in function 'find'
frontend/apps/filemanager/filemanagersearch.lua:228: in function 'close'
frontend/apps/filemanager/filemanagersearch.lua:199: in function 'callback'
frontend/ui/widget/button.lua:158: in function 'action'
frontend/ui/uimanager.lua:277: in function 'checkTasks'
frontend/ui/uimanager.lua:303: in function 'run'
./reader.lua:162: in main chunk
[C]: in function 'dofile'
./koreader-base:22: in main chunk
[C]: at 0x0000bd85

The error reported seems to be an attempt to concatenate a nil value, I guess within the query structure. If I were looking at the code I would try to find where a joining of two elements into one occurs, to form the query. Perhaps also if an intermediate result would have tried to write to the external uSD card. (Just guessing here.)

I am assuming that the search location(s) are defined correctly in defaults. (Could result in a variable getting a nil value, if the location can't be accessed/found)

Luck;
Ken

[WS64]

@Ken, my problem is that at this point the string simply can't be nil.
Well, obvious it is, but I still cannot reproduce it. I've got the corresponding metadata.calbre files here from two other users with his problem, and the error simply does not happen here.

[Don_Karnage]

i have a problem on my glo with koreader,its keep freezing after 1 min of inactivity.
i tryed after a factoryreset without any book, without changing any setting...
same result with the last stable version, nightly build, launched by fmon or advboot.
if anyone know whats wrong..... i would be very happy.
same on firmware 3.5 or 3.8.

and i have aalsso the screen remaining black with the aandroid versions, on marek v2 img.... there alsso i would need some help
thank you.

[chrox]

Originally Posted by WS64

@Ken, my problem is that at this point the string simply can't be nil.
Well, obvious it is, but I still cannot reproduce it. I've got the corresponding metadata.calbre files here from two other users with his problem, and the error simply does not happen here.

Add

assert(self.data[i][self.tags], "assert failed: tags data is nil")

before line 329 and found that the tag data could be nil sometimes.

# single tap detected in slot 0
./luajit: frontend/apps/filemanager/filemanagersearch.lua:329: assert failed: tags data is nil
stack traceback:
	[C]: in function 'assert'
	frontend/apps/filemanager/filemanagersearch.lua:329: in function 'find'
	frontend/apps/filemanager/filemanagersearch.lua:228: in function 'close'
	frontend/apps/filemanager/filemanagersearch.lua:199: in function 'callback'
	frontend/ui/widget/button.lua:158: in function 'action'
	frontend/ui/uimanager.lua:277: in function 'checkTasks'
	frontend/ui/uimanager.lua:303: in function 'run'
	./reader.lua:172: in main chunk
	[C]: in function 'dofile'
	./koreader-base:22: in main chunk
	[C]: at 0x004049d0

[WS64]

Originally Posted by chrox

Add

assert(self.data[i][self.tags], "assert failed: tags data is nil")

before line 329 and found that the tag data could be nil sometimes.

@Chrox, if you can reproduce this, please try if
self.data[i][j] = line or ""
in line 317 fixes it.
Like I said, I cannot reproduce it, and not all of my books have tags either, so I should run into this issue also, but I don't.

[chrox]

Originally Posted by WS64

@Chrox, if you can reproduce this, please try if
self.data[i][j] = line or ""
in line 317 fixes it.
Like I said, I cannot reproduce it, and not all of my books have tags either, so I should run into this issue also, but I don't.

Yes, it fixes the nil tags data bug.

[WS64]

@Chrox, thx!

@hombretranquilo, with a little luck this is fixed with the next release