Removing/Hiding Percentage or entire Progress Bar

[knc1]

Originally Posted by twobob

I /could/ expand this cover DX's... but I'm not sure it is an issue on DX?

On the DX, the progress line is only a few points high at the bottom of a very tall screen.

Personally, I don't see where it would be an issue.

[twobob]

agreed. That was my thoughts. Thanks

[sinan]

If only we could have something similar to this solution, it would be much better.

This one removes toolbar completely.
https://www.mobileread.com/forums/sho...d.php?t=207872

# lipc-set-prop com.lab126.pillow disableEnablePillow disable
# lipc-set-prop com.lab126.pillow disableEnablePillow enable

[twobob]

right. hope you don't mind - I removed the other attachment. just to be safe :\

feel free to give me a nudge to remove mine if you want to refactor your other solution to replace the log awking one I have provided. (this one should drain almost zero battery)

I suspect that "shove the rubbish on the bottom code" stuff is embedded in a jar somewhere...

probably Ixtab our resident ninja would know...

[sinan]

No problem. Mine was a rookie solution.

I wonder is there a way of completely removing progress bar? I spent last weekend to find a way but so far no luck.

[twobob]

hmm yeah. I think the solution would be - a) to find exactly where it is invoked and lives.

and then b) either interfere with the event that triggers it or even "kill" the thing inside where it lives.

assuming this things lives in a jar (which I think it will) perhaps gratuitous usage of "patch" may be in that jars future...

[twobob]

This:

Spoiler:

19999:19999 cvm[24461]: I ReadingTimerController:Information::PreviousPage,V erdict:Processed,BookInfo:BookInfo:Num words known in book:19999:Percentage of book for the known words:0.063599999999422:,LogDataReturnCode:-2,GlobalWPM:196.716099999943,GlobalTime:22299992,G lobalWords:199991,CurrentPos:MobiPosition: 399994,EndPos:MobiPosition: 199991,PosLeft:199997,%Left:0.9739999999999992,Cur rentPagePosDiff:9999,TimeForPage:99,PosPassed:fals e,NewTimeLeft:9999,OldTimeLeft:99999,NextTOCEntryL abel:CHAPTER 3,NextTOCEntryPosition:MobiPosition: 5999,NextTOCEntryLength:99999,NextTOCEntryLevel:0, NextTOCEntryType:,CurrentPos:MobiPosition: 39999,EndPos:MobiPosition: 51689,PosLeft:9999,%Left:0.01999999999995,CurrentP agePosDiff:1999,TimeForPage:99,PosPassed:false,New TimeLeft:1999,OldTimeLeft:999,TimeLeftInBookString :Time left in book: 19 h 99 m,TimeLeftInSectionString:Time left in chapter: 99 m;

looks to be the rubbish that is involved...

so...

/opt/amazon/ebook/lib/ReadingTimer-pt_BR.jar
/opt/amazon/ebook/lib/ReadingTimer-es_ES.jar
/opt/amazon/ebook/lib/ReadingTimer-it_IT.jar
/opt/amazon/ebook/lib/ReadingTimer-en_GB.jar
/opt/amazon/ebook/lib/ReadingTimer-zh_CN.jar
/opt/amazon/ebook/lib/ReadingTimer-de_DE.jar
/opt/amazon/ebook/lib/ReadingTimer-fr_FR.jar
/opt/amazon/ebook/lib/ReadingTimer.jar
/opt/amazon/ebook/lib/ReadingTimer-ja_JP.jar

at a guess?

so I copied the entire contents of the /opt/amazon/ebook/lib/ dir to /mnt/us/lib and

[root@kindle root]# mount --bind /mnt/us/lib /opt/amazon/ebook/lib
and then
rm /mnt/us/lib/ReadingTimer-*
restart framework

voila, reading timer nerfed.

just get the oldy wordly LOC 999 and 9% in it's stead.

The mount, and restart commands would only survive until a restart so not dangerous to play around.

Hope it helps.

[cody.]

I found that the log-tailing solution worked great on my K4NT, but it would stop functioning every time the messages log was rotated, which turned out to be every 15 minutes.

To solve, I had to cross-compile a version of busybox with the "fancy tail" option enabled, which provides the -F option for tail. It tails the file based on name rather than file descriptor. Now it works until reboot.

Thanks!