[android] AudioFlinger cannot acquire wakelock from powermanager service

Bug #1102415 reported by Ricardo Salveti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
touch-preview-images
Invalid
Medium
Ricardo Salveti

Bug Description

Powermanager is a JAVA based service at Android, which is responsible for exporting the acquire/release methods for general usage at the Android Platform code.

AudioFlinger needs to acquire a wakelock in order to be able to play a sound when it receives a notification and the device is suspended, otherwise the sound may not play or get interrupted during playback.

As in our case we're not yet supporting audio notifications when the device is suspended, this is not critical, but something will probably need to be supported at some point.

And due the service being exported as JAVA, we'd need to implement this acquire/release wakelocks methods via another service, which will probably be used for general power management at the device.

The log which presents this error:
W/AudioFlinger( 165): Thread AudioOut_2 cannot connect to the power manager service

This bug is being reported based on code inspection, not direct testing. It should be reproducible on the Nexus4 which actually goes into full suspend.

Revision history for this message
Tony Espy (awe) wrote :

I'm updating the Status to FixReleased, as I can't reproduce this behavior with phablet-image #76 ( plus updated qtubuntu ).

I caused the indicator go blue by sending text messages, and after each was received, pulled down the messaging indicator and tapped the "clear all" button. I repeated 10 times and for each, the messaging indicator had correctly reset to a white icon.

Changed in manhattan:
status: New → Fix Released
Revision history for this message
Tony Espy (awe) wrote :

Actually I made a mistake and marked the wrong bug FixReleased. I'm resetting the Status back to New so that someone can confirm.

Changed in manhattan:
status: Fix Released → New
Revision history for this message
Tony Espy (awe) wrote :

@Ricardo

Does this occur on all devices? I couldn't reproduce on a Nexus Galaxy, probably because it doesn't fully go into S3. Was this on the Nexus4 only?

Changed in manhattan:
status: New → Incomplete
assignee: nobody → Ricardo Salveti (rsalveti)
Tony Espy (awe)
Changed in manhattan:
status: Incomplete → Confirmed
description: updated
information type: Proprietary → Public
affects: manhattan → touch-preview-images
Revision history for this message
Yuan-Chen Cheng (ycheng-twn) wrote :

as now it switch to pulseaudio and not using audiofliger, the wrong behaviours (press power button to suspend device will stop music playback) still exists.

Bill Filler (bfiller)
Changed in touch-preview-images:
status: Confirmed → Invalid
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.