Closed Bug 1895471 Opened 5 months ago Closed 5 months ago

Choppy video playback when looping

Categories

(Core :: Audio/Video: Playback, defect)

Firefox 127
All
Android
defect

Tracking

()

RESOLVED FIXED
127 Branch
Tracking Status
firefox127 --- fixed

People

(Reporter: e412byoy7, Assigned: kinetik, NeedInfo)

References

Details

Attachments

(1 file)

Steps to reproduce:

Watch any video on Tiktok.
Device: Moto G54

Actual results:

Video plays as expected on the first run, but on the second and succeeding loops, playback is choppy.

Expected results:

Videos should play in a loop without frame drops.

Regression of Bug 1872354 it seems

See Also: → 1872354

Hello, would you mind to following this instruction (it's for desktop, but we have about:logging on mobile as well) to capture a profiled result?
Thank you!

Flags: needinfo?(e412byoy7)

Per comment1, set the regression.

Keywords: regression
Regressed by: 1872354
See Also: 1872354

NI john and kinetik because this bug seems a regression caused by bug 1872354.

Flags: needinfo?(kinetik)
Flags: needinfo?(jolin)

Adding dependency to bug 1894401, where the fix will be landed.

Depends on: 1894401
Flags: needinfo?(kinetik)
Flags: needinfo?(jolin)
Flags: needinfo?(e412byoy7)

Also, moving bug 1872354 from Regressed by back to See Also. (The fix was cherry-picked there for firefox126.)

No longer regressed by: 1872354
See Also: → 1872354
Keywords: regression
Assignee: nobody → kinetik
Status: NEW → ASSIGNED
Blocks: 1877948

I'll land the Android AAudio fix for Fx127 here, since there's an unrelated Windows issue blocking the libcubeb update in bug 1894401.

No longer depends on: 1894401
Pushed by mgregan@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f262bae431fa Uplift cubeb AAudio timing fix for reused streams. r=cubeb-reviewers,pehrsons
Blocks: 1872354
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch

(In reply to Alastor Wu [:alwu] from comment #2)

Hello, would you mind to following this instruction (it's for desktop, but we have about:logging on mobile as well) to capture a profiled result?
Thank you!

It doesn't work sadly, the dropdown list of "Logging preset:" is completely empty in Nightly 127.0a1, I am unable to select the "Media Playback" profile...

Flags: needinfo?(alwu)

Sadly have to reopen, still not fixed on nightly 127.0a1 (Build #2016019535), hg-0d84aa48c2d6+
(on Moto G54, Android 13).
:/

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

(In reply to Dan from comment #11)

It doesn't work sadly, the dropdown list of "Logging preset:" is completely empty in Nightly 127.0a1, I am unable to select the "Media Playback" profile...

Sorry to hear that, I've filed the bug 1896982 for the logging problem.

Flags: needinfo?(alwu)

(In reply to Dan from comment #12)

Sadly have to reopen, still not fixed on nightly 127.0a1 (Build #2016019535), hg-0d84aa48c2d6+
(on Moto G54, Android 13).
:/

Kinetik, do you have any thought about this? Do we have another way to capture cubeb logs on Android? Thanks!

Flags: needinfo?(kinetik)

(In reply to Alastor Wu [:alwu] from comment #13)

(In reply to Dan from comment #11)

It doesn't work sadly, the dropdown list of "Logging preset:" is completely empty in Nightly 127.0a1, I am unable to select the "Media Playback" profile...

Sorry to hear that, I've filed the bug 1896982 for the logging problem.

Ah, in that case it seems nobody moved bug 1896324 into the right Product/Component, argh. :P Marked duplicate.

Hi Dan, sorry to hear that the fix doesn't work on your phone. I tried Fenix Nightly Build#2016020495 on my Pixel 3 and couldn't reproduce the issue.

Could you please connect your phone via about:debugging and use Profile performance to record a profile with the Media preset, then upload it and share the link here? Thank you very much!

Flags: needinfo?(e412byoy7)

Doesn't show up, I tried everything on that article, and https://developer.android.com/tools/adb doesn't explain how to install Android Debug Bridge from Android Tools on my computer, although this part in your linked page https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugging/#connecting-to-a-remote-device links to that article which should explain how to install it....... I'm getting super frustrated here!!

Flags: needinfo?(e412byoy7)

NEVERMIND, I had to approve some weird thing on my phone, that step is NOT mentioned in https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugging/ it seems!!!

I can't reproduce anymore on Build #2016020495, hg-45d7400ced7e+ , interesting! Did this patch only land after Build #2016019535, hg-0d84aa48c2d6+ or what just happened here?

Flags: needinfo?(jolin)
Flags: needinfo?(kinetik)

(In reply to Dan from comment #19)

I can't reproduce anymore on Build #2016020495, hg-45d7400ced7e+ , interesting! Did this patch only land after Build #2016019535, hg-0d84aa48c2d6+ or what just happened here?

Yes, the patch landed after 0d84aa48c2d6 (first nightly build with this patch was ee7969730d0c). Thanks for confirming the fix, I'll mark this bug as resolved.

Status: REOPENED → RESOLVED
Closed: 5 months ago5 months ago
Resolution: --- → FIXED
Flags: needinfo?(jolin)

Ok would be nice if Pulsebot could be updated to include a date when it is expected to be published on Google Play, whenever Pulsebot posts about an Android bugfix push. That could've avoided all my debugging troubles (and of all other future bugzilla Android-bugs users)

Flags: needinfo?(kinetik)
Severity: -- → S2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: