search

ubports / ubuntu-touch

Ubuntu Touch's issue inbox is now migrated to GitLab.
https://gitlab.com/ubports/ubuntu-touch
1.28k stars 110 forks source link

Load is constantly above 2.0 #777

Closed ruedigerkupper closed 5 years ago

ruedigerkupper commented 6 years ago

On my Nexus 5, load is constantly around 2.3 with the phone just sitting there and doing (apparently) nothing. Is this to be expected? I see dekkod taking up around 50% of CPU, but even after I killed the process, load does not go down.

doniks commented 6 years ago

which dekko?

mauricioduarte01 commented 6 years ago

There is a WIP dekko2 for xenial which is not working yet (I think it only works when using previous config from Vivid) and its also a battery drainer so I suggest uninstalling it from Xenial until a more stable version is released.

ruedigerkupper commented 6 years ago

Thanks, deinstalled it. The notifications daemon was still working, I got push notifications for new mail. That's why I kept it installed.

BTW, did soemone notice you cannot uninstall old vivid apps from the openstore?

ruedigerkupper commented 6 years ago

Deinstalling dekko did not help reducing the load. Still constantly above 2.

ruedigerkupper commented 6 years ago

Need to add that although deinstalling Dekko did not help with the load, it greatly improved battery life time! Life time has almost doubled (but this is on a already worn-out battery. With Dekko it lasted less than 24h, now it's regularly 1,5–2 days. Since Dekko is for me one of the essential apps that should come preinstalled, its battery demand should be reduced.

UniversalSuperBox commented 5 years ago

Coming back through some older bugs, and I don't believe this one should continue to stay on the radar. The load average is a complicated measure of processes that are waiting on a system resource. Between the Android container and the power management of Android devices, it is possible that having a load average of around 2 on a 4-core device is normal.

As for the issues with Dekko, they should be tracked on its bug tracker: https://gitlab.com/dekkoproject/dekko/issues