19
edits
Mobile/PowerUsage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
<ul> | <ul> | ||
<li>The variation between power models for different types of phones is significant. Therefore a meter-based power model will have to be generated for each new phone that we want to test.</li> | <li>The variation between power models for different types of phones is significant. Therefore a meter-based power model will have to be generated for each new phone that we want to test.</li> | ||
</ul> | </ul> | ||
| Line 29: | Line 28: | ||
Right now we automate only on tegra boards that are on full AC power. | Right now we automate only on tegra boards that are on full AC power. | ||
According to Clint Talbert (ctalbert), once he has the s1s2 stuff live (don't know what s1s2 is), we can look at testing this on real devices on a per-nightly basis. | According to Clint Talbert (ctalbert), once he has the s1s2 stuff live (don't know what s1s2 is), we can look at testing this on real devices on a per-nightly basis. | ||
<strong>Questions</strong> | |||
<ul> | |||
<li>Is being test accurately only on the G1, G2 and Nexus One a dead breaker? If so, we would have to pick another device and use the Main Paper above to generate a power model for it and code up an implementation similar to PowerTutor's. Thankfully we have the source code for it!</li> | |||
<li>Right now I am manually starting PowerTutor and then running RoboCop tests, then stopping PowerTutor and transfering a log to a machine on which I run an analysis script. Ideally I could fully automate the process by running setup and teardown Robotium-style scripts.</li> | |||
<li></li> | |||
</ul> | |||