Thread: NanoClock: Yet another persistent clock
View Single Post
Old 04-22-2022, 08:32 PM   #195
Deobulakenyo
Guru
Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.
 
Posts: 706
Karma: 2153490
Join Date: Aug 2021
Location: Stupid Philippines
Device: Kobo Libra 2, Boyue Likebook P78
Quote:
Originally Posted by NiLuJe View Post
And released version 0.11.2, which should fix the crash mentioned above .
Thank you but...

Still happens. after importing a book via calibre using USB connection, nanoclock disappears

Using Kobo Uncaged, nanoclock works fine after disconnecting via KU in the device or ejecting via Calibre
Attached Files
File Type: txt v11.2.nanoclock.log.txt (12.9 KB, 104 views)
Last edited by Deobulakenyo; 04-22-2022 at 09:36 PM.
Deobulakenyo is offline   Reply With Quote