Playing video has audio crackling
Since upgrading from Andriod 8 to ver. 9 (security patch level March 1 2019), my Firefox videos now have audio issues and make crackling noise. Issue occurs on any video I play in Firefox and I confirmed it occurs on YouTube, Vimeo, and any other video hosting website. Issue does not occur with Chrome.
I have; Rebooted my phone, cleared cache, deleted Firefox data, and even re-installed Firefox from scratch. Issue still occurring. I have had this phone, with Firefox, for over a year with no issues and last night's Android update has triggered this problem.
Device details: -Samsung Galaxy S8 (SM-G950W) -Andriod version 9 (kernel ver. 4.4.153-15485298) -Software update version: G950WVLU5CSC1/G950WOYA5CSC1/G950WVLU5CSC1 -Firefox version 66.0.2
Выбранное решение
Hi Baldape, Confirmed this problem no longer occurs if using Firefox Beta 68.0b7 or Firefox Nightly 68.0a1 (2019-06-05). Test with these updated versions was successful as audio was clean/clear when playing any video (over WiFi).
Issue will likely go away once current FF release 67 is updated to 68. Ref. bug 1552665
https://bugzilla.mozilla.org/show_bug.cgi?id=1552665
Прочитайте этот ответ в контексте 👍 0Все ответы (4)
- note: issue happens with headphones or built in speaker (when playing video in FF). Tested VLC player and Netflix app and confirmed audio problem does not occur.
I regret doing the OS update as I use Firefox on a daily basis for playing video. Hopefully a fix or workaround can be found shortly.
Also confirmed;
- Factory reset my phone, issue still occuring
- Firefox 67 (beta) and 68.x (nightly) both have the same issue.
- Issue only occurs when streaming on WiFi
Изменено newbreed2001
Same exact problem, Only difference is the security patch level is April 1st 2019.
Выбранное решение
Hi Baldape, Confirmed this problem no longer occurs if using Firefox Beta 68.0b7 or Firefox Nightly 68.0a1 (2019-06-05). Test with these updated versions was successful as audio was clean/clear when playing any video (over WiFi).
Issue will likely go away once current FF release 67 is updated to 68. Ref. bug 1552665