View Single Post
Old 11-21-2010, 07:22 AM   #16
h1uke
Zealot
h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.h1uke can do the Funky Gibbon.
 
Posts: 121
Karma: 82565
Join Date: Aug 2010
Location: Maryland, USA
Device: dxg, k3w,k4nt,kpw
Quote:
Originally Posted by WS64 View Post
First, is it possible to force FBKindle to ignore any CSS coming with a book?
AFAIU you can only ignore CSS's _fonts_. Just check the 'always use my fonts' on the CSS tab of options dialog
Quote:
Originally Posted by WS64 View Post
Second, when you shut down the Kindle while it is in FBKindle mode it shows a (pretty empty) Amazon Screensaver, is there a way to change this?
Show nothing, or show something fancy?
The undocumented shell command is currently used to invoke the screensaver:
Code:
/usr/sbin/eips -s 5
Can this be used to show other images? Probably, I don't know.

Quote:
Originally Posted by WS64 View Post
And since the Kindle reacts different here, is there any other difference between the Kindle sleepmode and the FBKindle sleepmode?
both programs just catch signals from the power daemon which acts at certain intervals of inactivity.
The length of this interval is a system-wide setting, and there should be a way to change this.
You can trigger the power daemon signal by sliding the power button or by simulating this action in software:
Code:
powerd_test -p
or
Code:
powerd_test -h
simulate "press" and "hold" power button action, respectively.

In a response to a 'sleep' signal current build of fbKindle just shows the screensaver and blocks its screen output.
Maybe the native framework does more.. currently unknown.

Quote:
Originally Posted by WS64 View Post
With FBKindle to me it seems that the battery drains fast, but that just might be my imagination)
based on the assumption that refreshing eink is the most energy-hungry part of the unit,
this can be caused even by running clock shown at the right bottom.
h1uke is offline   Reply With Quote