Thread: NanoClock: Yet another persistent clock
View Single Post
Old 12-10-2021, 08:32 PM   #117
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
It should *always* come back after a full reboot, so I'd try to pin this down first .

(Otherwise, I would need debug logs to tell you what might be happening, but the likeliest culprit is a broken USBMS session).

It was okay in my Libra H2O. This only happens on my Libra 2. Full reboot does not always fix it.
Deobulakenyo is offline   Reply With Quote