Force the indexing of a book

[encol]

Hello, i wonder if there's any way to force the building of the index of a book?
I downloaded a (large) book on my pw3 and for a lot of time i was unable to search anything on it.
Any command to force this process or to show the current status?

Perhaps we can make a kual extension

[knc1]

Originally Posted by encol

Hello, i wonder if there's any way to force the building of the index of a book?
I downloaded a (large) book on my pw3 and for a lot of time i was unable to search anything on it.
Any command to force this process or to show the current status?

Perhaps we can make a kual extension

There are some indexer control scripts among the semi-colon searchbar commands in the factory firmware images.

Open one of those images with KindleTool and browse the scripting for signs of an answer to your question.

[knc1]

Ref:
/usr/share/webkit-1.0/pillow/debug_cmds.json
and the scripts it calls in one of the factory_initial.bin packages used for the downgrade jailbreak (see step #3 for link to their index page).

[encol]

Thanks, I'll give a look

[encol]

/usr/share/webkit-1.0/pillow/debug_cmds.json:

...
    "`stopIndexing" : "/usr/local/bin/indexerstop.sh",
    "`startIndexing" : "/usr/local/bin/indexerenable.sh",
    "`disableIndexing" : "/usr/local/bin/indexerdisable.sh",
    "`indexStatus" : "/usr/local/bin/indexstatus.sh",
...

i'm going to make the extension

[knc1]

Something I am sure you know . . .

Those scripts are not on the consumer version firmware so you will have to re-invent them for your extension so as not to re-distribute Amazon code.
But they will contain the system indexer control commands.

Note:
Lua is pre-installed on all 5.x firmwares and you can 'exec' a Lua script from the KUAL control files rather than call a shell script.
Ah...
That isn't specific to Lua, KUAL control files can either call or exec any executable code, the calling an external shell script is only tradition here.

Translation:
If the control script is just a simple system control command - stick the system control command directly in the menu.json command line of KUAL.
If the command requires arguments, use the 'params' field of menu.json command line.

- - - -

I.E: There is a lot of flexibility in how you chose to 'not duplicate Amazon code'.

PS: Sorry for stealing the ;log searchbar command - but we put a 'dispatcher' script on it, so you can put your 'hide books' calls into the 'dispatcher' script.
I don't recall if anyone PM'd you about doing that last month, it was a hectic few days.

[encol]

Originally Posted by knc1

PS: Sorry for stealing the ;log searchbar command - but we put a 'dispatcher' script on it, so you can put your 'hide books' calls into the 'dispatcher' script.
I don't recall if anyone PM'd you about doing that last month, it was a hectic few days.

no problem

[encol]

i'm trying the commands i found in the script but, when i try to suspend the indexer:

lipc-set-prop -- com.lab126.indexer pauseIndexerMilliseconds 86400000

nothing happens, and in /var/log/messages i see:

160802:230232 cvm[4818]: E IndexerThread:Error::indexer pause, unsourced, value 86400000 not supported, non-positive values clear all sourced pauses

i tried also other values but nothing changes

[geekmaster]

"160802:230232 cvm[4818]: E IndexerThread:Error::indexer pause, unsourced, value 86400000 not supported, non-positive values clear all sourced pause"

That sure looks like it is saying the number of milliseconds you specified is an unsupported value (probably too large). Try a smaller number.

What value did the factory script use?

[encol]

Originally Posted by geekmaster

"160802:230232 cvm[4818]: E IndexerThread:Error::indexer pause, unsourced, value 86400000 not supported, non-positive values clear all sourced pause"

That sure looks like it is saying the number of milliseconds you specified is an unsupported value (probably too large). Try a smaller number.

What value did the factory script use?

86400000.
I tried also smaller numbers, with no luck

[knc1]

Originally Posted by encol

i'm trying the commands i found in the script but, when i try to suspend the indexer:

lipc-set-prop -- com.lab126.indexer pauseIndexerMilliseconds 86400000

nothing happens, and in /var/log/messages i see:

160802:230232 cvm[4818]: E IndexerThread:Error::indexer pause, unsourced, value 86400000 not supported, non-positive values clear all sourced pauses

i tried also other values but nothing changes

So it isn't double precision (from the message that the value was treated as negative).

Will lipc-probe tell you what is expected as arguments?

Well, now you know how to clear all other indexer pauses ( pass -1 ).
Which is what you wanted, isn't it?

Your topic here was:
"Force the indexing of a book"
So now that you have removed all reasons for the indexer to pause, I guess that is what it will do, index your book.

[encol]

Originally Posted by knc1

So it isn't double precision (from the message that the value was treated as negative).

Well, now you know how to clear all other indexer pauses -
Which is what you wanted, isn't it?

Your topic here was:
"Force the indexing of a book"
So now that you have removed all reasons for the indexer to pause, I guess that is what it will do, index your book.

Yes, but in the factory script it uses -1 as value to clear pauses.
However, in the extension i'm writing i want to have also a button to pause the indexer

Anyone knows the difference between a "sourced" and a "unsourced" pause?

[knc1]

I had the same question myself when reading many lines of log messages.

Since this is a multi-threaded, multi-tasked processing system and the messages aren't sequenced ....

I found that it helps to sort the messages (usually by the originating task name) - -
I **think** there must be an "expected from" list (sourced) and otherwise its (unsourced).

Let me stress that the above is a WAFG without any testing behind it.

[encol]

I can't get indexer suspension working on my pw3, but i don't know if the problem is related to my device/fw.
Indexer status and enabling seems to work, so i pubblish anyway the extension, so if someone wants to test it and report back it would be appreciated

Furthermore i don't know if eips stuff works also on KOAs