We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-02-13 15:08:30 +0200 |
While I am quite happy with the Jolla battery standby time, I have noticed that if I am listening to music or podcasts, my battery is draining quite much faster than when I am just using apps.
Looking at the "top" output, it shows that pulsaudio has an average load of around 20% on the CPU while music is playing.
Is this normal are there any possibilities for optimization?
2 | No.2 Revision |
While I am quite happy with the Jolla battery standby time, I have noticed that if I am listening to music or podcasts, my battery is draining quite much faster than when I am just using apps.
Looking at the "top" output, it shows that pulsaudio has an average load of around 20% on the CPU while music is playing.
Is this normal and are there any possibilities for optimization?
3 | retagged |
While I am quite happy with the Jolla battery standby time, I have noticed that if I am listening to music or podcasts, my battery is draining quite much faster than when I am just using apps.
Looking at the "top" output, it shows that pulsaudio has an average load of around 20% on the CPU while music is playing.
Is this normal and are there any possibilities for optimization?
4 | retagged |
While I am quite happy with the Jolla battery standby time, I have noticed that if I am listening to music or podcasts, my battery is draining quite much faster than when I am just using apps.
Looking at the "top" output, it shows that pulsaudio has an average load of around 20% on the CPU while music is playing.
Is this normal and are there any possibilities for optimization?
5 | No.5 Revision |
While I am quite happy with the Jolla battery standby time, I have noticed that if I am listening to music or podcasts, my battery is draining quite much faster than when I am just using apps.
Looking at the "top" output, it shows that pulsaudio has an average load of around 20% on the CPU while music is playing.
Is this normal and are there any possibilities for optimization?
UPDATE March 2015: At some point of time (probably with one of the updates) the problem disappeared.