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

[jlynton]

Is it possible, using koreader on the H2O, to set up an area to tap (ideally long press) to toggle the frontlight, then control the intensity with swipes?

I have trawled through this thread but not found the answer.

[Murky]

Originally Posted by tshering

I installed the latest koreader today and I really like it. I would even more like it, if one could exit it without rebouting. One problem is, that after koreader the screen is turned by 270 degree. Therefore, I thought a first step to a solution might be restoring the original frame buffer settings after running koreader.

Before running koreader, fbset -s gives

mode "800x600-0"
	# D: 0.033 MHz, H: 0.034 kHz, V: 0.055 Hz
	geometry 800 600 800 1280 16
	timings 30000000 8 164 4 18 4 1
	accel false
	rgba 5/11,6/5,5/0,0/0
endmode

After running koreader, fbset -s givers

mode "600x800-0"
	# D: 0.033 MHz, H: 0.043 kHz, V: 0.052 Hz
	geometry 600 800 608 1792 8
	timings 30000000 8 164 4 18 4 1
	accel false
	rgba 8/0,8/0,8/0,0/0
endmode

I try to set

fbset -g 800 600 800 1280 16 -rgba 5/11,6/5,5/0,0/0 -t 30000000 8 164 4 18 4 1

and fbset -s shows

mode "600x800-0"
	# D: 0.033 MHz, H: 0.043 kHz, V: 0.052 Hz
	geometry 600 800 608 1792 16
	timings 30000000 8 164 4 18 4 1
	accel false
	rgba 5/11,6/5,5/0,0/0
endmode

As you see, of the geometry set only the -depth value (8 to 16 bits per pixel) has changed, the resolution is unchanged. Was this to be expected? I also tried setting each of the 5 geometry values individually, but with the same result. Is it an error in busybox? Is my approach totaly hopeless? Any ideas?

Excuse me I have a simillar problem. Koreader's display looks fine but touch turned by 270 degree. I read your post but I didn't understand which file needs change?

Fix problem in accordance with:

Originally Posted by tshering

In the file E:\.kobo\koreader\frontend\ui\input.lua, you find

-- For single-touch events (ABS.code).
local ABS_X = 01
local ABS_Y = 00

change it to

-- For single-touch events (ABS.code).
local ABS_X = 00
local ABS_Y = 01

You will probably need an editor that writes only line feed at the end of lines, rather than carriage return and line feed; cf. this.

But the way to input.lua was: i:\.adds\koreader\frontend\device\input.lua

[tshering]

Originally Posted by Murky

Excuse me I have a simillar problem. Koreader's display looks fine but touch turned by 270 degree. I read your post but I didn't understand which file needs change?

Fix problem in accordance with:

But the way to input.lua was: i:\.adds\koreader\frontend\device\input.lua

Good that you found the solution. I was just going to post it here. And yes, the location of the file has changed since then. At least in some versions it was possible to make this a permanent setting (so that it survives updates). I think this is not longer the case, but I am not sure.

[hawhill]

put "KOBO_TOUCH_MIRRORED=true" into a file "defaults.persistent.lua".

[tshering]

Originally Posted by hawhill

put "KOBO_TOUCH_MIRRORED=true" into a file "defaults.persistent.lua".

Thank you! I thought I read that this option has been removed at some point.

[kwokhin]

Why does my Kobo Glo HD drain battery so quickly during standby?
This morning I remember the battery was well over 90%. Then after standing by for about 10 hours it went to 67%. I wonder why. I am using koreader-nightly-20150517. I pressed the button at the top to put it into sleep mode.

[Ken Maltby]

Originally Posted by kwokhin

Why does my Kobo Glo HD drain battery so quickly during standby?
This morning I remember the battery was well over 90%. Then after standing by for about 10 hours it went to 67%. I wonder why. I am using koreader-nightly-20150517. I pressed the button at the top to put it into sleep mode.

Power usage as an issue seems to come and go, with it seldom getting nailed down to a single correctable factor. Going by the built in percentage monitoring routines has not been too reliable. Also, it takes a number of recharge cycles for a new device to become consistent with its power management.

That said; for some people with some devices, replacing the "suspend.sh" in /.adds/koreader/ with the "suspend.sh" from /.adds/valasovsoft/, has improved their power consumption issues. This may be an example of where Sergey got one better, than the Koreader team.

Luck;
Ken

(The same answer to the same question, in the other thread.)

[church mouse]

Originally Posted by kwokhin

Why does my Kobo Glo HD drain battery so quickly during standby?
This morning I remember the battery was well over 90%. Then after standing by for about 10 hours it went to 67%. I wonder why. I am using koreader-nightly-20150517. I pressed the button at the top to put it into sleep mode.

I experienced inexplicable power drains on both my Glo and H20 using Koreader. Initially I thought it was solely linked to my sleepcover on my Glo (that was certainly a factor), but I was never able to prevent sudden large 20-30% drain issues, perhaps once every 2-3 days, when sleeping overnight.

I tried all the changes Ken, Ebri and tshering helpfully suggested but sudden inexplicable large drops still occurred. (See post 2143 and earlier)

Eventually, I switched to Coolreader entirely about three weeks ago and I have had no more excessive battery drain. I prefer Koreader, but Coolreader is not a bad second so I am sticking with it.

I realise that this answer may not be too helpful, but if you cannot resolve the issue, Coolreader may be an alternative for you.

[kwokhin]

Originally Posted by Ken Maltby

Power usage as an issue seems to come and go, with it seldom getting nailed down to a single correctable factor. Going by the built in percentage monitoring routines has not been too reliable. Also, it takes a number of recharge cycles for a new device to become consistent with its power management.

That said; for some people with some devices, replacing the "suspend.sh" in /.adds/koreader/ with the "suspend.sh" from /.adds/valasovsoft/, has improved their power consumption issues. This may be an example of where Sergey got one better, than the Koreader team.

Luck;
Ken

(The same answer to the same question, in the other thread.)

Thank you Ken for such a detailed and helpful reply!
I will wait and observe for a few more days to see how the bettery does with more recharge cycles.

May I ask what Sergey is?

I can't believe with such an awesome and powerful comes with a fatal flaw... I wonder why they never fixed it. It is a huge issue. I really need the PDF reading experience in Koreader

[kwokhin]

Originally Posted by church mouse

I experienced inexplicable power drains on both my Glo and H20 using Koreader. Initially I thought it was solely linked to my sleepcover on my Glo (that was certainly a factor), but I was never able to prevent sudden large 20-30% drain issues, perhaps once every 2-3 days, when sleeping overnight.

I tried all the changes Ken, Ebri and tshering helpfully suggested but sudden inexplicable large drops still occurred. (See post 2143 and earlier)

Eventually, I switched to Coolreader entirely about three weeks ago and I have had no more excessive battery drain. I prefer Koreader, but Coolreader is not a bad second so I am sticking with it.

I realise that this answer may not be too helpful, but if you cannot resolve the issue, Coolreader may be an alternative for you.

This is a very good suggestion already! Thanks for taking the time to share your experience

Does Coolreader come with the same PDF reading experience as Koreader offers? Like zoom to fit content width? This is of paramount importance to me

[Ken Maltby]

Originally Posted by kwokhin

Thank you Ken for such a detailed and helpful reply!
I will wait and observe for a few more days to see how the bettery does with more recharge cycles.

May I ask what Sergey is?

I can't believe with such an awesome and powerful comes with a fatal flaw... I wonder why they never fixed it. It is a huge issue. I really need the PDF reading experience in Koreader

Sergey Valasov is the one who ported Coolreader to the Kobo (and other) devices. His pbchess and launcher utilities are examples of how his efforts have benefited the ereader community. But Coolreader is not a PDF reading program.

There is no reason you can't have and use both on your Kobo device.

Have you tried using the "Poweroff" function of KSM7, when shutting down for the night?

Luck;
Ken

[kwokhin]

Originally Posted by Ken Maltby

Sergey Valasov is the one who ported Coolreader to the Kobo (and other) devices. His pbchess and launcher utilities are examples of how his efforts have benefited the ereader community. But Coolreader is not a PDF reading program.

There is no reason you can't have and use both on your Kobo device.

Have you tried using the "Poweroff" function of KSM7, when shutting down for the night?

Luck;
Ken

Thank you Ken I don't normally power off and on the device every day. I'm thinking of trying to exit Koreader and enter Nickel and then into sleep mode before I sleep. I hope it solve the problem

Thanks anyway and I will keep you guys updated

I really really love my new Kobo Glo HD. It's my first ereader and the screen is fantastic!

[hawhill]

I think we would very much like to fix the power problem - though it had proven to be not easily reproducable, thus quite difficult to debug - and then developers lack access to most of the devices the software actually runs on :-)

[Ken Maltby]

The power issue is a real knotted mess of subjective variables. Kobo says that you should get up to 2 months, with "average" reading. Somehow I doubt that there are any "average" readers here. A battery's performance changes over time and with changing conditions. The monitoring circuit and charge management appears to need a calibration process before it provides consistent results. Use of the device during that period can effect the outcome.

A user's perception of their use of the device and the length of time that has elapsed since the last charging can vary greatly, few of us keep a calendar of both and can correlate that data. The cases where the monitoring display shows a larger than should be expected drop in capacity overnight, seem to show a real problem. But I am not sure, how or if, that effects the battery's performance over a longer period. It may be more alarming to the user, but not something that has a lasting effect on how much reading you can do between charges.

For Koreader there are additional concerns, how was it launched? KSM? or some other method? Has Nickel been started before Koreader was? Maybe there is some unplanned interaction with Kobo's firmware? Which FW? Which device? Which Koreader version? Which KSM version? Power Management is a very low level function, closer to the hardware level, almost anything could be effected by it, or effect it.

Personally, I would be amazed if the team can even track this down to a correctable issue.

For me, I just charge my AuraHD whenever I think of it, or it reads a little lower than I would like (I try to have ~60%, at least). Of course I use mine all the time. I know for sure it lasts a lot longer than my tablet. A number of days, as opposed to a number of hours. If I am charging it up averaging every 3 or 4 days, instead of every two months, I don't feel cheated or that there is a problem with my device, or Koreader.

Luck;
Ken

[Ebri]

Actually in my Kobo I am disappointed with battery usage, the longest time was two weeks, and most of the drain happened during sleep. My PW2 and Sony T2 lasted much longer. But I am still happy with other features, and it is OK for me if I have to charge it weekly.