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

[tshering]

Originally Posted by Markismus

Could any of you Touch owners enable debugging with the "-d" flag after reader.lua in koreader_kobo.sh, start koreader and press the home button a number of times and post the resulting ev.log file?

Here you go!

[Markismus]

Originally Posted by tshering

Here you go!

Great! Exactly what we need. EV_KEY, code 102 has a value 1 when pressed and 0 when released. Wonder if we can shoot this into straight into /dev/input/event0 in lua or whether we have to use a shell script.

[tshering]

Originally Posted by Markismus

Rather nice would also be a binary file for the home button as generated by pacos' method.

At the Touch the home "button" is a key, therefore

cat KT_homebutton.bin > /dev/input/event0

I know that you know this, I mention it nevertheless.

[Markismus]

Originally Posted by tshering

At the Touch the home "button" is a key, therefore

cat KT_homebutton.bin > /dev/input/event0

I know that you know this, I mention it nevertheless.

Thanks for mentioning nonetheless.

[Markismus]

Originally Posted by tshering

At the Touch the home "button" is a key, therefore

cat KT_homebutton.bin > /dev/input/event0

KT_homebutton.bin doesn't do anything on an Kobo Aura for any /dev/input/eventx. So either (1) the file got corrupted, e.g. it has not come through the forum as a binary, but as a textfile. Or (2) the hack will have to check what kind of firmware and device is running and select the appropriate binary to send to /dev/input/eventx.

@tshering Does the _uploaded_ binary still work for you? Could you send the binary file in a compressed format such as a rar- or zip-file?

@paola or @pazos Could you check whether either of the binary files work on your mini?

@pazos Would upload your binary file for the mini? For route (2) that info would be needed

Would anyone be willing to generate the binary for the Kobo Glo and for the Kobo Aura HD by going through these steps?

[tshering]

Originally Posted by Markismus

KT_homebutton.bin doesn't do anything on an Kobo Aura for any /dev/input/eventx. So either (1) the file got corrupted, e.g. it has not come through the forum as a binary, but as a textfile. Or (2) the hack will have to check what kind of firmware and device is running and select the appropriate binary to send to /dev/input/eventx.

@tshering Does the _uploaded_ binary still work for you? Could you send the binary file in a compressed format such as a rar- or zip-file?

I did not try to download and test the uploaded file again. In any case I upload it now as zip.

Yesterday, I compared your Aura-binary with my Touch-binary, they were of considerable different size.

Edit: I downloaded the uploaded binary. I can confirm that the content is identical with the original binary file.

[paola]

Originally Posted by Markismus

@paola or @pazos Could you check whether either of the binary files work on your mini?

sorry Marksimus, I am travelling without the Mini, but should be able to have a go at this tomorrow night.

[tshering]

I would like to confirm that this script (spoiler) works on my Touch, that means after exiting KOReader, you see the home screen of nickel.

Spoiler:

#!/bin/sh
export LC_ALL="en_US.UTF-8"

# we're always starting from our working directory
cd /mnt/onboard/.kobo/koreader/

# export trained OCR data directory
export TESSDATA_PREFIX="data"

# export dict directory
export STARDICT_DATA_DIR="data/dict"

# stop Nickel
killall -STOP nickel

# store the content of the framebuffer
#dd if=/dev/fb0 of=.last_screen_content

# finally call reader
./reader.lua /mnt/onboard 2> crash.log

# continue with nickel
#cat .last_screen_content | /usr/local/Kobo/pickel showpic
#rm .last_screen_content
killall -CONT nickel
cat /mnt/onboard/KT_homebutton.bin > /dev/input/event0

Note: It is just per chance, that I have KT_homebutton.bin in the root instead of .kobo/koreader.

[pazos]

I can comfirm that writting tshering's binary file to /dev/input/event0 does nothing on mi mini. I attach the bin file for the mini (pixie) in this post. As I said you on github, it is simply a matter of creating a folder (like "kobo") and populate it with bin files (like update-pixie, update-dragon, update-trilogy...) and add those lines to koreader_kobo.sh after "killall -CONT nickel"

Spoiler:

model=`/bin/kobo_config.sh 2>/dev/null`
printf "Refreshing nickel homescreen: "
case $model in
pixie | dragon | kraken )
cat kobo/update-${model} > /dev/input/event1
;;
trilogy )
cat kobo/update-${model} > /dev/input/event0
;;
* )
printf "[Error] model $model not supported\n"
exit 1
;;
esac
if [ $? -eq 0 ]; then
printf "[Done]\n"
fi

[Markismus]

Originally Posted by pazos

.., it is simply a matter of creating a folder.. and add those lines to koreader_kobo.sh ...

Done, see issue #559.

Now let's wait until an owner of Aura HD or Glo gets annoyed enough to generate those device specific binary files.

[serdar0020]

another suggestion: pdf, non-reflowed, landscape mode - I'd like to expand the left and right borders into the grey area outside the frame

screenshot http://www.anonimg.com/img/4af22168b...08749fd93f.jpg

new 6" kobo aura, nightly build 2014-04.14

[Markismus]

Originally Posted by serdar0020

another suggestion: ..I'd like to expand the left and right borders into the grey area outside the frame...

It would be nice to have better contol of the crop margins, I agree. Maybe something with control buttons or size entry.

But is what your looking for not a free zoom level?

Or couldn't you adjust the zoom level to page width and select large margins? In defaults.lua you are able to set those margins to any size you fancy.

[cieljonn]

Originally Posted by Ken Maltby

What works for me is to change the timing settings in uimanager.lua, using Notepad++. The file is located at ./.kobo/koreader/frontend/ui/uimanager.lua.
Around line 300 you should see a "timeout=1" I change it to timeout=0. Then you should find another line like this: self:scheduleIn(0.5, function() Device:Suspend() end) I change it to: self:scheduleIn(2, function() Device:Suspend() end)

This gives me a suspend that is just a frozen screen that makes it so I can clean the screen or put my AuraHD in my pocket. I can check that it is working by poking where I would normally get a menu.

Sometimes, after along period of use I may have to restart Koreader for it to continue to work. Some others have tried this but they reported that it didn't work for them.

Luck;
Ken

Hi, I have the exact same problem on my Glo, but this solution doesn't seem to work for me. Help?

Also, is there any way to prevent the frontlight from automatically turning on whenever I go into Koreader?

Thanks!

[Markismus]

Originally Posted by cieljonn

..
Also, is there any way to prevent the frontlight from automatically turning on whenever I go into Koreader?..

We are looking at that problem here.

[mr_nobody]

Quick question...the initial post in this thread says:

"Use koreader_old.zip for 2.5.x or older firmware (not really supported); for 2.6.1 use the nightly builds."

Do the nightlies work on 2.6.2? Thanks.