Thread: NanoClock: Yet another persistent clock
View Single Post
Old 06-24-2022, 03:54 AM   #208
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,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
miniclock is unmaintained and won't work with latest firmwares - at the very least, the patch to no longer grab input events exclusively so miniclock can listen in, no longer works for current firmware so you would have to patch it manually, and you'd also have to update fbink manually for device support...

I doubt that miniclock could fix any issue that nanoclock has... its an issue with the device itself, anyhow
Last edited by frostschutz; 06-24-2022 at 04:14 AM.
frostschutz is offline   Reply With Quote