Tools kindle-reading-dashboard — view your on-device reading stats, pace & metadata

zevi svei · Yesterday, 03:31 AM

I put together a small offline toolkit that reads and visualizes the reading metadata a Kindle already stores on-device — reading time, pace (WPM), per-book progress, highlights, printed-page mapping, and read/unread status — in a local web dashboard. No cloud account, no Amazon API, no KOReader.

GitHub: https://github.com/zevisvei/kindle-reading-dashboard
License: GPL v3

What it shows

Library list: title, author, series, % complete, reading time, pace, current page, read/reading/unread — sortable & searchable.
Per-book detail: timer.model reading-time data, reading-speed distribution, reading timeline, device sessions, highlights/notes, font prefs, all cc.db fields, plus the raw decoded JSON of every source.
Position → printed page translation via the apnx page map.

Where the data comes from

cc.db (/var/local) — library: title/author/series/%/legacy read-state.
*.azw3f / *.azw3r KRDS sidecars — reading time/pace (timer.model), word counts, page history, last/first position, annotations, font prefs.
fmcache.db (/mnt/us/system/fmcache) — this was the interesting find: the modern "Mark as Read" status is NOT in cc.db.p_readState. The new app keeps read-state in fmcache (schema mar_content_readstate_update_success) and in the cloud (whispersync BookReadStates), so a manual mark can sit there without ever touching p_readState. The dashboard reads fmcache and uses it as an override, and also surfaces the per-book reading_sessions there.

Requirements

Python 3 + paramiko.
Full dashboard needs a jailbroken device with USB networking (SSH). Basic sidecar decoding (time/pace/highlights/page map) works on a stock device mounted as a USB drive, via the CLI scripts or --local.

Tested on a Kindle Basic 10th gen (J9G29R), FW 5.18.1.

Credits
The KRDS parser (krds.py) is John Howell's work (GPL v3) from the KRDS thread ( https://www.mobileread.com/forums/sh...d.php?t=322172 ); I patched it for FW 5.18.x (a raw fallback so unknown/new structures don't break decoding). Windows RNDIS usbnet driver by Marco77.

Not affiliated with Amazon. Reads metadata only — no DRM circumvention, read-only against the device. Feedback welcome.

j.p.s · Yesterday, 10:25 PM

Looks very interesting!

Have you considered making a pull request to the KRDS github repository with your changes to krds.py?

Yesterday, 03:31 AM	#1
zevi svei Junior Member Posts: 7 Karma: 100000 Join Date: Feb 2023 Device: Kindle Paperwhite ,boox tab ultra	kindle-reading-dashboard — view your on-device reading stats, pace & metadata I put together a small offline toolkit that reads and visualizes the reading metadata a Kindle already stores on-device — reading time, pace (WPM), per-book progress, highlights, printed-page mapping, and read/unread status — in a local web dashboard. No cloud account, no Amazon API, no KOReader. GitHub: https://github.com/zevisvei/kindle-reading-dashboard License: GPL v3 What it shows Library list: title, author, series, % complete, reading time, pace, current page, read/reading/unread — sortable & searchable. Per-book detail: timer.model reading-time data, reading-speed distribution, reading timeline, device sessions, highlights/notes, font prefs, all cc.db fields, plus the raw decoded JSON of every source. Position → printed page translation via the apnx page map. Where the data comes from cc.db (/var/local) — library: title/author/series/%/legacy read-state. .azw3f / .azw3r KRDS sidecars — reading time/pace (timer.model), word counts, page history, last/first position, annotations, font prefs. fmcache.db (/mnt/us/system/fmcache) — this was the interesting find: the modern "Mark as Read" status is NOT in cc.db.p_readState. The new app keeps read-state in fmcache (schema mar_content_readstate_update_success) and in the cloud (whispersync BookReadStates), so a manual mark can sit there without ever touching p_readState. The dashboard reads fmcache and uses it as an override, and also surfaces the per-book reading_sessions there. Requirements Python 3 + paramiko. Full dashboard needs a jailbroken device with USB networking (SSH). Basic sidecar decoding (time/pace/highlights/page map) works on a stock device mounted as a USB drive, via the CLI scripts or --local. Tested on a Kindle Basic 10th gen (J9G29R), FW 5.18.1. Credits The KRDS parser (krds.py) is John Howell's work (GPL v3) from the KRDS thread ( https://www.mobileread.com/forums/sh...d.php?t=322172 ); I patched it for FW 5.18.x (a raw fallback so unknown/new structures don't break decoding). Windows RNDIS usbnet driver by Marco77. Not affiliated with Amazon. Reads metadata only — no DRM circumvention, read-only against the device. Feedback welcome.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sync reading stats between 2 device (Clara HD / Libra 2)	TDUK	Kobo Reader	0	06-13-2024 11:04 AM
Kobo daily reading stats same on Kindle? How?	sofia915	Kobo Reader	8	04-28-2021 07:50 AM
Glo Reading Life Reading Stats inaccuracy	Uschiekid	Kobo Reader	18	02-08-2014 08:57 PM
Digital Reading Company Kobo 'On Pace To Be A Billion Dollar Company	taming	General Discussions	4	09-28-2013 04:15 AM
Glo How to access Reading Menu Stats reading sideloaded epubs	cinetici	Kobo Reader	23	05-27-2013 07:43 AM

Yesterday, 10:25 PM	#2
j.p.s Grand Sorcerer Posts: 6,031 Karma: 107275331 Join Date: Apr 2011 Device: pb360	Looks very interesting! Have you considered making a pull request to the KRDS github repository with your changes to krds.py?

Advert