Remove StageFright decoding blocklisting on Froyo, GB, HC

RESOLVED FIXED in mozilla21

Status

()

RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: scoobidiver, Assigned: cajbir)

Tracking

Trunk
mozilla21
ARM
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments, 2 obsolete attachments)

(Reporter)

Description

6 years ago
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.
Is this happening sometime soon?
tracking-fennec: --- → ?
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.
(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 4

6 years ago
I'll take it.
Assignee: nobody → chris.double
(Assignee)

Comment 5

6 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

6 years ago
Created attachment 714220 [details] [diff] [review]
White HTC Gingerbread devices
Attachment #714220 - Flags: review?(bjacob)
(Assignee)

Comment 7

6 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

6 years ago
Created attachment 714225 [details] [diff] [review]
Part 1: Whitelist HTC Gingerbread devices
Attachment #714220 - Attachment is obsolete: true
Attachment #714225 - Flags: review?(bjacob)
(Assignee)

Comment 9

6 years ago
Created attachment 714242 [details] [diff] [review]
Part 2: Whitelist LG Froyo devices
Attachment #714242 - Flags: review?(bjacob)
(Assignee)

Comment 10

6 years ago
Created attachment 714252 [details] [diff] [review]
Part 3: Whitelist Samsung Gingerbread devices
Attachment #714252 - Flags: review?(bjacob)
(Assignee)

Comment 11

6 years ago
Created attachment 714254 [details] [diff] [review]
Part 2: Whitelist LG Froyo devices

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

6 years ago
Created attachment 714256 [details] [diff] [review]
Part 4: Whitelist Samsung Honeycomb devices
Attachment #714256 - Flags: review?(bjacob)
Attachment #714225 - Flags: review?(bjacob) → review+
Attachment #714256 - Flags: review?(bjacob) → review+
Attachment #714252 - Flags: review?(bjacob) → review+
Attachment #714254 - Flags: review?(bjacob) → review+
(Assignee)

Updated

6 years ago
Status: NEW → ASSIGNED
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
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
(Reporter)

Comment 15

6 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

6 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.
Did this need to land on mozilla-aurora/mozilla-beta?
(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.
(Reporter)

Updated

6 years ago
Depends on: 847837
(Reporter)

Updated

6 years ago
Depends on: 859032
(Reporter)

Updated

6 years ago
Depends on: 864734
(Reporter)

Updated

6 years ago
Depends on: 874810
tracking-fennec: ? → ---
You need to log in before you can comment on or make changes to this bug.