Closed
Bug 823253
Opened 11 years ago
Closed 11 years ago
Remove StageFright decoding blocklisting on Froyo, GB, HC
Categories
(Core Graveyard :: Widget: Android, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla21
People
(Reporter: scoobidiver, Assigned: cajbir)
References
Details
Attachments
(4 files, 2 obsolete files)
1.28 KB,
patch
|
bjacob
:
review+
|
Details | Diff | Splinter Review |
1.09 KB,
patch
|
bjacob
:
review+
|
Details | Diff | Splinter Review |
1.29 KB,
patch
|
bjacob
:
review+
|
Details | Diff | Splinter Review |
1.11 KB,
patch
|
bjacob
:
review+
|
Details | Diff | Splinter Review |
Currently, the StageFright decoding is blocked on the Android API level lower than 14 but bug 787228, bug 805700, and bug 821160 allow the feature so it should be unblocked, maybe partially like in API level 15.
Comment 2•11 years ago
|
||
FWIW --- I just fail at being the single point of failure for all gfx/h264 blacklisting bugs. The most likely to be successful course of action that I can see here, is along the lines of: 1. Bring this bug to Maire Reavy and/or Brad Lassey 's attention 2. They then find someone from mobile or media teams to work on this The gfx team is swamped at the moment with the layers refactoring.
Comment 3•11 years ago
|
||
(In reply to Benoit Jacob [:bjacob] from comment #2) > FWIW --- I just fail at being the single point of failure for all gfx/h264 > blacklisting bugs. The most likely to be successful course of action that I > can see here, is along the lines of: > 1. Bring this bug to Maire Reavy and/or Brad Lassey 's attention > 2. They then find someone from mobile or media teams to work on this > The gfx team is swamped at the moment with the layers refactoring. Chris, Anthony - I'm not sure if you or anyone in NZ has the time and are comfortable taking over the blacklisting code itself from bjacob. If not, we can ask blassey if he has someone. All -- Regardless of who takes over for bjacob, I feel we need to target modifying the blacklist code to allow working GB and HC devices (which have been tested/verified by QA) before Firefox 21 uplifts to Aurora (in approximately 2 weeks -- Feb 18).
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to Maire Reavy [:mreavy] from comment #3) > > All -- Regardless of who takes over for bjacob, I feel we need to target > modifying the blacklist code to allow working GB and HC devices (which have > been tested/verified by QA) before Firefox 21 uplifts to Aurora (in > approximately 2 weeks -- Feb 18). Which devices have been tested/verified by QA? In the absence of this information I'm modifying the code for the devices I've tested.
Assignee | ||
Comment 6•11 years ago
|
||
Attachment #714220 -
Flags: review?(bjacob)
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 714220 [details] [diff] [review] White HTC Gingerbread devices Oops, got the versions wrong. Will upload new one shortly.
Attachment #714220 -
Flags: review?(bjacob)
Assignee | ||
Comment 8•11 years ago
|
||
Attachment #714220 -
Attachment is obsolete: true
Attachment #714225 -
Flags: review?(bjacob)
Assignee | ||
Comment 9•11 years ago
|
||
Attachment #714242 -
Flags: review?(bjacob)
Assignee | ||
Comment 10•11 years ago
|
||
Attachment #714252 -
Flags: review?(bjacob)
Assignee | ||
Comment 11•11 years ago
|
||
Fix error where I was including the Froyo version range.
Attachment #714242 -
Attachment is obsolete: true
Attachment #714242 -
Flags: review?(bjacob)
Attachment #714254 -
Flags: review?(bjacob)
Assignee | ||
Comment 12•11 years ago
|
||
Attachment #714256 -
Flags: review?(bjacob)
Updated•11 years ago
|
Attachment #714225 -
Flags: review?(bjacob) → review+
Updated•11 years ago
|
Attachment #714256 -
Flags: review?(bjacob) → review+
Updated•11 years ago
|
Attachment #714252 -
Flags: review?(bjacob) → review+
Updated•11 years ago
|
Attachment #714254 -
Flags: review?(bjacob) → review+
Assignee | ||
Comment 13•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/cef45c1cb7d4 https://hg.mozilla.org/integration/mozilla-inbound/rev/50dc45f30b22 https://hg.mozilla.org/integration/mozilla-inbound/rev/d5cb684d6b76 https://hg.mozilla.org/integration/mozilla-inbound/rev/8a5523cc2812
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Comment 14•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/cef45c1cb7d4 https://hg.mozilla.org/mozilla-central/rev/50dc45f30b22 https://hg.mozilla.org/mozilla-central/rev/d5cb684d6b76 https://hg.mozilla.org/mozilla-central/rev/8a5523cc2812 Please be more careful with bug numbers...
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Reporter | ||
Comment 15•11 years ago
|
||
I've updated https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#On_Android_2 accordingly (that should have been done by the assignee). Are there both StafeFright HW and SW decoding on those Android versions or only HW decoding?
Assignee | ||
Comment 16•11 years ago
|
||
(In reply to Scoobidiver from comment #15) > I've updated > https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#On_Android_2 > accordingly (that should have been done by the assignee). The assignee didn't even know it existed, but thanks for pointing it out. > Are there both StafeFright HW and SW decoding on those Android versions or > only HW decoding? It depends. Some devices are HW only (some Froyo devices), others are HW and SW. I'm sure there are SW only ones out there too. Our implementation picks whatever the device can do.
Comment 17•11 years ago
|
||
Did this need to land on mozilla-aurora/mozilla-beta?
Comment 18•11 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #17) > Did this need to land on mozilla-aurora/mozilla-beta? I would suggest uplifting to aurora.
Updated•10 years ago
|
tracking-fennec: ? → ---
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•