We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2019-07-19 10:02:24 +0200

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. It can be followed with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. It can be followed Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

This time it does not depend on Ambience switching but only restarts of the device.

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

This time it does not depend on Ambience switching but only restarts of the device.

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

This time it does not depend on Ambience switching but only restarts of the device.

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

This time it does not depend on Ambience switching but only restarts of the device.

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

[Bug] Voicecall-ui preload process constant cpu usage

This began in SFOS 3.1.0.11. It is very similar to this other already fixed issue: https://together.jolla.com/question/191784/bug-switching-ambience-triggers-constant-cpu-usage-on-voicecall-ui-process

This time it does not depend on Ambience switching but only restarts of the device.

Immediately after the phone (Xperia X) has been restarted, voicecall-ui --preload process gets stuck running at 1 to 1.6 % CPU capacity. Checked with the top command.

The situation can be cleared simply by starting the Phone app once.

Update

Fixed in SFOS 3.2.0.12