I am a firm believer that using a 1% battery driver will drain it faster simply because the device has to do more work to continually update the battery level. Also, what is your Poll Interval set at?
Check it here: HKLM\Drivers\BuiltIn\Battery\PollInterval
mine is 4e20 (been using that for like a year on juicy's recommendation)
If you are using a visual kitchen (or platformrebuilder, which is what EVK uses anyway) check your balance of modules vs files. The more modules you have the more memory will be used (since modules are ALWAYS in RAM) and therefor more cpu cycles will be wasted on them, thus draining more power. Another thing to sheck is startup entries, how much crap is running on top of all the potentially useless modules? get a task manager (dotfred's is good) and check how much memory is being used by the various system processes such as device.exe and gwes.exe.
If all that is too much information or you have no idea what I am talking about just ask your chef what his or her memory map looks like (what slots are filled with how many modules) I believe even with the 6.5 native kernel, even though we CAN have more modules, I don't think we SHOULD. I treat slot 60 as the new slot 0. Keep slot 0 as free as possible since those are the spots in memory that are higher up (faster access) and leave them reserved for the system processes. slot 60 comes next, I keep that clear too. I want to have the best memory management and the best battery life. And it really does show. the order of slots is 0, 1, 60, 61..
example. here's mine:
Code:
Memory Map...
SLOT 0: 0x02000000 - 0x01be0000 (END: 0x00060000, 0 MODULES)
0x02000000 - 0x01fe0000 - ROM 0
0x01fa0000 - 0x01be0000 - ROM 1
SLOT 1: 0x04000000 - 0x02022000 (END: 0x02020000, 272 MODULES)
SLOT 60: 0x7a000000 - 0x7a000000 (END: 0x78020000, 0 MODULES)
SLOT 61: 0x7c000000 - 0x7b610000 (END: 0x7a020000, 63 MODULES)
RAM IMAGE: 0x80000000 - 0x80294c70
RAM: 0x80295000 - 0x80365000 - Used for kernel modules
0x80365000 - 0x84000000 - 60 MB free
hope it helps