We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Headset doesn't control videos anymore.

  • 1 cavab
  • 0 have this problem
  • 7 views
  • Last reply by Paul

more options

I have a Shokz headset with volume and pause/play buttons. I watch videos on my Samsung s21+ using Firefox (more privacy, and easier to have multiple videos up with tabs comparedto YouTube app.

It worked fine up till today, when the pause/play button no longer does anything. I tried restarting the phone, closing and opening the Firefox (Ff) app, force-stopping the Ff app, and turning the headset off amd on. The headset functions correctly in other apps, just not Ff.

I don't want to uninstall and reinstall Ff if I can avoid it, but would that even work? I've done all I can short of that, but it still doesn't work.

I have a Shokz headset with volume and pause/play buttons. I watch videos on my Samsung s21+ using Firefox (more privacy, and easier to have multiple videos up with tabs comparedto YouTube app. It worked fine up till today, when the pause/play button no longer does anything. I tried restarting the phone, closing and opening the Firefox (Ff) app, force-stopping the Ff app, and turning the headset off amd on. The headset functions correctly in other apps, just not Ff. I don't want to uninstall and reinstall Ff if I can avoid it, but would that even work? I've done all I can short of that, but it still doesn't work.

All Replies (1)

more options

Hi

This does appear to be an issue that our developers are aware of and are looking into. You can follow progress on this and add comments at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1827583