[mako] high cpu usage when playing audio via speaker

Bug #1373392 reported by Andrew Hayzen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Expired
High
Unassigned

Bug Description

$ system-image-cli -i
current build number: 253
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-09-24 00:51:54
version version: 253
version ubuntu: 20140923.1
version device: 20140923.1
version custom: mako-0.6

I noticed that when playing audio via the speaker/headphones the CPU usage is higher than when playing via a paired bluetooth speaker.

Speaker CPU usage:
Format pulse media-hub
m4a 30 20
flac 30 15
mp3 25 20

Bluetooth Speaker CPU usage:
Format pulse media-hub
m4a 10 15
flac 10 10
mp3 15 10

It has been suggested that changing the buffer size may resolve this issue.

Tags: pulse-touch
Changed in pulseaudio (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ricardo Salveti (rsalveti)
Revision history for this message
Jim Hodapp (jhodapp) wrote :

This is an issue that needs to be optimized for each supported device platform. It's currently optimized for krillin, but not yet for the nexus 4, 7 or 10.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

tags: added: pulse-touch
Changed in pulseaudio (Ubuntu):
status: Confirmed → Incomplete
assignee: Ricardo Salveti (rsalveti) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]

Changed in pulseaudio (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.