I liked the program.
Aside overclocking I'm not interested, not found on the Loox 720 tasks with which he could not have done. And what kind of mobility during acceleration can be discussed if in your own Loox turbo mode for 2.5 - 3 hours battery sucks (at max load.)
But in the direction of decreasing consumption experimented (there were situations where it would be desirable to extend the reading time in Hali reader a little longer)
General comments (touch Loox 720):
1. As the author writes XGuru impossible to put the processor in the auto mode.
2. From that which mode was XGuru percent before starting and the final result depends (LCD operation stability, current consumption) own utility Looxa apparently operates kakimito parameters (most likely frequency LCD) which does not affect XGuru in their work
Experiment 1 (No running, is CF 1Gb (10 mA), the backlight 1 division (20 mA), the battery - 98%):
1. XGuru - 104 (percent) / 26 (tire) / fast memory; Loox - Turbo Mode
LCD not fails, current 100 mA
2. XGuru - 104 (percent) / 26 (tire) / fast memory; Loox - Standard Mode
LCD not fails, current 84 mA
3. XGuru - 104 (percent) / 26 (tire) / fast memory; Loox - Energy saving
LCD fails, current 78 mA (by the way, until the screen is hanging box "state" LCD is not buggy)
Experiment 2 (same as Eksperiment1 Khali + reader):
1. XGuru - 104 (percent) / 26 (tire) / fast memory; Loox - Standard Mode
LCD not fails, the current 84 - 95 mA, with a load of 120 mA
2. XGuru in monitor mode (running window state, girlfriend does not know how to talk to see); Loox - Energy saving
LCD (of course) no fails, the current 142 - 150 mA, with a load of 190 mA
When reading in the mode 1 (with no straining rate only download books naturally longer) 11 - 12 min for 1% capacity, while reading in the 2 mode - 7 min.
So it works :)
Post has been editedaov - 01.02.06, 16:34