High CPU usage with flashlight on

REPRODUCIBILITY: 100%
OS VERSION: 4.4.0.64
HARDWARE: 10 III
UI LANGUAGE: Norwegian
REGRESSION: ?

DESCRIPTION:

When flashlight is activated CPU usage goes higher than expexted.

PRECONDITIONS:

N/A

STEPS TO REPRODUCE:

  1. Enable flashlight
  2. Look at CPU usage

EXPECTED RESULT:

No high CPU usage.
My Xperia X does not show a noticeable CPU usage.

ACTUAL RESULT:

CPU goes :up:

MODIFICATIONS:

ADDITIONAL INFORMATION:

CSD tool without flashlight on

CSD tool with flashlight on

top with flashlight on

Mem: 3081592K used, 2558520K free, 21572K shrd, 35392K buff, 781412K cached
CPU: 12.7% usr  3.5% sys  0.4% nic 81.9% idle  0.0% io  1.0% irq  0.2% sirq
Load average: 3.33 3.21 2.04 2/1311 26712
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
 3549  3127 camerase S    10.7g200.3   7 13.9 {provider@2.4-se} /vendor/bin/hw/android.hardware.camera.provider@2.4-service_64
 3624  3127 media    S    67696  1.2   1  1.1 /usr/libexec/droid-hybris/system/bin/minimediaservice
 3200  3127 logd     SN   10.3g191.8   3  0.2 /system/bin/logd
 5866  5864 defaultu SN    911m 16.5   7  0.1 /usr/bin/csd
  343     2 root     IW       0  0.0   2  0.1 [kworker/u16:9-c]
    8     2 root     DW       0  0.0   0  0.1 [kworker/u16:0+i]
26378  5339 defaultu S     738m 13.3   7  0.1 /usr/bin/jolla-settings-system-flashlight
2 Likes

I have the same behaviour on my X10 II.

This is likely due to the flashlight actually turning on the whole camera and probably hiding a viewport in the background.

Assuming the camera is as horrible as other Sonys’ you should hear the actuator while it is trying to autofocus if you move e.g. your hand closer and away from it (the 10 III also sports OIS).

Does enabling the torch without having a viewport require Camera2 API here and why can’t the LED be triggered from within sysfs (by using torch0_trigger)?

1 Like

Yes, I can hear it. I leave those other questions for the developers. :slight_smile: :camera_flash:

1 Like

Thanks for creating the bug report @emva. I’ve copied the details to our internal bug tracker, and so have tagged this as “tracked”. If we have updates to share about it we’ll do our best to post them back here.

1 Like