> -----Original Message----- > [mailto:[email protected]] On Behalf Of ext > Zachary Goldberg > Sent: 27 October, 2009 01:51 > To: Gil Quim (Nokia-D/Helsinki) > > > The problem I see now is that either you know about power > management > > issues and how to detect them or you don't. it would be > great to have > > really basic documentation telling testers like me to > install whatever > > tools, follow clear steps and evaluate the output. --snip-- > > Hi! This is my first post (of hopefully many useful ones in the > future!) to the maemo-developers list. > > I definitely remember some documentation on this. I can't > seem to find it on the wiki so perhaps it was at the Maemo > Summit. Anyway the procedure is basically:
The tool manuals will move to the wiki once the Fremantle version is updated. The Diablo versions were in http://maemo.org/development/documentation/man_pages/ Most of them still apply, but some changes have happened. I don't see powertop in the Diablo version for instance. But the below is essentially what the average tester should do. Testing also promoted top as a power tool, if the app spends time on the top of top even when it is supposedly inactive it is doing something wrong. > 1) Run 'powertop' in xterm (or via ssh) and observe a rough > number of wakups per second > 2) Run the application, then switch back to ssh/xterm > 3) Run powertop again. Observe the number of wakeups per > second to see if its much larger than before. > > I have already used this procedure succesfully to find a > widget which was causing a huge number of wakeups in hildon home > (https://bugs.maemo.org/show_bug.cgi?id=5351) > > -Zach Goldberg Exellent simple guide, thanks :-) Tero _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
