Revision history [back]

Harbour QA process is using powertop tool. I'll try to add some instructions how developer can debug and reproduce similar problems. This needs enabled developer mode on the Jolla device.

Steps to install powertop from command line:

1. Add mer-tools repository: "ssu ar mer-tools"
2. Refresh repository cache: "pkcon refresh"
3. Install tool: "pkcon install powertop"

After installing powertop tool, usage is easiest via ssh over USB or WLAN connection. Difference between these connections is that device does not suspend when we have PC USB connection enabled and with WLAN device goes to suspend if we don't have any network traffic and display is turned off.

With powertop tool one can see all running processes which are waking up and how many times in a second. If we strace only our own process, it does not tell all about the system, e.g. when our process has interaction with audio or network. Of course applications are allowed to do things on a background but that should be minimal for its own functionality.

Harbour QA testing is mostly done with PC USB cable connection, application minimized to home screen and display is turned off. In this state application should not block suspend and wake ups should be minimal. Suspend is blocked by wake locks and easy test for that is catting /sys/power/wake_lock file. The file should be empty normally if nothing from user space is not blocking suspend. If application is using e.g. audio, then file should include "mce_cpu_keepalive" string. Powertop output is easy to take before opening application and compare those results when application is minimized to home screen.

Hopefully this post will help developers!

Harbour QA process is using powertop tool. I'll try to add some instructions how developer can debug and reproduce similar problems. This needs enabled developer mode on the Jolla device.

Steps to install powertop from command line:

1. Add mer-tools repository: "ssu ar mer-tools"
2. Refresh repository cache: "pkcon refresh"
3. Install tool: "pkcon install powertop"

After installing powertop tool, usage is easiest via ssh over USB or WLAN connection. Difference between these connections is that device does not suspend when we have PC USB connection enabled and with WLAN device goes to suspend if we don't have any network traffic and display is turned off.

With powertop tool one can see all running processes which are waking up and how many times in a second. If we strace only our own process, it does not tell all about the system, e.g. when our process has interaction with audio or network. Of course applications are allowed to do things on a background but that should be minimal for its own functionality.

Harbour QA testing is mostly done with PC USB cable connection, application minimized to home screen and display is turned off. In this state application should not block suspend and wake ups should be minimal. Suspend is blocked by wake locks and easy test for that is catting /sys/power/wake_lock file. The file should be empty normally if nothing from user space is not blocking suspend. If application is using e.g. audio, then file should include "mce_cpu_keepalive" string. Powertop output is easy to take before opening application and compare those results when application is minimized to home screen.

Hopefully this post will help developers!

Harbour QA process is using powertop tool. I'll try We need pointers on how to add some instructions how developer can debug and reproduce similar problems. This needs enabled developer mode on the Jolla device.

Steps to install powertop from command line:

1. Add mer-tools repository: "ssu ar mer-tools"
2. Refresh repository cache: "pkcon refresh"
3. Install tool: "pkcon install powertop"

After installing powertop tool, usage is easiest via ssh over USB or WLAN connection. Difference between these connections is that device does not suspend when we have PC USB connection enabled and with WLAN device goes to suspend if we don't have any network traffic and display is turned off.

With powertop tool one can see all running processes which are waking up and how many times in a second. If we strace only our own process, it does not tell all about the system, e.g. when our process has interaction with audio or network. Of course applications are allowed to do things on a background but that should be minimal for its own functionality.

Harbour QA testing is mostly done with PC USB cable connection, application minimized to home screen and display is turned off. In this state application should not block suspend and wake ups should be minimal. Suspend is blocked by wake locks and easy test for that is catting /sys/power/wake_lock file. The file should be empty normally if nothing from user space is not blocking suspend. If application is using e.g. audio, then file should include "mce_cpu_keepalive" string. Powertop output is easy to take before opening application and compare those results when application is minimized to home screen.

Hopefully this post will help developers!that.

We need pointers on how to debug that.that and how it's tested in Harbour QA.