Closed Bug 1363547 Opened 8 years ago Closed 4 years ago

Video corruption with LG D605 Optimus L9II

Categories

(Firefox for Android Graveyard :: Audio/Video, defect)

53 Branch
Unspecified
Android
defect
Not set
normal

Tracking

(firefox53 wontfix, firefox54 wontfix, firefox55 fix-optional, firefox56 fixed)

RESOLVED INCOMPLETE
Firefox 56
Tracking Status
firefox53 --- wontfix
firefox54 --- wontfix
firefox55 --- fix-optional
firefox56 --- fixed

People

(Reporter: philipp, Assigned: JamesCheng)

References

Details

Attachments

(4 files, 1 obsolete file)

Attached image 2017-05-09-23-44-25.png (obsolete) —
We got a report from a user on a LG D605 Optimus L9II device about video playback corruption since 1-2 weeks which sounds very similar to the regression from the adaptive playback feature that was also observed on some samsung s3/s4 models.
Attached image error condition
Attachment #8866079 - Attachment is obsolete: true
Thanks for reporting this issue. We can add this device into blacklist for solving this issue. But we do not have this device to ensure the "Model ID". I've build an APK which may display the model ID when playing the video. https://queue.taskcluster.net/v1/task/U2-E1LyNRlWTtI68h1bimA/runs/0/artifacts/public/build/target.apk Please see bug1360408 comment 19 for details. If we can have the contact with user directly or the real device. we can make this bug move on.
Attached image Model Id.png
the user reported back and the ModelId is LG-D605
Flags: needinfo?(jacheng)
Thank you for providing the model ID. Hi John, I add this model into blacklist, please review it, thank you.
Flags: needinfo?(jacheng)
Comment on attachment 8883424 [details] Bug 1363547 - Block LG D605 Optimus L9II for adaptive playback. https://reviewboard.mozilla.org/r/154322/#review159402
Attachment #8883424 - Flags: review?(jolin) → review+
Assignee: nobody → jacheng
Pushed by jacheng@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dfa61b6f9e93 Block LG D605 Optimus L9II for adaptive playback. r=jolin
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 56
Philipp, any chance you can get the fix verified by the affected user?
Flags: needinfo?(madperson)
the user was replying that the issue wasn't solved when testing it with the latest nightly on their phone.
Status: RESOLVED → REOPENED
Flags: needinfo?(madperson)
Resolution: FIXED → ---
I think currently I have nothing to do to handle this bug. I suspect that the user didn't use the Nightly with this patch phased in.... Since the symptom snapshot almost the same as other Samsung issues... Is there any chance to get the user's log from adb logcat or ask user to test again with latest Nightly(also ask the user with the build date of Nightly)?
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: REOPENED → RESOLVED
Closed: 8 years ago4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: