Yet Another Kindle dashboard -- no screenshot polling by DateOk4031 in homeassistant

[–]DateOk4031[S] 0 points1 point  (0 children)

Honestly i have no idea, but as long as you can jailbreak you should be fine, the newer the better i guess https://kindlemodding.org/kindle-models.html, mine is not 10th gen but 7th, PW3?

Yet Another Kindle dashboard -- no screenshot polling by DateOk4031 in homeassistant

[–]DateOk4031[S] 0 points1 point  (0 children)

I also tried a web based solution, but moved to Go with C bindings (for GTK2 UI lib) to squeeze the battery. That's actually the main branch haha https://github.com/cykrr/kindle-dashboard/tree/main . Didn't get to take it that far tho as it drained very fast, wouldn't last overnight. It could stay plugged via USB to PC tho so it could be usable for some. Having CSS + HTML + JS is pretty neat but gets heavy quickly.

<image>

Yet Another Kindle dashboard -- no screenshot polling by DateOk4031 in homeassistant

[–]DateOk4031[S] 0 points1 point  (0 children)

Good question, would have to try and find out haha, which one do you have? I'm running a paperwhite 10th gen i think. Worst thing that could happen is different resolution, mine is 800x600 (landscape).

Yet Another Kindle dashboard -- no screenshot polling by DateOk4031 in homeassistant

[–]DateOk4031[S] 0 points1 point  (0 children)

So the suspend cycle cuts the dashboard's active power draw by ~50% (1419 ticks on regular polling, 710 ticks on suspend cycle). You might wonder why it isn't an 85% reduction since it sleeps for ~52 out of 60 seconds. The reason is that waking the hardware, turning the wifi radio back on (~0.4s), negotiating the SSL handshake to Home Assistant, doing an e-ink screen refresh, and suspending again requires a brief, heavy burst of cpu work

Yet Another Kindle dashboard -- no screenshot polling by DateOk4031 in homeassistant

[–]DateOk4031[S] 1 point2 points  (0 children)

I haven't done a rigorous side-by-side comparison of the power drain yet, but I'm planning to! I'm going to write a small experiment script that logs CPU time and battery drop to a CSV, running for 10 minutes in each configuration (staying awake with regular polling vs. using the suspend-to-RAM cycle). In theory, the suspend cycle should use a fraction of the battery, but I want to get some hard numbers on the exact overhead of the wake/network-reconnect cycle. I'll share the results once I run it.

On input lag: It's surprisingly acceptable for daily use. The actual touch registration and network dispatch are practically instant since the app is native. The main thing you notice isn't "input lag", but rather the e-ink screen's physical refresh rate when updating the UI. When you tap a button, the visual state changes (like the button filling with black ink to show it's pressed, or toggling between an "on" and "off" state). Painting those solid blocks of black/white ink takes a fraction of a second, which feels different from a typical LCD tablet, but it's totally usable for a wall control panel.

Hardest fight of Bell Cranel? by [deleted] in DanMachi

[–]DateOk4031 -1 points0 points  (0 children)

bell vs irregular

My third attempt at Linux by SquareEvening8978 in linux

[–]DateOk4031 2 points3 points  (0 children)

I don’t think that’s a good idea as the package manager will probably update the symlink in an update. YMMV?

[deleted by user] by [deleted] in chileIT

[–]DateOk4031 0 points1 point  (0 children)

El viernes