Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 06-15-2021, 07:05 PM   #1
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Lightbulb NanoClock: Yet another persistent clock

Following a recent unrelated discussion on Discord, I finally bit the bullet and did what I may have vaguely mentioned before, and basically rewrote MiniClock from scratch, this time in Lua, mostly to experiment with a fancy new toy. Oops .

I'm posting this in the Dev forum because it *does* employ a rather low-level trick (as we *are* basically monkey-patching a kernel function), one that has only seen minimal testing on the Kobo side of things, but was originally successfully implemented on the reMarkable to develop an efficient VNC server.

Anyway, I'll leave the floor to myself, further details and documentation available on the GitHub project page.

Make *very* sure to read this to the end, because there are know caveats on the latest Kobo devices, some of which may be fairly severe.
Attached Files
File Type: zip NanoClock-v0.11.4.zip (896.0 KB, 660 views)

Last edited by NiLuJe; 06-04-2022 at 06:23 PM. Reason: Released v0.11.4
NiLuJe is offline   Reply With Quote
Old 06-16-2021, 03:56 AM   #2
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Thanks, I installed it on my H2O. The nanoclock does show up, once, during boot. And then, it's just not there anymore. lsmod shows the module is being loaded, and I see nanoclock.lua running in pstree.

Enabling debug gives me these:

Code:
Jun 16 09:51:42 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 1020x1166+60+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 950x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 71x120+714+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:44 nanoclock[707]: No clock update necessary: damage rectangle 71x120+714+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:45 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:46 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:47 nanoclock[707]: No clock update necessary: damage rectangle 238x342+544+689 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:47 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:48 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:49 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:50 nanoclock[707]: No clock update necessary: damage rectangle 980x1166+50+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:50 nanoclock[707]: No clock update necessary: damage rectangle 824x315+196+716 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:00 nanoclock[707]: No clock update necessary: damage rectangle 245x488+50+181 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:06 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:06 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:25 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:15 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:19 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:20 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:38 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:40 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:00 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:03 nanoclock[707]: No clock update necessary: damage rectangle 380x879+30+41 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:03 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:04 nanoclock[707]: No clock update necessary: damage rectangle 300x70+70+729 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:05 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:06 nanoclock[707]: No clock update necessary: damage rectangle 903x83+88+917 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:07 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:07 nanoclock[707]: No clock update necessary: damage rectangle 145x74+846+179 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:08 nanoclock[707]: No clock update necessary: damage rectangle 113x70+878+441 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:08 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 643x34+234+704 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:12 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:13 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:15 nanoclock[707]: No clock update necessary: damage rectangle 1080x1310+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:15 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Does that mean it just thinks it never has to update?

PS: changed the intersection function to always return true ;-) now it works great

Last edited by frostschutz; 06-16-2021 at 04:19 AM.
frostschutz is offline   Reply With Quote
Advert
Old 06-16-2021, 05:08 AM   #3
jamalau
Connoisseur
jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.jamalau knows what's going on.
 
Posts: 78
Karma: 25542
Join Date: Nov 2013
Location: NRW Germany
Device: Kobo Forma
Thank you, great work, always works fine!
jamalau is offline   Reply With Quote
Old 06-16-2021, 05:13 AM   #4
Carmelocotonto
Connoisseur
Carmelocotonto began at the beginning.
 
Carmelocotonto's Avatar
 
Posts: 93
Karma: 12
Join Date: Nov 2018
Location: Salamanca
Device: kobo Clara HD, Onyxboox C67
Thanks MiLuJe, I have tried it. One question: the clock is not updated when time goes, isn't it? Only when I touch the screen the clock updates
Carmelocotonto is offline   Reply With Quote
Old 06-16-2021, 12:00 PM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@frostschutz: Well, that's... interesting . I'll take a look at it, thanks.

@Carmelocotonto: Yup. Doing that would be sort of trivial (assuming every minute on the dot), though, but I'm not sure there's much interest in it?

Last edited by NiLuJe; 06-16-2021 at 12:04 PM.
NiLuJe is offline   Reply With Quote
Advert
Old 06-16-2021, 12:03 PM   #6
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@frostschutz: Given the debug, I assume your clock is on the first row, but is it genuinely almost halfway behind the top-bezel?

(This seems related to the H2O's top 11 pixels offset).

EDIT: Oh, wait, no, it's related to the boot anim rotation >_<".

Last edited by NiLuJe; 06-16-2021 at 12:42 PM.
NiLuJe is offline   Reply With Quote
Old 06-16-2021, 03:04 PM   #7
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Released v0.9.2 .

It should fix the rotation related issue encountered by @frostschutz, and also implements an automatic refresh on every minute change, as proposed by @Carmelocotonto (configurable, enabled by default. Enabling backgroundless or overlay display modes silently disable it, as the combination would lead to overlapping text ).

EDIT: Updated to v0.9.4. No user visible changes, just minor code tweaks related to the changes above .

Last edited by NiLuJe; 06-16-2021 at 08:02 PM.
NiLuJe is offline   Reply With Quote
Old 06-16-2021, 05:51 PM   #8
Carmelocotonto
Connoisseur
Carmelocotonto began at the beginning.
 
Carmelocotonto's Avatar
 
Posts: 93
Karma: 12
Join Date: Nov 2018
Location: Salamanca
Device: kobo Clara HD, Onyxboox C67
very thankful. I am going to try it immediately. 8)

Quote:
Originally Posted by NiLuJe View Post
Released v0.9.2 .

It should fix the rotation related issue encountered by @frostschutz, and also implements an automatic refresh on every minute change, as proposed by @Carmelocotonto (configurable, enabled by default. Enabling backgroundless or overlay display modes silently disable it, as the combination would lead to overlapping text ).
Carmelocotonto is offline   Reply With Quote
Old 06-17-2021, 02:44 AM   #9
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Tested v0.9.4, and it works great now. Thanks again!
frostschutz is offline   Reply With Quote
Old 06-17-2021, 12:40 PM   #10
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Released v0.9.5.

Some more minor code tweaks related to the autorefresh feature (the actual timer is now toggled dynamically, instead of just the clock refresh).
NiLuJe is offline   Reply With Quote
Old 06-17-2021, 09:18 PM   #11
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
And now v0.9.6.

More low-level code tweaks (switched to inotify to handle config file modification tracking, which saves us a stat call before every clock update).
NiLuJe is offline   Reply With Quote
Old 06-18-2021, 10:47 PM   #12
Phil_C
Addict
Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.
 
Phil_C's Avatar
 
Posts: 245
Karma: 391602
Join Date: Oct 2009
Location: Chicago, IL USA
Device: Sony PRS-350; Kobo Clara HD; Kobo Clara 2E; Kobo Clara BW
This is working great, except for the auto update. The time does auto update on the home screen and other main screens, but not while in a book. This is on a Clara HD with the battery charge % also displayed.

Looking at it another way, the NanoClock auto updates only on screens where the regular Kobo clock is also visible.

Of course, pages will be getting turned while in a book.
Phil_C is offline   Reply With Quote
Old 06-18-2021, 11:04 PM   #13
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,484
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@Phil_C: You wouldn't happen to have backgroundless or overlay enabled, would you?

(c.f., https://github.com/NiLuJe/NanoClock/...oclock.ini#L85)
NiLuJe is offline   Reply With Quote
Old 06-18-2021, 11:21 PM   #14
Phil_C
Addict
Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.
 
Phil_C's Avatar
 
Posts: 245
Karma: 391602
Join Date: Oct 2009
Location: Chicago, IL USA
Device: Sony PRS-350; Kobo Clara HD; Kobo Clara 2E; Kobo Clara BW
Quote:
Originally Posted by NiLuJe View Post
@Phil_C: You wouldn't happen to have backgroundless or overlay enabled, would you?

(c.f., https://github.com/NiLuJe/NanoClock/...oclock.ini#L85)
No, both are set to 0.
Phil_C is offline   Reply With Quote
Old 06-18-2021, 11:25 PM   #15
Phil_C
Addict
Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.Phil_C ought to be getting tired of karma fortunes by now.
 
Phil_C's Avatar
 
Posts: 245
Karma: 391602
Join Date: Oct 2009
Location: Chicago, IL USA
Device: Sony PRS-350; Kobo Clara HD; Kobo Clara 2E; Kobo Clara BW
Here is my .ini file, if it helps.
Attached Files
File Type: txt nanoclock.ini.txt (5.2 KB, 485 views)
Phil_C is offline   Reply With Quote
Reply

Tags
clock, fbink, lua, miniclock, nanoclock

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cover images not persistent gogu1904 Kobo Reader 5 08-21-2020 10:55 AM
PW2 jailbreak not persistent chrnit Kindle Developer's Corner 3 01-06-2017 08:16 PM
Persistent Display? jessie102 Sony Reader 2 03-08-2010 09:45 PM
Persistent WIFI connection. tovarish iRex 2 11-16-2009 03:30 AM


All times are GMT -4. The time now is 12:56 PM.


MobileRead.com is a privately owned, operated and funded community.