![]() |
#346 | |||
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
Quote:
Quote:
Another observation ... probably not relevant, but just in case ... Your help note about overlay says: Quote:
Code:
fg_color=GRAY4 ![]() Last edited by jackie_w; 12-26-2019 at 11:47 AM. |
|||
![]() |
![]() |
![]() |
#347 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@jackie_w: Huh. That'd be a bug (somewhere
![]() I'll have to double-check, but I think it's because you have both bgless & overlay enabled. Overlay is a superset of the other, so it ought to "win". This is explained in FBInk, but I forgot to mention that here ![]() EDIT: Yeah, overlay wins in the fixed-cell codepath, but bgless wins in the OT one. -_-". EDIT²: Okay, tweaked the comment & fixed the OT codepath in FBInk ![]() I'm in the middle of some FBInk cleanups, but I'll post an updated package later today. Hopefully after I've had a chance to look at your weird cold boot issue ![]() EDIT³: Given your comments, you probably just want backgroundless anyway ![]() Last edited by NiLuJe; 12-26-2019 at 12:39 PM. |
![]() |
![]() |
Advert | |
|
![]() |
#348 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
Quote:
I'll leave it with you. There's no rush on my part if you've got more urgent things on the go. |
|
![]() |
![]() |
![]() |
#349 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@jackie_w: Ah, that's because overlay (in MiniClock) switches to hardware inversion (while, usually, we go with simply inverting the colors ourselves
![]() AFAICT, software inversion *should* do the trick for plain bgless, though. I'll double-check, as it's entirely plausible that this is yet another thing that's subtly broken in the OT codepath ;p. EDIT: Ah, yeah, I see what you mean, bgless definitely ought to switch to true nightmode on its own, too ![]() Last edited by NiLuJe; 12-26-2019 at 03:03 PM. |
![]() |
![]() |
![]() |
#350 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@jackie_w: Okay, package in #311 updated
![]() The bgless/overlay confusion should definitively be fixed, and I updated the comments in the example config to make their behavior slightly less obscure. (To keep your current behavior, you'll have to disable overlay). I couldn't reproduce the weird cold boot thingy (with or without your specific config, FWIW), but I did tweak (very, very slightly) the config timestamp check, which seems to be what goes wrong on your end, for some reason, so, fingers crossed... Thanks for the detailed tests ![]() |
![]() |
![]() |
Advert | |
|
![]() |
#351 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
Quote:
After a reboot there's no clock on the Home screen but if I tap on a book (kepub) to open it, the clock briefly flashes in the bottom right of Home screen but once the book finishes opening it's never seen again. What Kobo device did you do your testing on? If it's the Forma, why don't you post your working config and I'll try that. I deliberately chose my ClaraHD for initial testing to avoid the (potentially) added complications of buttons/auto-rotate of the Forma, but I can try it if you want. |
|
![]() |
![]() |
![]() |
#352 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
@NiLuJe,
I went ahead and tried it on the Forma where everything seems to work OK. So it's the ClaraHD which is the problem. ![]() The Clara and Forma are the only devices Miniclock is installed on. It's too late tonight, but I might try it on my KA1 and H2O tomorrow. |
![]() |
![]() |
![]() |
#353 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
I happened to check on the H2O tonight, but last time I checked was on a Forma
![]() There shouldn't be any complications related to rotation (with relative positioning, that is). (He said, hopeful ^^). I can't think of anything that might be Clara specific off the top of my head, so, err, you could try switching to debug mode and checking the logs until I get a lightbulb moment ;p. The fact that you saw it flash at least once rules out the timestamp checks, so at least there's that ![]() Last edited by NiLuJe; 12-27-2019 at 12:40 AM. |
![]() |
![]() |
![]() |
#354 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
I don't recall if you have shell access on that device, because another interesting tidbit would be the state of the FBInk daemon right after a cold boot vs. when it works...
|
![]() |
![]() |
![]() |
#355 | ||
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
Quote:
Quote:
![]() |
||
![]() |
![]() |
![]() |
#356 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
I may also have a stupid idea to check out. It's not Clara specific, but it is resolution-dependent
![]() If my hunch is correct, the debug logs should make it obvious. Opening a full-screen image might also make it pop up once (maybe. ^^). |
![]() |
![]() |
![]() |
#357 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
I have logs from the Clara test.
This is the debug log: Spoiler:
This is a file containing the .cfg settings I used plus a list of the Kobo actions I took, in case you want to try to synchronise the two. Spoiler:
P.S. I also tested an non-kobopatched H2O on fw 4.19. No obvious problems with miniclock. |
![]() |
![]() |
![]() |
#358 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
|
Quote:
I did double-click a kepub image to open the Image Viewer on the Clara. The miniclock did not make a miraculous reappearance. I've now tested a non-kobopatched KA1 on fw 4.19. It appears to have the same problems as the ClaraHD. Another new piece of info for both Clara and KA1. Immediately after a full reboot the miniclock can be made to appear on the Home screen by tapping the Battery icon. It will remain even after closing the Battery pop-up. However, it disappears forever once a book is opened. I can't then make it reappear on the Home screen by tapping Battery again. As far as I can see, once it's gone, it's gone. |
|
![]() |
![]() |
![]() |
#359 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@jackie_w: Okay, updated the package in #311.
Many thanks for the detailed reports, the debug log *appears* to confirm my hunch (that was basically the subtext in my previous message: "don't try anything too fancy/annoying, I think debug logs will do just fine") ![]() So, hopefully, this *should* fix that issue, as well as a number of related possible issues after an orientation switch on some devices (not a Forma, apparently, but that was basically blind luck, and/or helped my by own setup without the pickel progress bar ^^). I also made a few things (related to FBInk daemon killing/spawning) more defensive, because I tripped something that might have been a race condition during my testing ![]() ---- It might take a couple taps for things to get back into working order. (Then again, there's a lot of things that are wonky on the first event after significant changes ^^). Last edited by NiLuJe; 12-27-2019 at 12:53 PM. |
![]() |
![]() |
![]() |
#360 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Oops, now with one less typo. -_-".
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
I (almost) spend more time reading about e-readers than e-reading | Antoinekamel | General Discussions | 15 | 02-25-2013 10:48 AM |
360 PB360 display gets "stripes" from time to time | klaetsch | PocketBook | 1 | 01-05-2011 04:49 AM |
How to get the time to display | synic | Sony Reader | 9 | 06-10-2009 06:05 PM |
Time Display | Jenny123 | Sony Reader | 2 | 04-23-2009 02:06 PM |
Time Display? | MickeyC | Sony Reader | 3 | 02-10-2008 11:57 PM |