|
2010-10-15
, 11:40
|
Posts: 91 |
Thanked: 22 times |
Joined on Apr 2010
@ Germany
|
#12
|
|
2010-10-15
, 12:29
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#13
|
You could charge it while testing. But this would generate more heat. On the other hand this may not be bad since you dont want you device to fail in Summer just becuase you finetuned it in Winter.
|
2010-10-15
, 15:37
|
Posts: 284 |
Thanked: 74 times |
Joined on Mar 2010
@ Wigan, UK
|
#14
|
|
2010-10-15
, 19:44
|
Posts: 166 |
Thanked: 30 times |
Joined on Apr 2010
@ Halifax, UK
|
#15
|
|
2010-10-15
, 19:53
|
|
Posts: 1,210 |
Thanked: 597 times |
Joined on Apr 2010
@ hamburg,germany
|
#16
|
|
2010-10-16
, 08:07
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#17
|
Have you tried looking in "dmesg" after taken a picture or done a video? It could be working but also generate looping errors that depleats your battery faster. I think that however this will become it will need or some way of listening on error output. I am not sure "dmesg" would be enough. If we could find out the precise error that occur just before reboot.. then we will be able to make a more robust script/program.
A nother problem with the "reboot" strategy would be what to do if the battery gets fully depleated. Reboots takes about 10% battery.
all this fuss over, over clocking. it'd be a waste of time for a dev to do this especially seen the profile's make almost no difference to battery life
its not the cpu thats the problem really.
if you want to have a low voltage load because you think it'll give you more battery life, try dimming the screen and disconnecting from gprs/wifi and turning bluetooth off instead
|
2010-10-18
, 08:03
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#18
|
Well, we can always pipe STDERR to a file in /tmp/, then read that file. The only issue would be determining -real- errors from comments or errors not caused by the OC process(say a slightly corrupted video file etc.)
Actually, this is something of a myth. Rebooting resets the internal battery percentage calculation, which is then based solely on the battery voltage.
This means that -- depending -- a reboot can cause relatively unpredictable results in the battery % value. Sometimes it will go down 10%, sometimes up... But 10 reboots in under an hour won't drain your battery completely, no matter how much a single reboot "drained".
It -will- take some power though, but considering that you should be able to run fully loaded for 3-6hrs(depending on condition of the battery), it shouldn't be -that- much of a problem.
Charging it during the test probably wouldn't hurt -too- much, and charging it before the test would also be a good idea.
|
2010-10-18
, 08:08
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#19
|
all this fuss over, over clocking. it'd be a waste of time for a dev to do this especially seen the profile's make almost no difference to battery life
its not the cpu thats the problem really.
if you want to have a low voltage load because you think it'll give you more battery life, try dimming the screen and disconnecting from gprs/wifi and turning bluetooth off instead
|
2010-10-18
, 09:42
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#20
|
A nother problem with the "reboot" strategy would be what to do if the battery gets fully depleated. Reboots takes about 10% battery.
You like what i do? Donate!
Make your desktop look awesome - use the AwOken Theme with the AwOken Icon Theme.
Add me on twitter @almehdin
Visit the swedish maemo/meego community forums