|
harry, think about what happens when you play mp3s. using the cpu definately will affect power consumption, and constant polling is pretty taxing.
however, on second thought, i think polling every 10 ms or so won't affect the battery much and will also give perfect responsiveness.
then after 10 minutes of inactivity i'll...
no, wait, what will i do? it probably will not turn itself off like it normally does since i'm stealing all the messages. either that, or it'll turn itself off all the time because i'm stealing all the messages...
Hopefully it won't turn itself off, and I think I can just cut down the polling to be even more infrequent and put the screen into standby (there's an ioctl for that). Hopefully you're right, and my slow-polling method will yield the same two weeks of battery.
But I really wonder what i'll be affecting by messing with /dev/ttyDB0. Am I going to have to take over everything, including the power button? Even battery status supposedly gets conveyed over ttyDB0 so I might have to do that too (which is good, seeing as it doesn't work now!). But I'm not sure how i'd decode the messages for things like that.
The only thing I pray for is that the reset button doesn't use ttyDB0 ;-)
|