Detect page changing

[encol]

Hello there is any lipc event to detect when the user changes the "page" of a book?

[encol]

None?
As alternative, any way to detect current page/position of the book?

[geekmaster]

There may be such an event (lipc or otherwise, such as a /proc or /sys file), but it would probably be different for different kindle models, and perhaps different firmware versions within a given model (not unknown for lab126 to make such changes in the past).

You might be able to find what you seek in the GPL source code for your firmware version, or in the firmware update*.bin file (root filesystem extracted with Kindletool), or in the de-obfuscated (if required) .jar files within that rootfs.

[Hanspeter]

or you can check /var/log/messages as it is used in the titlebar extension if there is a message for a page turn.
I also used this to trek the password dialogue on the screenserver. But as geekmaster said, that messages can/will change with different firmware versions.

HaPe

[encol]

Originally Posted by Hanspeter

or you can check /var/log/messages as it is used in the titlebar extension if there is a message for a page turn.

Wow!
I tried geekmaster's suggestions with no luck (even if i'm not sure if i looked everywhere ), but this works!:

This is what i get when i go to the next page:

160602:101443 cvm[4541]: I ContentPanel:UserActionInfo:PageTurnAction=NextPage:
160602:101443 cvm[4541]: I ReadingTimerController:Information::NextPage,Verdict:Processed,PageStartPos:MobiPosition: 330792,IntervalTime:29047,IntervalWords:80,IntervalWPM:165.24942334836646,ScreenStart:MobiPosition: 330072,ScreenEnd:MobiPosition: 330791,Interval%:0.001501664571158745,TotalTime:29120673,TotalWords:87503,TotalWPM:498.47944109174074,Total%:1.2977535599266443,BookInfoKnownWords:107098,BookInfoKnown%:1.6013863768321634,LogDataReturnCode:80,GlobalWPM:1996.070252681267,GlobalTime:29120673,GlobalWords:227962,CurrentPos:MobiPosition: 330792,EndPos:MobiPosition: 478702,PosLeft:147910,%Left:0.3089168382755293,CurrentPagePosDiff:661,TimeForPage:3.066024350485245,PosPassed:false,NewTimeLeft:2460,OldTimeLeft:6931,NextTOCEntry:null,CurrentPos:MobiPosition: 330792,EndPos:MobiPosition: 478702,PosLeft:147910,%Left:0.3089168382755293,CurrentPagePosDiff:661,TimeForPage:3.066024350485245,PosPassed:false,NewTimeLeft:2460,OldTimeLeft:6931,TimeLeftInBookString:Tempo alla fine del libro: 41 min.,TimeLeftInSectionString:Tempo alla fine del capitolo: 41 min.;

Thanks a lot!

[geekmaster]

Originally Posted by encol

Wow!
I tried geekmaster's suggestions with no luck (even if i'm not sure if i looked everywhere ), but this works!:

While monitoring /proc and /sys for status changes, I would also look in /var/log/messages (and other places as well). It did not occur to me to explicitly say to look in "other places as well" when I posted. Yes, there can be useful log messages, but as mentioned previously, such things can vary by firmware model, and especially by log level (i.e. ~debugOn), and the 'dmesg' log can even have a log level set where almost NOTHING gets posted there (useful when re-puposing the serial port, which also displays log messages).

I will try to be more explicit in the future, but the reason I mentioned /proc and /sys is that the "next page" 'keypress' or touchscreen event may be found there, and lab126 is fond of putting things you would think belong in userland into their device drivers (such as screensaver management in the eink display driver).

Not only can various log messages be prevented from being logged, but their format can change as well so even if logged, detecting them reliably could be tricky if you want your hack to continue to work across multiple devices and firmware versions, and not suffer "bit-rot" over time.

I prefer the simplest solution whenever possible, but it must also be robust and reliable.

[encol]

Don't worry, geekmaster.
I appreciated your suggestions, and perhaps i missed something in my search.
There was too many things for me to look into, and i wasn't able to deobfuscate completely jar files.
I don't know if there is a simplier/more efficient method, and i'd prefer a lipc event for my code, but Hanspeter's one is the only working method i have found for now

[geekmaster]

Anything that works is a great place to start. As long as it works for your needs, no need to make it portable to other devices. Still worth sharing your results though. Keep us posted.

[encol]

I'm working on a improved version of the "show time" extension, in order to call eips only when necessary.
As soon as i have a working version i'll post it

Meanwhile...
What's in your opinion the best way to check the /var/log/messages (better if only the lines added from the last check)?

[geekmaster]

Years ago, I tried "inotify" on a kindle, but it was mostly useless. Files changed without detection. Not sure if there is a reliable way other than to see if the logfile timestamp or size has changed, by periodic polling. Though you could try inotify again (but it may require linux kernel support). Others have discussed this issue as well:

How to notice log file changes with Linux standard tools?

In Linux, how do I run a shell script when a file or directory changes

https://en.wikipedia.org/wiki/Inotify

Like I said, inotify did not work for me (but that was years ago), so tools based on inotify are likely to be unreliable too. YMMV

[NiLuJe]

Using inotify is a bit tricky because of both the USBMS handling and the fuse layer proxy.
You basically have to watch out for unmounts, and re-create your watches when the userstore becomes available again (that takes care of the USBMS issue), and you have to setup your watches on base-us and not us (that takes care of the fuse proxy).

See the <K5 screensavers hack for an example. Which also bundles the required inotifywait tools.

See also the same basic principle on the other side of the fence for another example of how to deal with USBMS, in C this time.

[sguerrini97]

I used dbus-monitor to detect some lipc events (like going in/out of screensaver, hide/show title bar, ...). Perhaps you can find the page turn event there too.

dbus-monitor --system

[encol]

Originally Posted by sguerrini97

I used dbus-monitor to detect some lipc events (like going in/out of screensaver, hide/show title bar, ...). Perhaps you can find the page turn event there too.

dbus-monitor --system

I tried but no events for page changing are raised
However... Nice trick to discover lipc events