05-13-2016, 02:04 PM | #31 | |
Fanatic
Posts: 511
Karma: 64554
Join Date: Aug 2013
Device: Kobo Glo, GloHD
|
Quote:
The version of Koreader I use works very well and there is not a "real" reason to update it, but then again ... who needs a "real"reason ) |
|
05-13-2016, 03:22 PM | #32 | |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
Quote:
Luck; Ken |
|
Advert | |
|
05-13-2016, 05:13 PM | #33 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@Ken Maltby: Yup, really new .
|
05-13-2016, 11:03 PM | #34 |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
Ok, I'm still on 389, I'll give 396 a try. I tried the 389, and it works holding the power slide switch for 3+ seconds. It even gave me my KSM PowerOff page, but slapped an info box with "Powered off." on top of my image. (I'll have to comment out the "show" command.) One thing though, it requires fewer pokes to just use the Home Icon and return directly to KSM then poke the Poweroff selection.
Luck; Ken PS; comment out: frontend/ui/uimanager.lua line 70, to drop the Info box. Last edited by Ken Maltby; 05-13-2016 at 11:25 PM. |
05-30-2016, 07:09 PM | #35 |
Zealot
Posts: 100
Karma: 470830
Join Date: Nov 2012
Location: Berlin
Device: Nook Simple Touch, Kobo Aura H2O, Kobo Libra 2
|
After the recent changes, I get a segfault on my H2O when suspend kicks in (or maybe when waking up?).
This is with build 411. The same with several recent builds. from crash.log: [05/30/16 @ 23:13:36] Kobo Suspend: BEGIN! [05/30/16 @ 23:13:36] Kobo Suspend: Current WakeUp count: 246 [05/30/16 @ 23:13:36] Kobo Suspend: Asked the kernel to put subsystems to sleep [05/30/16 @ 23:13:38] Kobo Suspend: Waited for 2s because of reasons... [05/30/16 @ 23:13:38] Kobo Suspend: Synced FS [05/30/16 @ 23:13:38] Kobo Suspend: Wrote WakeUp count: 246 (0) [05/30/16 @ 23:13:39] Kobo Suspend: Asked to suspend to RAM... ZzZ ZzZ ZzZ? (0) [05/30/16 @ 23:13:40] Kobo Suspend: END! (WakeUp count: 247) Segmentation fault Last edited by xor_; 05-30-2016 at 07:12 PM. |
Advert | |
|
05-30-2016, 08:02 PM | #36 |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
I never understood how the "WakeUp count" idea was supposed to work.
Luck; Ken |
05-30-2016, 08:18 PM | #37 |
Zealot
Posts: 100
Karma: 470830
Join Date: Nov 2012
Location: Berlin
Device: Nook Simple Touch, Kobo Aura H2O, Kobo Libra 2
|
Adding a crash.log with debug enabled. It seems to be time-related?
I close the reader with the magnet mechanism, and let it sit for a while. Then open it. A couple of times it came back (after only waiting for a relatively short time), maybe the time was too short for the suspend to actually come on? The crash only occurs after the last open (when I had let it sit for some longer). Could it be that the new suspend interferes with the magnet cover mechanism? Last edited by xor_; 05-30-2016 at 08:20 PM. |
05-31-2016, 01:22 PM | #38 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
There's a PR open on GH (can't remember the #ID right now) for that one. We probably need a proper stack trace to figure this one out, something which has proven to be a bit tricky to actually get on Kobos...
|
05-31-2016, 05:34 PM | #39 | ||
Zealot
Posts: 100
Karma: 470830
Join Date: Nov 2012
Location: Berlin
Device: Nook Simple Touch, Kobo Aura H2O, Kobo Libra 2
|
Quote:
Quote:
|
||
06-03-2016, 09:19 AM | #40 |
BLAM!
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@xor_: Basically can't for the life of me get the kernel to coredump automatically. Which is rather annoying, since this appears to be a semi-random crash and a PITA to trigger in any case.
And on top of that, coredumps generated by gcore appear to be borked... So my cheap workaround would be attaching gdb to luajit in a tmux session, and making sure you're in a position to re-attach on crash (i.e., usbnet). Binaries for all that are available in there. (Because *that*, at least, works to get useful stacktraces ). EDIT: For ref., this is the GH issue we're talking about. EDIT²: And my comments on stacktraces were in this one. @xor_: Good point on its name, I just fixed that. Last edited by NiLuJe; 06-03-2016 at 09:27 AM. |
06-14-2016, 03:07 PM | #41 |
Member
Posts: 16
Karma: 10
Join Date: Mar 2016
Device: Kobo Aura H2O
|
What's working for me on my Kobo Aura H2O is using the suspend.sh script from pbchess.
Download latest build from here: http://forum.vlasovsoft.net/viewtopic.php?f=8&t=537 Only edit I do is to comment out the wifi line, like this: Code:
#. $ROOT/wifi_off.sh You will have to replace the file again after every update as it will be overwritten with the original file. |
08-26-2016, 04:44 PM | #42 |
Evangelist
Posts: 440
Karma: 1084584
Join Date: Aug 2007
Location: Sisak, Croatia
Device: Kobo Aura H2O, Kobo Aura ONE
|
Interesting thing I just found out on this problem:
Yesterday I had 100% battery, today when I started reading it dropped to 72%. Well, that isn't that interesting. But, interesting is the clock. There was "lost time", i.e. clock was about 3 minutes late(r) than it should. Like something influenced clock also. Like it crashed, or went in some processor intensive loop. On the surface everything looked normal, I started reader just fine, there was no obvious problems with reader except lost battery and clock time. |
09-15-2016, 06:50 PM | #43 | |
Evangelist
Posts: 440
Karma: 1084584
Join Date: Aug 2007
Location: Sisak, Croatia
Device: Kobo Aura H2O, Kobo Aura ONE
|
Quote:
More info you can find here: https://github.com/koreader/koreader...ment-246927411 I just changed setting on my device and will monitor how things go from now on. |
|
09-16-2016, 07:57 AM | #44 |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
"Oldhasbeen" has added a post to that thread, that describes the state of his research and indicates that the change of "koreader\frontend\device\generic\device.lua
UIManager:scheduleIn(10, self.suspend) to UIManager:scheduleIn(15, self.suspend)" allows for "True Sleep", in almost all situations. He has also provided some data that helps understand the final scenario that can cause power drain. So, it looks like the change to 15 may fix the suspend for Kobos issue, and the final problem/scenario is described and can be avoided, until a permanent fix is merged into KOReader. Luck; Ken |
09-16-2016, 10:14 AM | #45 | |
Addict
Posts: 393
Karma: 123456
Join Date: Feb 2009
Location: Central US
Device: k1 - KAO2, ipads, h2o, KA1, inkBOOK, T80s, Mars, Nova Pro
|
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Koreader running on Kobos (all of them, hopefully!) | giorgio130 | KOReader | 3517 | 03-24-2024 05:43 PM |
Aura H2O Problem with KSM and/or Koreader -> Nickel full freeze | johnnyb | Kobo Developer's Corner | 8 | 04-15-2015 02:18 AM |
Mini KOreader--Request to solve CHM parsing the Chinese code problem | sbwtxj | Kobo Developer's Corner | 0 | 11-01-2014 01:06 PM |
[Koreader] Rendering problem on KPW2 | natto | Kindle Developer's Corner | 1 | 04-10-2014 10:42 AM |
iLiad Reason for suspend problem | bitz | iRex Developer's Corner | 0 | 10-01-2007 06:41 PM |