Closed
Bug 825485
Opened 12 years ago
Closed 11 years ago
Cannot play AAC music content in the browser & music app
Categories
(Core :: Audio/Video, defect)
Tracking
()
People
(Reporter: jsmith, Assigned: cajbir)
References
Details
(Keywords: regression)
Attachments
(2 files)
Build: B2G 18 12/29/2012 Device: Unagi Steps: 1. Go to http://songza.com/listen/acoustic-bedtime-songza/ in the browser Expected: Music should eventually start playing from the phone. Actual: Music fails to start. This works fine on FF Android with the FF Android user agent and FF OS user agent, so it's definitely not a user agent issue. Looking at the attached logcat, it appears we may be bombing on some aac decoding possibly: 12-30 00:18:51.893: E/OMXCodec(2347): Attempting to allocate OMX node 'OMX.qcom.audio.decoder.aac' 12-30 00:18:51.893: E/QC_AACDEC(2347): COmxDecAac::component_init role[OMX.qcom.audio.decoder.aac] 12-30 00:18:51.893: E/QC_BASE(2347): Dev Open Failed[-1] errno[13] 12-30 00:18:51.893: E/QC_BASE(2347): OMX AAC component destroyed 12-30 00:18:51.893: E/OMXCodec(2347): Attempting to allocate OMX node 'OMX.TI.AAC.decode' 12-30 00:18:51.893: E/OMXCodec(2347): Attempting to allocate OMX node 'OMX.google.aac.decoder' 12-30 00:18:51.893: E/OMXCodec(2347): Successfully allocated OMX node 'OMX.google.aac.decoder' 12-30 00:18:51.953: W/AudioFlinger(115): Thread AudioOut_1 cannot connect to the power manager service 12-30 00:18:51.973: E/AudioHardwareMSM76XXA(115): Parsing error in AudioFilter.csv.
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
Reporter | ||
Updated•12 years ago
|
Version: unspecified → Trunk
Comment 2•12 years ago
|
||
This is a regression between Dec 18th -> Dec 29th.. Most likely can get there bissecting builds, but a review of what changed at a driver level will probably provide some insight as well.
Reporter | ||
Updated•12 years ago
|
Keywords: regression
Comment 3•11 years ago
|
||
This should be marked blocking if we broke AAC playback.
Assignee | ||
Comment 4•11 years ago
|
||
Has AAC playback ever worked in the browser? The browser can't access the hardware decoders, for privilege reasons, which is why this fails: > 12-30 00:18:51.893: E/OMXCodec(2347): Attempting to allocate OMX node > 'OMX.qcom.audio.decoder.aac' > 12-30 00:18:51.893: E/QC_AACDEC(2347): COmxDecAac::component_init > role[OMX.qcom.audio.decoder.aac] It does try with the software decoder: > 12-30 00:18:51.893: E/OMXCodec(2347): Successfully allocated OMX node > 'OMX.google.aac.decoder' I'm not sure what the capabilities of that are. I'm on leave till next week and can't investigate until then.
Flags: needinfo?(chris.double)
Comment 5•11 years ago
|
||
It's unclear if AAC ever worked in the browser to bb- unless that's incorrect.
blocking-basecamp: ? → -
Reporter | ||
Comment 6•11 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #5) > It's unclear if AAC ever worked in the browser to bb- unless that's > incorrect. comment 2 implies this is a regression. Renoming. dclarke - can you confirm this was working previously on Dec 18th?
blocking-basecamp: - → ?
Flags: needinfo?(dclarke)
Comment 7•11 years ago
|
||
Let's let Chris Double investigate a bit more when he gets back from PTO.
Flags: needinfo?(dclarke) → needinfo?(chris.double)
Comment 8•11 years ago
|
||
I can confirm that playback on songza was working on December 18th. I have also confirmed that the AAC codec playback seemed to work. E/OMXCodec( 3224): Attempting to allocate OMX node 'OMX.qcom.audio.decoder.aac' E/QC_AACDEC( 3224): COmxDecAac::component_init role[OMX.qcom.audio.decoder.aac] E/QC_BASE ( 3224): Dev Open Failed[-1] errno[13] E/QC_BASE ( 3224): OMX AAC component destroyed E/OMXCodec( 3224): Attempting to allocate OMX node 'OMX.TI.AAC.decode' E/OMXCodec( 3224): Attempting to allocate OMX node 'OMX.google.aac.decoder' E/OMXCodec( 3224): Successfully allocated OMX node 'OMX.google.aac.decoder'
Comment 9•11 years ago
|
||
Thanks for confirming, David.
Assignee: nobody → chris.double
blocking-basecamp: ? → +
Flags: needinfo?(chris.double)
Assignee | ||
Comment 10•11 years ago
|
||
Sadly, visting the URL in comment 0 gives: "We are very sorry to say that due to licensing constraints we cannot allow access to Songza for listeners located outside of the United States and Canada". Is there an URL accessible from NZ?
Assignee | ||
Comment 11•11 years ago
|
||
I put an AAC audio file in an MP4 container at http://cd.pn/a3 and this does not play on b2g. In the absence of an working URL from NZ I'll track down the issue with this and hope it's the same problem.
Reporter | ||
Comment 12•11 years ago
|
||
(In reply to Chris Double (:doublec) from comment #10) > Sadly, visting the URL in comment 0 gives: > > "We are very sorry to say that due to licensing constraints we cannot allow > access to Songza for listeners located outside of the United States and > Canada". > > Is there an URL accessible from NZ? Ack. You are right. I'm in Germany right now and hitting the same thing. (In reply to Chris Double (:doublec) from comment #11) > I put an AAC audio file in an MP4 container at http://cd.pn/a3 and this does > not play on b2g. In the absence of an working URL from NZ I'll track down > the issue with this and hope it's the same problem. Sounds like a good mitigation strategy. Are we getting the same/similar logcat output as above with that test case? If so, that would probably confirm it's close comparison to the problem.
Assignee | ||
Comment 13•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #12) > (In reply to Chris Double (:doublec) from comment #10) > Sounds like a good mitigation strategy. Are we getting the same/similar > logcat output as above with that test case? If so, that would probably > confirm it's close comparison to the problem. Yes, similar logs. I reverted back to a December 18 build and that plays the AAC fine. I'm tracking down the regression now.
Reporter | ||
Updated•11 years ago
|
Summary: Cannot play music on songza.com - works fine on FF Android with FF OS user agent → Cannot play AAC music content in the browser
Comment 14•11 years ago
|
||
Is this the same bug as bug 825523?
Assignee | ||
Comment 15•11 years ago
|
||
A bisect shows the bad commit as: dc040b91b7b6a616f2969e0568b080aa60dccdae is the first bad commit commit dc040b91b7b6a616f2969e0568b080aa60dccdae Author: Chris Jones <jones.chris.g@gmail.com> Date: Mon Dec 24 15:43:10 2012 -0800 Bug 824230 - Handle UNKNOWN_ERROR in OmxDecoder. r=doublec, a=blocking-basecamp Which means it's probably the same as bug 825523 and maybe bug 826083.
Reporter | ||
Updated•11 years ago
|
Summary: Cannot play AAC music content in the browser → Cannot play AAC music content in the browser & music app
Assignee | ||
Comment 17•11 years ago
|
||
Attachment #698519 -
Flags: review?(jones.chris.g)
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Updated•11 years ago
|
Attachment #698519 -
Flags: review?(jones.chris.g) → review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Updated•11 years ago
|
Attachment #698519 -
Flags: checkin?(emorley)
Comment 19•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/0037353015da Presume this also wants to land on b2g18? Does it need additional approval? I can't find the post/wiki page that described the changes as we progressed through the milestones.
Keywords: checkin-needed
Target Milestone: --- → mozilla20
bb+ is still enough for uplift. The patches only need to go to b2g18 now.
Comment 21•11 years ago
|
||
Ok, thank you :-) https://hg.mozilla.org/releases/mozilla-b2g18/rev/7ebd5d44afa1
status-b2g18:
--- → fixed
status-firefox20:
--- → fixed
Updated•11 years ago
|
Attachment #698519 -
Flags: checkin?(emorley) → checkin+
Thanks! :)
Just wondering, is there a reason to have this bug still open?
Reporter | ||
Comment 24•11 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #23) > Just wondering, is there a reason to have this bug still open? Nope.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 25•11 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #23) > Just wondering, is there a reason to have this bug still open? Bugs stay open until the changeset has merged from mozilla-inbound to mozilla-central. In this case I'll leave closed, since will be merging shortly and not worth the dependency bugspam of reopening and closing again.
Updated•11 years ago
|
status-firefox19:
--- → wontfix
Updated•11 years ago
|
status-firefox21:
--- → fixed
Target Milestone: mozilla20 → mozilla21
You need to log in
before you can comment on or make changes to this bug.
Description
•