04-29-2015, 03:37 PM | #46 | |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Quote:
Not sure how else to track the standby state. Nickel does some fancy things when entering standby, such as reading the first sector of /dev/mmc0p3 using dd and removing some modules with rmmod, but I'm loath to hook into those for standby detection. It doesn't seem to trigger any udev events either. Not sure how this standby of the Kobo actually works... |
|
04-29-2015, 04:29 PM | #47 |
Wizard
Posts: 2,839
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
|
Well seems to work just fine on my H2O, though I suppose that's to be expected since you're using an H2O to test it out.
|
Advert | |
|
04-29-2015, 04:34 PM | #48 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Still good to know that it's not just me - since I have other mods on my H2O as well.
Why a particular message would appear on the H2O but not other devices with presumably identical firmware... and why Kobo would feel the need to remove such log messages... is beyond me. |
04-29-2015, 04:41 PM | #49 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
What I meant to say was that on Kobo Touch, I cannot see any (error or other) messages that you could use for your purpose. When entering standby it is just continuing to report the same things as it did before.
Last edited by tshering; 04-29-2015 at 04:45 PM. |
04-29-2015, 04:56 PM | #50 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Could you post or PM me the output of logread -f in the seconds before and after going standby (by pressing power button)? So I could compare to what I'm seeing on the H2O. Thanks.
|
Advert | |
|
04-29-2015, 05:29 PM | #51 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
With Screensaver > Show current read unchecked; I pressed the power button at around 15:42, and again at around 16:27:
Spoiler:
With Screensaver > Show current read checked: Spoiler:
|
04-29-2015, 06:37 PM | #52 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Thanks... that's... completely different. Looks like a dead end, as far as the logread idea is concerned anyway. I'll have to come up with something else, then.
|
04-29-2015, 07:42 PM | #53 |
Enthusiast
Posts: 46
Karma: 303048
Join Date: Feb 2013
Location: Brazil
Device: Kindle Paperwhite 3
|
using old pngcat(3.13.1) with new pack, is working.
tested: kobo Glo 3.15.0 |
04-30-2015, 03:50 AM | #54 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
So the culprit was not the missing message? Maybe I did not wait long enough when I logread?
|
04-30-2015, 06:07 AM | #55 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Hum. Not sure why the pngcat binary changed at all, it was supposed to change screensaver.sh only. Even so, without the log message it would not work.
Although I'll have to update pngcat anyhow for the Glo HD, just not sure which resolution it uses; if someone has telnet on a Glo HD, the output of "fbset" would be interesting. |
04-30-2015, 06:53 AM | #56 |
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
fbset on my Glo HD gives:
Code:
mode "1072x1448-45" # D: 80.000 MHz, H: 65.681 kHz, V: 45.049 Hz geometry 1072 1448 1088 3072 16 timings 12500 16 102 4 4 28 2 accel false rgba 5/11,6/5,5/0,0/0 endmode |
04-30-2015, 11:54 AM | #57 |
Member
Posts: 20
Karma: 10000
Join Date: Sep 2014
Device: Kobo Glo
|
|
04-30-2015, 05:33 PM | #58 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
This might support the Glo HD, I have no way of testing it myself.
@Kobo_Mao, you might try this one as well, the previous package had some errors. Also make sure you've disabled Kobo's screensaver settings (no cover/progress, just a blank sleeping screen). Edit: Maybe I'm drunk, but it appears I've uploaded the wrong files three times in a row now Last edited by frostschutz; 06-28-2015 at 02:43 PM. |
05-01-2015, 06:31 AM | #59 | |
Member
Posts: 20
Karma: 10000
Join Date: Sep 2014
Device: Kobo Glo
|
Quote:
I disabled Kobo's screensaver settings. Do you think to be my fault? Sorry for my english! |
|
05-01-2015, 06:37 AM | #60 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
No, it's due to whatever changes Kobo made to their firmware. Although I'm not sure why it would work for Cecel3000 in that case. Maybe installed Mark 5 firmware on a Mark 4 device or something like that? (not recommended)
I'll just have to find another / more reliable way to detect standby. |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Boox T68 - Screensaver Image | fozzedout | Onyx Boox | 4 | 07-27-2020 07:25 PM |
(PW) Location of waterstones screensaver image | mrspaceman | Kindle Developer's Corner | 19 | 05-09-2013 02:07 AM |
[PB360] Image Viewer with random? | rogue_librarian | PocketBook | 2 | 12-12-2010 05:20 AM |
K2i original screensaver image | Aeroraptor | Kindle Developer's Corner | 1 | 12-12-2009 07:40 PM |
Hacks Angus Young Screensaver Image | Jason Shaffer | Amazon Kindle | 5 | 04-08-2009 01:34 PM |